Navy Configuration & Logistics DEX The storey so far (i.e. W.I.P)

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 ScopeThe 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)

Design_occurrence_ assembly

Design_ occurrence

Logistics_ occurrence

Logistics_ occurrence_assembly

System_ breakdown

HSC_ breakdown

Logistics_ configuration_item

Lsd_metadata

Repairable_ part

Installed_item Ship

parent

child

parent

child

(INV) assembly_parent

(INV) assembly_child



(INV) is_documented_by S[0:?]

identifies_supply_support_for

is_located_at

has_characteristics_of

(INV) are_characteristics_for S[0:?]

ship (INV) hsc_breakdown S[0:?]

(INV) is_naval_activity_for S[0:?]

(INV) has_supply_support_identified_by S[0:?]

design_occurrence (INV) log_occurrence S[0:?]

documents_logistics_occurrence S[0:?]

hsc_breakdown S[0:?] (INV) system_breakdown

PLCS SCLSIS in EXPRESS(2)

Design_occurrence_assembly

Logistics_configuration_item

System_breakdown

Lsd_metadata

Installed_item

HSC_breakdown

Logistics_occurrence_assembly

Ship

Configuration_item

Repairable_part

Logistics_occurrence

Design_occurrence

hsc_breakdown S[0:?]

(INV) system_breakdown

parent


has_supply_support_identified_by (INV) identifies_supply_support_for S[0:?]

is_documented_by S[0:?] documents_logistics_occurrence S[0:?]

(INV) is_located_at is_naval_activity_for S[0:?]


design_occurrence (INV) log_occurrence S[0:?]


child

(INV) config_item S[0:?]

design_occurrence S[0:?]

logistics_occurrence S[0:?] (INV) config_item S[0:?]


parent


child

are_characteristics_for S[0:?]

(INV) ship

(INV) has_characteristics_of S[0:1]


System_breakdown hsc_breakdown S[0:?]

(INV) system_breakdown HSC_breakdown


parent




Installed_item

has_supply_support_identified_by (INV) identifies_supply_support_for S[0:?] Repairable_part

is_documented_by S[0:?]

Lsd_metadata

documents_logistics_occurrence S[0:?] (INV) has_characteristics_of S[0:1] are_characteristics_for S[0:?]


Ship


(INV) ship

design_occurrence (INV) log_occurrence S[0:?] Design_occurrence


child

(INV) config_item S[0:?] design_occurrence S[0:?]

Configuration_item

logistics_occurrence S[0:?]



parent


child

Physical_occurrence

Physical_assembly

parent child

(INV) parent_assembly (INV) child_assembly

design_occurrence (INV) physical_occurrences S[0:?]

Design_occurrence_definition

occurrence_definition (INV) design_occrrence

applicable_ship (INV) ship_includes S[0:?]

Hull_ applicability

hull_applicability S[1:?] Hull_applicability S[1:?]

Hull_applicability S[1:?] Document_metadata

Physical_part

Design_part

Part_assembly

parent

child

design_part

Design_part_definition

part_definition

part_occurrence



(INV) physical_part S[0:?]

(INV) design_part physical_occurrence

(INV) part_realization

Configuration_item_definition

definition (INV) config_item

hull_applicability S[1:?]

Wider Context .. Four TreesLogistics 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





parent




Installed_item



Lsd_metadata



Ship


(INV) ship

design_occurrence (INV) log_occurrence S[0:?] Design_occurrence


child

(INV) config_item S[0:?] design_occurrence S[0:?]

Configuration_item

logistics_occurrence S[0:?]



parent


child

Physical_occurrence

Physical_assembly

parent child

(INV) parent_assembly (INV) child_assembly




applicable_ship (INV) ship_includes S[0:?]

Hull_ applicability

hull_applicability S[1:?] Hull_applicability S[1:?]

Hull_applicability S[1:?] Document_metadata

Physical_part

Design_part

Part_assembly

parent

child

design_part


part_definition

part_occurrence



(INV) physical_part S[0:?]

(INV) design_part physical_occurrence





Key Parameters?Serial No’s Serial No’d

Effectivity Part No Quantity Revision

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

Logistic_occur

HSC Bkdn parent/childHSC 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?





parent




Installed_item



Lsd_metadata

Document_metadata hull_applicability S[1:?] Hull_

applicability



Ship


(INV) ship

(INV) ship_includes S[0:?] applicable_ship

Physical_occurrence


Design_occurrence



Hull_applicability S[1:?]


child

(INV) design_part part_occurrence S[0:?]

Design_part

part_definition

(INV) design_part


(INV) physical_part S[0:?] design_part

Physical_part

physical_occurrence


(INV) assembly_child child

Part_assembly

parent (INV) assembly_parent

(INV) log_occurrence S[0:?] design_occurrence


parent

(INV) child_assembly

child

Physical_assembly

parent

(INV) parent_assembly



child

Configuration_item

design_occurrence S[0:?] logistics_occurrence S[0:?]

Hull_applicability S[1:?]



*Revised several relationships based upon naming convention of UML equivalent. E.g. those around the Logistics_configuration_item. However, in the final analysis these may need to be tweaked appropriately for the PLCS interpretation (as UML more flexible than Express?).*

PLCS_SCLSIS_UML_V1_1 From PLCS_SCLSIS_UML_V1; Added link between Phy_occurr and Ship

PLCS_SCLSIS_UML_V1 Re-ordered relationships to allow easier visualization of parent-child trees.

PLCS_SCLSIS_UML_V1_2 Added Hull_applicability - but note, I did not include the global axis placement entity related to this.

PLCS_SCLSIS_UML_V1_3 Adds Document_metadata Note not all relations shown from Doc_metadata

V1_4 adds Design_part, Design_part_definition, Part_ assembly Physical_part Cong item definition

V1_5 adds Document_metadata.hull applicability

Rename to configuration item

relationship?

Documents

Navy Configuration & Logistics DEX The storey so far (i.e. W.I.P)