Configuration Management & changes over time Options in Express-G, Tim Turner, 24 May 2012.

5
Configuration Management & changes over time Options in Express-G, Tim Turner, 24 May 2012

Transcript of Configuration Management & changes over time Options in Express-G, Tim Turner, 24 May 2012.

Page 1: Configuration Management & changes over time Options in Express-G, Tim Turner, 24 May 2012.

Configuration Management & changes over time

Options in Express-G,Tim Turner, 24 May 2012

Page 2: Configuration Management & changes over time Options in Express-G, Tim Turner, 24 May 2012.

Design_occurrence_assembly

System_breakdown hsc_breakdown S[0:?]

(INV) system_breakdown HSC_breakdown

Logistics_occurrence_assembly

parent

(INV) assembly_parent

Logistics_occurrence

Logistics_configuration_item

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:?]

(INV) is_located_at is_naval_activity_for S[0:?]

Ship

hsc_breakdown S[0:?]

(INV) ship

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

(INV) assembly_child

child

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

Configuration_item

logistics_occurrence S[0:?]

(INV) config_item S[0:?]

(INV) assembly_parent

parent

(INV) assembly_child

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

(INV) assembly_parent

(INV) physical_part S[0:?]

(INV) design_part physical_occurrence

(INV) part_realization

Configuration_item_definition

definition (INV) config_item

hull_applicability S[1:?]

As-is Model (Express-G)

Does not allow to record config

changes over time or across hulls

Page 3: Configuration Management & changes over time Options in Express-G, Tim Turner, 24 May 2012.

Proposed move for CI?

Design_occurrence_assembly

System_breakdown hsc_breakdown S[0:?]

(INV) system_breakdown HSC_breakdown

Logistics_occurrence_assembly

parent

(INV) assembly_parent

Logistics_occurrence

Logistics_configuration_item

Installed_item

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

is_documented_by S[0:?]

Lsd_metadata

Document_metadata hull_applicability S[1:?] Hull_

applicability

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

(INV) is_located_at is_naval_activity_for S[0:?]

Ship

hsc_breakdown S[0:?]

(INV) ship

(INV) ship_includes S[0:?] applicable_ship

Physical_occurrence

design_occurrence (INV) physical_occurrences S[0:?]

Design_occurrence

occurrence_definition (INV) design_occrrence

Design_occurrence_definition

Hull_applicability S[1:?]

(INV) assembly_child

child

(INV) design_part part_occurrence S[0:?]

Design_part

part_definition

(INV) design_part

Design_part_definition

(INV) physical_part S[0:?] design_part

Physical_part

physical_occurrence

(INV) part_realization

(INV) assembly_child child

Part_assembly

parent (INV) assembly_parent

(INV) log_occurrence S[0:?] design_occurrence

(INV) assembly_parent

parent

(INV) child_assembly

child

Physical_assembly

parent

(INV) parent_assembly

hull_applicability S[1:?]

(INV) assembly_child

child

Configuration_item

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

Hull_applicability S[1:?]

definition (INV) config_item

Configuration_item_definition

*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

Pointing to the relationships that may change with new or

revisions of the configuration – better?

Page 4: Configuration Management & changes over time Options in Express-G, Tim Turner, 24 May 2012.

Alternative? Re-organise relationships (a)

Design_occurrence_assembly

System_breakdown hsc_breakdown S[0:?]

(INV) system_breakdown HSC_breakdown

Logistics_occurrence_assembly

parent

(INV) assembly_parent

Logistics_occurrence

Logistics_configuration_item

Installed_item

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

is_documented_by S[0:?]

Lsd_metadata

Document_metadata hull_applicability S[1:?] Hull_

applicability

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

(INV) is_located_at is_naval_activity_for S[0:?]

Ship

hsc_breakdown S[0:?]

(INV) ship

(INV) ship_includes S[0:?] applicable_ship

Physical_occurrence

design_occurrence (INV) physical_occurrences S[0:?]

Design_occurrence

occurrence_definition (INV) design_occrrence

Design_occurrence_definition

hull_applicability S[1:?]

(INV) assembly_child

child

(INV) design_part part_occurrence S[0:?]

Design_part

part_definition

(INV) design_part

Design_part_definition

(INV) physical_part S[0:?] design_part

Physical_part

physical_occurrence

(INV) part_realization

(INV) assembly_child child

Part_assembly

parent (INV) assembly_parent

(INV) log_occurrence S[0:?] design_occurrence

(INV) assembly_parent

parent

(INV) child_assembly

child

Physical_assembly

parent

(INV) parent_assembly

hull_applicability S[1:?]

(INV) assembly_child

child

Configuration_item

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

hull_applicability S[1:?]

definition (INV) config_item

Configuration_item_definition

Alternative to leave CI as is but modify relationships involving

Hull_applicability to include assembly relationships that might change?

Replaced

Page 5: Configuration Management & changes over time Options in Express-G, Tim Turner, 24 May 2012.

Alternatives? Refine relationships (b)

Design_occurrence_assembly

System_breakdown hsc_breakdown S[0:?]

(INV) system_breakdown HSC_breakdown

Logistics_occurrence_assembly

parent

(INV) assembly_parent

Logistics_occurrence

Logistics_configuration_item

Installed_item

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

is_documented_by S[0:?]

Lsd_metadata

Document_metadata hull_applicability S[1:?] Hull_

applicability

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

(INV) is_located_at is_naval_activity_for S[0:?]

Ship

hsc_breakdown S[0:?]

(INV) ship

(INV) ship_includes S[0:?] applicable_ship

Physical_occurrence

design_occurrence (INV) physical_occurrences S[0:?]

Design_occurrence

occurrence_definition (INV) design_occrrence

Design_occurrence_definition

design_configuration S[1:?]

(INV) assembly_child

child

(INV) design_part part_occurrence S[0:?]

Design_part

part_definition

(INV) design_part

Design_part_definition

(INV) physical_part S[0:?] design_part

Physical_part

physical_occurrence

(INV) part_realization

(INV) assembly_child child

Part_assembly

parent (INV) assembly_parent

(INV) log_occurrence S[0:?] design_occurrence

(INV) assembly_parent

parent

(INV) child_assembly

child

Physical_assembly

parent

(INV) parent_assembly

logistic_configuration S[1:?]

(INV) assembly_child

child

Configuration_item

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

hull_applicability S[1:?]

definition (INV) config_item

Configuration_item_definition

Perhaps better to point from Hull_applicability to these

relationships than other way around – then to rename them?