TSIS2-SC-CDRL-0002_Rev-B_DRAFT-1_Observatory_CDRL_Redlined.pdf

Effective Date: <Entered by CMO>

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

National Aeronautics and Space Administration

Goddard Space Flight Center Greenbelt, Maryland

TSIS2-SC-CDRL-0002, Revision AB

Total and Spectral solar Irradiance Sensor (TSIS)-2 Project, Code 424

Observatory Contract Data Requirements List (CDRL)

DRAFT 1: January 22, 2020

DRAFT

TSIS-2 Observatory CDRL TSIS2-SC-CDRL-0002 Revision AB

Effective Date: <Entered by CMO Upon Release>

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

TSIS-2 Observatory Contract Data Requirements List (CDRL)

Review/Signature/Approval Page

Prepared by:

Michael Rhee Date TSIS-2 Mission Systems Engineer NASA/GSFC, Code 424599

Approved by:

Susan Breon Date TSIS-2 Project Manager NASA/GSFC, Code424

*** Electronic signatures are available on-line at: https://ipdtdms.gsfc.nasa.gov***

Effective Date: <Entered by CMO Upon Release>

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Preface

This document is under the TSIS-2 project configuration control. Once this document is approved, TSIS-2 approved changes are handled in accordance with Class I and Class II change control requirements as described in the TSIS-2 Configuration Management Procedures, and changes to this document shall be made by complete revision.

Any questions should be addressed to:

TSIS-2 Configuration Management Office

NASA GSFC

Code 424 Greenbelt, MD 20771

Effective Date: <Entered by CMO Upon Release>

DRAFT

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Change History Log

Revision Effective Date Description of Changes

(Reference the CCR & CCB/ERB Approval Date)

- 08/07/2019 TSIS2-CCR-0014 – Baseline Release A 11/06/2019 CMO Editorial Change – Per S. Krimchansky – Changed effective date to 11/06/2019; Changed DID CDRL No. SW-1 added “C” to NPR 7150.2 in Reference and Preparation Information Sections per S. Breon email dated 8/7/2019.

B Entered by CMO Entered by CMO

Effective Date: <Entered by CMO Upon Release>

DRAFT

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Table of TBDs/TBRs/TBSs

Item No.

Location Summary Due date

TBD1 Table 3-1 Thermal Math Model (TMM) Due Date TBD

(MM/DD/YYYY)

TBD2 Table 3-1 Structural Math Model Due Date TBD

(MM/DD/YYYY)

Effective Date: <Entered by CMO Upon Release> ii

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Table of Contents

1 INTRODUCTION

2 DEFINITION OF DUE DATES/MATURITY, DEFINITION OF CATEGORIES, AND

DISTRIBUTION INSTRUCTIONS

2.1 DUE DATES/MATURITY - RELATED DEFINITIONS

2.2 CATEGORY - RELATED DEFINITIONS

2.3 MEDIA - RELATED DEFINITIONS

3 TSIS-2 OBSERVATORY CDRL LIST

4 DESCRIPTION OF REQUIRED DATA

APPENDIX A ABBREVIATIONS AND ACRONYMS

List of Tables

Table 3-1. OBSERVATORY CDRL LIST

Effective Date: <Entered by CMO Upon Release>

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

1 INTRODUCTION

This Contract Data Requirements List (CDRL) document defines the requirements for deliverable documentation to be provided by the Total and Spectral solar Irradiance Sensor-2 (TSIS-2) Spacecraft Contractor. Section 2.0 includes definitions and instructions for mailing and/or distribution. Table 3-1 presents the CDRL item by item, with due dates, maturity and category. Section 4.0 provides the Description of Required Data (DRD) a description of each item, which provides the use for the deliverable and the required preparation information.

Except where specifically indicated to the contrary, the formats and drawing standards used shall be those normally used by the TSIS-2 Spacecraft Contractor and by its subcontractors.

Effective Date: <Entered by CMO Upon Release>

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

2 DEFINITION OF DUE DATES/MATURITY, DEFINITION OF

CATEGORIES, AND DISTRIBUTION INSTRUCTIONS

2.1 DUE DATES/MATURITY - RELATED DEFINITIONS

The following definitions apply to the "DUE DATE, MATURITY" column in Table 3-1. Unless otherwise specified, deadlines are in working days.

(a) DUE DATE:

(1) Monthly: Submitted on monthly basis

(2) L: Launch Date

(3) ATP: Authorization to Proceed

(b) MATURITY:

(1) Initial: The first submission of an item, which will be revised and resubmitted at a later date.

(2) Preliminary: An early submission of an item. To be completed as is practicable at the time of preparation. Preliminary submittals are written with the best available current information and are resubmitted when further information becomes available.

(3) Final: The complete, thorough submission of an item for approval, review, or

Information, which to the best of the contractor’s knowledge and intention, will not require further revision or updates. However, this does not preclude updating if later found to be necessary. Any updates shall require the same "approval/review" process as was required for the original submissions.

(4) Current: The delivery is written with the best up-to-date information available at the time.

(5) Update: The delivery is revised with the best up-to-date information available at the time.

Other entries in the "DUE DATE, MATURITY" column are self-explanatory.

2.2 CATEGORY - RELATED DEFINITIONS

The following definitions apply to "Submission Category (CAT)" column in Table 3-1. If separate approval instructions are not specified for separate submission due date/maturity items, then the listed approval instruction applies to all submissions.

Effective Date: <Entered by CMO Upon Release>

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

A Approval: CDRL items in this category require approval by the GSFC Contracting Officer’s Representative (COR) or Contracting Officer prior to use by the contractor.

Receipt by the Government shall occur within the time specified in the "Due Date" column of Table 3-1 of this document. Requirements for re-submission shall be as specified by the Contracting Officer. For most cases the contractor will be required to resubmit the document within 14 calendar days of receiving comments from the Government. If the contractor has not received response from GSFC within 30 calendar days of delivery of a CDRL item, the contractor may proceed as if the document has been approved.

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 Table 3-1 of this document.

They are subject to evaluation by the Government or its designated representatives to determine Contractor effectiveness in meeting contract objectives. Upon submission, the Contractor may proceed with associated work while the Government reviews the submission.

I Information. Data in this category shall be delivered to the Government within the time period specified in the “Due Date” column of Table 3-1 for the purpose of determining current program status, progress, and future planning requirements.

2.3 MEDIA - RELATED DEFINITIONS

All Data items shall be delivered in electronic format to a GSFC TSIS-2 Spacecraft specified web portal unless otherwise noted in Table 3-1. The Contracting Officer, COR, and CM shall be notified of electronic submission of the deliverable by email. Electronic deliverables shall be delivered in the following formats unless otherwise approved by the government:

Text Documents: MSWord Presentations: PowerPoint Spreadsheets: Microsoft Excel Schedules: PDF and MS Project Schematics and Drawings: Design Web Format (DWF) and PDF Photographs: JPEG or current industry standard.

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

Effective Date: <Entered by CMO Upon Release>

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

3 TSIS-2 OBSERVATORY CDRL LIST

Table 3-1 provides the SOW-referenced TSIS-2 Observatory Contract Data Requirements List. The table of contents are listed in the following order:

PM- Program Management

IT- Integration and Test

SE- System Engineering

SW- Software

OO-Flight Operations

LO- Launch Operations

MA-Mission Assurance

Table 3-1. OBSERVATORY CDRL LIST

No. Title Due Date/Maturity CAT

PM-1 Monthly and Weekly Status Reviews As scheduled I

PM-2 Project Management Plan Initial : 30d after ATP Final: 60d after ATP

I A

PM-3 Integrated Master Schedule (IMS)

Prelim: with Proposal I

Rev: 45d after ATP R

Final: 60d after ATP A

Monthly Updates: end of first full calendar week of each month

I

PM-4 ECPs, Deviations, and Waivers Class I, As Generated Class II, As Requested

A I

PM-5 Reserved PM-6 Final Report 30d after PLAR I PM-7 Photographs and Video Monthly or upon request I

PM-8 Configuration Management Plan Final: 60d after ATP A

PM-9 Program Security Plan Prelim: 60d after ATP Final: 30d after PDR

R A

PM-10 Review Data Packages

Agenda: Review - 2 wks Prelim: Review – 1 week Final: Review – 48 hours

I

PM-11 Acceptance Data Package Final: PSR-10 days A

Effective Date: <Entered by CMO Upon Release>

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

IT-1

Integration and Test Plans, Procedures, and As-Run Procedures

Plans:

Prelim: PDR-10 days Rev: CDR-10 days Final: PER-10 days Procedures:

10 days prior to use As-Run: 5 days after activity

IT-2

Packaging, Handling, Storage, and Transportation Plan and Procedures

Prelim Plan: PDR-10 days Plan Rev: CDR-10 days Plan Final: PER-15 days Procedures: 10 days prior to use

I I A A

IT-3 Integration and Test Reports 2 weeks after activity A IT-4 Reserved

IT-5 Test and Operations Logs Rev: at major reviews Final: L + 15 days

I

IT-6

Environmental Verification Plan and Environmental Test Matrix (ETM)

CDR- 2 weeks Updates as required

A A

SE-1 Reserved SE-2 Reserved

SE-3 Analyses Prelim: PDR-10 days Final: CDR- 10 days

I

SE-4

Thermal Math Model, Environmental Back-Loads

Model: TBD Backloads: 1 month prior to each Observatory CDR, PER, and PSR

A

SE-5 Structural Math Model TBD A

SE-6

System Performance Verification Plan and Matrix

CDR- 2 weeks Updates as required

A A

SE-7 Mass Properties Report As Required by LV I

SE-8

Previously Qualified Hardware and Software Report

Final: PDR - 30 days I

SE-9 Reserved

SE-10

Observatory Command and Telemetry Database

Prelim: CDR-5days Final: PER Updates as needed

I

SE-11 Engineering Drawing Trees and Lists Prelim: PDR–15 days Final: CDR–15 days Updates as generated

I

SE-12 Reserved

SE-13 Observatory User’s Manual Prelim: CDR-5days Final: PSR

A

SE-14 Command and Telemetry Handbook Prelim: CDR-5days Final: PER Updates as needed

Effective Date: <Entered by CMO Upon Release>

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

SE-15 Trend Parameter List and Approach Prelim: CDR Final: PER

I A

SE-16 Reserved

SE-17 Gold Rules Compliance Matrix Prelim: PDR Interim: CDR Final: PSR

I I A

SE-18 Simulator User’s Guide (Manual) Prelim: PDR-10 days Rev as generated Final: L + 15 days

I I A

SW-1

Software Development and Management Plan

Final: ATP + 90 days A

SW-2 Software Requirements Specification Prelim: PDR Final: CDR

I A

SW-3

Software Test Plans, Procedures, and Reports

Prelim Plan: PDR Final Plan: CDR Prelim Procedures: TRR–15 d Final Procedures: TRR Final Report: PSR

I I I A I

SW-4

Software Test Readiness Review Data Package

Prelim: TRR – 15d Final: TRR

I I

SW-5

Software Acceptance Review Data Package

Final: PSR I

SW-6 Reserved SW-7 Reserved

SW-8

Software Users Guide and Maintenance Manual

Prelim: CDR Final: TRR – 10 days

I I

SW-9

Software Version Description Document

With each new formal software release

I

SW-10 Software Source Code Upon request I

OO-1

On-orbit Observatory Commissioning Plan

Final: CDR A

OO-2 Reserved

OO-3

On-Orbit Performance and Test Reports

Start at L+1 day Rev daily until Acceptance

I

OO-4

Mission Operations Procedures and Scripts

Prelim: ORR-90 days Revisions as generated Final: ORR – 30 days

I I A

OO-5 Reserved LO-1 Reserved LO-2 Reserved

LO-3 Launch Commit Criteria Prelim: ORR-10 days Final: L-15 days

LO-4 Reserved

Effective Date: <Entered by CMO Upon Release>

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

LO-5

Inputs to the Launch Vehicle Interface Control Document (LVICD)

Initial: L-30 months Update as Required

I

MA-1

Mission Assurance Compliance Matrix

60 days after ATP I

MA-2 Reporting of MRB Actions

Major MRB actions: within five (5) working days of MRB action

A

Minor MRB actions: within five (5) working days of MRB action

R

MA-3 Major Anomaly Report

Initial submission to the project office within 24 hours of occurrence

I

Notice of a change in status within 24 hours of occurrence

I

Proposed closure to the project office prior to closure

A

MA-4 Input to ODAR and EOMP

Preliminary ODAR inputs 15 days prior to mission PDR

I

ODAR interim inputs 60 days prior to mission CDR

I

Final/updated ODAR inputs 90 days prior to PSR

A

Draft EOMP inputs 60 days prior to mission CDR

I

Final/updated EOMP inputs 90 days prior to PSR

A

MA-5 System Safety Program Plan Final version 45 days prior to PDR I

MA-6

Safety Requirements Compliance Checklist

With each Safety Data Package

(CDRL MA-8)

A

MA-7

Operations Hazard Analysis and Hazard Verification Tracking Log

Submit Launch Range Hazardous Procedures 45 days prior to first use

A

MA-8 Safety Data Package (SDP)

SDP I 45 days prior to Mission PDR R

SDP II 45 days prior to Mission CDR R

SDP III 120 days prior to shipment A

MA-9

Hazardous Procedures for Payload I&T and Prelaunch Processing

Payload I&T Hazardous Procedures 7 days before first use

R

Launch Range Hazardous Procedures 10 days after delivery for Project Office Approval

A

Launch Range Hazardous Procedures 45 days prior to first use

Effective Date: <Entered by CMO Upon Release>

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

MA-10 Reliability Program Plan (RPP) Preliminary 30 days prior to SRR R

Final 30 days after SRR R

MA-11 FMECA and Critical Items List

Preliminary 30 days prior to PDR R Updates 30 days prior to CDR and each milestone review through Launch Readiness Review

A

MA-12 Fault Tree Analysis

Preliminary qualitative mission FTA 30 days prior to PDR

R

Final qualitative FTA report 30 days prior to CDR

A

Updates/changes to qualitative mission FTA within 30 days after identification of update/change

A

MA-13

Mishap Reporting and Investigation Process (See MAR 3.3.8 for data description)

Preliminary 30 days prior to PDR R Final 30 days prior to CDR

MA-14 Parts Stress Analysis 45 days prior to CDR R Revisions within 30 days after identification

R

MA-15

Safety Waivers (if applicable) (See MAR 3.3.7 for data description)

Submit preliminary waivers with Phase II SDP.

R

Final waivers must be approved by the Payload Safety Working Group with the Phase III SDP

A

MA-16 Limited-Life Items 30 days prior to PDR A Updates no later than 30 days after identification

A

MA-17 EEE Parts Control Plan 30 days after ATP I

MA-18 As Built Parts List (ABPL) 30 days prior to PSR A

MA-19

Materials & Processes Selection, Control, and Implementation Plan

60 days after ATP I

MA-20

Materials Identification and Usage List

30 days prior to PDR R

30 days prior to CDR A

Updates within 30 days of identification

Effective Date: <Entered by CMO Upon Release>

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

MA-21 Contamination Control Plan

Preliminary 30 days before PDR R

Final 30 days before CDR A

Final thermal vacuum bakeout results provided within 30 days of completion

R

Contamination certificate of compliance with Acceptance Data Package (PM-11)

R

MA-22

Non-destructive Evaluation (NDE) Plan. (If applicable, See MAR 8.3 for description)

30 days prior to PDR I

MA-23

Foreign Object Debris Prevention and Control Plan

Preliminary plan no later than thirty

(30) days prior to SRR

I

MA-24 Software Assurance Plan

Preliminary 30 days prior to SRR I

Submit final plan no later than fifteen

(15) days prior to PDR

I

Submit updates no later than thirty

(30) days prior to implementation

I

MA-25

Alternate Printed Circuit Board Standard Report

Within 30 days of identification R

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

4 DESCRIPTION OF REQUIRED DATA

Title:

Monthly and Weekly Status Reviews

CDRL No.: PM-1

Reference:

SOW Paragraph 4.4.1.6, 4.5 Purpose:

To evaluate contract status. Tabular reports with graphical analyses will be used during discussions between the contractor and the Government regarding project status, plans, and issues. The monthly review includes a monthly schedule report, which depicts and describes the status of the Integrated Master Schedule for the spacecraft or observatory.

Preparation Information The Monthly Status Reviews (MSR) shall include all aspects of the contract effort, and will usually be presented at a face-to-face meeting with the Government. These meetings will occur at the contractor’s facility or by teleconference with email documents, as expressly determined by the Government in coordination with the Contractor. All reports, charts, and other materials to be used for the reviews shall be provided 24 hours prior to each meeting.

The MSR shall include but not be limited to:

Status of all work being performed including appropriate metrics and analyses.

Report of Key Technical Parameters (KTPs) including mass and power budgets, peak and average power budgets, pointing knowledge and control error budgets, their current best estimated, calculated, and/or measured values for all parameters, and trends for each KTP.

The list of reported Key Technical Parameters shall be agreed upon with the Government and may be revised by the Government as the situation dictates. The values to be presented shall be at least to the major component level of the subsystems, e.g. Mechanisms, Power supplies, heaters, cabling, etc. The accuracy of the values and units shall be identified. The status of margins and contingency based on maturity shall be presented.

Trending of key parameters that relate to performance stability, per SE-15.

Descriptions and status of technical issues and the resolutions.

Detailed status of schedule.

Status of project staffing and any shortages.

Milestone Monitoring – The Contractor shall report on the status of progress made toward accomplishing the next major milestone. Each report shall include a cumulative milestone status and a listing of major accomplishments and a discussion of any problems associated with each milestone as well as their resolution.

Status of technical risks.

Changes to design parameters such as weight, power profile, communications, system performance, etc.

Resource allocations and margins (telemetry, commands, power, weight, data storage, processor capability, etc.)

Subcontract technical performance, manpower resources, schedule, and milestone status.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Mission assurance status including non-conformance and failure reports Chief Systems Engineer’s assessment and issues A Monthly Schedule Report, which shall include the following:

1. Master Schedule – The contractor shall provide a Master Schedule chart in a format suitable for viewgraph presentations that summarizes the schedule data and status contained in the IMS. The Master Schedule will depict an overview of the entire FF1effort including design, manufacturing, integration and test through OAR/PLAR.

This chart will be derived directly from the IMS and will include major program milestones such as Preliminary Design Review (PDR), Critical Design Review (CDR), Pre-Ship Review (PSR), etc. The schedule baseline, critical path and schedule reserve should also be clearly identified.

2. Subsystem Overview Schedules – For each subsystem the contractor shall provide a subsystem overview schedule that depicts the subsystem, including design, manufacturing, integration, and test. This chart will be derived directly from the IMS and will include major milestones. The schedule baseline, critical path and schedule reserve should also be clearly identified.

3. Control Milestone Trend Report – The contractor shall provide a control milestone trend chart that consists of the baselined list of control milestones (determined by the contractor and agreed to by the project office) and their baselined and projected or actual completion dates. The report will also contain a list of the control milestones expected to complete during the reporting period, their baselined and projected completion dates, and their current status. Note that changes to the control milestones shall be submitted as part of the monthly report for review and concurrence by the Project Office.

4. Monthly Schedule Analysis Narrative – The contractor shall provide an overall analysis of the schedule position of each element (e.g., spacecraft, instrument). This will contain a brief description of the current status and existing or potential problems. The critical path and near critical paths will be explained along with possible workarounds being considered to maintain the schedule.

The Weekly Status Review shall be by oral teleconference reviewing the developing interim status of the information to be presented at the Monthly. The Contractor shall not hold a weekly status the week an MSR is held.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Title:

Project Management Plan

CDRL No.: PM-2

Reference:

SOW Paragraph 4.1, 4.1.5 Purpose:

Describes how the project is organized and managed by the contractor. It provides the management structure, its system of operation, and responsible lines of communications. The organization chart identifies the contractor's project organization with names, functions, lines of authority, coordination.

Preparation Information This plan shall address the overall organization, management approach, and structure of the contractor’s project plus its interrelationships with the parent company and the subcontractors.

Describe how and where the project will operate during all phases of the contract. This plan shall identify and describe interfaces with the Government.

This plan shall include graphical displays such as flow diagrams, WBS, logic networks, etc., to reduce verbal descriptive material.

This plan shall provide an organizational chart(s) and sufficient supplemental narrative to describe fully the following:

(a) Organization proposed for carrying out the project showing interrelationships of technical management, business management, and subcontract management, from lower level through intermediate management to top-level management with detailed explanation of:

1. The authority of the Project Manager relative to other ongoing projects and applicable support organizations within the company structure. Discuss the Project Manager’s control over essential resources and functions necessary to accomplish the work.

2. How and by whom interdepartmental work will be monitored and the authority of the Project Manager over interdepartmental work.

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

4. The project team members with names and functions.

(b) Implementation approach for the project. Describe in general how the requirements of the Statement of Work (SOW) will be achieved. Identify potential problems related to this work, and your approach to problem avoidance and/or solution. Identify how your risk management system and processes are integrated into the daily management, decision making, and strategic direction of the project. Address the degree to which your proposed personnel and overall management procedures are proven through similar experience. Describe such things as make/buy strategies, acquisition plans, sparing philosophy, project dependencies, facility requirements, internal review strategies and plans, Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

significant work elements on critical paths, long-lead items, and significant milestones down to at least the lowest level of the WBS.

(c) Contractual procedures proposed for the project to effect administrative and engineering changes, describing any differences from existing procedures.

(d) Management techniques to be employed to minimize: 1) project costs and schedule overruns, and 2) risks of violating interface requirements and agreements. Describe associated controls to be exercised over subcontractors and suppliers. Describe how issues will be surfaced in a timely manner and at the proper levels. Identify initial proposed Key Technical Parameters the project will use to monitor and report on (see CDRL PM-1) interface compliance and resource status.

(e) The proposed Safety and Mission Assurance organizational structure, including staffing plans, reporting channels, authority and responsibilities, and management visibility. Discuss whether the technical, test, manufacturing and system safety/quality assurance/ reliability/ configuration management personnel required for this project (as indicated in your proposed labor hours) are presently on your payroll and immediately available for this work. State the number and disciplines/skills of persons who would have to be hired, and plans to obtain them.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Title:

Integrated Master Schedule

CDRL No.: PM-3

Reference:

NPR 7120.5, Program and Project Management Processes and Requirements Purpose:

To track the spacecraft design, build, and I&T status over contract lifetime with a coherent, integrated scheduling tool.

Preparation Information The IMS shall be developed using the Critical Path Method scheduling technique. It will consist of the schedule baseline and the current schedule updated each reporting period. The IMS shall relate actual progress to the baseline and contain the current forecast for the remaining tasks.

The IMS shall be developed and maintained in the release of Microsoft Project at contract award.

The IMS will be used to plan, monitor, communicate issues and control all activities, including pertinent resources and facilities necessary to accomplish assigned tasks in compliance with the TSIS-2 Observatory SOW. The IMS will provide the contractor’s time-phased plan, current status, key milestones, schedule reserve, task interdependencies, and major development phases necessary to accomplish the total scope of work.

It will reflect the minimum schedule reserve margins, as follows:

a) From Confirmation to the beginning of Observatory I&T: One and a half (1.5) months of funded schedule reserve per year;

b) From start of I&T to shipment to launch site (or to planned storage): Two (2) months of funded schedule reserve per year;

c) From delivery to launch site to launch: One (1) week of funded schedule reserve per month.

Schedule will be used to provide management insight into contractor status, potential problem areas and critical path identification which will serve as the basis for evaluating contractor performance. The baseline IMS will be the basis for evaluating the impact of Government-directed changes to the Launch date.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Title:

ECPs, Deviations and Waivers

CDRL No.: PM-4

Reference:

SOW Paragraph 4.3.1 Purpose:

To coordinate and control all Deviations, Waivers and Engineering Change Proposals Preparation Information Consistent with the Contractor’s Configuration Management Plan (CMP), the contractor shall determine the classification level of, 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. For the purposes of this DRD, a Class I CCR is a change that:

a) Affects any Government Contract specification or interface requirement.

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

c) Impacts Government Furnished Equipment.

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

b. 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.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Title:

Final Report

CDRL No.: PM-6

Reference:

N/A Purpose:

To provide a summary of the performance of the contract.

Preparation Information:

The final report shall be written per FAR 1852.235-73

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Photographs and Video

CDRL No.: PM-7

Reference:

SOW Paragraph 4.7.3, 4.10.3 Purpose:

Documents and provides a photographic and video history and real-time capture of the spacecraft build and I&T, and the Observatory I&T and launch site operations.

Preparation Information

A. Still Photography

1. Pictures shall be made at appropriate points in the development of the Observatory.

2. Pictures shall be made of the major subsystems, critical components, the full-up system, and major GSE items. These pictures shall be in color and provided in a digital format on appropriate medium.

3. Pictures of environmental test fixtures shall also be provided.

B. Video

1. Video media (DVD)

Assembly of the Observatory shall be video recorded in sufficient detail to be used for possible failure investigation, including dynamic testing and all lifts and mechanism deployments.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Title:

Configuration Management Plan

CDRL No.: PM-8

Reference:

N/A Purpose:

The purpose of the CM Plan is to enable the government to understand the contractor’s methods for implementing configuration management and to provide a common frame of terminology reference for efficient information exchange between the customer and the supplier.

Preparation Information

The Contractor’s CM Plan shall document and describe the CM organization, including:

1. The functions of Program-level and matrixed staffing in the various business units

2. Data management systems and functions

3. Product configuration identification practices, including nomenclature and numbering systems

4. Change management, including methods of obtaining customer approvals and the role of the

NASA Resident Office

5. Configuration status reporting

6. Internal/external audits

The Contractor shall prepare and provide the following configuration control documentation:

a. CCB status shall be reported at the MSR

b. Engineering Drawings and Change Notices as developed

c. The Configuration Item Identification List (CIIL) and the Computer Software

Configuration Items (CSCIs) and Hardware Configuration Items (HWCIs)

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Title:

Program Security Plan

CDRL No.: PM-9

Reference:

SOW Section 4.1.1 NPR 2810.1A, Security of Information Technology NPR 7120.5E Program Project Management Processes and Requirements NPR 2190.1 NASA Export Control Program Purpose:

The purpose of the Program Security Plan is to address physical, Information Technology (IT), Personnel, and Industrial Security aspects of the program.

Preparation Information Provide a Program Security Plan detailing the complete approach to program security. This plan should address all requirements, including those contained in the SOW. This plan should address Physical, Information/IT, Personnel and Industrial Security, and Asset Protection requirements of the program, and should cover the following areas:

1. It should describe Security Organization and Responsibilities.

2. Describe the Security violation and corrective action program.

3. Describe the Physical Security program (description of area and facility to include floor plans where contracted work will be performed).

4. Describe access control, badge system, guard force (if any), storage facilities, equipment and document/material controls (for sensitive data).

5. Describe the approach to IT security for sensitive systems, including the systems that require connectivity to the Mission Operations Center for readiness testing and rehearsals.

6. It should address the orientation and training program to achieve an effective program.

7. It should describe the approach to handling evolving government security requirements.

8. It should describe all program phases, including Observatory shipping, launch site activities, and contingency plans and operations.

9. It should describe the approach to ensuring security during sensitive development/integration operations related to command authentication and space asset protection.

10. It should describe any risks identified and the proposed mitigation approach.

The Contractor shall define and implement a Command Authentication strategy for the TSIS-2 mission. The Contractor shall produce all documentation required for the design, verification, management and flight of the system. The Contractor shall obtain any certifications necessary for the system.

Housekeeping telemetry data shall include flags for any attempted interference or unauthorized commanding to the Observatory, if flag triggers NASA shall be notified.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Title:

Review Data Packages

CDRL No.: PM-10

Reference:

SOW Paragraph 4.4, 4.4.1.2, 4.4.1.3, 4.4.1.4, 4.4.1.5, 4.4.1.11 NASA GSFC-STD-1001, Criteria for Flight Project Critical Milestone Reviews Purpose:

To document the Contractor’s review materials.

Preparation Information The Contractor shall research the requirements in NASA GSFC-STD-1001, Criteria for Flight Project Critical Milestone Reviews, and prepare an agenda no later than two weeks prior to the meeting for the Government to review, amend, and approve. The material to be presented at the reviews, tailored for the appropriate level of detail and maturity for each review, includes:

System Budgets including updates to mass, power, alignment budgets or total system performance, command/telemetry, data rate, processor memory, and CPU margins.

Determine Probability of Success for Controlled Reentry utilizing detailed analysis of current design performed to the subcomponent level Closure of actions from the previous review Changes since the previous review Spacecraft/Observatory modes, anomaly detection/autonomous response capability, and compliance with sun avoidance requirements Redundancy management Flight software design Pointing accuracy, knowledge, and system jitter analyses Grounding and fusing definitions Risk management items and mitigation plans Identification of special needs such as purge, cleanliness, sensor and instrument stimulus Instrument accommodations Completed Instrument ICDs Flight software architecture Final implementation plans including engineering models, prototypes, flight units, and spares Engineering model/breadboard status: plans, test results and design margins, as appropriate Stress and dynamics design analysis Thermal test and flight predictions Final attitude control system stability analyses.

Qualification/Environmental test plans and test flow at the box, subsystem and system level Integration and Test Plans Contamination Control Plan

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Launch vehicle interfaces Ground System interfaces Observatory Ops concept Preliminary Command and Telemetry Handbook Reliability analyses results: FMEA, worst case analysis, FTA, PRA Mechanical and Electrical Ground support equipment Plans for shipping containers, environmental control and mode of transportation Problem areas/Open items Schedules Program Manager and Chief Engineer assessments and readiness to proceed Trend Reports*

*The trend data shall be graphed with clearly marked axes. The scale of the graphs shall be set such that trends can be clearly identified. The scale of each graph shall be tailored for each parameter for the best clarity. The scale of the graphs shall be readjusted with the range of the data in order to continue identification of trends.

For Mission reviews, the Contractor shall provide the Spacecraft or Observatory portions of the data package, as applicable.

The Contractor shall submit Review Data Packages, for the following reviews:

Spacecraft Kick-Off Spacecraft PDR Spacecraft CDR System Integration Review (SIR) Observatory PER Observatory PSR Mission PDR Mission CDR Operations Readiness Review Mission Readiness Review Safety & Mission Success Review Launch Readiness Review Post Launch Assessment Review

For Test Readiness Reviews, the contractor shall submit a review package that contains, at a minimum, the following information:

Tests planned and success criteria Test facilities Test configuration (flight articles not installed, non-flight articles installed) Software status Test procedure status GSE status

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Open anomalies Open Engineering documentation Open integration and test paperwork Test procedure status Staffing plans Expected results (pre-test analyses and safeguards during test) System safety Schedule Test Readiness assessment summary

Test Readiness Reviews (TRRs) shall be held for major environmental tests and initial Spacecraft and Observatory power-on.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Title:

Acceptance Data Package

CDRL No.: PM-11

Reference:

SOW Paragraph 4.11.2.2 Purpose:

To ensure that the deliverable contract end-items are in accordance with contract requirements prior to Government acceptance.

Preparation Information The Contractor shall provide the following information.

This acceptance data package, as a minimum, shall be comprised of the following Spacecraft/Observatory information:

A. Waivers and deviations to all government documents.

B. As-built configuration list C. Hardware parts lists D. Hardware materials and processes lists E. Test Log Book (including total operating time and cycle records) F. Non-conformance or Open item lists (including reasons for being open) G. Safety compliance data package H. Limited life items listings and status I. Environmental tests results J. Subsystem tests results K. Calibration tests results L. Critical parameters trend data (see SE-15 for details) M. Anomaly reports and FRB disposition information N. Complete as-built drawing package O. Photographic documentation of hardware (pre and post-conformal coating for printed wiring assemblies, box or unit, subsystem, system, harness, structure etc.).

P. Contamination Certificate of compliance (see MA-21 for contamination plan details)

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Title:

Integration and Test Plans, Procedures and As-Run Procedures

CDRL No.: IT-1

Reference:

SOW Paragraph 4.4.1.12, 4.7.1, 4.7.2, 4.7.3, 4.10.3 Purpose:

Provide information and details on how the spacecraft/observatory will be functionally tested at both Contractor facility and at Launch site and how the performance will be verified and the As-Run details showing the results Preparation Information

A. Test Plans The contractor shall provide detailed test plans to be used during Integration and Test at both Contractor facility and at Launch site. Test Plans shall be written at a level above the test procedures and shall provide information sufficient to understand the purpose and methodology of all activities and tests, and to provide the required environmental and configuration controls necessary for successful completion of the test. The plans shall be prepared for each test activity defined in the Performance Verification Plan and shall cover all test operations, interfaces, and performance requirements (e.g., electrical, structural and mechanical, EMC, etc), and shall cover specialized tests such as mechanical function and deployments, environmental exposure tests (e.g., vacuum, vibration), spacecraft calibration, GSE calibration and checkout, and pre-launch end-to-end tests. If integration and tests are conducted in conjunction as part of a “group” test, for example, Limited Performance Test (LPT) or Comprehensive Performance Test (CPT), one test plan may encompass this group. At a minimum, the plans shall contain the following information:

a. Test/integration Objectives

b. Test/integration Methods

c. Applicable Documents and Software

d. Level of assembly at which the test is being performed. Define the required test configuration, including any differences from flight configuration.

e. Test Equipment Configuration, including layout and interconnection of test equipment and articles including the grounding scheme. Location and identification of all measuring points on appropriate schematics and diagrams

f. Test and Integration Equipment and Facility Identification

g. Test Instrumentation

h. Safety Provisions and Cautions, including Identification of hazardous and potentially hazardous situations and operations and abort conditions

i. Environmental and/or other conditions to be maintained, including contamination controls

j. Responsibilities and chain-of-command for test performance

k. Expected results in telemetry and associated caution and warning levels.

n. Data Recording Requirements

o. Data Recording Forms and Tables

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

p. Accept/Reject Criteria

q. Any test phases and profiles

r. List the requirements for the integration/ test procedure and test report development

s. Description of any necessary functional operations required during the test (i.e. a CPT performed at hot and cold during thermal vacuum testing).

B. Test Procedures The Contractor shall produce Integration and Test Procedures corresponding to the agreed upon test sequences as specified in the appropriate Integration and Test plan. These shall include:

1. The objectives

2. Integration / Test requirements

3. Integration / Test limits

4. Pass / Fail criteria

5. GSE and instrumentation

6. Handling procedure

7. Environment

8. Test recording requirements

C. As-Run Test Procedures As-Run Test Procedures shall be all the as-run, red-lined, contractor-format test procedures used during Integration and Testing.

Note: Integration and Test Reports are contained in IT-3.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Title:

Packaging, Handling, Storage and Transportation Plan and Procedures

CDRL No.: IT-2

Reference:

SOW Paragraph 4.9, 4.10.6 Purpose:

1. To understand the Contractor’s role, responsibility, and plans to handle, store, package, and ship the Observatory, separately handled components, Instrument, as well as the supporting equipment.

2. To define how the spacecraft or Observatory can be stored in the event launch is significantly delayed.

Preparation Information

1. The documents shall discuss the plan and all of the step-by-step procedures for the packaging, handling, storage, and transporting of the Observatory or instrument, the spacecraft, spares, and GSE. The PHS&T Plan and Procedures shall contain separate sections for spacecraft and instrument components and assemblies that require special handling, such as batteries and solar panels.

The data provided in the plan shall address the following as a minimum:

A. Description of shipping container.

B. Methods of transporting Observatory and GSE within facilities and between facilities.

C. Transportation handling flows.

D. Bagging and purging requirements.

E. Environmental controls and monitoring equipment.

F. Expected roles and responsibilities of the Contractor and the Government.

G. Staging area plans and diagrams H. Trip planning, schedule of events, transportation/arrangements.

I. Shipping crew support, convoy support, route, contingency plans, permits J. Compliance with local, state, and federal regulations K. Procedures for maintaining contact with the flight hardware L. Off-loading of Observatory at the launch site.

M. Movement between facilities at the launch site.

N. Lifting slings.

O. Electrical and mechanical support equipment general description.

P. Analyses and other processes to support shipping containers, plans, and procedures

The Contractor shall provide procedures, as appropriate, for the above activities.

2. To define how the spacecraft or Observatory can be stored in the event launch is significantly delayed, the contractor shall provide a detailed plan for ground storage of the Observatory. The plan shall describe the following:

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

a. Preparation for storage.

b. Ground storage facilities.

c. Environmental control.

d. Monitoring of critical functions during storage.

e. GSE and testing requirements during storage.

f. Impact of prolonged storage on observatory operational lifetime including expendables.

g. Removal from storage, including retesting requirements.

The plan shall describe the elements necessary for storage durations of three and twelve months.

This plan should assume that the storage occurs at the Observatory level of integration at the Contractor’s plant.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Title:

Integration and Test Reports

CDRL No.: IT-3

Reference:

SOW Section 4.7.1, 4.7.2, 4.7.3 Purpose:

Report the results of all tests identified in the Test Plans (IT-1), including test procedures used, test results, and configuration status of all items under test.

The following shall be included in test reports:

a. Test identification and hardware configuration– for specific test

b. Facility description

c. Reference - applicable test plan, test procedures, and test requirements, test log including the dates of the testing, photographs of test setup, any malfunction reports written during the test d. Test results, to include:

1. Identification of test results which confirmed the expected results as specified in the test plan / procedures or for which variations between actual and expected results were within specified tolerance. For the latter case, actual test results shall be shown.

2. Identification of test results which differ from expected results beyond expected or acceptable limits

3. Identification of any planned test objective or requirement for which actual results were not obtained. Reasons for not meeting the objective/requirement shall be stated.

4. Identification of any false or aberrant results noted during the test or subsequent analyses. Note that any such behavior that can prevent the payload from accomplishing its mission objectives can be a basis for rejection.

d. Recommendations for subsequent actions shall be stated, based on the test results, to include:

1. Redesign of a particular component to enable the payload to meet a specific requirement which was not fulfilled

2. Revision of a system / subsystem specification in cases where the test results disclose ambiguity or conflicting requirements

3. The performance of additional tests where results were not acceptable to fulfill objectives.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Title:

Test and Operations Logs

CDRL No.: IT-5

Reference:

SOW Section 4.7.1 Purpose:

Provides a log of operating hours and key parameter values, starting at component acceptance testing and continuing during the system integration and test phases through the on-orbit commissioning phase.

Preparation Information

Test and Operations Log:

A log shall be maintained of the accumulated spacecraft/observatory operating time. The log shall include the following information, as a minimum:

A. Identification of hardware item B. Serial number C. Total operating time since assembly as a unit D. Total operating time since last failure E. Total additional operating time projected for the unit prior to launch F. Observed value (in sequence) for the reporting interval G. Mechanism activations H. Mechanical switch activations I. Flight Software image/patch version or firmware version used in the subsystem J. Observatory Configuration

This shall be maintained throughout spacecraft (beginning at the component level) and observatory testing, instrument…