FORM # LAT-FS-0012-02 LAT Project Office – SLAC DCN No. LAT-XR-1829-01 DOCUMENT CHANGE NOTICE (DCN) SHEET 1 OF 1 ORIGINATOR: Dick Horn PHONE: 650-926-8578 DATE: 3/17/03 CHANGE TITLE: DCN for LAT Configuration Management Plan ORG.: DOCUMENT NUMBER TITLE NEW REV. LAT-MD-00068 LAT Configuration Management Plan 01 CHANGE DESCRIPTION (FROM/TO): Initial release REASON FOR CHANGE: ACTION TAKEN: Change(s) included in new release DCN attached to document(s), changes to be included in next revision Other (specify): DISPOSITION OF HARDWARE (IDENTIFY SERIAL NUMBERS): DCN DISTRIBUTION: No hardware affected (record change only) List S/Ns which comply already: List S/Ns to be reworked or scrapped: List S/Ns to be built with this change: List S/Ns to be retested per this change: SAFETY, COST, SCHEDULE, REQUIREMENTS IMPACT? YES NO If yes, CCB approval is required. Enter change request number: APPROVALS DATE OTHER APPROVALS (specify): DATE ORIGINATOR: D. Horn (signature on file) 3/17/03 Principal Investigator- P. Michelson (Bill for Peter) 3/26/03 ORG. MANAGER: L. Klaisner (signature on file) 3/17/03 Project Manager- B. Althouse (signature on file) 3/26/03 P&SA- D. Marsh (signature on file) 3/18/03 Project Controls- T. Boysen (signature on file) 3/31/03 I&T- E. Bloom (signature on file) 3/31/03 Instrument Scientist- S. Ritz (signature on file) 3/17/03 DCC RELEASE: Natalie Cramar (signature on file) 3/31/03 Doc. Control Level: Subsystem LAT IPO GLAST Project
Transcript
FORM # LAT-FS-0012-02
LAT Project Office – SLAC
DCN No. LAT-XR-1829-01
DOCUMENT CHANGE NOTICE (DCN) SHEET 1 OF 1
ORIGINATOR: Dick Horn PHONE: 650-926-8578 DATE: 3/17/03
CHANGE TITLE: DCN for LAT Configuration Management Plan ORG.: DOCUMENT NUMBER TITLE NEW REV.
LAT-MD-00068 LAT Configuration Management Plan 01
CHANGE DESCRIPTION (FROM/TO): Initial release
REASON FOR CHANGE:
ACTION TAKEN: Change(s) included in new release DCN attached to document(s), changes to be included in next revision Other (specify):
DISPOSITION OF HARDWARE (IDENTIFY SERIAL NUMBERS): DCN DISTRIBUTION:
No hardware affected (record change only)
List S/Ns which comply already:
List S/Ns to be reworked or scrapped:
List S/Ns to be built with this change:
List S/Ns to be retested per this change:
SAFETY, COST, SCHEDULE, REQUIREMENTS IMPACT? YES NO If yes, CCB approval is required. Enter change request number:
APPROVALS DATE OTHER APPROVALS (specify): DATE
ORIGINATOR: D. Horn (signature on file) 3/17/03 Principal Investigator- P. Michelson (Bill for Peter) 3/26/03
ORG. MANAGER: L. Klaisner (signature on file) 3/17/03 Project Manager- B. Althouse (signature on file) 3/26/03
P&SA- D. Marsh (signature on file) 3/18/03 Project Controls- T. Boysen (signature on file) 3/31/03
I&T- E. Bloom (signature on file) 3/31/03
Instrument Scientist- S. Ritz (signature on file) 3/17/03
DCC RELEASE: Natalie Cramar (signature on file) 3/31/03 Doc. Control Level: Subsystem LAT IPO GLAST Project
LAT-MD-00068-01 LAT Configuration Management Plan Page 1 of 19
Document # Date Effective
LAT-MD-00068-01 3/17/03 Prepared by(s) Supersedes
Dick Horn None Warren Davis
Subsystem/Office GLAST LAT PROJECT MANAGEMENT PLAN System Engineering
Document Title
LAT Configuration Management Plan
Gamma-ray Large Area Space Telescope
(GLAST)
Large Area Telescope (LAT)
Configuration Management Plan
LAT-MD-00068-01 LAT Configuration Management Plan Page 2 of 19
CHANGE HISTORY LOG Revision Effective Date Description of Changes DCN #
1 3/17/03 Initial Release LAT-XR-01829-01
LAT-MD-00068-01 LAT Configuration Management Plan Page 3 of 19
LAT-MD-00068-01 LAT Configuration Management Plan Page 4 of 19
1 Purpose This Configuration Management Plan (CMP) describes the configuration management
(CM) responsibilities and processes that support the design and implementation of the GLAST Large Area Telescope (LAT). The purpose of this CMP is to identify the organization providing the configuration control, define what a configuration-controlled item is, describe the change control process, and identify the plan for configuration status accounting and verification.
This CMP is designed to ensure that:
a. Baselines are defined and documented
b. Documentation is identified, released and controlled
c. The Configuration Control Board (CCB) is established and functions according to CMP guidelines
d. Changes to the baseline are evaluated and controlled
e. Approved configuration changes are implemented and tracked
f. Configuration status accounting is accomplished
2 Scope This CMP is applicable to all work performed as part of the LAT project, which includes
the design, integration and test of the Science Instrument and the Instrument Operations Center. It provides guidance for all personnel on CM activities in support of the LAT project, including all subsystem teams and subcontractors. CM is applied to items selected by the Project Manager and includes hardware and software components along with the related design documents, specifications, drawings, procedures and other support documents. The scope of this CMP encompasses the lifecycle of the LAT project.
3 Definitions
3.1 Acronyms CCB – Configuration Control Board
CI – Configuration Item
CIDL – Configuration Items Data List
CM – Configuration Management
CMP – Configuration Management Plan
CR – Change Request
DCN – Document Change Notice
GLAST – Gamma-ray Large Area Space Telescope
GSFC – Goddard Space Flight Center
ICD – Interface Control Document
LAT-MD-00068-01 LAT Configuration Management Plan Page 5 of 19
IOC – Instrument Operations Center
IPI – Instrument Principal Investigator
IPM – Instrument Project Manager
ISE – Instrument System Engineering Manager
LAT – Large Area Telescope
PCM – Project Controls Manager
RPE – Responsible Product Engineer
3.2 Definitions Allocated Baseline – The LAT Project-approved documentation detailing the subsystem-
level functional and design requirements.
Baseline – An arbitrary point at which a project design or requirements are considered to be “frozen” and after which all changes must be tracked and approved.
Change Classification - All proposed changes to LAT Project documentation submitted to the CCB for consideration are designated as Level 1, 2, 3 or 4 changes. Configuration changes may affect hardware, software, verification requirements and the documents, drawings and procedures which define them.
Configuration Control Board (CCB) – A board composed of technical and administrative representatives who recommend approval or disapproval of proposed changes or deviations and waivers to a CI’s current approved configuration documentation.
Configuration Item (CI) – An aggregation of hardware or software that satisfies an end use function and is designated for separate CM.
Configuration Items Data List (CIDL) – A LAT Project-controlled database that identifies all CIs and contains tracking and status information for changes to the CIs.
Configuration Management (CM) – The systematic control and evaluation of all changes to documentation that has reached a baseline point.
Functional Baseline – The LAT Project-approved documentation detailing the functional requirements of the LAT system as a whole.
Product Baseline – The LAT Project-approved documentation that completely defines the CIs at the time of production.
4 Applicable Documents The following documents are applicable to the development or implementation of this
CMP:
“GLAST Large Area Telescope Flight Investigation: An Astro-Particle Physics Partnership Exploring the High-Energy Universe”, proposal to NASA, P. Michelson, PI, November, 1999
MD-00054-08 LAT Project Management Plan
MD-00066-01 LAT System Engineering Management Plan
LAT-MD-00068-01 LAT Configuration Management Plan Page 6 of 19
DS-01687-01 Configuration Item Data List
433-PROC-0001 GLAST Project CM Procedure
5 Overview CM is the process through which the LAT Project documents the functional and physical
characteristics of the instrument and the IOC, controls changes to those characteristics, and provides information on the state of change action. The key elements of CM, as shown in Figure 1, are Configuration Identification, Configuration Change Control, Configuration Status Accounting, and Configuration Verification.
Configuration Identification defines the LAT system through drawings and documents that
specify the system components in terms of functional and physical characteristics, as well as how they will be manufactured and tested. For convenience, the LAT system is broken down into Configuration Items (CIs). The CIs are listed in a Configuration Items Data List (CIDL), which is a database that lists each CI and its defining documentation. The CIDL is also used to track proposed changes to CIs. The Change Control process is the vehicle by which proposed changes are reviewed and approved. It ensures that the technical, cost and schedule impacts of each major change are considered before approval is granted. Configuration Status Accounting is a means to track configuration information and relay it to key personnel in order to support management decisions and ensure that all work is performed according to the current design. The Configuration
Figure 1: LAT Project Configuration Management
Configuration Identification
Configuration Change Control Configuration Verification
Configuration Status Accounting
Baseline Documents
CI SelectionOnline Access
by LAT Team
Proposed Change
Change Approval
(Manager or CCB)
CIDL
Online Access for Status Reporting and Real-Time Inquiries
Change Verification
Configuration Audits
LAT-MD-00068-01 LAT Configuration Management Plan Page 7 of 19
Verification process ensures that the current hardware and software configurations match the intended design by verifying the implementation of each approved change and through periodic configuration audits.
CM is the responsibility of the Project Office (IPO) and must be supported by all LAT team members. Figure 2 shows the organization of the LAT Project. The Project Manager (IPM) has the overall responsibility for CM. The IPM is responsible for ensuring that all project CIs are
identified and controlled. The Instrument System Engineering Manager (ISE) is responsible for technical oversight and coordination of project configuration control activities. The Project Control Manager (PCM) is responsible for Configuration Control Board (CCB) administration activities and implementing approved changes to the project cost and schedule baselines. The Subsystem Managers maintain CM control over their Class III change control areas of responsibility, including subcontracts.
Figure 2. LAT Project Organization
System Engineer (ISE) SLAC
Integration & TestSLAC
Mech. Systems SLAC
Project Controls SLAC
Performance & SafetyAssurance
SLAC
Principal Investigator (IPI) SU
Project Manager (IPM)SLAC
Chief EngineerSLAC
Sci. SoftwareSLAC
IOC SU
CALNRL, France,
Sweden
TKR UCSC, SLAC,
Italy, Japan
ACDGSFC
Instrument Scientist GSFC
E/PO SSU
SSACGSFC
CollaborationScience Team
Electronics & DAQSLAC
IPO
ConfigurationManagement
LAT-MD-00068-01 LAT Configuration Management Plan Page 8 of 19
Figure 3 provides the hierarchy of LAT Technical requirements and level of change control.
Figure 3: Technical Requirements
Figure 4 provides the hierarchy of LAT Program Management Plans and level of change control.
LAT-MD-00068-01 LAT Configuration Management Plan Page 9 of 19
System EngineeringManagement PlanLAT-MD-00066-01
A
Project ManagementPlan
LAT-MD-00054-08 A
Work BreakdownStructure
LAT-MD-00033-06
PerformanceAssurance
Implementation PlanLAT-MD-00039-01
A
Risk ManagementPlan
LAT-MD-00067-03 A
ConfigurationManagement PlanLAT-MD-00068-01
A
LAT ScienceVerification Analysis
Calibration PlanLAT-MD-00446-04
A
LAT InstrumentVerification Plan
LAT-MD-00408-01
GLAST LAT QualityManual
LAT-MD-00091-01
LAT EEE PartsProgram Control Plan
LAT-MD-00099-03
LAT EEE PartsProgram Control Plan
LAT-MD-00099-03 A
GLAST LAT S/WManagement PlanLAT-MD-00104-02 A
A- Approved by GSFC/GLAST Project Managers & DOE Federal Project Managers
Figure 4: Level of Change Control
LAT-MD-00068-01 LAT Configuration Management Plan Page 10 of 19
6 Configuration Management Process and Responsibilities Configuration Management responsibilities are described in Figure 5.
GLAST Project Office433-PROC-0001
LAT ConfigurationManagement
LAT-MD-00068-01
Spectrum Astro
TrackerSLAC/UCSC
LAT-MD-00068-01
ACD/GSFCLAT-MD-00845-01
CAL/NRLLAT-MD-01486-01
LAT CM
Major Supplier CM
Italy France
Figure 5: Configuration Management Hierarchy
LAT-MD-00068-01 LAT Configuration Management Plan Page 11 of 19
The Goddard Space Flight Center (GSFC) Project Office maintains CM of all non-LAT specific Level II System Documents defined in the LAT System Engineering Management Plan (LAT MD-00066-01) utilizing GSFC Procedure 433-PROC-0001.
The LAT Instrument Performance Specification (LAT-SS-00010) and IOC Performance Specification (LAT-SS-00020) are maintained within the LAT CM procedures defined herein.
Central LAT CM of all Level III documents are maintained within the SLAC/LAT CM library utilizing the processes defined herein.
Products below level III developed by SLAC & UCSC are maintained within the SLAC/LAT CM library.
Products developed by the supporting collaborators indicated utilize internal CM processes. Coincident with delivery to SLAC of the collaborator’s CI, all level 4 specifications and assembly level drawings associated with the CI shall be transferred to the SLAC/LAT CM library and become subject to the control of this CM plan.
The CM process consists of four ongoing stages: (1) configuration identification, (2) change control, (3) configuration status accounting, and (4) configuration verification.
6.1 Configuration Identification Configuration identification is the ongoing process of identifying and documenting the LAT
system’s functional and physical characteristics, from initial requirements selection through design, development, fabrication, test, and delivery. Configuration identification provides unique identity to LAT system components as well as the configuration documentation.
6.1.1 Baseline Definition The configuration identification is developed and maintained in a series of IPO-approved
baseline configurations as follows:
The Functional Baseline is the initially approved documentation describing the LAT system’s top-level functional characteristics and the verification required to demonstrate the achievement of those characteristics. The LAT functional baseline was established after the System Requirements Review (SRR).
The Allocated Baseline is the formal definition of the LAT system, subsystems, software, and equipment while further defining the performance requirements from the Functional Baseline documentation. This baseline specifies the requirements that will be used to design the system. The Allocated Baseline was established after completion of the Preliminary Design Review (PDR).
The Product Baseline is the formal design of the LAT system. This baseline contains the manufacturing drawings, procedures, and specifications that will be used to build the system. The Product Baseline is established upon completion of a pre-production audit of the design documentation in conjunction with the Critical Design Review (CDR).
6.1.2 Configuration Items In order to facilitate CM, the LAT system will be broken down into manageable units,
called Configuration Items (CIs). CIs are selected through a top-down system decomposition process that divides the total system into logically related and subordinate aggregates of hardware
LAT-MD-00068-01 LAT Configuration Management Plan Page 12 of 19
and/or software. The main criteria is to select those items whose performance parameters and physical characteristics can be separately defined, tested and managed.
6.1.3 Configuration Items Data List All CIs will be listed in a Configuration Items Data List (CIDL). The CIDL is a database
containing relevant information about each CI, such as item number, title, revision history, responsible organization, release date, baseline code, and relation to higher-level and lower-level CIs. The CIDL will also identify the documents that define the CI. These documents are controlled through CM and may include, but are not limited to, specifications, drawings, interface control documents (ICDs), software description documents, databases, and procedures.
Where the LAT design incorporates commercial off-the-shelf (COTS) hardware or software, the vendor part number will be used in LAT drawings and specifications, but the design data and documentation owned by the vendor is not subject to LAT CM.
6.1.4 Documentation and Part Numbers Documentation and part numbers are obtained from the LAT CM System.
6.1.5 On-Line Documentation The CIDL is controlled by the ISE and will be available to all LAT personnel through read-
only on-line access. Additionally, all baseline documentation will be available on-line. This will enable all team members to obtain and verify the latest approved version of controlled documents.
6.2 Change Control Change control is the process by which the LAT Project Office manages and approves the
release and update of configuration-controlled items.
6.2.1 Initial Release Drawings and documents are placed under configuration control upon their initial release.
Prior to initial release, the originator should submit the item to peer or expert review, as applicable. Initial release is accomplished by submitting a completed and approved Document Change Notice (DCN) to the project configuration management. The project CM group enters the item in the SLAC document tracking system and the ISE enters the item in the CIDL if appropriate. The CM coordinator distributes the DCN to the LAT team.
6.2.2 Change Control Process Updates to released documents are accomplished through the change control process. This
process is used to classify proposed changes and manage the approval process accordingly. All proposed changes are assigned a classification of Level 1, Level 2, Level 3, or Level 4 based on the level of impact to the overall system (see level definitions Figure 7). Figure 6 shows a graphic representation of the change control process.
The change control process is started when a need for change is identified and the Responsible Product Engineer (RPE) submits a Change Request (CR) to his/her Subsystem Manager for approval. Level 4 changes are managed and controlled at the subsystem level. The DCN is used to inform the rest of the LAT team of approved changes and to alert the ISE to update
LAT-MD-00068-01 LAT Configuration Management Plan Page 13 of 19
the CIDL. If the RPE and Subsystem Manager determine that the proposed change requires CCB approval, then the Change Request (CR) is sent to the LAT Project Office. Prior to the CCB meeting, the ISE conducts an informal screening to make sure the CR is complete and accurate. The ISE may request additional support documentation, reports and/or analyses for the CCB presentation. The CCB then evaluates the CR and recommends that it be approved or rejected. The IPM will approve or reject the change once concurrence is obtained from the board members. Level II changes are then sent to GSFC for approval by the GLAST Project Office.
When the appropriate level of approval has been granted the CR form is routed to the ISE and copies are distributed to the LAT team. The approved CR directs the LAT team to implement the change. Upon completion of a document change, a DCN is produced by the RPE and routed by the CM coordinator for final verification review, upon review the DCN and associated document are released within the LAT CM library.
The change control process may be accelerated, if required, to accommodate urgent change requests. In urgent situations, an emergency CCB meeting is convened, consisting of the CCB chairperson and his designated participants. An informal change request is presented and evaluated. Action items may be identified and verbal approval granted contingent on the action items. A formal CR and DCN must be submitted later to receive formal approval and to be entered in the CIDL for tracking.
Impact to requirements, cost,
schedule?
NO Need for Change
Identified
Level 4 change. Change is implemented and
DCN is distributed to LAT team.
RPE submits Change Request (CR) for manager approval.
YES
Level 2 or 3 change. RPE submits a Change Request
(CR) for CCB screening.
CR is sent to the Configuration Control Board for approval.
GSFC approval required?
YES, Level 2
CR is sent to GSFC for approval.
If approved, the change is implemented and the CR and DCN
are distributed to the LAT team.
NO, Level 3
Figure 6: Change Control Process
6.2.3 Document Change Notice A Document Change Notice form (Appendix, form A1) is used to notify the LAT team that
an approved change has been implemented. The DCN will also announce the first release of a new
LAT-MD-00068-01 LAT Configuration Management Plan Page 14 of 19
document or the document revision which has incorporated previously approved DCNs. New document revisions must be released when the current revision has six or more attached DCNs.
6.2.4 Change Request Form The Change Request form (Appendix, form A2) is used to submit a proposed change to a
released document. The CR provides the Subsystem Manager and CCB (as appropriate) with information about the technical performance, cost and schedule impacts of the proposed change.
6.2.5 CCB Operations The CCB is primarily responsible for reviewing all Level 2 and Level 3 CR’s for merit
based on the impact to LAT cost, schedule and technical performance. The CCB may also be called on to evaluate and approve or reject GSFC-initiated change requests and subcontractor requests for deviation or waiver.
Once baseline configuration items are established, the Configuration Control Board (CCB) will manage requests for changes to system-level designs and interfaces, as well as proposed drawdowns on instrument cost, schedule and technical reserves. The CCB, chaired by the Project Manager, reviews each change request to determine its effect on the project. The CCB consists of:
Cost, schedule and technical reserves are under the control of the Project Manager as defined in Figure 7, LAT Project Change Control Thresholds. Subsystem internal re-allocations may be made within the resources of the subsystem, documented through the established CCB processes and approved by the subsystem manager. Changes that affect the LAT or other LAT subsystems must be documented, requested and approved by the Configuration Control Board.
The DOE LAT Federal Project Manager and NASA/GSFC GLAST Project Manager serve as members of the LAT CCB when changes which affect Level 2 or higher items (as defined in Figure 7) are considered, and sign off on these LAT CCB actions if approved. They are responsible for obtaining higher level approvals if required.
LAT-MD-00068-01 LAT Configuration Management Plan Page 15 of 19
The System Engineer and Project Control Manager will coordinate all activities pertaining to a proposed change, to ensure that the material is complete for making a decision. Changes approved by the CCB will result in modifications to the subsystem technical, cost and/or schedule baseline, drawing against contingency available in the total LAT project baseline. Cost and schedule changes will be implemented in the PMCS, with all subsequent performance measured against the new subsystem baseline. All CCB actions will be reviewed with the SU-SLAC Director and Associate Director of Research, and reported to the DOE LAT Federal Project Manager and GSFC Project Office.
LAT-MD-00068-01 LAT Configuration Management Plan Page 16 of 19
Technical2 Cost3 Schedule4 Mass5 Power5
Level 16 And higher
As described in the DOE Project Execution Plan and the GLAST Mission Project Management Plan.
Level 26 DOE LAT Federal Project Manager
AND
NASA/GSFC GLAST Project Manager
Changes affecting any mission (level 2) requirement
Changes to any subsystem (level 3) allocation >$500K, or any change which causes the estimate at completion to exceed $110M
Changes which delay any level 2 or higher milestone
Changes to any subsystem (level 3) allocation which cause the total allocated mass to exceed the following thresholds:
Before PDR: 2725 kg Before CDR: 2850 kg Before launch: 2960 kg
Changes to any subsystem (level 3) allocation which cause the total allocated power to exceed the following thresholds:
Before PDR: 550 W Before CDR: 600 W Before ship: 625 W Before launch: 650 W
Level 36 LAT Project Manager
Changes affecting any LAT subsystem (level 3) requirement
Changes to any subsystem allocation; any changes > $50K
Changes which delay any level 3 milestone
Changes to any subsystem allocation
Changes to any subsystem allocation
Level 47 LAT Subsystem Manager
All changes to controlled documentation not affecting level 3 requirements
Any level 4 change <$50K which doesn’t increase subsystem cost
Any change not affecting level 1, 2, or 3 milestones
Any change within the subsystem level 3 allocation
Any change within the subsystem level 3 allocation
1 Any change to LAT baseline meeting the criteria listed in any row requires the 5 Appendix D approval of the person(s) identified in the first column 6 Level 1, 2 or 3 change requests require LAT CCB approval 2 Appendix A 7 Level 4 Cost or Schedule change requests are recorded in the 3 Appendix B Change Request log and captured in the PMCS, but require no additional 4 Appendix C review Figure 7: LAT Change Control Thresholds (from Project Management Plan LAT-00054-08)
LAT-MD-00068-01 LAT Configuration Management Plan Page 17 of 19
6.2.6 CCB Member Responsibilities The member responsibilities for the Configuration Control Board (CCB) are described as
follows:
The IPM is the chairperson of the CCB and exercises control of engineering changes and project cost and schedule.
The PCM is responsible for assessing impacts to cost, schedule or contract.
The ISE, or his designee, is responsible for CCB screening and is responsible for assuring the technical completeness of all change request evaluations. The ISE also assures the designation of the disciplines required to perform a complete evaluation of all CRs submitted to the CCB. This responsibility includes interfacing with all team members.
The Instrument Scientist, Chief Engineer and ISE evaluate the impact of the proposed change on the technical performance of the system.
The Integration and Test Manager advises the other members in the areas of integration and test, calibration, science verification, facilities, observatory integration launch site operations, etc.
Each Subsystem Manager is a member of the CCB and exercises control of engineering changes to his subsystem and controls the subsystem configuration.
The Performance & Safety Assurance Manager evaluates proposed changes with respect to the impact to product performance/safety and ensures compliance with Quality/Safety Assurance requirements.
The PCM acts as the CCB Secretary and exercises control of the CCB documentation. The PCM, or designee, is responsible for assuring the completeness of the CCB record. The PCM supports the CM process by tracking all contract document change requests and pertinent correspondence to and from GSFC.
The Responsible Product Engineer (RPE) who initiated the CR supports the CCB by assessing the change request for cost, schedule, and technical performance, scientific objectives, and risk impact. The RPE defends the CR during CCB evaluation.
Subcontractors may submit out-of-scope changes for approval by the LAT CCB. The Subsystem Manager responsible for the subcontractor reviews the change request and represents the subcontractor at the CCB.
6.2.7 Deviations and Waivers Deviation and waiver requests are processed, categorized, approved and tracked in the same
manner as other change requests.
A deviation is project approval to deviate from the approved design and occurs before the unit is built. The deviation differs from the normal change request in that it applies only for a limited quantity or limited time period.
A waiver is project approval to waive a specific requirement because of a nonconformance that violates an approved requirement.
The CR and DCN forms are used to request a deviation or a waiver.
LAT-MD-00068-01 LAT Configuration Management Plan Page 18 of 19
6.3 Configuration Status Accounting
6.3.1 Configuration Tracking The CIDL provides the ability to track all changes to CIs. The CIDL will maintain the
change history of all CIs so that the evolution of the system will be documented.
6.3.2 Configuration Status Reporting The CIDL serves as the vehicle for communicating the status of configuration through
periodic reports and direct real-time inquiries. Configuration Verification
The Subsystem Managers are responsible for implementing and closing the CCB-approved changes to CIs that are under their control. The DCN serves as notice that a document change has been implemented and verified. The verification of hardware changes is reported by signing the bottom of the DCN form and returning it to the CM coordinator for entry into the CM library and LAT distribution. In this manner, all changes can be tracked to completion and easily audited.
6.3.3 Document Verification Prior to release within the CM library all documents are required to go through a review
process. The review process is generally 10 days during which the document is circulated for comments. After the comments have been received the document is updated and revised. For final verification, the document goes out for 5 days for signature release. All additional comments that are received will be incorporated into the next version of the document. Once all signatures are received and the document has been approved it is then put under configuration control and released.
6.4.2 Signature Process Figure 8 represents the signatures required for release of a document. The figure is grouped
by document type and document hierarchy level.
The figure represents the minimum required signatories for release of a document supporting the LAT instrument flight program. The signatures required at collaboration facilities working on LAT subsystem components may differ from those listed here but in any case, may not be fewer.
