Software physical configuration audit

Identifying method s of examining the production-representative item e. Ensuring the pre-established review criteria have been met to make sure the production capability forms a satisfactory, affordable and sustainable basis for proceeding with FRP. Ensuring that for software CIs a detailed audit of design documentation, listings and operations and support documents is completed.

Advising the PM on whether production capability forms a satisfactory, affordable and sustainable basis for proceeding into FRP. Ensuring plans to get to FOC allow for contingencies. Ensuring production implementation supports overall performance and maintainability requirements. Monitoring and controlling the execution of the PCA closure plans. Identifying risks associated with meeting program objectives, given the proposed PCA plans.

The Hardware PCA is an examination of the as-built system against its design documentation. Preliminary Operation and Maintenance manuals and red-lined preliminary engineering drawings may be used when appropriate. The hardware PCA may also be conducted incrementally when the contract involves a large system. Privacy policy. This website uses cookies. Click here to find out more. Accept cookies. Approved final draft of the configuration item product specification.

These are precisely the attributes needed to satisfy the ISO series requirements for design verification and design validation as well as the ISO requirement for configuration audit. Configuration verification is a process that is common to configuration management, systems engineering, design engineering, manufacturing, and quality assurance. It is the means by which a contractor verifies his design solution.

The functional aspect of configuration verification encompasses all of the test and demonstrations performed to meet the quality assurance sections of the applicable performance specifications. The physical aspect of configuration verification establishes that the as-built configuration is in conformance with the as-designed configuration. The contractor accomplishes this verification by physical inspection, process control, or a combination of both.

Once the initial configuration has been verified, approved changes to the configuration must also be verified. Figure illustrates the elements in the process of implementing an approved change. Change verification may involve a detailed audit, a series of tests, a validation of operation, maintenance, installation, or modification instructions, or a simple inspection.

The choice of the appropriate method depends upon the nature of the CI, the complexity of the change, and upon the support commodities that the change impacts. If the change is being introduced into a production line, and all future units will have the change incorporated via the production process, it is normally sufficient to ensure that:.

Manufacturing instructions contain the change and are released for use as with a work order , and. However, if support elements are impacted, or the change requires incremental retrofit to many units, complete implementation and verification of the change can be a lengthy process. Under these circumstances, implementation planning must define the extent to which the change to each unit and support commodity is to be verified; and the records to be maintained.

When materials, parts, or retrofit kits are ordered in incremental stages e. Retrofit changes to organically supported items are verified and reported to the Government's status accounting system by the activity given installation and checkout responsibility for the retrofit. Changes retrofit by the contractor for contractor supported items are verified by the contractor. The dictionary definition of the word "audit" as a final accounting gives some insight into the value of conducting configuration audits.

As has been discussed earlier in this handbook, configuration management is used to define and control the configuration baselines for the CIs and the system. In general, a performance specification is used to define the essential performance requirements and constraints that the CI must meet. When a performance specification is baselined by the Government, those requirements are contractual, so it is prudent for the Government to ascertain that the contractor has provided the expected performance capabilities.

For complex systems and CIs, a "performance" audit is necessary to make this determination.