Configuration_and

A type of part in a shipyard catalog which is used in design. The part is referenced by the CAGE of the shipyard in the Common Parts Catalog (CPC). Typically, a Catalog_part embodies a specific form, fit, and function (FFF) which may be satisfied by many OEM Parts.

The configuration_item is a key concept to support explicit configuration management. It represents the identification of a particular configuration, i.e. variation of ship design. A configuration_item is defined with respect to the hulls to which it is applicable.

A Design_occurrence represents the instantiation of a single, location-specific item in the ship design. The Design_occurrence not only represents the design item instance but also provides the means for collecting the properties associated with each design item instance. The properties that apply to a Design_occurrence may vary with respect to the particular type of Design_occurrence (a piping Design_occurrence has different properties from a structural Design_occurrence) or to context (the PDM properties of a Design_occurrence pertain to its configuration management aspect irrespective of design). Its hull applicability characteristics distinguishes a Design_occurrence from a Design_part (which is a design item not associated with any particular hull) as well as from a Physical_occurrence (which denotes one particular item at one particular location on one particular hull).

A Design_part is an instantiation of a Catalog_part used in the design. Typically, a Design_part embodies a specific form, fit, and function (FFF) which may be satisfied by many OEM Parts.

Document_metadata is the collector of information about a document. A Document_metadata instance may be used as placeholder for a document, conveying information such as version and holding a reference to the document per se. A document is a human-readable collection of data, whose content is not structured by definitions in the SCIM. A document, while not an entity per se, is an identifiable resource.

A functional breakdown of all logistics worthy components (functionally significant items) for a given ship class. The breakdown is used to classify all elements of the ship configuration baseline in CDMD-OA. Used during early stage design to maintain weight budget.

An occurrence of a logistics-worthy item (functionally significant item) for which logistics products and data are developed. Logistics occurrences are often identified by a unique Hierarchical Structure Code (HSC) and related to other logistics occurrences via a logistics occurrence assembly.

An entity which defines the data for a logistics support document associated with a piece of equipment. Lsd_metadata holds the data unique to SCLSIS Record Type 3 and is related to Document_metadata which holds common data associated with logistics support documents as well as other types of documents.

An activity is either a ship or a shore-based facility. Only ships have a Ship Type and Hull Number. Initially, ships in new construction do not have a Unit Identification Code (UIC). Physical_occurrence items associated with a ship are Installed_items that make up the current configuration baseline. A training facility is a Naval_activity with selected systems used for training, including Installed_items at the site. A refit facility has alteration items for refit, referred to as Rotatable_pool_items (RPI), which are pulled from specific ships.

A unique item that is the physical manifestation of a Design_occurrence. A Physical_occurrence is applicable to one and only one hull. It represents the tangible item that corresponds to some unique Design_occurrence in the design, and it is the collector for planning, installation, and test-related properties.

A physical part is the physical manifestion of a Design_part. In addition to the designation of vendor and vendor part number, the physical part is designated also by its serial number. For example, a purchased pump will have a serial number. The purchased pump is a physical manifestation of the pump design which has a manufacturer and model number. Like the Design_part, the physical part is independent of hull; it can be used on one hull and later be removed, overhauled, and used on a different hull.

A type of part managed by the US Navy supply system where the part number is specified as a Repairable Identification Code (RIC). A Repairable Part is characterized by a set of physical and logistics properties that may be satisfied by one or more OEM Parts. In addition, if the Repairable Part is an APL or AEL, then it is characterized by a breakdown by quantity of the OEM Parts required for maintenance.

A Rotatable Pool Item (RPI) is a Physical_occurrence item at a refit facility which will be swapped with an Installed_item. In the submarine world, a separate RPI is maintained for each hull. In general, an RPI may replace an Installed_item onboard any member of the class.

The Ship entity represents a ship that operates under the command of the US Navy. It is the primary end product of the design and build activities supported by the IPDE. A ship is a Naval_activity uniquely identified by UIC or by Ship Type and Hull Number.

A hierarchical structure used to organize the systems and sub-systems of the ship into standard functional groups that are used throughout the Navy. The Navy Expanded Ship Work Breakdown Structure (ESWBS) is generally used in ship construction and lifecycle maintenance as the standard system breakdown structure. The ESWBS is defined in the NAVSEA ESWBS Manual, S9040-AA-IDX-010/ESWBS.

Terms