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)

PLCS SCLSIS in EXPRESS(2)

Wider Context.. Four Trees Logistics Design Physical Part

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’s Serial No’d Effectivity Part NoQuantityRevision

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 PLCS generally uses the ‘representing breakdown element realization’ template for this purpose.. Logistic_occurrence _assembly / HSC breakdown? Design_occurrence_ assembly / System breakdown? Physical_assembly ? Could also use the generic Representing_breakdown to build a hybrid model

PLCS Breakdown Model Arrangements

Basic DEX Structure

Using breakdown Instantiations (1) System Breakdown Properties attach here System Bkdn parent/child Design_occurr Logistic_occur to Design_occurr Relation Design_occurr Logistic_occur HSC Bkdn parent/child HSC Bkdn Props attach here Sys Brkdn 2 HSC Bkdn Relation

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) Items pointing to instances of structure Multiple breakdowns will require multiple config reps.

Better – Usage Root & Effectivity Items Effectivity gives valid Structure of HSC breakdown elements Usage gives root relationship

Results in Proposed move for CI? Rename to configuration item relationship?