AP227 Piping Functional - Latest in Interoperability · · 2008-09-13the arrangement in 3-D space of piping components meeting the applicable system specification and with ... required

IPDE Specification Information Requirements

Overview:

Piping Functional

Piping systems are used to convey and process fluids or gases within a variety of engineering products. Generally, a piping system comprises a network of pipes and piping components (fittings and valves), and is attached to processing equipment such as pressure vessels and pumps. Large piping systems are generally attached to some supporting structure through the use of pipe supports and hangers.

Four major application areas corresponding to major stages of piping product life cycle are:

l contract/functional design; l detail design; l production engineering; l support engineering.

Users/developers of piping product information in these stages of product life cycle have different information requirements and views of the product. Users in the contract design stage design view a piping system principally as a functional network of equipment.

Functional design stage designers see piping in much the same way but develop and use much more detailed information concerning operating states of a system, and the characteristics of sub-networks of piping within an overall system (pipelines) in terms of material specifications and flow characteristics. They also, for some systems, develop and use data concerning the loading on, and fixity of, portions of the system in order to evaluate stress levels. The functional view is typically used to identify a preliminary purchasing bill of material in which purchase specification and long lead-time equipment and components are identified. The functional design stage view is also the one which, along with contract specifications, is used in formulating and performing systems testing following installation.

Because of the commonality of views in the contract and functional design stages, they can be combined into a single application area. Detail design users have a three-dimensional arrangements view of piping. They are concerned with the arrangement in 3-D space of piping components meeting the applicable system specification and with ensuring that the arranged components are free from interference with the surrounding environment. This view of the data is also the view that typically supports the final purchasing bills of material.

Production engineering stage users are concerned with defining piping assemblies and the information needed to fabricate the pieces of these assemblies. This information can consist of bending instructions, joining instructions/specifications, and coating instructions. They also specify the installation processes to be used to install such assemblies in the final product and the post-installation tasks to be carried out. The production engineering function creates and makes use of the production bill of material view.

The piping product view taken by users in the support engineering stage is mainly that of the functional design, but from the standpoint of defining the support requirements of the product. Such requirements include spare parts complements, maintenance procedures and related documentation, and operational specifications and documentation.

This chapter of the SCIM (Piping Functional) will focus on the first and fourth of the application areas above – contract/functional design and support engineering. It will specify information concerning items such as operating states, material specifications, and flow characteristics. The previous chapter of the SCIM (Piping Physical) addressed the areas of detail design and production engineering.

The piping functional configuration entails connectivity, sequencing, component size, and schedule, and may include other information, such as equipment tag numbers and requirements to perform consistency checks between the functional and physical representations of the design. This data will include:

l basic engineering data as needed for spatial layout and configuration of systems l references to functional requirements of piping systems, such as stream data and operational characteristics l references to or designation of functional characteristics of components and connected equipment as

required for system design

The SCIM chapter on Piping Functional describes the functional connectivity of a piping system and the functional

2-1

connectivity among objects in that system. It provides the information that describes the functional links and properties of a flow stream in a piping system. It includes information about the segments in the line and the specifications for these segments, such as design criteria, service conditions, and line identifier.

Structure:

PartsSeveral types of entities that are described with a “functional” suffix in this chapter will reference descriptions that come from the detailed Part definitions provided in the Piping Physical Chapter. Among those entities are:

l Piping_system_component_part l Specialty_item_part l Inline_equipment_item_part l Valve_part

Parts Model

Functional InstancesSeveral entities in this chapter of the SCIM have the suffix “functional” attached. In those cases, the entity represents an instance of this item in a 2D representation, rather than the detailed 3D description provided in the design occurrence. For example, as quoted in the SCIM XML: “The Piping_system_component-functional represents an instance of the Piping_system_component in a 2D model.” In general, “functional” is a descriptive adjective that, when applied to an item, refers to the actions, activities, or capabilities, that the item provides or may provide to fulfill a purpose. The functional configuration entails connectivity, sequencing, component size, and schedule, and may include other information, such as equipment tag numbers and requirements to perform consistency checks between the functional and

2-2

Structure:

physical representations of the design. One should note that a functional connection can exist between two items without a physical joining of the items.

Functional Instances Model

Intent:

Motivation:

Entity Name:

Information Requirements: Definition: Properties:

Entity: Piping_system_component_functional

To collect properties that describe a design occurrence of the Piping_system_component in a 2D model.

In order to define the Piping_system_component_functional, specific properties must be captured.

npd:Piping_system_component_functional

The Piping_system_component-functional represents an instance of the Piping_system_component in a 2D model.

None

2-3

XML:

<xtc:Entity name="npd:Piping_system_component_functional" abstract="true"> <xtc:Definition> The Piping_system_component-functional represents an instance of the Piping_system_component in a 2D model. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Specialty_item_functional

To collect properties that describe an instance of the Specialty_item in a 2D model.

In order to define a Specialty_item_functional, certain properties must be captured.

npd:Specialty_item_functional

The Specialty_item-functional represents an instance of the Specialty_item in a 2D model.

None

<xtc:Entity name="npd:Specialty_item_functional"> <xtc:Definition> The Specialty_item-functional represents an instance of the Specialty_item in a 2D model. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Entity: Inline_equipment_item_functional

To collect properties for the functional inline equipment item.

2-4

Motivation:

Entity Name:


XML:

In order to describe the functional use of the Inline equipment item, certain properties must be captured.

npd:Inline_equipment_item_functional

The Inline_equipment_item-functional describes the functional use of the Inline_equipment_item.

None

<xtc:Entity name="npd:Inline_equipment_item_functional"> <xtc:Definition> The Inline_equipment_item-functional describes the functional use of the Inline_equipment_item. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Entity: Valve_functional

To collect properties that describe a design occurrence of the valve in a 2D model.

In order to describe the valve_functional, certain properties must be captured that represent an instance of the valve in a 2D model.

npd:Valve_functional

The Valve-functional represents an instance of the valve in a 2D model.

None

2-5

XML:

<xtc:Entity name="npd:Valve_functional"> <xtc:Definition> The Valve-functional represents an instance of the valve in a 2D model. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Fitting_functional

To collect properties that describe a design occurrence of a planned type of fitting.

In order to define a Fitting_functional, certain properties must be captured.

npd:Fitting_functional

The fitting_functional is a planned type of Fitting, as instanced in a design.

None

<xtc:Entity name="npd:Fitting_functional" abstract="true"> <xtc:Definition> The fitting_functional is a planned type of Fitting, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Entity: Blank_functional

2-6

Intent:

Motivation:

Entity Name:


XML:

To collect properties that describe a design occurrence of a planned type of Blank

In order to define a Blank_functional, certain properties must be captured.

npd:Blank_functional

The Blank_functional is a planned type of Blank, as instanced in a design.

None

<xtc:Entity name="npd:Blank_functional"> <xtc:Definition> The Blank_functional is a planned type of Blank, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:

Information Requirements: Definition:

Entity: Paddle_blank_functional

To collect properties that describe a design occurrence of a planned type of Paddle_blank.

In order to describe a Paddle_blank_functional, certain properties must be captured.

npd:Paddle_blank_functional

2-7

Properties:

XML:

The Paddle_blank_functional is a planned type of Paddle_blank, as instanced in a design.

None

<xtc:Entity name="npd:Paddle_blank_functional"> <xtc:Definition> The Paddle_blank_functional is a planned type of Paddle_blank, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Blank_functional"> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Spectacle_blind_functional

To collect properties that describe a design occurrence of a Spectacle_blind.

In order to describe a Spectacle_blind_functional, certain properties must be captured.

npd:Spectacle_blind_functional

The Spectacle_blind_functional is a planned type of Spectacle_blind, as instanced in a design.

None

<xtc:Entity name="npd:Spectacle_blind_functional"> <xtc:Definition> The Spectacle_blind_functional is a planned type of Spectacle_blind, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Blank_functional">

2-8

<xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Tee_functional

To collect properties that describe a design occurrence of a Tee.

In order to describe a Tee_functional certain properties must be captured.

npd:Tee_functional

The Tee_functional is a planned type of Tee, as instanced in a design.

None

<xtc:Entity name="npd:Tee_functional"> <xtc:Definition> The Tee_functional is a planned type of Tee, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Entity: Orifice_plate_functional

To collect properties that describe a design occurrence of an Orifice_plate.

2-9

Motivation:

Entity Name:


XML:

In order to describe an Orifice_plate_functional, certain properties must be captured.

npd:Orifice_plate_functional

The Orifice_plate_functional is a planned type of Orifice_plate, as in an instanced design.

None

<xtc:Entity name="npd:Orifice_plate_functional"> <xtc:Definition> The Orifice_plate_functional is a planned type of Orifice_plate, as in an instanced design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Entity: Elbow_functional

To collect properties that describe a design occurrence of an elbow.

In order to describe a Elbow_functional, certain properties must be captured.

npd:Elbow_functional

The Elbow_functional is a planned type of Elbow, as instanced in a design.

2-10

XML:

None

<xtc:Entity name="npd:Elbow_functional"> <xtc:Definition> The Elbow_functional is a planned type of Elbow, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Insert_fitting_functional

To collect properties that describe a design occurrence of an Insert_fitting.

In order to describe an Insert_fitting_functional, certain properties must be captured.

npd:Insert_fitting_functional

The Insert_fitting_functional is a planned type of Insert_fitting, as instanced in a design.

None

<xtc:Entity name="npd:Insert_fitting_functional"> <xtc:Definition> The Insert_fitting_functional is a planned type of Insert_fitting, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

2-11

Intent:

Motivation:

Entity Name:


XML:

Entity: Cross_functional

To collect properties that describe a design occurrence of a Cross.

In order to describe a Cross_functional, certain properties must be captured.

npd:Cross_functional

The Cross_functional is a planned type of Cross, as instanced in a design.

None

<xtc:Entity name="npd:Cross_functional"> <xtc:Definition> The Cross_functional is a planned type of Cross, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:

Entity: Coupling_functional

To collect properties that describe a design occurrence of a coupling.

In order to describe a Coupling_functional, certain properties must be captured.

npd:Coupling_functional

2-12


XML:

The Coupling_functional is a planned type of Coupling, as instanced in a design.

None

<xtc:Entity name="npd:Coupling_functional"> <xtc:Definition> The Coupling_functional is a planned type of Coupling, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Lateral_functional

To collect properties that describe a design occurrence of a lateral.

In order to describe a Lateral_functional, certain properties must be captured.

npd:Lateral_functional

The Lateral_functional is a planned type of Lateral, as instanced in a design.

None

<xtc:Entity name="npd:Lateral_functional"> <xtc:Definition> The Lateral_functional is a planned type of Lateral, as instanced in a design.

2-13

</xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Olet_functional

To collect properties that describe a design occurrence of an olet.

In order to describe an Olet_functional, certain properties must be captured.

npd:Olet_functional

The Olet_functional is a planned type of Olet, as instanced in a design.

None

<xtc:Entity name="npd:Olet_functional"> <xtc:Definition> The Olet_functional is a planned type of Olet, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Entity: Boss_functional

To collect properties that describe a design occurrence of a boss.

2-14

Motivation:

Entity Name:


XML:

In order to describe a Boss_functional, certain properties must be captured.

npd:Boss_functional

The Boss_functional is a planned type of Boss, as instanced in a design.

None

<xtc:Entity name="npd:Boss_functional"> <xtc:Definition> The Boss_functional is a planned type of Boss, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Olet_functional"> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Entity: Y_type_lateral_functional

To collect properties that describe a design occurrence of a Y_type_lateral.

In order to describe a Y_type_lateral_functional, certain properties must be captured.

npd:Y_type_lateral_functional

The Y_type_lateral_functional is a planned type of Y_type_lateral, as instanced in a design.

2-15

Properties:

XML:

None

<xtc:Entity name="npd:Y_type_lateral_functional"> <xtc:Definition> The Y_type_lateral_functional is a planned type of Y_type_lateral, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity:Lap_joint_stub_end_functional

To collect properties that describe a design occurrence of a Lap_joint_stub_end.

In order to describe a Lap_joint_stub_end_functional, certain properties must be captured.

npd:Lap_joint_stub_end_functional

The Lap_joint_stub_end_functional is a planned type of Lap_joint_stub_end, as instanced in a design.

None

<xtc:Entity name="npd:Lap_joint_stub_end_functional"> <xtc:Definition> The Lap_joint_stub_end_functional is a planned type of Lap_joint_stub_end, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref>

2-16

</xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Bushing_functional

To collect properties that describe a design occurrence of a bushing.

In order to describe a Bushing_functional, certain properties must be captured.

npd:Bushing_functional

The Bushing_functional is a planned type of Bushing, as instanced in a design.

None

<xtc:Entity name="npd:Bushing_functional"> <xtc:Definition> The Bushing_functional is a planned type of Bushing, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:

Entity: Reducer_functional

To collect properties that describe a design occurrence of a reducer.

In order to describe a Reducer_functional, certain properties must be captured.

2-17


XML:

npd:Reducer_functional

The Reducer_functional is a planned type of Reducer, as instanced in a design.

None

<xtc:Entity name="npd:Reducer_functional"> <xtc:Definition> The Reducer_functional is a planned type of Reducer, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Entity: Ferrule_functional

To collect properties that describe a design occurrence of a Ferrule.

In order to describe a Ferrule_functional, certain properties must be captured.

npd:Ferrule_functional

The Ferrule_functional is a planned type of Ferrule, as instanced in a design.

None

2-18

XML:

<xtc:Entity name="npd:Ferrule_functional"> <xtc:Definition> The Ferrule_functional is a planned type of Ferrule, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Eccentric_reducer_functional

To collect properties that describe a design occurrence of a Eccentric_reducer.

In order to describe a Eccentric_reducer_functional, certain properties must be captured.

npd:Eccentric_reducer_functional

The Eccentric_reducer_functional is a planned type of Eccentric_reducer, as instanced in a design.

None

<xtc:Entity name="npd:Eccentric_reducer_functional"> <xtc:Definition> The Eccentric_reducer_functional is a planned type of Eccentric_reducer, as instanced in a design. </xtc:Definition> <xtc:Properties/> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Entity: Pipe_closure_functional

2-19

Intent:

Motivation:

Entity Name:


XML:

To collect properties that describe a design occurrence of a Pipe_closure.

In order to describe a Pipe_closure_functional, certain properties must be captured.

npd:Pipe_closure_functional

The Pipe_closure_functional is a planned type of Pipe_closure, as instanced in a design.

None

<xtc:Entity name="npd:Pipe_closure_functional"> <xtc:Definition> The Pipe_closure_functional is a planned type of Pipe_closure, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Entity:Cap_functional

To collect properties that describe a design occurrence of a Cap.

In order to describe a Cap_functional, certain properties must be captured.

npd:Cap_functional

2-20

Properties:

XML:

The Cap_functional is a planned type of Cap, as instanced in a design.

None

<xtc:Entity name="npd:Cap_functional"> <xtc:Definition> The Cap_functional is a planned type of Cap, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Pipe_closure_functional"> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Plug_functional

To collect properties that describe a design occurrence of a Plug.

In order to describe a Plug_functional, certain properties must be captured.

npd:Plug_functional

The Plug_functional is a planned type of Plug, as instanced in a design.

None

<xtc:Entity name="npd:Plug_functional"> <xtc:Definition> The Plug_functional is a planned type of Plug, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Pipe_closure_functional">

2-21

<xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Perforated_cap_functional

To collect properties that describe a design occurrence of a Perforated_cap.

In order to describe a Perforated_cap_functional, certain properties must be captured.

npd:Perforated_cap_functional

The Perforated_cap_functional is a planned type of Perforated_cap, as instanced in a design.

None

<xtc:Entity name="npd:Perforated_cap_functional"> <xtc:Definition> The Perforated_cap_functional is a planned type of Perforated_cap, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Cap_functional"> <xtc:Entity_ref eref="npd:Pipe_closure_functional"> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Entity: Plate_functional

2-22

Intent:

Motivation:

Entity Name:


XML:

To collect properties that describe a design occurrence of a Plate.

In order to describe a Plate_functional, certain properties must be captured.

npd:Plate_functional

The Plate_functional is a planned type of Plate, as instanced in a design.

None

<xtc:Entity name="npd:Pipe_closure_plate_functional"> <xtc:Definition> The Plate_functional is a planned type of Plate, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Pipe_closure_functional"> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Entity: Perforated_plate_functional

To collect properties that describe a design occurrence of a Perforated_plate.

In order to describe a Perforated_plate_functional, certain properties must be captured.

npd:Perforated_plate_functional

2-23

Properties:

XML:

The Perforated_plate_functional is a planned type of Perforated_plate, as instanced in a design.

None

<xtc:Entity name="npd:Perforated_plate_functional"> <xtc:Definition> The Perforated_plate_functional is a planned type of Perforated_plate, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Plate_functional"> <xtc:Entity_ref eref="npd:Pipe_closure_functional"> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Flange_functional

To collect properties that describe a design occurrence of a Flange.

In order to describe a Flange_functional , certain properties must be captured.

npd:Flange_functional

The Flange_functional is a planned type of Flange, as instanced in a design.

None

<xtc:Entity name="npd:Flange_functional"> <xtc:Definition> The Flange_functional is a planned type of Flange, as instanced in a design. </xtc:Definition>

2-24

<xtc:supertype_map> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Slip_on_jacket_flange_functional

To collect properties that describe a design occurrence of a Slip_on_jacket_flange.

In order to describe a Slip_on_jacket_flange_functional , certain properties must be captured.

npd:Slip_on_jacket_flange_functional

The Slip_on_jacket_flange_functional is a planned type of Slip_on_jacket_flange, as instanced in a design.

None

<xtc:Entity name="npd:Slip_on_jacket_flange_functional"> <xtc:Definition> The Slip_on_jacket_flange_functional is a planned type of Slip_on_jacket_flange, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Flange_functional"> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Entity: Weld_neck_jacket_flange_functional

2-25

Motivation:

Entity Name:


XML:

To collect properties that describe a design occurrence of a Weld_neck_jacket_flange.

In order to describe a Weld_neck_jacket_flange_functional , certain properties must be captured.

npd:Weld_neck_jacket_flange_functional

The Weld_neck_jacket_flange_functional is a planned type of Weld_neck_jacket_flange, as instanced in a design.

None

<xtc:Entity name="npd:Weld_neck_jacket_flange_functional"> <xtc:Definition> The Weld_neck_jacket_flange_functional is a planned type of Weld_neck_jacket_flange, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Flange_functional"> <xtc:Entity_ref eref="npd:Fitting_functional"> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Structure:

Piping SystemsA Piping System is a type of ship system that performs a transport function, and that is composed primarily of pipes, pipe fittings, and valves subject to the same set or sets of design conditions. A Piping System is a system of interconnected objects that convey fluid, vapor, or particulate flow throughout a ship.

The functional description of a Piping System is provided under the entities for Piping_system_line and Piping_system_line _segment.

A Piping_system_line is a logical component of a Piping System and is composed of a collection of interconnected Piping_system_line_segment objects. The information contained within these entities and their attributes describes the functional links and properties of a flow stream in a Piping System. It includes information about the segments in the line and the specifications for these segments, such as design criteria, service conditions, and line identifier.

2-26

Piping System model

Intent:

Motivation:

Entity Name:


Entity: Piping_system_functional

To collect properties that describe a piping system, which is a type of ship system composed of piping components.

In order to describe a Piping_system_functional , certain properties must be captured.

npd:Piping_system_functional

An Piping_system_functional is a type of Ship_system that is a system of piping_system_component_functionals.

2-27

XML:

Name Key Description

Code No The code specifies the name of the specification to which the Piping_system needs to conform.

<xtc:Entity name="npd:Piping_system_functional"/> <xtc:Definition> An Piping_system_functional is a type of Ship_system that is a system of piping_system_component_functionals.. </xtc:Definition> <xtc:Properties> <xtc:Property name="Code" datatype="xs:anyURI"/> <xtc:Definition> The code specifies the name of the specification to which the Piping_system needs to conform. </xtc:Definition> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Ship_system"/> <xtc:Entity_ref eref="npd:Configuration_item"/> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Structure:

InsulationAn Insulation is a type of item that is a material or assembly of materials used to provide resistance to heat flow, electricity, sound, or mechanical vibration. An Insulation_part refers to the catalogue item of Insulation in a parts library, whereas an Insulation_instance is a functional type of Insulation, as instanced in a design.

2-28

Insulation model

Intent:

Motivation:

Entity Name:


XML:

Entity: Insulation_part

To collect properties that describe an insulation part.

In order to describe an insulation part, properties peculiar to that part must be captured.

npd:Insulation_part

Insulation_part refers to the catalogue item of Insulation in a parts library.

None

<xtc:Entity name="npd:Insulation_part"> <xtc:Definition> The Insulation_part refers to the catalogue item of Insulation in a parts library. </xtc:Definition>

2-29

<xtc:Properties/> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Generic_part"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Insulation_functional

To collect properties that describe a design occurrence of an insulation.

In order to describe an Insulation_functional , certain properties must be captured.

npd:Insulation_functional

The Insulation_instance is a functional type of Insulation, as instanced in a design.

None

<xtc:Entity name="npd:Insulation_functional"> <xtc:Definition> The Insulation_instance is a functional type of Insulation, as instanced in a design. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Instrumentation & ControlAn Instrumentation and Control System is a type of ship system that is a system of wiring, switches, controls, and other equipment associated with monitoring and controlling the performance characteristics of ship system objects. An Instrumentation and Control Component is a type of item that is an individually identifiable item or combination of items that is part of the functional Instrumentation and Control System. Each Instrumentation_and_control_component may be an Instrument.

An Instrument is a type of Instrumentation_and_control_component that monitors one or more performance

2-30

Structure:

characteristics of a system. Examples of Instrumentation_and_control_component objects include wiring, switches, control valves, and gauges.

The Instrument_functional is a functional type of Instrument, as instanced in a design.

Instrumentation & Control model

Intent:

Motivation:

Entity: Instrumentation_and_control_component

To collect properties that describe the instrument and control component type of design occurrence in an Instrumentation_and_control_system.

In order to describe an Instrumentation_and_control_component, certain properties must be captured, such as whether the item is an Instrument.

2-31

Entity Name:


Properties:

XML:

npd:Instrumentation_and_control_component

An Instrumentation_and_control_component is a type of Design_occurrence that is an individually identifiable item or combination of items that is part of the functional Instrumentation_and_control_system. Each Instrumentation_and_control_component may be an Instrument.

None

<xtc:Entity name="npd:Instrumentation_and_control_component_functional"> <xtc:Definition> An Instrumentation_and_control_component is a type of Design_occurrence that is an individually identifiable item or combination of items that is part of the functional Instrumentation_and_control_system. Each Instrumentation_and_control_component may be an Instrument. </xtc:Definition> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Entity: Instrument_functional

To collect properties that describe a design occurrence of an instrument.

In order to describe an Instrument_functional, certain properties must be captured, such as the control loop key.

npd:Instrument_functional



2-32

XML:

Control_loop_id Yes A control_loop_id specifies a unique identfier for a control module that is implemented by an Instrument.

<xtc:Entity name="npd:Instrument_functional"> <xtc:Definition> The Instrument_functional is a functional type of Instrument, as instanced in a design. </xtc:Definition> <xtc:Properties> <xtc:Property use="required" name="npd:Control_loop_id" datatype="xs:normalizedString" key="true"/> <xtc:Definition> A control_loop_id specifies a unique identfier for a control module that is implemented by an Instrument. </xtc:Definition> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Inline_instrument_functional

To collect properties that describe a design occurrence of an inline instrument.

In order to describe an Inline_instrument_functional, certain properties must be captured.

npd:Inline_instrument_functional

The Inline_instrument_functional is a functional type of Inline_instrument, as instanced in a design.

None

<xtc:Entity name="npd:Inline_instrument_functional"> <xtc:Definition> The Inline_instrument_functional is a functional type of Inline_instrument, as instanced in a design. </xtc:Definition> <xtc:Properties/> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Instrument_functional">

2-33

<xtc:Entity_ref eref="npd:Instrumentation_and_control_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> <xtc:Entity_ref eref="npd:Piping_system_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Offline_instrument_functional

To collect properties that describe a design occurrence of an offline instrument.

In order to describe an Offline_instrument_functional, certain properties must be captured.

npd:Offline_instrument_functional

The Offline_instrument_functional is a functional type of Offline_instrument, as instanced in a design.

None

<xtc:Entity name="npd:Offline_instrument_functional"> <xtc:Definition> The Offline_instrument_functional is a functional type of Offline_instrument, as instanced in a design. </xtc:Definition> <xtc:Properties/> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Instrument_functional"> <xtc:Entity_ref eref="npd:Instrumentation_and_control_component_functional"> <xtc:Entity_ref eref="npd:Design_occurrence"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

2-34

Structure:

Connectors & ConnectionsA key feature of piping and all distribution products is the connectivity of components of the product to form networks. In general, connectivity between piping objects is established by defining a relationship between the distribution ends of connecting objects and a distribution interface. A connection is an association between two items that enables the flow of process material, energy, mechanical loads, or signals between them or constrains their relative positions. Within the scope of the SCIM, a connection can be between either functional or physical plant items. A connection can be the result of a physical joining, or a functional connection can exist between two plant items without a physical joining of the plant items.

A connector is a physical or functional property of a plant item that links it to another plant item, or to a compatible connector on another plant item. This linkage enables the flow of energy, mechanical loads, process material, or signals through the connected plant items

A Functional_connector is a type of Plant_item_connector_occurrence that represents the functional or logical aspect of the Plant_item_connector_occurrence. Each Functional_connector is either: a Line_piping_branch_connector, or a Line_-piping_connector. The distinction is that a “Line_piping_connector” participates in a connection between the logical terminations of two or more “Piping_system_line_segments”, whereas a “Line_piping_branch_connector” participates in a connection between the logical termination of one “Piping_system_line_segment” and a point on another “Piping_system_line_segment” other than a termination. The former “Piping_system_line_segment” branches from the latter “Piping_system_line_segment”.

Connectors & Connections model

Intent:

Entity: Piping_connection_functional

2-35

Motivation:

Entity Name:


XML:

To collect properties that describe a design occurrence of a Piping_connection.

In order to describe an Piping_connection_functional, certain properties must be captured, such as the connection type.

npd:Piping_connection_functional

A Piping_connection is a joint that involves a physical linkage between two or more Piping_physical_connector objects.


Owner Yes Designates the organization and repository that owns the information item. The value should be a URI that uniquely names the repository as well as the organization that owns the repository in which the information item is managed.

Id Yes Designates the primary identifier of the informatin item. The information item is uniquely identified by the concatenation of all its properties.

Version Yes Designates the version of the information item.

Connection_type No Designates the type of connector.

<xtc:Entity name="npd:Piping_connection_functional"> <xtc:Definition> A Piping_connection is a joint that involves a physical linkage between two or more Piping_physical_connector objects. </xtc:Definition> <xtc:Properties> <xtc:Property datatype="xs:anyURI" name="Owner" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Id" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Version" key="true"/> <xtc:Property name="Connection_type" datatype="npd:Piping_connection_type"/> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="ex:Entity"/> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity: Piping_functional_connector

To collect properties that describe a functional or logical aspect of the piping physical connector.

2-36

Entity Name:


Properties:

XML:

In order to describe an Piping_functional_connector, certain properties must be captured.

npd:Piping_functional_connector

A Piping_functional_connector is a type of piping connector that represents the functional or logical aspect of the Piping_physical_connector. Each Functional_connector is either: a Line_piping_branch_connector or a Line_piping_connector.

None

<xtc:Entity name="npd:Piping_functional_connector"> <xtc:Definition> A Piping_functional_connector is a type of piping connectore that represents the functional or logical aspect of the Piping_physical_connector. Each Functional_connector is either: a Line_piping_branch_connector or a Line_piping_connector. </xtc:Definition> <xtc:Properties/> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Piping_connector"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Entity: Line_piping_branch_connector

To collect properties that describe a functional or logical aspect of the piping branch connector.

In order to describe the type of piping functional connector that is used in a line piping branch connection.

npd:Line_piping_branch_connector

A Line_piping_branch_connector is a type of Piping_functional_connector that participates in a Line_piping_branch_connection.

None

2-37

XML:

<xtc:Entity name="npd:Line_piping_branch_connector"> <xtc:Definition> A Line_piping_branch_connector is a type of Piping_functional_connector that participates in a Line_piping_branch_connection. </xtc:Definition> <xtc:Properties/> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Piping_functional_connector"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Structure:

Piping LinesA Piping Line is a logical component of a Piping System, and is composed of a collection of interconnected line segments. Piping Lines generally correspond to defined sections of Piping and Instrumentation Diagrams (P&ID) which are used to specify the functional piping arrangement. A P&ID is a design that represents the logical functionality of a Piping System, as opposed to a three-dimensional geometric model which is a design that represents the physical shape and arrangement of the components of the Piping System. In the Piping Functional chapter of the SCIM, the entities used to describe this relationship are the Piping_system_line and Piping_system_line_segment, where the first is composed of a collection of interconnected objects of the second type. A Piping_system_line_segment terminates at one of the following:

l Piping_connector_functional l Tap into a Piping_system_line l Point where the stream diverges or converges l Vent l Drain

2-38

Piping Line model

Intent:

Motivation:

Entity Name:


Properties:

Entity: Piping_system_line_segment

To collect properties that describe an element of a piping system line that terminates at a piping connector funcctional.

In order to describe the Piping_system_line_segment, various properties must be collected, such as data regarding line, corrosion, temperature, pressure and elevation.

npd:Piping_system_line_segment

A Piping_system_line_segment is an element of a Piping_system_line. A Piping_system_line_segment terminates at a Piping_connector_functional, a tap into a Piping_system_line, a point where the stream diverges or converges, a vent, or a drain.

2-39

XML:





heat_tracing_type No The heat_tracing_type specifies the heating method used to maintain temperature in the Piping_system_line.

Line_size No The line_size specifies the intended diameter of the piping to be selected to satisfy the Piping_system_line. The line_size need not be specified for a particular Piping_system_line_segment where the Piping_system_line_segment corresponds to one Piping_system_component.

Line_size_unit No The line_size_unit specifies the unit of measurement used to measure the line_size.

Corrosion_allowance No The corrosion_allowance specifies the depth that corrosion may encroach below the surface of components on a Piping_system_line_segment before action is required. For a given Piping_system_component, the value of this attribute overrides any global specification.

Corrosion_allowance_unit No The corrosion_allowance_unit specifies the unit of measurement used to measure the corrosion_allowance.

Design_temperature No The design_temperature specifies the requirement for maximum allowable temperature of the Piping_component objects associated with the Piping_system_line.

Min_design_temperature No The min_design_temperature specifies the minimum design_temperature.

Max_design_temperature No The max_design_temperature specifies the maximum design_temperature.

Design_temperature_unit No The design_temperature_unit spcifies the unit of measuremnt used to measure the design_temperature.

Elevation No The elevation specifies the distance above sea level that the piping assigned to the line should exist.

Design_pressure No The design_pressure specifies the requirement for maximum allowable pressure of the Piping_component objects associated with the Piping_system_line.

Min_design_pressure No The min_design_pressure specifies the minimum design_pressure.

Max_design_pressure No The max_design_pressure specifies the maximum design_pressure.

Design_pressure_unit No The design_pressure_unit specifies the unit of measurement used to measure the design_pressure.

<xtc:Entity name="npd:Piping_system_line_segment"> <xtc:Definition> A Piping_system_line_segment is an element of a Piping_system_line. A Piping_system_line_segment terminates at a Piping_connector_functional, a tap into a Piping_system_line, a point where the stream diverges or converges, a vent, or a drain.

2-40

</xtc:Definition> <xtc:Properties> <xtc:Property datatype="xs:anyURI" name="Owner" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Id" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Version" key="true"/> <xtc:Property name="npd:heat_tracing_type" datatype="xs:normalizedString"/> <xtc:Definition> The heat_tracing_type specifies the heating method used to maintain temperature in the Piping_system_line. </xtc:Definition> <xtc:Property name="npd:Line_size" datatype="measure_schema:positive_length_measure"/> <xtc:Definition> The line_size specifies the intended diameter of the piping to be selected to satisfy the Piping_system_line. The line_size need not be specified for a particular Piping_system_line_segment where the Piping_system_line_segment corresponds to one Piping_system_component. </xtc:Definition> <xtc:Property name="npd:Line_size_unit" use="optional" datatype="measure_schema:si_unit_name"/> <xtc:Definition> The line_size_unit specifies the unit of measurement used to measure the line_size. </xtc:Definition> <xtc:Property name="npd:Corrosion_allowance" datatype="measure_schema:positive_length_measure"/> <xtc:Definition> The corrosion_allowance specifies the depth that corrosion may encroach below the surface of components on a Piping_system_line_segment before action is required. For a given Piping_system_component, the value of this attribute overrides any global specification. </xtc:Definition> <xtc:Property name="npd:Corrosion_allowance_unit" use="optional" datatype="measure_schema:si_unit_name"/> <xtc:Definition> The corrosion_allowance_unit specifies the unit of measurement used to measure the corrosion_allowance. </xtc:Definition> <xtc:Property name="npd:Design_temperature" datatype="measure_schema:thermodynamic_temperature_measure"/> <xtc:Definition> The design_temperature specifies the requirement for maximum allowable temperature of the Piping_component objects associated with the Piping_system_line. </xtc:Definition> <xtc:Property name="npd:Min_design_temperature" use="optional" datatype="measure_schema:thermodynamic_temperature_measure"/> <xtc:Definition> The min_design_temperature specifies the minimum design_temperature. </xtc:Definition> <xtc:Property name="npd:Max_design_temperature" use="optional" datatype="measure_schema:thermodynamic_temperature_measure"/> <xtc:Definition> The max_design_temperature specifies the maximum design_temperature. </xtc:Definition> <xtc:Property name="npd:Design_temperature_unit" use="optional" datatype="measure_schema:si_unit_name"/> <xtc:Definition> The design_temperature_unit spcifies the unit of measuremnt used to measure the design_temperature. </xtc:Definition> <xtc:Property name="npd:Elevation" datatype="xs:double"/> <xtc:Definition> The elevation specifies the distance above sea level that the piping assigned to the line should exist. </xtc:Definition> <xtc:Property name="npd:Design_pressure" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The design_pressure specifies the requirement for maximum allowable pressure of the Piping_component objects associated with the Piping_system_line. </xtc:Definition> <xtc:Property name="npd:Min_design_pressure" use="optional" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The min_design_pressure specifies the minimum design_pressure. </xtc:Definition> <xtc:Property name="npd:Max_design_pressure" use="optional" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The max_design_pressure specifies the maximum design_pressure. </xtc:Definition> <xtc:Property name="npd:Design_pressure_unit" use="optional" datatype="measure_schema:si_unit_name"/> <xtc:Definition> The design_pressure_unit specifies the unit of measurement used to measure the design_pressure. </xtc:Definition> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="ex:Entity"/> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity: Piping_system_line_segment

To collect properties that describe a logical end point of a piping system line segment.

In order to describe the logical end point, certain properties must be captured, such as the type of termination.

2-41

Entity Name:


Properties:

XML:

npd:Piping_system_line_segment_termination

A Piping_system_line_segment_termination is one of two logical end-points of a Piping_system_line_segment. Each Piping_system_line_segment_termination is either: a Line_branch_termination, a Line_to_line_termination, a Line_piping_termination, or Piping_system_line_termination.





Flow_direction No The flow_direction specifies the direction of material flow at the Piping_system_line_segment_termination.

<xtc:Entity name="npd:Piping_system_line_segment_termination" abstract="true"> <xtc:Definition> A Piping_system_line_segment_termination is one of two logical end-points of a Piping_system_line_segment. Each Piping_system_line_segment_termination is either: a Line_branch_termination, a Line_to_line_termination, a Line_piping_termination, or Piping_system_line_termination. </xtc:Definition> <xtc:Properties> <xtc:Property datatype="xs:anyURI" name="Owner" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Id" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Version" key="true"/> <xtc:Property name="npd:flow_direction" datatype="npd:flow_direction_with_none_enum"/> <xtc:Definition> The flow_direction specifies the direction of material flow at the Piping_system_line_segment_termination. </xtc:Definition> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="ex:Entity"/> </xtc:supertype_map> </xtc:Entity>

Intent:

Entity: Line_piping_termination

To collect properties that describe a type of piping system line segment termination that connects to other line to line terminations.

2-42

Motivation:

Entity Name:


XML:

In order to describe the Line_piping_termination, certain data must be captured.

npd:Line_piping_termination

A Line_piping_termination is a type of Piping_system_line_segment_termination that connects to other Line_to_line_termination.

None

<xtc:Entity name="npd:Line_piping_termination"> <xtc:Definition> A Line_piping_termination is a type of Piping_system_line_segment_termination that connects to other Line_to_line_termination. </xtc:Definition> <xtc:Properties/> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Piping_system_line_segment_termination"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Properties:

Entity: Line_piping_branch_connection

To collect properties that describe a connection between a line piping branch connector and a point on a piping system line segment (other than a termination).

In order to describe the Line_piping_branch_connection, certain data must be captured, such as the branch sequence id key.

npd:Line_piping_branch_connection

A Line_piping_branch_connection is a connection between a Line_piping_branch_connector and a point on a Piping_system_line_segment other than a termination. The Line_piping_branch_connector branches from the Piping_system_line_segment.

2-43

XML:


Branch_sequence_id Yes The branch_sequence_id specifies an alphanumeric identifier that indicates the order that branches extend from the main Piping_system_line_segment.

<xtc:Entity name="npd:Line_piping_branch_connection"> <xtc:Definition> A Line_piping_branch_connection is a connection between a Line_piping_branch_connector and a point on a Piping_system_line_segment other than a termination. The Line_piping_branch_connector branches from the Piping_system_line_segment. </xtc:Definition> <xtc:Properties> <xtc:Property name="npd:Branch_sequence_id" datatype="xs:normalizedString" key="true"/> <xtc:Definition> The branch_sequence_id specifies an alphanumeric identifier that indicates the order that branches extend from the main Piping_system_line_segment </xtc:Definition> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Piping_connection_functional"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Properties:

Entity: Line_piping_connection

To collect properties that describe a connection between a logical termination of a piping system line segment and a line piping connector.

In order to describe the Line_piping_connection, certain data must be captured, such as the key information.

npd:Line_piping_connection

A Line_piping_connection is a connection between the logical termination of a Piping_system_line_segment and a Line_piping_connector.

2-44

XML:





<xtc:Entity name="npd:Line_piping_connection"> <xtc:Definition> A Line_piping_connection is a connection between the logical termination of a Piping_system_line_segment and a Line_piping_connector. </xtc:Definition> <xtc:Properties> <xtc:Property datatype="xs:anyURI" name="Owner" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Id" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Version" key="true"/> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="ex:Entity"/> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Line_piping_connector

To collect properties that describe a type of piping functional connector that is used in a line piping connector.

In order to describe the Line_piping_connector , certain data must be captured.

npd:Line_piping_connector

A Line_piping_connector is a type of Piping_functional_connector that participates in a Line_piping_connection.

None

<xtc:Entity name="npd:Line_piping_connector"> <xtc:Definition> A Line_piping_connector is a type of Piping_functional_connector that participates in a

2-45

Line_piping_connection. </xtc:Definition> <xtc:Properties/> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Piping_functional_connector"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


XML:

Entity: Line_to_line_connection

To collect properties that describe the connection between two or more piping system line segment logical terminations.

In order to describe the Line_to_line_connection , certain data must be captured, such as the key.

npd:Line_to_line_connection

A Line_to_line_connection is a connection between the logical terminations of two or more Piping_system_line_segment.





<xtc:Entity name="npd:Line_to_line_connection"> <xtc:Definition> A Line_to_line_connection is a connection between the logical terminations of two or more Piping_system_line_segment. </xtc:Definition> <xtc:Properties> <xtc:Property datatype="xs:anyURI" name="Owner" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Id" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Version" key="true"/> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="ex:Entity"/> </xtc:supertype_map> </xtc:Entity>

2-46

Intent:

Motivation:

Entity Name:


Properties:

XML:

Entity: Line_to_line_termination

To collect properties that describe a type of piping system line segment termination that connects to other line to line termination objects.

In order to describe the Line_to_line_termination, certain data must be captured.

npd:Line_to_line_termination

A Line_to_line_termination is a type of Piping_system_line_segment_termination that connects to other Line_to_line_termination objects.

None

<xtc:Entity name="npd:Line_to_line_termination"> <xtc:Definition> A Line_to_line_termination is a type of Piping_system_line_segment_termination that connects to other Line_to_line_termination objects. </xtc:Definition> <xtc:Properties/> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Line_piping_termination"> <xtc:Entity_ref eref="npd:Piping_system_line_segment_termination"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:

Entity: Line_branch_termination

To collect properties that describe a type of piping system line segment termination that connects to a piping system line segment at a point other than termination.

In order to describe the Line_branch_termination , certain data must be captured.

2-47


Properties:

XML:

npd:Line_branch_termination

A Line_branch_termination is a type of Piping_system_line_segment_termination that connects to a Piping_system_line_segment at a point other than a termination.

None

<xtc:Entity name="npd:Line_branch_termination"> <xtc:Definition> A Line_branch_termination is a type of Piping_system_line_segment_termination that connects to a Piping_system_line_segment at a point other than a termination. </xtc:Definition> <xtc:Properties/> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Piping_system_line_segment_termination"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Properties:

Entity: Line_branch_connection

To collect properties that describe a connection between the logical termination of one piping system line segment and a point on another (other than a termination).

In order to describe the Line_branch_connection, certain data must be captured, such as they key information.

npd:Line_branch_connection

A Line_branch_connection is a connection between the logical termination of one Piping_system_line_segment and a point on another Piping_system_line_segment other than a termination. The former Piping_system_line_segment branches from the latter Piping_system_line_segment.


2-48

XML:




<xtc:Entity name="npd:Line_branch_connection"> <xtc:Definition> A Line_branch_connection is a connection between the logical termination of onePiping_system_line_segment and a point on another Piping_system_line_segment other than a termination. The former Piping_system_line_segment branches from the latter Piping_system_line_segment. </xtc:Definition> <xtc:Properties> <xtc:Property datatype="xs:anyURI" name="Owner" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Id" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Version" key="true"/> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="ex:Entity"/> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Entity: Piping_system_line_termination

To collect properties that describe a type of termination on a piping system line segment that begins/ends a piping system line.

In order to describe a Piping_system_line_termination, certain properties must be captured, such as the position and start/end values.

npd:Piping_system_line_termination

A Piping_system_line_termination is a type of Piping_system_line_segment_termination that begins or ends a Piping_system_line.


Position_on_pipe No The position_on_pipe specifies an indicator of the relationship between the point and the Piping_component that will eventually satisfy it.

Start_or_end No The start_or_end specifies an enumerated value that defines the side of the pipe on which the line termination lies. A value of 'start' indicates the line

2-49

XML:

termination is on the upstream end, and a value of 'end' indicates that the line termination is on the downstream end.

<xtc:Entity name="npd:Piping_system_line_termination"> <xtc:Definition> A Piping_system_line_termination is a type of Piping_system_line_segment_termination that begins or ends a Piping_system_line. </xtc:Definition> <xtc:Properties> <xtc:Property name="npd:Position_on_pipe" datatype="xs:normalizedString"/> <xtc:Definition> The position_on_pipe specifies an indicator of the relationship between the point and the Piping_component that will eventually satisfy it. </xtc:Definition> <xtc:Property name="npd:Start_or_end" datatype="npd:Start_or_end"/> <xtc:Definition> The start_or_end specifies an enumerated value that defines the side of the pipe on which the line termination lies. A value of 'start' indicates the line termination is on the upstream end, and a value of 'end' indicates that the line termination is on the downstream end. </xtc:Definition> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="npd:Piping_system_line_segment_termination"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Properties:

Entity: Piping_system_line

To collect properties that describe a logical component of a piping system that is composed of piping system line segment objects.

In order to describe a Piping_system_line, certain properties must be captured, such as the key information.

npd:Piping_system_line

A Piping_system_line is a logical component of a Piping_system and is composed of a collection of interconnected Piping_system_line_segment objects.



2-50

XML:



<xtc:Entity name="npd:Piping_system_line"> <xtc:Definition> A Piping_system_line is a logical component of a Piping_system and is composed of a collection of interconnected Piping_system_line_segment objects. </xtc:Definition> <xtc:Properties> <xtc:Property datatype="xs:anyURI" name="Owner" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Id" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Version" key="true"/> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="edo:Edo"> <xtc:Entity_ref eref="ex:Entity"/> </xtc:Entity_ref> </xtc:supertype_map> </xtc:Entity>

Structure:

Piping Functional PropertiesThe Piping Functional characterization is used to describe the functional connectivity of a Piping System and the functional connectivity among the objects in that system. It provides the information that describes the functional links and properties of a flow stream in a Piping System. It includes information about the segments in the line and the specifications for these segments, such as design criteria, service conditions, and line identifier.

The functional requirements define the nomenclature, codes, and named values that describe or specify the performance or behavior to be met by items in a Piping System. For example, functional characteristics include flow rates, operating pressure, and maximum temperature.

Piping Functional Properties model

2-51

Intent:

Motivation:

Entity Name:


Properties:

XML:

Entity: Piping_specification

To collect properties that describe a specification of conditions that must be met in a piping system line segment.

In order to describe a Piping_specification, certain properties must be collected, such as the key, service description and owner.

npd:Piping_specification

A Piping_specification is a specification of conditions such as pressure, material, and corrosion allowance that must be met in a Piping_system_line_segment and may include a list of Piping_component objects by size range that meet these conditions.





Service_description No The service_description specifies a textual explanation or summary of the process stream conditions that are supported by the Plant_item objects described in the Piping_specification.

npd:Owner No The owner specifies the person or organization responsible for the specification.

<xtc:Entity name="npd:Piping_specification"> <xtc:Definition> A Piping_specification is a specification of conditions such as pressure, material, and corrosion allowance that must be met in a Piping_system_line_segment and may include a list of Piping_component objects by size range that meet these conditions. </xtc:Definition> <xtc:Properties> <xtc:Property datatype="xs:anyURI" name="Owner" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Id" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Version" key="true"/> <xtc:Property name="npd:Name" datatype="xs:normalizedString"/> <xtc:Definition> The name specifies a textual label given to the Piping_specification. </xtc:Definition> <xtc:Property name="npd:Service_description" datatype="xs:normalizedString"/> <xtc:Definition> The service_description specifies a textual explanation or summary of the process stream conditions that are supported by the Plant_item objects described in the Piping_specification. </xtc:Definition>

2-52

<xtc:Property name="npd:Owner" datatype="xs:anyURI"/> <xtc:Definition> The owner specifies the person or organization responsible for the specification. </xtc:Definition> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="ex:Entity"/> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Properties:

XML:

Entity: Family_definition

To collect properties that describe a plant item definition that defines piping component objects based upon their physical characteristics.

In order to describe a Family_definition , certain properties must be captured, such as the family classification description.

npd:Family_definition

A Family_definition is a Plant_item_definition that characterizes a set of Piping_component objects based on common physical characteristics. Physical characteristics may be specified as a specific value or as a range of values.


Family_classification_description No The family_classification_description specifies a textual explanation of the principal characteristics thatvary within the family.

<xtc:Entity name="npd:Family_definition"/> <xtc:Definition> A Family_definition is a Plant_item_definition that characterizes a set of Piping_component objects based on common physical characteristics. Physical characteristics may be specified as a specific value or as a range of values. </xtc:Definition> <xtc:Properties> <xtc:Property name="npd:Family_classification_description" datatype="xs:string"/> <xtc:Definition> The family_classification_description specifies a textual explanation of the principal characteristics thatvary within the family. </xtc:Definition> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="ex:Entity"/> </xtc:supertype_map>

2-53

</xtc:Entity>

Intent:

Motivation:

Entity Name:


Properties:

Entity: Stream_design_case

To collect properties that define characteristics of a gas, liquid , vapor or solid stream under a specific circumstance at the termination of a piping system line segment or plant item connector occurrence.

In order to describe a Stream_design_case, certain properties must be captured, such as the velocity, flow and pressure data.

npd:Stream_design_case

A Stream_design_case is the set of characteristics of a gas, liquid, vapor, or solid stream under a specific circumstance at the termination of a Piping_system_line_segment or a Plant_item_connector_occurrence.


Velocity No The velocity specifies the distance that the stream of gas, liquid, vapour, or solid stream moves per unit of time, usually in feet per minute or feet per second.

Min_velocity No The min_velocity specifies the minimum velocity.

Max_velocity No The max_velocity soecifies the maximum velocity.

Velocity_unit No The velocity_unit specifies the unit of measurement used to measure the velocity.

Stream_case_type No The stream_case_type specifies the condition that the stream characteristics are being defined under. Stream_case_type is required for each Stream_design_case.

Flow_rate No The flow_rate specifies the stream volume, mass, or molar units per unit time. It may be specified as a single value or as a range of values

Min_flow_rate No The min_flow_rate" specifies the minimum flow_rate.

Max_flow_rate No The max_flow_rate" specifies the maximum flow_rate.

Flow_rate_unit No The flow_rate_unit specifies the unit of measurement used to measure the flow_rate.

pressure No The pressure specifies the amount of force applied by the stream over a unit area. It may be specified as a single value or as a range of values.

Min_pressure No The min_pressure specifies the minimum pressure.

Max_pressure No The max_pressure specifies the maximum pressure.

2-54

XML:

Pressure_unit No The Pressure_unit specifies the unit of measurement used to measure the Pressure.

<xtc:Entity name="npd:Stream_design_case"> <xtc:Definition> A Stream_design_case is the set of characteristics of a gas, liquid, vapour, or solid stream under a specific circumstance at the termination of a Piping_system_line_segment or a Plant_item_connector_occurrence. </xtc:Definition> <xtc:Properties> <xtc:Property name="npd:Velocity" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The velocity specifies the distance that the stream of gas, liquid, vapour, or solid stream moves per unit of time, usually in feet per minute or feet per second. </xtc:Definition> <xtc:Property name="npd:Min_velocity" use="optional" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The min_velocity specifies the minimum velocity. </xtc:Definition> <xtc:Property name="npd:Max_velocity" use="optional" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The max_velocity soecifies the maximum velocity. </xtc:Definition> <xtc:Property name="npd:Velocity_unit" use="optional" datatype="measure_schema:si_unit_name"/> <xtc:Definition> The velocity_unit specifies the unit of measurement used to measure the velocity. </xtc:Definition> <xtc:Property use="required" name="npd:Stream_case_type" datatype="xs:normalizedString"/> <xtc:Definition> The stream_case_type specifies the condition that the stream characteristics are being defined under. Stream_case_type is required for each Stream_design_case. </xtc:Definition> <xtc:Property name="npd:Flow_rate" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The flow_rate specifies the stream volume, mass, or molar units per unit time. It may be specified as a single value or as a range of values. </xtc:Definition> <xtc:Property name="npd:Min_flow_rate" use="optional" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The min_flow_rate" specifies the minimum flow_rate. </xtc:Definition> <xtc:Property name="npd:Max_flow_rate" use="optional" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The max_flow_rate specifies the maximum flow_rate. </xtc:Definition> <xtc:Property name="npd:Flow_rate_unit" use="optional" datatype="measure_schema:si_unit_name"/> <xtc:Definition> The flow_rate_unit specifies the unit of measurement used to measure the flow_rate. </xtc:Definition> <xtc:Property name="npd:pressure" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The pressure specifies the amount of force applied by the stream over a unit area. It may be specified as a single value or as a range of values. </xtc:Definition> <xtc:Property name="npd:Min_pressure" use="optional" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The min_pressure specifies the minimum pressure. </xtc:Definition> <xtc:Property name="npd:Max_pressure" use="optional" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The max_pressure specifies the maximum pressure. </xtc:Definition> <xtc:Property name="npd:Pressure_unit" use="optional" datatype="measure_schema:si_unit_name"/> <xtc:Definition> </xtc:Definition> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="ex:Entity"/> </xtc:supertype_map> </xtc:Entity>

Intent:

Entity:Stream_phase

To collect properties that define the set of characteristics of a single gas, liquid, vapor or solid stream that may be composed into a stream design case.

2-55

Motivation:

Entity Name:


Properties:

In order to describe a Stream_phase, certain properties must be collected, such as the

npd:Stream_phase

A Stream_phase is the set of characteristics of a single gas, liquid, vapor, or solid stream that may be composed into a Stream_design_case.





Constituents No The constituents specifies the various chemicals for the Stream_phase.

Stream_case_type No The stream_case_type specifies the condition that the stream characteristics are being defined under. Stream_case_type is required for each Stream_design_case.

Phase_fraction No The phase_fraction specifies the percentage of the mass of this Stream_phase in the Stream_design_case.

Viscosity No The viscosity specifies a measure of the resistance of a stream to deformation when subjected to a shear stress.

Temperature No The temperature specifies the measure of molecular motion of a stream. It may be specified as a single value or as a range of values.

Min_temperature No The min_temperature specifies the minimum temperature.

Max_temperature No The max_temperature specifies the maximum temperature.

Constituent_mole_fraction No The constituent_mole_fraction specifies the mass ratio of any given component to the whole for the Stream_phase.

Constituent_mole_fraction_unit No The constituent_mole_fraction_unit specifies the unit of measurement used to measure the constituent_mole_fraction.

Phase_density No The phase_density specifies the amount of mass per unit volume for the Stream_phase.

Phase_density_unit No The phase_density_unit specifies the unit of measurement of the phase_density.

Specific_gravity No The specific_gravity specifies the ratio of the mass of a liquid to the mass of an equal volume of distilled water at 4 degrees Celsius.

Specific_gravity_unit No The specific_gravity_unit specifies the unit of measurement used to

2-56

XML:

measure the specific_gravity.

Surface_tension No The surface_tension specifies the force per unit area of the cohesive forces at or near the surface of a liquid Stream_phase.

Surface_tension_unit No The surface_tension_unit specifies the unit of measurement used to measure the surface_tension_unit.

<xtc:Entity name="npd:Stream_phase"> <xtc:Definition> A Stream_phase is the set of characteristics of a single gas, liquid, vapour, or solid stream that may be composed into a Stream_design_case. </xtc:Definition> <xtc:Properties> <xtc:Property datatype="xs:anyURI" name="Owner" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Id" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Version" key="true"/> <xtc:Property name="npd:Constituents" datatype="xs:normalizedString"/> <xtc:Definition> The constituents specifies the various chemicals for the Stream_phase. </xtc:Definition> <xtc:Property name="npd:Stream_case_type" datatype="xs:normalizedString"/> <xtc:Definition> The stream_case_type specifies the condition that the stream characteristics are being defined under. Stream_case_type is required for each Stream_design_case. </xtc:Definition> <xtc:Property name="npd:Phase_fraction" datatype="xs:double"/> <xtc:Definition> The phase_fraction specifies the percentage of the mass of this Stream_phase in the Stream_design_case. </xtc:Definition> <xtc:Property name="npd:Viscosity" datatype="xs:double"/> <xtc:Definition> The viscosity specifies a measure of the resistance of a stream to deformation when subjected to a shear stress. </xtc:Definition> <xtc:Property name="npd:Temperature" datatype="measure_schema:thermodynamic_temperature_measure"/> <xtc:Definition> The temperature specifies the measure of molecular motion of a stream. It may be specified as a single value or as a range of values. </xtc:Definition> <xtc:Property name="npd:Min_temperature" use="optional" datatype="measure_schema:thermodynamic_temperature_measure"/> <xtc:Definition> The min_temperature specifies the minimum temperature. </xtc:Definition> <xtc:Property name="npd:Max_temperature" use="optional" datatype="measure_schema:thermodynamic_temperature_measure"/> <xtc:Definition> The max_temperature specifies the maximum temperature. </xtc:Definition> <xtc:Property name="npd:Constituent_mole_fraction" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The constituent_mole_fraction specifies the mass ratio of any given component to the whole for the Stream_phase. </xtc:Definition> <xtc:Property name="npd:Constituent_mole_fraction_unit" use="optional" datatype="measure_schema:si_unit_name"/> <xtc:Definition> The constituent_mole_fraction_unit specifies the unit of measurement used to measure the constituent_mole_fraction. </xtc:Definition> <xtc:Property name="npd:Phase_density" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The phase_density specifies the amount of mass per unit volume for the Stream_phase. </xtc:Definition> <xtc:Property name="npd:Phase_density_unit" use="optional" datatype="measure_schema:si_unit_name"/> <xtc:Definition> The phase_density_unit specifies the unit of measurement of the phase_density. </xtc:Definition> <xtc:Property name="npd:Specific_gravity" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The specific_gravity specifies the ratio of the mass of a liquid to the mass of an equal volume of distilled water at 4 degrees Celsius. </xtc:Definition> <xtc:Property name="npd:Specific_gravity_unit" use="optional" datatype="measure_schema:si_unit_name"/> <xtc:Definition> The specific_gravity_unit specifies the unit of measurement used to measure the specific_gravity. </xtc:Definition> <xtc:Property name="npd:Surface_tension" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The surface_tension specifies the force per unit area of the cohesive forces at or near the surface of a liquid Stream_phase. </xtc:Definition> <xtc:Property name="npd:Surface_tension_unit" use="optional" datatype="measure_schema:si_unit_name"/> <xtc:Definition> The surface_tension_unit specifies the unit of measurement used to measure the surface_tension_unit. </xtc:Definition> </xtc:Properties>

2-57

<xtc:supertype_map> <xtc:Entity_ref eref="ex:Entity"/> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Entity: Service_operating_case

To collect properties to define a stream condition that ma exist at a plant item connector.

In order to describe a Service_operating_case, certain properties must be collected, such as the duration, operating pressure and frequency.

npd:Service_operating_case

A Service_operating_case is a stream condition that may exist at a Plant_item_connector.





Name No The name specifies a textual label given to the condition that the Equipment operating characteristics are being defined under.

Duration No The duration specifies the expected time span of the Service_operating_case. It may be specified as a single value or as a range of values.

Min_duration No The min_duration specifies the minimum duration.

Max_duration No The max_duration specifies the maximum duration.

Frequency No The frequency specifies the expected number of times that the Service_operating_case will occur over a defined period of time. It may be specified as a single value or as a range of values.

Min_frequency No The min_frequency specifies the minimum frequency.

Max_frequency No The max_frequency specifies the maximum frequency.

Operating_pressure No The name specifies a textual label given to the condition that the

2-58

XML:

Equipment operating characteristics are being defined under.

Min_operating_pressure No The min_operating_pressure specifies the minimum operating_pressure.

Max_operating_pressure No The max_operating_pressure specifies the maximum operating_pressure.

Frequency_unit No The frequency_unit specifies the unit of measurement used to measure the frequency.

Operating_temperature No The operating_temperature specifies the temperature of the process stream on the Plant_item under a specific Service_operating_case. It may be specified as a single value or as a range of values.

Min_operating_temperature No The min_operating_temperature specifies the minimum operating_temperature.

Max_operating_temperature No The max_operating_temperature specifies the maximum operating_temperature.

Temperature_unit No The temperature_unit specifies the unit of measurement used to measure the temperature.

<xtc:Entity name="npd:Service_operating_case"> <xtc:Definition> A Service_operating_case is a stream condition that may exist at a Plant_item_connector. </xtc:Definition> <xtc:Properties> <xtc:Property datatype="xs:anyURI" name="Owner" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Id" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Version" key="true"/> <xtc:Property name="npd:Name" datatype="xs:normalizedString"/> <xtc:Definition> The name specifies a textual label given to the condition that the Equipment operating characteristics are being defined under. </xtc:Definition> <xtc:Property name="npd:Duration" datatype="xs:duration"/> <xtc:Definition> The duration specifies the expected time span of the Service_operating_case. It may be specified as a single value or as a range of values. </xtc:Definition> <xtc:Property name="npd:Min_duration" use="optional" datatype="xs:duration"/> <xtc:Definition> The min_duration specifies the minimum duration. </xtc:Definition> <xtc:Property name="npd:Max_duration" use="optional" datatype="xs:duration"/> <xtc:Definition> The max_duration specifies the maximum duration. </xtc:Definition> <xtc:Property name="npd:Frequency" datatype="xs:nonNegativeInteger"/> <xtc:Definition> The frequency specifies the expected number of times that the Service_operating_case will occur over a defined period of time. It may be specified as a single value or as a range of values. </xtc:Definition> <xtc:Property name="npd:Min_frequency" use="optional" datatype="xs:nonNegativeInteger"/> <xtc:Definition> The min_frequency specifies the minimum frequency. </xtc:Definition> <xtc:Property name="npd:Max_frequency" use="optional" datatype="xs:nonNegativeInteger"/> <xtc:Definition> The max_frequency specifies the maximum frequency. </xtc:Definition> <xtc:Property name="npd:Operating_pressure" datatype="measure_schema:positive_length_measure"/> <xtc:Definition> The name specifies a textual label given to the condition that the Equipment operating characteristics are being defined under. </xtc:Definition> <xtc:Property name="npd:Min_operating_pressure" use="optional" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The min_operating_pressure specifies the minimum operating_pressure. </xtc:Definition> <xtc:Property name="npd:Max_operating_pressure" use="optional" datatype="measure_schema:ratio_measure"/> <xtc:Definition> The max_operating_pressure specifies the maximum operating_pressure. </xtc:Definition> <xtc:Property name="npd:Frequency_unit" datatype="measure_schema:si_unit_name"/> <xtc:Definition> The frequency_unit specifies the unit of measurement used to measure the frequency. </xtc:Definition> <xtc:Property name="npd:operating_temperature" datatype="measure_schema:thermodynamic_temperature_measure"/> <xtc:Definition> The operating_temperature specifies the temperature of the process stream on the Plant_item under a

2-59

specific Service_operating_case. It may be specified as a single value or as a range of values. </xtc:Definition> <xtc:Property name="npd:Min_operating_temperature" use="optional" datatype="measure_schema:thermodynamic_temperature_measure"/> <xtc:Definition> The min_operating_temperature specifies the minimum operating_temperature. </xtc:Definition> <xtc:Property name="npd:Max_operating_temperature" use="optional" datatype="measure_schema:thermodynamic_temperature_measure"/> <xtc:Definition> The max_operating_temperature specifies the maximum operating_temperature. </xtc:Definition> <xtc:Property name="npd:Temperature_unit" use="optional" datatype="measure_schema:si_unit_name"/> <xtc:Definition> The temperature_unit specifies the unit of measurement used to measure the temperature. </xtc:Definition> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="ex:Entity"/> </xtc:supertype_map> </xtc:Entity>

Intent:

Motivation:

Entity Name:


Entity: Piping_connector_service_characteristic

To collect properties that define the conditions that the piping connector is designed to withstand.

In order to describe a Piping_connector_service_characteristic, certain properties must be captured, such as the design pressure and design temperature.

npd:Piping_connector_service_characteristic

A Piping_connector_service_characteristic holds the conditions that the Piping_connector is designed to withstand.





Design_pressure No The design_pressure specifies the maximum allowable pressure at the Piping_connector. It may be specified as a single value or as a range of values.

Min_design_pressure No The min_design_pressure specifies the minimum design_pressure.

Max_design_pressure No The max_design_pressure specifies the maximum design_pressure.

2-60

Imported Entities:

XML:

Design_pressure_unit No The design_pressure_unit specifies the unit of measurement used to measure the design_pressure.

Design_temperature No The design_temperature specifies the maximum allowable temperature at the Piping_connector. It may be specified as a single value or as a range of values.

Min_design_temperature No The min_design_temperature specifies the minimum design_temperature.

Max_design_temperature No The max_design_temperature specifies the maximum design_temperature.

Design_temperature_unit No The design_pressure_unit specifies the unit of measurement used to measure the design_temperature.

<xtc:Entity name="npd:Piping_connector_service_characteristic"> <xtc:Definition> A Piping_connector_service_characteristic holds the conditions that the Piping_connector is designed to withstand. </xtc:Definition> <xtc:Properties> <xtc:Property datatype="xs:anyURI" name="Owner" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Id" key="true"/> <xtc:Property datatype="xs:normalizedString" name="Version" key="true"/> <xtc:Property name="npd:Design_pressure" datatype="measure_schema:positive_length_measure"/> <xtc:Definition> The design_pressure specifies the maximum allowable pressure at the Piping_connector. It may be specified as a single value or as a range of values. </xtc:Definition> <xtc:Property name="npd:Min_design_pressure" use="optional" datatype="measure_schema:positive_length_measure"/> <xtc:Definition> The min_design_pressure specifies the minimum design_pressure. </xtc:Definition> <xtc:Property name="npd:Max_design_pressure" use="optional" datatype="measure_schema:positive_length_measure"/> <xtc:Definition> The max_design_pressure specifies the maximum design_pressure. </xtc:Definition> <xtc:Property name="npd:Design_pressure_unit" use="optional" datatype="measure_schema:si_unit_name"/> <xtc:Definition> The design_pressure_unit specifies the unit of measurement used to measure the design_pressure. </xtc:Definition> <xtc:Property name="npd:Design_temperature" datatype="measure_schema:positive_length_measure"/> <xtc:Definition> The design_temperature specifies the maximum allowable temperature at the Piping_connector. It may be specified as a single value or as a range of values. </xtc:Definition> <xtc:Property name="npd:Min_design_temperature" use="optional" datatype="measure_schema:positive_length_measure"/> <xtc:Definition> The min_design_temperature specifies the minimum design_temperature. </xtc:Definition> <xtc:Property name="npd:Max_design_temperature" use="optional" datatype="measure_schema:positive_length_measure"/> <xtc:Definition> The max_design_temperature specifies the maximum design_temperature. </xtc:Definition> <xtc:Property name="npd:Design_temperature_unit" use="optional" datatype="measure_schema:si_unit_name"/> <xtc:Definition> </xtc:Definition> </xtc:Properties> <xtc:supertype_map> <xtc:Entity_ref eref="ex:Entity"/> </xtc:supertype_map> </xtc:Entity>

Geometry

2-61

Structure:

STEP AP227 (ISO 10303-227) specifies an application protocol (AP) for the exchange of the spatial configuration information of industrial facilities, for example, process plants, ships and their supporting systems. This information includes the shape, spatial arrangement and connection characteristics of piping, HVAC (heating, ventilation and air-conditioning), mechanical, and cableway system components as well as the shape and spatial arrangement characteristics of other related plant systems (for example, instrumentation and controls, and structural systems). Users of this standard should understand the basic principles and concepts of plant design, and piping, HVAC, cableway, and mechanical system design. This chapter of the SCIM specifies requirements for the exchange of information required for the design, analysis, fabrication and installation of piping components and piping systems. It is based on the structures in ISO 10303-227, but these have been modified to account only for the entities required for shipbuilding. The figure below contains a data planning that provides a high level description of the requirements for this chapter of the SCIM, as well as the relationships between the basic data concepts. The data planning model is in similar format to the data planning model included in ISO 10303-227, but has been modified to include only the concepts used in the SCIM Piping Physical Chapter. The data planning model illustrates that a ship consists of ship systems. Ship systems consist of parts and instances with parts describing the properties and attributes of all occurrences of the item, while instances are represented as design occurrences which may be connected to one another using connectors on the design occurrence. The shape and spatial arrangement of plant items are represented by reference geometry and shape representation elements. The shape representation may use constructive solid geometry (CSG), solid boundary representation (Brep) geometry, wireframe geometry, or combinations of these. The design occurrence shape may be represented at various levels of abstraction, from an encompassing envelope to a detailed design description.

Figure — SCIM Piping Physical Data Planning Model

2-62

XML:

 <xtc:Entity name="geometry_schema:geometric_representation_item"/> <xtc:Entity name="geometry_schema:placement"/> <xtc:Entity name="geometry_schema:point"/> <xtc:Entity name="representation_schema:representation_item"/> <xtc:Entity name="geometry_schema:cartesian_point"/> <xtc:Entity name="geometry_schema:direction"/> <xtc:Entity name="geometry_schema:polyline"/> <xtc:Entity name="geometry_schema:composite_curve"/> <xtc:Entity name="representation_schema:founded_item"/> <xtc:Entity name="geometry_schema:composite_curve_segment"/> <xtc:Entity name="geometry_schema:conic"/> <xtc:Entity name="geometry_schema:curve"/> <xtc:Entity name="geometry_schema:line"/> <xtc:Entity name="geometry_schema:circle"/> <xtc:Entity name="geometry_schema:bounded_curve"/>

Structure:

MeasureSome attributes of application objects in the SCIM specify relationships to types of measures. The appropriate unit corresponding to each measure is defined globally in the units attribute of the Ship object. If this is not the appropriate unit, the unit of measure can be specified in an attribute of xxx_unit (e.g. length_unit). Units shall be instantiable in either SI units or other systems of units.

2-63

XML:

 <xtc:Entity name="hmea:Unit_of_measure"/> <xtc:Entity name="measure_schema:named_unit"/> <xtc:Entity name="measure_schema:derived_unit_element"/> <xtc:Entity name="measure_schema:dimensional_exponents"/>

Structure:

PDMProduct Data Management (PDM) data is primarily captured in the SCIM by the PLM Core entities. The PLM Core entities are abstract in that they appear in the ship product model only as instances of the more specialized application specific types. The purpose of an abstract supertype is to collect data that is common to all its more specific subtypes. In the case of the PLM Core, that data is concerned primarily with configuration management, a requirement that befalls all the items in the ship product model – irrespective of life cycle stage or application domain. Configuration management is comprised of a number of facets: one is the ability to create and manage versions of items within the ship product model. This capability applies across the entire product model. A second fact relates to the effectivity of items, which in the shipbuilding world is treated as hull applicability. The PLM Core defines the entities by which each item in the ship product model is applicable to certain hulls or a certain class of hulls. This capability preponderates in the design stage, but it appears in other stages as well. Finally, there has traditionally been a practice of associating certain metadata with items in the ship product model. In the early PDM systems, this metadata consisted of properties, such as author, creation date, etc., which were tied to the models or files managed by the PDM system. In today’s PLM approach, this metadata is tied to particular items within the product model. The PLM Core metadata properties include approval data, the association of documents to items in the product model, certification, and contract references. The PLM Core also describes how product model items are to be linked to various geometric representations of shape. Finally, the PLM Core defines the high level means to define collections or aggregations of items. These aggregations may be hierarchical (as for a product structure or indented bill of material), or they may be unordered (as a for a model’s worth of items).

2-64

XML:

 <xtc:Entity name="npd:Material_specification_selection"/> <xtc:Entity name="npd:Material_specification_subset_reference"/> <xtc:Entity name="npd:Required_material_description".> <xtc:Entity name="npd:External_classification"/> <xtc:Entity name="npd:Pdm_design_definition"/> <xtc:Entity name="npd:Ship"/> <xtc:Entity name="npd:Design_occurrence"/> <xtc:Entity name="npd:Hull_applicability"/>

Structure:

Instances & PartsAn instance of an item is a planned or actual occurrence of that item at a specific location in a spatial, functional, or other design. A part definition will define the properties and attributes of all occurrences of the item, but the instance will refer to a specific occurrence of that part in the design. Please note that the part definition is discussed in the Piping Physical Chapter of the SCIM, rather than this one which addresses functional requirements. The “instances” are subtypes of “Design_occurrence”. If an exchange includes the piping physical descriptions, then each “instance” can be linked to one or more “parts” of the same type to obtain the attributes and properties that apply to all occurrences of that item.

2-65

XML:

 <xtc:Entity name="npd:Piping_size_description"/> <xtc:Entity name="npd:Inside_and_thickness"/> <xtc:Entity name="npd:Outside_and_thickness"/> <xtc:Entity name="npd:Schedule"/> <xtc:Entity name="npd:Pressure_class"/>

Structure:

Parts InstanceAn instance of an item is a planned or actual occurrence of that item at a specific location in a spatial, functional, or other design. A part definition will define the properties and attributes of all occurrences of the item, but the instance will refer to a specific occurrence of that part in the design. Please note that the part definition is discussed in the Piping Physical Chapter of the SCIM, rather than this one which addresses functional requirements. The “instances” are subtypes of “Design_occurrence”. If an exchange includes the piping physical descriptions, then each “instance” can be linked to one or more “parts” of the same type to obtain the attributes and properties that apply to all occurrences of that item.

2-66

XML:

 <xtc:Entity name="npd:Piping_system_component_part"/> <xtc:Entity name="npd:Specialty_item_part"/> <xtc:Entity name="npd:Inline_equipment_item_part"/> <xtc:Entity name="npd:Valve_part"/>  <xtc:Entity name="npd:Fitting_part"/> <xtc:Entity name="npd:Blank_part"/> <xtc:Entity name="npd:Paddle_blank_part"/> <xtc:Entity name="npd:Spectacle_blind_part"/> <xtc:Entity name="npd:Tee_part"/> <xtc:Entity name="npd:Union_part"/> <xtc:Entity name="npd:Orifice_plate_part"/> <xtc:Entity name="npd:Elbow_part"/> <xtc:Entity name="npd:Insert_fitting_part"/> <xtc:Entity name="npd:Cross_part"/> <xtc:Entity name="npd:Coupling_part"/> <xtc:Entity name="npd:Lateral_part"/> <xtc:Entity name="npd:Olet_part"/> <xtc:Entity name="npd:Boss_part"/> <xtc:Entity name="npd:Y_type_lateral_part"/> <xtc:Entity name="npd:Lap_joint_stub_end_part"/> <xtc:Entity name="npd:Reducer_part"/> <xtc:Entity name="npd:Ferrule_part"/> <xtc:Entity name="npd:Eccentric_reducer_part"/> <xtc:Entity name="npd:Pipe_closure_part"/> <xtc:Entity name="npd:Cap_part"/> <xtc:Entity name="npd:Plug_part"/> <xtc:Entity name="npd:Perforated_cap_part"/> <xtc:Entity name="npd:Pipe_closure_plate_part"> <xtc:Entity name="npd:Perforated_plate_part"/>  <xtc:Entity name="npd:Flange_part"/>

2-67

<xtc:Entity name="npd:Slip_on_jacket_flange_part"/> <xtc:Entity name="npd:Weld_neck_jacket_flange_part"/>

Structure:

XML:

Connectors & ConnectionsA key feature of piping and all distribution products is the connectivity of components of the product to form networks. In general, connectivity between piping objects is established by defining a relationship between the distribution ends of connecting objects and a distribution interface. A connection is an association between two items that enables the flow of process material, energy, mechanical loads, or signals between them or constrains their relative positions. Within the scope of the SCIM, a connection can be between either functional or physical plant items. A connection can be the result of a physical joining, or a functional connection can exist between two plant items without a physical joining of the plant items.

A connector is a physical or functional property of a plant item that links it to another plant item, or to a compatible connector on another plant item. This linkage enables the flow of energy, mechanical loads, process material, or signals through the connected plant items

A Functional_connector is a type of Plant_item_connector_occurrence that represents the functional or logical aspect of the Plant_item_connector_occurrence. Each Functional_connector is either: a Line_piping_branch_connector, or a Line_-piping_connector. The distinction is that a “Line_piping_connector” participates in a connection between the logical terminations of two or more “Piping_system_line_segments”, whereas a “Line_piping_branch_connector” participates in a connection between the logical termination of one “Piping_system_line_segment” and a point on another “Piping_system_line_segment” other than a termination. The former “Piping_system_line_segment” branches from the latter “Piping_system_line_segment”.



2-68

<xtc:Entity name="npd:Connector_definition"/>

Structure:

Piping SupportsAnother type of general connectivity used throughout applications is the attachment. An attachment defines a joining of an attached/penetrating object such as an engineering part or a pipe run with an attaching/penetrated object at their attachment ends (refer to Figure below on Attachment Connectivity). Attachments are not used in establishing network connectivity. One type of attachment is the Piping Support.

Figure — Attachment Connectivity

A Piping Support is a type of support component that is fabricated onto the pipe, and supports the pipe detail when it is installed into the ship. Types of Piping Supports include: Base_elbow_support (Adjustable and Non-adjustable), Base_line_support, Dummy_leg, Eccentric_base_elbow_support, Hanger, Lug, Pad, Shoe, Stopper, and Trunnion.

2-69

XML:

 <xtc:Entity name="npd:Support_constraints"/> <xtc:Entity name="npd:Support_usage"/> <xtc:Entity name="npd:Support_usage_connection"/>

Structure:

Piping SystemsA Piping System is a type of ship system that performs a transport function, and that is composed primarily of pipes, pipe fittings, and valves subject to the same set or sets of design conditions. A Piping System is a system of interconnected objects that convey fluid, vapor, or particulate flow throughout a ship.

The functional description of a Piping System is provided under the entities for Piping_system_line and Piping_system_line _segment.

A Piping_system_line is a logical component of a Piping System and is composed of a collection of interconnected Piping_system_line_segment objects. The information contained within these entities and their attributes describes the functional links and properties of a flow stream in a Piping System. It includes information about the segments in the line and the specifications for these segments, such as design criteria, service conditions, and line identifier.

2-70

XML:

 <xtc:Entity name="npd:Ship_system"/> <xtc:Entity name="npd:Piping_system"/> <xtc:Entity name="npd:Ship_system_assembly"/>

Structure:

Instrumenation & ControlAn Instrumentation and Control System is a type of ship system that is a system of wiring, switches, controls, and other equipment associated with monitoring and controlling the performance characteristics of ship system objects. An Instrumentation and Control Component is a type of item that is an individually identifiable item or combination of items that is part of the functional Instrumentation and Control System. Each Instrumentation_and_control_component may be an Instrument.

An Instrument is a type of Instrumentation_and_control_component that monitors one or more performance characteristics of a system. Examples of Instrumentation_and_control_component objects include wiring, switches, control valves, and gauges.


2-71

XML:

 <xtc:Entity name="npd:Instrumentation_and_control_component_part"/> <xtc:Entity name="npd:Instrument_part"/> <xtc:Entity name="npd:Inline_instrument_part"/> <xtc:Entity name="npd:Offline_instrument_part"/>

2-72

Associations:

Name From Object To Object Description

piping_system_functional.is_composed_of

Piping_system_functional"

Piping_system_component_functional

The is_composed_of specifies what Plant_item's the Plant_system is composed of.

Piping_functional_connector.is_defined_by"

Piping_functional_connector"

Connector_definition The is_defined_by specifies what Connector_definition defines the Piping_functional_connector_definition.

piping_functional_connector.connect_point

Piping_functional_connector

geometry_schema:cartesian_point

The connect_point specifies a point on or in the connector where the terminal interface with another connector occurs.

Piping_connection_functional.connects

Piping_connection_functional


The connects specifies the Physical_connectors which the Piping_physical_connector connects.

piping_system_component_functional.end_1_connector



The end_1_connector specifies the Piping_connector designated as end one.


Inline_instrument_functional Bushing_functional Blank_functional Cross_functional Coupling_functional Elbow_functional Flange_functional Insert_fitting_functionalLap_joint_stub_end_functional Lateral_functional Olet_functional Orifice_plate_functionalPerforated_cap_functional Perforated_plate_functional Tee_functional Union_functional Y_type_lateral_functional


The end_2_connector specifies the Piping_connector designated as end two.


Cross_functional Weld_neck_jacket_flange_functional Slip_on_jacket_flange_functional Lateral_functional Tee_functional


The end_3_connector specifies the Piping_connector designated as end three.

pipe_functional.end_4_connector

Cross_functional Piping_functional_connector

The end_4_connector specifies the Piping_connector designated as end four.

Line_piping_branch_connector.is_connected_to

Line_piping_branch_connection

Line_piping_branch_connector

The is_connected_to specifes the Line_piping_branch_connection which connects the Line_piping_branch_connector.

piping_system_component_functional_to_part


Piping_system_component_part

piping_component.standard_point

piping_component_functional

geometry_schema:cartesian_point

The standard_point specifies an x, y, z coordinate position defined for the Piping_component that will

2-73

position the Piping_component in the schematic.

specialty_item_functional_to_part

Specialty_item_functional

Specialty_item_part

inline_equipment_item_functional_to_part

Inline_equipment_item_functional

Inline_equipment_item_part

valve_functional_to_part

Valve_functional Valve_part

fitting_functional_to_part

Fitting_functional Fitting_part

blank_functional_to_part

Blank_functional fitting_functional_to_part

paddle_blank_functional_to_part

Paddle_blank_functional

Paddle_blank_part

spectacle_blind_functional_to_part

Spectacle_blind_functional

Spectacle_blind_part

tee_functional_to_part Tee_functional Tee_part

union_functional_to_part

Union_functional Union_part

orifice_plate_functional_to_part

Orifice_plate_functional

Orifice_plate_part

elbow_functional_to_part

Elbow_functional Elbow_part

insert_fitting_functional_to_part

Insert_fitting_functional Insert_fitting_part

cross_functional_to_part

Cross_functional Cross_part

coupling_functional_to_part

Coupling_functional Coupling_part

lateral_functional_to_part

Lateral_functional Lateral_part

olet_functional_to_part Olet_functional Olet_part

boss_functional_to_part Boss_functional Boss_part

y_type_lateral_functional_to_part

Y_type_lateral_functional

Y_type_lateral_part

lap_joint_stub_end_functional_to_part

Lap_joint_stub_end_functional

Lap_joint_stub_end_part

bushing_functional_to_part

Bushing_functional Bushing_part

reducer_functional_to_part

Reducer_functional Reducer_part

ferrule_functional_to_part

Ferrule_functional Ferrule_part

eccentric_reducer_functional_to_part

Eccentric_reducer_functional

Eccentric_reducer_part

pipe_closure_functional_to_part

Pipe_closure_functional Pipe_closure_part

2-74

cap_functional_to_part Cap_functional Cap_part

plug_functional_to_part Plug_functional Plug_part

perforated_cap_functional_to_part

Perforated_cap_functional

Perforated_cap_part

plate_functional_to_part

Plate_functional Plate_part

perforated_plate_functional_to_part

Perforated_plate_functional

Perforated_plate_part

flange_functional_to_part

Flange_functional Flange_part

slip_on_jacket_flange_functional_to_part

Slip_on_jacket_flange_functional

Slip_on_jacket_flange_part

weld_neck_jacket_flange_functional_to_part

Weld_neck_jacket_flange_functional

Weld_neck_jacket_flange_part

instrumentation_and_control_component_functional_to_part

Instrumentation_and_control_component_functional

Instrumentation_and_control_component_part

instrument_functional_to_part

Instrument_functional Instrument_part

inline_instrument_functional_to_part

Inline_instrument_functional

Inline_instrument_part

offline_instrument_functional_to_part

Offline_instrument_functional

Offline_instrument_part

piping_specification.is_composed_of

Piping_specification Family_definition

piping_specification.specifies_components_for

Piping_specification Piping_system_line_segment

piping_connector_service_characteristic.supports

Piping_connector_service_characteristic

Service_operating_case

stream_design_case.defines

Stream_design_case Service_operating_case

stream_design_case.is_composed_of"

Stream_design_case Stream_phase

stream_design_case.defines_transport_needs_for

Piping_system_line_segment

Stream_design_case

piping_system.is_made_up_of

Piping_system_functional

Piping_system_line

piping_system_line.p_and_i_reference

Piping_system_line Document_metadata

piping_system_line.is_started_or_ended_by

Piping_system_line Piping_system_line_termination

line_to_line_connection.connects

Line_to_line_connection

Line_to_line_termination

piping_system_line_segment.is_connected_to

Line_piping_branch_connection


2-75

Line_piping_connector.is_connected_to"

Line_piping_item_branch_connection

Line_piping_connector

Line_piping_termination.is_connected_to

Line_piping_connection Line_piping_termination

line_branch_termination.branches_from

Line_branch_connection

Line_branch_termination

piping_system_line.is_composed_of

Piping_system_line Piping_system_line_segment

piping_system_line_segment.is_terminated_by


Piping_system_line_segment_termination

piping_system_line_segment.has_branches_defined_by


Line_branch_connection

2-76

Traceability Matrix:

SCIMEntity/Properties STEP Schema

2-77

Documents

AP227 Piping Functional - Latest in Interoperability · · 2008-09-13the arrangement in 3-D space of piping components meeting the applicable system specification and with ... required