CMOE II Exhibit B - DRD_Amendment_2.pdf

Exhibit B 80LARC23R0001

CENTER MAINTENANCE, OPERATIONS, AND ENGINEERING II

(CMOE II)

EXHIBIT B

CONTRACT DATA REQUIREMENTS DOCUMENT (DRD)

(Version 0)

National Aeronautics and Space Administration Langley Research Center (LaRC)

Exhibit B 80LARC23R0001

Document History Log

Revision Effective Date Description of Change

Exhibit B 80LARC23R0001

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.

OPR indicates the program office for the respective 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 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 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 period established in the DRD.

3. That 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. However, to be a satisfactory delivery, the data shall satisfy all applicable contractual requirements and be submitted on time.

Exhibit B 80LARC23R0001

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 recipients and number of copies are identified within each DRD, provided within the contract, or as directed by the Contracting Officer (CO).

Format 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 by email to the recipient identified in the individual DRD, or entry into the provided Electronic Contract Management System (ECMS), or other mechanism(s) 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.

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

Exhibit B 80LARC23R0001

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.

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.

Exhibit B 80LARC23R0001

For the purpose of classification and control, DRs are grouped into the following broad functional management categories:

CATEGORY SYMBOL DESCRIPTION

C Contracts/Management 0 SOW Section 0 - General 1 SOW Section 1 - Maintenance 2 SOW Section 2 - Operations 3 SOW Section 3 - Engineering 4 SOW Section 4 - Task Order Specific

The number representing these categories forms the prefix of the DR identification number (e.g., the first maintenance DR would be 1.1).

Contract Data Requirements List

DRD

DRD

Type

DRD Title OPR

C.1 1 Initial Baseline Financial Management Report C.2 1 Monthly Contractor Financial Management Report C.3 1 Monthly Progress Report C.4 1 Award Fee Report C.5 3 Contractor Monthly/Annual Accident/Incident Reports C.6 3 Mishap Reporting C.7 3 Notice of Violation Response C.8 1 Safety and Health Plan C.9 1 Information Technology (IT) Security Management Plan C.10 1 Annual IT Security training Requirements C.11 1 Conformable Wage Rate Agreement C.12 1 Collective Bargaining Agreement C.13 3 NASA Property in the Custody of Contractors C.14 1 Documentation for Transferring Property to the Government C.15 2 Subcontracting Reports C.16 1 Government Property Management Plan C.17 1 ISO 9001 Compliance Documents C.18 3 Employment Reports on Veterans C.19 1 Evidence of Insurance C.20 3 Interim New Technology Summary Report C.21 3 Final New Technology Summary Report C.22 3 Disclosure of New Technology C.23 3 On and Near-Site Staffing Report C.24 3 EPA-Designated Categories Annual Purchasing Report C.25 3 Bio-based Products Report C.26 3 Limitations on Subcontracting Report C.27 1 Organizational Conflicts of Interest (OCI) Avoidance Plan

Exhibit B 80LARC23R0001

C.28 3 Monthly Government Purchase Card (P-Card) Summary C.29 1 Diversity, Equity, Inclusion, and Accessibility (DEIA) Plan C.30 3 Contractor Monthly Vacancy Status Report C.31 3 Contractor Monthly IDIQ Quote Status Report C.32 1 Phase-In Plan C.33 2 Re-procurement Data Package

0.1 1 Annual Service Plan (ASP)

1.1 2 Reliability Centered Maintenance (RCM) Program Plan

1.2 2 Emergency Preparedness and Response Plan

1.3 1 Operation Procedure Plans

1.4 3 Implementation of AVEVA PI for Plant and Utility Operations

Data Management

1.5 2 LaRC Recent Failures Report

1.6 3 HAZMAT Spill Response Data

2.1 3 Business Development Report

2.2 3 Knowledge Capture Report

2.3 3 Compressor Station Report

2.3.1 3 Compressor Station and Compressed Air Distribution System Availability and Reliability Report

2.3.2 3 Compressor Station and Compressed Air Distribution System Daily Log

2.4 3 Measurement and Test Equipment (M&TE) Services Report

2.5 2 Ground Data System (GDS) Software Configuration Management

Plan

2.6 3 GDS CM Procedures Audit Report

2.7 3 GDS Sustaining Engineering Reliability Evaluation and Risk

Management Report

2.8 3 GDS Software Release Assessment Report

2.9 3 GDS IT Security Self-Assessment Report

2.10 3 Operation Reliability/Tunnel Availability

2.11 3 Facility Qualified Personnel

3.1 3 Tactical Engineering Summary Report

4.1 3 IDIQ Task Orders Report

Exhibit B 80LARC23R0001

1. DRD Title: Initial Baseline Financial Management Report

2. DRD No.: C.1 3. Data Type: 1 4. OPR: OP

5. Solicitation No.: 80LARC23R0001

6. Contract No.: TBD

7. Date Issued:

8. Date Revised: 9. DRD Category:

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The Contractor shall prepare a time-phased Baseline Financial Management Report, detailing by month how it plans to incur costs for the base period of performance utilizing the NASA Form 533M format.

11. Distribution: Contracting Officer; Contracting Officer’s Representative and Financial Management LaRC-DL-NF533@mail.nasa.gov

Initial Submission: The Contractor shall submit the initial 533M within 30 calendar days after the effective date of the contract.

Submission Frequency: After the initial submission, within 30 business days after the effective date of the option period.

Format: NASA Form 533M.

Interrelationship: The Contractor shall prepare a time-phased Baseline Financial Management Report, detailing by month how it plans to incur costs for the base period of performance utilizing the NASA Form 533Q format. The Contractor shall prepare and submit the report in accordance with instructions set forth on the reverse side of the 533M Form and NASA Procedural Requirements (NPR) 9501.2E, NASA Contractor Financial Management Reporting.

Applicable Documents: The 533M Form and NASA Procedural Requirements (NPR) 9501.2E, NASA Contractor Financial Management Reporting

Scope: The Contractor shall submit a Baseline Financial Management Report for each option period within 30 working days after the effective date of the option period. The total estimated cost reflected in the reports must equal the contract value unless otherwise directed by the Contracting Officer (e.g., to reflect the Annual Service Plan). The Contractor shall update the report, as required, during performance of the contract for approval by the Contracting Officer. The report shall be revised each time a contract modification is executed which increases or decreases the contract estimated cost, for a reason other than an overrun. The report shall not be revised to include overrun costs.

Contents: The minimum reporting categories indicated below shall be included in column 6 of this report.

a. Direct Labor Hours

b. Direct Labor Dollars

Exhibit B 80LARC23R0001

c. Overhead(s)

d. Subcontract

e. Material

f. Travel

g. Other Direct Cost

h. G&A

i. Total Estimated Cost

j. Fee

k. Total Estimated Cost and Fee

Remarks: The data contained in the reports shall be auditable using Generally Accepted Accounting Principles.

Maintenance: The report will be updated for each option and with each contract modification.

Exhibit B 80LARC23R0001

1. DRD Title: Monthly Contractor Financial Management Report

2. DRD No.: C.2

3. Data Type: 1 4. OPR: OP

Technical ☐Administrative ☒

S&MA ☐

10. Description/Use: The contractor shall submit a Monthly Contractor Financial Management Report for monitoring costs.

11. Distribution: Contracting Officer; Contracting Officer’s Representative and Financial Management LaRC-DL-NF533@mail.nasa.gov

Initial Submission: The Contractor shall submit the initial 533M at the completion of the first month of contract.

Submission Frequency: The Contractor shall submit the report not later than the 10th business day following the close of the Contractor's accounting period being reported each month. There is not a recurring NF533Q requirement

Format: NASA Form 533M.

Interrelationship: The contractor shall submit a Monthly Contractor Financial Management Report in accordance with NFS 1852.242-73, NASA Contractor Financial Management Reporting. The Contractor shall prepare and submit the form in accordance with the instructions set forth on the reverse side of the form and NASA Procedural Requirements (NPR) 9501.2E, NASA Contractor Financial Management Reporting.

Applicable Documents: The 533M Form and NASA Procedural Requirements (NPR) 9501.2E, NASA Contractor Financial Management Reporting.

Scope:

(1) The contractor shall complete Columns 8.a and b using estimates (forecasts) for the succeeding two months.

(2) The Contractor shall ensure that estimates (forecasts) are the best projection of the actual costs to be reported in column 7.a of the subsequent month's 533M. Since NASA uses the Contractor's estimate for the current month (column 8.a of the 533M) as accrued costs in its monthly financial statements, the accuracy of these projections is critical to the integrity of NASA’s financial data.

(3) The Contractor shall report costs on the basis of the contractor’s most current data for actual rates experienced at the time the report is prepared, rather than on the basis of Defense Contract Audit Agency (DCAA) approved provisional billing or bidding rates. In addition, Exhibit B 80LARC23R0001 the Contractor shall adjust as needed for actual cost experience to reflect rates reported in its final indirect cost rate proposal submitted after the end of each of its fiscal years in accordance with paragraph (d) of FAR 52.216-7, Allowable Cost and Payment. The Contractor shall explain in the footnotes on the 533 report any adjustments made for actual rates as determined by the Contractor in its annual final indirect cost rate proposal.

(4) The Contractor shall include a narrative explanation for variances exceeding plus or minus 10 percent (+/-10%) between estimated costs shown in the prior month and actual costs shown in the current month at the contract level. (For example, the estimated costs shown for June in column 8.a in the May 533M and the actual June costs shown in column 7.a in the June 533M.)

(5) The Government will consider the Contractor’s accuracy of financial reporting when evaluating the Contractor’s performance in the Contractor Reporting Assessment Reporting System (CPARS).

Contents: The minimum reporting categories indicated below shall be included in column 6 of this report.

a. Direct Labor Hours

b. Direct Labor Dollars

c. Overhead(s)

d. Subcontract

e. Material

f. Travel

g. Other Direct Cost

h. G&A

i. Total Estimated Cost

j. Fee

Remarks: The data contained in the reports shall be auditable using Generally Accepted Accounting Principles. The Government will consider the Contractor’s accuracy of financial reporting when evaluating the Contractor’s performance in the Contractor Reporting Assessment Reporting System (CPARS).

Maintenance: None required

Exhibit B 80LARC23R0001

1. DRD Title: Monthly Progress Report

2. DRD No.: C.3 3. Data Type: 1 4. OPR: OP

☐A dministrative ☒

S&MA ☐

10. Description/Use: Monthly reports of all work accomplished during each month of contract performance. Additionally, as a minimum, this report shall include performance against contract performance measures, technical specifications, service utilization, and any items or issues that may impact performance evaluation.

11. Distribution: Contracting Officer and Contracting Officer’s Representative

Initial Submission: The Contractor shall submit the initial at the completion of the first month of contract.

Submission Frequency: Report shall be submitted monthly within 10 business days following the close of the Contractor’s accounting period being reported. A monthly report shall not be required for the period in which a final report is due.

Format: The Contractor’s format for the Monthly Progress Reports is acceptable.

Interrelationship: As applicable throughout the SOW

Applicable Documents: N/A

Scope: The Contractor shall submit monthly progress reports describing work accomplished during the reporting period, current and potential problem areas and proposed corrective action, and work to be performed during the next reporting period. The Contractor shall submit the monthly progress report within 10 working days after the end of each calendar monthly report period. A monthly report shall not be required for the period in which the final report is due. Identify the extent to which the requirement is relevant. For example, the onsite employee listing provides a listing of all contractor employees working on this contract and their designated locations at the Center.

Remarks: This document is the vehicle for the contractor to communicate to NASA senior management a monthly program status of major accomplishments, issues, plans, and risks.

Maintenance: None required.

Exhibit B 80LARC23R0001

1. DRD Title: Award Fee Report

2. DRD No.: C.4 3. Data Type: 1 4. OPR: OP

☐Administr ative ☒

S&MA ☐

10. Description/Use: The Contractor shall submit an Award Fee report that summarizes significant achievements during the Award Fee evaluation period.

11. Distribution: Contracting Officer and Contracting Officer’s Representative

Initial Submission: Within 15 business days after the close of the first evaluation period.

Submission Frequency: Within 15 business days after the close of the evaluation period.

Format: Microsoft Word.

Interrelationship: 1852.216-76, Award Fee for Service Contracts; CMOE Award Fee Evaluation Plan

Applicable Documents:

Scope: The Contractor shall submit an Award Fee report that summarizes significant achievements during the Award Fee evaluation period. The report shall include lessons learned and summarize the results of the entire contract work for that period. The Award Fee report shall include sufficient detail to comprehensively explain the results achieved under the contract and shall follow the format of and specifically address each evaluation factor contained in the Award Fee Evaluation Plan.

(NTE 25 pages).

Remarks:

Maintenance: None required.

Exhibit B 80LARC23R0001

1. DRD Title: Contractor Monthly/Annual Accident/Incident Reports

2. DRD No.: C.5 3. Data Type: 3 4. OPR: SFAB

Administrative ☒

S&MA ☒

10. Description/Use: Accident/incident data and reporting for the prime and the subcontractor.

11. Distribution: Contracting Officer; Contracting Officer’s Representative, Safety and Facility Assurance Branch (via CMAR)

Initial Submission: The Contractor shall submit the initial at the completion of the first month of contract.

Submission Frequency: Within 10 business days after the end of each month. The Contractor shall submit an annual summary of occupational injuries and illnesses to the Occupational Safety and Health Administration (OSHA) as described in 29 CFR Part 1904.32.

Format: The Contractor shall submit monthly reports via the web-based system entitled Contractor Monthly Accident Reporting (CMAR) located at https://cmar.larc.nasa.gov/login.cfm. If the Contractor is unable to submit its information electronically via CMAR, then the Contractor shall submit Langley Form 272 to SFAB to SFAB either by 1) calling 757-864-7233 for the current point of contact email address; or 2) sending it to Mail Stop 305.

Interrelationship: N/A

Applicable Documents: 29 CFR Part 1904.32

Scope: The Contractor shall submit monthly man-hours, headcount, and accident/incident data for the prime and the subcontractor(s) to the LaRC Safety and Facility Assurance Branch. The Contractor shall submit an annual summary of occupational injuries and illnesses to the Occupational Safety and Health Administration (OSHA) as described in 29 CFR Part 1904.32.

Remarks: NAMS request for LARC Contractor Monthly Accident Reporting (CMAR) will need to be submitted in iDMAX for access to the CMAR system.

Exhibit B 80LARC23R0001

1. DRD Title: Mishap Reporting

2. DRD No.: C.6 3. Data Type: 3 4. OPR: SFAB

Administrative ☒

S&MA ☒

10. Description/Use: To provide reporting of metrics, mishaps, close calls, and serious non-occupational injuries or illnesses.

11. Distribution: Contracting Officer’s Representative, Contract Specialist; Safety and Facility Assurance Branch

Initial Submission: Per incident.

Submission Frequency: The Contractor shall submit

Format: In the event of an emergency, the contractor shall call 911 on a center telephone or 757- 864-2222 from a cellular phone. The Contractor shall verbally notify Safety and Facility Assurance Branch (SFAB) (call 757-864-7233) of any NASA mishap (reference NPR 8621.1) as soon as practical, but no later than two (2) hours following occurrence. For any incident that does not result in contractor personnel injury, the Contractor shall submit a Safety Concern via NASA Langley Form 164 or through the LaRC Safety Website located at https://safety.larc.nasa.gov/index.cfm?ContentID=3 within 24 hours of occurrence.

Interrelationship: Safety and Health Plan.

Applicable Documents: NPR 8621.1 NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Record keeping

Scope: For any incident involving contractor personnel injury, the Contractor shall call the NASA Langley Research Center (LaRC) Occupational Health Clinic at 757-864-3193 [between 7:00 a.m.

and 3:30 p.m. (M-F)] to initiate the injury report within 24 business hours of occurrence if the injured employee does not seek initial treatment at the NASA LaRC Occupational Health Clinic.

Any contractor employee who receives medical treatment for a work-related injury from the LaRC Fire Department or an outside medical facility shall report to the NASA LaRC Occupational Health Clinic (Building 1216) when they return to work on Center at LaRC. The Contractor is required to investigate their own NASA mishaps and coordinate with SFAB on the submission requirements of the investigation report.

Contents: The Mishap and Safety Statistics Reports shall contain the information required by NPR 8621.1D and as specified by the Center’s Safety Office.

Exhibit B 80LARC23R0001

1. DRD Title: Notice of Violation Response

2. DRD No.: C.7 3. Data Type: 3 4. OPR: SFAB

Administrative ☒

S&MA ☒

10. Description/Use: Notice of Violation (NOV) issued for safety violations to the prime and/or its subcontractors.

11. Distribution: Contracting Officer’s Representative, Contract Specialist; Safety and Facility Assurance Branch

Initial Submission: Per incident.

Submission Frequency: The Contractor shall submit the response to the issuer of the NOV and SFAB within three business days of issuance. For safety and health mishaps, the contractor’s submission shall comply with NFS 1852.223-70 Safety and Health Measures and Mishap Reporting.

Format: The Contractor’s format is acceptable as long the submittal includes all required contents.

Interrelationship:

Applicable Documents: NFS 1852.223-70

Scope: The Contractor shall respond to any Notice of Violation (NOV) issued for safety violations to the prime and/or its subcontractors. The response shall include the cause for violation; mitigation of impact, if applicable; and planned prevention of recurrence.

Contents:

Remarks: Insert special instructions, if applicable

Exhibit B 80LARC23R0001

1. DRD Title: Safety and Health Plan

2. DRD No.: C.8 3. Data Type: 1 4. OPR: OP

Administrative ☒

S&MA ☒

10. Description/Use: Safety and Health Plan

11. Distribution: Contract Specialist; Contracting Officer’s Representative, Safety and Facility Assurance Branch

Initial Submission: With initial proposal submission.

Submission Frequency: The Contractor shall continually update the Safety and Health Plan when necessary (e.g., requirement change, safety regulation change, safety incident impact). The Contractor shall submit a revised Plan for Contracting Officer approval no later than 30 calendar days after the effect of a change or incident. (See Attachment 3, Safety and Health Plan Instructions for additional instructions).

Format: The Contractor’s format for the Safety and Health Plan is acceptable as long the submittal includes all required contents (see applicable documents).

Interrelationship:

Applicable Documents: NFS 1852.223-73 and Attachment 3 – Safety and Health Plan Instructions

Scope: The Contractor shall submit a Safety and Health Plan in accordance with NFS 1852.223-73 and Attachment 3 – Safety and Health Plan Instructions and in conjunction with the requirements outlined at 1852.223-70 Safety and Health Measures and Mishap Reporting.

Contents:

Remarks: Per NFS 1852.223-73, the Contractor shall not commence work until a functional review of the submitted Safety and Health Plan is completed by the NASA LaRC Safety and Mission Assurance Office (SMAO) Safety and Facility Assurance Branch (SFAB), and the Safety and Health Plan is approved by the Contracting Officer.

Maintenance: Changes shall be incorporated by complete reissue.

Exhibit B 80LARC23R0001

1. DRD Title: Information Technology (IT) Security Management Plan

2. DRD No.: C.9 3. Data Type: 1 4. OPR: OP

7. Date Issued: 8. Date Revised: 9. DRD Category:

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: IT Security Management Plan In accordance with NFS 1852.204-76, Security Requirements for Unclassified Information Technology Resources

11. Distribution: Contract Specialist; Contracting Officer’s Representative; Center Information Technology Security Manager (CITSM) larc-dl-ciso-review@mail.nasa.gov.

Initial Submission: Within 30 calendar days of contract effective date.

Submission Frequency: The IT Security Management Plan will be updated as required to address changes in the Federal Law or other NASA regulations.

Format: Contractor’s format is acceptable if all requirement in the applicable documents is addressed.

Applicable Documents: Specific guidance for contracts can be found in the following documents.

These documents can be located at: https://www.nasa.gov/content/cybersecurity-policies or https://csrc.nist.gov/publications/PubsSPs.html

1. Federal Information Security Management Act (FISMA)

2. NPD 1600.2E, NASA Security Policy

3. NPD 2810.1F, NASA Information Security Policy

4. NPR 1600.1A, NASA Security Program Procedural Requirements

5. NPR 1620.2B, Facility Security Level Determinations

6. NPR 2810.1F, Security of Information and Information Systems

7. NIST Special Publication (SP) 800-18 Rev 1, Guide for Developing Security Plans for

Federal Information Systems

8. NIST SP 800-34, Contingency Planning Guide for Information Technology Systems

9. NIST SP 800-35, Guide to Information Technology Security Services

10. NIST SP 800-37, Guide for the Security Authorization of Federal Information Systems

11. NIST SP 800-42, Guideline on Network Security Testing

12. NIST SP 800-53, Recommended Security Controls for Federal Information Systems

13. NIST SP 800-53A, Techniques and Procedures for Verifying the Effectiveness of Security

Controls in Federal Information Systems

14. NIST SP 800-60 Vol 1, Guide for Mapping Types of Information and Information

Systems to Security Categories

15. NIST SP 800-60 Vol 2, Guide for Mapping Types of Information and Information

Systems to Security Categories

Exhibit B 80LARC23R0001

16. NIST SP 800-61, Computer Security Incident Handling Guide

17. NIST SP 800-115, Technical Guide to Information Security Testing and Assessment

18. NIST SP 800-160 Vol 1, Systems Security Engineering: Considerations for a

Multidisciplinary Approach in the Engineering of Trustworthy Secure Systems

19. NIST SP 800-160 Vol 2, Developing Cyber-Resilient Systems: A Systems Security

Engineering Approach

Scope/Contents: The Contractor’s submit a IT Security Management Plan In accordance with NFS 1852.204-76, Security Requirements for Unclassified Information Technology Resources, for review and approval by the Center Information Security Officer (CISO). The approved plan will be incorporated into the contract as a compliance document. The plan shall:

1. Identify how the requirements for IT security (including developing and maintaining IT system security plans, contingency plans, and performing information system security assessment).

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

3. Describe how the Contractor intends to hold its employees and subcontractors accountable for meeting all the requirements relative to the NPR 2810.1, NASA interim IT requirements (NITRs), IT Security Handbooks, and CIO directives. The documents can be found at:

https://www.nasa.gov/content/cybersecurity-policies

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

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

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

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

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

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

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

Exhibit B 80LARC23R0001

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

Maintenance: The Contractor shall maintain the IT Security Management Plan throughout the term of the contract. Changes shall be incorporated by change page or complete reissue.

Exhibit B 80LARC23R0001

1. DRD Title: Annual IT Security Training Requirements

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: Requirements for all Contractor and subcontractor personnel requiring physical or logical access to NASA IT resources to complete NASA’s annual on-line IT Security Awareness training.

11. Distribution: Contract Specialist; Contracting Officer’s Representative; Center Information Technology Security Manager (CITSM)

Initial Submission: Annually

Submission Frequency: Annually – no later than July 10th of each year

Format: Contractor’s format is acceptable if all requirement in the applicable documents is addressed.

Interrelationship:

Applicable Documents: NFS 1852.204-76

Scope: In accordance with NFS 1852.204-76, Security Requirements for Unclassified Information Technology Resources, all Contractor personnel requiring physical or logical access to NASA IT resources must complete NASA’s annual on-line IT Security Awareness training no later than June 30th of each year.

Contents:

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

Exhibit B 80LARC23R0001

1. DRD Title: Conformable Wage Rate Agreement

2. DRD No.: C.11 3. Data Type: 1 4. OPR: OP

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: Conformable Wage Rate Agreement

11. Distribution: Contracting Officer; Contracting Officer’s Representative.

Initial Submission: The Contractor shall submit this report within 15 working days after the award date of the contract

Submission Frequency: No later than 30 calendar days after a change.

Format: Contractor’s format is acceptable if all requirement in the applicable documents is addressed.

Interrelationship:

Applicable Documents: FAR 52.222-41

Scope: For individuals employed by the Contractor who are covered by the Service Contract Act, but are not listed in Exhibit (E1, E2, F1, & F2), Register of Wage Determinations and Fringe Benefits (WD), the Contractor shall submit a report that verifies their conformable wage rate agreement as addressed in FAR 52.222-41, Service Contract Labor Standards.

Contents:

Exhibit B 80LARC23R0001

1. DRD Title: Collective Bargaining Agreements

2. DRD No.: C.12 3. Data Type: 1 4. OPR: OP

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: IT Security Management Plan In accordance with NFS 1852.204-76, Security Requirements for Unclassified Information Technology Resources

11. Distribution: Contracting Officer; Contracting Officer’s Representative.

Initial Submission: Within 15 business days after the effective date of the base period contract

Submission Frequency: No later than 30 calendar days after a change

Format: Contractor’s format is acceptable if all requirement in the applicable documents is addressed.

Interrelationship:

Applicable Documents: FAR 52.222-41

Scope: The Contractor shall submit Collective Bargaining Agreements to the Contracting Officer in accordance with FAR 52.222-41, Service Contract Act, as Amended.

Contents:

Exhibit B 80LARC23R0001

1. DRD Title: NASA Property in the Custody of Contractors

2. DRD No.: C.13 3. Data Type: 3 4. OPR: OP

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The Contractor shall submit annually a NASA Form (NF) 1018, NASA Property in the Custody of Contractors, in accordance with NFS 1852.245-73, Financial Reporting of NASA Property in the Custody of Contractors.

11. Distribution: Contracting Officer; Financial Management; Industrial Property Offices; Others according to instructions on form

Initial Submission: Annually

Submission Frequency: The Contractor shall submit the NASA Form (NF) 1018 no later than October 31st of each year for the period October 1 through September 30 of the following year. A final report shall be submitted within 30 calendar days after disposition of all property when contract performance is complete

Format: The Contractor’s format for the Government Property plan is acceptable as long the submittal includes all required contents (see applicable documents).

Interrelationship:

Applicable Documents: NASA Form (NF) 1018 and NFS 1845.71

Scope: The Contractor shall comply with the instructions on the Form and NFS 1845.71 and any supplemental instructions for the current reporting period issued by NASA.

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

Contents:

Maintenance:

Exhibit B 80LARC23R0001

1. DRD Title: Documentation for Transferring Property to the Government

2. DRD No.: C.14 3. Data Type: 1 4. OPR: OP

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: In accordance with the NFS 1852.245-71, Installation-Accountable Government Property, documentation required to transfer property initially acquired for the Government under this contract to the Government.

11. Distribution: Contracting Officer; Industrial Property Offices; Others according to instructions on form

Initial Submission: Within 90 days of contract effective date.

Submission Frequency: For purchases of supplies and materials, this document shall be submitted within 30 calendar days after the end of each calendar-year quarter (that is, not later than January 30, April 30, July 30, and October 30).

Format: See scope

Interrelationship:

Applicable Documents: NFS 1852.245-71 and Requisition and Invoice/Shipping Document, DD Form 1149, Scope: The transfer of accountability shall be initiated by the Contractor submitting a Requisition and Invoice/Shipping Document, DD Form 1149, accompanied by a copy of the Contractor's applicable purchasing and receipt document for the property. The Contractor shall insert both the Contractor's Subcontract/ Purchase Order number and the Government contract number on the DD Form 1149 under the Federal Stock Number, Description, and Coding of Material and/or Services block. For purchases of supplies and materials, this document shall be submitted within 30 calendar days after the end of each calendar-year quarter (that is, not later than January 30, April 30, July 30, and October 30). For equipment purchases, the DD 1149 shall be submitted within five working days after acceptance of each item of equipment by the Contractor. Receipt by the Contractor of a copy of the DD Form 1149 signed by the Government relieves the Contractor of accountability for the property specified on that form.

Contents:

Exhibit B 80LARC23R0001

1. DRD Title: Subcontracting Reports

2. DRD No.: C.15 3. Data Type: 1 4. OPR: OP

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: In accordance with FAR 52.219-9, Small Business Subcontracting Plan;

NFS1852.219-75, Small Business Subcontracting Reporting

11. Distribution: Contracting Office; http://www.esrs.gov/

Initial Submission: In accordance with FAR 52.219-9

Submission Frequency: In accordance with FAR 52.219-9

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

Interrelationship:

Applicable Documents: FAR 52.219-9, Small Business Subcontracting Plan; NFS 1852.219-75, Small Business Subcontracting Reporting, Scope: 1. The Contractor shall submit all subcontracting reports in accordance with FAR 52.219-9 and NFS 1852.219-75, using the Electronic Subcontract Reporting System (eSRS). Access to eSRS can be found at: http://www.esrs.gov/

2. The Contractor shall notify the Contracting Officer in writing within 5 business days of its eSRS submission.

Contents:

Exhibit B 80LARC23R0001

1. DRD Title: Government Property Management Plan (PMP)

2. DRD No.: C.16 3. Data Type: 1 4. OPR: OP

7. Date Issued: TBD 8. Date Revised: TBD 9. DRD Category:

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: To describe the method of administering and controlling Government personal property and submitting proposed property manager qualifications

11. Distribution: Contract Specialist; Contracting Officer’s Representative; LaRC Industrial Property Officer

Initial Submission: If the offeror can provide the information required in L.8(b) along with its proposal submission in this volume, then the offeror may defer submission of the GPMP until 30 days after contract award. If the offeror is unable to provide the information required in L.8(b), then the initial submission is due with the offeror’s initial proposal submission.

Submission Frequency: When updates are made to the Plan.

Format: Refer to Electronic Format instruction.

Interrelationship:

Applicable Documents: FAR 52.245-1, Government Property Clause; NASA FAR 1845 Government Property; NPR 4500.1, Administration of Property in the Custody of Award Recipients; NASA Form (NF) 1019, Property Management System Analysis (PMSA); and NF 1018, NASA Property in the Custody of Award Recipients.

Scope: The Government Property Management Plan defines the Contractor's use, maintenance, repair, protection, and preservation of Government personal property. It shall describe the Contractor's approach to receiving, handling, stocking, maintaining, protecting, and issuing Government property (equipment and material). The Plan should include interaction and Department/ Office responsibilities. The Contractor shall submit to the delegated Government Property Administrator (GPA) detailed supplemental property procedures, which are separate from the Property Management Plan, within 60 calendar days after the contract start date.

The Contractors submitting an initial Property Management Plan as part of their reply to the Request for Proposal in accordance with Contracting Officer direction, will also submit proposed property manager qualifications and experience as specified below.

Contents: This plan shall reference those policies and procedures which are part of the Contractor's Property Management System and shall include at a minimum, but not limited to, the following

Exhibit B 80LARC23R0001 functions/outcomes/activities on the NASA Form 1019 (performed by the Government Property Administrator (GPA)), and NPR 4500.1 – Table 5.1, Risk Assessment Matrix:

1. Property Management

(a) Annual property submissions on NASA Electronic Submission System (NESS) at https://ness.nasa.gov/contractor.

The outcome from submission is a pdf version of the NF 1018.

(b) Voluntary consensus standards, industry-leading practices and standards, customary commercial practices

(c) Periodic internal reviews, surveillances, self-assessments, and audits

(d) Written procedures

2. Acquisition of Property

(a) Acquisition authority

(b) Classification of property

3. Receipt of Government Property

(a) Receiving

(b) Identification

4. Records of Government Property

5. Physical Inventory

6. Subcontractor Control

(a) Flow down of property clauses to subcontractors

7. Reports

(a) Loss, Theft, Damage, Destruction reports

(b) Physical Inventory reports

(c) Audits and self-assessment reports

(d) Corrective Action reports

8. Relief of Stewardship Responsibility and Liability

(a) Loss, Theft, Damage, Destruction of property

(b) Consumed property

(c) Delivered property

(d) Contractor Inventory Disposal of property

i. In-house screening of excess

ii. Disclosure of excess

(e) Abandonment of Government property (if directed by the Government)

9. Utilizing Government Property

(a) Utilization

(b) Consumption

(c) Movement

(d) Storage

Exhibit B 80LARC23R0001

10. Maintenance

(a) Preventive maintenance

(b) Rehabilitation

(c) Calibration

11. Property Closeout

(a) Screening for further use

(b) Final physical inventory

(c) Transfers off the contract

(d) Final property submission on NESS at https://ness.nasa.gov/contractor. The outcome from submission is a pdf version of the NF 1018. All final property dispositions and reconciliation are completed prior to the final property submission.

12. Center-Unique Considerations (as they arise or known now)

Management Qualifications/Experience: The Offeror/Contractor shall specify the name and the qualifications of the proposed property manager.

1. List the Federal agencies or departments supported in managing Government property and the corresponding number of years of experience.

2. List completed personal property management training courses.

3. Specify the level of professional property management certification obtained by the proposed property manager.

4. List professional personal property management organizations in which the proposed property manager has an active current membership.

This qualification data shall be a one-time submittal from the Offerors with their initial Property Management Plan (PMP) when the plan is requested by the Contracting Officer. Insert that data as a separate tab after that PMP. This qualification data shall be excluded from the final PMP from the awarded Contractor.

Remarks: This document shall be the official contract requirements document for the control and identification of all Government property

Maintenance: Changes to the PMP shall be incorporated by change pages or complete reissue after coordination with the Government PA.

Exhibit B 80LARC23R0001

1. DRD Title: ISO 9001 Compliance Documents.

2. DRD No.: C.17 3. Data Type: 1 4. OPR: OP

7. Date Issued: TBD.

8. Date Revised: TBD 9. DRD Category:

Technical ☒ Administrative ☐

S&MA ☐

10. Description/Use: The Contractor's quality system shall be compliance to the current International Standard ISO 9001

11. Distribution: Contract Specialist; Contracting Officer’s Representative; LaRC Industrial Property Officer.

Initial Submission: At the time of proposal submission.

Submission Frequency:

The Contractor's quality system shall remain compliance to the ISO 9001 standard during the term of the contract. The Contractor shall notify the Contracting Officer within ten working days of any change in its ISO 9001 compliance status.

Format: Refer to Electronic Format instruction.

Interrelationship: LaRC 52.246-99

Applicable Documents: LaRC 52.246-99

Scope: The Contractor shall submit a copy of its Quality Plan, its Quality System Manual, as well as the specific Quality System Procedures to address the following: (a) contract and subcontract management, (b) customer requirement review and execution, (c) task management, including work order generation and processing, (d) document control, (e) handling of customer supplied product, (f) corrective, preventive and continuing improvement action systems, (g) training of employees, (h) customer satisfaction/performance measurement and (i) design control.

Contents: The Quality Plan shall describe how the Contractor will maintain or modify existing quality system documentation needed to ensure effective planning, operation, and control of processes/work activities/resources specific to accomplish the requirements of this contract. The Contractor shall describe how the integrity of the Quality Management System (QMS) is maintained when changes to the QMS are planned and implemented.

The Quality System Manual shall describe the quality management system of an organization. The quality manuals can vary in detail and format to suit the size and complexity of an individual organization.

Exhibit B 80LARC23R0001

Exhibit B 80LARC23R0001

1. DRD Title: Employment Reports on Veterans

2. DRD No.: C.18 3. Data Type: 3 4. OPR: OP

Administrative ☒

S&MA ☐

10. Description/Use: In accordance with FAR 52.222.37 the Annual VETS-4212 Report

11. Distribution: Contracting Officer

Initial Submission: Within 30 calendar days following the first VETS-4212 Report submission.

Submission Frequency: Annually, no later than September 30 of each year or Within 30 calendar days following each VETS-4212 Report submission

Format: Contractor’s format is acceptable

Interrelationship:

Applicable Documents: VETS-4212 Report; FAR 52.222.37

Scope: The Contractor shall submit a letter to the Contracting Officer confirming that it has submitted the most recent annual VETS-4212 Report required by FAR 52.222.37.

Contents:

Exhibit B 80LARC23R0001

1. DRD Title: Evidence of Insurance

2. DRD No.: C.19 3. Data Type: 1 4. OPR: OP

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: Evidence of the insurance coverage required by NFS 1852.228-75, Minimum Insurance Coverage (i.e., a Certificate of Insurance or other confirmation).

11. Distribution: Contracting Officer

Initial Submission: Prior to commencement of performance under any options exercised.

Submission Frequency: Prior to commencement of performance under any options exercised.

Format:

Interrelationship:

Applicable Documents: NFS 1852.228-75

Scope: The Contractor shall submit evidence of the insurance coverage required by NFS 1852.228-75 Minimum Insurance Coverage (i.e., a Certificate of Insurance or other confirmation) to the Contracting Officer

Contents:

Maintenance: The contractor shall notify NASA within 2 business days of any changes to insurance.

Exhibit B 80LARC23R0001

1. DRD Title: Interim New Technology Summary Report

2. DRD No.: C.20 3. Data Type: 3 4. OPR: OP

Administrative ☒

S&MA ☐

10. Description/Use: Annual list of subject New Technology required to be disclosed as set forth in NFS 1852.227-70, New Technology.

11. Distribution: Contracting Office; Contracting Officer’s Representative; Office of Chief Technologist

Initial Submission: 12 months from the effective date of the base period.

Submission Frequency: Every 12 months from the effective date of the contract base period.

Format: The Contractor shall submit the Interim New Technology Summary Report through the e- NTR New Technology Reporting System website at https://invention.nasa.gov/.

Interrelationship:

Applicable Documents: NFS 1852.245-71 and Requisition and Invoice/Shipping Document, DD Form 1149, Scope: The…