Attachment C - CDRL - L1 Series SWIPS 1-11-2023.pdf

Effective Date: January 11, 2024 Expiration Date: January 11, 2029

Check the L1 Series CM tool Server at https://ipdtdms gsfc nasa gov/ to verify that this is the correct version prior to use.

L1SERIES-SWIPS-REQ-0015, Revision - Space Weather Next L1 Series Project, Code 493

Space Weather Next (SW Next) Program

Lagrange (L1) Series Project Solar Wind Plasma Sensor (SWiPS)Contract

Deliverables Requirements List (CDRL)

U.S. Department of Commerce (DOC) National Oceanic and Atmospheric Administration (NOAA) National Environmental Satellite, Data, and Information Service (NESDIS) National Aeronautics and Space Administration (NASA)

GSFC SW Next L1 Series CMO

January 12, 2023

Released

L1 Series Project SWiPS CDRL L1SERIES-SWIPS-REQ-0015, Revision -ii Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

Lagrange 1 (L1) Series Project Solar Wind Plasma Sensor

Contract Deliverables Requirements List (CDRL)

Signature/Approval Page

Originally signed on 1/11/2024 by:

Alejandra Constante SW Next L1 Series STIS Instrument Engineer NASA Goddard Space Flight Center

Originally signed on 1/12/2024 by:

C. Hudson DeLee SW Next L1 Series Instrument Systems Manager

Originally signed on 1/12/2024 by:

J. Timothy Van Sant Project Manager, SW Next L1 Series

L1 Series Project SWIPS CDRL L1SERIES- SWIPS -REQ-0015, Revision -iii Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

Preface

This document is under L1 Series Program configuration control. Once this document is approved, L1 Series approved changes are handled in accordance with Class I and Class II change control requirements as described in the L1 Series Configuration Management Procedure, and changes to this document shall be made by complete revision.

In this plan, all mandatory actions (i.e., requirements) are denoted by statements containing the term “shall.” The terms “may” or “can” denote discretionary privilege or permission; “should” denotes a good practice and is recommended but not required; “will” denotes expected outcome;

and “are/is” denotes descriptive material.

Any questions should be addressed to:

L1 Series Configuration Management Office

NASA/GSFC

Code 493 Greenbelt, MD 20771 iv Check the L1 Series CM tool 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) Revision - January 11, 2024 This document was reviewed and approved at CCR

L1SERIES-CCR-0038 for baseline on January 11, 2024 v Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

Table of Contents

1. INTRODUCTION

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

DELIVERY INSTRUCTIONS

1.1.1 Due Date

1.1.2 Maturity

1.1.3 NASA Acceptance Code

1.2 SWiPS CONTRACT DELIVERABLES REQUIREMENTS LIST (CDRL)

1.3 DATA ITEM DESCRIPTION (DID) OVERVIEW

1.4 DELIVERY INSTRUCTIONS

1.5 CDRL ITEMS OVEVIEW

2. PROGRAM DATA ITEM DESCRIPTIONS

PM-1 PROGRAM MANAGEMENT PLAN

PM-2 WEEKLY STATUS REPORTS AND TELECON MINUTES

PM-3 CONFIGURATION MANAGEMENT PLAN

PM-4 CONFIGURATION CHANGE REQUESTS (CCR) CLASS I

PM-5 PROGRAM MANAGEMENT STATUS REVIEW DATA PACKAGE

PM-6 NASA PROPERTY IN THE CUSTODY OF THE CONTRACTORS

PM-7 CONTRACTOR TASK PLAN

PM-8 DOCUMENT TREE

3. RESOURCE MANAGEMENT

RM-1 EARNED VALUE MANAGEMENT (EVM) PLAN

RM-2 FINANCIAL REPORTS

RM-3 RISK MANAGEMENT PLAN

RM-4 INTEGRATED PROGRAM MANAGEMENT DATA AND ANALYSIS REPORT

(IPMDAR)

RM-5 INTEGRATED BASELINE REVIEW (IBR) PACKAGE

RM-6 CONTRACT WORK BREAKDOWN STRUCTURE AND DICTIONARY

4. REVIEW DATA ITEM DESCRIPTIONS

RVW-1 SYSTEM DEFINITION REVIEW (SDR) DATA PACKAGE

RVW-2 PRELIMINARY DESIGN REVIEW (PDR) DATA PACKAGE

RVW-3 CRITICAL DESIGN REVIEW (CDR) DATA PACKAGE

RVW-4 PRE-ENVIRONMENTAL REVIEW (PER) DATA PACKAGE

RVW-5 PRE-STORAGE/PRE-SHIP REVIEW (PSR) DATA PACKAGE

RVW-6 SUBSYSTEM REVIEW MINUTES AND ACTION ITEMS

RVW-7 RESPONSES TO REQUEST FOR ACTIONS

RVW-8 SUBCONTRACT AND SUBSYSTEM REVIEW DATA PACKAGES

5. SYSTEMS ENGINEERING DATA ITEM DESCRIPTIONS

SE-1 SYSTEMS ENGINEERING MANAGEMENT PLAN

SE-2 ENGINEERING ANALYSES REPORTS

SE-3 SWIPS SYSTEM SPECIFICATION

SE-4 DETAILED DESIGN SPECIFICATIONS

SE-5 THERMAL MATH MODEL AND REPORTS

SE-6 STRUCTURAL MATH MODEL AND REPORTS

vi Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

SE-7 SOLID MATH MODEL

SE-8 INSTRUMENT BLOCK DIAGRAMS, AND APPROVED OR CONTROLLED

DRAWINGS

SE-9 SYSTEM PERFORMANCE VERIFICATION PLAN

SE-10 SYSTEM PERFORMANCE VERIFICATION REPORT

SE-11 PERFORMANCE VERIFICATION PROCEDURES

SE-12 ENVIRONMENTAL VERIFICATION SPECIFICATION

SE-13 ENVIRONMENTAL VERIFICATION REPORTS

SE-14 DIGITAL IMAGE AND VIDEO RECORDS

SE-15 INDIVIDUAL TEST PLANS

SE-16 MAGNETIC CONTROL PLAN

SE-17 COMPONENT AND SUBASSEMBLY TEST REPORTS FOR ALL

SUBCONTRACTED ITEMS

SE-18 EMC/EMI COMPATIBILITY PLAN

SE-19 MAINTENANCE, TEST, AND OPERATIONS MANUAL FOR THE SWIPS

EMULATOR

SE-20 REQUEST FOR USE OF MULTI-MISSION OR PREVIOUSLY DESIGNED,

FABRICATED, OR FLOWN HARDWARE

6. MISSION ASSURANCE AND SAFETY DATA ITEM DESCRIPTIONS

MA 1-1 MISSION ASSURANCE REQUIREMENTS COMPLIANCE MATRIX

MA 1-2 SUPPLIER LIST

MA 2-1 INPUT TO ORBITAL DEBRIS ASSESSMENT REPORT and End of Mission Plan

(EOMP)

MA 3-1 SYSTEM SAFETY PLAN (SSP)

MA 3-2 SAFETY REQUIREMENTS COMPLIANCE CHECKLIST

MA 3-3 OPERATIONS HAZARD ANALYSIS AND HAZARD VERIFICATION

TRACKING LOG

MA 3-4 INSTRUMENT SAFETY ASSESSMENT REPORT

MA 3-5 HAZARDOUS PROCEDURES FOR PAYLOAD I&T AND PRELAUNCH

PROCESSING

MA 3-6 PRE-MISHAP PLAN

MA 4-2 FAILURE MODE, EFFECTS, AND CRITICALITY ANALYSIS, AND

CRITICALITY ITEMS LIST

MA 4-3 FAULT TREE ANALYSIS

MA 4-4 RELIABILITY PREDICTIONS

MA 4-5 LIMITED LIFE ITEMS LIST

MA 4-6 PARTS STRESS ANALYSIS

MA 4-7 WORST-CASE ANALYSES

MA 5-1 SOFTWARE ASSURANCE PLAN

MA 6-1 ELECTROSTATIC DISCHARGE (ESD) CONTROL PLAN

MA 6-2 PRINTED CIRCUIT BOARD (PCB) PROCUREMENT PLAN

MA 6-5 LEAD-FREE CONTROL PLAN (LFCP)

MA 7-1 EEE PARTS CONTROL PLAN

MA 7-2 MASTER EEE PARTS LIST

MA 7-3 RADIATION EFFECTS MITIGATION

MA 7-4 RADIATION SHIELDING AND DOSE ANALYSIS REPORT

vii Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

MA 7-5 SINGLE EVENT FAULT MANAGEMENT PLAN

MA 8-1 MATERIALS & PROCESSES SELECTION, CONTROL, AND

IMPLEMENTATION PLAN

MA 8-2 MATERIALS USAGE AGREEMENT

MA 8-3 MATERIALS IDENTIFICATION AND USAGE LIST

MA 8-4 LIFE TEST PLAN AND FINAL REPORT FOR LUBRICATED MECHANISMS . 89

MA 8-5 ADDITIVE MANUFACTURING CONTROL PLAN (AMCP)

MA 8-6 AM PRODUCTION PLAN (PPP)

MA 9-1 CONTAMINATION CONTROL PLAN

MA 9-2 FOREIGN OBJECT DEBRIS PROGRAM

MA 11-1 GIDEP ALERTS/NASA ADVISORY DISPOSITIONS

MA 11-2 INITIATING GIDEP ALERTS

MA 12-1 END ITEM ACCEPTANCE DATA PACKAGE

7. OPERATIONS DATA ITEM DESCRIPTIONS

OPS-1 FLIGHT TELEMETRY AND COMMAND DATABASE

OPS-2 FLIGHT TELEMETRY AND COMMAND HANDBOOK

OPS-3 OPERATIONS HANDBOOK

OPS-4 GROUND PROCESSING ALGORITHMS TEST AND VALIDATION PLAN

OPS-5 GROUND PROCESSING ALGORITHM DOCUMENT

OPS-6 GROUND SOFTWARE ACCEPTANCE PLAN INPUT

OPS-7 TREND ANALYSIS PLAN AND DATA REPORTS

OPS-8 ON-SITE DATA ANALYSIS REPORTS

OPS-9 MASS PROPERTIES AND POWER REPORT

OPS-10 SWIPS PACKETIZED DATA

OPS-11 INSTRUMENT OPERATIONS CONFIGURABLE ITEMS

8. SOFTWARE DATA ITEM DESCRIPTIONS

SW-1 SOFTWARE MANAGEMENT PLAN

SW-2 SOFTWARE DELIVERY PACKAGES

9. INTEGRATION AND TEST DATA ITEM DESCRIPTIONS

I&T-1 TRANSPORTATION, HANDLING PLAN AND PROCEDURES

I&T-2 POST LAUNCH TEST REPORTS

I&T-3 OBSERVATORY LEVEL TEST PROCEDURES

I&T-4 OBSERVATORY LEVEL TEST REPORT

I&T-5 CALIBRATION PROGRAM PLAN

I&T-6 CALIBRATION DATA BOOKS

10. FPGA DATA ITEM DELIVERABLE

FW-1 FPGA DEVELOPMENT PLAN

FW-2 FPGA DESIGN DATA PACKAGE

11. SWIPS HARDWARE/SOFTWARE DELIVERABLE ITEMS

APPENDIX A ABBREVIATIONS AND ACRONYMS

APPENDIX B RECOMMENDED OPERATING PROCEDURES (ROPS) TEMPLATE 122

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

1. INTRODUCTION

This Space Weather Next (SW Next) Lagrange 1 (L1) Series (L1 Series) Instrument Contract Deliverables Requirements List (CDRL) document defines the requirements for deliverable items to be provided by the L1 Series Solar Wind Plasma Sensor (SWiPS) contractor. All data shall be prepared, maintained/updated, and delivered to the Government in accordance with the requirements specified in the governing contract, delivery order, Statement of Work (SOW), Mission Assurance Requirements (MAR), and this CDRL and its associated Data Item Descriptions (DIDs).

1.1 DEFINITION OF DUE DATES/MATURITY, DEFINITION OF CATEGORIES,

AND DELIVERY INSTRUCTIONS

The following definitions apply to the "Delivery" column in Error! Reference source not found.

1.1.1 Due Date

a. Proposal: Items that are provided with the proposal.

b. CDR, PER, etc.: Critical Design Review, Pre-Environmental Review, Pre-Ship Review, etc.

c. As Generated: After each initial edition, revision, addition, etc. Monthly: Monthly by the 15th of each month or as required or as modified by CO

d. Weekly: Weekly status reports by Tuesday close of business or as modified by Contracting Officer (CO)

e. L: Launch Date

f. DACA: Days after contract award

g. MACA: Months after contract award

h. NLT: No later than

i. Authorization to Proceed: ATP

Unless otherwise noted, the data in the due date column titled "days" are to be interpreted as calendar days.

1.1.2 Maturity

a. Preliminary: The initial submission of an item. To be completed with available information as of the time of preparation for the due date.

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

c. Final: The complete thorough submission of an item for approval, review, or information. This does not preclude updating later.

1.1.3 NASA Acceptance Code

A Approval: Documents in this category require approval by the Goddard Space Flight Center (GSFC) Contracting Officer’s Representative (COR) prior to use by the contractor. If the Government disapproves, the requirement for resubmission by the Contractor shall be as specified by the Government Contracting Officer. Normally, the requirement for resubmission will be within 30 days of receiving the Government’s

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

comments. If the Government does not provide comments in the prescribed time, the Contractor may proceed with the associated work after notifying the Government of the intention to proceed.

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 this document.

They are subject to evaluation by the Government or its designated representatives to determine Contractor effectiveness in meeting contract objectives. Following submission, the Contractor may proceed with the associated work. Starting when the Government receives the document, the Government Contracting Officer may provide written (electronic) comments within 21 calendar days. When the Government identifies a deficiency, the Contractor shall re-submit within 30 calendar days of receiving Government comments (3 days for Spacecraft-level test and calibration/validation procedures) or provide a plan within 7 calendar days (1 day for test calibration/ validation procedures), as specified by the Government Contracting Officer, for approval by the Government to close the deficiency.

I Information: Data in this category require delivery to the Government within the time period specified in the “Due Date” column of the SWiPS Contract Deliverables Requirements List for the purpose of determining current program status, progress, and future planning requirements. The Government Contracting Officer may provide written (electronic) comments within 21 calendar days to identify errors and omissions, and the Contractor shall make the corrections and re-submit as specified by the Government Contracting Officer. The Contractor shall address Government comments in the next version delivered, or in a revised version if it is the final delivery

1.2 SWiPS CONTRACT DELIVERABLES REQUIREMENTS LIST (CDRL)

Items with an “As Generated” due date that are critical to schedule, performance, or interface shall be transmitted to GSFC by within 48 hours of generation.

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

All Data items shall be delivered in electronic format to a GSFC L1 Series specified web portal unless otherwise noted in the SWiPS Contract Deliverables Requirements List.

Individual CDRL items may be combined with other CDRL items to increase documentation efficiency if the content and requirements of the CDRL items are satisfied.

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

a. Text Documents: PDF (searchable) or MS Word

b. Presentations: PDF (searchable) or PowerPoint

c. Spreadsheets: Microsoft Excel

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

d. Database: Delimited ASCII files accompanied with database schema document defining tables and entries.

e. Schedules: MS Project

f. Schematics and Drawings: PDF

g. Photographs: JPEG or current industry standard.

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

1.3 DATA ITEM DESCRIPTION (DID) OVERVIEW

Each CDRL item is defined by a corresponding DID. The DID includes the title, number, SOW reference, purpose, applicable documents, and required preparation information.

Much of the required information specified in the DIDs may already exist in the Contractor’s documentation. In those cases, existing documents and formats should be used if they meet the intent of the DID requirements. If so, a notation shall be supplied in the deliverable which indicates where in the Contractor’s document the information that satisfies the requirement can be found.

1.4 DELIVERY INSTRUCTIONS

a. The Contractor shall deliver each CDRL item via the media indicated below in accordance with the schedule and any special instructions indicated in Table 2 and/or the corresponding DID, and in accordance with the contract or mission-specific Delivery Order (DO) requirements and provisions.

b. All CDRL items shall be delivered electronically (one electronic copy for each CDRL item) to an electronic library designated by the Government. If all or a portion of a CDRL item is not well suited for electronic delivery, the item may be delivered via hard copy upon mutual agreement between the Contractor and the Government.

c. Upon submitting each CDRL item, the Contractor shall notify via email the Government Contracting Officer (CO), the CO Representative, and the Data Management Office.

1.5 CDRL ITEMS OVEVIEW

Table 1 provides a list of CDRL item categories as follows:

a. Item # An alpha-numeric identifier for each CDRL item category and its respective DID.

The alpha descriptor is based on the subject matter of the deliverable:

Table 1 Alpha-numeric identifiers for each CDRL

PM Program Management RM Resource Management

RVW Reviews SE Systems Engineering MA Mission Assurance and Safety OPS Operations SW Software

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

I&T Integration and Test FW FPGA Development Plan

b. Requirements Reference: The reference indicates the section of the L1 Series Instrument

SOW, IMAR, and/or Instrument Requirements Specification (SPEC) where the CDRL item is called out.

c. Title (self-explanatory)

d. Delivery: The contract baseline schedule of delivery for the CDRL item. Many of the dates are referenced to reviews or other milestones. Unless stated otherwise, days are calendar days.

e. Flight Model: This column describes if a deliverable is required for the first flight model (FM1), the second flight model (FM2), or both flight models.

f. Purpose: The purpose of the CDRL item submission (i.e., The Government’s role following receipt of a CDRL item) is based on the definitions below. The designation for an item applies to all submissions (e.g., preliminary/initial, update, final) of that item unless noted otherwise. UAR indicates Update as Required with the approval letter indicated in the parenthetical. An A, R, or I indicate the delivery is required, with the Government’s role following a receipt as indicated.

Table 2 L1 Series SWiPS Contract Deliverables Requirements List (CDRL)

CRDL No. SOW Title Delivery Flight Model

Purpose

PM-1 4.1. Program Management Plan

Preliminary: 30 DACA Final: PDR+14 days

Both R

PM-2 4.1 Weekly Status Reports and Telecon Minutes

Weekly Both I

PM-3 4.4.1 Configuration Management Plan

Preliminary: 15 DACA Final: PDR + 14 days

FM1 A

PM-4 4.4.1 Configuration Change Requests (CCR) Class I

As generated Both A

PM-5 4.1

4.5.9

Program Management Status Review Data

Package

Bi-monthly Both I

PM-6 4.2 NASA Property in the Custody of the

Contractors

Per Contract Clause 1852.245-73, Oct. 15, of each contract year for prior year. Final at contract closeout..

Both R

PM-7 4 Contractor Task Plan Per the contract ordering mechanism for Special Studies (only required once a special study is requested/awarded)

Both R

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

CRDL No. SOW Title Delivery Flight Model

Purpose

PM-8 4.1 Document Tree Preliminary: PDR Final: CDR

Both R

RM-1 4.3.1 Earned Value Management (EVM)

Plan

Initial Submission:

In accordance with NFS 1852.234-2, or

Alternate I, 60 DACA Frequency:

Revised EVMS description or plan as directed

Both A

RM-2 4.3.4 Financial Reports:

533 M Package 533 Q Reports

Initial Submission:

533M package shall be submitted 30 DACA.

533Q Reports: shall be submitted after the initial 533M and contain a full fiscal year estimate by quarter Frequency:

533M are due NLT 10 working days following the close of the contractor’s monthly accounting period, unless otherwise specified in the contract.

The 533Q reports shall be distributed NLT the 15th day of the month preceding the quarter being reported.

RM-3 4.3.4

4.9

Risk Management (RM) Plan

Initial Submission:

60 DACA

Frequency:

Revised RM description or plan within 30 days after contractor internal approval or as directed by Contracting Officer.

Update:

The Risk Report shall be updated monthly or more frequently, as required. A review copy shall be provided to the Government at least 24 h in advance of Monthly Risk Management

Board Meetings.

RM-4 4.3.5 Integrated Program Management Data and

Analysis Report

(IMPDAR)

Initial Submission:

The IMPDAR authoritative data (CPD, Schedule, and Performance Narrative) shall be submitted NLT 16 business days after the end of the first full accounting period following the

ATP.

Frequency:

Microsoft Project or Native Schedule and SPD by the 5th business day after the contractor’s accounting month ends.

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

2. PROGRAM DATA ITEM DESCRIPTIONS

PM-1 PROGRAM MANAGEMENT PLAN

Title:

Program Management Plan

DID for CDRL No.

PM-1

Reference:

SWiPS SOW Section 4.1 Purpose:

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

1. The Program Management Plan shall address the overall organization, management approach, and structure of the SWiPS Program plus its interrelationships with the parent company and the subcontractors, and relationship with the Government.

2. The Program Management Plan shall delineate how the requirements of the Statement of Work (SOW) will be achieved and include a description of planned activities for identifiable SOW requirements.

3. The Program Management Plan shall address interfaces with the Government and with any Government Furnished Equipment (GFE) suppliers.

4. The Program Management Plan shall indicate critical paths, long-lead items and significant milestones down to the lowest level of the WBS.

5. The Program Management Plan shall indicate the need for additional definition of spacecraft and mission information, and when this information is required to avoid schedule slippage.

6. The Program Management Plan shall include graphical displays such as flow diagrams, WBS, logic networks, etc., to reduce verbal descriptive material.

7. The Program Management Plan shall provide an organizational chart(s) and sufficient supplemental narrative to describe fully the organization proposed for carrying out the program 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:

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

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

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

c. Process to be followed by the program manager in obtaining decisions beyond his/her authority and in resolving priority conflicts for resources and functions

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

not under the program manager’s direct control such as personnel, finances, and facilities.

d. The lead program team members with names, functions, and qualifications

8. The Program Management Plan shall provide contractual procedures proposed for the program to effect administrative and engineering changes, describing any differences from existing procedures.

9. The Program Management Plan shall describe management techniques to be employed in minimizing program costs and schedule impacts, including controls to be exercised over subcontractors and suppliers.

10. The Program Management Plan shall describe how issues will be surfaced in a timely manner and at the proper levels.

11. The Program Management Plan shall describe how supply chain performance will be tracked.

12. The Program Management Plan shall discuss and illustrate the proposed SWiPS Mission Assurance organizational structure, including staffing plans, reporting channels, authority and responsibilities, and management visibility.

13. The Program Management Plan shall discuss whether the technical, test, manufacturing and system safety/quality assurance/ reliability/ configuration management personnel required for this program (as indicated in your proposed labor hours) are presently on payroll and immediately available for this work.

14. The Program Management Plan shall state the number and kind of persons who would have to be hired and plans to obtain them.

15. The Program Management Plan shall describe how the schedules are developed, maintained and updated.

16. The Program Management Plan shall describe how subcontracts will be managed and reviewed and describe the performance milestones of each.

17. The Program Management Plan shall list and describe the planned subsystem reviews.

PM-2 WEEKLY STATUS REPORTS AND TELECON MINUTES

Title:

WEEKLY STATUS REPORTS AND TELECON MINUTES

DID for CDRL No.

PM-2

Reference:

SWiPS SOW Section 4.1 Purpose:

Contract status evaluation.

Preparation Information:

1. The Weekly Status Report shall indicate the status of the contract as of close of business the preceding Friday, including a summary of progress made.

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

2. The Weekly Status Report shall address the work completed during the week against the work planned for the week, and address recovery plans if necessary.

3. The Weekly Status Report shall include technical progress, including significant accomplishments and milestones reached.

4. The Weekly Status Report shall include problems encountered and proposed corrective action.

5. The Weekly Status Report shall indicate any actual or anticipated slip in schedule.

6. The Weekly Status Report shall include identification of any Class I or Class II changes.

7. The Weekly Status Report shall detail the work planned for the next week and summarize the work planned for the next month.

8. The Weekly Status Report shall contain Action Item Status for any overdue action items and any action items due in the next two weeks.

9. The Weekly Status Report shall contain status of any open Non-Conformance Reports.

10. The Weekly Status Report shall contain status on any open contract actions, including Special Engineering Analyses.

11. The Weekly Status Report shall contain status on any red risk item.

Note: This weekly report is intended to be timely and informal and should detail the above topics as changes or problems occur.

PM-3 CONFIGURATION MANAGEMENT PLAN

Title:

CONFIGURATION MANAGEMENT PLAN

DID for CDRL No.

PM-3

Reference:

SWiPS SOW Section 4.4.1 Purpose:

To define the contractor’s configuration management system and provide a means of control for all changes affecting form, fit, or function and any impact on performance, cost or schedule.

Preparation Information:

1. The Configuration Management Plan shall describe the scope, approach, methods, and procedures of the system used to control changes of requirements, design, and any other configuration managed item.

2. The Configuration Management Plan shall describe the organization of the configuration management program and how it relates to the rest of the SWiPS program.

3. The Configuration Management Plan shall list all tools used for configuration management.

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

4. The Configuration Management Plan shall use the following product change classifications:

a. A change or request for Deviation/Waiver is classified as Class I when it affects one or more of the following factors:

i. Program baseline documentation

ii. Technical requirements contained in the product configuration identification, including the following:

1. Form, fit, or function

2. Performance

3. Power

4. Reliability outside stated requirements

5. Weight, balance, moment of inertia

6. Interface characteristics

7. Hardware and process qualifications

iii. Non-technical contractual provisions

1. Fee

2. Incentives

3. Cost

4. Schedule

5. Guarantees or deliveries

iv. Other factors

1. Government-furnished property (GFP)

2. Safety

3. Electromagnetic characteristics

4. Deliverable operational, test, or maintenance computer programs

5. Compatibility with support equipment

b. A change is classified as Class II when it does not fall within the definition of a Class I change.

PM-4 CONFIGURATION CHANGE REQUESTS (CCR) CLASS I

CONFIGURATION CHANGE REQUESTS (CCR) CLASS I

DID for CDRL No.

PM-4

Reference:

SWiPS SOW Section 4.4.1

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

Purpose:

Class I changes are to be used as a vehicle for orderly processing of change requests to appropriate level of approval authority for disposition.

Preparation Information:

Class I Configuration Change Requests shall document proposed changes impacting form, fit, function, cost, schedules or performance per the Configuration Management Plan or per the Software Configuration Management Plan section of the Software Management Plan.

PM-5 PROGRAM MANAGEMENT STATUS REVIEW DATA PACKAGE

PROGRAM MANAGEMENT STATUS REVIEW DATA PACKAGE

DID for CDRL No.

PM-5

Reference:

SWiPS SOW Section 4.1 and 4.5.9 Purpose:

To summarize the progress since the previous Program Management Status Review.

Preparation Information:

The Program Management Status Review Data Package shall include the following items:

1. Accomplishments since last review, including 20 milestone events depicting critical items of program status for the succeeding two months with a report on the previous two months milestone events

2. Schedule

3. Technical issues and concerns, including summaries of technical progress and descriptions of the current technical issues and concerns

4. Business issues and concerns, including personnel changes

5. Open contract items

6. Open action items

7. Planned effort for next review period

8. Reliability and quality assurance information

9. Mass properties and power summary

10. Software metrics for each Class A, B or C Computer Software Configuration Item (CSCI) including:

a. Number of software requirements and their change status

b. Number of software change requests and problem reports and their status

c. Resource utilization estimates and measurements of memory, CPU and I/O Bandwidth

11. Financial summary including a summary of actuals versus planned manpower

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

12. Subcontractor status including:

a. Efforts under contract

b. Efforts waiting contract award

c. Changes to first tier and sub-tier contractors

d. Change orders, problems, issues

e. Pending subcontractor consent packages

f. Supply chain performance will be tracked using the table below, updated bi-monthly. This includes items 12. a. through 12. e. for subcontracts.

Part Description

Supplier Leadtime

Original Date

(on contract)

Delivery Date

Need date

Slack (days)

Affected Constraint

T ec hn ic al

S ch ed ul e

C on tr ac t

13. A list of actions requested of GSFC management

14. Update of corporate changes, for example: early warning of

a. Restructuring activities (including internal reorganizations)

b. Indirect/direct rate changes

15. Risk assessment including approach for mitigation

16. Any additional data requested by GSFC

PM-6 NASA PROPERTY IN THE CUSTODY OF THE CONTRACTORS

Title:

NASA PROPERTY IN THE CUSTODY OF THE CONTRACTORS

DID for CDRL No.

PM-6

Reference:

SWiPS SOW Section 4.2 Purpose:

For budget, cost, and property control Preparation Information:

The NASA Property in the Custody of the Contractors report shall consist of NASA Form 1018 in accordance with NFS 1845.505-14, the instructions on the form, subpart 1845.71, and any supplemental instructions for the current reporting period issued by NASA.

PM-7 CONTRACTOR TASK PLAN

Title: DID for CDRL No.

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

CONTRACTOR TASK PLAN PM-7

Reference:

SWiPS SOW Section1.1 Purpose:

The task plan is the contractor's resources plan for accomplishing the work described in the task order.

Preparation Information:

The Contractor Task Plan shall be prepared in accordance with the contract ordering mechanism for Special Studies.

PM-8 DOCUMENT TREE

DOCUMENT TREE

DID for CDRL No.

PM-8

Reference:

SWiPS SOW Section 4.1 Purpose:

For ready reference list of all SWIPS and GSE documents.

Preparation Information:

1. The document tree shall list all documents for the SWiPS and separately for the GSE.

2. The document trees shall be organized and identified to serve as a ready reference list.

3. The document tree shall identify documents by name and number.

4. The document tree shall include a brief description defining the scope of each document

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

3. RESOURCE MANAGEMENT

RM-1 EARNED VALUE MANAGEMENT (EVM) PLAN

EARNED VALUE MANAGEMENT (EVM) PLAN

DID for CDRL No.

RM-1

Reference:

SWiPS SOW Section 4.3.1

Purpose:

To provide a comprehensive description of the contractor’s plan for utilizing an earned value management system (EVMS) that complies with the Electronic Industries Alliance (EIA)-748 guidelines.

Preparation Information:

1. The EVMS description or plan shall present the contractor's approach to comply with the EIA-748 guidelines.

2. The EVMS description or plan shall address the processes for conducting variance analysis; developing ongoing comprehensive estimates at completion; flowing down requirements to all applicable subcontracts; and managing technical scope, schedule, cost, and risk.

3. The EVMS description or plan shall address the requirements of NASA’s Federal Acquisition Regulation Supplement (NFS) 1852.234-2 or Alternate I.

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

5. Contractor-selected Format are acceptable

Applicable Documents:

Industry Guidelines for Earned Value Management Systems, EIA-748-D Earned Value Management System, NFS 1852.234-2 (or Alternate I) Earned Value Management System, EIA-748-D Intent Guide Appendix Compliance

Map Template

RM-2 FINANCIAL REPORTS

FINANCIAL REPORTS

DID for CDRL No.

RM-2

Reference:

SWiPS SOW Section 4.3.4 Purpose:

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

To provide data necessary for:

a. Projecting cost 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.

d. Accruing cost in NASAs accounting system.

Preparation Information:

Financial management reports shall be submitted by the contractor on NASA’s 533 series reports, in accordance with NASA Procedural Requirements (NPR) 9501.2, NASA Contractor Financial Management Reporting (current version), and additional instructions issued by the contracting officer. The following information is required for all 533 series reports:

1. Level of Detail: The contractor’s 533 reports shall contain a summary of total contract costs and per the level specified in the WBS and WBS Dictionary DID (RM-

6) and contract modifications. The reports shall contain a breakdown of hours and costs by the elements of cost categories listed in bullet item (d) below.

2. Variance Narrative Reporting: In accordance with Section 3.6 of NPR 9501.2, the contractor shall include a narrative explanation for variances per items identified 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). Each variance narrative shall explain the: (1) reason for the variance, (2) impact(s) on the core baseline and/or each individual task order, and (3) specific corrective action(s) being taken or to be taken.

3. Distribution: The contractor shall distribute 533 reports to each addressee indicated in the contract clause entitled, "Financial Management Reporting." The contractor shall submit an initial report in the NF 533M format within 30 working days after contract award. After the initial report, the NF 533M reports shall be distributed not later than the 10th working day following the close of the contractors' monthly accounting period. The 533Q reports shall be distributed not later than the 15th day of the month preceding the quarter being reported.

4. Reporting Requirements: Each individual report shall, at a minimum, provide cost data (using accruals to match the schedule and earned value management monthly data and end date) by the following elements of cost (EOC) categories and summaries:

a. Prime direct labor hours:

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

i. Prime direct labor hours – onsite

ii. Prime direct labor hours – offsite

iii. Total prime direct labor hours

b. Subcontractor direct labor hours:

i. Subcontractor A direct labor hours – onsite (include once for every subcontractor)

ii. Subcontractor A direct labor hours – offsite (include once for every subcontractor)

iii. Total subcontractors direct labor hours

c. Total prime and subcontractors direct labor hours:

i. Total prime and subcontractors hours – onsite

ii. Total prime and subcontractors hours – offsite

iii. Total prime and subcontractors direct labor hours

d. Prime direct labor costs:

i. Prime direct labor costs – onsite

ii. Prime direct labor costs – offsite

iii. Total prime direct labor costs

e. Prime overhead expenses:

i. Onsite overhead

ii. Offsite overhead

iii. Total prime overhead

f. Other direct costs (ODC):

i. Subcontracts (list separately, Subcontractor A, B, C, etc.)

ii. Material

iii. Travel

iv. Other (specify)

v. Total ODCs

g. Subtotal (direct labor, overhead, and ODCs)

h. General and Administrative expense

i. Total estimated cost

j. Fixed fee

k. Total cost-plus-fee

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

5. Financial Period End Date: Financial period end date will reconcile with the schedule status date and the earned value management calendar period end date.

NPR 9501.2, NASA Contractor Financial Management Reporting

NASA’s Federal Acquisition Regulation Supplement 1842.72, NASA Contractor Financial Management Reporting

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

G.8, NASA Contractor Financial Management Reporting (1852.242-73) NPR 7120.5F, NASA Space Flight Program and Project Management Requirements

RM-3 RISK MANAGEMENT PLAN

Title:

RISK MANAGEMENT PLAN

DID for CDRL No.

RM-3

Reference:

SWiPS SOW Section 4.3.4 and 4.9 Purpose:

To provide a comprehensive description of the contractor’s plan for identifying, analyzing, communicating, and managing risks, opportunities, and issues per Agency and GSFC requirements.

Preparation Information:

1. The risk management (RM) description or plan shall present the contractor's approach to comply with NPR 8000.4 and GPR 7120.4.

2. The RM description or plan shall define the contractor’s RM philosophy, policies, guidelines, and practices used to identify, analyze, communicate, and manage risks, opportunities, and issues. This document establishes the contractor’s RM organization and process, providing the framework for RM program implementation.

3. The RM description or plan shall explain the relationship between the contractor’s Risk Management Board (RMB) and associated GSFC RMB(s) and how risk information continuously flows throughout the contractor’s organization.

4. A Risk Report shall be prepared for the monthly RMB. The Government shall be participants in the monthly RMB meetings. The updated risk assessment shall include an update of the list of risks, as well as risk handling plans and status for all higher-level risks.

5. The RM description or plan shall document how RM requirements are flowed down to all applicable subcontracts. The RM description or plan shall address the requirements of NASA’s Federal Acquisition Regulation Supplement (NFS) 1852.234-2 or Alternate I.

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

Format:

Contractor-selected formats are acceptable

Applicable Documents:

NPR 8000.4, Agency Risk Management Procedural Requirements GPR 7120.4, Risk Management

RM-4 INTEGRATED PROGRAM MANAGEMENT DATA AND ANALYSIS REPORT

(IPMDAR)

Title:

INTEGRATED PROGRAM MANAGEMENT DATA AND ANALYSIS

REPORT (IPMDAR)

DID for CDRL No.

RM-4

Reference:

SWiPS SOW Section 4.3.5 Purpose:

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 integrated program management data and analysis report (IPMDAR) DRD shall be in consonance with the work breakdown structure (WBS), organizational breakdown structure (OBS), 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 (NASA 533M/Q). The contractor shall be able to reconcile between the NASA 533M/Q and the IPMDAR. This reconciliation should be included within the required IPMDAR performance narrative report.

IPMDAR contains data for measuring contractor cost and schedule performance at NASA.

The primary purpose is to reflect current performance status and the forecast of future performance.

The IPMDAR consists of the following components:

1) Contract Performance Dataset (CPD) – Provides performance/execution data from contractor existing management systems.

2) Schedule (Comprised of both Microsoft Project or Native Schedule File and the Schedule Performance Dataset (SPD) – Provides data from the consolidated contractor Integrated Master Schedule (IMS). At a minimum, subcontractor effort shall be incorporated into the IMS at an intermediate level with key milestones and be distinguishable from the contractor’s and subcontractor’s efforts.

3) Performance Narrative Report (Comprised of both the Executive Summary and Detailed Analysis Report) – Provides narrative analysis of data provided in the CPD and the SPD.

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

Preparation Information:

GSFC strongly recommends contractors to use Microsoft Project as their scheduling tool for integration with GSFC schedules.

1. Contract Performance Dataset (CPD), Instructions

Contractor will meet the requirements set forth in NASA IPMDAR Tailoring Supplement

(NITS)

a. The CPD shall be submitted in dollars as part of the original JavaScript Object Notation (JSON) submission. Contractors with IPMDAR flow down may submit dollars as part of the original Prime submission and provide a separate JSON file with dollars file directly to the Government to protect data sensitivities related to rates.

b. Data Repository-Electronic Submission and File Formats: Data in accordance with the applicable approved CPD FFS and Data Exchange Instructions (DEI) is to include all structures and units to at least the work package level.

c. Subcontractor Integration: Data for Subcontractors with an IPMDAR DID flow down requirement shall be integrated with the Prime’s IPMDAR CDRL delivery.

2. Schedule Performance Dataset (SPD)

a. GSFC strongly recommends contractors to use Microsoft Project as their scheduling tool for integration with GSFC schedules.

b. Contractors with IPMDAR flow down may submit dollars as part of the original Prime submission and provide a separate JSON file with both dollars and hours file directly to the Government to protect data sensitivities related to rates.

c. IMS Data Dictionary for Microsoft Project or Native IMS Schedule File’: The first monthly analysis narrative submission for the Schedule shall include the ‘Schedule Assumptions’ and ‘Data Dictionary’. Any change, post-first submission, to the ‘Schedule Assumptions’ or ‘Data Dictionary’ requires re-submittal of the information with the affected IPMDAR deliverable.

d. Schedule Risk Assessment (SRA) - Reporting Frequency’: An SRA can be performed, at the request of the Government, particularly when the schedule is a significant issue for the Government due to operational requirements, funding limitations, or when scheduling is considered a major risk element to the acquisition effort.

e. The Integrated Master Schedule (IMS) contains the contract milestones, accomplishments, criteria, discrete tasks/activities, work packages and planning packages, as applicable, from contract start to contract completion. The IMS is an integrated, logically driven, network-based schedule that is vertically and horizontally traceable. The IMS has traceability to, the project earned value management (EVM) work breakdown structure (WBS), project Organizational Breakdown Structure (OBS), contractor control accounts (CAs), and contractor

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

work packages (WPs), if applicable to provide transparency for execution. The WBS and other SPD fields in the IMS are consistent with the contract performance dataset (CPD). The IMS contains all calendars that define working and non-working time periods or other information that may impact the schedule. Each event (e.g., milestone, activity, summary, etc.) identified in the IMS has a unique identifier that is consistent period to period.

f. The Table below shows elements of the Schedule Performance Dataset.

Element Description

Schedule The Schedule consists of horizontally and vertically integrated discrete tasks/activities, consistent with all authorized work, and relationships necessary for successful contract completion.

The Schedule is a single integrated network that also contains significant external interfaces, subcontractor discrete work, Government furnished equipment/ information/property and relationship dependencies for the entire contractual effort.

The Schedule shall contain all calendars that define working and nonworking time periods.

The schedule shall reflect accurate remaining durations, start dates, and finish dates for all tasks/activities and milestones in respect to the status date.

SOW/IMP

References

If a Statement of Work (SOW) or Integrated Master Plan (IMP) are used for vertical schedule integration, those references shall be provided in both the SPD and native schedule.

Milestones Provide zero duration schedule events marking the due date for accomplishment of a specified work scope or objective.

Milestone may mark the start, an interim step, or the end of one or more activities.

Tasks/Activities Provide elements of work with duration and logical relationships/dependencies.

Task/activity names shall be concise and unique in respect to other names within the Schedule.

The name of each task/activity shall clearly reflect the scope, output (e.g., deliverable), and place within the Schedule architecture so that the content can be understood without the subproject task structure, if applicable.

Duration Provide the length of time estimated, realized, and/or remaining to accomplish a task/activity. Discrete tasks are preferred to be 42 work days or less.

Baseline Dates and Information

For all tasks within the performance measurement baseline (PMB), baseline dates in the SPD and Native Schedule files shall be consistent with the start and finish of the cost baseline in the CPD at the control account (or work package) level. The baseline is typically set equal to the current schedule early dates at the time of the baseline establishment when change control is initiated.

Control Account/Work Package Identification

Tasks in the schedule shall be tagged with a control account and work package as appropriate. This is accomplished by using the corresponding ControlAccountID and WorkPackageID fields in the Task table of the SPD. The SPD shall be consistent with the CA and WP definitions within the CPD. As a minimum, the ControlAccountID values shall be consistent with the ID tags as defined in the ControlAccount table and the Task table of the SPD shall be consistent with the work package definitions.

Level of Effort

(LOE)

Level of effort (LOE) activities may be included or excluded in the network, as appropriate. This determination should be made based on standard procedures.

LOE activities shall not impact discrete work or the calculation of the critical and driving paths and never drive paths. When LOE activities are included within the IMS, they are clearly identified as such and defined in the Data Dictionary.

Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

Schedule Percent Complete

The calculated schedule percent complete is a time-based status calculated by the schedule tool without regard to task/activity scope accomplishment. This is not used to status budgeted cost of work performed (BCWP) (i.e., depicts the “time” percent complete based on the forecast completion date, not earned value percent complete based on work accomplished). Earned Value % complete when used, will be in the physical % complete field.

Earned Value Technique

The Earned Value Technique (EVT) used for planning and statusing the EV Tool can, as needed, be identified with the Schedule Performance Dataset (SPD). The EVT for each task is identified within the SPD and if LOE tasks are included withing the schedule then they shall be identified using the appropriate EVT tag.

Total Float/Slack Provide the amount of time a task/activity or milestone forecast finish date can slip before delaying contract completion or constraint date.

Free Float/Free Slack Provide the amount of time a task/activity or milestone can slip before it delays any of its successor tasks/activities or milestones.

Driving Path The driving path is the longest continuous sequence chain of incomplete discrete tasks/activities/milestones and, if present, parallel chains in the schedule network that drive the forecast dates of the agreed to discrete task/activity or milestone. A driving path may or may not be on the IMS critical path

Critical Path A sequence of discrete work packages and planning packages (or lower level tasks/activities) in the IMS that has the longest total duration with the least amount of total float/slack through an end point.

Subcontractor Tasks Identify the tasks that are unique to the scope of a major subcontractor, if any. The subcontractor discrete work will be incorporated as tasks within the contractor IMS at a level necessary…