GXI Instrument Draft CDRL.pdf

418-XO-GXICDRL-0055

GeoXO GXI Contract Data Requirements List (CDRL)

RFI Draft April 12, 2022

Contents

1 Introduction

1.1 Definition of Due Dates/Maturity, Definition of Categories, and Delivery Instructions

1.2 Applicable Documents

1.3 Reference Documents

2 Contract Data Requirements List 3 Data Item Descriptions

3.1 Project Management

PM-01: Project Management Plan PM-02: Weekly Status Reports and Telecon Minutes PM-03: Risk Management Plan (RMP) PM-04: Configuration Management Plan PM-05: Configuration Change Requests, Deviations, and Waivers PM-06: Knowledge Management Plan PM-07: Project Management Status Review – Technical (PMSR-T) PM-08: Spare Parts Plan and List PM-09: Digital Image and Video Records PM-10: Document Tree PM-11: Engineering Design Unit (EDU), Prototype, and Engineering Development Model (EDM) Activities Report

3.2 Resource management

RM-01: Earned Value Management (EVM) Plan RM-02: Financial Reports RM-03: Integrated Program Management Report (IPMR) RM-04: Contract Work Breakdown Structure (CWBS) and CWBS Dictionary RM-05: Integrated Master Schedule (IMS) RM-06: Unit Cost Report RM-07: Task Order Status Report RM-08: Program Management Status Reviews – Business (PMSR-B) RM-09: Integrated Baseline Review (IBR) Package

3.3 System Review

SR-01: System Requirements Review (SRR) / System Definition Review (SDR) Data Package SR-02: Preliminary Design Review (PDR) Data Package SR-03: Critical Design Review (CDR) Data Package SR-04: Pre-Environmental Review (PER) Data Package SR-05: Pre-Shipment Review (PSR) Data Package SR-06: Design Modification Review (DMR) Data Package SR-07: Subsystem / Subcontract / Peer Review Data Packages SR-08: Reserved SR-09: Reserved SR-10: Input to Higher Level Reviews

3.4 Systems Engineering

SE 1: Specifications

SE 1-1: Instrument System Specification

SE 1-2: Detailed Design Specifications SE 1-3: Environmental Verification Specification SE 1-4: Instrument Block Diagrams and Approved or Controlled Drawings SE 1-5: Instrument Description Document (IDD) SE 1-6: Drawing Tree

SE 2: Plans SE 2-1: Systems Engineering Management Plan SE 2-2: System Performance Verification Plan and Compliance SE 2-3: Contamination Control Plan SE 2-4: Field Programmable Gate Array (FPGA) Development Plan SE 2-5: Electrostatic Discharge Control Plan SE 2-6: Single Event Effects Control Plan SE 2-7: Electromagnetic Compatibility (EMC) / Electromagnetic Interference (EMI) Compatibility Plan SE 2-8: In-Orbit Electro-Static Discharge Control Plan SE 2-9: Trend Analysis Plan SE 2-10: Individual Test Plans SE 2-11: Life Test Plan SE 2-12: Image Navigation and Registration (INR) Modeling and Analysis Plan SE 2-13: Engineering Development and Test Plan

SE 3: Procedures SE 3-1: Test and Calibration Procedures SE 3-2: Instrument Assembly and Integration Procedures/Drawings

SE 4: Models, Analyses, and Reports SE 4-1: Mass Properties and Power Report SE 4-2: Thermal Math Models and Reports SE 4-3: Solid Math Model SE 4-4: Structural Math Model and Reports SE 4-5: Radiation Shielding and Dose Analysis Report SE 4-6: Engineering Analysis Reports (EAR) SE 4-7: Trend Reports SE 4-8: Test Reports SE 4-9: Test Reports for Subcontracted Items SE 4-10: System Performance Verification Reports SE 4-11: INR Design Document SE 4-12: Line-of-Sight Math Model and Report SE 4-13: Scanner Controls Math Model and Report SE 4-14: End-to-End INR Simulation Math Model and Report SE 4-15: Radiometric Math Model and Report SE 4-16: Optical Model and Report SE 4-17: Stray Light Model and Report SE 4-18: Life Test Report for Lubricated Mechanisms SE 4-19: Structural, Thermal, and Optical Performance (STOP) Analysis Report SE 4-20: FPGA Design Data Package

SE 5: Calibration SE 5-1: Calibration Program Plan SE 5-2: Ground Processing Algorithm Document SE 5-3: Relative Spectral Response (RSR) Component Measurements and System RSR Analysis SE 5-4: Calibration Data Book SE 5-5: Ground Processing Algorithms Test and Validation Plan SE 5-6: Ground Software Acceptance Plan Input SE 5-7: Instrument Packetized Data SE 5-8: Special Calibration Test Report

3.5 Software

SW-01: Software Management Plan SW-02: Software Maintenance Plan SW-03: Software Requirements Specification SW-04: Software Preliminary Design Review (SWPDR) Data Package SW-05: Software Critical Design Review (SWCDR) Data Package SW-06: Software Design Document SW-07: Software Test Plan SW-08: Software Test Procedures SW-09: Software Test Readiness Review (SWTRR) Data Package SW-10: Software Test Report SW-11: Software Acceptance Review (SWAR) Data Package SW-12: Software Delivery Package SW-13: Software Version Description Document SW-14: Operations, Test, and Maintenance Manual for the Flight Software Development Environment (FSDE) SW-15: Operations, Test, and Maintenance Manual for the Instrument Software Simulator Development Environment (SSDE)

3.6 Integration & Test (I&T)

I&T-01: Transportation and Handling Plan I&T-02: Transportation and Handling Procedures I&T-03: Storage and Test Plan I&T-04: Satellite-level Test Plan for the Instrument I&T-05: Satellite-level Test Procedures for the Instrument I&T-06: Satellite-level Test Report for the Instrument I&T-07: Assembly and Operations Manual for the Lifting and Handling Fixture I&T-08: Operations and Maintenance Manual for the Portable GN2 Purge Cart I&T-09: Operations, Test, and Maintenance Manual for Electrical System Test Equipment (ESTE) I&T-10: Integration and Test Plan I&T-11: Mechanical Ground Support Equipment Maintenance Plan

3.7 Operations

OPS-01: Instrument Telemetry and Command Database OPS-02: Instrument Telemetry and Command Handbook OPS-03: Instrument Operations Handbook OPS-04: Instrument Operations Training Package OPS-05: Instrument Operations Configurable Items

OPS-06: Instrument Post Launch Test Plan and Procedures OPS-07: Instrument Post Launch Test Reports OPS-08: Instrument On-Orbit Anomaly Reports OPS-09: Operations, Test, and Maintenance Manual for the Instrument Hardware Simulator OPS-10: Operations, Test, and Maintenance Manual for the Instrument Software Simulator

3.9 Mission Assurance (MA)

MA 1: System Safety and Mission Assurance

MA 1-1: Mission Assurance Implementation Plan and Compliance Matrix MA 1-2: Reserved MA 1-3: Suppliers List MA 1-4: Use of Inherited Products/Items

MA 2: Quality Management System MA 2-1: Non-Conformance Report - Material Review Board (MRB) MA 2-2: Non-Conformance Report - Failure Review Board (FRB) MA 2-3: Reserved MA 2-4: Inputs for the Orbital Debris Assessment Report (ODAR) and End of Mission Plan (EOMP)

MA 3: System Safety MA 3-1: System Safety Program Plan (SSPP) MA 3-2: Safety Requirements Compliance Checklist MA 3-3: Instrument Safety Assessment Report (ISAR) and Verification Tracking Log (VTL) MA 3-4: Operations Hazard Analysis (OHA) and Verification Tracking Log MA 3-5: Procedures for Payload I&T and Pre-launch Processing MA 3-6: Pre-Mishap Plan MA 3-7: Safety Non-Compliances and Waivers MA 3-8: Mishap Reports

MA 4: Reliability MA 4-1: Reliability Program Plan MA 4-2: Failure Modes Effects and Criticality Analysis (FMECA) and Critical Items List (CIL) MA 4-3: Fault Tree Analysis (FTA) MA 4-4: Parts Stress Analysis Report MA 4-5: Worst Case Analysis (WCA) Report MA 4-6: Reliability Assessments and Predictions MA 4-7: Limited-Life Items List (LLIL)

MA 5: Software Assurance MA 5-1: Software Assurance Plan

MA 6: Workmanship Standards MA 6-1: Workmanship Program Plan MA 6-2: Printed Circuit Board Procurement Plan MA 6-3: Alternate Printed Circuit Board (PCB) Standard Report MA 6-4: Printed Circuit Board Coupon Evaluation Reports MA 6-5: Lot Acceptance and Quality Conformance Testing Results for PCBs

MA 7: EEE Parts MA 7-1: EEE Parts Control Plan

MA 7-2: Master EEE Parts List MA 8: Materials, Processes and Lubrication Requirements

MA 8-1: Materials and Processes Selection, Control, and Implementation Plan MA 8-2: Materials Usage Agreement (MUA) MA 8-3: Materials Identification and Usage List (MIUL) MA 8-4: Additive Manufacturing Control Plan (AMCP) and Additive Manufacturing Part Production Plan (PPP)

MA 9: Government-Industry Data Exchange Program (GIDEP) Alerts and Problem Advisories MA 9-1: Responses to Alerts

4 Acronym List

1 Introduction

This Contract Data Requirements List (CDRL) document defines the requirements for deliverable data to be provided by the GeoXO Instrument Contractor. “Instrument” as referred to in this document applies to GXI.

Section 1.1 includes definitions and instructions for distribution. Section 2 presents the CDRL item by item with due dates. Section 3 provides the Data Item Descriptions (DID) with use and preparation information.

1.1 Definition of Due Dates/Maturity, Definition of Categories, and Delivery Instructions

The following definitions apply to the "DUE DATE, MATURITY" column in the Table in Section 2.

a) DUE DATE:

1) Proposal. Items that are provided with the proposal.

2) CDR, PER, PSR, etc. Critical Design Review, Pre-Environmental Review, Pre-Ship Review, etc., respectively.

3) As Generated. After each initial edition, revision, addition, etc.

4) Monthly. As specified in Section 2 or as modified by the Contracting Officer (CO).

5) Weekly. By Monday 9am ET or as modified by CO.

6) L. Launch Date.

7) DACA. Days After Contract Award. Unless otherwise noted, "days" are to be interpreted as calendar days.

b) MATURITY:

1) Preliminary: The first submission of an item. Applies to milestone deliveries. To be completed with available information as of the time of preparation to meet the due date.

2) Initial: The first submission of an item for deliveries that are periodic – weekly, monthly, etc. To be updated with available information as of the time of preparation to meet the due date.

3) Update: The best up-to-date information available at the time.

4) Final: The complete thorough submission of an item. This does not preclude updating later.

c) NASA Acceptance Code A Approval: Documents in this category require approval by the GSFC Contracting Officer’s

Representative (COR) prior to use by the Contractor.

R Review. Documents in this category require delivery to the Government prior to use and within the time period specified in the "Due Date" column of the Instrument CDRL in Section 2 of this document. They are subject to evaluation by the Government or its designated representatives to determine Contractor effectiveness in meeting contract objectives.

I Information. Data in this category require delivery to the Government within the time period specified in the “Due Date” column of the CDRL in Section 2 of this document for the purpose of determining current program status, progress, and future planning requirements.

The following requirements terminology is used throughout this document:

a) The use of “shall” designates a requirement that must be met.

b) The use of “will” designates a statement of fact or intention of the Government.

c) The use of “may” designates that permission has been granted by the Government.

The Contractor shall transmit items with an “As Generated” due date that are critical to schedule, performance, or interface to GSFC within 48 hours of generation.

Unless specified otherwise, any updates to items of “Final” maturity shall require the same "approval/review" process as was required for the previous submissions.

Receipt of “Approval”, “Review”, and “Information” coded items by the Government shall occur on or before the time specified in the “Due Date” column of the CDRL in Section 2 of this document.

Requirements for re-submission of “Approval” coded items shall be as specified in the letters of disapproval.

For most cases, the Contractor will be required to resubmit the document within 30 days of receiving comments from the Government.

If the Contractor has not received response from GSFC within 60 days of delivery of an “Approval” coded CDRL item (15 days for test procedures), the Contractor may proceed as if the document has been approved.

When Government evaluations of “Review” coded items reveal inadequacies, the Contractor shall correct the documents within 30 days of receiving comments or provide a plan approved by the Government for closing deficiencies.

All Data items shall be delivered in electronic format to the GeoXO portal unless otherwise noted in this document.

Electronic deliverables shall be delivered in the following formats unless otherwise approved by the Government:

a) Text Documents: PDF (searchable) or MSWord.

b) Presentations: PDF (searchable) or PowerPoint.

c) Spreadsheets: Microsoft Excel.

d) Database: Unless specified otherwise, delimited ASCII files accompanied with database schema document defining tables and entries.

e) Schedules: MS Project compatible.

f) Schematics and Drawings: PDF.

g) Photographs: JPEG or current industry standard.

h) Video: Any readily available open standard (e.g., AVI, MPEG).

i) System Specifications in DOORS (DPA, DMA updates) and PDF.

1.2 Applicable Documents

The following documents form a part of this specification to the extent specified herein:

1. Contract Clause XX or NFS

2. NASA’s Federal Acquisition Regulation Supplement 1852.234-2, Earned Value Management System, or Alternate I.

3. Earned Value Management Systems Intent Guideline, EIA-748.

4. Earned Value Management Systems Intent Guideline Appendix A, Compliance Map Template, EIA-

5. NASA Procedural Requirement (NPR) 9501.2, NASA Contractor Financial Management Reporting

6. Integrated Program Management Report (IPMR) DI-MGMT-81861

7. NASA Policy Directive 7120.4, NASA Engineering and Program/Project Management

8. NPR 8000.4B, Risk Management Procedural Requirements

9. NPR 7150.2, NASA Software Engineering Requirements

10. GSFC-STD-7000, GSFC General Environmental Verification Standard

11. NASA-STD-8739.8A Requirements Compliance Matrix (Appendix C)

12. Air Force Space Command Manual (AFSCMAN) 91-710, Range Safety User Requirements

13. NPR 8621.1A NASA Procedural Requirements for Mishap Reporting, Investigating, and

Recordkeeping

14. MSFC-STD-3029, Multi-Program/Project Common-Use Document Guidelines for the Selection of

Metallic Materials for Stress Corrosion Cracking Resistance in Sodium Chloride Environments

15. NPR 2200.2B, Requirements for Documentation, Approval, and Dissemination of NASA Scientific and Technical Information

16. XML Telemetric and Command Exchange (XTCE), Informational Report, Green Book, Issue 2;

CCSDS 660.2-G-2; February 2021

17. XML Telemetric and Command Exchange—Version 1.2, Blue Book, Issue 2; CCSDS 660.0-B-2;

February 2021

18. NASA-STD-8719.24 (with Annex), NASA Expendable Launch Vehicle (ELV) Payload Safety Requirements

19. GEIA-STD-0005-1, Performance Standard for Aerospace and High Performance Electronic Systems Containing Lead-free Solder

20. GEIA-STD-0005-2, Standard for Mitigating the Effects of Tin Whiskers in Aerospace and High Performance Electronic Systems

21. NASA-STD-6016A Standard Materials and Processes Requirements for Spacecraft

22. 410-XO-PLN-0006 GeoXO Risk Management Plan

23. NASA-STD-8719.9 Standard for Lifting Devices and Equipment

24. NASA-STD-6030 Additive Manufacturing Requirements for Equipment and Facility Control

25. ISO/TR 10013 Guidelines for Quality Management System

26. Q9001

27. IPC-2221 Generic Standard on Printed Board Design

28. IPC-601X

• IPC-6011, Generic Performance Specification for Printed Boards, Class 3

• IPC-6012, Qualification and Performance Specification for Rigid Printed Boards, Class 3 (Some

NASA Centers also apply “space” appendix “A")

• IPC-6013, Qualification and Performance Specification for Flexible Printed Boards, Class 3

• IPC-6015, Qualification and Performance Specification for Organic Multichip Module (MCM-L)

Mounting and Interconnecting Structures

• IPC-6018, Microwave End Product Board Inspection and Test, Class 3

• IPC-6012DS, Space and Military Avionics Applications Addendum to IPC-6012D, Qualification and Performance Specification for Rigid Printed Boards

1.3 Reference Documents

The following documents contain information relating to the work required but which do not constitute requirements:

1. GPR 8730.5 Safety and Mission Assurance Acceptance of Inherited and Build-to-Print Products

2. MIL-HDBK-217, Reliability Prediction of Electronic Equipment

3. GSFC-STD-8004 (Draft) Performing a Failure Modes and Effects Analysis

4. Chinese standard GJB/z 299B, Reliability Prediction Model for Electronic Equipment

5. Government Industry Data Exchange Program (GIDEP) Operations Manual (Note: this document is available through http://www.gidep.org).

6. GSFC 500-PG-8715.1.2 AETD Safety Manual

7. HRD5, Handbook for Reliability Data for Electronic Components used in Telecommunications

Systems, Developed by British Telecommunications plc

8. IEC TR 62380 model is based on the Reliability Data Handbook - Universal Model for Reliability

Prediction of Electronic Components, PCBs, and Equipment, published by the International Electrotechnical Commission (IEC)

9. IEEE Std 1413-1998, IEEE Standard Methodology for Reliability Prediction and Assessment for Electronic Systems and Equipment

10. Joseph G. Wohl, “Maintainability Prediction Revisited: Diagnostic Behavior, System Complexity, and Repair Time”, IEEE Transactions on Systems, Man, And Cybernetics, Vol. SMC-12, No. 3, May/June 1982 pp. 241 – 250

11. J-STD-001FS Joint Industry Standard, Space Applications Electronic Hardware Addendum (except Chapter 10 of IPC-J-STD-001F)

12. KNPR 8715.3 KSC Safety Practices Procedural Requirements

13. NPR 8715.3 NASA General Safety Program Requirements

14. MIL-HDBK-472, Maintainability Prediction

15. MIL-STD-756B, Reliability Prediction

16. NASA Fault Tree Handbook with Aerospace Applications

(http://www.hq nasa.gov/office/codeq/doctree/fthb.pdf)

17. NASA/SP-2009-569 Bayesian Inference for NASA Probabilistic Risk and Reliability Analysis

18. NASA/CR-2005-213424 Lubrication for Space Applications

19. NASA-TM-86556 Lubrication Handbook for the Space Industry (Part A: Solid Lubricants, Part B:

Liquid Lubricants)

20. NPD 8720.1, NASA Reliability and Maintainability (R&M) Program Policy.

21. NPR 7120.6, Lessons Learned Process

22. NPR 8705.4, Risk Classification for NASA Payloads

23. NPR 8705.5 Technical Probabilistic Risk Assessment (PRA) Procedures for Safety and Mission

Success for NASA Programs and Projects

24. NSWC-07, The Handbook of Reliability Prediction Procedures for Mechanical Equipment, issued by the Naval Surface Warfare Center Carderock Division, July 31, 2007

25. RIAC-HDBK-217Plus, Handbook of 217Plus Reliability Prediction Models

26. SR-332 Issue 2, Reliability Prediction Procedure for Electronic Equipment, issued by Telcordia

Technologies, September 2006

27. NASA/SP-3406, NASA Integrated Baseline Review (IBR) Handbook

28. GPR-1410.2C, Configuration Management

29. G.1, Financial Management Reporting (GSFC 52.52.242-90)

29. G.8, NASA Contractor Financial Management Reporting (1852.242-73)

30. NASA Integrated Program Management (IPMR) Data Requirements Description (DRD) Guide

31. NPR 7120.5, NASA Space Flight Program and Project Management Requirements

32. NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project

Management Requirements

33. NPR 7120.8, NASA Research and Technology Program and Project Management Requirements

34. Department of Defense Handbook Work Breakdown Structure, MIL-HDBK-881

35. SP-2010-403, NASA Schedule Management Handbook

36. NASA’s Federal Acquisition Regulation Supplement 1842.72, NASA Contractor Financial

Management Reporting

37. 418-XO-RPT-0042, Radiation Environment for Electronic Devices on the GeoXO Series Satellites

38. 400-PG-7120.0.2B, NASA Goddard Flight Projects Directorate Schedule Management Procedures and Guidelines

39. GSFC-STD-1001 Criteria for Flight and Flight Support Systems Lifecycle Reviews

40. NPR 7123.1 Systems Engineering Processes and Requirements

41. GIDEP Operations Manual

42. NASA-STD-8729.1, Planning, Developing and Managing an Effective Reliability and Maintainability

(R&M) Program.

SE 4-3 4.4 Solid Math Model Preliminary: PDR Update:

• CDR

• PER

• FM1 PSR

• As Generated

R

R R

SE 4-4 4.4 Structural Math Model and Reports

Preliminary: PDR Update:

• CDR

• FM1 PER

• PSR for each FM

R R

SE 4-5 4.3.4 Radiation Shielding and Dose Analysis Report

Preliminary: PDR Final: CDR

R R

SE 4-6 2.5

4.1 4.8

7.1.7

Engineering Analysis Reports For formal design reviews: Review – TBS days Update: As Generated

SE 4-7 2.6

7.1.4

Trend Reports Preliminary: PSR for each FM Update: Satellite PSR for each FM Final: End of PLT for each FM

R R R

SE 4-8 4.8

7.1

Test Reports Preliminary: Test + 3 days Final: Test + 30 days

R R

SE 4-9 1.3.7 Test Reports for All Subcontracted Items

Update: As Generated I

SE 4-10 2.1

7.1

System Performance Verification Reports

Update: As Generated per

SE 2-2

Final: PSR of each FM

A

A SE 4-11 4.8 INR Design Document Preliminary: SRR

Update:

• PDR

• As Generated Final: CDR

R

SE 4-12 4.7 Line of Sight Math Model and Report

Preliminary: PDR Update:

• CDR

• FM1 PER

• FM1 PSR

R R

SE 4-13 4.3.5 Scanner Controls Math Model and Report

Preliminary: PDR Update:

• CDR

• FM1 PER

3 Data Item Descriptions

3.1 Project Management

PM-01: Project Management Plan

DATA ITEM DESCRIPTION

1. CDRL No.: PM-01

2. Title: PROJECT MANAGEMENT PLAN

3. Use: Describes how the Project is organized and managed. It provides the management structure, its system of operation, responsible lines of communications, and key personnel assignments.

4. Preparation Information:

General The Project Management Plan shall:

a) Address the overall organization, management approach, and structure of the Project plus its interrelationships with the parent company and the subcontractors, and relationship with the Government.

b) Address interfaces with the Government and with any Government Furnished Equipment (GFE) suppliers.

c) Delineate how the requirements of the Statement of Work (SOW) will be achieved and include a description of planned activities for identifiable SOW requirements.

d) Describe the concept of the nature of the tasks and related potential problems. Discuss the approach to problem avoidance and/or solution.

e) Define the technical, schedule and cost control plan and describe management techniques to be employed in minimizing program costs and schedule impacts for all activities, including controls to be exercised over subcontractors and suppliers.

f) Describe make/buy strategies, acquisition plans, sparing philosophy, Project dependencies, facility requirements, internal review strategies and plans, significant work elements on critical paths, long-lead items.

g) Identify how Contractor’s risk management system and processes are integrated into the daily management, decision making, and strategic direction of the Project and foreseen Government participation in that process.

h) Describe how issues will be identified in a timely manner and at the proper levels.

i) Indicate the need for additional definition of spacecraft interfaces and mission design, and when this information is required to avoid schedule slippage.

j) Identify and list the subsystems and subcontracts that warrant a formal design review process due to their criticality or development risk.

k) Provide contractual procedures proposed for the Project to affect administrative and engineering changes, describing any differences from existing procedures.

l) Describe how and where the program will operate during all phases of the contract.

Organization

a) Provide an organizational chart(s) and sufficient supplemental narrative to describe fully the organization proposed for carrying out the Project showing inter- relationships of technical management, business management, and subcontract management, from lower level through intermediate management to top-level management with detailed explanation of:

1) How and by whom interdepartmental work will be monitored and the authority of the program manager over interdepartmental work.

2) Process to be followed by the program manager in obtaining decisions beyond his/her authority and in resolving priority conflicts for resources and functions not under the program manager’s direct control such as personnel, finances, and facilities.

3) The authority of the Program Manager relative to other ongoing programs and applicable support organizations within the company structure.

4) Discuss the program manager’s control over essential resources and functions necessary to accomplish the work.

b) Discuss the availability of the technical, test, manufacturing and system safety/quality assurance/ reliability/ configuration management personnel required for this program (as indicated in your proposed labor hours).

c) State the number and skillset of persons who would have to be hired and plans to obtain them.

Mission Assurance

a) Discuss and illustrate the proposed Mission Assurance organizational structure, including staffing plans, reporting channels, authority and responsibilities, and management visibility.

b) State the independence of the system safety/quality assurance functions

Schedule

a) Describe how the schedules are developed, maintained, and updated.

b) Explain/describe the schedule administration/control.

c) Explain the internal review cycle of the scheduling process.

d) Explain how subcontract schedules maintained and reported in the master schedule.

e) Explain how internal audits/reviews ensure that scheduling data reported to the Government accurately reflects the work status.

f) Define processes for Schedule Risk Analysis (SRA)

PM-02: Weekly Status Reports and Telecon Minutes

1. CDRL No.: PM-02

2. Title: Weekly Status Reports and Telecon Minutes

3. Use: Program status reviews; system, subsystem, and assembly packaging evaluations; and trouble shooting. This weekly report is intended to be timely and informal and should detail the above topics as changes or problems occur.

The Weekly Status Report shall:

a) Indicate the status of the contract as of close of business the preceding Friday, including a summary of progress made.

b) Address the work completed during the week against the work planned for the week, and address recovery plans if necessary.

c) Detail the work planned for the following week and summarize the work planned for the next month.

d) Include:

1) Technical progress, including significant accomplishments and milestones reached.

2) Problems encountered and proposed corrective action.

3) Indicate any actual or anticipated slip in schedule.

4) Identification of any new Class I or Class II changes.

5) Status of Class I or Class II changes from prior week.

e) Contain:

1) Telecon minutes for the previous week's weekly telecon.

2) Action Item Status for any overdue action items and any action items due in the next two weeks.

3) Status of any open Non-Conformance Reports.

4) Status on any open contract actions, including Special Engineering Analyses.

5) Status on any red risk item.

Beginning one month prior to the start of system I&T activities, the Weekly Status Report shall include an I&T Schedule.

The I&T schedule submitted with the Weekly Status Report shall:

a) Consist of the I&T Manager’s daily working schedule.

b) Contain:

1) Details of the activities accomplished in the previous week (with the exception of the first delivery).

2) Details of work planned for the next two weeks.

c) Be organized by shift when appropriate (if more than one standard shift).

d) Submitted in electronic format (.pdf is acceptable).

PM-03: Risk Management Plan (RMP)

1. CDRL No.: PM-03

2. Title: RISK MANAGEMENT PLAN

3. Use: The Risk Management Plan is the basis for identifying and managing all performance, reliability, schedule, cost, and safety risks on the Contractor’s Project. The identification, characterization, mitigation plan, and mitigation responsibilities associated with specific risks are described and specific risk abatement strategies or contingency planning processes are discussed. “Risk” refers to anything that can prevent a team from meeting the Delivery Order objectives.

The Risk Management Plan shall:

a) Meet the requirements of NPD 7120.4, NPR 8000.4B and 410-XO-PLN-0006.

b) Describe the Contractor’s process for Risk Identification, Risk Analysis, Risk Handling and Risk

Monitoring.

c) Include a process for tracking and reporting risk status and changes.

d) Clearly describe:

1) Overview of the risk management process.

2) Organizational and project team member responsibilities.

3) Membership and operation of the Risk Management Board.

4) Risk identification approach.

5) Risk mitigation planning.

6) Interface of risk management to schedule and financial/cost management.

7) Risk tracking/documentation/status updates.

8) Risk management list reporting.

e) Include risks associated with hardware and software (e.g., technical challenges, new technology qualification, etc.), COTS, system safety, performance, cost, and schedule (i.e., programmatic risks).

f) Identify which tools and techniques will be used to manage the risks.

g) Use the GSFC risk 5x5 definitions as described in Figure 1.

h) Define the process for residual risk acceptance, including approval from the Government.

i) Define the process to quantify the cost and schedule threat of each risk and how these threats may impact the planned budget and schedule.

j) Form risk statements in the condition-consequence format: “Given the [CONDITION], there is a possibility that [INTERMEDIATE CONSEQUENCE] will occur resulting in [CONSEQUENCE].” The condition must be a short and concise fact. The intermediate consequence is the immediate, direct effect from a concern being realized, and as such is an outcome internal to the project or organization that may have implications not immediately apparent to individuals outside the project and that may need further analysis to show its connection to higher level requirements. The consequence is a threat to project or organizational requirements that clearly communicates the impact to stakeholders and individuals that may not have detailed knowledge of the project.

Figure 1 GSFC Risk Matrix Standard Scale

PM-04: Configuration Management Plan

1. CDRL No.: PM-04

2. Title: CONFIGURATION MANAGEMENT PLAN

3. Use: Defines the Contractor’s configuration management system (including policies and procedures) that will be implemented for the Instrument flight hardware.

4. Preparation Information:

The Configuration Management Plan shall:

a) Describe in detail all flight hardware configuration management processes, methods, and procedures the Contractor intends to use on the Instrument.

b) Describe how the Contractor plans to:

1) Accomplish hardware and software configuration management,

2) Achieve consistency between product definition, the product’s configuration, and the configuration management records, and

3) Maintain Configuration Management throughout the applicable phases of the product’s life cycle.

c) Describe the Contractor’s approach, methodology, and application of configuration management principles and practices, including:

1) General product definition and scope.

2) Description of configuration management activities and procedures for each of the following configuration management functions:

i) Configuration planning and management.

ii) Configuration identification.

iii) Configuration Change management.

iv) Configuration status accounting.

v) Configuration verification and audit.

vi) Configuration management of digital data.

vii) Configuration management of software.

3) Organization, roles, responsibilities, and resources.

4) Definition of terms.

5) Programmatic and organizational interfaces.

6) Subcontract flow-down of configuration management.

PM-05: Configuration Change Requests, Deviations, and Waivers

1. CDRL No.: PM-05

2. Title: CONFIGURATION CHANGE REQUESTS, DEVIATIONS, AND WAIVERS

3. Use: To facilitate the orderly processing of engineering change requests to specifications or requirements, changes to plans or procedures, specification deviations, waivers, to appropriate level of review, classification, and approval authority for disposition.

Consistent with the Contractor’s Configuration Management Plan (CMP), the Contractor shall prepare, and submit Configuration Change Requests (CCR) for Government review.

CCRs shall be either Class I or Class II.

In addition to the change description, the CCR shall contain sufficient information in the form of attachments, drawings, test results, etc., to allow the Government to evaluate the total impact of the proposed change. The Government Contracting Officer may direct the Contractor to prepare CCRs under the “Changes” clause of the contract.

A Class I CCR is a change that:

a) Affects any Government Contract requirement, specification, or interface requirement.

b) Affects cost or schedules of end item deliverables to the Government.

c) Impacts Government Furnished Equipment.

d) Affects configuration to the extent that changes would be required to prior deliverables in order to maintain specified performance.

e) Creates a new Single Point Failure possibility.

A change may be classified Class II when it does not fall within the definition of a Class I change as given above. Examples of Class II changes are:

a) A change in documentation only (for example, correction of errors, addition or clarifying notes or views).

b) A minor change in hardware (for example, substitution with an approved alternative material) which does not affect any item listed under Class I changes.

c) Drawing changes that do not affect a baseline, interface, etc.

Class II changes normally do not require Government CCB approval unless they are written against Government CM-controlled documents.

PM-06: Knowledge Management Plan

1. CDRL No.: PM-06

2. Title: KNOWLEDGE MANAGEMENT PLAN

3. Use: To indicate how the Contractor will capture and document the combined knowledge pertinent to the development of the Instrument in a database or other readily available format so that it can used by Project successors (Contractor and Government).

The Knowledge Management Plan shall describe:

a) How lessons learned from Instrument development, integration, and test will be captured.

b) How training will be performed to convey lessons learned as they apply to the development, integration, and test of future flight models.

c) How lessons learned will be captured and applied to subcontractor development of critical subassemblies and assemblies.

d) Overall training plan.

PM-07: Project Management Status Review – Technical (PMSR-T)

1. CDRL No.: PM-07

2. Title: PROJECT MANAGEMENT STATUS REVIEWS – TECHNICAL

3. Use: To evaluate contract status. These reports will be used to provide an opportunity for face-to-face discussions between the Contractor and the Government regarding Project status, plans, and issues. The Contractor provides a management level review of technical, schedule, and programmatic activities to the Government. These reviews will typically address the topics listed below as required. Addition of special topics will be coordinated between Government and Contractor prior to each meeting.

The Project Management Status Review (PMSR) shall:

a) Include all aspects of the contract effort.

b) Occur at a face-to-face meeting with the Government. These meetings will occur at the

Contractor’s facility unless stipulated otherwise.

c) Include:

1) Program Manager’s Assessment and Program Summary.

2) Current organization chart, including names of individuals fulfilling the roles identified and updates as necessary.

3) Report of Key Technical Parameters and trends for each Technical

Performance Metric (TPM). The list of reported Key Technical Parameters will be per mutual agreement with the Government. The parameters presented will be at least to the major component level of the subsystems, e.g.

Mechanisms, Power supplies, heaters, cabling, etc. At a minimum, the TPMs (Current Best Estimate (CBE) and Margin) against the specification for:

i) Mass (Kg).

ii) Operational Peak and Average Power (W).

iii) Survival Peak and Average Power (W).

iv) Pointing knowledge and control error budgets.

v) Average Data Rate (Mbps).

vi) Peak Data Rate (Mbps).

vii) Memory Utilization.

viii) CPU Utilization.

ix) Science metrics that are selected to show the satisfaction and stability of the science performance requirements.

x) Accuracy of the values and units.

xi) Status of margins and contingency.

xii) Volume

4) Technical status for system and subsystem design and development activities, including subcontract technical performance.

5) Design Status (when design work is being accomplished) covering the design activities for the previous month, including schedule and technical status of development, manufacturing status, qualification and test status, issues and concerns, and Configuration Change status:

i) List of Class I in process and approved changes.

ii) List of Class II approved Changes available upon request.

d) Summary of Integrated Master Schedule Status, including a brief description of the status of each subsystem or subassembly along with descriptions of any existing or potential problem areas.

e) Critical path and near critical paths explained along with possible workarounds being considered to maintain the schedule. A slack metric with at least 1 month of aging (prior month slack) will be maintained and provided for major subassemblies and activities.

f) Schedule Risk Analysis (SRA) results, including projected delivery date based on SRA

g) Integration & Test Status such as Test Issues, Test Results, Performance Trends.

h) Verification & Validation status and issues (as required).

i) Mission Assurance status such as summary of MRB actions and status; summary of FRB actions and status; failure investigations and corrective actions.

j) Lower Tier Suppliers Status (as required).

k) A detailed 12-month “rolling-wave” schedule (3 months of actual, plus 9 months of forecast).

l) Metrics summarizing all milestones depicting planned versus actual accomplishments and explanations for variances, e.g., graphic display of planned versus actual cumulative milestone status, xx of 1,000 milestones are behind plan and why, etc. and anticipated approaches for resolution (including, as appropriate, technical issues, manpower and staffing, supplier and subContractor issues, etc.).

m) Problems (problems that are significant in nature, questionable “significance” should be discussed with and determined by the Instrument Manager or COR) encountered during the reporting period, and anticipated approaches for resolution (including, as appropriate, technical issues, manpower and staffing, supplier and subcontractor issues, etc.).

n) Status of open issues and problems from prior reporting periods.

o) Risk Status for top 10 risks including mitigation plans of each.

p) Schedule and Cost Threats summary based on quantified values of all risks with schedule and cost impacts

q) Status of action items as captured in the Master Action Item Database (MAID) with focus brought to those actions which are not closing in a timely manner.

r) PM&P Issues including identification and status of long-lead purchases/acquisitions planned.

Need to expand PM&P Project Management & Planning? Parts and Materials Procurement?

s) Prohibited Materials Compliance Status (as required):

1) GeoXO Product Alert evaluation status.

2) Production Readiness Issues (as required).

t) Significant plans and activities for the following month, including upcoming milestone events depicting critical items of Project status.

u) Contract Status:

1) Summary of current proposals, proposal preparations and expected completion dates.

2) Summary of current and expected Configuration Change Requests (CCRs).

3) Summary of potential future proposals and CCRs.

v) Summary of Task Orders.

1) Status of current task orders and estimated completion dates.

2) Discussion of impediments to timely completion of tasks.

3) Discussion of potential future tasks.

w) CDRL Status Report that includes the following information for each document delivered in accordance with the CDRL or overdue from previous reporting periods:

1) Document Number.

2) Document Title.

3) Scheduled Due Date.

4) Actual Submittal Date.

5) Current Status.

6) List of documents planned for delivery during the next reporting period, listed by document number, title, and scheduled submittal date.

x) Award Fee (AF) Milestone Status.

1) List of Current AF Milestones with current due date and expected completion dates.

2) Summary of issues that may be hindering the timely completion of each AF milestone.

PM-08: Spare Parts Plan and List

1. CDRL No.: PM-08

2. Title: SPARE PARTS PLAN AND LIST

3. Use: To review Contractor’s spares plan and parts list.

The Spare Parts Plan shall:

a) Define and justify the Contractor’s position for the spares proposed for the Instrument.

b) Present the schedule and method for obtaining the spares.

c) Provide a listing of Spare Parts and assemblies.

d) Consider the judicious definition, procurement, and stock of a set of these critical spares to help minimize potential schedule impact created by subsystem failures, by contamination, or by other plausible events or conditions.

For the purposes of this CDRL, the information sought is for parts and assemblies that are not commonly available or may impact schedule if out of stock.

PM-09: Digital Image and Video Records

1. CDRL No.: PM-09

2. Title: DIGITAL IMAGE AND VIDEO RECORDS

3. Use: Program status reviews, system, subsystem, and assembly packaging evaluations, and troubleshooting.

The Digital Image and Video Records shall:

a) Include closeout photographic documentation of all assemblies during the manufacturing process and of the final integrated configuration "as flown."

b) Be of sufficiently high resolution to reasonably support anomaly resolutions.

c) Include images of major subsystems, critical assemblies, the full-up system, and major GSE items.

d) Serve as a record of the build-up of major subassemblies and assemblies; e.g., a typical electronic card, motherboard, electronic subsystem with cover off, etc.

e) Include pictures of environmental test fixtures.

Each image shall:

a) Be identified with a label containing the following information: assembly number, serial number, description (e.g. name of the assembly), date of image, and the supplier's company name.

b) Appropriately fill the digital frame to allow for effective magnification.

c) Be of sufficient resolution to clearly show component placement, part marking, or details that are covered or obscured at subsequent levels of assembly and/or any other operation that renders subsequent inspection impractical.

d) Be of sufficient resolution to permit identification of components and verification of wire routings.

Recorded video shall include:

a) Assembly of the Instrument of sufficient detail to be used for future assembly training and possible failure investigation.

b) Packaging, handling, and movement of major Instrument components.

The Contractor shall archive photographic documentation of the hardware not posted to the GeoXO portal and make it available to the Government upon request.

PM-10: Document Tree

1. CDRL No.: PM-10

2. Title: DOCUMENT TREE

3. Use: For ready reference list of all Instrument and GSE documents.

The Document Tree shall:

a) List all documents for the Instrument.

b) Be organized and identified to serve as a ready reference list.

c) Identify documents by name and number.

d) Include a brief description defining the scope of each document.

PM-11: Engineering Design Unit (EDU), Prototype, and Engineering Development Model (EDM) Activities Report

1. CDRL No.: PM-11

2. Title: ENGINEERING DESGIN UNIT (EDU), PROTOTYPE, AND ENGINEERING

DEVELOPMENT MODEL (EDM) ACTIVITIES REPORT AND DATA PACKAGE

3. Use: The EDU, Prototype, and EDM activities report provides performance assessment to raise confidence in the Instrument design and minimize risk to Flight Model development.

4. Preparation Information:

The EDM Activities Report shall include a comprehensive performance assessment including, but not limited to:

a) Assessment against the objectives of the EDU, Prototype, and EDM development over the Program lifecycle

b) Assessment against performance requirements in the PORD, UIID and GIRD requirements

c) Trending of key parameters during the EDU, Prototype, and EDM development

d) Risks mitigated

e) Design modifications that need to be implemented for the FMs

f) As build parts and material list, highlighting differences from the FM

g) Lessons learned about integration, FSW, GSW, and GPA.

3.2 Resource management

RM-01: Earned Value Management (EVM) Plan

1. CDRL No.: RM-01

2. Title: EARNED VALUE MANAGEMENT PLAN

3. Use: To provide a comprehensive description of the Contractor’s plan for utilizing an EVM System

(EVMS) that complies with the Electronic Industries Alliance (EIA)-748 guidelines.

The EVM Plan shall present the Contractor's approach to comply with the EIA-748 guidelines.

The EVMS description or EVM Plan shall address:

a) Establishing and maintaining the Project Management Baseline (PMB).

b) Processes for changing the PMB through Baseline Change Requests (BCRs).

c) Processes for conducting variance analysis.

d) Processes to determine and implement solutions to resolve the causes of variances.

e) Developing ongoing comprehensive estimates at completion.

f) Flowing down requirements to all applicable subcontracts.

g) Managing technical scope, schedule, cost, and risk.

h) The requirements of NASA’s Federal Acquisition Regulation Supplement (NFS) 1852.234-2 or

Alternate I. Guidelines are available in the Earned Value Management Systems EIA-748 Intent Guide Appendix Compliance Map Template.

RM-02: Financial Reports

1. CDRL No.: RM-02

2. Title: FINANCIAL REPORTS

3. Use: To provide data necessary for:

a) Projecting costs and hours to ensure that cost and labor resources realistically support the Project and its schedules,

b) Evaluating Contractor’s actual cost and fee data in relation to negotiated contract value, estimated costs, and budget forecast data,

c) Planning, monitoring, and controlling Project resources, and

d) Accruing cost in NASA’s accounting system.

The Contractor shall submit Financial Reports on NASA’s 533 series reports, in accordance with the instructions on the reverse of the forms, NASA Procedural Requirements (NPR) 9501.2, NASA Contractor Financial Management Reporting (current version), and additional instructions issued by the contracting officer.

The Contractor shall include in the 533 series Financial Reports, a summary of total contract costs.

The Contractor shall include in the 533 series Financial Reports, a breakdown of hours and costs by WBS element XXX.

The Contractor shall include in the 533 series Financial Reports, a narrative explanation for variances exceeding plus or minus 10 percent between the total direct labor hours (prime and subcontractors) and total estimated cost amount shown in the prior month, and the actual total direct labor hours and actual total cost amount shown in the current month at the total contract level (for example, the “Estimated Cost Hours to Complete” amount shown for June in column 8a in the May NF 533M report and the “Cost Incurred Actual” June total cost amount shown in column 7a in the June NF 533M report) in accordance with Section 3.6 of

NPR 9501.2.

For each variance narrative, the Contractor shall include in the 533 series Financial Reports:

a) Reason(s) for the variance.

b) Impact(s) on the core baseline and/or each individual task order.

c) Specific corrective action(s) being taken or to be taken.

The Contractor shall distribute 533 reports to each addressee indicated in the Contract Clause entitled, "Financial Management Reporting".

The Contractor shall include in the 533 series Financial Reports, at a minimum, cost data (using accruals to match the schedule and earned value management monthly data and end date) by the Contractors element of cost categories and Provisionally-billed and Provisionally-earned but unbilled Fee.

Financial period end date shall reconcile with the schedule status date and the earned value management calendar period end date.

RM-03: Integrated Program Management Report (IPMR)

1. CDRL No.: RM-03

2. Title: INTEGRATED PROGRAM MANAGEMENT REPORT

3. Use: To provide information for: (1) integrating cost and schedule performance data with technical performance measures; (2) assessing the magnitude and impact of actual and potential problem areas causing significant cost and schedule variances; and (3) providing valid, timely Project status information to higher management.

To ensure an integrated approach to Project management, the data provided by this IPMR Data Requirements Description (DRD) is in consonance with the work breakdown structure (WBS), integrated master schedule (IMS), risk management processes, plans and reports (where required), probabilistic risk assessment processes and reports (where required), the cost analysis data requirement (CADRe) (when required), and the monthly/quarterly Contractor financial management reports (533M/Q). The Contractor must be able to reconcile between the 533M/Q and the IPMR. This reconciliation may be included within the required IPMR formats.

The IPMR shall include data pertaining to all authorized contract work, including both priced and un-priced effort that has been authorized at a not-to-exceed amount in accordance with the contracting officer's direction.

The IPMR shall separate direct and indirect costs and identify elements of cost for all direct reporting.

The IPMR period end date shall reconcile with the schedule status date and financial calendar period end date.

The IPMR shall include an electronic signature.

The IPMR shall include Formats 1-7 described below.

Format 1, WBS: Format 1 shall provide data to measure cost and schedule performance by CWBS elements.

Critical/major subcontractor summary level performance measurement data shall be included as an attachment to Format 1. A lower level of reporting may be required for elements that are classified as technical, schedule, or cost risk areas.

Format 2, Organizational Categories: Format 2 shall provide the same data as Format 1, sorted by the Contractor organization. If the Contractor is organized by product, Format 2 is not needed.

Format 3, Baseline: Format 3 shall provide the budget baseline plan against which performance is measured.

It is the baseline report used to track all changes to the PMB.

In addition to the six month…