product_breakdown_structure Business Overview

Purpose

This NDLO-DEX shall enable the exchange of data about system/product breakdown structures and their elements. The data are input for configuration management and for engineering, risk, and logistics analysis with focus on requirements allocation and system design, and planning and conduct of support.

Usage

This NDLO-DEX provides input data to manage product risk and configuration through life, for requirements definition and analysis, for architectural design assessment, for maintenance scheduling and resource planning and allocation.

Business DEXs overview

This section provides an overview of the business DEXs.

Zone breakdown

Zone breakdowns are briefly described in the section "Terms".

The figure below describes the zone breakdown of a product. It is divided into several different areas. The number in the parenthesis indicates the capability that is described by the entities in the rectangle.

• The entities in the blue rectangle to the right contain descriptions of the design of the main product (for example the ship). In this particular case it identifies the fleet and is modelled as "part".
• The entities in the green rectangle on the left hand side describe the zone breakdown elements, which constitute the design of the main product.
• The entities in the bottom yellow rectangle describe the breakdown view of the part, in this case a zone breakdown
• The entities in the top orange rectangle describe how individual products (e.g. ships) are linked to different designs and what zone elements pertain to a particular product. For example Zone Y is an element on Ship A, which is of Design X, version 1.2
• The remaining entities in the middle describe how elements in a design may be viewed from different views. For example, all elements related to the electrical design of a ship design can be filtered out and viewed separately.

Figure 1a —  Overview of zone breakdown

Block breakdown

The figure below describes the block breakdown of a product. It is divided into several different areas. The number in the parenthesis indicates the capability that is described by the entities in the rectangle.

• The entities in the blue rectangle to the right contain descriptions of the design of the main product (for example the ship). In this particular case it identifies the fleet and is modelled as "part".
• The entities in the green rectangle on the left hand side describe the block elements (categorised as physical elements), which are part of the design of the main product. The model contains no explicit link between blocks and zones.
• The entities in the bottom yellow rectangle describe the breakdown view of the part, in this case a work breakdown structure based on a "Physical breakdown"
• The entities in the top orange rectangle describe how individual products (e.g. ships) are linked to different designs. and what functional elements pertain to a particular product. For example Block Z is an element on Ship A, which is of Design X, version 1.2
• The remaining entity in the middle describes how elements in a design may be viewed from different views. For example, all elements related to the electrical design of a ship design can be filtered out and viewed separately

Figure 1b —  Overview of block breakdown

Module breakdown

The figure below describes the block breakdown of a product. It is divided into several different areas. The number in the parenthesis indicates the capability that is described by the entities in the rectangle.

• The entities in the blue rectangle to the right contain descriptions of the design of the main product (for example the ship). In this particular case it identifies the fleet and is modelled as "part".
• The entities in the green rectangle on the left hand side describe the module breakdown elements (described as physical elements), which are part of the design of the main product.
• The entities in the bottom yellow rectangle describe the breakdown view of the part, in this case a "Physical breakdown"
• The entities in the top orange rectangle describe how individual products (e.g. ships) are linked to different designs. and what functional elements pertain to a particular product. For example Module Z is an element on Ship A, which is of Design X, version 1.2
• The remaining entity in the middle describes how elements in a design may be viewed from different views. For example, all elements related to the electrical design of a ship design can be filtered out and viewed separately

Figure 1c —  Overview of module breakdown

Work breakdown

A work breakdown structure is a functional decomposition from the project viewpoint of the tasks that are required for a program of work to be a success. It is a means of organizing system development activities based on system and product decompositions. The prime use of the WBS is the design and tracking of work. The WBS is used to establish what work is necessary, a logical decomposition down to work packages and a method of organizing feedback. Work breakdowns may or may not coincide with other types of breakdowns.

The figure below shows the work breakdown structure (WBS) of a product, which is used to enable budgeting, maintenance planning and cost follow-up. The main product is divided into elements, on which costs related to for example maintenance will be registered. The aim of the business function is to link work breakdown elements (in this case functional elements such as propulsion) to an individual parent product. This parent product is in turn linked to a specific design.

• The entities in the blue rectangle to the right contain descriptions of the design of the main product (for example the ship). In this particular case it identifies the fleet and is modelled as "part".
• The entities in the green rectangle on the left hand side describe the functional breakdown elements, which form the design of the main product. These are the elements on which for example costs will be registered
• The entities in the bottom yellow rectangle describe the breakdown view of the part, in this case a work breakdown structure based on a "Functional breakdown"
• The entities in the top orange rectangle describe how individual products (e.g. ships) are linked to different designs. and what functional elements pertain to a particular product. For example Module Z is an element on Ship A, which is of Design X, version 1.2
• The remaining entities in the middle describe how elements in a design may be viewed from different views. For example, all elements related to the electrical design of a ship design can be filtered out and viewed separately

Figure 1d —  Overview of work breakdown

Configuration item

Configuration items identify all configurable items on a ship.

Figure 1e —  DEX 001 Configuration item

Breakdown element realisation

The figure below shows how a breakdown element is realised using physical parts. The blue rectangle on the left side in the figure contains entities describing the breakdown element, whereas the entities in the green rectangle to the right describe the part or parts which are the realisation of the element. Finally, the entity in the orange rectangle describe how the breakdown element is linked to a specific product.

Figure 1f —  DEX 001 Breakdown element realisation

Business functions and rules

This NDLO-DEX is divided into several business DEXs, each supporting various business functions. The table below indicates which functions are available in the different business DEXs. An "x" in the table means that the function is available for the business DEX in question. The following appreviations are used Zone breakdown=Z, Block breakdown=B, Module breakdown=M, Work breakdown=W, Configuration item=C, Breakdown element realisation=BER

Table 0 — Business functions present in different business DEXs

Rules

Model rules - zone breakdown

• A Part_view_definition shall reference two or more View_definition_contexts sharing the same classification
• A Breakdown_element shall have maximum one Ship_zone_code
• A Breakdown_of shall be classified maximum once as Breakdown_for_part_support

Model rules - block breakdown

• A Part_view_definition shall reference two or more View_definition_contexts sharing the same classification
• A Breakdown_element shall have maximum one Ship_block_code
• A Breakdown_of shall be classified maximum once as Breakdown_for_part_support

Model rules - module breakdown

• A Part_view_definition shall reference two or more View_definition_contexts sharing the same classification
• A Breakdown_element shall have maximum one Ship_module_code
• A Breakdown_of shall be classified maximum once as Breakdown_for_part_support

Model rules - work breakdown

• A Part_view_definition shall reference two or more View_definition_contexts sharing the same classification
• A Breakdown_element shall have maximum one Ship_work_breakdown_element_code
• A Breakdown_of shall be classified maximum once as Breakdown_for_part_support

Model rules - Configuration item

• A Part_view_definition shall reference two or more View_definition_contexts sharing the same classification
• A Breakdown_element shall have maximum one Configuration_item_identification_code
• A Breakdown_of shall be classified maximum once as Breakdown_for_part_support

Model rules - breakdown element realisation

• A Part_view_definition shall reference two or more View_definition_contexts sharing the same classification
• A Breakdown_element shall have maximum one Configuration_item_identification_code
• A Breakdown_element_realization shall only be classified as Design_of_configuration_item

© OASIS 2010 — All rights reserved