ISO 10303-239 Activity model coverage
ISO 10303-239 Activity model definitions
ISO 10303-239 Activity definitions
ISO 10303-239 ICOM definitions
Business information requirements
Representing a maintenance work order
Representing reportable item maintenance activity
Representing a reportable item
Representing properties on a reportable item
Representing state of a reportable item
Representing change of Part Number, Serial Number, and NSN
Representing installation/removal position on an aircraft
Representing resource: replaced parts
Representing resource: trades used
Representing a reportable item usage activity
Representing deferred activities
Deferred activities - life properties
Representing reportable item location
Representing related components
Representing Inventory Gain and Loss
Figures
Figure 1 — A4 In scope - Provide support
Figure 2 — A44 In scope - Collect data and provide feedback
Figure 3 — Typical business process using the Aviation Maintenance DEX
Figure 4 — Example exchange points
Figure 5 — UML model representing a reportable activities
Figure 6 — Summary of maintenance feedback information
Figure 7 — UML model representing information that can be exchanged
Figure 8 — UML model representing reportable activities
Figure 9 — Overview of PLCS constructs used to represent maintenance feedback information
Figure 10 — UML class diagram representing a message
Figure 11 — EXPRESS-G diagram for identifying a message and its envelope
Figure 12 — UML model representing a maintenance work order
Figure 13 — EXPRESS-G diagram for work order
Figure 14 — Model representing reportable item maintenance activity
Figure 15 — EXPRESS-G diagram for reportable item maintenance activity
Figure 16 — UML model representing a reportable_item
Figure 17 — EXPRESS-G diagram for identifying a reportable item
Figure 18 — EXPRESS-G diagram for identifying a reportable item
Figure 19 — UML model representing the properties on a reportable item
Figure 20 — EXPRESS-G diagram for properties on a reportable item
Figure 21 — EXPRESS-G diagram for properties on a reportable item
Figure 22 — UML class diagram representing different states of an asset
Figure 23 — UML class diagram representing the state of an asset
Figure 24 — EXPRESS-G diagram for representing a symptom
Figure 25 — EXPRESS-G diagram for state of a reportable item
Figure 26 — Model representing a change in part / serial number
Figure 27 — EXPRESS-G diagram for new Part number , Serial Number and stock code
Figure 28 — Model representing the installation/removal position on an aircraft
Figure 29 — Illustration of a Part assembly
Figure 30 — EXPRESS-G diagram for installation/removal of a reportable item on aircraft
Figure 31 — Illustration of a fitted parts
Figure 33 — Model representing the replaced parts
Figure 34 — EXPRESS-G diagram for recording parts used
Figure 35 — EXPRESS-G diagram for recording parts used
Figure 36 — Model representing the consumed resources
Figure 37 — EXPRESS-G diagram for recording trades used
Figure 38 — UML model representing a reportable item usage activity, e.g. a sortie
Figure 39 — EXPRESS-G diagram for representing a usage activity
Figure 40 — Model representing tasks and extensions
Figure 41 — Summary of information representing task extensions
Figure 42 — EXPRESS-G diagram for representing activities deferred to given life values
Figure 43 — EXPRESS-G diagram for representing activities for deferred faults
Figure 44 — EXPRESS-G diagram for representing limitation of usage
Figure 45 — Model representing the movement of a reportable item to a new location
Figure 46 — EXPRESS-G diagram for identifying the change of a location of a reportable item
Figure 47 — Model representing the relationship of a reportable item to other items
Figure 48 — EXPRESS-G diagram for identifying the related components of a reportable item
Figure 49 — Model representing the addition or loss of a reportable item to the inventory
Figure 50 — EXPRESS-G diagram for representing inventory events
ISO 10303-239 Activity model coverage
ISO 10303-239 Activity model definitions
ISO 10303-239 Activity definitions
ISO 10303-239 ICOM definitions
Business information requirements
Product in focus identification
Product in focus support classification
Task identification and revisioning
Task legal, health and safety advisories
Task special requirements indication
Resource identification (specification)
Material resource hazardous classification
Material resource document reference
Material resource LSA classification
Estimated required elapsed time
Personnel resource estimated labour time;
Alternative / substitute resource requirement
On/off end item classification
Task effectivity / applicability
Task administrative information
Part support classification - repairability
Breakdown element as product in focus
Breakdown element identification
Breakdown element support classification
Task identification and revisioning
Task legal, health and safety advisories
Task special requirements indication
Resource identification (specification)
Material resource hazardous classification
Material resource document reference
Material resource maturity classification
Resource quantity determination
Estimated resource elapsed time
Human resource estimated labour time
Alternative / substitute resource requirement
Computable scheduled task triggers
Non-computable scheduled task triggers
Computable event based task triggers
Non-computable event based task triggers
On/off end item classification
Zone as an explicit zone element i a zone breakdown
Zone provided as a description
Access via a breakdown element
Access provided as a description
Access provided as a task step
Removal route defined as a code
Removal route provided as a description
Removal provided as a task step
Task step identification and categorization
Task effectivity / applicability
Product (Product variant) end item as effectivity condition
Product configuration (Product role) as effectivity condition
Product Modification as Effectivity Conditon
Position in product as effectivity condition
Operational environment as effectivity condition
Operating state as effectivity condition
Customer as effectivity condition
Performing organization as effectivity condition
Task compound conditions representation
Task administrative information
Task revision change description
Message - Date time of data extraction
Message - Sending and recieving organization
Message - Contract information
Optional characterizations of templates
Optional characterization of template assigning_code
Optional characterization of template assigning_descriptor
Optional characterization of template assigning_identification
Optional characterization of template assigning_justification
Optional characterization of templates for assigning referenced document
Optional characterization of templates for property representation
Figures
Figure 1 — A24 Design Support Solution
Figure 2 — A242 Perform Task Analysis
Figure 3 — A2422 Define Potential Task
Figure 4 — A243 Define Support Solution
Figure 5 — A2432 Develop Support Plan
Figure 6 — A24322 Develop Support Plan Logic
Figure 7 — UML Class Model for Product in Focus
Figure 8 — UML Class Model for Task Definition
Figure 9 — UML Class Model for Task Resource
Figure 10 — UML Class Model for Task Usage
Figure 11 — UML Class Model for Task End Item Context
Figure 12 — UML Class Model for Task Structure
Figure 13 — Example on task structure and references to associated task specifications
Figure 14 — Overview of PLCS constructs used to represent Task Specification
Figure 15 — PLCS representation of part as product in focus
Figure 16 — PLCS representation of breakdown element as the product in focus
Figure 17 — PLCS representation of Task definition
Figure 18 — PLCS representation of Task resources
Figure 19 — PLCS representation of Task trigger
Figure 20 — PLCS representation of Task end item context
Figure 21 — PLCS representation of task structure
Figure 22 — PLCS representation of Task dated effectivities
Figure 23 — PLCS representation of Task conditional effectivity assignment
Figure 24 — PLCS representation of Task conditional effectivity condition parameters
Figure 25 — PLCS representation of Task serial effectivities
Figure 26 — PLCS representation of compound conditon
Figure 27 — PLCS representation of Task administrative information
Figure 28 — PLCS representation of Task specification message
Figure 29 — PLCS representation of assigning_code characterization
Figure 30 — PLCS representation of assigning_descriptor characterization
Figure 31 — PLCS representation of assigning_identification characterization
Figure 32 — PLCS representation of assigning_justification characterization