# Configuration Management

The product and component is done on screens:

- Products
- Components
- Product Versions
- Component Versions
- Versions planning

## Products

Allows to define product and sub-product.

Allows to link components to product.

Section: Description

Field | Description
--- | ---
Id | Unique Id for the product.
Name | Name of the product.
Product type | Type of product.
Designation | Trade name of the product known outside the company.
Customer | The customer the product should be delivered to.
Prime contractor | The contact, into customer organization, who will be responsible for the product delivery.
Responsible | Person responsible for the product.
sub-product | Name of the top product if this product is a sub-product.
Status | State to be registered.
Closed | item is closed if checked
Description : | Box checked indicates the product is archived.

* Required field

Section: Product versions

- List of versions defined for the product.
- Product versions are defined in Product Versions screen.

Section: Composition - List of sub-products used by this product

- List of sub-products for the product.

Section: Composition - List of components used by this product

- See: Relationships between product and component elements.

Button: Display structure

- Displays the structure of the product.
- Box checked “Show versions for all structure” allows to display versions of sub-products and components.
- Box checked “Show projects linked to versions” allows to display projects linked.

## Product Versions

Allows to define versions of a product.

Allows to link a component version to product version.

Allows to link the product version to a project.

Ability to define the compatibility between product versions (feature activated through a global parameter)

Automatic formatting of version name

- Possibility to define if the version name is automatically produced from the product name and version number.
- Set global parameters to activate this feature.
- Else, the version name will entered manually.

Section: Description

Field | Description
--- | ---
Id | Unique Id for the version.
Product | The product on which the version applies.
Version number | Version number of the product.
Name | Name of the version.
Prime contractor | The contact, into customer organization, who will be responsible for the version delivery.
Responsible | Resource responsible of the version.
Entry into service | Initial, planned and real entry into service date of the version.
End date | Initial, planned and real end dates of the version.
Status | State to be registered
Description | Complete description of the version.

* Required field

Fields: Version number & Name

- The field “Version number” appears only if the global parameter “Automatic format of version name” is set to Yes.
- The field “Name” will be read only.

Field: Prime contractor

- Can be different from product prime contractor.

Field: Entry into service (Real)

- Specify the date of entry into service.
- The box “Done” is checked when the real date field is set.

Field: End date (Real)

- Specify the date end-of-service.
- The box “Done” is checked when the real date field is set.

## Components

Allows to define product components.

Allows to define products using the component.

Possibility to define component types and component versions that will only be used for definition of structure (not for Version Planning or Tickets)

Section: Description

Field | Description
--- | ---
Id | Unique Id for the component.
Name | Name of the component.
Component type | Type of component
Identifier | Another name to identify the component.
Responsible | Person responsible for the component.
Statut | State to be registered
Closed | Box checked indicates the component is archived.
Description | Complete description of the component.

* Required field

Section: Component versions

- List of versions defined for the component.
- Component versions are defined in Component Versions screen.

## Component Versions

Allows to define versions of a component.

Allows to link a product version to component version.

Automatic formatting of version name

- Possibility to define if the version name is automatically produced from the component name and version number.
- Set global parameters to activate this feature.
- Else, the version name will entered manually.

Section: Description

Field | Description
--- | ---
Id | Unique Id for the version.
Component | The component on which the version applies.
Version number | Version number of the component.
Name | Name of the version.
Entry into service | Initial, planned and real entry into service date of the version.
End date | Initial, planned and real end dates of the version.
Statut | State to be registered
Description | Complete description of the version.

* Required field

Fields: Version number & Name

- The field “Version number” appears only if the global parameter “Automatic format of version name” is set to Yes.
- The field “Name” will be read only.

Field: Entry into service (Real)

- Specify the date of entry into service.
- The box “Done” is checked when the real date field is set.

Field: End date (Real)

- Specify the date end-of-service.
- The box “Done” is checked when the real date field is set.

## Relationships between product and component elements

Allows to manage relationships between products and components to define product structure.

See possible relationships: Product structure

Relationships management

- Click on to create a new relationship. The dialog box “Structure” appear.
- Click on to delete the corresponding relationship.

## Link between versions of products and components

Allows to define links between versions of products and components.

Note

- Only with the elements defined in the product structure.

Link management

- Click on to create a new link. The dialog box “Version Structure” appear.
- Click on to delete the corresponding link.

## Link version to projects

This section allows to manage links between projects and versions of products.

Link version to projects management

- Click on to create a new link.
- Click on to update an existing link.
- Click on to delete the corresponding link.

Fields - Project-Version link dialog box
Field | Description
--- | ---
Project | The project linked to product version or the project list.
Product | Product linked to the project or the list of products.
Version | Product version linked to the project or list of product versions.
Start date | Start date for validity of the link.
End date | End date for validity of the link.
Status | State to be registerd
Closed | Box checked indicates the link is not active anymore, without deleting it.

Fields: Project, Product and Version

- From the screen «Projects», the fields «product and version» will be selectable.
- From the screen «Product versions», the field «project» will be selectable.

## Versions planning

Select one or more product versions and the planning version is displayed.

This planning displays each version of selected product versions and their components from define start date to deliverable date.

To use it define your start and delivery date in Product Version and Component Version.

Note

- To insert values you have to Actives ‘display the start and delivery milestones’ in global parameters otherwise these fields are hidden.

This screen allows to see if the delivery date of Component versions is more later than their Product versions.

Graphically, you can see any delay or incompatibility.