January 16, 2012

Product Tree - M-5

Break the product down into the management parts

A. Scope

The product tree gives a comprehensive breakdown of the product into hardware and/or software elements.

It is a key structure in the management of a project.

The tree diagram in fact identifies the interfaces to consider in the design and production of the expected product or system. The product tree represents the definition of the product or system and its components. It also serves as a basis for drawing up the Management Plan for Documentation and Configuration (see M-9) and the Definition File (see E-4) of the product, and establishing costs and schedules.

This section is based on the CNES Standards Reference (RNC) document "RNC-CNES-M-HB-10-501 Construction de l'organigramme des tâches".

B. Fundamentals

The product tree is initialised during phase A and continually develops during the definition process. It is consolidated at the end of phase B.

It is worked out from the functional breakdown, which itself comes from the internal functional analysis of the product.

1. Functional breakdown

Drawn up from the expected functions of a product or of a system and the constraints identified in the Functional Performance Specification, the functional breakdown allows a tree diagram of its functions to be specified.

With every identified function is linked a hardware concept that will allow this function to be performed.

The tree representation of the results of this analysis is the function tree.

2. Product Tree

All the product constituents are derived from the functional breakdown.

The breakdown into hardware and/or software subassemblies constitutes the product tree.

The product tree has a top (level 0) representing the final product, supporting the function performed by the system, and successive levels breaking down into the hardware or software elements.

This tree structures the product or the system into constituents considered to be significant and shows the compositional links existing between elements in level "n" and those of level "n-1".

In the first part of the development V cycle (during phases A, B and C), the system is broken down into sub-systems which may be specified, produced and tested individually. For every contract, the breakdown will be carried out until the appropriate level (namely the level of an element supplied by a partner or a subcontractor).

Every element of the Product Tree is identified by a code:

  • the top has code 0,
  • the elements of the first level have codes 1,..., n,..., N,
  • the first breakdown level of element n has code n1,..., nx,
  • the first breakdown level of element n1 has code n11,..., n1y,
  • etc.

 

gns_uk_m5.jpg

 

Risks

RisksComplex international cooperation outline
Multiple interfaces
 RecommandationsDEFINE THE SHARING OF RESPONSIBILITIES
Project organisation note
BREAK PRODUCT DOWN INTO MANAGEABLE ITEMS
Product Tree
BREAK PRODUCT DOWN INTO BASIC TASKS
Task Flowchart
RisksDiscrepancies between documentation and equipment
Lack of knowledge of changes and modifications
Non-representativeness of models
Uncontrollable unauthorised modifications
 RecommandationsIDENTIFY THE PRODUCT COMPONENTS
Product Tree
IDENTIFY AND CONTROL THE CONFIGURATION
Configuration Management Plan (PGC)

 

Activities / documentation

Published in: