J-2 Contract Data Requirements List A3.pdf

Attachment J-2

CONTRACT DATA REQUIREMENTS LIST (DRL)

AND

DATA REQUIREMENTS DESCRIPTIONS (DRDs)

National Aeronautics and Space Administration Johnson Space Center

DOCUMENT CHANGE LOG

DRD

No.

DRD Title Revision Date

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.

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

Data Requirements Description (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.

DRD Data Type Description: Each DRD is classified by data type as defined below:

TYPE DESCRIPTION

1 - All submittals of and interim changes to Type 1 DRDs require written approval from the contracting officer before formal release for use or implementation.

2 - NASA reserves a time-limited right to disapprove in writing any submittal of and interim changes to Type 2 DRDs. The contractor shall submit the required data to NASA for review within the time period established in the DRD prior to its release for use or implementation. The contractor shall clearly identify the release target date. If the data is unacceptable, the contracting officer will notify the contractor within the time period established in the DRD from the date of submission, regardless of the intended release date. The contractor shall resubmit the information for reevaluation if disapproved. The submittal is considered approved if the contractor does not receive disapproval or an extension request from the contracting officer within the time period established in the DRD.

3 – Type 3 DRDs shall be delivered as required by the contract and do not require NASA approval.

DRD Categories DRDs are grouped into categories for clarity and ease of reference. The categories and DRD abbreviations are defined as follows:

• MGMT = Management – DRDs that address contract management processes and employee compensation

• BP = Business Processes – DRDs that address non-technical business processes.

• IT = Information Technology – DRDs address IT requirements.

• SMA = Safety and Mission Assurance – DRDs that address safety assessments, problem reporting, and hardware/software quality assurance.

• OH = Occupational Health – DRDs that address occupational health and safety requirements

• INST = Institutional and Agency compliance DRDs – DRDs which include mandatory reporting requirements imposed by the Center and/or Agency.

Office of Primary Responsibility (OPR) BA – Office of Procurement (OP) IA – Information Resources Directorate JB – JSC Center Operations Logistics Division LA – Office of the Chief Financial Officer LF – Accounting Services Office NA – Safety and Mission Assurance Directorate NT – Quality and Flight Equipment Division OCIO – Office of Chief Information Officer OSMA – Office of Safety and Mission Assurance SA – Human Health and Performance Directorate SD = Space Medicine Operations Division

Code Definitions on Reporting Frequency for each DRD in CDRL AD, As Directed DA, Daily RD, As Released AN, Annually DD, Deferred Delivery RT, One Time and Revisions AR, As Required MO, Monthly SA, Semi Annually BA, Biannually OT, One Time TY, Three per Year BM, Bimonthly PV, Per Vehicle UR, Upon Request BW, Biweekly QU, Quarterly WK, Weekly

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 Distribution: In most cases, distribution is as directed by the Contracting Officer (CO), as noted in the DRDs.

Format: Offeror format is acceptable except where indicated within individual DRDs.

Electronic Format: Electronic submission of data deliverables is required. Electronic deliverables shall be printable. 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 a single Adobe Acrobat PDF file and the native format electronic file(s). The preferred native formats include Microsoft Word, Excel, or PowerPoint, as appropriate.

Transmittal: Data shall be transmitted to NASA via the mechanism agreed to by the Contracting Officer (CO), Contracting Officer’s Representative (COR), and project representatives who are responsible to receive, index, and store the data deliverables.

If email is used to transmit data deliverables, the email size shall be 10 megabytes or less to ensure receipt by the NASA email servers. Encrypted email format shall be used to transmit data.

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

1. Contract number

2. Data Requirements Description (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)

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 must make a determination for each individual data deliverable, and shall not apply a default or blanket data restriction marking to all data deliverables (e.g., “data may be export restricted”). If NASA does not agree with the contractor applied data restriction, 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.

Reference to Other Documents and Data Deliverables in Data Submittals: All referenced documents shall be made readily available to the cognizant NASA organization upon request.

Document Revisions: Revisions of documentation previously submitted may be accomplished either by individual page revision or by a complete reissue of the document. 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.

Contract Data Requirements List

DRD

No.

DRD

Type DRD Title OPR

MGMT-01 1 Contract Management Plan OP MGMT-02 1 Work Breakdown Structure (WBS) and Dictionary OP MGMT-03 1 Contract Management Reports OP MGMT-04 1 Staffing and Critical Skills Plan OP MGMT-05 1 Contract Phase-In Plan OP MGMT-06 1 Partnerships and Technology Incubation Plan OP

MGMT-07 RESERVED

MGMT-08 1 External Customer Plan SA MGMT-09 1 Continual Improvement Plan OP MGMT-10 1 Organizational Conflicts of Interest (OCI) Mitigation Plan OP MGMT-11 1&2 Small Business Subcontracting Plan OP MGMT-12 2 Contract Close-Out Plan OP BP-01 2 NASA Contractor Financial Management Report (533) OCFO BP-02 1 Records Management Plan OP BP-03 1 Flight Products Configuration Management Plan SA BP-04 1&2 Export Control Plan OP BP-05 3 New Technology Reporting Plan SA BP-06 1 Reports Required for Logistics JB BP-07 1 Financial Reporting—Contractor-Held Property JB BP-08 1 Government Property Management Plan JB BP-09 3 Reprocurement Incumbent Compensation Data Package OP

IT-01 2 Information Technology (IT) Capital Planning and Investment Control (CPIC) Plan OCIO

IT-02 1 Security Requirements for Unclassified IT Resources OCIO IT-03 1 Commercial IT Authorization Report (CITAR) OCIO SMA-01 1 Quality Plan NT

SMA-02 1 Electrical, Electronic and Electromechanical (EEE) Parts Control Plan NT

SMA-03 1&2 Safety and Health Plan NA SMA-04 1 Software Assurance Plan NT

SMA-05 1

NASA Advisory and Government-Industry Data Exchange Program (GIDEP) Problem Data Sharing and Utilization Program Documentation and Reporting

NT

OH-01 3 Occupational Health Monthly, Quarterly and Annual Work Achievement Reports SD

OH-02 3 Occupational Health Customer Satisfaction Surveys SD OH-03 3 Occupational Health Standard Operating Procedures SD OH-04 3 Workplace Health Inspection Reports SD

OH-05 3 Annual Sampling Strategy, Exposure, Monitoring, and Complaint Log SD

OH-06 3 Building and Facility Hazardous Material and Components Information SD

OH-07 3 JSC Chemical Inventory and SDS Database SD

OH-08 3 Occupational Health Database and SharePoint Management SA

INST-01 2 Environmental Compliance Reports JE

INST-02 RESERVED

INST-03 1 Supply Chain Visibility Reporting OSMA

1. DRD Title: Contract Management Plan

2. DRD No.: MGMT-01 3. Data Type: 1 4. OPR: OP

5. Solicitation No.: 80JSC024HHPC2 6. Contract No.: 80JSC025HHPC2

7. Date Issued: TBD 8. Date Revised: N/A 9. DRD Category:

☐ Technical ☒ Administrative

☐ S&MA

10. Description/Use: Contractor to provide a comprehensive plan to integrate, manage and track all aspects of the contract statement of work (SOW).

11. Distribution: Distribution shall be as instructed by the Contracting Officer (CO).

Submission:

• Initial – Contents section, elements 1 through 8 below, due with proposal

• Final – Complete Plan due at start of Phase-In

• Approval – By Contract start

Submission Frequency: Annual updates

Format: Contractor’s format is acceptable. The electronic file shall be compatible with Microsoft Office.

Interrelationship: SOW Section 1.0 Contract Management and Administration, DRD MGMT- 02 Work Breakdown Structure (WBS) and Dictionary, DRD MGMT-03 Contract Management Reports, DRD MGMT-04 Staffing and Critical Skills Plan; DRD MGMT-08 External Customer Plan

Applicable Documents: Clause H.11 Associate Contractor Agreements for HHPC2 Activities;

Clause H.21 Remote Worker Travel Costs; JPR 8000.4 JSC Risk Management Plan

Scope: The Contract Management Plan (CMP) shall describe the Contractor’s management approach, organization, and systems for accomplishing and managing all services and functions described in the SOW. The plan shall be comprehensive in nature and integrate all management systems of the prime, significant vendors, subcontractors, including Small and Small Disadvantaged businesses, teaming or partnering arrangements, and Associate Contractor Agreements (ACAs).

Contents: The Contractor shall address the following elements, at a minimum, in the CMP:

1. Overall proposed contract management approach, strategies, policies, processes, subcontractor management, significant vendors, small businesses, teaming/partnering arrangements, and indirect cost management including any efficiencies proposed.

2. Internal and external organizational structure (including a chart), explaining roles and responsibilities, subcontractors, parent corporations and other organizations, communication channels including lines of communication to NASA, lines of authority(including the line of succession of key personnel), cross matrix capabilities, reporting relationships and responsibilities of all organizational elements.

3. Reporting responsibilities of the Program Manager to corporate management and the relationship between the Program Manager and the prime’s corporate management, as well as the management of any subcontractors or team members and reach-back to cover staff shortages.

4. Teaming relationships and prime contractor to subcontractor arrangements, a description of the nature and extent of work to be performed, roles and responsibilities, addressing how management and control policies will be implemented, and how work will be scheduled, controlled, reported, and reviewed.

5. Process for the coordination and execution of all contract technical and administrative tasks, and how the contractor’s technical personnel (individuals and line managers) will interact with NASA line management.

6. Policies, procedures, practices, and techniques for electronic Task Order (TO) processing, including a discussion of the timeline and process/procedure associated with providing TO estimates (initial ROM and final BOE) to NASA once a TO request has been received from NASA.

7. Risks and mitigation strategies anticipated in successful performance of the SOW requirements. Describe the processes used to identify, monitor, and control risks associated with contract management.

8. Discussion of how the contractor will meet the intent of the personnel security requirements stated in Sections 13 and 14 of the DD FORM 254 Contract Security Classification Specification, provided in Attachment J-14.

9. Approach to development of procedures for protection of sensitive and classified information.

10. Degree of local autonomy, any relationship to a parent organization, and any decisions and approvals that will be made outside the local organization.

11. Methods of communication with other contractors as listed in Clause H.11

ASSOCIATE CONTRACTOR AGREEMENTS (ACA) FOR HHPC2

ACTIVITIES.

12. External Customer Report which provides a status on External Customer activities per DRD MGMT-08 External Customer Plan.

13. Process to ensure the Government will receive the services ordered by providing the method, level and frequency of internal surveillance, how the management policies, procedures, and techniques are monitored to ensure their effectiveness and facilitate continuous improvement, and the methods of identifying and correcting deficiencies.

14. Approach for managing the baseline work as well as IDIQ delivery orders and LOE task orders. Provide specific details of how each work element in the SOW will be integrated across the contract.

15. Technical metrics with rationale to be collected during the performance of this contract.

16. Approach to supporting NASA and affiliated organizations regarding technical and schedule information.

17. Staffing location plans, including lease arrangements, for the contractor’s off- site facilities. Discuss any other issues related to logistics management, including approach for onsite vs. telework, remote workers and required travel for critical remote workers.

Remarks: None

Maintenance: Revisions shall be incorporated by change page or complete reissue.

1. DRD Title: Work Breakdown Structure (WBS) and Dictionary

2. DRD No.: MGMT-02 3. Data Type: 1 4. OPR: OP

5. Solicitation No.: 80JSC024HHPC2 6. Contract No.: 80JSC025HHPC2

7. Date Issued: TBD 8. Date Revised: N/A 9. DRD Category:

☐ Technical ☒ Administrative

☐ S&MA

10. Description/Use: To organize the tasks to be accomplished in this contract in a service-oriented WBS that reflects the Statement of Work (SOW) and maps to the current HHPD WBS. The HHPC2 WBS and dictionary shall provide the framework for structuring the program implementation plans, establishing and tracking budgets, preparing schedules, developing work force and material estimates, preparing work authorization documents, and reporting contract performance.

11. Distribution: Distribution shall be as instructed by the Contracting Officer (CO).

Initial Submission:

• Initial – Due during Phase-In

• Final – Due at Contract start

• Approval – Contract start + 60 calendar days.

Submission Frequency: As required.

Format: Contractor format is acceptable. Electronic files shall be compatible Microsoft Office.

Interrelationship: NASA SA WBS; SOW Section 1.1 Contract Management; Attachment J-17 Work Breakdown Structure (WBS)

Applicable Documents: None

Scope: The WBS shall encompass all the services required to achieve all the requirements of this contract. The WBS shall subdivide the work to be accomplished into elements that serve as the basis for detailed planning and control, and in addition, permit collection of cost and schedule data for each element.

Contents: The WBS shall graphically depict the WBS tree that reflects the SOW. The dictionary shall contain a concise description of contract tasks to be performed and products to be delivered, subdivided by WBS element. A WBS element may represent an identifiable product, a set of data, a service, a task, or a budget function. The structure shall be at the RFP WBS level (See Attachment J-17 for mapping to the SOW) with additional levels as required by the Contractor. Lower levels of detail, which the Contractor uses for its own management purposes to validate information reported to NASA, shall be compatible with NASA requirements and be accessible by NASA. The relationship between the WBS and the Contractor's internal organizations and processes shall also be provided. The WBS shall map to the Human Health and Performance WBS.

Remarks: Contractor is expected to work with HHPD analyst to refine the WBS and ensure correct mapping to current HHPD WBS for effective financial reporting.

1. DRD Title: Contract Management Reports

2. DRD No.: MGMT-03 3. Data Type: 1 4. OPR: OP

5. Solicitation No.: 80JSC024HHPC2 6. Contract No.: 80JSC025HHPC2

7. Date Issued: TBD 8. Date Revised: N/A 9. DRD Category:

☒ Technical ☒ Administrative

☒ S&MA

10. Description/Use: Provide information on the contractor’s safety, technical, quality, financial, and deliver-to-schedule progress for use by the contract management team consisting of Human Health and Performance, S&MA and Administrative personnel.

11. Distribution: Distribution shall be as directed by the Contracting Officer (CO).

Initial Submission: End of month containing contract start date + 5 days

Submission Frequency: End of each contract month + 5 business days or otherwise synchronized with monthly contract reviews.

Format: Contract Management Reports shall be arranged as stated in the Contents section of this DRD. The Contract Management Summary Review shall be a chart presentation. Both products shall be provided in the Contractor’s format, an electronic submission compatible with MS Office.

Interrelationship: MGMT-01 Contract Management Plan DRD, MGMT-09 Continual Improvement Plan DRD, MGMT-06 Partnerships and Technology Incubation Plan DRD, BP-01 NASA Contractor Financial Management Reporting (NF 533) DRD, BP-05 New Technology Reporting Plan DRD, SMA-03 Safety and Health Plan DRD

Applicable Documents: N/A

Scope: The monthly Contract Management Reports shall contain information on the contractor's safety, technical, quality, cost, and deliver-to-schedule performance. This report, along with detailed financial reports, serves as the contractor's formal reports given to NASA for contract surveillance. The Contract Management Reports shall be delivered, and the associated Summary Review presented at the monthly Contract Management Review (SOW 1.1).

Contents: The contents of the report shall address all active contractual activities and performance. The structure of the report shall be selected by the contractor and agreed upon by the NASA COR. The following shall be addressed in the report:

1. SAFETY SUMMARY

• OSHA reportable events

• Personnel Injuries

• JSC on-site Close Calls and Status involving HHPC2 personnel

• Inspection Reports of on-site facilities dedicated to HHPC2 activities

• Flight Product Safety Related Discrepancy Reports (DR) and summary status of all remaining open DRs

2. COST PERFORMANCE SUMMARY (Performance Based) (For each TO)

• Project Actual-To-Date Cost & Projected Total Cost - Last Period

• Project Actual-To-Date Cost & Projected Total Cost - This Period

• Projected Total Cost Addition Due to Approved Changes

• Graphics Of Initial Cost Projection, Approved Changes Projection, Full Cost Projection

• Variance not due to approved changes and description of cause and a plan for recovery or how this impacts the overall yearly budget

3. RESOURCE PERFORMANCE SUMMARY

• Graphic of the initial planned manpower for each WBS item

• Current planned manpower with approved changes

• Actual manpower used to date, and % of WBS task completed

4. TECHNICAL & QUALITY PERFORMANCE SUMMARY STATUS

• Technical /Quality Performance metrics

• Quality issues (documentation, hardware, software)

• Action to be taken to resolve quality issues

• Continual improvement initiatives and status

• Other Quality Subjects as needed

5. PRODUCT PRODUCTION AND SCHEDULE SUMMARY STATUS

• Overall Schedule Status

• Completed Products and Schedule – Projected vs. Actual

• Projected Next Month’s Products and Schedule

• Change from last month due to approved changes

• Variance not due to approved change and description of cause

6. MANAGEMENT SUMMARY

• Corrective Actions Taken

• Organization

• Configuration Management

• Risk Management (Risk identification and mitigation plans)

• Any changes to OCI status

• Partnerships and Technology Incubation Plan progress report

• New Technology Summary Report

• External Customer status

Contract Management Summary Review: The summary review shall contain the highlights of the report and shall be presented at the Monthly Contract Management Review. The COR and the contractor shall agree upon the contents of the review. Minutes during the Summary Review shall be taken and submitted with the next status report.

Remarks: N/A

1. DRD Title: Staffing and Critical Skills Plan

2. DRD No.: MGMT-04 3. Data Type: 1 4. OPR: SA

5. Solicitation No.: 80JSC024HHPC2 6. Contract No.: 80JSC025HHPC2

7. Date Issued: TBD 8. Date Revised: N/A 9. DRD Category:

☐ Technical ☒ Administrative

☐ S&MA

10. Description/Use: The Staffing and Critical Skills Plan describes and documents the Contractor’s approach for meeting the staffing requirements for the entire statement of work.

11. Distribution: Distribution shall be as instructed by the Contracting Officer (CO).

Submission:

• Initial – Contents section, elements 1 through 6 below, due with proposal

• Final – Complete Plan due at start of Phase-In

• Approval – By Contract start

Submission Frequency: Update annually

Format: Contractor’s format is acceptable. The electronic format shall be compatible with Microsoft Office.

Interrelationship: SOW Section 1.7 Staffing Training, and Retention, DRD MGMT-01 Contract Management Plan

Applicable Documents: None

Scope: The Staffing and Critical Skills Plan describes the process for attracting and retaining qualified personnel to meet the required staffing levels and describes the qualifications of key personnel.

Contents: At a minimum, the Contractor shall address the following elements:

1. Staffing of the proposed organizational structure including proposed teaming partners and subcontractor personnel, including numbers and types for all contract years.

2. Sources of the proposed staff including its plans to use qualified personnel efficiently from within its own organization, other corporate divisions, new hires, incumbent personnel and other resources, with each source cited as a percentage of the total work force to be applied to this contract. Provide rationale for hiring and/or replacing incumbent personnel. The Contractor shall identify the extent of commitment and availability of personnel. The Contractor shall identify the percentage of current contract employees to be retained at the contract level.

3. Plans for staffing flexibility to accommodate changes in requirements, fluctuation in workload including how staffing will be efficiently managed for newly authorized IDIQ work, along with supporting logic and rationale. Provide a discussion of this proposed approach, the length of time the Contractor (or other elements of the company) has used the approach, and the successes experienced. Address specifically the plans for staffing flexibility around the decommissioning of ISS.

4. A list of critical skills—defined as those positions requiring significant formal training, certifications, extensive on the job training, or those in high demand or short supply or with a high attrition rate. Examples include Biomedical Engineer Flight Controller, Cloud Architect, Data Scientist, Epidemiologist, Flight Surgeon, Food Scientist, Health Physicist (including Space Radiation Analysis Group personnel requiring TOP SECRET//Sensitive Compartmented Information (SCI) and SECRET security clearances), Injury Biomechanist, Lighting Engineer, Research Veterinarian and Space Architect. Explain how the critical skills will be maintained. Explain how any loss of critical skills will be mitigated in a timely fashion.

5. Risks and mitigation strategies associated with staffing and critical skills.

6. A narrative that describes the basis of the overall staffing approach by department/discipline/laboratory, to recruit, staff, train, and retain a qualified workforce with the needed critical skills and certifications to assume and perform the requirements of the SOW from contract start throughout the contract period of performance. Include the role of management and supervisors in the work being performed.

7. Job descriptions and qualifications by proposed skill levels, including mapping of the Contractor’s proposed labor categories to the Government-provided SLCs. If new SLCs are proposed, the SLC descriptions should include details similar to the Government-provided SLC description.

8. Retention Plans for maintaining and retaining a qualified workforce for all positions with an emphasis on those positions that are expected to be high attrition positions throughout the course of the contract.

9. Plans for staffing the contract with an appropriate mix of experience levels for program and project support requirements that reflects a phased approach to ensuring no gaps in critical expertise levels for the entire period of performance.

10. Identification of key personnel including name, position, and job description. The Contractor shall identify the extent of commitment and availability of key personnel.

At contract start, update this DRD to include key personnel resumes. For this DRD, resume format and content are at the Contractor’s discretion.

11. Process for employee recognition and reward for exceptional performance.

1. DRD Title: Contract Phase-In Plan

2. DRD No.: MGMT-05 3. Data Type: 1 4. OPR: OP

5. Solicitation No.: 80JSC024HHPC2 6. Contract No.: 80JSC025HHPC2

7. Date Issued: TBD 8. Date Revised: N/A 9. DRD Category:

☐ Technical ☒ Administrative

☐ S&MA

10. Description/Use: Plan to describe the Contractor’s approach to phase-in of the contract, assuming responsibilities from the incumbent, and ensuring continuity of the work.

11. Distribution: Distribution shall be as instructed by the Contracting Officer (CO).

Submission:

• Initial – Due with proposal

• Final – Due 15 days after Contract award

• Approval – By start of Phase-In

Submission Frequency: N/A

Microsoft Office.

Interrelationship: Contract Management Plan DRD (MGMT-01); Staffing and Critical Skills Plan DRD (MGMT-04); Statement of Work Section 1.1 Contract Management.

Applicable Documents: None

Scope: The Phase-In Plan shall describe the Contractor’s approach for transitioning responsibilities and overall accountability from the Incumbent Contractor during the 60-day transition period and completing all Phase-In activities by contract start.

Contents: The Contractor is expected to meet full performance requirements from the start date of the base contract period. Prior to performance of services ordered by the Government under this contract, the Contractor shall accomplish all tasks required to begin work ordered under this contract. This Phase-In Plan shall describe the overall plan for transition. The plan shall contain, at a minimum, detailed rationale, schedule, and specific approach to successfully complete each item described below.

1. Schedule with key phase-in milestones and personnel responsible for completion of milestones.

2. Approach for:

a. Transitioning and processing of multiple IDIQ task orders and associated task order plans required for work to begin on day 1 of the contract start.

b. Continuous support of purchases and contracts defined in IDIQ task orders.

c. Documentation control transfer. Describe how an inventory will be performed with the

Incumbent Contractor of all records that will be transitioned. Records transition shall be completed at contract start.

d. Continuance of facilities maintenance and operations.

e. Phase-in of critical and high-risk operations and activities and mitigation strategies to minimize impact to JSC.

f. Establishing contacts and interfaces with Associate Contractor Agreements and the Government.

g. Description of tasks, if any, requiring a continuation of support from the Incumbent Contractor.

h. Uninterrupted support for ground and flight operations with emphasis on crew health and safety.

i. Implementing the plans, procedures, and processes required for performance of the contract, including property, personnel, facilities, and security. Include metrics used to determine progress for contract transition, and plan for informing NASA of milestone status, progress, and issues.

3. Identify risks associated with the phase-in and discuss risk mitigation strategy.

4. Identify any temporary onsite office space required for personnel directing phase-in.

5. Information Technology Preparation:

a. Identify all contractor-provided applications that will need to be integrated at JSC.

b. Provide evidence of successful Functional Testing of applications to be integrated at

JSC.

c. Identify any application or system connectivity needs to or from JSC.

d. Verify access to all technical data owned by NASA and managed by the incumbent contractor for this contract.

6. Property control transfer, including schedule and milestones for completing 100% inventory in the following areas. The schedule shall include notification to the organizations 30 days prior to the start of an inventory. Individuals who will be performing inventories shall be identified.

a. Store stock assets

b. Program stock assets

c. Flight and qualification hardware, software, firmware, and critical GSE as well as critical spares

d. Government Furnished Property

e. Installation Accountable Government Property

7. Security considerations, including Homeland Security Presidential Directive (HSPD)-12 contractor badging requirements. Describe approach for badging requirements and personnel security clearances (including Secret and Top Secret//Sensitive Compartmented Information (SCI) clearance, where required) to ensure employees are cleared for access to JSC and its associated facilities, as required, prior to start of the contract.

8. Approach for establishing Vendor Partner Agreement held between NASA and the incumbent as well as agreements with current commercial partners to ensure continuity of those services to commercial partners at contract start.

9. Phase-in training plan.

10. Annual issuance of approximately 28 task orders.

Remarks: None.

Maintenance: The contractor may revise the Contract Phase-In Plan at any time or upon Contracting Officer (CO) request. Revisions must be coordinated with the CO and documented.

1. DRD Title: Partnerships and Technology Incubation Plan

2. DRD No.: MGMT-06 3. Data Type: 1 4. OPR: SA

5. Solicitation No.: 80JSC024HHPC2 6. Contract No.: 80JSC025HHPC2

7. Date Issued: TBD 8. Date Revised: N/A 9. DRD Category:

☐ Technical ☒ Administrative

☐ S&MA

10. Description/Use: Contractor to develop a plan to assist Human Health and Performance Directorate (HHPD) to (1) promote and facilitate HH&P partnerships and collaborations with the aerospace industry, academia, federal agencies, and other institutions and entities and (2) identify, develop, and incubate, either onsite or offsite, in house and/or with key partners, new technologies that show promise to fill knowledge/technology gaps and address human system risks for space exploration.

11. Distribution: Distribution shall be as instructed by the Contracting Officer (CO).

Initial Submission: Due during Phase-In

Submission Frequency: Annual update required

Format: Contractor format, electronic file compatible with MS Office.

Interrelationship: Contract Management Plan DRD (MGMT-01); Contract Management Reports (DRD MGMT-03); External Customer Plan DRD (MGMT-08).

Applicable Documents: NPD 1050.7, Authority to Enter into Partnership Agreements; JPR

1050.1 Procedures for Partnership Agreements; Clause H.23 NON-GOVERNMENT USE OF

EQUIPMENT AND FACILITIES

Scope: NASA-JSC works with universities, hospitals and businesses in Texas, throughout the US and partner nations to innovate, develop and bring solutions to address key knowledge and technology gaps associated with JSC mission objectives. The contractor provides key support for those initiatives within HH&P. The contractor supports the infusion of promising technologies and innovations developed/incubated in-house or via partnerships into HH&P products, processes and operations, particularly as they promote human exploration of space.

Contents: This plan shall include the following aspects:

(1) Strategy to facilitate collaborations and partnerships between HH&P and industry, universities, non-profit research entities, private industry and other US Government Agencies to innovate, develop and bring solutions to address key knowledge and technology gaps associated with JSC human spaceflight mission objectives

(2) Process for identifying and assessing new technologies, innovations, best practices and process improvements and how they could be incubated or customized for HH&P

(3) Process for developing, evaluating and presenting proposals to NASA for funding

(4) Methods to demonstrate the feasibility and effectiveness of the contractor’s proposal

Metrics that NASA can use to evaluate the effectiveness of the plan.

(5) Plans to facilitate technology transfer and commercialization of space technologies.

(6) Identification of whether NASA action is required to implement specific approaches or other dependencies, and how it would be authorized.

(7) Description of any risks and mitigation strategies associated with the plan.

(8) Status information, delivered periodically as part of the Contract Management Reports

(DRD MGMT-03), shall include as a minimum:

• Status of partnership and technology development activity during the reporting period

• Summary of new proposals for improving HH&P products, processes and operations including rationale for each identified candidate

• Explanation of how the technology development projects fill current recognized human exploration knowledge/technology gaps or addresses known risks in the strategy

• Estimated cost savings, and other benefit to the Government, for innovations implemented during the reporting period

1. DRD Title: External Customer Plan

2. DRD No.: MGMT-08 3. Data Type: 1 4. OPR: SA

5. Solicitation No.: 80JSC024HHPC2 6. Contract No.: 80JSC025HHPC2

7. Date Issued: TBD 8. Date Revised: N/A 9. DRD Category:

☐ Technical ☒ Administrative

☐ S&MA

10. Description/Use: Contractor plan for marketing the excess capacity HHPD may have in certain onsite laboratories and facilities to external US customers to retain skills within these facilities and off-set costs.

11. Distribution: Distribution shall be as instructed by the Contracting Officer (CO).

Initial Submission: 30 days prior to contract start

Submission Frequency: Annual update required

Format: Contractor’s format is acceptable. Electronic file shall be compatible with MS Office.

Interrelationship: Contract Management Plan and Reports DRD MGMT-01; Contract Management Reports DRD MGMT-03; Partnerships and Technology Incubation Plan DRD MGMT-06; SOW Section 1.14; Clause H.23 NON-GOVERNMENT USE OF EQUIPMENT

AND FACILITIES.

Applicable Documents: NPD 1050.7, Authority to Enter into Partnership Agreements; JPR

1050.1 Procedures for Partnership Agreements

Scope: The External Customer Plan (ECP) describes the Contractor's multi-year approach for identifying, marketing, and retaining external customers for HHPD. The intent of the plan is to allow the contractor to market and use HHPD Directorate facilities and capabilities on a non-interference basis, for the purposes of maintaining, and upgrading critical skills, and off setting the Government's cost of maintaining such capabilities. Ideally, the excess capacity projects support NASA’s human spaceflight research goals. The ECP will be negotiated, and agreed upon by the contractor and NASA, prior to approval. Upon approval, the ECP will become a part of the contract as Attachment J-13. After the finalized ECP is approved by NASA, the Contractor shall enter into a formal agreement with NASA that establishes the terms and conditions for use of Government property. A report, referred to as the ECP status report, shall be provided as part of the Monthly Contract Management Report (DRD MGMT- 03). The report shall contain a running list of contacts being sought through the ECP process.

Contents: The plan shall describe the Contractor's approach for retaining skills and offsetting the government's cost of maintaining facilities by marketing and supporting External Customers. The plan shall outline cost avoidance targets that the contractor shall be evaluated against. Cost avoidance is defined as the estimated funds that would have been spent by the Government for the maintenance of facilities, equipment, and capabilities had it not been paid for by the external customers. Also, it includes any funds for facility usage that are provided to the Government.

1. DRD Title: Continual Improvement Plan

2. DRD No.: MGMT-09 3. Data Type: 1 4. OPR: OP

5. Solicitation No.: 80JSC024HHPC2 6. Contract No.: 80JSC025HHPC2

7. Date Issued: TBD 8. Date Revised: N/A 9. DRD Category:

☐ Technical ☒ Administrative

☐ S&MA

10. Description/Use: To provide a comprehensive plan for improving contract performance with the goals of working more safely, enhancing quality, and maximizing customer value and satisfaction.

11. Distribution: Distribution shall be as instructed by the Contracting Officer (CO).

Submission:

• Initial: Due with proposal

• Final: Contract award + 30 calendar days

• Approval: Receipt of Final Plan + 30 calendar days

Submission Frequency: Annually, 60 days prior to the start of every contract year if changes are proposed.

Format: Contractor’s format is acceptable. The electronic file shall be compatible with Microsoft Office.

Interrelationship: DRD MGMT-01 Contract Management Plan; DRD MGMT-03 Contract Management Reports; SOW Section 1.0 Contract Management and Administration

Applicable Documents: None

Scope: The Contractor shall collaborate with NASA on strategic, innovative, and cost-effective solutions for current and future contract operations that align with the NASA and Human Health and Performance (HH&P) vision as it relates to the SOW. This includes developing forward-thinking and adaptable solutions that enable HH&P to be responsive to new NASA programs, missions, requirements, providers, and partnerships. The Continual Improvement Plan supports this effort and describes the Contractor’s multi-year approach for identifying, formulating, and tracking proposed improvements (both approved and disapproved for implementation) that will provide safe, secure, effective, and cost-efficient support in the implementation of HH&P requirements within the SOW while eliminating waste, driving efficiency, and maximizing customer value.

Contents:

1. The Contractor shall define and institute processes (upon approval by the Government) to improve cost effectiveness and efficiency in management, administration, development, modification, sustaining, maintenance, reconfiguration, operations, and other activities required in performance of this contract to increase resources capacity without compromising the health, safety, and performance of astronaut crews, JSC employees, and employees at other NASA Centers supported by this contract. The Contractor shall identify, track, and status actual results of process improvements approved for implementation. The Contractor shall also be able to accommodate Government feedback into the process.

2. For each management or technical improvement proposed through the process, the Contractor shall, as a minimum, describe technical/management approach, risk identification, risk reduction, schedule, investment cost by fiscal year for each WBS element (for each labor and non-labor category), and proposed savings for each WBS element. There shall be enough detail for the Government to adequately assess the practicality and payback for each suggested improvement.

Remarks: None.

1. DRD Title: Organizational Conflicts of Interest (OCI) Plan

2. DRD No.: MGMT-10 3. Data Type: 1 4.OPR: OP

5. Solicitation No.: 80JSC024HHPC2 6. Contract No.: 80JSC025HHPC2

7. Date Issued: TBD 8. Date Revised: N/A 9. DRD Category:

☐ Technical ☒ Administrative

☐ S&MA

10. Description/Use: The OCI Plan communicates the contractor’s approach to identify and mitigate OCIs. The contractor will be held accountable for identifying, dispositioning, and reporting OCIs during contract performance.

11. Distribution: Distribution shall be as instructed by the Contracting Officer (CO).

Initial Submission: Plan shall be submitted with the proposal.

Submission Frequency: Annual review may require updates.

Format: Contractor’s format is acceptable. Electronic file shall be compatible with Microsoft Office.

Interrelationship: NFS 1852.209-71, Limitation of Future Contracting, NFS 1852.237-72, Access to Sensitive Information, NFS 1852.237-73, Release of Sensitive Information; SOW Section 1.0 Contract Management; Clause H.12 Mitigation of Organizational Conflicts of Interest; Clause H.13 Disclosure of Organizational Conflicts of Interest after Contract Award.

Applicable Documents: FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest, NFS 1809.500, NASA Guide on Organizational Conflicts of Interest.

Scope: The OCI Plan describes the contractor’s comprehensive approach to identify, avoid, mitigate, neutralize, and report potential OCI issues, including conflicts described in the solicitation and those discovered during contract performance.

Contents: The OCI Plan shall meet the requirements of FAR 9.5 and include the following:

1. Point of contact for OCI issues and reports.

2. Demonstrate an understanding of (1) OCI principles and (2) the full breadth of OCI issues and the types of harm that can result. The Plan at a minimum addresses the three primary types of OCIs (i.e., biased ground rules, unequal access to information, and impaired objectivity).

3. Define company roles, responsibilities, and procedures for (1) screening (i.e., identifying/recognizing, analyzing/evaluating, resolving, and reporting) existing and new business opportunities for actual/potential OCIs and (2) monitoring and reporting all potential/actual OCIs that arise, resolving conflicts, and reporting previously unidentified OCIs or potential OCIs to the Government.

4. Describe how employees are notified of the Plan’s requirements and how this notification will be documented. Establish and require entrance training for new employees, refresher training for existing employees, and exit training for departing employees. Describe how completion of this training will be documented, including a copy of any training certification template that the contractor will use to document that its employees have completed training.

5. Describe how the contractor will report breaches of the protective measures in the Plan to the contracting officer. Describe what processes the contractor will implement following any breach and indicate that final resolution of the corrective action must be approved by the contracting officer.

6. Identify any affiliated companies/entities (e.g., a parent company or a wholly owned subsidiary) and procedures for coordinating OCIs with such affiliated companies/entities.

7. Address the process for reporting all potential/actual OCIs that arise during performance of the contract. An OCI report shall include (1) a description of the conflict, (2) the plan for resolving the conflict, and (3) the benefits/risks to contract performance associated with plan approval/acceptance. Specific resolution strategies shall be appended to the Plan upon approval by the Government.

8. Explain how the contractor will flow down the provisions of this Plan to any subcontractor that may have a conflict with regard to performing the requirements of this contract. Discuss affected subcontractors’ OCI program as it relates to this contract and specifically explain how affected subcontractors will identify, resolve, and report actual/potential OCIs associated with this contract.

9. Define organizational and employee sanctions for violations of established OCI procedures/requirements/guidelines.

10. Include an assertion from the Offeror that to the best of its knowledge no OCIs exist currently, if applicable. Provide a list of all the prime’s and proposed subcontractor(s)’s NASA contracts and subcontracts currently being performed and contracts performed within the last five years of the release of this solicitation, in order to provide the CO a better understanding of other NASA work performed by the Offeror that may give rise to an actual or potential conflict. For each prime contract and subcontract listed, the Offeror shall: (1) identify the contract number; (2) describe the scope of work in sufficient detail to ascertain the likelihood of a conflict with performance of this contract; and (3) discuss any conflicts that may arise from performance of the listed contracts and award of this contract.

11. The Offeror shall also list any non-NASA Federal contracts and subcontracts that it or its proposed subcontractors are currently performing or have performed in the five years preceding the release of the solicitation that may give rise to an OCI. For each and subcontract listed, the Offeror shall: (1) identify the contract by number and name; (2) identify the name, address and contact information of the customer(s); (3) describe the scope of work in sufficient detail to ascertain the likelihood of a conflict with performance of this contract; and (4) discuss any conflicts that may arise from performance of the listed contracts and award of this contract.

12. For financial or other interests or relationships beyond Federal contracts or subcontracts that may give rise to an OCI, the Offeror shall (1) address the nature and extent of the interest(s) or relationship(s); (2) list any entity or entities involved in the interest(s) or relationship(s) and award of this contract.

13. The Offeror shall address how it will avoid, neutralize, or mitigate each potential OCI listed above. Sufficient information must be provided to allow a meaningful evaluation of the potential effect of the interest on the performance of the statement of work.

14. Include a requirement to update this plan as necessary to address specific OCIs. All updates to the plan must be approved by the contracting officer and the updates/changes must be incorporated in the contract to be effective.

15. Require periodic self-audits to ensure compliance with established OCI procedures/requirements/guidelines.

16. Define records related to the OCI Plan (e.g., training and audit records) that will be made available to the Government upon request. Note: The OCI Plan as outlined in paragraphs 1 through 12 above is not for the purpose of addressing other very important contractual obligations such as (1) the contractor’s obligation to protect sensitive information in accordance with NFS 1852.237-72, Access to Sensitive Information, (2) the contractor’s obligation to conduct business in an ethical manner in accordance with FAR 52.203-13, Contractor’s Code of Business Ethics and Conduct, and (3) the contractor’s obligation to prevent personal conflicts of interest in accordance with FAR 52.203-16, Preventing Personal Conflicts…