In Netscape use the right mouse button to expand the figure.
FIGURE 1. Configuration Management Organization.
Configuration management is defined as part of the Project Management System required for the technical and administrative direction and surveillance of the project and operates on several conceptual levels:
Configuration management relationship to the project/program management structure is illustrated in figure 1.
In Netscape use the right mouse button to expand the figure.
FIGURE 1. Configuration Management Organization.
Configuration management is a discipline to ensure the proper identification of the configuration, to control changes, and to record the change implementation status of the physical and functional characteristics of the structure; system/subsystem, HWCIs, CSCIs and equipment.
Configuration Management identifies what is required, designed, and produced, evaluating changes including effects on technical and operational performance and integrated logistic support (ILS) activities. It will also provide visibility of the configuration.
At the start of the 'Engineering and Manufacturing Development' phase, information will be provided to the Acquirer (customer) in accordance with the 'Data Requirements List' as defined in the 'System/subsystem Specification(s)' or 'Statement of Work' in order to ensure this visibility of the required configuration.
Configuration management will be performed down to the lowest removable part and is limited to end-items only.
Configuration management covers three basic essential interdependent activities:
These activities will be described in more detail in the following sections.
Configuration management is therefore the means through
which integrity and continuity of the design, systems engineering
and cost trade-off decisions made between technical performance,
producibility, operability, and supportability are recorded, communicated,
and controlled by project managers.
In support of these activities, Formal Configuration Audits will
be performed for HWCIs and CSCIs) for compliance with baseline
specifications. They will be performed by suitably qualified personnel
from the developer and acquirer who will certificate the components
and inform configuration Management of the outcome.
In accordance with the 'Project Management System', it is a firm objective that this 'Configuration Management Plan' shall apply through all the system life cycle phases of the program (project) starting with the 'Engineering and Manufacturing Development' phase through to the 'Production and Deployment' phases.
This plan shall contain the overall policies, principles, and objectives, precise methods (procedural data) shall be defined within detailed suppliers Configuration Management Plans/procedures documents and will be in accordance with this plan.
Corresponding with these procedures, appropriate baselines and build standards will be established, starting with the Configuration identification at the start of development and will include standards for each prototype and production item.
For the CSCIs during the "Engineering and manufacturing development phase" software configuration management will be identified and defined within a 'Software Development plan' or an optional 'Software Configuration Management plan', which will be fully compatible with this CMP. Once becoming available for release to the system, (that is, successful completion of the System PCA) the developed CSCI will be subject to the change methods and procedures outlined in this CMP.
For Class I changes the customer will receive "Change Proposals" using the Change reports defined in Section 5.
For Class II changes the customer will receive status reports in accordance with the documents defined in Section 5.
The following documentation and information will be made available:
While the acquirer (purchaser) or his agent has overall responsibility for all aspects of Configuration Management, in accordance with its agreement with the customer, each participating company is responsible for the major component documentation for which they are contracted to build as defined in the "Statement of Work", under technical responsibility allocations.
It is the responsibility of that company to produce and maintain a Design Build Standard for the major component which will be delivered to the final assembly location, as part of the handover documentation.
It is also the authorized suppliers responsibility to maintain the Design Build Standard of the major component thereafter, to information supplied by the final assembly site. This is necessary in order that the final assembly company can prepare the total Design Build Standard.
Configuration documentation shall be provided in either hard copy data transfer, transfer of processable data files, interactive access to data through contractor integrated technical information services, or a combination of the above, as specified by the contract.
A distribution statement in accordance with the 'Documentation Standard' shall be affixed to all data items. Access to the data will be limited in accordance with the applicable distribution statements as well as by data rights, CDRL distribution, security requirements, and data status level (released, submitted, or approved unless otherwise specified). This statement will be in accordance with the 'Documentation Standard'.
When required, data may be provided in an electronic format version of the form. Textual data in electronic form shall be by paragraph number, or topic heading, as applicable, in accordance with the format and content requirements for the data specified in the contract.
When specified access to the integrated technical information service shall accommodate pre-defined query and extraction of data.
Back to Home page
Back to CMP page
Back to Top of this page
For Home page MANAGING STANDARDS home page
kenr@wysywig.airtime.co.uk
Originated on the 17th of July 1995
Please send any beneficial comments or identification of errors
using the following form to: kenr@wysywig.airtime.co.uk