Attachment J-01 - Data Requirements Deliverable Draft.pdf

DRAFT 80JSC023R0003

PART III - -LIST OF DOCUMENTS, EXHIBITS, AND OTHER ATTACHMENTS

J01-1

Attachment J-01

DATA REQUIREMENTS DESCRIPTION (DRD)

National Aeronautics and Space Administration Johnson Space Center

J01-2

DOCUMENT CHANGE LOG

DRD

No.

DRD Title Revision Date

J01-3

INTRODUCTION

This document defines the requirements for contractual data to be delivered by the contractor to the Government. The data requirements are set forth in each Data Requirements Description (DRD) and shall govern that data required by the contract. The contractor shall furnish data defined by the DRDs as listed on the Contract Data Requirements List (CDRL) by category of data, attached hereto, and made a part of this contract. Such data shall be prepared, maintained, and delivered to NASA in accordance with the requirements set forth within this document. In cases where data requirements are covered by a Federal Acquisition Regulation (FAR) or NASA FAR Supplement (NFS) clause or other term (e.g., requirements statement), that clause or term shall take precedence over the DRD.

Subject to contract Clause I.16 FAR 52.227-14 RIGHTS IN DATA—GENERAL (MAY 2014)

ALTERNATE II (DEC 2007) [(MODIFIED BY NFS 1852.227-14 (APR 2015)]

ALTERNATE III (DEC 2007) ALTERNATE V (DEC 2007), this document sets forth the data requirements in each DRD and shall govern the data required under this contract. The Contractor shall furnish data defined by the DRDs listed by category of data. Such data shall be prepared, maintained, and delivered to National Aeronautics and Space Administration (NASA) in accordance with the requirements set forth herein. In cases where data requirements are covered by a FAR or NFS regulation or clause, the regulation takes precedence, pursuant to

FAR 52.215.33.

CDRL: Throughout the performance of the contract, the CDRL provides a listing by number, data type, title, and Office of Primary Responsibility (OPR).

DRD: Each DRD included in this CDRL prescribes content, format, and submittal requirements. The DRDs included in this CDRL are ordered sequentially as listed in the CDRL page(s) that precede(s) the actual DRDs.

Data Type Description: The data types are used to identify the approval and control required for each DRD. The following types are applicable:

Type 1 – Requires NASA approval prior to release. Approved Type 1 documentation shall be controlled, and deviations from or changes to concepts, techniques, and/or requirements stated therein shall require NASA approval prior to implementation. All work under this contract covered by approved Type 1 documents shall be performed in accordance with those approved documents. The Contracting Officer Representative (COR) shall have approval authority and shall sign the documentation prior to its release. To be an acceptable delivery, disapproved data shall be revised to remove causes for the disapproval prior to its release and implementation. Contractually binding documents shall not be implemented or revised without contractual authorization.

Type 2 - NASA reserves a time-limited right to disapprove in writing any issues and interim changes to those issues. Data shall be submitted to the procuring activity for review not less than 45 calendar days prior to its release for use or implementation. The Contractor

J01-4 shall clearly identify the release target date in the “submitted for review” transmittal. If the Contractor has not been notified of any disapproval prior to the release target date, the data shall be considered approved. To be an acceptable delivery, disapproved data shall be revised to remove causes for the disapproval prior to its release and implementation.

Type 3 – Information and documentation, which is provided to NASA for surveillance, information, review, and/or management control. This information does not require formal NASA review and approval. Information in this category would include status, cost reporting, analyses and test results, and other designated lists, reports, etc.

The contractor shall deliver a complete revised Type 1 or Type 2 data requirement with NASA comments incorporated within 45 calendar days of receipt of comments.

NOTE: Documents submitted per DRDs, even though directly (Type 1) or implicitly (Type 2) approved by NASA, shall not take precedence over the specifications as set out in the Statement of Work (SOW), Section C.

DATA FIDELITY

In addition to the required frequency for data deliverable submittals, the DRD also defines the level of readiness/fidelity, which applies to the submission of DRDs:

Initial (I) - A preliminary version of a delivery for NASA review. Initial submittals may contain some To Be Determined (TBD) items. Initial version fidelity shall reflect the Contractor’s internally approved baseline of the product and be adequate to permit NASA disposition in accordance with the DRD Type. Initial versions may be submitted periodically leading to a Final version.

Final (F) - A Final version of a delivery shall reflect the Contractor’s internally approved final version of the product and is ready for NASA disposition in accordance with the DRD Type. No TBDs may be included. Unless otherwise specified within the DRD, after final version DRD has been dispositioned by NASA, the Contractor shall submit any changes or additions for NASA review and disposition in accordance with the DRD Type.

STATEMENT OF GENERAL REQUIREMENTS

Subcontractor Data Requirement The prime contractor is responsible for flowing down any specific data requirements that apply to subcontracts and vendor agreements.

Reference to subcontractor data in the contractor’s responses is permissible and a copy of the referenced subcontractor data must be supplied with the response document at time of

J01-5 delivery to NASA.

Data Distribution, Format, and Transmittal Distribution: Distribution recipients and number of copies are identified within each DRD, provided within the contract, or as directed by the CO.

Data Format

The Contractor’s submittal in response to the DRDs shall be provided in an electronic format that meets four basic requirements: “Readable”, “Printable”, “Searchable”, and “Downloadable” by NASA utilizing publicly available off-the-shelf software. If the electronic format is not supported by publicly available off-the-shelf software, the Contractor shall provide NASA with the necessary software and approach to support the four basic requirements.

Data deliverables shall be delivered to NASA in the format specified below unless a specific format is required by a DRD. Data submittals shall consist of native format electronic file(s). NASA’s preferred native formats include Microsoft Word, Excel, or PowerPoint, as appropriate.

Transmittal Data shall be transmitted to NASA by submittal into an International Space Station (ISS) Program Authorized Repository (e.g. Electronic Document Management System (EDMS) for most DRD deliverable submittals or the Vehicle Master Data Base specifically for drawings).

Data Transmittal Package: Each data transmittal package shall include a transmittal memorandum that specifies the following:

1. Contract number

2. DRD number

3. DRD data type

4. Submission date or milestone being satisfied

5. Document number and revision

6. Document title

7. File names of all files being delivered; file naming convention shall clearly identify the document being delivered

8. NASA Records Retention Schedule (NRRS) number, if applicable (See NRRS

1441.1, NASA Records Retention Schedules)

EDMS Workflow Process The contractor shall deliver a Data Requirement (DR) to NASA electronically using the EDMS workflow. Approval of DRs is based on the prescribed data type, described above.

A DR will follow a workflow process once it is delivered into EDMS where it may either be approved or marked for “rework”. If NASA approves a DR, the contractor will get notification via e-mail that the DR has been approved. If the DR is rejected, NASA will

J01-6 provide comments to the contractor through the “rework” process detailing why it has not been approved. The contractor has 30 workdays from the date the DR was rejected to disposition NASA comments and resubmit the DR electronically into EDMS. The DR will then be either approved or sent back again to the contractor via the “rework” process.

There is not a limit on how many times a DR can go through the “rework” process before it is finally approved.

SOW Data Deliveries Data required in accordance with a SOW statement that does not have a DR reference will be delivered to NASA electronically using the EDMS workflow, indicating the applicable SOW paragraph. This information does not require NASA’s approval prior to its release in EDMS and will be released in EDMS upon delivery.

Document Identification: For all data types, the document number, change legend, date, and title constitute the minimum identification of the specific document and shall appear on the cover and title page. The contract number shall also appear on the cover and title page as separate markings. The originator and organization shall be included on the title page. The document number, change legend and date shall appear on each page of the document. All Type 1 documentation shall be marked “PRELIMINARY PENDING NASA APPROVAL,” and once approved shall be reissued with “APPROVED BY NASA” and the date and approval authority annotated on the cover.

Data Restriction Determination and Marking Requirements: The contractor shall properly mark data in accordance with the data rights clause(s) included in the contract. The contractor shall mark data deliverable sections with appropriate data restrictions and export classifications. The contractor shall not apply the most restrictive classification to the entire data delivery if only applicable to one section. If NASA does not agree with the contractor applied data restriction, the Contracting Officer (CO) shall request supporting rationale for applied data restrictions. If NASA does not agree with the rationale, the CO shall return the data to the contractor, cancel the markings, or ignore the markings consistent with the procedures set forth in the "data rights" clause(s) contained in the contract and per U.S.

export laws.

The contractor shall ensure all Controlled but Unclassified Information (CUI) is marked in accordance with NASA Procedural Requirements (NPR) 2810.7, Controlled Unclassified Information and ITS-HBK-CUI, Controlled Unclassified Information Handbook.

Reference to Other Documents and Data Deliverables in Data Submittals: The Contractor’s submittal of a DRD deliverable may refer to other documents and/or other DRD deliverables. At the time of submission of the DRD deliverable, any referenced document within the DRD deliverable shall be made available to NASA. The Contractor shall provide NASA with access to any referenced document and the location of that data within the referenced document. Any reference made to data associated with another DRD deliverable that is required separately by the contract, shall include the DRD number of and location of the data within the referenced DRD deliverable.

J01-7

Document Revisions:

The Contractor shall employ a system for organizing, identifying, and tracking all submittals of DRD deliverables, to include any changes, revisions, dates, NASA approvals, disapprovals and requested updates.

Revisions of documentation previously submitted may be accomplished either by individual page revision or by a complete reissue of the document.

A document shall be completely reissued when, in the opinion of the contractor and/or NASA, the document has been revised to the extent that it is unusable in its present state, or when directed by the CO. When complete reissues are made, the entire contents of the document shall be brought up to date and shall incorporate revised pages. All revisions shall be recorded. A revision log shall identify complete reissues except for periodic reports and documents, which are complete within themselves as final.

Individual page revisions shall be made as deemed necessary by the contractor or as directed by the CO.

Changes of a minor nature to correct obvious typing errors, misspelled words, etc., shall only be made when a substantial change is made, unless the accuracy of the document is affected.

All revised pages shall be identified by a revision identifier and a new date. Each document shall contain a log of revised pages that identify the revision status of each page with the revision symbol. This list shall follow the table of contents in each document. The line or lines revised on a given page shall be designated using vertical line in the margin of the page, and the change authority shall be indicated adjacent to the change.

CDRL/DRD MAINTENANCE PROCEDURES

NASA-Initiated Change: New and/or revised data requirements shall be incorporated by contract modification to which the new or revised portion shall be appended. The contractor shall notify the CO in the event a deliverable data requirement is imposed and is not covered by a DRD, or when a DRD is changed by a contract modification and for which no revision is appended.

CDRL or DRD Change Procedures Revisions to the CDRL or DRDs will be identified by NASA in the Document Change Log. The date of the revision, DRD number, title, and revision description will be annotated in the Document Change Log. Revision descriptions will include the modification number, which implements the change, and a brief description of the portions of the CDRL and/or DRD affected within the “Revision” column of the Document Change Log.

J01-8

Contract Data Requirements List DRD No. DRD Type DRD Title OPR

USDV-1 1 Program Management Plan (PMP) Transportation Integration Office (ON)

USDV-2 2 Program Management Review (PMR) ON

USDV-3 1 Project Life-Cycle Review Plan and Data Packages ON

USDV-4 1 Concept of Operations (ConOps) ON

USDV-5 1 Insight Management Plan ON

USDV-6 2 Work Breakdown Structure (WBS) and WBS Dictionary

Program Planning & Control (OH)

USDV-7 3 Integrated Program Management Report (IPMR) OH

USDV-8 3 Contractor Financial Management Report

(NF533)

Program Resources Office (LC)

USDV-9 N/A RESERVED N/A

USDV-10 1 Organizational Conflicts of Interest (OCI) Plan Office of Procurement

(BG)

USDV-11 1 Small Business Subcontracting Plan and Reports Office of Small Business Programs (BA)

USDV-12 3 Diversity, Equity, Inclusion, and Accessibility (DEIA) Plan BG

USDV-13 1 Configuration Management Plan OH

USDV-14 1 Information Technology Security Management Plan (ITSMP) OH

USDV-15 2 Export Control Plan External Integration Office (OX)

USDV-16 3 Government Property Management Plan BG

USDV-17 3 Financial Reporting Contractor-Held Property Accounting Services

J01-9

Office (LF)

USDV-18 1 Safety and Health Plan Safety and Test Operations Division (NS)

USDV-19 2 Risk Management Plan (RMP) Safety & Mission Assurance/Risk (OE)

USDV-20 1 Safety and Mission Assurance (S&MA) Plan OE

USDV-21 1 Safety Data Package (SDP) OE

USDV-22 2 Mishap Preparedness and Contingency Plan OE

USDV-23 1 Technology Readiness Level (TRL) and Technology Maturity Assessment

Engineering Directorate

(EA)

USDV-24

Software Management Plan (SMP) Avionics & Software

(OD)

USDV-25 2 Design, Development, Test, and Evaluation (DDT&E) Plan ON

USDV-26 1 Verification and Validation (V&V) Plan ON

USDV-27 2 System Engineering Management Plan (SEMP) ON

USDV-28

2 (Plan) 3 (Imagery)

Imagery Plan Mission Integration & Operations Office (OC)

USDV-29 1 US Deorbit Vehicle (USDV) Transportation and Logistics Requirements Plan ON

USDV-30 1 USDV Spacecraft Readiness Plan ON

USDV-31 3 Data Input for NASA Integration and Independent Verification and Validation (IV&V) ON

USDV-32 1 Assembly, Integration, and Test (AI&T) Plan ON

USDV-33 1 NASA Standards and Specifications Compliance and Tailoring ON

USDV-34 2 Mass Properties Report System Engineering & Integration Office (OM)

J01-10

USDV-35 2 Engineering Computer-Aided Design (CAD) Models OM

USDV-36 2 USDV Acceptance Data ON

USDV-37 1 Command and Telemetry Dictionary Flight Operations Directorate (FOD) (CA)

USDV-38 2 Operations Data Book CA

USDV-39 2 Models and Simulation Plan CA/EA/OD

USDV-40 1 USDV Launch Site Integration Plan (LSIP) ON/Launch Services Program (LSP)

USDV-41 2 Launch Site Integration & Test Procedures ON/LSP

USDV-42 2 USDV Launch Commit Criteria (LCC) ON/LSP

USDV-43

1 (Plan) 2 (Results)

Post Dock Assessment ON

USDV-44 1 Qualification and Acceptance Plan ON

USDV-45 1 Guidance, Navigation and Control (GNC) Controller Model ON

USDV-46 1 Specification for USDV Hardware In The Loop (HITL) Test Bed OD/ON

USDV-47 1 Specification for USDV Simulator for ISS integration testing OD/ON

USDV-48 1 Flight Operations Review Data Package CA

J01-11

1. DRD Title: Program Management Plan (PMP)

2. DRD No.: USDV-1 3. Data Type 1 4. OPR: ON

5. Solicitation No.: 80JSC023R0003

6. Contract No.: To be filled in by CO at contract award

7. Date Issued: To be filled in by CO at contract award

8. Date Revised: To be filled in by CO at first revision of this DRD after contract award

9. DRD Category:

☒ Technical ☐ Administrative

☐ S&MA

10. Description/Use: Describes the Contractor’s organization philosophy for managing contractual, program, technical, operations, and interfaces with respect to their internal business unit, subcontractors, and associate contractors. Allows for re-calibration of the NASA – Contractor interface points during the period of performance.

11. Distribution:

1 electronic copy: ISS Program Authorized Repository Program Authorized Repository Upload Notification:

Contractor’s CO

BG/CO

OA/COR and Alternate COR ON/USDV Lead OH/Assessment Office

Initial Submission: Initial: PMP paragraphs a-o, provide with proposal

Additional Submissions: Full PMP update due at 30 working days post contract award, Final due at Mission Concept Review (MCR)

Submission Frequency: The plan shall be reviewed annually for currency and submitted by Sept. 30th if updates are required to reflect changes to the plan. If no changes to the plan are required, the Contractor shall submit an EDMS delivery notice indicating this.

Format: The Contractor’s format is acceptable and in accordance with Data Format section at the beginning of this attachment.

Interrelationship: SOW: 2.1 Program Management, 3.6 Mission Concept Review (MCR);

DRD: USDV-2, USDV-3, USDV-19, USDV-20, USDV-27

Applicable Documents: SSP 50175, ISS Risk Management Plan

Scope: The PMP describes the Contractor’s overall plan for managing the contracted scope of work.

Contents:

The plan shall describe the Contractor’s approach to managing the contract scope, including

J01-12 management approach, performance management implementation, teaming arrangements, communication processes, strategies, policies, processes for work planning, work prioritization, subcontractor management, supply chain management, indirects management, Associate Contractor Agreements, facilities, operating locations, use of Government provided services, and any efficiencies planned. The plan shall include the following descriptions (not limited to):

a. Identify all available corporate resources that will be used on this contract, including personnel, facilities, and equipment, which are either internal or external to this contract, and methods and risks associated with obtaining these resources. Identify management, technical, and business approaches, strategies, policies, and processes used to assign, monitor, measure, control, and accomplish contractual tasks and performance and integrate cost, schedule, and technical performance across all areas of the contract. Describe processes and procedures used to manage workload definitization, assignment, prioritization, surges, and use of shared personnel and facility resources.

b. Provide a contract-specific organization chart, including subcontractors, and teaming partner(s), as applicable, and a rationale for the approach selected. Define the direct lines of control, responsibilities, functional relationships, and authority between the USDV program management and the Contractor’s other organizational elements, corporate management, and subcontractors/teaming partners. If there is a subcontracting or teaming arrangement, include specific details on how the subcontractor or teaming partner is managed, how their performance is incentivized, the business size of each company, the relative amount of work to be performed by each, and if there are discreet tasks to be performed by each or whether there is co-mingling of personnel and resources.

c. Describe the approach to delivering all technical data, computer software, and computer software documentation developed and delivered under this contract or otherwise incorporated within a system provided under this contract with Government purpose rights or better. Further, describe the Contractor’s approach to incorporating any data not first produced in the performance of this contract into data delivered under this contract and how this process conforms to the requirements in Clause I.15

FAR 52.227-14, RIGHTS IN DATA—GENERAL (MAY 2014) ALTERNATE II

(DEC 2007) [(MODIFIED BY NFS 1852.227-14 (APR 2015)] ALTERNATE III

(DEC 2007) ALTERNATE V (DEC 2007), and Clause H.17 IDENTIFICATION

AND REPRESENTATION OF LIMITED RIGHTS DATA AND RESTRICTED

COMPUTER SOFTWARE AFTER AWARD.

d. Describe Contractor’s approach to vetting subcontractor assertions of limited rights data and ensuring all data delivered to the Government is delivered with appropriate contractual markings.

e. Describe plans for staffing location, including lease arrangements, for the Contractor’s off-site facilities including a discussion of the government on-site and off-site approach (if needed). Discuss logistics management plans consistent with Contractor’s management approach to deliver the full scope of the USDV contract for events occurring at Contractor off-site, at government on-site facilities, including

J01-13 transfer of flight hardware to the next level integrator.

f. Describe all USDV contractor interfaces between the Contractor and the Government;

describe the Contractor’s plan to create an efficient and effective interface to the Government for the management, performance, communication, program schedules, deliveries, integration, testing, operations, and information technology required to complete the contract requirements. Describe the approach and process for conducting reviews with NASA management, such as Program Reviews, technical reviews, Project Life-Cycle Reviews, contract reviews, Technical Interchange Meetings (TIMs) with NASA, NASA panels and control boards, and working groups.

g. Describe the Contractor’s approach to key personnel. For each key personnel position identified, include qualification requirements for that position, selection process for that position, roles and responsibilities of that position, interfaces the position has with the Government, and transition process of personnel in that position during contract execution in accordance with Clause H.6, NFS 1852.235-71 KEY PERSONNEL

AND FACILITIES (MAR 1989).

h. Describe the approach to Contractor’s decision-making process and authority (e.g., working groups, panels, and control boards), and interfaces with NASA control boards for approval of system baseline, and baseline changes that could impact the USDV, ISS, or crew. Describe Contractor's approach to making decisions about the management, operation, and design of the USDV System that impact lifecycle costs, while still ensuring NASA requirements are met. Describe the Contractor's approach to handling dissenting opinions (operational and non-operational). Describe the governance structure.

i. Describe the Contractor’s approach, process, and timeline for work authorization, and assignment from identification of new work through Authority to Proceed (ATP) to subcontractors, to include but not limited to evaluation of NASA Change Requests, generation of Basis of Estimate Rough Order of Magnitudes, tailoring requirements;

requests for Government furnished resources; assertions of data rights, delivery of quality and timely proposals, and responses to Request for Task Order proposals.

j. Describe the approach for how the Contractor manages and reports risk. Specify the program/project risk objectives and policy toward risk. Provide an overview of the risk management process and information flow; describe how the risk management process integrates and relates to other project management and system engineering activities including but not limited to lessons learned reporting, System Safety analyses, reliability/probabilistic risk analyses, schedule, financial, and other business reporting systems. Include general risk mitigation strategies to be employed throughout the project life cycle. The Contractor’s approach shall be consistent with SSP 50175, ISS Risk Management Plan and the details provided in Risk Management Plan (DRD USDV-19).

k. Describe the Contractor’s approach and rationale to implementing a performance management system including specific performance objectives, measurements, standards, and tools used to manage, report, improve, and adapt performance against the project baseline across the full scope of work on contract.

J01-14

l. Identify the Contractor’s controls applicable to tasks, activities, and projects exceeding established schedule baselines and discuss Contractor’s approach and methods to recover, while ensuring the full scope of contracted effort is delivered in accordance with contractual obligations.

m. Describe the Contractor’s Systems Engineering approach, processes and tools used to implement the contracted technical effort and document the overall technical approach, maintain integrity between NASA and Contractor requirements to the Contractor verification plans, and to transition the products through the lifecycle (for both Contractor and subcontractor efforts). The Contractor’s approach shall be consistent with the details provided in System Engineering Management Plan (SEMP)

(DRD USDV-27).

n. Describe the Contractor’s approach to the scalability to support Indefinite Delivery, Indefinite Quantity (IDIQ) task ordering Contract (CLINs 3-5) and Changes to baseline work (CLINs 1 & 2) including lead times covering the full scope of this work anticipated for this contract. Describe the approach to staffing, maintaining, and augmenting a qualified workforce to meet contract needs in a timely manner through the life of the contract, including dwell and sustaining. Describe the overall management approach for attracting and retaining personnel capable of meeting contract requirements at a high level of excellence. Describe the staffing and skills required for proper accomplishment of the contractual tasks. Describe the strategy to ensure personnel will maintain the minimum qualification standards described in the Standard Labor Categories. For the proposal, state how many personnel are currently available and how many new hires are required to staff fully to accomplish the USDV contract with the Contractor’s proposed baseline schedule.

o. Describe the Contractor’s approach and methodology to obsolescence and life extension management in the case of an extended Dwell to ensure a reliable USDV is delivered and sustained in accordance with Safety and Mission Assurance (S&MA) Plan (DRD USDV-20) and USDV sustaining support remains available to meet - NASA requirements throughout the life of the contract.

p. Include an approach to identifying, resolving, and prioritizing conflicts between contract performance and Contractor’s work in support of other Government and commercial customers.

q. Discuss the management approach to obtaining and maintaining all required local, state, federal, licenses, permits, and agreements required in the performance of the contract.

r. Describe how management policies, procedures, and techniques are monitored to ensure their effectiveness and facilitate continuous improvement.

s. Describe the methods and plans to identify and correct deficiencies. Describe the Contractor’s approach to identifying and resolving Corrective Actions and the Government’s role when applicable.

t. Identify performance metrics for contract surveillance by NASA that are consonant with the importance of the products and services delivered, and which provide the ability to evaluate the quality, quantity, and timeliness of the Contractor’s

J01-15 performance outputs. These metrics shall include references to SOW paragraphs for the three categories: most important outcome-based metrics, leading indicator metrics, and trend metrics.

u. Describe the Contractor’s approach to implementing Associate Contractor Agreements and identify the specific agreements and purpose, which are required to conduct the USDV contractual obligations.

v. Provide the data and records data management plan, which describes the Contractor’s plan to store, provide access to, and transition at contract end, all deliverable data and records generated during the contract and transitioned to the contract. The plan shall define the scope and depth of the Contractor’s efforts including management, organization, planning, and implementation. The plan shall include the following elements: 1) data and records identification, 2) data and records control, 3) data and records status accounting, 4) data and records acquisition, 5) data and records management and verification, 6) data and records management organization, 7) data and records storage and retrieval procedures, 8) subcontractor procedures, 9) special restrictions, 10) process to transition data and records at contract end, and 11) NASA Records Management training for personnel responsible for managing records. The plan shall include the data submittal schedule for fulfilling submission of data in the specific quantities, media, and due dates required.

w. Describe Contractor’s approach to Sensitive Positions in accordance with Clause I.1.II NFS 1852.223-74, Drug- and alcohol-free workforce for this contract. Provide the list of contractor and subcontractor positions that the contractor has identified for this contract.

x. Discuss the Contractor’s approach to facilitate a proactive and efficient close-out of the contract.

Remarks: It is not intended that this plan duplicate other plans called for in other DRDs. This plan shall summarize the overall project and reference or summarize other plans where appropriate and shall reference Contractor internal procedures where applicable.

The final plan, as approved, shall be incorporated in the contract as Attachment J-06, Program Management Plan.

Maintenance: DRD deliverable submittals shall include two versions: 1) Clean copy with redlines incorporated, and 2) Redlined version showing the updates made since the last submittal.

J01-16

1. DRD Title: Program Management Review (PMR)

2. DRD No.: USDV-2 3. Data Type: 2 4. OPR: ON

7. Date Issued: To be filled in by CO at contract award

8. Date Revised: To be filled in by CO at first revision of this DRD after contract award

9. DRD Category:

☒ Technical ☐ Administrative

☐ S&MA

10. Description/Use: The following contains the data that the Contractor shall provide in support of each quarterly PMR. PMRs provide an opportunity for discussions and technical interchange between NASA and the Contractor regarding progress of USDV contract.

11. Distribution:

1 electronic copy: ISS Program Authorized Repository Program Authorized Repository Upload Notification:

Contractor’s CO BG/CO and CS OA/COR and Alternate COR and Alternate COR OH/ISS Data Management ON/USDV Lead

LC/ISS Resource Management Office

Initial Submission: Initial PMR shall occur 90 calendar days after contract start. Data shall be submitted two (2) calendar days prior to the meeting.

Additional Submissions: Quarterly. Data shall be submitted two (2) calendar days prior to the meeting.

Submission Frequency: The PMRs shall occur quarterly. For the cases where a PMR coincides with a required Project Life-cycle Review prescribed the SOW, the PMR may be combined with the required review.

Format: Specific formatting to be tailored by NASA/Contractor.

Interrelationship: SOW: 2.1.1 Program Management Review (PMR), 5.0 Dwell (CLIN 3);

DRD: USDV-1, USDV-3, USDV-7, USDV-8, USDV-9, USDV-19, USDV-20, USDV-23,

USDV-24, USDV-25, USDV-30, USDV-32

Applicable Documents: N/A

Scope: As a basis for the discussions and technical interchange, the PMR Briefing Package shall detail the Contractor’s technical progress, risk assessment, schedule status, and forward

J01-17 plans.

Contents:

The data and reviews shall cover all aspects of the contract. Specific agendas for reviews with NASA shall be co-managed by NASA and the Contractor. For each data package and review, the contractor shall provide/present the following:

a. Summary of IPMR (DRD USDV-7) including:

1. Summary of progress to date, critical path, and schedule reserves.

Identification of interdependencies among tasks associated across all CLINs, and associated risks, impacts, and mitigation plans.

2. For all cost plus and fixed price tasks:

i. Format 6, which defines and contains the contractor’s Integrated

Master Schedule (IMS).

3. For cost plus only:

i. Format 1, which defines cost and schedule performance data by product oriented WBS.

ii. Format 2, which defines cost and schedule performance data by the contractor‘s organizational structure (e.g., Functional or Integrated Product Team (IPT)).

iii. Format 3, which defines changes to the Performance Measurement Baseline (PMB).

iv. Format 4, which defines staffing forecasts.

v. Format 5, which is a is a narrative report used to provide the required analysis of data contained in Formats 1-4 and 6.

vi. Format 7, which defines the time-phased historical & forecast cost submission

b. Closure status of action items from previous PMRs, Project Life Cycle Reviews, and corrective actions, including their status, due date, estimated closure date, closure plan, and closure rationale.

c. Current status: provide cost/schedule/technical status with explanations and risk.

Include drivers of any schedule slips, cost variance at complete (cost-plus only), and technical issues. Include critical path items and estimated closure dates.

d. Issues and problems (including at subcontractor/suppliers) affecting schedule, quality, performance, risks, and mitigation plans.

e. The status, closure plan and schedule to demonstrate compliance to the contract requirements. This shall include:

1. Status of Key Design Parameters, which track the implementation of key requirements.

J01-18

2. Technical performance status related to margins, comparison of actual versus predicted margin for Technical Performance Measures, resolution of the previous review discrepancies addressing effectiveness of technical achievement and communicating the overall risk to the project.

3. Summary status of trade studies, including their status, completion or due date, estimated closure date, and closure plan

4. A status of the USDV design requirements, verification and validation (V&V activities, and Verification Closure Notice (VCN) closures with NASA acceptance status.

5. A summary of any tasks required to be repeated in the event of changes to the USDV baseline.

f. Status MCR and Milestones Schedule – Next 120 days

1. Program Plan (major events), plan, actual, and forecast dates for all major events.

2. Major upcoming events (next 6 months)

g. Change Management

1. List of all changes dispositioned over the past quarter

2. List of all changes currently under evaluation

h. Burn down charts with prior and current period status along with an executable and achievable burn down plan showing:

1. Requirement Trends (% growth, number of requirement changes, TBD/To Be Reviewed (TBR)s burndown)

2. Interface Trends (% Interface Control Document (ICD) approved, TBD/TBR burndown, number of interface change requests)

3. Engineering drawings scheduled to be released vs released

4. Purchase orders required, issued, definitized, closed

5. Number of parts needed, ordered, and received

6. Software-unique Trends (number of requirements/features per build/release vs.

plan)

7. Review Trends (Request for Action/Review Item Discrepancy (RID)/Action

Item closure)

8. Verification Trends (VCN closure burndown, Deviation/Waivers, non-conformances, non-compliance (anticipated/approved/open))

9. Problem Report/Discrepancy Report Trends (number open and closed)

10. Manufacturing Trends (number of Material Review Board (MRB) nonconformance/corrective actions) Note: Refer to OCE-52, NASA Common Leading Indicators Detailed

J01-19

Reference Guide.

i. Test status including a summary of all development, qualification, acceptance, and integrated system testing schedules and results.

j. Status of Long Lead Parts procurement, including outstanding and completed.

k. Risk management status that includes a description of the top USDV programmatic risks (e.g., Technical, schedule) with a discussion of potential impacts to the USDV System safety, technical, cost and schedule performance, and the Contractor’s mitigation strategies, and any areas for potential Government assistance.

l. Contractor’s progress in safety, engineering, manufacturing, fabrication, testing, logistics, configuration management, sustaining, and/or quality assurance issues, and other areas identified as high risk.

m. Safety and Mission Assurance (S&MA):

1. S&MA key issues and concerns, including impact, action plan, and projected resolution date

2. Detailed content related to S&MA disciplines reliability, Probabilistic Risk

Assessment (PRA) inputs, Electrical, Electronic and Electromechanical (EEE) parts, quality assurance, materials and processes, system safety, and software assurance

3. Status of analyses with traceability to subsystem/system

4. Summary of activities for that period to include issues/resolutions, analyses results, test results, and nonconformances

5. Failures, anomalies, waivers/deviations, audits & findings (including Product

Assurance Action (PAA) closures and status), mishaps, and quality metrics

6. Summary of upcoming activities for the next period including level of confidence to successfully achieve the next period (including Dwell and Launch)

7. Status of corrective actions and open items

n. Status of Flight Operations products and support including:

1. USDV-to-Ground ICD development

2. Status of mission support facilities (e.g., Remote Mission Evaluation Room )

3. Input to flight procedures, flight rules, training products, etc.

4. Status of simulators and readiness to support joint simulations

o. Status on inputs to ISS integration

p. Status on inputs to launch vehicle integration

q. Listing of DRD submissions and summary level of the changes made since last PMR and forecast of updates and summary level of the changes for DRD submissions planned for upcoming quarter.

J01-20

r. Insight and collaboration status highlighting current status of NASA/Contractor interfaces, tools, and processes used for establishing effective, efficient, and transparent insight, and collaboration between Government and Contractor teams at all levels.

s. Summary status of the special task and study assignments (under CLIN 5) that were started, in work, or completed since the previous PMR. Forecast of tasks and milestone completion for special task and study assignments (under CLIN 5) to be performed for upcoming quarter.

t. Status of progress on signed contracts and agreements with subcontractors, vendors, suppliers, and partners, as forward plans.

u. Special topics/other areas as identified by NASA and Contractor during PMR agenda coordination.

v. Readiness to support a Launch-12 month call-up for launch.

w. Any areas where the contractor would like to explore opportunities for Government assistance.

x. Rate Impacts (CLIN 1 Cost Reimbursable Only): cumulative rate impacts by fiscal year for each year of the contract and explanations for rate increase and/or decreases.

Include prime and subcontractor rate impacts as well as any known forecasted rate impacts, which may impact the contract in the future.

y. If in Dwell, the Contractor shall present status and provide the following additional information at the PMR:

1. Compliance with activity and operations described in USDV Spacecraft Readiness Plan (DRD USDV-30)

2. Summary of the overall health and status of the USDV

3. Preventative and corrective maintenance performed since previous status review or initial arrival at dwell facility (as applicable)

4. Testing and inspection performed since the previous status

5. Summary of closure of action items, anomalies, and issue resolutions from previous status review

6. Identification of any new anomalies, issues, or non-conformances since the previous review and resolution or the proposed resolution plan

7. Status of limited-life items

8. Summary of preventative maintenance, testing, inspection, or other activity and operations scheduled to be performed prior to the next status review

9. Status on inputs to operational products

10. Status of operations and sustaining teams’ proficiency

11. Road-to Plan for the Ship-to-Launch Site (if notification of launch date has been received from NASA) including identification of key tasks and key

J01-21 decision points required for USDV readiness to ship to launch site Color Definitions:

Green: early/on-time schedule delivery; no technical issues.

Yellow: projected late delivery but potential to recovery schedule; technical issues being worked, but no Government help needed.

Red: schedule unrecoverable; technical issues requiring Government help.

Remarks: The Contractor shall publish PMR charts at least two (2) calendar days prior to the meeting. The Contractor shall publish PMR final charts, minutes, actions, and estimated closure dates within seven (7) calendar days after the meeting.

Quarterly Review data package shall be delivered on the last Thursday of the month following the end of the quarter.

Maintenance: Electronic changes shall be incorporated as required by change page or complete reissue.

J01-22

1. DRD Title: Project Life-Cycle Review Plan and Data Packages

2. DRD No.: USDV-3 3. Data Type: 1 4. OPR: ON

6. Contract No.: To be filled in by CO at contract award

7. Date Issued: To be filled in by CO at contract award

8. Date Revised: To be filled in by CO at first revision of this DRD after contract award

9. DRD Category:

☒ Technical ☐ Administrative

☐ S&MA

10. Description/Use: To establish an agreement between NASA and the Contractor on planning, preparing for, entrance and exit success criteria, data delivery and conducting Project Life-cycle Reviews.

Describes the Contractor’s methodology, actions, and readiness to satisfy Project Life-Cycle reviews. To establish the data required for Project Life-Cycle Reviews listed in CLIN 1 and CLIN 2.

11. Distribution:

1 electronic copy: ISS Program Authorized Repository Program Authorized Repository Upload Notification:

Contractor’s CO

BG/CO

OA/COR and Alternate COR OH/ISS Data Management

Initial Submission:

Project Life-Cycle Review Plan: Initial (paragraph a only) Provide with Proposal.

Joint Integration Plan (JIP): MCR JIP due at Contract Kickoff. System Acceptance Review (SAR) JIP due at SAR – 6 months. All other JIPs at least 120 calendar days prior to the review

Final electronic copy of the Project Life-Cycle Review presentation(s) and all data pack material to NASA at least thirty (30) calendar days before the review is held.

Submission Frequency:

Project Life-Cycle Review Plan: Final due at MCR. Update required for currency if the content changes Project Life-Cycle Review Data packages: Submitted to Program Authorized Repository (EDMS or equivalent) are due 30 calendar days prior to each scheduled review.

Format: The Contractor’s format is acceptable and in accordance with Data Format section at the beginning of this attachment.

Interrelationship: SOW: 2.7 Project Life-Cycle Reviews, 3.6 Mission Concept Review (MCR), 3.7 System Requirements Review (SRR), 3.8 System Definition Review (SDR), 3.9 Preliminary Design Review (PDR), 3.10 Critical Design Review (CDR), 4.2.4 System Integration Review (SIR), 4.3.3 Assembly, J01-23

Integration, and Test Progress Review (APR), 4.4.5 System Acceptance Review (SAR), 4.5.1 Shipment to Space Station Processing Facility, 4.5.2 Dwell Release Review (DRR), 4.5.3 Shipment to Launch Site Payload Processing Facility; DRD: USDV-1, USDV-2, USDV-4, USDV-5, USDV-10, USDV-13, USDV-19, USDV-20, USDV-21, USDV-22, USDV-23, USDV-24, USDV-25, USDV-26, USDV-27, USDV-28, USDV-29, USDV-30, USDV-31, USDV-32, USDV-33, USDV-34, USDV-35, USDV-36, USDV-37, USDV-38, USDV-39, USDV-40, USDV-41, USDV-42, USDV-44, USDV-46, USDV-47

Applicable Documents: N/A

Scope: This covers Project Life-Cycle Reviews in CLIN 1 and CLIN 2.

Contents:

a. The Contractor shall deliver a Project Life-Cycle Review Plan, which includes the reviews identified in the contract requirements SOW CLIN #s 1 and 2. The review plan shall describe the process for developing the JIP for each applicable review, the review process (including any specific tools and tool training required to conduct the review), schedule, location, deliverables, delivery method, delivery dates, means, and timing by which data will be made available to NASA, document review dates, presentation meetings, TIMs, pre-boards, boards, and other logistics related information. The Contractor shall describe in the Project Life-Cycle Review Plan the approach for review input and disposition, including how to submit comments, when the comments are due, joint disposition process, actions, action recording and tracking, configuration management of review products, and review minutes. The plan shall ensure NASA has adequate time and access to the data to perform meaningful technical reviews. The plan may be segregated into volumes for individual reviews or split up accordingly to optimize incremental updates.

b. The Contractor shall prepare, jointly with NASA, and deliver for NASA review, feedback and concurrence a JIP specific to the following Project Life-Cycle Review Reviews and Contractor proposed interim milestones in CLIN 2 at least 120 calendar days prior to the review that describes all components required to hold a successful review: MCR, System Requirements Review (SRR), System Definition Review (SDR), Preliminary Design Review (PDR), Critical Design Review (CDR), System Integration Review (SIR), Assembly Integration and Test Progress Review (APR), System Acceptance Review (SAR), Pre-Ship Review (PSR), Dwell Release Review (DRR). This shall include the review schedule, the review agenda, jointly agreed to detailed entrance and exit criteria, expected NASA and Contractor processes, instructions to the review board, mapping of data requirements to specific Contractor provided products and locations within data pack, etc. The Contractor shall include in the JIP a detailed mapping of the NASA data requirements for each review to the Contractor specific plans, documents, reports, etc.

by document number, title, revision, date, and specific location in the data package on where to find that information. The Contractor may include additional data elements above the NASA data elements, which may be beneficial to the Government to aid in its understanding of the Contractor’s approach, plans, processes, status, and expected performance to facilitate a successful review. NASA may request additional data elements during the review process to aid its understanding of the Contractor’s approach, plans, processes, status, and performance.

c. The Contractor shall submit a final electronic copy of the Project Life-Cycle Review presentation(s) and all data pack material to NASA at least thirty (30) calendar days before the review is held.

J01-24

d. The Contractor shall provide responses to any NASA questions within ten (10) calendar days.

e. The Contractor shall prepare and deliver the following documents within seven (7) calendar days following the Project Life-Cycle Review:

1. Final presentation and documents

2. Meeting Minutes

3. List of attendees

4. Agreements from each review

5. Actions, actionee, status and due dates, estimated closure date from each review

f. The Contractor shall prepare, maintain, and deliver an action item list that includes:

1. Assigned tracking number for each action item

2. Action

3. Subject

4. Due Date

5. Person or organization responsible for completing the action

6. Status of action (i.e., open, closed, or withdrawn)

7. Closure rationale

1.0 Part 1: CLIN 1 Project Life-Cycle Reviews

1.1 Mission Concept Review (MCR)

The MCR Data Package shall deliver data and presentations to address the MCR elements defined in the SOW Section 3.6 Mission Concept Review (MCR).

1.2 System Requirements Review (SRR)

The SRR Data Package shall deliver data and presentations to address the SRR elements defined in the SOW Section 3.7 System Requirements Review (SRR).

1.3 System Definition Review (SDR)

The SDR Data Package shall deliver data and presentations to address the SDR elements defined in the SOW Section 3.8 System Definition Review (SDR).

1.4 Preliminary Design Review (PDR)

The PDR Data Package shall deliver data and presentations to address the PDR elements defined in the SOW Section 3.9 Preliminary Design Review (PDR).

1.5 Critical Design Review (CDR)

The CDR Data Package shall deliver data and presentations to address the CDR elements defined in the SOW Section 3.10 Critical Design Review (CDR).

J01-25

2.0 Part 2: CLIN 2 Project Life-Cycle Reviews

2.1 System Integration Review (SIR)

The SIR Data Package shall deliver data and presentations to address the SIR elements defined in the SOW Section 4.2.4 System Integration Review (SIR).

2.2 Assembly Integration & Test Progress Review (APR)

The APR Data Package shall deliver data and presentations to address the APR elements defined in the SOW Section 4.3.3 Assembly, Integration, and Test Progress Review (APR).

2.3 System Acceptance Review (SAR)

The SAR Data Package shall deliver data and presentations to address the SAR elements defined in the SOW Section 4.4.5 System Acceptance Review (SAR).

2.4 Space Station Processing Facility (SSPF) Pre-Ship Review (PSR) The SSPF PSR Data Package shall deliver data and…