IPDE Specification Information Requirements Ship Arrangements

Transcription

1 IPDE Specification Information Requirements Ship Arrangements Overview: The SCIM provides an information model for the computer-interpretable representation of product information and for the exchange of product data. The objective is to provide a neutral mechanism capable of describing products throughout their life cycle. This mechanism is suitable not only for neutral file exchange, but also as a basis for implementing and sharing product databases, and as a basis for archiving. This chapter of the SCIM specifies an information model and schema for the exchange of product data representing a ship's internal subdivision information between different organizations with a need for that data. Such organizations include ship owners, design agents, fabricators, and classification societies. This chapter is one of a series of parts that together aim to provide an integrated computer interpretable product model for ships. The series of chapters comprising the SCIM assumes that the ship product model can be divided into separate ship systems that each cover a key element of the ship for its whole life cycle. This chapter of the SCIM has been developed to support the shipbuilding activities and computer applications associated with the functional design, detail design, production engineering, and operations life cycle phases for commercial or military ships. The types of design activities and computer applications supported include the arrangement of spaces within a ship, definition of the intended function of the compartments and zones, detail design of the compartments and zones, geometric representation of compartments and zones, compartment property requirements, compartment property as-designed and as-built values, identification of the outfitting items contained in a compartment, definition of cargoes, association of cargoes to a compartment, definition of design and operating loading conditions, and damage stability analysis. This chapter defines the context, scope, and information requirements for the exchange of ship arrangement definitions, geometric representations of compartments and zones, compartment properties, cargoes, cargo assignments, loading conditions, and damage stability information, and specifies the integrated resources necessary to satisfy these requirements. Arrangement Properties The hull form of a ship is internally subdivided early in the design lifecycle by the introduction of many additional surfaces. These surfaces are associated with the molded hull form elements such as bulkheads and decks. Structural entities such as plate parts and stiffeners will be defined on these surfaces as the design progresses. A region of the ship, whether it be interior to the hull such as a tank or enclosing one if its exposed decks such as a helicopter landing platform, is designated a space. Two types of spaces are addressed by this chapter of the SCIM: compartments and zones. Compartments represent physical, bounded spaces. Zones represent regions surrounded by some abstract boundary or alternatively can be defined as a set of compartments. Entity: Compartment_property To collect properties that describe the measure of significant characteristics of a compartment associated within a specific context. In order to define a Compartment_property, certain properties must be captured, such as the key information and the context. 2-1

2 npd:compartment_property A Compartment_property is a measure of some significant characteristic of a compartment associated with a specific context. Each Compartment_property is either a General_compartment_property, a Compartment_naval_administrative_property, a Cargo_compartment_property, or a Tank_compartment_property. Name 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. Compartment_property_context No The context specifies an indicator used to associate a design meaning with a compartment property. The maximum and minimum contexts serve to define the design limits for the property, while the estimated, calculated, and measured contexts associate a degree of accuracy for the property value. <xtc:entity name="npd:compartment_property" abstract="true"> <xtc:definition> A Compartment_property is a measure of some significant characteristic of a compartment associated with a specific context. Each Compartment_property is either a General_compartment_property, a Compartment_naval_administrative_property, a Cargo_compartment_property, or a Tank_compartment_property. <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="context" datatype="npd:compartment_property_context"/> <xtc:definition> The context specifies an indicator used to associate a design meaning with a compartment property. The maximum and minimum contexts serve to define the design limits for the property, while the estimated, calculated, and measured contexts associate a degree of accuracy for the property value. Entity: General_compartment_property 2-2

3 To collect properties that describe a type of compartment property that defines generic properties that are applicable to all type of compartments. In order to define a General_compartment_property, certain properties must be captured. npd:general_compartment_property A General_compartment_property is a type of Compartment_property that defines generic properties that are applicable to all types of compartments. Each General_compartment_property is either a Compartment_volume_property, a Compartment_area_property, a Compartment_volume_permeability_property, a Compartment_coating, a Compartment_tightness, a Compartment_occupancy, a Compartment_air_circulation_rate, a Compartment_illumination, a Compartment_abbreviated_name, a Compartment_acceleration, a Compartment_noise_category, a Compartment_insulation, or a Compartment_access_authorization. None <xtc:entity name="npd:general_compartment_property" abstract="true"> <xtc:definition> A General_compartment_property is a type of Compartment_property that defines generic properties that are applicable to all types of compartments. Each General_compartment_property is either a Compartment_volume_property, acompartment_area_property, a Compartment_volume_permeability_property, a Compartment_coating, a Compartment_tightness, acompartment_occupancy, a Compartment_air_circulation_rate, a Compartment_illumination, a Compartment_abbreviated_name, acompartment_acceleration, a Compartment_noise_category, a Compartment_insulation, or a Compartment_access_authorization. <xtc:entity_ref eref="npd:compartment_property"> Entity: Compartment_noise_category To collect properties that describe a compartment noise category. In order to define a Compartment_noise_category, certain properties must be captured, such as the noise category, a value and property context. npd:compartment_noise_category 2-3

4 A Compartment_noise_category is a sub-type of a General_compartment_property and defines properties that are applicable to noise category compartments. Name Noise_category No The category of compartment noise; a, b, c, d, e, f. User_defined_value No The value associated with the particular context within the category. Property_context No The context, such as estimated, calculated, maximum, measured or minimum. <xtc:entity name="npd:compartment_noise_category"> <xtc:property name="noise_category" datatype="npd:noise_category"/> <xtc:property name="user_defined_value" datatype="xs:normalizedstring" use="optional"/> <xtc:property name="property_context" datatype="npd:compartment_property_context"/> <xtc:entity_ref eref="npd:general_compartment_property"> <xtc:entity_ref eref="npd:compartment_property"> Entity: Compartment_volume_property To collect properties that describes the volumetric properties of a compartment In order to define a Compartment_volume_property, certain properties must be captured, such as the volume. npd:compartment_volume_property A Compartment_volume_property is a type of General_compartment_property that describes the volumetric properties of a compartment. 2-4

5 Name Volume No The volume specifies the volume of a compartment. <xtc:entity name="npd:compartment_volume_property"> <xtc:definition> A Compartment_volume_property is a type of General_compartment_property that describes the volumetric properties of a compartment. <xtc:property name="volume" datatype="measure_schema:volume_measure"/> <xtc:definition> The volume specifies the volume of a compartment. <xtc:property name="property_context" datatype="npd:compartment_property_context"> <!-- for centre location --> <xtc:property name="longitudinal_location" datatype="measure_schema:length_measure"/> <xtc:property name="transversal_location" datatype="measure_schema:length_measure"/> <xtc:property name="vertical_location" datatype="measure_schema:length_measure"/> <xtc:entity_ref eref="npd:general_compartment_property"> <xtc:entity_ref eref="npd:compartment_property"> Entity: Compartment_tightness To collect properties that describe a general compartment property that indicates the ability to prevent the passage of air and liquid, required of all bulkheads forming the boundary of the compartment. In order to define a Comprtment_tightness, certain properties must be captured, such as the tightness, user defined value and property context. npd:compartment_tightness A Compartment_tightness is a type of General_compartment_property that is an indicator as to the degree of tightness, the ability to 2-5

6 prevent the passage of air and liquid, required of all bulkheads forming the boundary of the compartment. Name Required_bulkhead_tightness No The required_bulkhead_tightness specifies an indicator of the ability to prevent the passage of air and liquid for all bulkheads forming the boundary of the compartment. User_defined_value No The tightness of the compartment is defined in the user_defined_value attribute. Property_context No The context, such as estimated, calculated, maximum, measured or minimum. <xtc:entity name="npd:compartment_tightness"> <xtc:definition> A Compartment_tightness is a type of General_compartment_property that is an indicator as to the degree of tightness, the ability to prevent the passage of air and liquid, required of all bulkheads forming the boundary of the compartment. <xtc:property name="required_bulkhead_tightness" datatype="npd:compartment_required_bulkhead_tightness"/> <xtc:definition> The required_bulkhead_tightness specifies an indicator of the ability to prevent the passage of air and liquid for all bulkheads forming the boundary of the compartment. <xtc:property name="user_defined_value" datatype="xs:normalizedstring" use="optional"/> <xtc:definition> The tightness of the compartment is defined in the user_defined_value attribute. <xtc:property name="property_context" datatype="npd:compartment_property_context"/> <xtc:entity_ref eref="npd:general_compartment_property"> <xtc:entity_ref eref="npd:compartment_property"> Entity: Compartment_air_circulation_rate To collect properties that describe the volume of air changes for the compartment per unit of time. In order to define a Compartment_air_circulation_rate, certain properties must be captured, such as the air circulation rate and the property context. npd:compartment_air_circulation_rate 2-6

7 A Compartment_air_circulation_rate is a type of General_compartment_property that defines the volume of air changes for the compartment per unit of time. Name Air_circulation_rate No The air_circulation_rate specifies measure of the volume of air changed for the compartment per unit of time. Property_context No The context, such as estimated, calculated, maximum, measured or minimum. <xtc:entity name="npd:compartment_air_circulation_rate"> <xtc:definition> A Compartment_air_circulation_rate is a type of General_compartment_property that defines the volume of air changes for the compartment per unit of time. <xtc:property name="air_circulation_rate" datatype="measure_schema:derived_unit"/> <xtc:definition> The air_circulation_rate specifies measure of the volume of air changed for the compartment per unit of time. <xtc:property name="property_context" datatype="npd:compartment_property_context"/> <xtc:entity_ref eref="npd:general_compartment_property"> <xtc:entity_ref eref="npd:compartment_property"> Entity: Compartment_abbreviated_name To hold the abbreviated name of a compartment. In order to capture the abbreviated name of a compartment, this entity must exist to store it. npd:compartment_abbreviated_name The Compartment_abbreviated_name holds the abbreviated name of the compartment. 2-7

8 Name Abbreviated_name No The abbreviated name of the compartment. <xtc:entity name="npd:compartment_abbreviated_name"> <xtc:property name="abbreviated_name" datatype="xs:normalizedstring"/> <xtc:entity_ref eref="npd:compartment_property"> Entity: Tank_compartment_property To collect properties that describe a measure of some significant characteristic of a tank compartment associated with a specific context. In order to define a Tank_compartment_property, certain properties must be captured, such as the design stowage density and property context. npd:tank_compartment_property A Tank_compartment_property is a measure of some significant characteristic of a tank compartment associated with a specific context. Name Design_stowage_density No 2-8

9 Property_context No The context, such as estimated, calculated, maximum, measured or minimum. <xtc:entity name="npd:tank_compartment_property"> <xtc:property name="design_stowage_density" datatype="measure_schema:derived_unit"/> <xtc:property name="property_context" datatype="npd:compartment_property_context"/> <xtc:entity_ref eref="npd:compartment_property"> Entity: Moments_of_inertia npd:moments_of_inertia Name Long_moment_of_inertia Trans_moment_of_inertia No No Property_context No The context, such as estimated, calculated, maximum, measured or minimum. 2-9

10 <xtc:entity name="npd:moments_of_inertia"> <xtc:property name="long_moment_of_inertia" datatype="measure_schema:derived_unit"/> <xtc:property name="trans_moment_of_inertia" datatype="measure_schema:derived_unit"/> <xtc:property name="property_context" datatype="npd:compartment_property_context"/> <xtc:entity_ref eref="npd:compartment_property"> Entity: Tank_geometric_parameters npd:tank_geometric_parameters Name Length_wash Breadth_wash No No Property_context No The context, such as estimated, calculated, maximum, measured or minimum. <xtc:entity name="npd:tank_geometric_parameters"> <xtc:property name="length_wash" datatype="measure_schema:length_measure"/> <xtc:property name="breadth_wash" datatype="measure_schema:length_measure"/> <xtc:property name="property_context" datatype="npd:compartment_property_context"/> <xtc:entity_ref eref="npd:compartment_property"> 2-10

11 Entity: Tank_piping_design_properties npd:tank_piping_design_properties Name Sounding_pipe_height Airpipe_height Relief_valve_pressure_setting Filling_height No No No No Property_context No The context, such as estimated, calculated, maximum, measured or minimum. <xtc:entity name="npd:tank_piping_design_properties"> <xtc:property name="sounding_pipe_height" datatype="measure_schema:length_measure"/> <xtc:property name="airpipe_height" datatype="measure_schema:length_measure"/> <xtc:property name="relief_valve_pressure_setting" datatype="npd:pressure_measure"/> <xtc:property name="filling_height" datatype="measure_schema:length_measure"/> <xtc:property name="property_context" datatype="npd:compartment_property_context"/> <xtc:entity_ref eref="npd:compartment_property"> Entity: Compartment_area_property 2-11

12 To collect properties that describes different types of area properties for a compartment, such as a vertical longitudinal cross sectional area property. In order to define a Compartment_area_property, certain properties must be captured, such as the property context. npd:compartment_area_property A Compartment_area_property is a type of General_compartment_property that defines different types of area properties for a compartment. Each Compartment_area_property is either a Compartment_vertical_longitudinal_cross_sectional_area_property, a Compartment_vertical_transverse_cross_sectional_area_property,a Compartment_horizontal_cross_sectional_area_property, a Compartment_stiffened_surface_area_property, or a Compartment_unstiffened_surface_area_property. Name Property_context No The context, such as estimated, calculated, maximum, measured or minimum. <xtc:entity name="npd:compartment_area_property"> <xtc:definition> A Compartment_area_property is a type of General_compartment_property that defines different types of area properties for a compartment. Each Compartment_area_property is either acompartment_vertical_longitudinal_cross_sectional_area_property, a Compartment_vertical_transverse_cross_sectional_area_property,a Compartment_horizontal_cross_sectional_area_property, a Compartment_stiffened_surface_area_property, or a Compartment_unstiffened_surface_area_property. <xtc:property name="property_context" datatype="npd:compartment_property_context"/> <xtc:entity_ref eref="npd:general_compartment_property"> <xtc:entity_ref eref="npd:compartment_property"> Entity: Compartment_horizontal_cross_sectional_area_property 2-12

13 To collect properties that describe a two dimensional cross sectional area for a compartment. In order to define a compartment horizontal cross sectional area property, certain properties must be captured, such as the horizontal cross sectional area. npd:compartment_horizontal_cross_sectional_area_property A Compartment_horizontal_cross_sectional_area_property is a type of Compartment_area_property that represents a two dimensional cross-sectional area for a compartment. Name Horizontal_cross_sectional_area No The horizontal_cross_sectional_area specifies an area measurement on a plane parallel to the baseline plane. <xtc:entity name="npd:compartment_horizontal_cross_sectional_area_property"> <xtc:definition> A Compartment_horizontal_cross_sectional_area_property is a type of Compartment_area_property that represents a two dimensional cross-sectional area for a compartment. <xtc:property name="horizontal_cross_sectional_area" datatype="measure_schema:area_measure"/> <xtc:definition> The horizontal_cross_sectional_area specifies an area measurement on a plane parallel to the baseline plane. <xtc:entity_ref eref="npd:compartment_area_property"> <xtc:entity_ref eref="npd:general_compartment_property"> <xtc:entity_ref eref="npd:compartment_property"> Spaces 2-13

14 The spaces breakdown provides the identification and functional information about the compartments that constitute the spatial partitioning of the interior volume of the ship. It supports both the physical subdivision of the space into compartments, and the logical subdivision of the space into zones. In the SCIM, a Space is a type of Item that is a defined volume on board a ship. A Space may have a functional definition, design definitions, and product structure definitions relating applicable properties to the Space. Each Space is a Compartment, a Deck_zone, or a Zone. Compartments represent physical, bounded spaces. The most common type of spatial partitioning is the subdivision of a ship into compartments. A compartment is very similar to the idea of a room in a building. The compartment is bounded by the surfaces representing structural decks and bulkheads and also by non-structural (or non load bearing) surfaces that form "joiner bulkheads". Compartments may be classified according to the function they perform with regard to the operation of the ship. The types of spaces supported by the SCIM are cargo/stowage (both liquid and dry cargo), void, habitable, and machinery/equipment. Collections of attributes have been defined for the various compartments depending on their designated use. Compartments serve a vital function in configuration managing engineering part occurrences throughout the lifecycle of the ship. In some cases, the same surfaces that subdivide a ship into compartments may also be used to subdivide the ship into zones. Zones represent regions surrounded by some abstract boundary or alternatively can be defined as a set of compartments. In other cases, additional moulded form geometry elements or geometric surfaces may be required to define zone boundaries. On naval ships, multiple zone subdivisions such as pressure (Collective Protection System), subsafe, damage control, and arrangement zones will be defined and each subdivides the hull into an independent set of spaces. Sometimes, two zones may have the same boundary; however, each zone is still independently represented. In addition to identifying the various spaces on the ship, it is important to represent the connectivity between these spaces. This model supports several types of relationships between spaces, specifically adjacency, functional, positional, connection, and enclosing. Functional relationships can be used to record the fact that one space's design parameters are dependent on some functional characteristic of another space --such as a pair of port and starboard ballast tanks used for anti-roll stabilization. Positional relationships capture design intent expressing the fact that certain spaces must maintain geometric characteristics similar to another space's such as two spaces that should maintain the same transverse width dimension. Finally, enclosing relationships allow the product model to record the fact that one space may be completely surrounded by another space such as a free-standing Lube Oil Settling Tank in the Machinery Space. From a functional standpoint, the model has been developed to associate properties with the various compartments, appropriate to their function. These properties include volumetric capacities, length measures, and cross-sectional areas. The ability to specify constraints on these properties is provided for where appropriate so as to assist engineers in the early stages of design. For example, it is possible to specify a minimum length for a compartment, as well as a maximum length for the compartment. Likewise, it is possible to record an estimated compartment volume, as well as a calculated and a measured. Entity: Space To collect properties that describe a defined volume on board a ship, such as a compartment, a deck zone or a zone. In order to define a space, certain properties must be captured, such as the key information. npd:space 2-14

15 A Space is a type of Item that is a defined volume on board a ship. A Space may have a functional definition, design definitions, and product structure definitions relating applicable properties to the Space. Each Space is either a Compartment, a Deck_zone, or a Zone. Name 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. <xtc:entity name="npd:space" abstract="true"> <xtc:definition> A Space is a type of Item that is a defined volume on board a ship. A Space may have a functional definition, design definitions, and product structure definitions relating applicable properties to the Space. Each Space is either a Compartment, a Deck_zone, or a Zone. <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"/> Entity: Compartment To collect properties that describe a type of space that is a physical subdivision of a space on a ship. In order to define a compartment, certain properties must be captured to describe its design definitions, such as it's physical and geometric properties. npd:compartment A Compartment is a type of Space that is a physical subdivision of space on a ship, designed to hold dry or liquid cargo, fuel, water, passengers, crew, machinery, and equipment. Each Compartment has one or more design definitions, which specify the boundaries of the Compartment as well as its physical and geometric properties. 2-15

16 None <xtc:entity name="npd:compartment"> <xtc:definition> A Compartment is a type of Space that is a physical subdivision of space on a ship, designed to hold dry or liquid cargo, fuel, water, passengers, crew, machinery, and equipment. Each Compartment has one or more design definitions, which specify the boundaries of the Compartment as well as its physical and geometric properties. <xtc:entity_ref eref="npd:space"> Entity: Deck_zone To collect properties that describe a bounded region of a deck with design requirements or characteristics. In order to define a deck zone, certain properties must be captured. npd:deck_zone A Deck_zone is a type of Space that identifies a bounded region of a deck with design requirements or characteristics that must be managed in the design process. None <xtc:entity name="npd:deck_zone"> <xtc:definition> A Deck_zone is a type of Space that identifies a bounded region of a deck with design requirements or characteristics that must be managed in the design process. <xtc:entity_ref eref="npd:space"> 2-16

17 Entity: Zone To collect properties that describe an abstract bounded volume identifying a region of a ship with unique requirements or characteristics. In order to define a zone, certain properties must be captured. npd:zone A Zone is a type of Space that represents an abstract bounded volume identifying a region of a ship with unique requirements or characteristics that must be specially treated in the design and manufacturing processes. None <xtc:entity name="npd:zone" abstract="true"> <xtc:definition> A Zone is a type of Space that represents an abstract bounded volume identifying a region of a ship with unique requirements or characteristics that must be specially treated in the design and manufacturing processes. <xtc:entity_ref eref="npd:space"> Requirement Definitions A Design_requirement is a type of Definition that represents a constraint placed on a design. These constraints identify the set of rules to which the design must adhere. Each Design_requirement is a Compartment_design_requirement, a Class_compartment _requirement_definition, or a Class_deck_load_requirement_definition. Entity: Design_requirement 2-17

18 To collect properties that describe a design requirement. In order to define a design requirement, certain properties must be captured, such as the key and documents properties. npd:design_requirement Name 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. Documents No <xtc:entity name="npd:design_requirement" abstract="true"> <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 datatype="xs:anyuri" name="documents"> <xtc:cardinalities> <xtc:cardinality monad="set" minoccurs="0" maxoccurs="unbounded"> </xtc:cardinalities> </xtc:property> Compartment_design_requirement To collect properties that describe a type of specification that represents a constraint placed on a design. 2-18

19 In order to define a compartment design requirement, certain properties must be collected such as the requirement type. npd:compartment_design_requirement A Compartment_design_requirement is a type of Design_requirement that defines a type of specification that represents a constraint placed on a design. Name Requirement_type No The requirement_type specifies an indicator used to denote the source placing the design requirement on the space. This indicator identifies the discipline or design function that governs some aspect of the design or operation of the space. <xtc:entity name="npd:compartment_design_requirement"> <xtc:definition> A Compartment_design_requirement is a type of Design_requirement that defines a type of specification that represents a constraint placed on a design. <xtc:property name="npd:requirement_type" datatype="npd:compartment_design_requirement_type"/> <xtc:definition> The requirement_type specifies an indicator used to denote the source placing the design requirement on the space. This indicator identifies the discipline or design function that governs some aspect of the design or operation of the space. <xtc:entity_ref eref="npd:design_requirement"> Entity: Class_compartment_requirement_definition To collect properties that describe the definition of a compartment that describes properties that are required for performing a ship design approval by rules. In order to define a class compartment requirement definition, certain properties must be captured, such as info about cargo density, pressure unit mass and length, height and temperature. 2-19

20 npd:class_compartment_requirement_definition A Class_compartment_requirement_definition is a type of Design_requirement that describes properties of a compartment that are required for performing a ship design approval by rules. Each Class_compartment_requirement_definition is either a Class_bulk_load_requirement_definition, or a Class_tank_requirement_definition. Name Cargo_density No The cargo_density specifies the highest cargo density for ships with tanks for liquid; otherwise, it is the stowage rate of bulk load, the total cargo capacity of the ship divided by the total hold volume. Pressure_unit_mass_unit Pressure_unit_length_unit Pressure_unit_time_unit No No No Cargo_height No The cargo_height specifies the filling height in the case of liquid load; otherwise, it is the height from the baseline to the top of the hatch in the case of bulk load. Ambient_temperature No The ambient_temperature specifies whether or not the cargo is to be transported without air conditioning. Min_temperature No The min_temperature specifies the minimum temperature inside the compartment. Max_temperature No The max_temperature specifies the maximum temperature inside the compartment. Min_pressure No The min_pressure specifies the minimum pressure inside the compartment. Max_pressure No The max_pressure specifies the maximum pressure inside the compartment. Coating No The coating specifies the indication whether the compartment is fully coated or not. Damage_waterline No The damage_waterline specifies the height from the baseline to the waterline in a damaged condition of the compartment. <xtc:entity name="npd:class_compartment_requirement_definition"> <xtc:definition> A Class_compartment_requirement_definition is a type of Design_requirement that describes properties of a compartment that are required for performing a ship design approval by rules. Each Class_compartment_requirement_definition is either a Class_bulk_load_requirement_definition, or a Class_tank_requirement_definition. <xtc:property name="cargo_density" datatype="xs:double"/> <xtc:definition> The cargo_density specifies the highest cargo density for ships with tanks for liquid; otherwise, it is the stowage rate of bulk load, the total cargo capacity of the ship divided by the total hold volume. 2-20

21 <xtc:property name="pressure_unit_mass_unit" datatype="measure_schema:si_unit_name"/> <xtc:property name="pressure_unit_length_unit" datatype="measure_schema:si_unit_name"/> <xtc:property name="pressure_unit_time_unit" datatype="measure_schema:si_unit_name"/> <xtc:property name="cargo_height" datatype="measure_schema:positive_length_measure"/> <xtc:definition> The cargo_height specifies the filling height in the case of liquid load; otherwise, it is the height from the baseline to the top of the hatch in the case of bulk load. <xtc:property name="ambient_temperature" datatype="xs:boolean"/> <xtc:definition> The ambient_temperature specifies whether or not the cargo is to be transported without air conditioning. <xtc:property name="min_temperature" datatype="measure_schema:thermodynamic_temperature_measure"/> <xtc:definition> The min_temperature specifies the minimum temperature inside the compartment. <xtc:property name="kax_temperature" datatype="measure_schema:thermodynamic_temperature_measure"/> <xtc:definition> The max_temperature specifies the maximum temperature inside the compartment. <xtc:property name="min_pressure" datatype="npd:pressure_measure"/> <xtc:definition> The min_pressure specifies the minimum pressure inside the compartment. <xtc:property name="max_pressure" datatype="npd:pressure_measure"/> <xtc:definition> The max_pressure specifies the maximum pressure inside the compartment. <xtc:property name="coating" datatype="xs:boolean"/> <xtc:definition> The coating specifies the indication whether the compartment is fully coated or not. <xtc:property name="damage_waterline" datatype="measure_schema:positive_length_measure"/> <xtc:definition> The damage_waterline specifies the height from the baseline to the waterline in a damaged condition of the compartment. <xtc:entity_ref eref="npd:design_requirement"> Entity: Class_tank_requirement_definition To collect properties that describes properties for tanks that are required for performing a ship design approval by rules. In order to define a class tank requirement definition, certain properties must be captured, such as npd:class_tank_requirement_definition A Class_tank_requirement_definition is a type of Class_compartment_requirement_definition that describes properties for tanks that are required for performing a ship design approval by rules. 2-21

22 Name Pressure_relief_setting No The pressure_relief_setting specifies the pressure at which the inert gas relief valve will open. Overflow_height No The overflow_height specifies the maximum filling height in a tank just before overflow. Partial_filling No The partial_filling specifies whether or not the compartment may be partially filled. Free_surface_parameters_length No The free_surface_length specifies the length of the free surface in the tank if there is any free surface. The free_surface_parameters need not be specified for a particular Class_tank_requirement_definition. Free_surface_parameters_breadth No The free_surface_breadth specifies the breadth of the free surface in the tank if there is any free surface. The free_surface_parameters need not be specified for a particular Class_tank_requirement_definition. <xtc:entity name="npd:class_tank_requirement_definition"> <xtc:definition> A Class_tank_requirement_definition is a type of Class_compartment_requirement_definition that describes properties for tanks that are required for performing a ship design approval by rules. <xtc:property name="pressure_relief_setting" datatype="npd:pressure_measure"/> <xtc:definition> The pressure_relief_setting specifies the pressure at which the inert gas relief valve will open. <xtc:property name=overflow_height" datatype="measure_schema:positive_length_measure"/> <xtc:definition> The overflow_height specifies the maximum filling height in a tank just before overflow. <xtc:property name="partial_filling" datatype="xs:boolean"/> <xtc:definition> The partial_filling specifies whether or not the compartment may be partially filled. <xtc:property name="free_surface_parameters_length" datatype="measure_schema:positive_length_measure" use="optional"/> <xtc:property name="free_surface_parameters_breadth" datatype="measure_schema:positive_length_measure" use="optional"/> <xtc:definition> The free_surface_parameters specifies the length and breadth of the free surface in the tank if there is any free surface. The free_surface_parameters need not be specified for a particular Class_tank_requirement_definition. </xtc:property> <xtc:entity_ref eref="npd:class_compartment_requirement_definition"> <xtc:entity_ref eref="npd:design_requirement"> Design & Functional Definitions A Design_definition is a type of Definition that is the basis for all types of design definitions. The ability to reference representations differentiates a Design_definition from a Definition. Each Design_definition is either a Compartment_design_definition or a Deck_zone_design_ definition. 2-22

23 A Functional_definition is a type of Definition that provides the capability to specify a role or purpose for an object. Each Functional_definition is either a Compartment_functional_ definition or a Deck_zone_functional_definition. Entity: Compartment_design_definition To collect properties that describe the definition of a version of a Compartment from a design perspective. In order to define a compartment design definition, certain properties must be captured, such as the key information. npd:compartment_design_definition A Compartment_design_definition is a type of Design_definition that defines a version of a Compartment from a design perspective. Name 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. <xtc:entity name="npd:compartment_design_definition"> <xtc:definition> A Compartment_design_definition is a type of Design_definition that defines a version of a Compartment from a design perspective. <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"/> Entity: Tank_compartment_design_definition 2-23

24 To collect properties that describe a version of a tank compartment from a design perspective. In order to define a tank compartment design definition, certain properties must be captured. npd:tank_compartment_design_definition A Tank_compartment_design_definition is a type of Compartment_design_definition that defines a version of a tank compartment from a design perspective. None <xtc:entity name="npd:tank_compartment_design_definition"> <xtc:definition> <xtc:entity_ref eref="npd:compartment_design_definition"> Entity: Compartment_functional_definition To collect properties that describe the functional role of a Compartment, which may be a pre-defined or user_defined role that corresponds to the intended use of the Compartment. In order to define a compartment functional definition, certain properties must be captured, such as the key and "used for" information. npd:compartment_functional_definition A Compartment_functional_definition is a type of Functional_definition that defines the functional role of a Compartment. The role may be a pre-defined one that corresponds to the intended use of the Compartment or may be a user-defined one. 2-24

25 Name 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. Used_for No The used_for specifies the intended use of a Compartment. The predefined functions correspond to either a general compartment use or a specialized function. The user_defined value allows identification of a type not specified by one of the pre-defined values. <xtc:entity name="npd:compartment_functional_definition"> <xtc:definition> A Compartment_functional_definition is a type of Functional_definition that defines the functional role of a Compartment. The role may be a pre-defined one that corresponds to the intended use of the Compartment or may be a user-defined one. <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="used_for" datatype="npd:pre_defined_compartment_function"/> <xtc:definition> The used_for specifies the intended use of a Compartment. The pre-defined functions correspond to either a general compartment use or a specialized function. The user_defined value allows identification of a type not specified by one of the pre-defined values. Entity: Deck_zone_functional_definition To collect properties that describe a user-defined or predetermined functional role of a Deck_zone. In order to define a deck zone functional definition, certain properties must be captured, such as the key and "used for" information. npd:deck_zone_functional_definition 2-25

26 A Deck_zone_functional_definition is a type of Functional_definition that defines the functional role of a Deck_zone. The role may be a pre-defined one or may be user-defined. Name 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. Used_for No The used_for specifies the intended use of a Compartment. The predefined functions correspond to either a general compartment use or a specialized function. The user_defined value allows identification of a type not specified by one of the pre-defined values. <xtc:entity name="npd:deck_zone_functional_definition"> <xtc:definition> A Deck_zone_functional_definition is a type of Functional_definition that defines the functional role of a Deck_zone. The role may be a pre-defined one or may be user-defined. <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="used_for" datatype="npd:pre_defined_deck_zone_function"/> <xtc:definition> The used_for specifies the name of a function that a specific Deck_zone may have in a ship. Entity: Deck_zone_design_definition To collect properties that describe the abstract definition of a version of a Deck_zone from a design perspective. In order to define a deck zone design definition, certain properties must be collected, such as the npd:deck_zone_design_definition 2-26

27 A Deck_zone_design_definition is a type of Design_definition that is the abstract definition of a version of a Deck_zone from a design perspective. Name 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. Inner_boundaries No The inner_boundaries specifies closed curves which specify any internal voids in the Deck_zone. There may be more than one inner_boundaries for a Deck_zone_design_definition. The inner_boundaries need not be specified for a particular Deck_zone_design_definition. <xtc:entity name="npd:deck_zone_design_definition"> <xtc:definition> A Deck_zone_design_definition is a type of Design_definition that is the abstract definition of a version of a Deck_zone from a design perspective. <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="inner_boundaries" datatype="xs:normalizedstring"/> <xtc:definition> The inner_boundaries specifies closed curves which specify any internal voids in the Deck_zone. There may be more than one inner_boundaries for a Deck_zone_design_definition. The inner_boundaries need not be specified for a particular Deck_zone_design_definition. <xtc:cardinalities> <xtc:cardinality monad="set" minoccurs="0" maxoccurs="unbounded"> </xtc:cardinalities> </xtc:property> > Space Relationships Space relationships provide information relating to the relationships between compartments that can be used to automate the generation of a preliminary compartmentation arrangement or identify relationships between compartments after they have been populated in the product model. A Space_arrangement_relationship is a type of Item_relationship that represents an association between two spaces. The collection of the set of any particular category of relationships defines a network of inter-related spaces. Each 2-27

28 Space_arrangement_relationship is one of the following types: Space_enclosing_relationship - identifies a space that is contained within another space. The two spaces may share one or more boundaries, or a portion of a boundary Space_adjacency_relationship - identifies spaces that share a common boundary. These spaces may or may not be accessible from one another and may share all or a portion of a boundary Space_connection_relationship - identifies spaces that are intended to be interconnected in some way Space_positional_relationship - identifies a space whose position is dependent upon another space. A variety of positional relationship types are supported that define the significant aspects of the relationship Entity: Space_adjacency_relationship To collect properties that describe spaces that share a common boundary that may or may not be accessible from one another and may share all or a portion of a boundary. In order to define a space adjacency relationship, certain properties must be captured, such as npd:space_adjacency_relationship A Space_adjacency_relationship is a type of Space_arrangement_relationship that identifies spaces that share a common boundary. These spaces may or may not be accessible from one another and may share all or a portion of a boundary. Name Adjacency_type No The adjacency_type specifies whether the two adjacent spaces are completely or partially adjacent. Adjacency_access No The adjacency_access specifies that it is or is not intended to provide a means to allow passage of a person between the two adjacent spaces. A value of TRUE specifies the design intent of accessibility. <xtc:entity name="npd:space_adjacency_relationship"> <xtc:definition> A Space_adjacency_relationship is a type of Space_arrangement_relationship that identifies spaces that share a common boundary. These spaces may or may not be accessible from one another and may share all or a portion of a boundary. <xtc:property name="adjacency_type" datatype="npd:space_adjacency_type"/> <xtc:definition> The adjacency_type specifies whether the two adjacent spaces are completely or partially adjacent. <xtc:property name="adjacency_access" datatype="xs:boolean"/> <xtc:definition> The adjacency_access specifies that it is or is not intended to provide a means to allow passage of a person between the two adjacent spaces. A value of TRUE specifies the design intent of accessibility. 2-28

29 <xtc:entity_ref eref="npd:space_arrangement_relationship"> Entity: Space_arrangement_relationship To collect properties that describe an association between two spaces. In order to define a space arrangement relationship, certain properties must be captured, such as the key information. npd:space_arrangement_relationship A Space_arrangement_relationship is a type of Item_relationship that represents an association between two spaces. The collection of the set of any particular category of relationships defines a network of inter-related spaces. Each Space_arrangement_relationship is either a Space_enclosing_relationship, a Space_adjacency_relationship, a Space_connection_relationship, or a Space_positional_relationship. Name 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. <xtc:entity name="npd:space_arrangement_relationship" abstract="true"> <xtc:definition> A Space_arrangement_relationship is a type of Item_relationship that represents an association between two spaces. The collection of the set of any particular category of relationships defines a network of interrelated spaces. Each Space_arrangement_relationship is either a Space_enclosing_relationship, a Space_adjacency_relationship, a Space_connection_relationship, or a Space_positional_relationship. <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"/> 2-29

30 Entity: Adjacent_space_surface_area To collect properties that describe the portion of the boundary between adjacent spaces that is common to both spaces. In order to define an adjacent space surface area, certain properties must be captured, such as the property context. npd:adjacent_space_surface_area An Adjacent_space_surface_area is the area of that portion of the boundary between adjacent spaces that is common to both spaces. Name Property_context No The context, such as estimated, calculated, maximum, measured or minimum. <xtc:entity name="npd:adjacent_space_surface_area"> <xtc:definition> An Adjacent_space_surface_area is the area of that portion of the boundary between adjacent spaces that is common to both spaces. <xtc:property name="property_context" datatype="npd:compartment_property_context"/> <xtc:property name="surface_area" datatype="measure_schema:area_measure"/> <xtc:definition> The surface_area specifies the area measure of shared boundary between the adjacent spaces. 2-30

31 Entity: Coating_level npd:coating_level Name Lower_extent Upper_extent No No Property_context No The context, such as estimated, calculated, maximum, measured or minimum. <xtc:entity name="npd:coating_level"> <xtc:property name="lower_extent" datatype="npd:percentage"/> <xtc:property name="upper_extent" datatype="npd:percentage"/> <xtc:property name="property_context" datatype="npd:compartment_property_context"/> Entity: Compartment_coating 2-31

32 npd:compartment_coating A Compartment_coating is a type of General_compartment_property that specifies the type of painting or coating required for a compartment. None <xtc:entity name="npd:compartment_coating"> <xtc:definition> A Compartment_coating is a type of General_compartment_property that specifies the type of painting or coating required for a compartment. <xtc:entity_ref eref="npd:general_compartment_property"> <xtc:entity_ref eref="npd:compartment_property"> Entity: Compartment_occupancy To collect properties that describe the design requirements for the number of people that are permitted to occupy a compartment. In order to define a compartment occupancy, certain properties must be captured, such as the number of persons permitted and the property context. npd:compartment_occupancy A Compartment_occupancy is a type of General_compartment_property that specifies the design requirements for the number of people that are permitted to occupy a compartment. 2-32

33 Name Occupancy No The occupancy specifies the number of persons who are permitted to occupy a compartment simultaneously. Property_context No The context, such as estimated, calculated, maximum, measured or minimum. <xtc:entity name="npd:compartment_occupancy"> <xtc:definition> A Compartment_occupancy is a type of General_compartment_property that specifies the design requirements for the number of people that are permitted to occupy a compartment. <xtc:property name="occupancy" datatype="xs:long"/> <xtc:definition> The occupancy specifies the number of persons who are permitted to occupy a compartment simultaneously. <xtc:property name="property_context" datatype="npd:compartment_property_context"/> <xtc:entity_ref eref="npd:general_compartment_property"> <xtc:entity_ref eref="npd:compartment_property"> Entity: Compartment_unstiffened_surface_area_property To collect properties that describe a measure of the amount of an unstiffened surface area for the compartment. In order to define a compartment unstiffened surface area property, certain properties must be captured, such as the unstiffened surface area and the property context. npd:compartment_unstiffened_surface_area_property A Compartment_unstiffened_surface_area_property is a type of Compartment_area_property that is a measure of the amount of surface area for the compartment excluding the surface area of any interior stiffeners on the bounding bulkheads, decks, and hull structure. 2-33

34 Name Unstiffened_surface_area No The unstiffened_surface_area specifies the value of the unstiffened surface area. Property_context No The context, such as estimated, calculated, maximum, measured or minimum. <xtc:entity name="npd:compartment_unstiffened_surface_area_property"> <xtc:definition> A Compartment_unstiffened_surface_area_property is a type of Compartment_area_property that is a measure of the amount of surface area for the compartment excluding the surface area of any interior stiffeners on the bounding bulkheads, decks, and hull structure. <xtc:property name="unstiffened_surface_area" datatype="measure_schema:area_measure"/> <xtc:definition> The unstiffened_surface_area specifies the value of the unstiffened surface area. <xtc:property name="property_context" datatype="npd:compartment_property_context"/> <xtc:entity_ref eref="npd:compartment_area_property"> <xtc:entity_ref eref="npd:general_compartment_property"> <xtc:entity_ref eref="npd:compartment_property"> Entity: Compartment_vertical_longitudinal_cross_sectional_area_p roperty To collect properties that describe a two dimensional cross-sectional area for a compartment. In order to define a compartment vertical longitudinal cross sectional area property, certain properties must be captured, such as the vertical longitudinal cross sectional area. npd:compartment_vertical_longitudinal_cross_sectional_area_property A Compartment_vertical_longitudinal_cross_sectional_area_property is a type of Compartment_- area_property that specifies a two dimensional cross-sectional area for a compartment. 2-34

35 Name Vertical_longitudinal_cross_sectional_area No The vertical_longitudinal_cross_sectional_area specifies an area measurement corresponding to a plane defined by the vertical and longitudinal global axes. Property_context No The context, such as estimated, calculated, maximum, measured or minimum. <xtc:entity name="npd:compartment_vertical_longitudinal_cross_sectional_area_property"> <xtc:definition> A Compartment_vertical_longitudinal_cross_sectional_area_property is a type of Compartment_- area_property that specifies a two dimensional cross-sectional area for a compartment. <xtc:property name="vertical_longitudinal_cross_sectional_area" datatype="measure_schema:area_measure"/> <xtc:definition> The vertical_longitudinal_cross_sectional_area specifies an area measurement corresponding to a plane defined by the vertical and longitudinal global axes. <xtc:property name="property_context" datatype="npd:compartment_property_context"/> <xtc:entity_ref eref="npd:compartment_area_property"> <xtc:entity_ref eref="npd:general_compartment_property"> <xtc:entity_ref eref="npd:compartment_property"> Entity: Compartment_vertical_transverse_cross_sectional_area_pro perty To collect properties that describe a two dimensional cross-sectional area for a compartment. In order to define a comparment vertical transverse cross sectional area property, certain properties must be captured, such as npd:compartment_vertical_transverse_cross_sectional_area_property A Compartment_vertical_transverse_cross_sectional_area_property is a type of Compartment_area_property that specifies a two dimensional cross-sectional area for a compartment. 2-35

36 Name Vertical_transverse_cross_sectional_area No The vertical_transverse_cross_sectional_area specifies an area measurement corresponding to a plane defined by the vertical and transverse global axes. Property_context No The context, such as estimated, calculated, maximum, measured or minimum. <xtc:entity name="npd:compartment_vertical_transverse_cross_sectional_area_property"> <xtc:definition> A Compartment_vertical_transverse_cross_sectional_area_property is a type of Compartment_area_property that specifies a two dimensional cross-sectional area for a compartment. <xtc:property name="vertical_transverse_cross_sectional_area" datatype="measure_schema:area_measure"/> <xtc:definition> The vertical_transverse_cross_sectional_area specifies an area measurement corresponding to a plane defined by the vertical and transverse global axes. <xtc:property name="property_context" datatype="npd:compartment_property_context"/> <xtc:entity_ref eref="npd:compartment_area_property"> <xtc:entity_ref eref="npd:general_compartment_property"> <xtc:entity_ref eref="npd:compartment_property"> Entity: Compartment_volume_permeability_property To collect properties that describe a measure, expressed as a percentage of the volume of the compartment, representing open space that is not occupied by equipment, structure, or machinery that would flood in the event the watertight integrity of the compartment was damaged. In order to define a compartment volume permeability property, certain properties must be captured, such as the permeability. npd:compartment_volume_permeability_property A Compartment_volume_permeability_property is a type of General_compartment_property that is a measure, expressed as a percentage of the volume of the compartment, representing open space that is not occupied by equipment, structure, or machinery that would flood in the event the watertight integrity of the compartment was damaged. This is a key parameter for the damage stability calculations for a ship. 2-36

37 Name Permeability No The permeability specifies the percentage of the total volume of a compartment that is not occupied by the ship structure, systems, or permanently attached outfitting and furnishing objects. Property_context No The context, such as estimated, calculated, maximum, measured or minimum. <xtc:entity name="npd:compartment_volume_permeability_property"> <xtc:definition> A Compartment_volume_permeability_property is a type of General_compartment_property that is a measure, expressed as a percentage of the volume of the compartment, representing open space that is not occupied by equipment, structure, or machinery that would flood in the event the watertight integrity of the compartment was damaged. This is a key parameter for the damage stability calculations for a ship. <xtc:property name="permeability" datatype="npd:percentage"/> <xtc:definition> The permeability specifies the percentage of the total volume of a compartment that is not occupied by the ship structure, systems, or permanently attached outfitting and furnishing objects. <xtc:property name="property_context" datatype="npd:compartment_property_context"/> <xtc:entity_ref eref="npd:general_compartment_property"> <xtc:entity_ref eref="npd:compartment_property"> Imported Entities: PDM Product 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. 2-37

38 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). <!-- PDM --> <xtc:entity name="npd:design_occurrence" abstract="true"> <xtc:entity name="npd:hull_applicability"> <xtc:entity name="npd:ship"> <xtc:entity name="npd:analysis_occurrence"> <xtc:entity name="npd:design_occurrence"> <xtc:entity name="npd:external_classification"> Geometry STEP AP227 (ISO ) 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 airconditioning), 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 , 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 , 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. 2-38

39 <!-- GEOMETRY ENTITIES FROM edo_aic_non_manifold_surface --> Figure SCIM Piping Physical Data Planning Model <xtc:entity name="geometry_schema:bounded_curve"> <xtc:entity name="geometry_schema:curve"> <xtc:entity name="geometry_schema:geometric_representation_item"> <xtc:entity name="representation_schema:representation_item"> <xtc:entity name="edo_508:non_manifold_surface_shape_representation"> <xtc:entity name="geometric_model_schema:face_based_surface_model"> <xtc:entity_ref eref="geometry_schema:pcurve"> <xtc:entity name="geometry_schema:bounded_surface_curve"> <xtc:entity name="geometry_schema:cartesian_transformation_operator_3d"> <xtc:entity name="geometry_schema:curve_replica"> <xtc:entity name="geometry_schema:degenerate_pcurve"> <xtc:entity name="geometry_schema:evaluated_degenerate_pcurve"> <xtc:entity name="geometry_schema:intersection_curve"> <xtc:entity name="geometry_schema:offset_curve_3d"> <xtc:entity name="geometry_schema:offset_surface"> <xtc:entity name="geometry_schema:point_on_curve"> <xtc:entity name="geometry_schema:point_on_surface"> <xtc:entity name="geometry_schema:seam_curve"> <xtc:entity name="geometry_schema:surface_replica"> <xtc:entity name="hsh:shape_representation" > <xtc:entity name="representation_schema:mapped_item"> <xtc:entity name="topology_schema:closed_shell"> <xtc:entity name="topology_schema:connected_face_set"> <xtc:entity name="topology_schema:open_shell"> <xtc:entity name="topology_schema:oriented_face"> <xtc:entity name="geometry_schema:cartesian_transformation_operator"> <xtc:entity name="representation_schema:functionally_defined_transformation"> <xtc:entity name="edo_511:advanced_face"> <xtc:entity name="geometry_schema:geometric_representation_context"> <xtc:entity name="geometry_schema:axis2_placement_2d"> <xtc:entity name="geometry_schema:axis2_placement_3d"> <xtc:entity name="geometry_schema:b_spline_curve_with_knots"> 2-39

40 <xtc:entity name="geometry_schema:b_spline_surface_with_knots"> <xtc:entity name="geometry_schema:bezier_curve"> <xtc:entity name="geometry_schema:bezier_surface"> <xtc:entity name="geometry_schema:cartesian_point"> <xtc:entity name="geometry_schema:circle"> <xtc:entity name="geometry_schema:composite_curve_on_surface"> <xtc:entity name="geometry_schema:conical_surface"> <xtc:entity name="geometry_schema:cylindrical_surface"> <xtc:entity name="geometry_schema:degenerate_toroidal_surface"> <xtc:entity name="geometry_schema:direction"> <xtc:entity name="geometry_schema:ellipse"> <xtc:entity name="geometry_schema:line"> <xtc:entity name="geometry_schema:hyperbola"> <xtc:entity name="geometry_schema:parabola"> <xtc:entity name="geometry_schema:pcurve"> <xtc:entity name="geometry_schema:plane"> <xtc:entity name="geometry_schema:polyline"> <xtc:entity name="geometry_schema:quasi_uniform_curve"> <xtc:entity name="geometry_schema:quasi_uniform_surface"> <xtc:entity name="geometry_schema:rational_b_spline_curve"> <xtc:entity name="geometry_schema:rational_b_spline_surface"> <xtc:entity name="geometry_schema:spherical_surface"> <xtc:entity name="geometry_schema:surface_curve"> <xtc:entity name="geometry_schema:surface_of_linear_extrusion"> <xtc:entity name="geometry_schema:surface_of_revolution"> <xtc:entity name="geometry_schema:swept_surface"> <xtc:entity name="geometry_schema:toroidal_surface"> <xtc:entity name="geometry_schema:uniform_curve"> <xtc:entity name="geometry_schema:uniform_surface"> <xtc:entity name="geometry_schema:vector"> <xtc:entity name="topology_schema:edge"> <xtc:entity name="topology_schema:edge_curve"> <xtc:entity name="topology_schema:edge_loop"> <xtc:entity name="topology_schema:face_bound"> <xtc:entity name="topology_schema:face_outer_bound"> <xtc:entity name="topology_schema:face_surface"> <xtc:entity name="topology_schema:oriented_edge"> <xtc:entity name="topology_schema:path"> <xtc:entity name="topology_schema:vertex_point"> <xtc:entity name="topology_schema:vertex_loop"> <xtc:entity name="representation_schema:definitional_representation"> <xtc:entity name="representation_schema:parametric_representation_context"> <xtc:entity name="geometry_schema:axis1_placement"> <xtc:entity name="geometry_schema:b_spline_curve"> <xtc:entity name="geometry_schema:b_spline_surface"> <xtc:entity name="geometry_schema:bounded_surface"> <xtc:entity name="geometry_schema:composite_curve"> <xtc:entity name="geometry_schema:composite_curve_segment"> <xtc:entity name="geometry_schema:conic"> <xtc:entity name="geometry_schema:elementary_surface"> <xtc:entity name="geometry_schema:placement"> <xtc:entity name="geometry_schema:point"> <xtc:entity name="geometry_schema:surface"> <xtc:entity name="topology_schema:face"> <xtc:entity name="topology_schema:loop"> <xtc:entity name="topology_schema:topological_representation_item"> <xtc:entity name="topology_schema:vertex"> <xtc:entity name="representation_schema:founded_item"> <xtc:entity name="representation_schema:representation"> <xtc:entity name="representation_schema:representation_context"> Measure Some 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. <!-- FROM MEASURE_SCHEMA --> <xtc:entity name="measure_schema:amount_of_substance_measure_with_unit"> <xtc:entity name="measure_schema:amount_of_substance_unit"> 2-40

41 <xtc:entity name="measure_schema:area_measure_with_unit"> <xtc:entity name="measure_schema:area_unit"> <xtc:entity name="measure_schema:context_dependent_unit"> <xtc:entity name="measure_schema:conversion_based_unit"> <xtc:entity name="measure_schema:derived_unit"> <xtc:entity name="measure_schema:derived_unit_element"> <xtc:entity name="measure_schema:dimensional_exponents"> <xtc:entity name="measure_schema:electric_current_measure_with_unit"> <xtc:entity name="measure_schema:electric_current_unit"> <xtc:entity name="measure_schema:global_unit_assigned_context"> <xtc:entity name="measure_schema:length_measure_with_unit"> <xtc:entity name="measure_schema:length_unit"> <xtc:entity name="measure_schema:luminous_intensity_measure_with_unit"> <xtc:entity name="measure_schema:luminous_intensity_unit"> <xtc:entity name="measure_schema:mass_measure_with_unit"> <xtc:entity name="measure_schema:mass_unit"> <xtc:entity name="measure_schema:measure_with_unit"> <xtc:entity name="measure_schema:named_unit"> <xtc:entity name="measure_schema:plane_angle_measure_with_unit"> <xtc:entity name="measure_schema:plane_angle_unit"> <xtc:entity name="measure_schema:ratio_measure_with_unit"> <xtc:entity name="measure_schema:ratio_unit"> <xtc:entity name="measure_schema:si_unit"> <xtc:entity name="measure_schema:solid_angle_measure_with_unit"> <xtc:entity name="measure_schema:solid_angle_unit"> <xtc:entity name="measure_schema:thermodynamic_temperature_measure_with_unit"> <xtc:entity name="measure_schema:thermodynamic_temperature_unit"> <xtc:entity name="measure_schema:time_measure_with_unit"> <xtc:entity name="measure_schema:time_unit"> <xtc:entity name="measure_schema:volume_measure_with_unit"> <xtc:entity name="measure_schema:volume_unit"> <xtc:entity name="representation_schema:global_uncertainty_assigned_context"> <xtc:entity name="representation_schema:uncertainty_measure_with_unit"> Moulded Forms 2-41

42 A moulded form model of the Torpedo Weapons Retrieval ship is illustrated in Figure 1. The model is cut away to reveal the inner structural moulded forms for the decks and bulkheads, which, together with hull forms, constitute the underpinning of the structural ship product model. It should be evident from this illustration that the moulded form model is a simplified and idealized model of the ship. What is less obvious is that there are actually two kinds of model captured by the moulded forms data: one consists of high level parameters that describe the ship and the second consists of the explicit (idealized) surface geometry needed for various analyses. The moulded form model is first used in the earliest concept design stage of the design life cycle. At that time the ship itself and its ship moulded form may be defined by a relatively small number of high level parameters. This makes it possible to determine ship characteristics, at a high level, by analyzing a variety of what-if scenarios and alternate concepts. These parameters are captured as property values attached to the ship and its ship moulded form. In addition, to the pliable parametric model, the moulded form model also consists of the idealized surface geometry for the ship and its major structural components: decks, bulkheads, tanks, appendages. The purpose of this model is to support an array of analyses, such as structural strength, powering and performance, and shock analysis, leading ultimately to a full-ship simulation for shock analysis. The moulded forms model of the ship may be maintained in its own system, but in some ship IPDEs the moulded forms model is maintained through the detailed design phase and manufacturing phase as the underlying surface geometry to which structural parts and design features are added. In the surface model, each physical structural component is modeled as a moulded form item and represented as a non-manifold, face-based surface. Of course, this type of model is not as easy to change as the parametric model, yet it is more flexible than the detailed design model, whose objective is manufacture rather than analysis. Because they constitute different representations of the same ship design the parametric model and the surface representation of the ship must maintain, at the same time, an independence of representation and a consistency of definition. Moreover, the same dual relationship holds between the moulded form model and the detailed design model. 2-42

43 Figure 2 illustrates the entities and properties that comprise the ship moulded form model. The items in the model are indicated in solid blue. They are the ship itself, each moulded form (that is, each physical item that is modeled as a surface), and the ship moulded form (that is, a particular configuration of moulded forms that capture some model of the ship). The high-level parameters, which apply ship-wide, are indicated in the green checkered boxes. The pink striped boxes indicate the properties specific to each individual moulded form. These include not only design parameters but also the face-based, non-manifold surface that represents the geometric shape of the moulded form. In the past the relationship between the moulded form model and the detailed design model has sometimes seemed murky. It has not always been clear which model precedes which, and the detailed design model has occasionally been recruited to serve as the basis of the analysis model. This approach has been hampered because the copious details and features needed for manufacture overwhelm the analysis methodologies, which are looking for simplified and idealized geometric foundations. The following describes the concept of operations of a CAE-centric modeling approach that starts with a moulded form model, maintains it as a constraint and guideline for the detailed design model, and finally employs it as the basis for full-ship analyses and simulations. CAE-centric design: concept of operations The capture, storage, and utilization of ship geometry are essential for today's IPDE processes for collaborative ship design activities across multiple disciplines and during all design stages. At the earliest stages, this begins with definition of ship moulded hull form geometry. As a ship design concept matures, additional attributes (material, plate thickness, etc.) are added to the captured definition. In this use case, this ship representation fosters the creation of various computational analysis and simulation models. Furthermore, this initial representation can be maintained persistently through subsequent design stages to augment evolving detailed CAD and PLM definitions. Engineering analysis models used for computational simulation are employed at various life cycle stages either for "checking" (confirmation) of a design or concept, or for actually "driving" (optimizing) a design 2-43