sgp information and configuration management procedure · pdf filesgp information and...

SGP Information and Configuration Management Procedure

12/1/16 iii SGP-MGMT-PROC-0002 Revision 1

Preface

This document is under the configuration management of the Space Geodesy Project (SGP) Configuration Control Board (CCB). Changes to this document require prior approval of the SGP Configuration Control Board (CCB) Chairperson, or designee. Proposed changes shall be submitted in the SGP Technical Data Management System (TDMS) via a Configuration Change Request (CCR) along with supportive material justifying the proposed change. Changes to this document will be made by complete revision.

All of the requirements in this document assume the use of the word "shall" unless otherwise stated.

Direct all comments, questions, or suggestions regarding this document to: Space Geodesy Project Office Code 61A Goddard Space Flight Center Greenbelt, MD 20771


12/1/16 v SGP-MGMT-PROC-0002 Revision 1

Table of Contents

1 Preface .................................................................................................................. 11.1 PURPOSE .......................................................................................................... 11.2 APPLICABILITY ................................................................................................. 11.3 AUTHORITY ...................................................................................................... 11.4 REFERENCES ................................................................................................... 2

2 INTRODUCTION ................................................................................................... 32.1 Configuration Management Objectives .............................................................. 32.2 Scope ................................................................................................................. 3

3 ROLES AND RESPONSIBILITIES ....................................................................... 43.1 SGP Project Manager ........................................................................................ 43.2 SGP Configuration Management Officer ........................................................... 43.3 SGP Configuration Control Board ...................................................................... 53.4 Internal Supporting Organizations and Contractor Support ............................... 53.5 External Organizations and SGP Major Interfaces ............................................ 5

4 CONFIGURATION IDENTIFICATION .................................................................. 64.1 Configuration Baselines ..................................................................................... 64.2 Classification of Controlled Documents ............................................................. 64.3 Requirements Hierarchy .................................................................................... 74.4 Document Identification and Numbering ............................................................ 7

4.4.1 Document Types ..................................................................................... 94.5 Document Format .............................................................................................. 94.6 Configuration Change Request (CCR) Identification ....................................... 104.7 Restricted Distribution Identification ................................................................. 10

4.7.1 Export Controlled Identification ............................................................. 104.7.2 Sensitive But Unclassified Data (SBU) ................................................. 11

4.8 Controlled Documents List (CDL) .................................................................... 114.9 Controlled Documents Tree ............................................................................. 114.10 Document Owner ............................................................................................. 124.11 Contractor Configuration Identification ............................................................. 124.12 Contractually binding documents ..................................................................... 124.13 Reference Documents ..................................................................................... 12


12/1/16 vi SGP-MGMT-PROC-0002 Revision 1

4.14 New Documents/Drawings ............................................................................... 124.15 New Document Submittal ................................................................................ 124.16 Document Changes/Revisions ......................................................................... 134.17 Document Storage ........................................................................................... 134.18 Documentation Release ................................................................................... 134.19 Document Distribution ...................................................................................... 134.20 Revalidation ..................................................................................................... 134.21 Superseded/Cancelled/Obsolete Documents/Drawings/Records .................... 14

4.21.1 Superseded/Cancelled Documents ....................................................... 144.21.2 Obsolete Documents ............................................................................. 14

4.22 Archival ............................................................................................................ 144.23 References To External Documents ................................................................ 14

5 CONFIGURATION CONTROL ........................................................................... 165.1 Configuration Change Classifications .............................................................. 165.2 Configuration Change Request (CCR) ............................................................ 16

5.2.1 CCR Owner Responsibilities ................................................................. 165.2.2 Configuration Change Request Process ............................................... 175.2.3 Configuration Change Request Package .............................................. 185.2.4 Configuration Change Request Priority ................................................. 185.2.5 Cost Estimates ...................................................................................... 19

5.3 Deviations and Waivers ................................................................................... 195.4 Contractor Configuration Control ..................................................................... 19

6 CONFIGURATION CONTROL BOARD ............................................................. 206.1 Configuration Control Board Responsibilities .................................................. 216.2 CCB Members Roles ....................................................................................... 21

6.2.1 CCB Members Responsibilities ............................................................. 226.2.2 Mandatory Reviewers ........................................................................... 226.2.3 SGP CMO Responsibilities ................................................................... 226.2.4 Configuration Control Board Meeting .................................................... 236.2.5 CCB Agenda ......................................................................................... 236.2.6 CCB Disposition .................................................................................... 236.2.7 Contract Action ...................................................................................... 246.2.8 Disposition of Internally/Externally Generated CCRs ............................ 246.2.9 CCB Action Items .................................................................................. 246.2.10 CCB Action Item Closure ...................................................................... 246.2.11 CCB Minutes ......................................................................................... 25

7 CHANGE IMPLEMENTATION ............................................................................ 267.1 Signature and Approval Controls ..................................................................... 26


12/1/16 vii SGP-MGMT-PROC-0002 Revision 1

7.2 Contractual Implementation of Approved CCRs .............................................. 267.3 Change Verification .......................................................................................... 27

7.3.1 SGP Controlled Documents .................................................................. 277.3.2 CMO Technical Publications ................................................................. 27

Appendix A – Definitions ............................................................................................. 28

Appendix B – Acronyms .............................................................................................. 31

List of Tables Table 1: Signature and Approval Authorities ............................................................................... 26


12/1/16 1 SGP-MGMT-PROC-0002 Revision 1

1 Preface

1.1 PURPOSE

This plan defines the Space Geodesy Project (SGP) policies, procedures, and requirements for Information and Configuration Management (CM). This procedure describes a process that is intended to ensure that all proposed and approved technical and programmatic baselines and changes to the SGP hardware, software, support systems, and equipment are documented.

1.2 APPLICABILITY

This procedure establishes the requirements for the implementation of CM on the SGP. This includes both SGP operational (legacy and next generation) and developmental elements. This document is applicable to the SGP and external organizations under direct contract to the SGP. The SGP mission development approach includes contractor elements and government management.

1.3 AUTHORITY

SGP-MGMT-PLAN-0001, Space Geodesy Project Plan SGP-MGMT-PLAN-0002, Space Geodesy Network Deployment Project Plan



1.4 REFERENCES

The following documents contain supplemental information to guide the user in the application of this document. In the event of a conflict between this document and the referenced documents, the instructions herein apply.

NASA-STD-0005 NASA Configuration Management Standard EIA-649-B Configuration Management Standard, SAE International Technical Report NPD 2190.1 NASA Export Control Program NPD 2200.1 Management of NASA Scientific and Technical Information NPD 1440.6 NASA Records Management NPD 7120.4 NASA Engineering and Program/Project Management Policy NPR 2200.2 Requirements for Documentation, Approval, and Dissemination of NASA

Scientific and Technical Information. NPR 1441.1 NASA Records Retention Schedule NPR 1600.1 NASA Security Program Procedural Requirements NPR 7123.1 NASA Systems Engineering Processes and Requirements GPR 1410.2 Configuration Management GPR 1440.8 Records Management GPR 2200.1 Processing and Approval of NASA Scientific and Technical Information

(STI) GPR 5100.4 Supplier Quality Audits GPR 7123.1 Systems Engineering NASA Form 1676 NASA Scientific and Technical Document Availability Authorization Form GSFC Form 25-49 GSFC STI Public Disclosure Export Control Checklist 22 CFR 120 - 130 International Traffic in Arms Regulations (ITAR)



2 INTRODUCTION

This procedure describes a process that is intended to ensure that all proposed and approved technical and programmatic baselines and changes to the Space Geodesy Project (SGP) documentation shall be systematically evaluated for validity, merit, need, and impact.

The function of the SGP CM System shall be to control and track the status of configured items (CIs)/controlled documents and interface with predominant and subordinate CM offices. This includes controlling changes to configuration documentation, maintaining status accounting records, and distributing all pertinent information as necessary. This will be accomplished by using the Technical Data Management System (TDMS). TDMS shall house the Project Library as well as serve as a repository for all CM and Data Management (DM) documentation. The SGP Project Office is responsible for the configuration management of SGP. This procedure establishes organizational responsibilities for implementing the CM system, top-level policies for configuration item identification, configuration change control, configuration status accounting, and configuration system verification for the SGP.

2.1 Configuration Management Objectives

This plan shall define and describe the CM system to be implemented by the SGP. The CM system functions defined are as follows:

1. Configuration Identification 2. Configuration Control 3. Configuration Status Accounting 4. Configuration Verification

The deployed CM processes shall provide the means by which the SGP Project Manager effectively assesses and controls all proposed changes to CM-controlled items (e.g., contracts, Statements of Work (SOW), requirements, specifications, plans, procedures, drawings, etc.) that may affect form, fit, function, safety, cost, or schedule.

2.2 Scope

This plan establishes the requirements for the implementation of CM for the Space Geodesy Project (SGP). It covers all aspects and phases of the Project, from development and network deployment through network operations (including legacy SLR and VLBI network operations) and analysis.



3 ROLES AND RESPONSIBILITIES

3.1 SGP Project Manager

The SGP Project Manager (PM) shall be responsible for ensuring that the SGP performs the configuration control functions necessary to meet the requirements of NASA and the Goddard Space Flight Center (GSFC). The SGP PM shall designate a Configuration Management Officer (CMO) as the central point-of-contact to facilitate the SGP configuration management activities.

3.2 SGP Configuration Management Officer

The SGP CMO duties shall include facilitating the overall SGP CM tasks that includes configuration identification, configuration control, configuration status accounting, interface control, and configuration audits.

The SGP CMO shall be the central point-of-contact for the input, control, and distribution of all SGP generated documents.

1. The CMO shall be responsible for ensuring an effective, controlled flow of data through the Configuration Control Board (CCB) and shall perform the following:

a. Report to PM (or designee); b. Serve as the central point-of-contact for input, processing configuration changes,

control, and distribution of all SGP generated and deliverable documents and drawings;

c. Review CCRs to ensure compliance with SGP CM requirements; d. Evaluate documents and drawings as to whether they are to be controlled or

reference (uncontrolled DM items) documents based on their type. Controlled documents are identified as such in the TDMS database;

e. Schedule CCB meetings with the concurrence of the CCB Chairperson by publishing notification memoranda (i.e., setting date, time, place, and agenda), and providing electronic review packages to the CCB;

f. Record minutes of the CCB meetings and distribute copies to attendees; g. Track CCB action items; h. Maintain the CM status accounting system; i. Coordinating changes to baselined documentation with appropriate internal and

external organizations; j. Perform periodic formal and informal audits of the functional organizations CM

system as directed by PM; and k. Maintain an up-to-date SGP Controlled Documents List (CDL).



3.3 SGP Configuration Control Board

The membership and responsibilities are defined and established in Section 6.0 of this document.

3.4 Internal Supporting Organizations and Contractor Support

Internal GSFC and JPL organizations and contractors supporting the SGP shall comply with the CM processes detailed in this procedures.

3.5 External Organizations and SGP Major Interfaces

The application of the SGP CM system to any other agency is governed by Memorandum of Understanding (MOU), Memorandum of Agreement (MOA) or Letter of Agreement (LOA).



4 CONFIGURATION IDENTIFICATION

4.1 Configuration Baselines

The life cycle of a typical project is broken down into phases that encompass, but are not limited to, preliminary design, detailed design, critical design, fabrication and assembly, integration and testing. As a configuration item (CI) proceeds through these phases, the technical documentation that identifies its configuration becomes progressively more definitive and precise.

The requirements baseline shall be established as soon as practical. Configuration baselines shall be established as major project milestones, and will typically be implemented as follows:

1. Project requirements baseline is established at the Systems Requirements Review (SRR).

2. Design baseline is established at the Preliminary Design Review (PDR). 3. Development baseline is established at the Critical Design Review (CDR). 4. Product baseline is the final, as-built configuration of a delivered CI, and for the SGP

Systems as documented for the Final Acceptance Review and/or Operational Readiness Review. This also includes all required operational, training and maintenance documentation.

4.2 Classification of Controlled Documents

SGP controlled documents fall into three basic categories as defined below. The document classification shall be noted on the configuration control record and the controlled documents tree because it determines the degree of CCB involvement required in the processing of associated configuration change requests.

4.2.1 Project/CCB Controlled

Technical requirements documents, which control the level-3 requirements or above require project-level CCB review and disposition of configuration change requests. Administrative documents, which are those documents issued by the SGP to provide management, procedural, and administrative guidance for the SGP may also require project-level CCB review. Documents in this class include plans and procedures of a non-technical nature, and documents related to information management. Configuration change requests for these documents may, at the discretion of the CCB Chairperson, or designee, be dispositioned out-of-board by the rendering of his/her approval.

4.2.2 Signature Controlled

Technical baseline documents, which control the requirements up to level-4, design of the associated ground station deliverables, designs, drawings, test plans, reports and communication/data interfaces are typically dispositioned out-of-board and approved through the



TDMS SCoRe process. Typically, technique specific CI that does not impact the Project schedule, budget, level-3 requirements, or other techniques/elements shall be dispositioned out-of-board, at the discretion of the CCB Chairperson, using an element specific CM process approved by the PM.

4.2.3 Reference Only

Reference documents do not go through any sort of review (and do not have comment matrices associated with them), but are archived and referenced in TDMS. Reference documents also include CI that has gone through an approval process outside of TDMS but should be contained in the project archive (such as Statement of Works and Task Orders).

4.3 Requirements Hierarchy

Level 0 Requirements - Scientific/Technical Objectives - HQ Level 1 Requirements - Science - SGP/HQ Level 2 Requirements - Mission/Network Level Level 3 Requirements - System level (technique/station/site: SLR, VLBI, GNSS, VTS) Level 4 Requirements - Subsystem (Station Subsystem) Level 5 Requirements - Component (Station Component)

4.4 Document Identification and Numbering

TDMS assigns a unique document identification number to all SGP generated documents, and shall is based on the following guideline:

• SGP prefix;

• WBS/System Level acronym indicating what element of the project the document belongs;

• Document type (i.e., REQ, PLAN, PROC, etc.);

• Four-digit sequential number by type;

• Revision number issued sequentially (if applicable), with the initial release being revision 1. For example, SGP-MGMT-PLAN-0001 Rev. 2.

4.4.1 Work Breakdown Structure

Documents are assigned a Project element acronym associated with the document’s work area and scope. The WBS elements and their acronyms, as they currently exist within TDMS, are shown below.

Table 1: SGP Work Breakdown Structure implemented within TDMS 1.0 Management

1.1 Project Management MGMT

1.2 Resources Management MGMT

1.3 Schedule Management/Planning MGMT

1.4 Configuration Management MGMT

1.5 Reviews MGMT



1.6 Contract and Procurement Management MGMT

1.7 Training MGMT

1.8 Logistics MGMT

2.0 Systems Engineering

2.1 Systems Engineering Management SYS

2.2 Systems Design SYS

2.3 Technical Evaluation SYS

2.4 Software Systems Engineering SYS

2.5 Systems Integration and Test SYS

3.0 Safety and Mission Assurance

3.1 Safety SMA

3.2 Quality Assurance SMA

3.3 Product Assurance SMA

3.4 Materials/Processes SMA

3.5 Reliability Analysis SMA

4.0 System/Technology Development

4.1 Analysis Tool Modernization TECH

5.0 Network Build

5.1 Integrated Network Operations INO

5.2 SGSLR SGSLR

5.3 VGOS VGOS

5.4 VTS VTSD

5.5 DORIS DORD

5.6 GNSS GNSSD

5.7 Data Archiving and Distribution DAD

5.8 Site Development SITED

5.9 Network Simulations SIM

6.0 Science and Analysis

6.1 Project Scientist Activities PS

6.2 SLR Analysis Center SLRA

6.3 VLBI Analysis Center VLBIA

6.4 IDS Analysis Center DORA

7.0 Network Operations and Maintenance

7.1 Integrated Network Operations and Maintenance INOM

7.2 SLR Operations and Maintenance SLR

7.3 VLBI Operations and Maintenance VLBI

7.4 VTS Operations and Maintenance VTS

7.5 DORIS Operations and Maintenance DOR

7.6 GNSS Operations and Maintenance GNSS

7.7 Site Infrastructure SITE



4.4.2 Document Types

Document types, as they currently exist within TDMS, are shown below. Table 2: Document types identified within TDMS.

ANYS Analyses CDRL Contract Deliverable Requirements List CORR Correspondence (memo, email, etc.) DESC Descriptive Reference Documentation EIDP End Item Data Package FIN Financial Documentation FORM Project-Specific Forms HDBK Handbooks, user guides, instruction manuals ICD Interface documentation (ICD, IRDs, IDDs) LEGL Contracts or Legal Agreements (ex: AO, MOU, MOA, LOA, LOU) LIST General Lists (materials, parts, etc.) LOG Miscellaneous Logs PLAN Plans PROC Procedures REQ Requirements REVW Presentations and/or Review Packages RPT Test or Status Reports SCHD Schedule-Related Documentation SPEC Specifications SOW Statement of Work TN Technical Notes TRD Trade Studies WBS Work Breakdown Structure

4.5 Document Format

For all new releases and revisions issued after the effective date of this document, all pages of a document shall have the document number and the current revision letter or status.

The following footer shall be placed, at a minimum, on the cover page indicating where to confirm the current revision status:

Check the SGP TDMS site at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

In addition to the permanent document identification number, the cover sheet for all SGP generated CM-controlled documents shall include, at a minimum, the document title, the effective and expiration dates.

All documents shall have a signature page indicating the responsible individuals and organizations, including the document preparers, reviewers, and approvers.



All documents shall have a change revision sheet and/or a change history log identifying the changes along with the current revision.

The online database shall reflect the current revision status. All controlled baseline documents shall have a CCR before processing.

Internal and external documents generated and submitted to the SGP CMO for formal review shall receive an SGP CM control number for internal tracking (CCR number).

Only the documents and drawings providing definition of products (components, subassemblies, assemblies, subsystems, and systems) shall be placed under CM control. Documents performing this function include: ICDs, IRDs, procedures, plans, requirements, specifications, SOWs, and MOUs/MOAs/LOAs.

All SGP controlled documents shall be identified on the CDL and tagged as such in the SGP database.

4.6 Configuration Change Request (CCR) Identification

The sequential portion of a SGP CCR number is assigned by TDMS using the following number convention: SGP-CCR-XXXX.

4.7 Restricted Distribution Identification

4.7.1 Export Controlled Identification

Document owners should mark all technical documentation with an affirmative statement advising the reader of the export jurisdiction and export classification. Most documents subject to export control under the ITAR and/or EAR are generally marked in one of two manners. The first and most common practice involves the marking of an entire document, such as an engineering drawing package, technical report, mishap investigation report, or technical presentation. In some engineering or scientific documents, the majority of the content may be export-controlled. While marking a whole document, place the ITAR and/or EAR notice on the cover page in a font size that is readable when printed. Ideally, insert the jurisdiction and category into the header or footer of the remaining pages, and the marking is complete. The appropriate markings for documentation controlled under the ITAR, EAR, or both are illustrated below.

ITARCategory___

-InternationalTrafficinArmsRegulations(ITAR)Notice-This document contains information which falls under the purview of the U.S. Munitions List (USML) as defined in

the International Traffic in Arms Regulations (ITAR), 22 CFR §120-130, and is export-controlled. It shall not be transferred to foreign persons in the U.S. or abroad without specific approval of a knowledgeable NASA export

control official, and/or unless an export license or license exemption is obtained/available from the Directorate of Defense Trade Controls, United States Department of State. Violations of these regulations are punishable by fine,

imprisonment, or both.

EAR ECCN ___ - Export Administration Regulations (EAR) Notice -



This document contains information within the purview of the Export Administration Regulations (EAR), 15 CFR §730-774, and is export-controlled. It may not be transferred to foreign persons in the U.S. or abroad without

specific approval of a knowledgeable export control official, and/or unless an export license or license exception is obtained/available from the Bureau of Industry and Security, United States Department of Commerce. Violations of

these regulations are punishable by fine, imprisonment, or both.

Subject to U.S. Export Control Regulations:

This document contains information within the purview of the International Traffic in Arms Regulations (ITAR), 22 CFR §120-130 and the Export Administration Regulations (EAR), 15 CFR §730-774, and is export-controlled. It

may not be transferred to foreign persons in the U.S. or abroad without specific approval of a knowledgeable export control official, and/or unless an export license, license exemption, or license exception is obtained/available from the Directorate of Defense Trade Controls, United States Department of State or Bureau of Industry and Security, United States Department of Commerce. Violations of these regulations are punishable by fine, imprisonment, or

both.

ALL documents marked as export controlled shall have the following statement included in the footer of every page containing export controlled data.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

4.7.2 Sensitive But Unclassified Data (SBU)

NPR 1600.1 establishes a uniform process whereby Sensitive But Unclassified (SBU) NASA information, known as "Administratively Controlled Information (ACI)," is identified and properly managed to ensure disclosure to unauthorized persons is effectively prohibited. Refer to NPR 1600.1, Chapter 5 for classifications of documents and pertinent information about labeling and dissemination of SBU documentation.

4.8 Controlled Documents List (CDL)

The SGP CMO shall maintain the SGP CDL. Baseline CIs (CM-controlled documents) shall be incorporated into a CDL that contains, at a minimum, the document number, document title, revision level, effective and expiration dates, and the owner’s name in accordance with GPR 1410.2. The PM, or designee, shall determine which documents are to be controlled, baselined, and included on the CDL.

4.9 Controlled Documents Tree

The Controlled Documents Tree is a diagram created in an organizational-chart format that depicts the hierarchy of all the CM-controlled documents. The diagram is itself a CM-controlled document sponsored by the SGP Chief Engineer. Each box contains the following information about a given controlled document:

• Document Number

• Document Title

• Government Owner



• Current Revision Indicator

• Date of Effectivity and Expiration Controlled document trees shall be maintained for both the Project CCB controlled documents and element signature controlled documents.

4.10 Document Owner

When a need for a document is identified, an owner shall be assigned to that document. The document owner is responsible for the content of the document, providing a reviewer’s distribution list to the CMO and assists in facilitating it through the CCB process.

4.11 Contractor Configuration Identification

Contractor configuration identification requirements are governed by the SGP approved contractor CM procedures and applicable agreements or contracts.

4.12 Contractually binding documents

Contractually binding documents shall be identified, as a minimum, by their document number, title, and a version/revision indicator. The version/revision indicator shall indicate use of a specific version, or the latest version, as determined by the CCB. They should not have footer information or an expiration date.

Contracting officers shall ensure that proper and adequate identification information is provided.

4.13 Reference Documents

Other documentation may be submitted for information and/or reference purposes. In these cases, the applicable revision/date shall be identified in TDMS. Reference documentation shall be submitted without a CCR.

4.14 New Documents/Drawings

The process of submitting new documents to the SGP CMO includes the proper assignment of document numbers, baseline identification, and document submission. NOTE: All documents under revision or not formally CM-approved shall be clearly marked as “DRAFT” on the cover page in accordance with GPR 1410.2 procedures and guidelines.

4.15 New Document Submittal

When a document is ready to be baselined, the electronic version of the document shall be uploaded to TDMS (preferably in Microsoft Word format).

All baseline CM-controlled documents require the approval of the SGP PM, or designee, via the CCB process. All documents shall be stored electronically and made accessible to SGP personnel via the TDMS site.



4.16 Document Changes/Revisions

When appropriate, SGP document changes shall be made in the form of a Document Change Notice (DCN) or complete revisions (for revisions, when >50% of the document needs to be revised). These changes/revisions are submitted using the CM/CCR process.

4.17 Document Storage

Documents, including electronic media, hard copy originals or master copies shall be stored in a safe and secured document control area by the SGP. TDMS will be used as the central repository for the final electronic version of SGP technical documentation baselines. User accounts authorized by the PM will be created and maintained by the CMO and the System Administrator. Contact the CMO for an account creation form. Electronic storage will be write-protected with limited access.

4.18 Documentation Release

A new document is released through the formal change control procedures defined in this document and the effective and expiration dates will be added to the front cover by the CMO.

In general, the expiration date will be five years from the effective date of release. A document publication notice shall be distributed by the CMO when a new or changed document is released with a reminder that superseded/cancelled/obsolete versions are not to be used.

4.19 Document Distribution

Each document will have a specific standard distribution list that is provided by the document owner and will be maintained by the owner. When documents are released and published on TDMS, SGP personnel included on the distribution list will be notified via TDMS alerts. The document owner and/or the CMO may also notify SGP personnel via email or other means. For documents, the CMO shall release CCB-controlled documents through TDMS.

4.20 Revalidation

Controlled documents in general will expire no more than 5 years after the effective date. The following requirements shall apply:

• The expiration date shall be tracked on the organization’s CDL;

• The expiration date may be placed on the cover, at the organization’s discretion;

• The organization shall have a process to ensure that documents not marked with an expiration date are unavailable for use after they expire;

• Only the CO can authorize a change to the expiration date on contractually binding documents;



• The organization may revalidate a controlled document by a documented review and approval process. If there are no changes, or changes are merely of an editorial nature, revalidation allows extending the expiration date for up to five years. The effective date is not changed. The revalidation shall be documented in the Change History Log.

• As appropriate, controlled documents that should be moved to the archive without review upon their expiration should be marked “Does not require revalidation.”

4.21 Superseded/Cancelled/Obsolete Documents/Drawings/Records

4.21.1 Superseded/Cancelled Documents

In the event that a document has been superseded or cancelled by another document, the superseded document shall be clearly marked as “SUPERSEDED” or “CANCELLED” and shall be archived for historical purposes.

When a document is superseded or cancelled, notification shall be sent to SGP personnel via e-mail. Documents that are cancelled or become superseded will be indicated as such on the CDL.

Electronic files of superseded documents shall be stored in a separate location in the database to provide assurance against unintended use.

The document record shall be marked as “SUPERSEDED” or “CANCELLED”.

4.21.2 Obsolete Documents

Documents will be periodically reviewed and assessed based on their expiration date and will be distributed for review to the CCB for revalidation of their expiration dates. At that time, it may be determined that the document is to be obsolete. The records that are obsolete follow NPR 1441.1, NASA Records Retention Schedules for document retention. Documents that are obsolete shall be listed in the database as being obsolete. Indication is also provided if the document is or is not replaced by another document. The CMO shall send out announcements listing documents that are deemed obsolete with instructions to dispose of the obsolete documents. As appropriate, controlled documents that should be moved to the archive without review upon their expiration should be marked "Does not require revalidation."

4.22 Archival

The CMO shall perform archival of SGP documentation in accordance with NPR 1441.1, NASA Records Retention Schedules.

4.23 References To External Documents

Whenever an external document is referenced in an SGP CM-controlled document, the current version is assumed. However, if the use of a specific version is desired, the revision information



needs to be specified. Referenced documents controlled outside of SGP shall be added to the SGP TDMS database (if possible) as reference documents.



5 CONFIGURATION CONTROL

Configuration control is the systematic coordination, evaluation, decision, and release of proposed and approved changes to an established baseline. The objective of configuration control is to ensure that changes are properly and completely defined and presented in such a way that the Project can consider the cost, schedule, and performance impacts of a proposed change, and can control change implementation.

5.1 Configuration Change Classifications

a. Class I Changes – changes that occur when one or more of the following items is affected: 1) Baselined documentation (except for typographical errors, simple clarification, or

other examples of Class II documentation changes); 2) Technical requirements contained in the product configuration items (CI) (form,

fit, function); 3) Contract end items/requirements

Class I changes shall be submitted for CCB approval. b. Class II Changes – changes that do not fall within the definition of a Class I change.

Examples of Class II changes are: 1) A change in documentation only (e.g., correction of errors, addition of clarifying

notes or views);

2) A minor change in hardware (i.e., substitution with an approved alternative material) which does not affect any item listed under Class I changes;

3) Plans and procedures of a non-technical nature or documents related to information management.

Class II changes written against CM-controlled documents normally do not require a formal CCB process. Once the Chairperson has validated the CCR, approval can be accomplished out-of-board with the appropriate approvals. The CCR will capture the signatures and identify the change as occurring out-of-board.

5.2 Configuration Change Request (CCR)

5.2.1 CCR Owner Responsibilities

An owner shall be assigned to each CCR upon initiation within TDMS. The CCR owner shall be a member of the SGP.

The owner’s name shall appear on the CCR form. The owner shall identify required and ad hoc reviewers.



The owner shall coordinate and assess these inputs to determine their validity or merit. The CMO shall notify the owner when the CCR is ready to be scheduled for the CCB.

A consolidated Reviewer’s errata form shall be completed and forwarded to the CMO by the owner prior to the CCB meeting for that CCR.

The owner shall attend the CCB meeting to represent the CCR and the CCB recommendation for disposition.

5.2.2 Configuration Change Request Process

Any SGP personnel may initiate a CCR to the appropriate CM baseline, with the agreement of the document owner. The CMO will assist the owner in assembling the CCR package and help in facilitating it through the CCB process. The formal CCR process begins when a CCR or a new CI is entered into TDMS. The CMO confers with the CCB Chairperson, the CI owner, and other required SGP team managers to determine a target date for consideration by the CCB and to confirm the list of mandatory reviewers for this CCR based on input received from the author of the CCR. The determination of CCR priority level and whether or not to formally convene the CCB shall be made by the CCB Chairperson. Once the list of mandatory reviewers and target date are established, the CMO distributes the CCR materials via TDMS, or directly to any reviewers without TDMS access, along with instructions for the review and submission of comments/recommendations. The instructions include a cut-off date for submission of review comments, normally three (3) days prior to the scheduled CCB/target date.

On the comment cut-off date, the CMO determines if all mandatory reviewers have responded and follows up with any that are delinquent, establishing a new cut-off date for mandatory reviewer comments, if required. In parallel, the CI owner and the CCR author develop recommended dispositions for each comment received. This may require that a technical convergence meeting be held if there is significant divergence of comments/recommendations. In the event that late comments are received from individuals not specified to be a mandatory reviewer, the CMO and CI owner/CCR author will determine if the comments will be considered.

Approximately three (3) days prior to the scheduled CCB review for the CCR, the CMO and CI owner/ CCR author will assess whether the CCR package is ready for consideration by the CCB. This assessment includes determination of whether responses were received from all mandatory reviewers, whether recommendations for disposition of comments have been completed, and a decision on whether the CCR / CI is sufficiently mature to be presented to the CCB. If any of these conditions are not met, the CCB Chairperson will be given the opportunity to decide whether consideration of the CCR should be withdrawn and re-submitted at a later date, or should be submitted to the CCB in its present state.

Review by the CCB will address two levels of decision. The first level pertains to the CCR as a whole with three potential outcomes:

1. The CCR is sufficiently mature and has sufficient merit to proceed with review / implementation of individual comment-level dispositions; or



2. The CCR is not sufficiently mature for the board to take a final action and should be deferred for revision and re-scheduled; or,

3. The CCR should be withdrawn because it is without sufficient merit. The second level pertains to specific individual changes / comments associated with the CCR. This level of review has four potential outcomes:

1. The line item comment and associated disposition are accepted / approved as written; 2. The CCB provides specific direction to change the line item comment and associated

disposition; 3. The CCB assigns an action for the CCR author / CI owner to implement without further

CCB review of the resulting specific line item change; or, 4. The CCB assigns an action, but requires review at a subsequent CCB meeting prior to

implementation of the specific line item change. The CMO records the decisions of the CCB at both the total CCR level, and at the individual line item level, and incorporates the decisions into the meeting minutes. The CI owner, assisted by the CCR author and the CMO, implements the change per the CCB decisions and publishes the associated document(s) or revisions / DCNs. The CMO reviews the resulting CI against the CCB decisions to confirm that only approved changes were implemented, and that any requirement for CCB review prior to implementation (line item disposition outcome #4) has been accomplished prior to submission to signatories. The CCR will be closed after the change implementation is completed and verified. Once signed, the revised CI is entered into the SGP CM Library.

5.2.3 Configuration Change Request Package

The CMO shall be responsible for compiling a complete master CCR package that will be maintained in TDMS as a case file for historical purposes. The CCR package shall include, at a minimum, the following items:

a. CCR Form; b. CCR attachments (e.g., baselines, revisions, Document Change Notices [DCNs]) c. CCR Transmittal Letters d. CCR Review Comments e. Contractor Correspondence (including e-mail correspondence) f. Project Correspondence (including e-mail correspondence) g. Contractual Direction h. Rough Order of Magnitude (ROM), cost of the change (if applicable) i. CCB Agenda j. CCB Minutes

5.2.4 Configuration Change Request Priority

The CMO (in conjunction with the CCR owner) shall recommend a priority to the proposed change.



The CCB Chairperson shall determine final priority. Three priority levels shall be used: a. Emergency. This priority shall be assigned when failure to implement a change in

operational characteristics may seriously compromise the effectiveness of the equipment or when a hazardous condition exists that may result in fatal or serious injury or extensive damage or destruction of the equipment. Emergency changes shall be dispositioned within 24 hours of receipt by the CMO. CCRs identified as “Emergency” will immediately be brought to the CCB Chairperson’s attention and a CCB meeting will be convened as soon as possible.

b. Urgent. This priority shall be used to effect a change that, if delayed, would cause schedule slippage or cost increase. Urgent changes shall be dispositioned within five (5) business days of receipt by the CMO.

c. Routine. This priority shall be used when the conditions specified in the Emergency and Urgent priorities do not exist. Routine changes shall be dispositioned within ten (10) business days of receipt by the CMO.

5.2.5 Cost Estimates

When a proposed change has a cost impact, a Rough Order of Magnitude (ROM) cost or an In-house Cost Estimate will be required as part of the CCR. In addition, the impact assessment statement must include positive, negative, and/or no impact assessment, as appropriate. The CCR owner is required to coordinate with the SGP Resource Manager to develop an accurate ROM. Any cost estimate accompanying a CCR shall be treated confidentially. The owner and CMO will consider each CCR for this purpose and act appropriately against unnecessary or unintentional release. Only users with Proprietary/Programmatic permissions can see a cost estimate entered into a TDMS CCR record.

5.3 Deviations and Waivers

Deviations and waivers are authorizations to depart from a particular performance or design requirement for that configuration item. Deviations are given prior to the manufacture/test of an item and waivers are given after the manufacture/test of an item. Requests for Deviations/Waivers (RDWs) shall be processed as Class 1 changes and require CCB approval through the CCR process. A Request for Waiver/Deviation is processed via a CCR in conjunction with completing the Deviation and Waiver form in TDMS and will be processed in the same manner as Class I CM changes. When the CCR and Waiver/Deviation is approved, the affected document of the deviation or waiver shall be updated with a table that includes the CCR number, date approved, and description of waiver or deviation that was approved. The Change History Log shall also be updated with a reference to the deviation and/or waiver description.

5.4 Contractor Configuration Control

Contractor configuration control requirements are governed by the SGP approved contractor CM procedures and applicable agreements or contracts.



6 CONFIGURATION CONTROL BOARD

Once a configuration baseline is established, all changes to the SGP configuration documents and drawings shall be controlled through the CCB review processes. The CCB is a group of technical and administrative personnel who are responsible for formally evaluating, dispositioning, and documenting its actions relative to proposed changes and ensuring that each change’s impact on all specified CIs is considered in terms of performance, cost, and schedule. The CCBs shall be responsible for making recommendations to the CCB Chairperson for approval, approval with change/comments, disapproval, withdraw, or defer for further study or action.

The CCB shall ensure the following is implemented: 1. Establish a list of applicable CIs; 2. Identify the baselines to be established during the development life cycle; 3. Establish the documentation (configuration identification) required to adequately and

accurately describe a CI in its current configuration; 4. Verify, approve, and place under configuration control the documentation associated

with each CI as appropriate for each configuration baseline; 5. Establish the format and level of detail required in the CDL and associated Controlled

Documents Tree; 6. Evaluate all CCRs submitted to the CCB and present its recommendations to the CCB

Chairperson. 7. Evaluate all change proposals that affect form, fit, or functional requirements defined

in applicable performance specifications, engineering drawings, and other baseline documents;

The CCB review process shall be used to control new document releases and changes to ensure that they are compatible in terms of mission requirements, schedules, and cost implications.

The CCB shall be responsible for controlling baselines and changes to those baselines at the Project level.

Changes that affect higher-level requirements shall be submitted to the CMO responsible for coordinating the operations of the affected CCB.

The CCB meets at the direction of the CCB Chairperson. CCR owners shall present the proposed changes to the CCB.

The CCB shall review and give proper consideration to the changes’ impacts on defined CIs from all aspects (e.g., technical, interfaces, operations, logistics, schedule, cost, etc.). The CMO records minutes of the meeting. The CCB Chairperson shall make the final decision on all CCB recommendations.



The CCB Chairperson shall be responsible for obtaining appropriate approval/disapproval for any proposed changes that are beyond the authority of the SGP.

6.1 Configuration Control Board Responsibilities

Each CCB shall be composed of members with the appropriate technical and management expertise necessary for decision-making and is responsible for reviewing all proposed changes to CM-controlled documents and evaluating matters relating to project resources, contract cost and schedule impacts.

6.2 CCB Members Roles

The following disciplines shall have major responsibilities for the CCB:

a. Project Manager - The PM, or designee, serves as the CCB Chairperson and is responsible for establishing the SGP CCB, appointing its members, presiding over CCB meetings, and exercising final approval/disapproval or concurring with the withdrawal in accordance with CCB recommendations. The PM or designee is responsible for all technical and engineering considerations regarding proposed changes to the CIs and performs the following: 1. Ensures that all participating SGP personnel and contractors comply with the

requirements of this procedure; 2. Appoints members to the CCB; 3. Calls scheduled and unscheduled meetings of the CCB; 4. Presides over all CCB meetings; 5. Authorizes out-of-board processing of CCRs to promote efficiency and

productivity, or to provide critical and emergency direction; 6. Evaluates the recommendations of the CCB, approving or disapproving all CCB

recommendations within the scope of the Chairperson’s authority and authorizing the establishment of baselines;

7. Obtains proper authorization for technical, engineering, or resource changes that are beyond his/her personal authority;

8. Approves CCB meeting action items, if necessary; 9. Approves the minutes, which document the CCB meeting and action items, for

distribution. b. Technique Element Leads - participates in the CCB as necessary to review proposed

changes for impacts to its development activities. c. Resource Manager - participates in the CCB as necessary to review all proposed

changes, evaluating matters relating to all project resources (cost, schedule, other program control elements, etc.) and contracts for impacts to development activities.

d. Chief Engineer - participates in the CCB as necessary and advises the Chairperson in all areas of mission systems engineering, surveillance, and risk mitigation.



e. Chief Safety and Mission Assurance Officer (CSO) – participates in the CCB as necessary by reviewing all proposed changes for impacts or potential problems in the areas of reliability, safety, quality assurance, non-conformance, etc.

f. Network Operations Managers – participates in the CCB as necessary to review proposed system, operations, and/or transition changes for potential impacts to operations.

g. Contracting Officers - responsible for ensuring that the SGP contract deliverables are acceptable under the terms of the contract and participates in the CCB as necessary for changes to SGP contract documents.

h. Project Scientist – participates in the CCB as necessary by reviewing proposed changes for impacts to the science requirements and scientific user community.

i. Configuration Management Officer (CMO) - is responsible for coordinating the CCB activities, and providing uniform policies and procedures for implementing an effective CM system.

j. Ad-Hoc CCB Members to the CCB – will be appointed by the CCB Chairperson as needed.

The following entities must be present in order to have a quorum and will also be required to review any disposition that was not explicitly presented to the CCB: PM, Engineering Technical Authority (i.e., Chief Engineer), Safety & Mission Assurance Authority (i.e., Chief Safety and Mission Assurance Officer), and Document Signatory.

6.2.1 CCB Members Responsibilities

CCB members shall:

a. Assess a CCR for technical merit and impact; b. Enter comments and disposition comments or give a response to a comment, if

applicable, and c. Attend CCB meetings or send an alternate designee.

6.2.2 Mandatory Reviewers

Mandatory reviewers will be clearly identified by the document owner when the configuration change request is distributed for review and shall:

a. Assess a CCR for technical merit and impact; b. Enter comments and disposition comments or give a response to a comment, if

applicable, and c. Attend CCB meetings or send an alternate designee.

6.2.3 SGP CMO Responsibilities

The SGP CMO shall:

a. Review CCR for completeness; b. Verify affected document(s);



c. Coordinate reviewers; d. Submit to CCB for review; e. Monitor review process; f. Schedule CCB meeting; g. Generate agenda; h. Prepare CCR form for signature; i. Obtain required signatures, either electronic or on hard copy; j. Maintain related CCR information in TDMS; and k. Notify Project of CCB approved documents.

6.2.4 Configuration Control Board Meeting

CCB meetings shall be convened as necessary.

The CMO shall be responsible for the preparation of CCRs for dissemination to CCB attendees and shall notify CCB members regarding time, location, and agenda of each meeting as well as any action items assigned during the meeting. The CCB Chairperson may convene emergency CCB meetings at any time.

6.2.5 CCB Agenda

CCRs shall be added to the agenda when the Reviewer’s errata form that lists all comments received in sequential order have been prepared/given to the CMO. The CMO will review comments received to see if the responses have any CM-related issues.

Technical issues shall be coordinated with the CCR owner. Technical issues may cause the CCR to be removed from the proposed agenda and may cause the CCR to be reworked or withdrawn.

Once CCRs are ready for CCB action, the CMO shall issue an agenda prior to the scheduled CCB meeting. The agenda will include the date, time, location of the meeting and the agenda items to be presented. The agenda shall be distributed, normally three days prior to the scheduled CCB meeting unless there is an emergency CCB then the agenda will be sent out upon determination of the emergency CCB. The CMO will send an e-mail notifying the CCB participants the agenda has been distributed. Original agendas will be stored in the appropriate CCR package by the CMO.

6.2.6 CCB Disposition

Proposed changes shall be reviewed at the CCB meeting with input from all CCB members and ad hoc reviewers. The final decision to approve, approve with errata/change/comments, disapprove, withdraw, or defer is the responsibility of the CCB Chairperson.

The CMO shall record and distribute minutes and action items of each CCB meeting. CCRs are dispositioned using one of the following categories:

a. Approve b. Approve with errata/change/comments



c. Disapprove d. Withdraw e. Deferred

Withdrawn and disapproved CCRs shall be kept on file in TDMS with no action. Deferred CCR packages are maintained by the CMO to await completion of action(s) resulting from the CCB meeting. CCB members shall be notified of all dispositions, actions, and minutes. Minutes of the CCB will be distributed by the CMO. At the discretion of the CCB Chairperson, CCRs for controlled documents classified as “Administrative” documents (i.e., non-technical documents) may be dispositioned by an out-of-board decision and signature rendered by the CCB Chairperson or his/her designee.

6.2.7 Contract Action

The appropriate contract action change order, Request for Proposal (RFP), bilateral modification, or contracting letter of direction shall be implemented by the CO for all approved CCRs.

6.2.8 Disposition of Internally/Externally Generated CCRs

The SGP will from time to time make changes that affect the community external to the SGP. Similarly, in the course of updating controlled documentation, external organizations occasionally make changes that affect the external community. The SGP Chief Engineer shall verify and determine the proper scope of the affected organization and review all internally/externally generated CCRs. CCRs will then be routed to these organizations for approval and concurrence.

6.2.9 CCB Action Items

The CMO shall document the CCR dispositions and any assigned action items recorded in the CCB minutes.

6.2.10 CCB Action Item Closure

Action items recorded in the CCB minutes shall be accomplished by the actionee by the due date imposed by the CCB and reflected in the minutes. Action items shall be closed only when the CMO is provided copies of the required documentation. Upon receipt, the CMO shall verify fulfillment of action items with appropriate CCB/Project personnel. Note: Action item due dates may only be modified/extended when the CCB Chairperson, or designee, agrees with the proposed date change. Upon approval, the CMO shall make the necessary modification(s).



6.2.11 CCB Minutes

The SGP CMO shall generate and distribute minutes of the CCB meetings. The minutes record the list of attendees, CCRs discussed, the CCB recommendations, CCB dispositions, procurement priority, and assigned CCB actions. The minutes are used by the CCB Chairperson to direct a person(s) or organization(s) to complete actions assigned by the CCB. Where appropriate, the minutes may include a schedule for verification of change implementation.



7.3 Change Verification

The document owner is the individual designated to be responsible for the content, changes, and records associated with a controlled document. Verification of change implementation is the responsibility of the owner of the document. The CMO shall assist in the verification process. All comments received from a reviewer of a CCR shall be resolved by the CCR owner. Verification is necessary to ensure proper implementation of CCB decisions and to ensure no additional changes were made. CCRs shall remain open until proper and complete implementation of the CCR has been verified.

7.3.1 SGP Controlled Documents

The CMO shall maintain all CM-controlled documents in TDMS and specify the format requirements to be followed when preparing SGP CM-Controlled Documents. Any SGP-controlled documents that have not been formally approved and released shall be marked “DRAFT”. The latest version of the approved controlled document shall be available online in TDMS.

Controlled documents include requirements documents such as Interface Requirements Documents (IRDs), specifications, contract documents, Statements of Work (SOWs), Task Orders, Mission Assurance Requirements (MARs), and Contract Deliverable Requirements Lists (CDRLs).

When a document is determined to be complete, accurate, and ready to be baselined, the owner shall prepare and submit a CCR.

The CMO shall verify completeness of the CCR and publish it for review. The CCB members may review the CCR for concurrence; however, the CCB Chairperson is the required CCR approver. After CCB approval, the appropriate expert (determined by the CCB) shall review the completed document to verify the closure requirements. Approval by the CCB Chairperson shall be obtained before the document is published.

7.3.2 CMO Technical Publications

The CMO shall be responsible for complete technical publications for all documents under SGP CCB control.

Documents that require CCB level approval have been identified by SGP management and are located on the SGP Document Tree. Once the CCB chairperson has approved the changes, the CMO shall publish a final clean version to be posted to TDMS.



Appendix A – Definitions

Approval: A final designation applied by the CCB Chairperson to a CI that shows concurrence, acceptance, and disposition. Chief Safety and Mission Assurance Officer (CSO): A civil servant or contractor who ensures that new documentation and changes to existing documentation does not negatively affect project/program hardware, software, etc. This means that CSOs verify that the documents/changes do not negatively impact a project's/system's reliability or quality, mission success, mission life; do not violate, ignore, change program/project S&MA requirements; do not violate, ignore, change Goddard Space Flight Center (GSFC) S&MA standards, PG's, GPR's that are related to S&MA management, S&MA requirements, risk management; and do not introduce new risks, or if they are introduced, the project is aware of them and tracks/mitigate/accepts them.

Class I Changes: changes that occur when one or more of the following items is affected: 1) Baselined documentation (except for typographical errors, simple clarification, or

other examples of Class II documentation changes); 2) Technical requirements contained in the product configuration items (CI) (form,

fit, function); 3) Contract end items/requirements

Class I changes shall be submitted for Configuration Control Board (CCB) approval and should be limited to those which are necessary or offer significant benefit to the Government.

Class II Changes: changes that do not fall within the definition of a Class I change. Examples of Class II changes are:

1) A change in documentation only (e.g., correction of errors, addition of clarifying notes or views);

2) A minor change in hardware (i.e., substitution with an approved alternative material) which does not affect any item listed under Class I changes;

3) Plans and procedures of a non-technical nature or documents related to information management.

Class II changes written against CM-controlled documents normally do not require a formal CCB process. Once the Chairman has validated the Configuration Change Requirement (CCR), approval can be accomplished out-of-board with the appropriate approvals. The CCR will capture the signatures and identify the change as occurring out-of-board.

Configuration Baseline: configuration of a product or service, formally established at a specific point in time, which serves as a reference for further activities.



Configuration Change Request (CCR): documented request to issue, change, revise, or delete a controlled document.

Configuration Control: the element of CM concerning the systematic proposal, justification, evaluation, coordination, and disposition of approved baselines and changes, and the implementation of approved changes to baseline documentation and products (CIs). Configuration Control Board (CCB): a designated group of technical and administrative individuals who review and recommend disposition of proposed baseline CIs and changes, revisions, or cancellations thereto.

Configuration Control Board Chairperson: the SGP Project Manager or his/her designee, who authorizes the scheduling of all CCB meetings, presides over those meetings, authorizes the establishment of baselines, and finalizes the approval/disapproval decisions on change proposal recommendations.

Configuration Documents: documents that define requirements, specifications, design, build/production, validation, and interfaces of a product or service and require document control action before the document can be issued or altered in any way. Configuration Management (CM): A technical and management process for establishing and maintaining consistency of a product's functional and physical attributes with its requirements, design and operational information throughout its life.

Configuration Item (CI): a designation applied to a product or service that has been determined to be subject to CM requirements. Products include: documents, hardware, software, processed materials, services, or any discrete portions thereof, designated for CM and treated as a single entity in the CM process.

Configuration Management Officer (CMO): The individual responsible for Project Configuration Management procedures, processes, and reporting. The Project CMO is a member of the CCB and shall be responsible for the administrative aspects of the CCB/CCR processes. Contract Deliverable Requirement: an organization’s required deliverable from the Implementation Contractor (IC) that is delivered to the Government and is an agreed upon set of actions and understandings to implement the SGP’s requirements.

Contract Deliverable Requirements Listing (CDRL): an organization’s list of contract deliverables that are required for the project.

Controlled Document - a document that affects the quality of an organization’s product. Controlled documents are those designated as requiring formal document control before they may be changed or released. Controlled Documents List (CDL): an organization’s list of controlled documents, as described in the organization’s document control procedures. The Configuration Management Officer (CMO) is responsible for the configuration management database.

Controlled Documents Tree: a diagram in organizational chart format, depicting each controlled document’s relative position with respect to the Work Breakdown Structure (WBS) element to which it corresponds. Defer - A final designation applied by the CCB Chairperson to a CCR that is being delayed pending some type of action.



Deviation: a specific written authorization, granted prior to the manufacture or testing of an item, to depart from a particular performance or design requirement of a specification, drawing, or document. Requests for Deviations undergo the same approval routing as Class I configuration changes, and are recorded on the CCR form, but are identified as Requests for Deviations. Directive: A policy, procedure and guideline, or instruction that has been approved and published by the appropriate authority. Disapproval: A final designation applied by the CCB Chairperson to a CCR that shows non- acceptance. Document Owner: the Engineer or designee who has technical ownership, or is otherwise responsible for a given document. Effective Date: A designated date on which the document becomes effective.

Expiration Date: The date on every controlled document that indicates when a document becomes obsolete. The expiration date cannot exceed five years from the effective date. For documents that are revised, a new expiration date is determined each time a revision is approved. Government Owner: A NASA Civil Servant or JPL employee who has technical ownership, or is otherwise responsible for a given document. This may be the same as the Document Owner or the element lead, contracting officer, etc. when the Document Owner is a contractor or some other non-NASA employee. Information: A designation applied by the CCB Board members to a CI that shows the members have received and acknowledged the item. Technical Data Management System (TDMS): the online database that contains the SGP library. Revalidation: A process of review and approval of an expiring document for the purpose of extending its expiration date. Review - A designation applied by the CCB Board members to a CI that shows that the members have read, understood, and provided feedback. Waiver: a specific written authorization, granted after the manufacture or testing of an item, to depart from a particular performance or design requirement of a specification, drawing, or other document, but will be considered suitable for use “as is”. Requests for Waivers undergo the same approval routing as Class I configuration changes and are recorded on the CCR form, but are identified as Waivers.

Withdrawn - A final designation applied by the CCB Chairperson to remove a CCR.



Appendix B – Acronyms

ACI Administratively Controlled Information AO Announcement of Opportunity CCB Configuration Control Board CCR Configuration Change Request CDL Controlled Documents List CDR Critical Design Review CDRL Contract Data Requirements List CI Configuration Item CM Configuration Management CMO Configuration Management Officer CO Contracting Officer COR Contracting Officer’s Representative CSO Chief, Safety and Mission Assurance Officer DCN Document Change Notice DM Data Management EAR Export Administration Regulation GPR Goddard Procedural Requirements GSFC Goddard Space Flight Center IC Implementation Contractor ICD Interface Control Document IT Information Technology ITAR International Traffic in Arms Regulations IRD Interface Requirements Document JPL Jet Propulsion Laboratory LOA Letter of Agreement MAR Mission Assurance Requirement MOA Memorandum of Agreement MOU Memorandum of Understanding NASA National Aeronautics and Space Administration NPR NASA Procedural Requirement NRRS NASA Records and Retention Schedule PDR Preliminary Design Review PG Procedural Guideline PM Project Manager PR Purchase Request QA Quality Assurance RDW Requests for Deviations/Waivers RFP Request for Proposal ROM Rough Order of Magnitude SBU Sensitive But Unclassified



SEMP Systems Engineering Management Plan SGP Space Geodesy Project SLR Satellite Laser Ranging SMA Safety & Mission Assurance SOW Statement of Work SRD System Requirements Document SRR System Requirements Review STI Scientific & Technical Information TDMS Technical Data Management System VLBI Very Long Baseline Interferometry WBS Work Breakdown Structure