Navy Configuration & Logistics DEX The storey so far (i.e. W.I.P) UML Overview from Argo Class PLCS SCLSIS DEX Extract Simplified DEX Overview DEX Scope The following are within the scope of this Data Exchange Specification (DEX): – Logistics configuration items – Installed items – Repairable parts – System breakdowns – Hierarchical structure code breakdowns – Logistics configuration items Out of Scope The following are outside the scope of this Data Exchange Specification (DEX): – – – – – – – – – – – – – – Catalog part Configuration_item (pending) Design occurrence (pending) Design occurrence assembly Document metadata Hull applicability (pending) Logistics occurrence Logistics occurrence assembly Lsd metadata Onboard spare part Physical occurrence (pending) Physical occurrence assembly (pending) Rotatable pool item Supply part Note: Pending items are under consideration for inclusion at this time. © OASIS 2010 — All rights reserved PLCS SCLSIS in EXPRESS(1) parent (INV) assembly_parent child (INV) assembly_child Design_occurrence_ assembly Design_ occurrence design_occurrence (INV) log_occurrence S[0:?] System_ breakdown Logistics_ occurrence_assembly parent (INV) assembly_parent child (INV) assembly_child Logistics_ occurrence Lsd_metadata hsc_breakdown S[0:?] (INV) system_breakdown documents_logistics_occurrence S[0:?] (INV) is_documented_by S[0:?] HSC_ breakdown has_characteristics_of (INV) are_characteristics_for S[0:?] Logistics_ configuration_item identifies_supply_support_for (INV) has_supply_support_identified_by S[0:?] ship (INV) hsc_breakdown S[0:?] Ship is_located_at (INV) is_naval_activity_for S[0:?] Installed_item Repairable_ part PLCS SCLSIS in EXPRESS(2) Design_occurrence_assembly parent child (INV) assembly_parent (INV) assembly_child design_occurrence S[0:?] Design_occurrence (INV) config_item S[0:?] design_occurrence (INV) log_occurrence S[0:?] System_breakdown Logistics_occurrence_assembly parent child (INV) assembly_parent Configuration_item logistics_occurrence S[0:?] (INV) config_item S[0:?] Logistics_occurrence (INV) assembly_child hsc_breakdown S[0:?] Lsd_metadata (INV) system_breakdown is_documented_by S[0:?] documents_logistics_occurrence S[0:?] HSC_breakdown hsc_breakdown S[0:?] (INV) ship Ship are_characteristics_for S[0:?] (INV) has_characteristics_of S[0:1] Logistics_configuration_item has_supply_support_identified_by (INV) identifies_supply_support_for S[0:?] is_naval_activity_for S[0:?] (INV) is_located_at Installed_item Repairable_part Wider Context .. Four Trees Logistics Design Part Physical Logistics_occurrence_assembly Design_occurrence_assembly (INV) assembly_parent (INV) assembly_child hsc_breakdown S[0:?] (INV) system_breakdown hull_applicability S[1:?] logistics_occurrence S[0:?] parent (INV) parent_assembly (INV) child_assembly (INV) assembly_parent child (INV) assembly_child occurrence_definition (INV) design_occrrence Design_occurrence Hull_applicability S[1:?] Hull_ applicability parent child Design_occurrence_definition System_breakdown design_occurrence (INV) log_occurrence S[0:?] Logistics_occurrence (INV) config_item S[0:?] design_occurrence (INV) physical_occurrences S[0:?] design_occurrence S[0:?] (INV) config_item S[0:?] Physical_occurrence part_occurrence Design_part hull_applicability S[1:?] Hull_applicability S[1:?] Document_metadata Configuration_item hsc_breakdown S[0:?] (INV) ship design_part (INV) physical_part S[0:?] part_definition physical_occurrence (INV) design_part (INV) part_realization definition (INV) config_item Configuration_item_definition Logistics_configuration_item is_naval_activity_for S[0:?] (INV) is_located_at Lsd_metadata Physical_part is_documented_by S[0:?] documents_logistics_occurrence S[0:?] are_characteristics_for S[0:?] (INV) has_characteristics_of S[0:1] Ship Part_assembly parent child parent child (INV) assembly_parent (INV) assembly_child HSC_breakdown Physical_assembly Installed_item has_supply_support_identified_by (INV) identifies_supply_support_for S[0:?] Repairable_part applicable_ship (INV) ship_includes S[0:?] Design_part_definition Observations • Clearly 4 types of tree structures (whether they be assembly or breakdowns) – Logistics_occurrence_assembly (HSC_breakdown) – Design_occurrence_assembly (System_breakdown) – Physical_assembly – Part_assembly Key Parameters? Serial No’d Effectivity Serial No’s Part No Quantity Logistics_occurrence_assembly Revision Design_occurrence_assembly (INV) assembly_parent (INV) assembly_child hsc_breakdown S[0:?] (INV) system_breakdown hull_applicability S[1:?] logistics_occurrence S[0:?] parent (INV) parent_assembly (INV) child_assembly (INV) assembly_parent child (INV) assembly_child occurrence_definition (INV) design_occrrence Design_occurrence Hull_applicability S[1:?] Hull_ applicability parent child Design_occurrence_definition System_breakdown design_occurrence (INV) log_occurrence S[0:?] Logistics_occurrence (INV) config_item S[0:?] design_occurrence (INV) physical_occurrences S[0:?] design_occurrence S[0:?] (INV) config_item S[0:?] Physical_occurrence part_occurrence Design_part hull_applicability S[1:?] Hull_applicability S[1:?] Document_metadata Configuration_item hsc_breakdown S[0:?] (INV) ship design_part (INV) physical_part S[0:?] part_definition physical_occurrence (INV) design_part (INV) part_realization definition (INV) config_item Configuration_item_definition Logistics_configuration_item is_naval_activity_for S[0:?] (INV) is_located_at Lsd_metadata Physical_part is_documented_by S[0:?] documents_logistics_occurrence S[0:?] are_characteristics_for S[0:?] (INV) has_characteristics_of S[0:1] Ship Part_assembly parent child parent child (INV) assembly_parent (INV) assembly_child HSC_breakdown Physical_assembly Installed_item has_supply_support_identified_by (INV) identifies_supply_support_for S[0:?] Repairable_part applicable_ship (INV) ship_includes S[0:?] Design_part_definition Observations • All ‘Occurrence” breakdown trees (except Physical Occurrences) use Hull_applicability. – Type of serial effectivity of Hull Numbers… • Physical Occurrences have separate ‘direct’ relationship to the ‘Ship’. • Physical Occurrences are realized by (actual) Physical_parts (serialized items). • Physical_parts have a Design_part that can be associated with other Design_parts through Part_assembly. Interpreting Main Structures • Potentially could be either a set of linked assemblies, breakdowns or a mixture of both. – NPDI/SCIM requirements use terminology of both Assembly structures and Breakdowns (specializations). – Generally, assemblies use quantified instance occurrences, whereas breakdowns use elements to represent each occurrence – Generally breakdowns used when trying to attach more information to the tree for through life purposes. Linking breakdowns Logistic_occurrence _assembly / HSC breakdown? Design_occurrence_ assembly / System breakdown? Physical_assembly ? PLCS generally uses the ‘representing breakdown element realization’ template for this purpose.. Could also use the generic Representing_breakdown to build a hybrid model PLCS Breakdown Model Arrangements Basic DEX Structure Using breakdown Instantiations (1) Design_occurr System Breakdown Properties attach here System Bkdn parent/child Sys Brkdn 2 HSC Bkdn Relation Design_occurr Logistic_occur to Design_occurr Relation Logistic_occur HSC Bkdn Props attach here HSC Bkdn parent/child Logistic_occur Adding Physical_part Logistic_occurrence.design_occurrence Physical_occurrence.design_occurrence Part_realization Part_occurrence Using Breakdowns Instantiations (2) Ignore the fact that normally we put the parent at the top & child node underneath… Effectivity & Configuration(2) Multiple breakdowns will require multiple config reps. Items pointing to instances of structure Better – Usage Root & Effectivity Items Usage gives root relationship Effectivity gives valid Structure of HSC breakdown elements Results in Proposed move for CI? Rename to configuration item relationship? Configuration_item_definition definition (INV) config_item Logistics_occurrence_assembly Configuration_item logistics_occurrence S[0:?] Design_occurrence_assembly parent child (INV) assembly_parent (INV) assembly_child (INV) assembly_parent (INV) assembly_childDesign_occurrence_definition Hull_applicability S[1:?] hsc_breakdown S[0:?] System_breakdown design_occurrence (INV) log_occurrence S[0:?] hull_applicability S[1:?] parent (INV) parent_assembly (INV) child_assembly (INV) assembly_parent child (INV) assembly_child Design_occurrence design_occurrence (INV) physical_occurrences S[0:?] Physical_occurrence part_occurrence S[0:?] (INV) design_part Hull_applicability S[1:?] Hull_ applicability parent child occurrence_definition (INV) design_occrrence (INV) system_breakdown Logistics_occurrence Design_part hull_applicability S[1:?] Document_metadata design_part (INV) physical_part S[0:?] part_definition physical_occurrence (INV) design_part (INV) part_realization hsc_breakdown S[0:?] (INV) ship Lsd_metadata Logistics_configuration_item is_naval_activity_for S[0:?] (INV) is_located_at Physical_part is_documented_by S[0:?] documents_logistics_occurrence S[0:?] are_characteristics_for S[0:?] (INV) has_characteristics_of S[0:1] Ship Part_assembly design_occurrence S[0:?] parent child HSC_breakdown Physical_assembly Installed_item has_supply_support_identified_by (INV) identifies_supply_support_for S[0:?] Repairable_part applicable_ship (INV) ship_includes S[0:?] Design_part_definition
© Copyright 2026 Paperzz