| Business DEX (UK_Defence012):— product_baseline |
Date: 2009/04/16 17:10:09
Revision: 1.3
|
For the purposes of this specification, the following terms apply:
Baseline
A Baseline is a snapshot of the Product Configuration Information at a particular time. This can be for a designated approval
stage, build milestone or for any other reason defined in the Configuration Management Plan. Note: A product Baseline (PBL)
has a distinct role in bringing the product “under ministry control” by the freezing of the engineering post during a Product
Configuration Audit (PCA)
Configuration Item
This information object represents the identification of, and the reference to, an item that is subject to formal Configuration
Management processes throughout its life.
Such processes are typically specified in standards such as DEF STAN 05-57.
Items typically subject to such processes are:
- requirements
- functional, physical and zonal aspects of a product design
- the actual products / assets that are used in-service
- the design of the support concept(s) and support solution(s) associated with the product
- all important reference documents upon which the above information depends or is derived from - such as standards, policies,
plans, contracts etc.
Source
[1]
Common Business Information Structure,
Common Business Information Structure, Issue 3
Configuration Status Record
This concept represents a (type of) record of the status of the related Configuration Items at a point in time.
This is typically used for baselining during the design, manufacture and in-service phases of the product lifecycle.
Source
[1]
Common Business Information Structure,
Common Business Information Structure, Issue 3
Document
This information object represents a permanent statement for preserving the memory or knowledge of facts, activities or events.
Source
[1]
Common Business Information Structure,
Common Business Information Structure, Issue 3
Draft Baseline
A provisional baseline which will change status to a released baseline after it has been authoirized
Source
[1]
Common Business Information Structure,
Common Business Information Structure, Issue 3
Justification
The reasons why a particular option should be selected.
Source
[1]
Common Business Information Structure,
Common Business Information Structure, Issue 3
Product
This information object represents the information about a physical instance of a Product Design.
Individual products are typically identified by a serial number, and batches are typically identified by a batch number. Both
of these would be captured by the referenced Identifier information object
Source
[1]
Common Business Information Structure,
Common Business Information Structure, Issue 3
Product Design
This information object represents the aggregated set of information that constitutes the design of a product.
Product designs can be of any "level" of product, from individual nuts and bolts, up to complete equipments, systems and
platforms.
Product designs are typically identified by a design authority part number, and when fully
specified, will have a detailed drawing/product model associated with them that contain the level of detail that enables instances
of the physical elements of the design to be manufactured and/or assembled. Those physical elements will be fully specified
by their own Product Design.
Product designs will typically also contain performance specifications, physical characteristcs (such as dimensions, weight
and material specifications), and other charateristics such as cost.
Prior to this level of detail being defined, the product design process may involve specification of functions, conceptual
physical design/general layout design and identification of spatial zones within the design.
Source
[1]
Common Business Information Structure,
Common Business Information Structure, Issue 3
Product Specification
This information object represents the specification of a type of product in terms of its functional and/or physical characteristics.
A product specification does not contain the level of detail neccessary in order to manufacture and / or assemble a product
that meets the specification. That level of detail is only provided by a product design.
Typical Product Specifications are those defined by each NATO stock number classification, and those defined by industry standards
specifications for items such as nuts, bolts, tyres, etc.
Several Product Designs by individual design authorities may meet the requirements of a Product Specification.
roduct specifications can be referred to by the elements of a Product Design as well as/instead of an individual Product Design,
depending on the item in question.
OTE: The characteristics that define a Product Specification are defined by the Property information object.
NOTE: The document(s) that define a Product Specification are defined by the Document Association information object.
Source
[1]
Common Business Information Structure,
Common Business Information Structure, Issue 3
Record
This information object represents a permanent statement for preserving the memory or knowledge of facts, activities or events.
Source
[1]
Common Business Information Structure,
Common Business Information Structure, Issue 3
Released Baseline
The authorised baselines that have been released.
The system development process shall ensure that top-level requirements are accounted for in lower level records and that
the traceability of requirements allocation is readily demonstrable. This means that all baselines will be mutually consistent
and compatible, and that each level of PCI is a logical extension of its predecessors.
Update of baselines is accomplished via the CM interrelated sub-process of Configuration Change Management.
Source
[1]
Common Business Information Structure,
Common Business Information Structure, Issue 3
Updated Baseline
Incorporation of the change into the PCI.
Source
[1]
Common Business Information Structure,
Common Business Information Structure, Issue 3
Additional terms used in the Help/Information pages.
NOTE These terms are not part of the released specification.