Configuration management status accounting and the configuration index is the recording activity of configuration management. It is concerned with relating fully approved Change Proposals to drawings, specifications and baselined documents and their issue, and from there to associated parts, for all sections of the specific system. The different baselines provide the foundation for Configuration Management Status Accounting.
Configuration Management Status Accounting and configuration index/matrix records for the project requires that the hardware (HWCIs) and Software (CSCIs) to be confirmed as embodied will always be identical to that shown on the drawings or specifications.
Hardware and Software shall be accounted for by part number within the drawing set of the system for the various Configuration Identification Baselines. This includes, for example, the system, subsystems and its test equipment.
Additionally, software configuration management status accounting during its development, prior to software release, is carried out in accordance with the Computer Software Change Status Procedures as defined in the CMP.
A Change can only be implemented if accompanied by the necessary reporting documentation of the Configuration Control process.
All basic draw alterations will be certified as embodied (incorporated) for the component for which the design authority is responsible and this will be documented to form the initial (Design) Baseline Build Standard for the specific system.
Further alterations beyond basic draw will be documented in the design standard, with embodiment status, etc., added when confirmed.
The Computer Software Configuration Index and Change Status Report shall be prepared in accordance with the Documentation Standard example text i.e., Change status index and Change status report.
The complete Drawing Set and the specifications of the system are held as the basis for Configuration Management Status Accounting.
The drawings for the individual equipments are produced by the suppliers and they are contracted to maintain them to the required Standard. The equipment drawings shall be maintained by the suppliers and only the end-item (product) will be called up on the Master Record Index (MRI) and drawings.
The Design Standard of the system is a definition of what is to be built and is a listing of all basic design authorities (approved drawings, etc.,) for each major component together with all subsequent design change authorities (approved changes, etc.,) for each component to be incorporated.
Each authorized supplier is responsible for the "Design Standard" of the component for which they have the system design responsibility, each supplier listing forms a section of the overall Design Standard (MRI) of the total system.
NOTE: Change Proposals will be listed in the Design Standard as and when they are authorized.
The "Build Standard" is the actual hardware and software standard which has been confirmed as embodied on the major component. The basis for the hardware and software standard to be confirmed are the drawings and specifications which are listed under the Design Authorities listed in the Design Standard.
The Build Standard shall be controlled by the manufacturing department who submits the embodiment information to be accepted, when accepted, will be confirmed as an official embodiment of the component.
The Build Standard may be issued separately but is usually integrated with the Design Standard into the Design Build Standard.
The 'Design Build Standard' is a document which incorporates
both the Design Standard and the Build Standard.
It is an evolving document, for each major component, which records
the design requirements and the embodiment status. The Design
Build Standard is required to be completely up to date at first
trials standard in order that the qualification organization can
submit it as part of the overall documentation for certification
and approval.
Any differences between the Design Requirement and the Build Standard
are highlighted in the document, and may result in limitations
being applied. Such differences are shown in the Design Build
Standard as outstanding activities, which require to be embodied
in order that limitations can be lifted.
The Design Build Standard forms part of the handover documentation
of major components forming the System.
To ensure configuration visibility data/documentation
exchange will be carried out for all approved single Changes,
and all other Changes from inception. This shall be supported
by software tools where possible within industry.
Data/documentation exchange between acquirer and supplier shall
be provided in accordance with the Contractual Data Requirements List
(CDRL), and the reporting requirements defined in the Project
Management System (PMS). For the configuration this shall be supported
by the acquirer access to the Change information, relating to
content and status, on the Database, to a level consistent with
that defined within the PMS, SOW, CDRL, and CMP. By this means,
customer visibility of the situation on Class I and Class II changes
will be realized.
All drawings, Bills of Materials, Specifications,
Acceptance Test Procedures, etc., including subsequent changes,
shall be exchanged within industry. The documents shall be of
reproducible quality in accordance with the 'Documentation Standard'.
When appropriate, in accordance with the Data Requirements List,
System Test Plan, and the provisions of the PMS, such documents
will be delivered to the purchaser.
A revision is defined as a re-issue of a specification
with all the 'Change Requests' and 'Problem/change Reports' since
the last issue (or original issue) incorporated in the revised
specification or deliverable document. A specification or contractually
deliverable document shall not be revised without approval of
the acquirer or his appointed agent. The specification or document
shall not contain the information from any Change Request/Change
Proposal that have not been approved. Details of amendment change
and revision procedure shall be contained in the 'Documentation Standard'.
Note the documentation change procedure is contained in the Documentation Standard Section 3.
The superseded specification or document shall be retained intact with all change pages and CRs and PCRs to provide traceability and continuity of all previous changes.
A verification matrix shall be included in any of the hardware specifications prepared. This matrix will provide for the correlation of the performance requirements (Section 3) with the verification requirements (Section 4). See the attached figure for an example.
Back to Home page
Back to CMP page
Back to Top of this page
For Home page Managing Standards 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