80JSC023R003 USDV RFP Model Contract Attachment J-01 - Data Requirements Deliverable.docx

Attachment J-01

DATA REQUIREMENTS DESCRIPTION (DRD)

National Aeronautics and Space Administration Johnson Space Center 80JSC023R0003 Amendment 6

J01-10

DOCUMENT CHANGE LOG

DRD

No.

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.

NASA-Owned/Contractor Held records shall be managed by the Contractor in accordance with Title 36 of the Code of Federal Regulations, Chapter XIII B. Records Management and NPD 1440.6, NASA Records Management. The records shall be organized in accordance with the instructions in NPR.1441.1, NASA Records Management Program Requirements as applicable. The Contractor shall disposition records and non-records in accordance with NPR 1441.1, which has been approved by NASA. All questions on records management issues shall be directed through the Contracting Officer to the International Space Station (ISS) Records Liaison Officer (RLO) or applicable Program Office RLO.

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 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 delivery to NASA.

Data Distribution, Format, and Transmittal

Data Distribution:

The Contractor shall provide one copy of each DR to the standard distribution list shown in Item 10 of the DRDs. Additional distribution shall be made as directed, in writing, by the Contracting Officer. EDMS Delivery Notices will be used to confirm delivery of electronically resident DR Deliverables.

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.

Data 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). The Contractor shall attach an EDMS Delivery Notice (DN) to each deliverable to notify the Contracting Officer and the Contracting Officer Representative (COR) electronically of DR Delivery.

DRs listed as requiring updates: The Contractor shall review the document to ensure that all content in the deliverable is verified as current and accurate. If the Contractor’s review determines that all content in the deliverable is verified as current and accurate, the Contractor shall submit a transmittal memorandum with a Delivery Notice to the Program Authorized Repository (EDMS or equivalent) stating that the document has been reviewed for currency and accuracy and requires no revision at this time (referencing the most current version and date– Basic, Rev 1, with date). If the Contractor’s review determines that any content in the deliverable is not current and accurate, the Contractor shall resubmit the deliverable with appropriate updates to ensure it is current and accurate.

Data Transmittal Package:

For each DRD, the transmittal package shall:

a) Provide the following information in a Contractor transmittal memorandum:

1. Contract number

2. Task or Delivery Order number (if applicable)

3. DRD number

4. DRD data type

5. Submission date

6. Milestone being satisfied (if applicable)

7. Document number, date and revision

8. Document title

9. File names of all files being delivered; file naming convention shall clearly identify the document being delivered; multiple files per document must be clearly related to the document

10. NASA Records Retention Schedule (NRRS) number, if applicable (See NRRS 1441.1, NASA Records Retention Schedules)

11. Distribution (Notification list as defined by the DRD distribution field)

12. Targeted release date

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 provide comments to the contractor through the “rework” process detailing why it has not been approved. The contractor has 45 calendar days 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 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.

If data delivered under this contract is subject to the International Traffic in Arms Regulations (ITAR), the data shall contain an “ITAR Notice” as follows:

International Traffic in Arms Regulations (ITAR) Notice

This document contains information which falls under the purview of the United States (U.S.) Munitions List (USML), as defined in the International Traffic in Arms Regulations (ITAR), 22 CFR 120-130, and is export controlled. It shall not be transferred to foreign nationals, in the U.S. or abroad, without specific approval of a knowledgeable NASA export control official, and/or unless an export license/license exemption is obtained/available from the United States Department of State. Violations of these regulations are punishable by fine, imprisonment, or both.

Insert Destination Control Statement that includes export classification and corresponding export authority.

If data delivered under this contract is subject to the Export Administration Regulations (EAR), the data shall contain the “EAR Notice” as follows:

Export Administration Regulations (EAR) Notice

This document contains information within the purview of the Export Administration Regulations (EAR), 15 CFR 730-774, and is export controlled. It may not be transferred to foreign nationals in the U.S. or abroad without specific approval of a knowledgeable NASA export control official, and/or unless an export license/license exception is obtained/available from the Bureau of Industry and Security, United States Department of Commerce. Violations of these regulations are punishable by fine, imprisonment, or both.

Insert Destination Control Statement that includes export classification and corresponding export authority.

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.

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.

DRDs Submitted As Part of Project Life Cycle Review Data Packages Multiple DRDs are required to be delivered as part of Project Life Cycle Review Data Packages. All DRDs which have a submission tied to a Project Life Cycle Review (e.g. Critical Design Review (CDR), System Acceptance Review (SAR), Dwell Release Review (DRR) etc.) are due as part of the review data package thirty (30) calendar days prior to the life-cycle review per Project Life-Cycle Review Plan and Data Packages (DRD USDV-3). Following the review, these DRDs shall be submitted for NASA approval using an EDMS Delivery Notice with the required updates as agreed upon at the review no later than seven

(7) calendar days after successful completion of the life cycle review.

CDRL Submission Table The following includes a CDRL Submission Table for convenience. If any discrepancies exist between the information in the CDRL Submission Table and the DRD documentation, the information contained within the DRD takes precedence.

Proposal 1Competitive Range Proposal

Contract Award

Contract Start

only)

U + 30 working days (Full

PMP)

F

Review annually for currency and U by Sept. 30 if needed

Review (PMR)

I + 90 calend ar days

PMR convenes Quarterly.

PMR data package due last Thursday of the month following the end of the quarter and no later than 2 calendar days prior to the PMR PMR final charts, minutes, actions, and estimated closure dates due 7 calendar days after PMR;

Subset of PMR data package delivered monthly due last Thursday of month following the end of reporting month (CLIN1only)

U required for

Cycle Review

A only)

currency if the Plan

Plan and Data

content changes;

Packages

JIPs (other than MCR

(MCR

JIP) due 120 calendar

JIP

days prior to review;

only)

Data Packages due 30 calendar days prior to review

U as required to reflect changes that affect the Concept of Operations

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

J01-12

Proposal 1Competitive Range Proposal

Contract Award

Contract Start

F

Review annually for currency and U by Sept. 30 if needed

U + 30 calendar days as required for currency

With Proposal: IMSs, Summary Master Schedule, Native Schedule File Data Dictionary, Schedule Assumptions & SRA only

Monthly submittals NLT 16th Government working day after close of Contractor’s accounting period

Cost Performance Data Set required during CPIF only

I + 30 working days

Monthly submittals NLT 10th working day after close of Contractor’s accounting period or 15th calendar day of month, whichever is earlier

NF533 required for CPIF only

F + 30

Review annually for

Conflicts of calend currency and U by

Interest (OCI) ar days

Sept. 30 when

Plan contractor teaming arrangements change

Proposal 1Competitive Range Proposal

Contract Award

Contract Start

or potential OCI issues occur

Plan Approval prior to Contract Award; U Plan in accordance with FAR 19.702;

Reports submitted semi-annually and at contract completion

F + 30 working days

Reviewed annually by Sept. 30 and submit to reflect changes to plan with performance metrics and objectives from current or most recent organizational reporting period.

Review annually for currency and U by Sept. 30 to reflect changes to plan

I + 30 workin g days

Review annually for currency and U by Sept. 30 to reflect changes to IT POCs and/or plans, processes, and baseline configuration of the system(s) stated in the DRD

calendar days

Offeror(s) will be notified by the CO of this submittal requirement;

Review annually for currency and U by Oct. 15 to reflect changes to plan

Management Plan

calendar days

Offeror(s) will be notified by the CO of this submittal requirement;

Proposal 1Competitive Range Proposal

Contract Award

Contract Start

Review annually for currency and U by Sept. 30 to reflect changes to plan

Contractor-Held Property

Submissions per NFS 1852.245-73 and CHATS manual

I + 30

U annually by Oct. 1 as needed to reflect latest OSHA, JSC, and VPP requirements

Review annually for currency and U by Sept. 30 to reflect

I + 30 calend ar days (Vol. 2) U (Vol. 1 and 2) F (Vol. 1 and 2)

Review annually for currency and U by Sept. 30 to reflect changes that affect S&MA Plan implementation

Phase 0 ISRP Review

Phase I ISRP Revie w Phase II ISRP Revie w

Phase III ISRP Review Data submittals occur 20 working days prior to ISRP Reviews

Plan

I + 30 workin g days F

Review annually for currency and U by Sept. 30 to reflect

Assessment and Technology Maturation Plan

U as required to reflect changes that affect TRL Assessment and Technology Maturation Plan

Review annually for currency and U by Sept. 30 to reflect changes that impact Software

Proposal 1Competitive Range Proposal

Contract Award

Contract Start

Management Plan implementation

U

Review annually for currency and U by Sept. 30 to reflect changes that affect DDT&E Plan implementation

U as required to reflect changes that affect Verification and Validation Plan

I + 30

Review annually for currency and U by Sept. 30 to reflect changes that affect SEMP

I (Plan only) F (Plan only)

Imagery submittals will be due per the approved Imagery Plan

Transportation and Logistics Requirements Plan

U as required to reflect changes that affect USDV Transportation and Logistics Requirements Plan implementation

Spacecraft Readiness Plan

I

Plan implementation

Integration and Independent Verification and Validation

(IV&V)

U as required to reflect changes that affect delivery of data inputs to NASA for NASA Integration and IV&V efforts

I

U as required to reflect changes that

Proposal 1Competitive Range Proposal

Contract Award

Contract Start

Test (AI&T) Plan affect AI&T Plan implementation

Standards and Specifications Compliance and Tailoring

U

F

U as required to reflect proposed changes to NASA Standards and Specification Compliance and Tailoring

6, 9 month s as needed

U @ L – 6 weeks;

U @ Build complete, wetted;

U as required to reflect changes that affect USDV mass properties

month s as needed

Acceptance Data

F – 45 days (USDV) F – 6 months (USDV Training simulator) U for DRR (USDV), U as necessary after Government acceptance to reflect changes that affect USDV Acceptance Data (USDV)

and Telemetry Dictionary

within the ODB

U as required to reflect changes that

Proposal 1Competitive Range Proposal

Contract Award

Contract Start

OD

affect Models and Simulation Plan implementation

U as required to reflect changes that affect LSIP

Test (I&T) Procedures

F

U as required to reflect changes that affect Launch I&T Procedures

I

implementation

Dock) 1: Plan 2: Results

ON

I (Plan only)

U as required to reflect changes that affect Qualification and Acceptance Plan

Models and Data

I (Part A only) F (Part A only)

I (Part B only)

F – 6 months U as required to reflect changes that affect delivery of data and model inputs to NASA for the GNC models and data

Hardware-In- The-Loop (HITL) Test Bed

I

F

U as required to reflect proposed changes to the USDV HITL Test Bed specification

Simulator for ISS Integration Testing

I

F

U as required to reflect proposed changes to the USDV SDIL Simulator for ISS Integration Testing Specification

Proposal 1Competitive Range Proposal

Contract Award

Contract Start

I – 30

No final version of

Package calen the DRD. Post dar approval of a days procedure in FOR, U-30 procedures are calen updated through dar

Change Request days process as defined in prior

JSC-36054 Annex 2.

to

During mission

Delta execution, procedures

FOR

are updated per OIP

5.2.1.1.

1 Upon request from the Contracting Officer, the Initial DRD submittal is required only for those Offerors in the Competitive Range or Apparent Successful Offeror.

Legend

I = Initial U = Update F = Final

FY = Fiscal Year NLT = No Later Than APR = Assembly, Integration and Test (AI&T) Progress Review CDR = Critical Design Review DRR = Dwell Release Review FOR = Flight Operations Review IMS = Integrated Master Schedule JIP = Joint Integration Plan MCR = Mission Concept Review PDR = Preliminary Design Review SAR = System Acceptance Review SDIL = Software Development and Integration Laboratory SDR = System Definition Review SIR = System Integration Review SRA = Schedule Risk Assessment SRR = System Requirements Review

1. DRD Title: Program Management Plan (PMP)

☒ 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 through p, 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 shall be in accordance with Data Format section at the beginning of this attachment.

Interrelationship: SOW: 2.1 Program Management,2.2.2 Resource Management, 3.6 Mission Concept Review (MCR); DRD: USDV-2, USDV-3, USDV-19, USDV-20, USDV-27, Clause I.26, NFS 1852.234-2 Earned Value Management System

Applicable Documents: SSP 50175, ISS Risk Management Plan, EIA-748, AS9100

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

Contents:

J01-20

The plan shall describe the Contractor’s approach to managing the contract scope, including 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. Describe management and controls of hybrid contract (if proposed in USDV Contract Clause B.3) to ensure no transfer of costs from firm-fixed price to cost-reimbursable CLINs.

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.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), 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 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 Contractor’s 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 in response to Request for Task/Delivery Order Proposals and core contract Change Requests.

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 analyses, NASA probabilistic risk assessment (PRA), 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) post award.

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. Describe the Contractor’s approach to integrating across the prime contractor and its subcontractors the contracted scope, project management baseline, scheduling, budgeting, work authorization, establishment of objective performance measurements, cost accumulation (applies to CPIF only), performance assessments, management of costs to the contracted target cost value (applies to CPIF only), implementation of managerial actions taken as a result of earned value information (applies to CPIF only) and timely incorporation of NASA authorized changes into the schedule and budget baselines

l. Identify the Contractor’s controls applicable to tasks, activities, and projects exceeding established schedule and cost 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) post award.

n. Describe the Contractor’s approach to the scalability to support Indefinite Delivery, Indefinite Quantity (IDIQ) task/delivery 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 manufacturing / production spares to ensure USDV production maintains on schedule, the USDV is delivered on- time, and the USDV is sustained through its entire lifecycle.

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

q. Describe the Contractor’s approach to identifying, resolving, and prioritizing conflicts between USDV contract performance and Contractor’s work in support of other Government and commercial customers.

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

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

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

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

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

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

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

y. Describe the Contractor’s approach to implement and 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.

1. DRD Title: Program Management Review (PMR)

☒ 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 OH/ISS Data Management ON/USDV Lead OH/Assessment Office LC/ISS Resource Management Office

Initial Submission: Initial PMR data package be delivered on the last Thursday of the month following the quarter in review (e.g. for Quarter October – December 2024, data package is due January 30, 2025) and no later than two (2) calendar days prior to the meeting.

Additional Submissions: Quarterly. PMR data package shall be delivered on the last Thursday of the month following the quarter in review and no later than two (2) calendar days prior to the meeting.

The Contractor shall delivery PMR final charts, minutes, actions, and estimated closure dates within seven (7) calendar days after the meeting.

Submission Frequency: PMR data package shall be delivered on the last Thursday of the month following the quarter in review and no later than 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.

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-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, subcontractors’, vendors’ overall technical, schedule, cost (applies to CPIF only) performance as well as the Contractor’s risk assessment and forward 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:

1) Current status: provide cost/schedule/technical status with explanations and risk for full scope of contracted effort (note: cost applies to CPIF only). Provide previous reporting period and current Cost Performance Index (CPI) and Schedule Performance Index (SPI) (note: CPI and SPI applies to CPIF only). Include drivers of any schedule variances, schedule margins, cost variances at complete (note: cost variance applies to CPIF only), and technical issues. Include recovery plans and estimate closure dates.

2) Current schedule overview

a) Program Plan (major events), baseline planned vs actual, and forecast dates for all major events.

b) Major upcoming events (next 6 months)

c) Current Critical Path

3) Summary of Integrated Program Management Data Analysis Report (IPMDAR) (DRD USDV-7) including:

a) For both CPIF and FFP:

i) Summary of Schedule and Schedule Performance Data set

ii) Summary of Performance Narrative Report (PNR)

b) For CPIF only:

i) Summary of Contract Performance Data set

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

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

5) 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.

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

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

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

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

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

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

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

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

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

c) Engineering drawings scheduled to be released vs released

d) Purchase orders required, issued, definitized, closed

e) Number of parts needed, ordered, received, accepted

f) Software-unique Trends (number of requirements/features per build/release vs. plan)

g) Review Trends (Request for Action/Review Item Discrepancy (RID)/Action Item closure)

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

i) Problem Report/Discrepancy Report Trends (number open and closed)

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

8) Change Management

a) List of all changes dispositioned over the past quarter

b) List of all changes currently under evaluation

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

10) Status of Long Lead Parts

a) Procurement – planned vs actual performance, forecast for next quarter. Identify any risk mitigations.

b) Receipt and Acceptance – planned vs actual performance, forecast for next two quarters. Identify any risk mitigations.

11) Risk management status that includes a description…