3. Attachment B SOW DRL_DRD Draft Release V1.pdf

DRAGONFLY MISSION

Solicitation #:

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem – Attachment B: Data Requirements List / Data Requirements Description

Page: of 46

PARACHUTE DECELERATOR SUBSYSTEM (PDS)

ATTACHMENT B:

CONTRACTOR DATA REQUIREMENTS LIST /

CONTRACTOR DATA REQUIREMENTS DESCRIPTION

(DRL/DRD)

SOLICITATION #: 80LARC22R0001

DRAFT RELEASE VERSION 1

Langley Research Center Hampton, Virginia

National Aeronautics and Space Administration

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

TABLE OF CONTENTS

List of Tables

1 INTRODUCTION

2 DEFINITIONS

2.1 Due Date / Maturity – Related Definitions

2.2 Media – Related Definitions

2.3 Category – Related Definitions

3 Contractor DATA REQUIREMENTS LIST (DRL)

4 Contractor DATA REQUIREMENTS DESCRIPTION (DRD)

4.1 Review DRDs

4.2 Project Management DRDs

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

LIST OF TABLES

Table B1. Formats for Electronic Deliverables

Table B2. Review DRL

Table B3. Project Management DRL

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

1.0 INTRODUCTION

This Contractor Data Requirements List (DRL) / Contractor Data Requirements Description

(DRD) document defines the requirements for deliverable documentation to be provided by the

Contractor under the PDS contract. Section 2.0 includes definitions and instructions for delivery.

Section 3.0 presents the DRL item by item, including due dates, quantity, and media format. Section

4.0 provides the DRD for each item listed in the DRL. Each DRD includes use and preparation information.

Symbols and abbreviations are not defined in this attachment; the reader should refer to

Sections 7 and 8, respectively, of the SOW. References and Applicable Documents are listed in

Sections 9 and 10, respectively, of the SOW.

2.0 DEFINITIONS

2.1 Due Date / Maturity – Related Definitions

The following definitions apply to the "Due Date / Maturity.” Unless otherwise specified, deadlines are in calendar days.

(A) Due Date

(1) PDR, CDR, etc.: Preliminary Design Review, Critical Design Review, etc.

(2) Monthly: Submitted on monthly basis.

(3) DACA: (Calendar) Days After Contract Award.

(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 based on the best available current information and are resubmitted when further information becomes available.

(3) Baseline: The complete submission of an item that, 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.

(4) Update: The item is revised with the best up-to-date information available at the time. Updates require the same "approval/review/information" process as was required for the most recent submission.

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

2.2 Media – Related Definitions

The following definition applies to the “Media” columns of Tables B2 and B3.

Electronic (E): The Contractor shall deliver data items to a Government specified web portal unless otherwise noted. The Contractor shall notify the Contracting Officer and Contracting

Officer’s Representative (COR) of electronic submission of the data item via electronic mail. The

Contractor shall provide electronic deliverables in the Contractor’s standard electronic formats specified in Table B1, unless otherwise approved by the Contracting Officer or COR.

Table B1. Formats for Electronic Deliverables.

Text Documents Portable Document Format (PDF) (searchable) or Microsoft

(MS) Word.

Presentations PDF (searchable) or MS PowerPoint.

Spreadsheets MS Excel.

Database Delimited American Standard Code for Information

Interchange (ASCII) text files accompanied with database schema document defining tables and entries.

Schedules PDF and MS Project.

Schematics and Drawings Design Web Format (DWF) and PDF.

Photographs Joint Photographic Experts Group (JPEG) or current industry standard.

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

If separate distribution instructions are not specified for separate submission due date/maturity items, then the listed distribution applies to all submissions.

CD/DVD: Compact Disc (CD) / Digital Video Disc (DVD) (readable).

Other (O): See DRD for additional distribution instructions.

2.3 Category – Related Definitions

The following definitions apply to "Category (CAT)" submission columns of Tables B1 and

B2. If separate submission instructions are not specified for separate submission due date/maturity items, then the listed submission instruction applies to all submissions.

Approval (A): Documentation items in this category require Government approval. The

Contractor shall wait until Government approval is provided to begin implementation of the document. If the Contractor has not received approval within 30 calendar days of delivery of a

DRD item, the Contractor may proceed as if the document has been approved. If the item is rejected (not approved) and returned with comments for revision, the Contractor shall follow the

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem – requirements specified by the COR. For most cases the Contractor shall resubmit the document within 14 calendar days of receiving comments from the Government.

Review (R): Documentation items in this category require Government review. The Contractor may implement the document if not notified of corrective actions within two weeks after receipt by the Government. If corrective actions are identified, their resolution will be mutually agreed upon and specified by the COR.

Information (I): Documentation items in this category are provided for Government information only. No formal feedback will be provided. Any issues or questions arising from review of the documentation will be addressed at regular oversight meetings.

3.0 CONTRACTOR DATA REQUIREMENTS LIST (DRL)

Table B2. Review DRL.

No. Document Due Date / Maturity Media CAT

RE-11 Integrated Baseline Review

(IBR) Data Package

14 days prior to review E R

Update if re-baseline occurs E R

Table B3. Project Management DRL.

No. Document Due Date / Maturity Media CAT

PM-1

Monthly Project Status

Report (MPSR)

Monthly, no later than the 15th calendar day E I

PM-2

Integrated Master Schedule

(IMS)

Baseline: 60 days prior to PDR E A

Submission Frequency: Monthly, no later than the 7th calendar day E R

PM-3

Contract Work Breakdown

Structure (CWBS) and

CWBS Dictionary

Baseline: 30 DACA E A

Update as needed E A

PM-4

Financial Management

Reports

Initial (Baseline): 30 DACA E I

Monthly (NASA Form 533M), no later than the 15th calendar day E, O I

PM-5

Configuration Management

Plan Update as needed E R

PM-6 Project Management Plan Baseline: 30 days prior to PDR E A

Update as needed E A

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-7 Risk Management Plan Baseline: 30 DACA E A

Update as needed E A

PM-8 Reserved

PM-9 Reserved

PM-10

Information Technology

(IT) Security Management

Plan

30 DACA and maintained throughout the contract E A

PM-11

NASA Property in the

Custody of Contractors

Annually, no later than October 15th of each year E, O I

Final report within 30 days after disposition of all property when contract performance is complete

E, O I

PM-12 Subcontracting Reports See instructions in DRD E, O I

PM-13

Patent Rights and

Invention Reporting See instructions in DRD E, O A

PM-14

Federal Contractor

Veterans Employment

Reports

Annually, no later than September

30th each year E, O I

PM-15

Conflicts of Interest

Avoidance Plan

30 DACA and maintained throughout the contract E, O A

PM-16 Contract Final Report 60 days after launch E, O A

PM-17 IT Security Plan Baseline: 30 days prior to PDR E A

Update as needed E A

MA-1 Safety and Mission Plan 90 DACA and update as needed E A

MA-2

Mishap and Contingency

Plan

30 days prior to PDR, Preliminary

30 days prior to CDR, Baseline

30 days prior to SMSR, Final

E

R

R

A

MA-3

Preliminary Hazard

Analysis

30 days prior to PDR, Baseline

30 days prior to CDR, Final E

R

A

MA-4

Reporting of

Non-Conformances

Baseline: 30 days prior to PDR

Submission Frequency: Monthly, no later than the 7th calendar day

E

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

MA-5

Reporting of Failures and

Anomalies

Baseline: 30 days prior to PDR

Submission Frequency: 8 hours after occurrence of Major and 24 hours after occurrence of Minor (Provide updates as necessary)

Two weeks after determination of root cause, Final Closure Report

(Type 1 only)

E

R

R

A

MA-6 Reliability Program Plan

30 days prior to PDR, Preliminary

30 days prior to CDR, Baseline

30 days prior to PSR, Final

E

R

R

A

MA-7

Failure Modes and Effects

Analysis (FMEA) and

Critical Items List (CIL)

30 days prior to PDR, Preliminary

30 days prior to CDR, Baseline

30 days prior to PSR, Final

E

R

4.0 CONTRACTOR DATA REQUIREMENTS DESCRIPTION (DRD)

4.1 Review DRDs

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

RE-11 INTEGRATED BASELINE REVIEW DATA PACKAGE

1 DRL/DRD No: RE-11

2 Title: Integrated Baseline Review (IBR) Data Package

3 References

• SOW

• NPR 7120.5F, NASA Space Flight Program and Project Management Requirements

• NASA Federal Acquisition Regulation (AR) Supplement Part 1834, Major System

Acquisition

4 Use

An IBR is a joint assessment conducted by the Government Project Manager and the

Contractor to verify the completeness, realism, and accuracy of the Contractor

Performance Measurement Baseline. This involves verifying the technical content of the baseline and assessing the realism and accuracy of the related resources (performance budget and IMS).

5 Preparation Information

IBR Data Packages shall support the IBR objectives stated above for each review. Data packages will be developed and submitted electronically prior to each IBR. The

Contractor shall ensure proper flow-down of this requirement to subcontractors per

NFS 1852.234-2(f ).

The IBR Data Package(s) shall contain the following:

A. Program/Business Management and Control Account Notebooks;

B. IMS;

C. Project Risk Register;

D. Control Account Plans, Basis of Estimates, Assumptions, and Risks;

E. Contract WBS and Dictionary to the Control Account level;

F. Organizational Breakdown Structure to the Control Account Manager level;

G. Responsibility Assignment Matrix showing dollars allocated by Control

Account;

H. Work Authorization Documents (all levels);

I. Subcontractor listing by Work Breakdown Structure (WBS) element and value of subcontracts;

J. Latest Estimate at Completion and supporting documentation;

K. Baseline Change Requests approved thus far, if applicable;

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

L. Baseline Control Logs (Management Reserve, Undistributed Budget, Budget

Base);

M. All CPR to date; and

N. Control Account/Work Package summary showing:

a. Number of work packages,

b. Number of Planning packages and total Planning Package budget, and

c. All contract changes to date.

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

4.2 Project Management DRDs

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-1 MONTHLY PROJECT STATUS REPORT

1 DRL/DRD No.: PM-1

2 Title: Monthly Project Status Report (MPSR)

3 References

• SOW

• MAR

• Risk Management Plan

4 Use

These reports will be used to provide an opportunity for monthly discussions between the

Contractor and the Government regarding plans and issues and to evaluate contract status.

5 Preparation Information

The MPSR shall be provided in a MS Word document with supplemental MS

PowerPoint Charts as necessary. The MPSR shall cover all aspects of the contracted effort and include the following for Phase B, C, and D:

1. Programmatic:

A. Project Status Summary for three months, 2 previous months (historical performance) plus current month (forward looking, reporting month). The

“stoplight” chart should give a visual (Green, Yellow, Red) summary for overall technical, schedule, programmatic, and resources. A short status description and action plan should be developed for categories that are identified yellow or red;

B. Problems encountered during the reporting period, and anticipated approaches for resolution (including, as appropriate, technical issues, manpower and staffing, supplier and subcontractor issues, and similar issues);

C. Summary of programmatic or technical risks related to the payload design elements that may impact the PDS contract;

D. Technical and programmatic issues and anticipated approaches for resolution;

E. Subcontractor/supplier status (performance, issues, risks, plans, surveillance audits);

F. Status of assigned actions;

G. Summary report of IMS current activities, critical path(s), and status. The report shall contain a narrative analysis of the schedule status, progress

(accomplishments) and issues. The Contractor shall base the report on

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem – data extracted from the accompanying IMS and shall organize the report in a manner consistent with the CWBS. At a minimum the report shall contain charts and narratives explaining:

a. Scheduled items accomplished since the last report,

b. Schedule items forecasted for the next reporting period,

c. Primary, secondary, and tertiary critical path analysis, with impacts and workarounds,

d. Variances, impacts and workarounds for contract milestones delayed from their baseline dates,

e. Tasks, activities, and milestones that have constraint dates, and

f. List of baseline change requests and key milestones. The

Contractor shall define and mutually agree upon key milestones with the Government;

H. DRL/DRD products status;

I. Project Financial Summary for three months, 2 previous months

(historical performance) plus current month (forward looking, reporting month). The “stoplight” chart should give a visual (Green, Yellow, Red) summary for overall financial, schedule, funding, and reserves. A short status description and action plan/forecast should be developed for categories that are identified yellow or red;

J. Summary of financial liens and threats;

K. Explanation of financial variances should be consistent with variance reported on NASA Form 533M as expressed in DRD PM-4;

L. Summary and explanation of key parameter performance and trends; and

M. Estimated monthly and cumulative engineering hours expended on the payload design elements.

2. Technical:

A. Report of Key Technical Parameters KTPs that include status of technical resources and performance budgets based on program design activity and updates driven by those activities. The KTP report emphasizes updates to

KTPs, if any. The fidelity and accuracy of the KTP Report shall be mutually agreed upon. The KTP Report shall include status of current best estimate and contingency based on maturity. KTPs shall include:

a. Mass, and

b. Volume (i.e., size/envelope).

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

B. Technical status for system and subsystem design and development activities, including subcontract technical performance;

C. A summary of trend data planning, trending methodology descriptions, and trend data at a level of maturity commensurate with the state of the design and test program;

D. List of the Configuration Control Board proposed and approved changes for Class I changes, as defined in DRL/DRD PM-5 Configuration

Management Plan;

E. Risk assessment and status for top 10 risks or an amount agreed upon by the Government. Risk assessment and mitigations and opportunities contain data extracted from the Contractor’s Risk Management Database.

This item shall provide the results of the risk assessment (the list of identified risks) and the plans, if any, for mitigating each risk. Identify, categorize, and document the risks and mitigation steps per the

Contractor’s Risk Management Plan; and

F. Identification and status of long-lead purchases/acquisitions planned or made prior to PDR and prior to CDR.

3. Safety and Mission Assurance:

A. The overall Safety and Mission Assurance (SMA) progress to date. Each description shall include pertinent data and/or graphs to explain any significant results achieved. Each description shall include a list of

Mission Assurance milestones with current status, and a summary of assessment/audit reports, including subcontractors/suppliers and any

SMA risks or concerns;

B. Non-Conformance Summary Lists;

C. Government-Industry Data Exchange Program (GIDEP) review status/results or information payload and any GIDEP reports generated by the Contractor;

D. Organization and key personnel changes.

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-2 INTEGRATED MASTER SCHEDULE

1 DRL/DRD No.: PM-2

2 Title: Integrated Master Schedule

3 References:

• SOW

• NPR 7120.5F, NASA Space Flight Program and Project Management Requirements

4 Use

This 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 progress and trends.

5 Preparation Information

The Contractor shall develop, maintain, and deliver an IMS consistent with their institution procedures in MS Project 2007 or later.

The IMS shall:

A. Reflect an accurate current status including new forecast dates for behind-schedule and on-time tasks;

B. Include tasks necessary to accomplish the total scope of work and be traceable to the approved CWBS;

C. Integrate all key milestones and events including:

a. Contract milestones,

b. Design reviews,

c. Readiness reviews, and

d. Receivables/deliverables among subsystems/organizations

(including subcontractor effort);

D. Include and clearly identify schedule reserves;

E. When practical, set the granularity of task duration to 10 days; and

Realistic work calendars (indicating working and non-working periods) with

Schedule Work Time format in days ensuring the required consistency to the project Integrated Master schedule. Assume 5 day work week or specify.

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-3 CONTRACT WORK BREAKDOWN STRUCTURE AND DICTIONARY

1 DRL/DRD No.: PM-3

2 Title: Contract Work Breakdown Structure (CWBS) and CWBS Dictionary

3 References

• SOW

• NPR 7120.5F, NASA Space Flight Program and Project Management Requirements

4 Use

The CWBS is an organizing structure for: project technical planning and scheduling; cost estimation and budget formulation; defining the scope of SOWs and specifications for contract efforts; project status reporting; and documentation products. The CWBS

Dictionary provides a documented vocabulary that describes every element within the

CWBS.

5 Preparation Information

The CWBS shall provide a product-based, hierarchical breakdown of the work necessary to complete the contract tasks and deliverables. The CWBS shall include a break down to a minimum of three levels (i.e., 05.XX.XX); all contract work should be scheduled and completion of tasks be tracked to at least this CWBS level in the IMS (DRD

PM-2). The CWBS shall identify major elements of subcontracted work at CWBS level three, separate from Contractor prime effort.

The CWBS shall identify elements by title and a numbering system that performs the following functions:

A. Identifies the level of the CWBS element;

B. Identifies the higher level element into which the CWBS element will be integrated; and

C. Provides the cost account number of the element.

CWBS element identification shall follow the established coding on all cost proposals, budgets, schedules, financial reports, status reports and documentation products.

CWBS Dictionary

The CWBS Dictionary shall provide a narrative description of all contract scope within the CWBS. The CWBS Dictionary shall utilize the same hierarchical numbering system as the CWBS and provide dictionary entries for all work elements to CWBS level 3, as described above.

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-4 FINANCIAL MANAGEMENT REPORTS

1 DRL/DRD No.: PM-4

2 Title: Financial Management Reports

3 References

• SOW

Applicable

• NPR 9501.2E, NASA Contractor Financial Management Reporting

• NFS 1852.242-73, NASA Contractor Financial Management

• Reporting FAR 52.216-7, Allowable Cost and Payment

4 Use

NASA Form 533M provides monthly contractual planned and actual expenditure data as defined by the Government, including subcontractor data. This data is necessary for:

A. Projecting costs and hours to ensure dollar and labor resources realistically support project schedules;

B. Evaluating Contractors’ actual cost data in relation to negotiated contract value, estimated costs, and budget forecast data;

C. Planning, monitoring, and controlling project resources; and

D. Accruing cost in NASA’s accounting system.

5 Preparation Information:

Baseline Financial Management Report

A. The Contractor shall prepare a time-phased Baseline Financial Management

Report, detailing by month how it plans to incur costs for all CLINs, utilizing the

NASA Form (NF) 533Q format. The Contractor shall prepare and submit the report in accordance with instructions set forth on the reverse side of the 533Q

Form and NPR 9501.2E, NASA Contractor Financial Management Reporting. The

Contractor shall submit the Baseline Financial Management Report within 30 calendar days after the effective date of the contract.

B. The Contractor shall update the Baseline Financial Management Report, as required, during performance of the contract. The Contractor shall revise the report each time a contract modification is executed which increases or decreases the contract estimated cost.

Monthly Contractor Financial Management Report

A. The Contractor shall submit a Monthly Contractor Financial Management Report in accordance with NFS 1852.242-73, NASA Contractor Financial Management

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

Reporting. The Contractor shall prepare and submit the form in accordance with the instructions set forth on the reverse side of the form and NPR 9501.2E, NASA Contractor Financial Management Reporting;

B. The Contractor shall submit the report not later than the 15th calendar day of the month following the month being reported;

C. The Contractor shall complete Columns 8.a and b using estimates (forecasts) for the succeeding two months;

D. The Contractor shall ensure that estimates (forecasts) are the best projection of the actual costs to be reported in column 7.a of the subsequent month's NASA Form

533M. Since NASA uses the Contractor's estimate for the current month (column

8.a of NASA Form 533M) as accrued costs in its monthly financial statements, the accuracy of these projections are critical to the integrity of NASA’s financial data;

E. The Contractor shall report costs on the basis of the Contractor’s most current data for actual rates experienced at the time the report is prepared, rather than on the basis of approved provisional billing or bidding rates. In addition, the

Contractor shall make adjustments as needed for actual cost experience to reflect rates reported in its final indirect cost rate proposal submitted after the end of each of its fiscal years in accordance with paragraph (d) of FAR 52.216-7, Allowable Cost and Payment. The Contractor shall explain in the footnotes on the NASA Form 533 report any adjustments made for actual rates as determined by the Contractor in its annual final indirect cost rate proposal;

F. The Contractor shall include a narrative explanation for variances exceeding plus or minus 10 percent (±10%) between estimated costs shown in the prior month and actual costs shown in the current month at the contract level;

G. The NASA Form 533 reporting for all CLINs shall be consistent with the CPRSP

CWBS, with reporting down to CWBS level 3;

H. For CLIN 4, the Contractor shall submit a separate NASA Form 533M for each authorized task order and a summary NASA Form 533M covering all authorized task orders;

I. The Government will consider the Contractor’s accuracy of financial reporting when evaluating the Contractor’s Performance in the Contractor Performance

Assessment Reporting System (CPAR);

J. Column 6 of this report shall include the minimum reporting categories indicated below:

a. Direct Labor Hours.

b. Direct Labor Dollars.

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

c. Overhead(s).

d. Subcontract.

e. Material.

f. Travel.

g. Other Direct Cost .

h. G&A. and

i. Total Estimated Cost.

Additional Distribution Requirements for the Financial Reports

The Contractor shall email all reports to LaRC-DL-NF533@mail.nasa.gov mailto:LaRC-DL-NF533@mail.nasa.gov

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-5 CONFIGURATION MANAGEMENT PLAN

1 DRL/DRD No.: PM-5

2 Title: Configuration Management Plan

3 References

• SOW

• Configuration Management Plan

4 Use

Defines the Contractor’s configuration management system (including policies and procedures) that will be implemented for the flight hardware and software, and documentation. To facilitate the orderly processing of change requests to specifications or requirements, changes to plans or procedures, specification deviations, waivers, to appropriate level of review, classification, and approval authority for disposition.

5 Preparation Information

This plan shall describe in detail all flight hardware and software configuration management processes, methods, and procedures the Contractor intends to use during the development of the Dragonfly PDS Payload and Mission Operations Systems. Note: It is not a requirement for one document to cover the configuration management plan for all systems. Additionally, it is acceptable for the configuration management plan of a given system to be covered in a section of its associated Software Development and

Management plan.

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-6 PROJECT MANAGEMENT PLAN

1 DRL/DRD No.: PM-6

2 Title: Project Management Plan

3 References

• SOW

• NPR 7120.5F, NASA Space Flight Program and Project Management Requirements

4 Use

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, and similar information.

5 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. The plan shall describe how and where the project will operate during all phases of the contract, The Contractor format is acceptable.

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-7 RISK MANAGEMENT PLAN

1 DRL/DRD No.: PM-7

2 Title: Risk Management Plan

3 References

• SOW

• Risk Management Plan

4 Use

The Risk Management Plan is the basis for identifying and managing all performance, reliability, schedule, cost, and safety risks and opportunities on the Contractor’s project.

5 Preparation Information

The Risk Management Plan shall describe the Contractor’s approach to Risk

Management. The Contractor format is acceptable.

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-8 RESERVED

1 DRL/DRD No.:

2 Title:

3 References

4 Use

5 Preparation Information

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-9 RESERVED

1 DRL/DRD No.:

2 Title:

3 References

4 Use

5 Preparation Information

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-10 INFORMATION TECHNOLOGY SECURITY MANAGEMENT PLAN

1 DRL/DRD No.: PM-10

2 Title: Information Technology (IT) Security Management Plan

3 Applicable

• NFS Clause 1852.204-76, Security Requirements for Unclassified Information

Technology Resources

4 Use

To identify how the requirements for IT security will be met.

5 Preparation Information

In accordance with NFS 1852.204-76, Security Requirements for Unclassified

Information Technology Resources, the Contractor shall submit an IT Security

Management Plan within 30 DACA for review and approval by the Government.

The Contractor shall maintain the IT Security Management Plan throughout the term of the contract. The Contractor’s plan shall:

A. Identify how the requirements for IT security will be met (including developing and maintaining IT system security plans, contingency plans, and performing information system security assessment);

B. Identify how the requirements, for which NASA directives specifically mandate compliance with respect to security of NASA IT, resources will be met;

C. Describe how the Contractor intends to hold its employees and subcontractors accountable for meeting all the requirements relative to NPR 2810.1, NASA

Interim Technical Requirements (NITRs), IT Security and Training

Handbooks, and Chief Information Officer Directives. The documents can be found at: http://www.nasa.gov/offices/ocio/itsecurity/index.html;

D. Describe how the Contractor will meet future or changing IT security requirements as directed by Federal Law or NASA requirements;

E. Describe how the Contractor plans to protect their corporate IT resources to ensure that they pose no adverse impact on NASA resources;

F. Describe how the Contractor will protect NASA or contract-specific information and data under their control;

G. Describe how the Contractor plans to provide documentation for any required IT security-related deliverable;

H. Describe how the Contractor will ensure compliance with all NASA IT security training and awareness requirements;

http://www.nasa.gov/offices/ocio/itsecurity/index.html%3B

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

I. Describe how the Contractor will ensure compliance with NASA-established physical security requirements as they relate to IT security requirements;

J. Describe how the Contractor will ensure compliance with personnel screening requirements including assurance that employees with privileged access have the appropriate background screening; and

K. Describe the Contractor’s procedures for termination of employees including assurance that all access privileges (e.g., network, remote access, virtual private network, campus computing, and other application access) are terminated.

The IT Security Management Plan will be made part of this contract and will be updated as required by changes in the Federal Law or other NASA regulations.

Specific guidance for can be found in the following documents located at http://www.nasa.gov/offices/ocio/itsecurity/index.html http://csrc.nist.gov/publications/PubsSPs.html:

A. Federal Information Security Management Act (FISMA).

B. NPD 1600.2, NASA Security Policy.

C. NPD 2810.1, NASA Information Security Policy.

D. NPR 1600.1, NASA Security Program Procedural Requirements.

E. NPR 1620.2, Physical Security Vulnerability Risk Assessments.

F. NPR 2810.1a, Security of Information Technology.

G. NIST Special Publication (SP) 800-18, Guide for Developing Security

Plans for Federal Information Systems.

H. NIST Special Publication (SP) 800-35, Guide to IT Security Services.

I. NIST SP 800-36, Guide to Selecting Information Security Products.

J. NIST SP 800-64, Security Considerations in the Information System Development

Life Cycle.

http://www.nasa.gov/offices/ocio/itsecurity/index.html http://csrc.nist.gov/publications/PubsSPs.html:

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-11 NASA PROPERTY IN THE CUSTODY OF CONTRACTORS

1 DRL/DRD No.: PM-11

2 Title: Financial Reporting of NASA Property in the Custody of Contractors

3 References

• NFS 1852.245-73, Financial Reporting of NASA Property in the Custody of

Contractors

4 Use

To annually report any government owned/Contractor held property that has been furnished or that has been acquired by the Contractor under the terms of this contract.

5 Preparation Information

The annually submitted NF 1018, NASA Property in the Custody of Contractors, shall conform to NFS 1852.245-73, Financial Reporting of NASA Property in the Custody of

Contractors. The NF 1018 shall conform to the instructions on the Form and NFS 1845.71 and any supplemental instructions for the current reporting period issued by NASA.

Subcontractor use of NF 1018 is not required by this clause; however, the Contractor’s annual NF 1018 shall include data on property in the possession of subcontractors.

The Contractor shall submit the NF 1018 no later than October 15th of each year for the period October 1 through September 30.

The Contractor shall submit a final report within 30 days after disposition of all property when contract performance is complete.

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-12 SUBCONTRACTING REPORTS

1 DRL/DRD No.: PM-12

2 Title: Subcontracting Reports

3 References

• FAR 52.219-9, Small Business Subcontracting Plan

4 Use

The Government uses Subcontracting Reports for collection of subcontract data from

Federal contractors, which are required to establish plans for subcontracting with small and small disadvantaged business concerns.

5 Preparation Information

NASA’s preferred method for obtaining both Standard Form (SF) 294, Subcontracting

Report for Individual Contracts, and SF 295, Summary Subcontractor Report is electronically using Electronic Subcontract Reporting System (eSRS). Access to eSRS can be found at http://www.esrs.gov/.

If the Contractor does not submit an electronic SF 294 and SF 295 using eSRS, the

Contractor shall follow the instructions found on the reverse of the forms.

In addition to the above, the Contractor is required to comply with NFS Clause

1852.219-75, Individual Subcontracting Reports.

http://www.esrs.gov/

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-13 PATENT RIGHTS AND INVENTION DISCLOSURE REPORTING

1 DRL/DRD No.: PM-13

2 Title: Patent Rights and Invention Disclosure Reporting

3 References

• FAR 52.227-11, Patent Rights-Ownership by the Contractor (as modified by NFS

1852.227-11, Patent Rights-Retention by the Contractor)

4 Use

To provide the Government with technical information concerning any invention, discovery, improvement, or innovation made by a Contractor in the performance of work under this contract for the purpose of determining title and rights.

5 Preparation Information

Interim Patent Rights Report

The Contractor shall submit an annual list of subject inventions required to be disclosed as set forth in FAR 52.227-11, Patent Rights-Ownership by the Contractor (as modified by NFS 1852.227-11, Patent Rights-Ownership by the Contractor).

Final Patent Rights Report

The Contractor shall submit a listing of all subject inventions required to be disclosed or certify that there were none as set forth in FAR 52.227-11 Patent Rights- Ownership by the Contractor (as modified by NFS 1852.227-11, Patent Rights- Ownership by the

Contractor).

Invention Disclosure Reporting

The Contractor shall disclose each subject invention under the contract as set forth in

FAR 52.227-11, Patent Rights-Ownership by the Contractor, (as modified by NFS

1852.227-11, Patent Rights-Ownership by the Contractor). The electronic and paper version of NF 1679, Disclosure of Invention and New Technology (Including Software), shall be used for this reporting. Both the electronic and paper versions of this form may be accessed at http://invention.nasa.gov. Disclosures are required within two months after the inventor discloses it in writing to Contractor personnel who are responsible for patent matters.

http://invention.nasa.gov/

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-14 FEDERAL CONTRACTOR VETERANS EMPLOYMENT REPORTS

1 DRL/DRD No.: PM-14

2 Title: Federal Contractor Veterans Employment Reports

3 References

• FAR 52.222-37, Employment Reports on Veterans

4 Use

Annual report required by the Secretary of Labor on veteran’s in the Contractor federal workforce.

5 Preparation Information

The Contractor shall submit a Federal Contractors Veterans’ Employment Reports

(VETS- 4212) as required by Clause 52.222-37, Employment Reports on Veterans.

Within 30 days following the VETS Report submission, the Contractor shall submit a letter to the Contracting Officer confirming that it has submitted the most recent annual

VETS-4212 Report required by FAR 52.222.37.

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-15 CONFLICTS OF INTEREST AVOIDANCE PLAN

1 DRL/DRD No.: PM-15

2 Title: Conflicts of Interest Avoidance Plan

3 References

• NFS 1852.237-72, Access to Sensitive Information

4 Use

To meet requirements for avoiding Organizational Conflicts of Interest (OCI). The plan and subsequent revisions will be reviewed and approved by the Contracting Officer. The approved plan will be incorporated into the contract as a compliance document, once approved.

5 Preparation Information

The plan shall comply with the requirements of NFS 1852.237-72, Access to Sensitive

Information. The plan shall explain the approach to identifying, mitigating and/or avoiding OCIs that may arise under this contract. The plan shall include, at a minimum:

A. An assessment of the potential risk for various types of conflicts such as access to sensitive, non-public information.

B. The process for identifying OCIs, including the Contractor’s coordination with each of its parent, subsidiary, affiliates, office locations, divisions and/or other similar entities (collectively, the “Business Units”) to determine whether OCIs currently exist.

C. The approach for maintaining communication with each Business Unit during the performance of this contract to identify potential OCIs arising during such performance period.

D. The approach to training and refresher training for its employees.

E. Once identified, the methods the Contractor will utilize to mitigate the various types of OCIs.

F. The approach for ensuring the processes and procedures included herein will be applied to each of its subcontractors and/or consultants (including their respective

Business Units).

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-16 CONTRACT FINAL REPORT

1 DRL/DRD No.: PM-16

2 Title: Contract Final Report

3 References

• NFS 1852.235-73, Final Scientific and Technical Reports

4 Use

To provide a brief summary and index of the most significant documents (in terms of history and lessons learned) generated on this contract

5 Preparation Information

This report shall contain at a minimum:

A. Overview of the payload development history (major events and timeline);

B. Overview of contract cost and schedule performance;

C. Document index organized by:

a. Conceptual design trades,

b. Final design and analysis, and

c. As-built configuration;

D. Development challenges and solutions;

E. Performance summary;

F. Out-of-specification items:

a. SOW waivers and deviations,

b. PDS Specification Document waivers and deviations,

c. Interface waivers and deviations, and

d. Technical issues;

G. Lessons learned:

a. Technical, and

b. Programmatic.

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

PM-17 IT SECURITY PLAN

1 DRL/DRD No.: PM-17

2 Title: IT Security Plan

3 References

• SP 800-18 Rev. 1, Guide for Developing Security Plans for Federal Information

Systems (February 2006).

4 Use

To provide an overview of the security requirements of the system and describe the controls in place or planned for meeting those requirements and to delineate responsibilities and expected behavior of all individuals who access the system.

5 Preparation Information

The Contractor shall develop an IT Security Plan for the Dragonfly PDS Project system. The IT Security Plan shall include:

A. System Identification:

a. General description/purpose,

b. System environment,

c. System interconnection/information sharing,

d. List any laws or regulations that establish specific requirements for confidentiality, integrity, or availability of data/information in the system,

e. List any laws or regulations that establish specific requirements for confidentiality, integrity, or availability of data/information in the system, and

f. General description of information sensitivity.

B. Management Controls:

a. Risk Management assessment,

b. Review of security controls

c. Rules of behavior

d. Planning for security in the life cycle

C. Operational Controls

a. Personnel security

b. Physical and environmental protection

c. Production input/output controls

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

d. Contingency planning

e. Hardware and system software maintenance controls

f. Integrity controls

g. Security awareness &training

h. Incident response capability

D. Technical Controls

a. Identification and authentication

b. Logical access controls

c. Audit trails

Note: The Contractor may include the IT Security Plan as a section in the IT Security

Management Plan effectively combining DRL/DRD PM-10 and DRL/DRD PM-17.

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

MA-1 Safety and Mission Assurance Plan

1 DRL/DRD No.: MA-1

2 Title: Safety and Mission Assurance Plan (SMAP)

3 References

• SOW Section 5

• NPR 8735.2C, Hardware Quality Assurance Program Requirements for Programs and Projects

• NPR 8705.4A, Risk Classification for NASA Payloads

• NPD 8720.1C, NASA Reliability and Maintainability (R&M) Program Policy

• NASA-STD-6016B, Standard Materials and Processes Requirements for Spacecraft

• NASA-STD-8729.1A, NASA Reliability and Maintainability (R&M) Standard for Spaceflight and Support Systems

• NPR 8715.7B, Payload Safety Program

• NASA-STD-8719.9B, Lifting Standard

• NASA-STD-8739.12, Metrology and Calibration

• ISO 9001:2015, Quality Management Systems

• SAE AS9100D, Quality Management Systems – Requirements for Aviation, Space, and Defense Organizations

4 Use

Documents that Contractor or/and all Sub-Contractor(s), responsible for the design and development of the project hardware plan for implementing a system safety and mission assurance program consistent with contract statement of work (SOW).

This identifies the applicable Systems Safety, Reliability, Quality, Parts, Materials and

Processes, Configuration Management requirements; the methods, procedures, and instructions to be used to implement the requirements; and organization (including position and names) responsible to assure applicable requirements are satisfied for the implementation of a system safety and mission assurance program.

5 Preparation Information

The SMAP scope shall cover:

A. The planning, execution, monitoring and control of reliability, quality assurance, workmanship, safety, parts and materials, software development, contamination control, non-conforming material, and failure investigation and reporting.

B. All phases of the Project’s efforts, including, but not limited to, requirements definition and verification, design and development, procurement, manufacturing and fabrication, assembly, and integration and test. This may include in special cases, Instrument processing in preparation for launch, ground systems, and mission operations assurance.

C. All flight hardware that is designed, built, or provided by the Contractor and its

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem – subcontractors, or furnished by the Government, from project initiation through launch and mission operations

D. Implementation of engineering changes

E. Acronym list

The SMAP shall include a description of the organization, responsibilities, and authorities responsible for implementing the SMA program. The SMAP shall also include how the contractor’s Quality System will be implemented for this Project, a description of all the quality system elements necessary to implement the requirements cited in the SOW and shall include a reference to the contractor’s implementation procedures.

The SMAP shall include reference to the Contractor’s internal procedure for each Product

Assurance function/element and deliverable and have brief description of the respective procedure. The SMAP shall include a more detailed description for the following areas as a minimum:

(A) Quality Management System

Allow for onsite review and evaluation of Contractor’s documented quality management system. Contractor shall demonstrate adherence to a Quality Manual addressing applicable requirements of AS9100D or ISO9001:2015. Acceptable to use an equivalent means to demonstrate that the intent of the AS9100 or

ISO 9001requirements are met.

(B) Material Review Board

(C) Review/disposition/approval of failure reports

(D) Reliability Program

(E) Workmanship equivalency (if applicable)

(F) Materials and Processes (M&P) Selection, Control, and Implementation Plan

(G) System Safety

Allow for onsite review and evaluation of Contractor’s documented system safety program. Contractor shall:

(i) Define the required documentation, applicable requirements documents, and completion schedules for analyses, reviews, and safety packages.

(ii) Provide for early identification and control of hazards to personnel, facilities, support equipment, and the flight system during product development, including design, fabrication, test, transportation, and ground activities.

(iii) Address compliance with industrial safety requirements imposed by NASA and OSHA design and operational needs and contractually imposed mission unique obligations

(iv) Address compliance with the launch range safety requirements

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

MA-2 Mishap Preparedness and Contingency Plan (MPCP)

1 DRL/DRD No.: MA-2

2 Title: Mishap Preparedness and Contingency Plan (MPCP) 3 References

• SOW Section 5

• NPR 8621.1D, NASA Procedural Requirements for Mishap and Close Call

Reporting, Investigating, and Recordkeeping 4 Use

Ensure NASA requirements for mishap reporting are met

5 Preparation Information

This plan shall address all the requirements to meet the NASA requirements for mishap reporting, investigation, and corrective action. The Contractor format is acceptable.

80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem –

MA-3 Preliminary Hazard Analysis (PHA)

1 DRL/DRD No.: MA-3

2 Title: Preliminary Hazard Analysis (PHA)

3 References

• SOW Section 5

• NPR 8715.7B, Payload Safety Program

4 Use

The Preliminary Hazard Analysis (PHA) is used to obtain an initial risk assessment and identify safety critical areas of concept system. It is based on the best available data, including mishap data from similar systems and other lessons learned. The PHA is used to evaluate hazards associated with the proposed design or function for security, probability, and operational constraints. The PHA is also used to identify safety provisions and alternatives needed to eliminate hazards or reduce their associated risk to an acceptable level.

5 Preparation Information

The PHA shall identify safety critical areas, provide an initial assessment of hazards, and identify requisite hazard controls and follow-on actions. The PHA shall incorporate on the best available data, including mishap data from similar systems and other lessons learned, The PHA shall include evaluations of the hazards associated with the proposed design or function for hazards severity, hazard probability, and operational constraint.

The PHA shall include safety studies identifying provisions and alternatives needed to eliminate hazards or reduce their associated risk to an acceptable level. The PHA shall include, as applicable, but is not limited to, the following:

(A) Hazardous components such as toxic substances, hazardous construction materials, pressure systems, and other energy sources.

(B) Safety related interface considerations among various elements of the system such as material compatibility, electromagnetic interference, inadvertent activation, fire and explosive initiation and propagation, and hardware and software controls. This shall include consideration of the potential contribution by software, including software developed by other contractors and sources, to subsystem and system mishaps.

(C) Environmental constraints including the operating environments such as drop, shock, vibration, extreme temperatures, humidity, noise, exposure to toxic substances, health hazards, fire, electrostatic discharge, lightning, electromagnetic environmental effects, ionizing and non-ionizing radiation including laser radiation.

(D) Operating, test, maintenance, built-in-tests, diagnostics, and emergency procedures (human factors engineering, human error analysis of operator functions, tasks, and requirements; effect of factors such as equipment layout, 80LARC22R0001

Draft Release Version 1

Title: Dragonfly Parachute Decelerator Subsystem – lighting requirements, potential exposures to toxic materials, effects of noise or radiation on human performance; explosive ordnance render safe and emergency disposal procedures; life support requirements and their safety implications in manned systems, crash safety, egress, rescue, survival, and salvage).

(E) Those test unique hazards that will be a direct result of the test and evaluation of the article or vehicle.

(F) Facilities, real property installed equipment, support equipment such as provisions for storage, assembly, checkout, proof testing of hazardous systems and assemblies that may involve toxic, flammable, explosive, corrosive, or cryogenic materials and wastes; radiation or noise emitters; and electrical power sources.

(G) Training and certification pertaining to hazardous and safety critical operations and maintenance of hazardous and safety critical systems.

(H) Safety related equipment, safeguards, and…