Capabilities...



Configuration Management

The 3D Research Corporation Configuration Management (CM) process ensures proper configuration identification, configuration change management, Configuration Status Accounting (CSA), configuration verification, and audit support. Our CM process applies technical and administrative direction and surveillance to (1) identify and document the functional and physical characteristics of a Configuration Item (CI), (2) control changes to those characteristics, (3) record and report change processing and implementation status, and (4) demonstrate through formal audits that the plan requirements are fulfilled.

3D Research Corporation establishes and maintains the integrity of the CIs produced within the company. This involves identifying the CIs created during the development and maintenance phases and implementing CM procedures to protect against uncoordinated and unauthorized changes.

Processes are defined within 3D Research Corporation that support development, maintenance, and control of software, hardware, data and documentation to support company activities. In addition, responsibilities, roles, and procedures necessary to meet the requirements for CM practices within 3D Research Corporation are practiced. 3D Research focuses on planning CM activities, identifying the product, controlling changes, and maintaining visibility of the CIs.

3D Research can provide:

• Configuration Control Board
  • Documents the baseline configuration
  • Configuration Control Board (CCB) to approve all modifications and reconfigurations before implementation.
  • The board's charter provides authorization to make any changes to the baseline configuration.
  • As desired changes occur, a Change Request (CR) is generated and processed by the CCB.
  • The CR addresses what will change and all potential side effects of the change.
  • The CCB reviews the CR with all stakeholders to determine if the CR is necessary and grant approval where necessary.
  • Work is performed per the direction of the CCB.
• Baseline/Release Process
  • A Baseline is an approved and released document or set of files comprising a software version that defines a basis for managing change.
  • The Release process is a designation by the originating activity that a document or software version is approved by an appropriate authority and is subject to configuration change management procedures.
  • Responsible for obtaining the proper approvals for documents, drawings, hardware, and software and subsequently releasing them in accordance with the approved company configuration management process.
  • All base lined data shall be subject to configuration control and all changes thereto are submitted through the CCB for approval.
• Configuration Lockdown & Verification
  • Ensures consistent and verifiable results from test line assessment period integration runs.
  • The following must be provided to the Test manager:
    • Access to the original hardware and software baseline.
    • Current, verified integration baseline.
    • An audit trail of all changes to the original baseline hardware and software.
  • All changes prior to test line lockdown will be controlled by the CCB. After test line lockdown, all changes must be coordinated with the Test Configuration Control Board (TCCB) with CCB representation.
  • Configuration verification is accomplished through audits using the As-Built Configuration List.
  • The goal is to establish that the product meets functional and physical requirements and has been accurately represented in the configuration documentation.
  • Each audit or review is documented in an automated system and action items are assigned to address issues or deficiencies, as required.