ISE6 Context Schema Overview 10/29/07

ISE6 Context Schema Ship_Class HSC Breakdown (HSC) Design Occurrence HSC Breakdown for Ship Class Example: HSC 512116 Instance in a ship class design Example: Tag Number FM-V1 Key values shown in parentheses Abstract classes shown with dashed line HSC Structure Ship_Class HSC Breakdown (HSC) 0,1 Design Occurrence (GUID) 0,1 0,n 1 CPC Design Part (CAGE, P/N) 0,1 1 Shipyard catalog part (Form, Fit, Function) Example: GV-4-CuN 0,1 Logistics worthy physical instance at an activity, Example: UIC 57075 RIN 00185 Planned Design Occurrence Derived 0,n 0, 1 Naval Activity: on-shore facility or ship Example: UIC 57075 Subcomponent & NHA 0,n 0,n OEM Catalog Part (CAGE, P/N) OEM catalog part Example: Conval 4.00-11G1 J-N22 5E-999 0,1 Logistics Occurrence (Activity Id, Component Id) Naval Activity (Activity Id) 0,n 0,n 1 0,n 0,n 1 1 Ship Installed Item RPI 1,,n 0,n 0,n Installed item onboard a ship. A CDMD OA ship configuration item. Rotatable Pool Item at a shore-based activity. Parent RIC 0,n 0,1 Onboard Spares (Activity Id, Location, RIC) 0,1 Repairable Part (RIC) 0,n 1 ISE6 Context Schema Overview 10/25/07 Spares at a specific stowage location onboard a ship Navy repairable part Example:RIC 99999

Document and Organization Relationships Key values shown in parentheses Abstract classes shown with dashed line Generic Document (Name) EDO (GUID) 0,n 0,n Subcomponent & NHA Logistics Occurrence (Activity Id, Component Id) Logistics Support Document (Serial Number) 1 0,n LSD RIN (LSD RIN) 0,n 1 Organizational Structure 0,n 0,n WCRE WCRC 0,1 0,n Org Unit (Org Unit Id) ISE6 Context Schema Overview 10/25/07

Part Relationships OEM Catalog Part (MF CAGE, P/N) Full Model Separate object for Item of Supply and APL structure Fully models COSAL or APL structure (Includes Qty or item line number) Full maintenance view OEM Catalog Part (MF CAGE, P/N) 0,1 1,n 1,n Top Level 1 0,1 Logistics Occurrence (Activity Id, Component Id) CPC Design Part (Shipyard CAGE, P/N) 0,n 0,n Item of Supply (NSN) 0,n Derived 0,n 0,n 0,n 0,1 Top Level 0,1 0,1 RIC Line Item Derived 0,1 Top Level 0,1 0,n 0,1 0,1 Key values shown in parentheses Abstract classes shown with dashed line Repairable Part (RIC) 0,1 ISE6 Context Schema Overview 10/25/07

Part Relationships: Minimal Model Minimal SCLSIS Model Sufficient for SCLSIS, Does not models COSAL or APL structure Top level catalog view OEM Catalog Part (CAGE, MF P/N) 0,1 0,1 1,n 1 Logistics Occurrence (Activity Id, Component Id) CPC Design Part (Shipyard CAGE, P/N) 0,n 0,n 0,n 0,n 0,1 0,1 0,n Key values shown in parentheses Abstract classes shown with dashed line Repairable Part (RIC) 0,1 ISE6 Context Schema Overview 10/25/07

Logistics Support Document Ship_Class HSC Breakdown Subtypes Abstract classes indicated with dashed lines EDO Logistics Occurrence Document Specific Part Generic Document Logistics Support Document Item of Supply CPC Design Part Installed Item RPI OEM Catalog Part Naval Activity Design Occurrence Repairable Part Ship Planned Design Occurrence Ship_Class HSC Breakdown LSD RIN Org Unit Onboard Spares ISE6 Context Schema Overview 10/25/07

SCLSIS vs Context Schema SCLSIS Record Type 1 Naval Activity CDMD Class Functional File (CFF) Ship Class HSC Breakdown SCLSIS Record Type 2 Logistics Occurrence Repairable Part Org Unit SCLSIS Record Type 3 Logistics Support Document LSD RIN ISE6 Context Schema Overview 10/25/07

ISE6 Context Schema Overview Hull Applicability Ship Class Entities: Ship Class HSC Breakdown Design Occurrence Hull Specific Entities (include Activity Id as part of key): Naval Activity Logistics Occurrence Onboard Spares Relationships between these entity types have hull applicability Hull specific entities have Activity Id as part of key - relationships to Naval Activity is redundant ISE6 Context Schema Overview 10/25/07

ISE6 Context Schema Overview Context Schema Notes Logistics Occurrence Is abstract Encompasses both actual and planned Is an instance of a NIDDESC Physical Part and already incorporates these attributes, i.e. serial number Design Occurrence and CPC Design Part are typically external references. A Generic Document object may be attached to any object Logistics Support Document is attached to a Logistics Occurrence and is managed by LSD RIN. All important relationships are modeled, even if they are potentially derivable. Typically all relationships are not supported within one software system or defined at one life cycle stage. ISE6 Context Schema Overview 10/25/07

ISE6 Context Schema Overview Part Notes Each item of supply has a unique NSN Each item of supply may be stocked from multiple vendors Each OEM catalog part has a unique NSN A Repairable Part (RIC) has a primary NSN and 0 or more component level NSN CPC Catalog contains parts for multiple shipyard with part equivalency relationships CPC Catalog optionally supports values for RIC, NSN, OEM P/N ISE6 Context Schema Overview 10/25/07

Relationship to Other Context Schemas ISE6 Shipbuilding Schemas CPC Part Schema Design Definition CPC Part Item Lifecycle Schema Reference Reference CPC Design Part Design Occurrence Logistics Occurrence Physical instance on a ship Example: UIC 57075 Serial Number 12345 1 0,n OEM Catalog Part OEM catalog part Example: Conval 4.00-11G1 J-N22 5E-999 0, 1 Navy supply part (RIC, NSN) Example: NSN 12345 678901234 RIC 99999 Naval Activity Ship_Class HSC Breakdown 0,1 HSC Structure Installed Item RPI Subcomponent & NHA Physical Occurrence Planned Design Occurrence Onboard Spares Installed item on a ship – A CDMD OA ship configuration item. RPI is at a shore-based activity. Logistics worthy physical instance at an activity, RIN 00185 Derived Item of Supply Repairable Part Org Unit ISE6 Context Schema Overview 10/25/07

Core Product Structure ( NIDDESC+) Not applicable Added Additional Concepts for Logistics Generic Part Generic Component (Parametric definition) Example: 4” Globe Valve Planned Design Occurrence Planned Occurrence Item Instance in a Ship Alt design Example: Tag Number FM-V1 0,n Design Occurrence CPC Design Part Instance in a ship class design Example: Tag Number FM-V1 1 n Occurrence Item Specific Design Part Part used in a design (Form, Fit, Function) Example: GV-4-CuN n 1 Item of Supply Incoporated in Logistics Occurrence Logistics Occurrence Item Instance in logistics system Example: HSC 512116 1 n 0,n 0,1 Ship Class HSC Breakdown 1 Planned Logistics Occurrence Item Planned Logistics Support Item Example: HSC 512116 0,n 0,1 0,1 Specific Supply Part Standard item of supply (NSN) Example: NSN 12345 678901234 RIC 99999 n 1 OEM Part n Specific Implementation Part Part from a specific OEM (Manufacturer, Model #) Example: Conval 4.00-11G1 J-N22 5E-999 0,n Incorporated in Physical Occurrence Logistics Occurrence 1 n Physical Instance on a ship (Hull #, Serial #) Example: Hull 17 Tag Number FM-V1 Serial Number 12345 Physical Occurrence Item Physical Part Physical instance of a part (Serial #) Inventory, spare, or installed Example: Serial Number 12345 0, 1 1 Spare Physical Part Spare Parts on a ship Example: Hull 17 NSN 12345 678901234 Stowage Locker #4 0,n 1 0, 1 Onboard Spares ISE6 Context Schema Overview 10/25/07

Derivation of Context Schema Convert the SAS database model to a UML model.  Foreign keys attributes were removed from the entities and explicit relationships added. Rename SAS entities in general conformance with the NIDDESC CM AP and SCLSIS and to reflect shipyard and potential NPDI usage. Add supertypes for the entities to further link to the NIDDESC CM AP and, in the case of documents, to allow exchange of general documents. Change SAS Component entity to abstract. Remove EB or submarine specific attributes which would not be useful to other organizations Rename SAS attributes to reflect their shipyard usage. Expanding abbreviations in SAS attribute names Extending the schema to include all useful CFF, Type 2, Type 3, and some reference table attributes Attaching SCLSIS names to attributes, e.g. attach UIC to Unit_identification_code. Including both the SCLSIS code value and the description, e.g. RIC and RIC_NOMENCLATURE, ESD and ESD_NOMEN, LSD_TYPE_CODE and LSD_TYPE.   (SCLSIS is implemented as normalized database where codes are used to refer to reference tables of strings.) ISE6 Context Schema Overview 10/25/07