The piping functional design use case (edo227-pipe-functional) describes the information needed to define the product model for ship's piping functional design. This entails the information traditionally associated with a piping diagram, exclusive of the schematics. The purpose of the use case is to provide enough information regarding the connectivity, joints, pipe lines and piping components to define the piping product model from a functional perspective. This use case includes the specification of the occurrences (functional instances) of the piping product model as well as the parts (ie engineering data for a pipe or piping component that is applicable to all occurrences of that part).

This information is developed during the following process stage:

The functional configuration of the piping systems

This information supports the following activities:

References to or designation of functional characteristics of piping components as required for piping system design.

This information is used in the following interchanges:

Design engineer and system engineer
Design engineer and fabricator
Integration of designs from different design engineers
Shipyard and customer (design deliverable)

This information contains the following kind of entities and associations:

Characterization of physical Pipe components

Including Pipelines, and piping Components which are a part of the piping system.

Connections, piping component parts, and piping functional instances.
Identification of catalog information associated with each component

This information contains no geometric representation:

For a more detailed description of the information requirements of this use case, see ISO10303-2227 (ed 2). Note that this standard, also known as Application Protocol (AP) 227 is a superset of the current use case and includes a number of information elements not used in this use case.

Latest Deliverable:
edo227-pipe-functional#current.zip
edo227-pipe-functional#current-metadata.zip