In How to Use CMPRO for PLM (Part 3) we covered how the Drawing, Document, and Software Release Repositories in CMPRO continue the Product Lifecycle Management Process. After the repository items are created, Baselines can be used to aggregate all of the information of a System and Subsystem in one place. In this issue the when and why of using Baselines in CMPRO is covered.

Baselines

The objective of establishing a baseline is to define a starting point for further system lifecycle process activity and allow reference to, control of, and traceability between configuration items. System program management normally employs three baselines for the validation and acquisition of systems and subsystems: functional, allocated, and production baselines depending on the requirements.

Baseline Modules

There are four baseline modules in CMPRO: Baseline, Product Baseline, As-Built Baseline, and Document Baseline.

1. The Baseline Module, also referred to as the PDM Baseline System, produces a Technical Data Baseline (TDB) based on a defined PD-part tree.  Baselines created in this module include supporting information about assembly level parts and the drawings associated to them. Associated documents and software records supporting component parts are NOT included in the baseline produced from this module.
2. The Product Baseline Module produces a fully indentured baseline that provides hierarchical relationships between all parts that combine to make the top-level assembly product.
3. The As-Built Baseline Module is used to create bills of material (BOMs) templates for product-based applications.  Those templates are used when fabricating an item found in a baseline.
4. The Document Baseline Module is used to represent how related Document Repository items link to one another. This relationship is shown as a document tree.

 

Choose the appropriate baseline by going to the menu and searching for “baseline”. This will display the baseline create, search, and report options.

Baseline Creation Methods

CMPRO offers three different baseline creation methods that have very specific uses:

• The Regularcreation method is the standard baseline creation method, which lists all the documents, drawings, change documents, and software for a system and/or subsystem.
• The Mergecreation method allows you to merge a previous baseline with new baseline data.
• The Product Definition method allows you to generate a baseline based on an existing product definition part tree (PD-Part Tree). Note: This will give you the same results as creating a baseline using the Product Baseline Module.

The Baseline Creation method is an option that is chosen as the first step in the Baseline Create process.

Baseline Types

In the Baseline Module nine different types of baselines can be created, depending on what is required. All of the following types are considered Technical Data Packages (TDP) and only include assembly level parts and drawingsNOT associated documents or software records. The different types to select from are as follows:

1. An Allocated Baseline represents the currently approved performance documentation for the configuration item (CI) to be developed. Documentation included in the baseline should describe the functional and interface characteristics that are allocated from the higher level CI and the verification required to demonstrate achievement of those specified characteristics.
2. A Design/Physical Baseline is a collection of drawings for assemblies and component parts. This type of baseline may also include any documents and software releases required by the physical items represented by the drawings.  The Design/Physical Baseline is the point of departure for all activities in the subsequent phases of the project, leading to fabrication and in-service operation of a system.
3. Development baselines can be established to aid in controlling development lifecycle processes.
4. An Engineering Baseline functions the same as the Design/Physical baseline (above) but is used for programs that specifically require identification of an Engineering Baseline. 
5. An Operational Baseline represents a product or system that is currently on-line and functioning in production.
6. A Functional Baseline consists of the approved documentation that describes the system as defined by top-level products or configuration items included in the functional configuration. This type of baseline normally includes performance characteristics and verification requirements. A functional baseline may also be referred to as a requirements baseline.
7. A Product Baseline for a configuration item is normally established after the successful completion of the Physical Configuration Audit (PCA). This baseline defines any necessary requirements for configuration items or end item products. This baseline must include enough data about the items it contains to facilitate the procurement of all parts included in it at a later date.
8. A Production Baseline serves as a requirement derived from a System Specification and product baseline that has been agreed on by the purchaser.  Any changes in this baseline after the purchaser’s approval must be contractually authorized.
9. A Test Baseline is a temporary baseline that is used to test the feasibility of a baseline configuration.

The Baseline Type is required during the creation process, but can be changed after the baseline is created from the Baseline Detail screen.

Baseline Categories

In the Baseline Module there are two categories under which the baselines may fall:

• A Temporary Baselineis for research and viewing purposes, with the intention of being deleted shortly thereafter.
• A Utilized Baseline is used for managing baseline data, with the intention that it will not be deleted.

The baseline category is a required field in the baseline create process and is chosen from a drop down list. However, the baseline category can later be changed in the Baseline Detail Screen:

Proprietary Groups and Data Visibility

In CMPRO Proprietary Groups affect the visibility of records in baselines.  Although all associated Drawings, Documents, and Software Repository records will be included in a baseline, a given user will only see the details of those records included on the Baseline that have Proprietary Groups assigned to which they themselves belong.

Conclusion

Using the Baseline Modules allows users to report and status on Configuration Items. Baselines further enable the product lifecycle management process by bringing all of the components together for reporting, manufacturing, and maintenance of end items.

This is part four of the series How to Use CMPRO for PLM if you would like to receive updates to this series pleaseSign Up for Our Newsletter.