Exhibit B Contract Data Requirements List Amendment 006.pdf

B - 1

Exhibit B

CONTRACT DATA REQUIREMENTS LIST

National Aeronautics and Space Administration Langley Research Center

Exhibit B 80LARC25R7002

B - 2

DOCUMENT CHANGE LOG

DRD

No.

DRD Title Revision Date

B - 3

INTRODUCTION

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

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.

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.

B - 4

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

Hardcopy Format: Hardcopy of data deliverables is not required unless electronic delivery is not possible.

Transmittal Data shall be transmitted to NASA by email or other 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.

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.

B - 5

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.

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

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

B - 7

Contract Data Requirements List

DRD

No.

DRD

Type DRD Title OPR

1 1 Organizational Conflicts of Interest (OCI) Plan

Office of Procurement (OP)

2 1 Safety & Health Plan (S&H) Plan

OP

3 1 Information Technology (IT) Security Management Plan OP

4 3 Initial Baseline Financial Management Report (NF 533l) OP

5 3 Quarterly Financial Management Report (NF

533Q) OP

6 3 Monthly Financial Management Report

(NF 533M) OP

7 3 Contractor Monthly/Annual Accident/ Incident Reports Report SFAB

8 3 Mishap Report

SFAB

9 3 Notice of Violation (NOV) Response SFAB

10 1 Conformable Wage Rate Agreement OP

11 1 Documentation for Transferring Property to the Government OP

12 3 Employment Reports on Veterans

OP

13 1 Evidence of Insurance OP 14 3 On and Near-Site Staffing Report OP 15 3 Limitations on Subcontracting Report OP 16 3 Workmanship Standards Training and Certification Plan OP

17 1 Annual IT Security Training Requirements Report OP

18 3 Collective Bargaining Agreements OP

19 1 ISO 9001 Certification/Registration Documents (Quality Plan) OP

20 3 Interim Patent Rights Report

OP

21 3 Final Patent Rights Report OP 22 3 Invention Disclosure Reporting OP 23 3 EPA-Designated Categories Annual Purchasing Report OP

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

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

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

Technical ☐ Administrative ☒

S&MA ☐

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

11. Distribution: Contract Specialist, Contracting Officer’s Representative, and Deputy Contracting Officer’s Representative

Initial Submission: The Contractor shall submit an Organizational Conflicts of Interest (OCI) Plan within 30 calendar days of contract award date.

Submission Frequency: As needed. Supplemental OCI plans are required for each task order in accordance with the contract clause I.13 Task Ordering Procedure.

Format: Contractor’s format is acceptable

Interrelationship: NASA Federal Acquisition Regulation (FAR) Supplement (NFS) 1852.209-71, Limitation of Future Contracting, NFS 1852.237-72, Access to Sensitive Information, NFS 1852.237-73, Release of Sensitive Information and clause I.13 Task Ordering Procedure and contract provision L.20

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 Contractor that to the best of their knowledge no OCIs exist currently, if applicable. Provide a list of all the prime’s and subcontractor’s NASA contracts and subcontracts, which would provide the CO a better understanding of other NASA work performed by the Offeror that may give rise to an actual or potential conflict.

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

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

13. 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 of Interest.

14. In an appendix to the OCI Plan identify the strategy (e.g., mitigation, limitation on future contracting, etc.)

for resolving each OCI that is either identified in the solicitation or created by the requirements of the solicitation/contract and explain the effect of such strategy on performance of the contract. If using a firewall, explain how these actions will operate to successfully address the conflict without adversely affecting performance of the contract. (Note: Specific plans to limit future competition are reflected in the clause at NFS 1852.209-71, Limitation of Future Contracting.)

Remarks: N/A

Maintenance: The contractor shall review the OCI Plan on an annual basis or as directed by the contracting officer to revise the OCI Plan if necessary. Revisions are subject to Contracting Officer approval and shall be incorporated by change page or complete reissue.

1. DRD Title: Safety and Health (S&H) Plan

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

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

Technical ☐ Administrative ☒

S&MA ☒

10. Description/Use: Safety and Health Plan

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

Initial Submission: The Contractor shall submit a Safety and Health Plan within 30 calendar days of contract award date. 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) and Safety and Facility Assurance Branch (SFAB), and the Safety and Health Plan is approved by the Contracting Officer. The approved plan will be incorporated into the contract as a compliance document.

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. Subsequent revisions will be reviewed by SFAB and approved by the Contracting Officer.

Format: Contractor’s format is acceptable as long as there is a base plan that speaks to the general requirements and an appendix for each center that addresses all the center specific requirements.

Interrelationship: N/A

Applicable Documents: NFS 1852.223-73 Safety and Health Measures and Mishap Reporting and Attachment L-6, Safety and Health Plan Instructions.

Scope: N/A

Contents: Base Plan: The contractor shall submit a Safety and Health Plan in accordance with NFS 1852.223-73 Safety and Health Measures and Mishap Reporting and Attachment L-6, Safety and Health Plan Instructions.

LaRC Center Specific Requirements:

Based on center unique safety clauses, incorporate the center specific requirements e.g mishap reporting, emergency phone numbers.

Remarks: N/A

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

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

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

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

7. Date Issued: TBD 8. Date Revised: N/A 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, Deputy Contracting Officer’s Representative, Center Information Technology Security Manager (CITSM), Information System Security Officer (ISSO)

Initial Submission: The contractor shall submit the IT Security Management Plan within 30 calendar days after award of contract. The approved plan will be incorporated into the contract as a compliance document.

Submission Frequency: The IT Security Management Plan shall be updated when referenced regulations are updated to address all required regulations and submitted on an annual basis as specified in paragraph one above for review and continued approval.

Format: Contractor’s format is acceptable as long as all requirements in the applicable documents are addressed.

Interrelationship: N/A

Applicable Documents: NFS 1852.204-76. 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.2, NASA Security Policy

3. NPD 2810.1, NASA Information Security Policy

4. NPR 1600.1, NASA Security Program Procedural Requirements

5. NPR 1620.2B, Facility Security Level Determinations

6. NPR 2810.1, Security of Information and Information Systems

7. NPR 2841.1, Identity, Credential, and Access Management

8. NIST Special Publication (SP) 800-35, Guide to IT Security Services https://csrc.nist.gov/publications/sp800

LAPD 2810.1, Security of Information Technology https://lmse.larc.nasa.gov/admin/public_docs/2810-1_H- FinalVersion.pdf

Scope/Content: The Contractor and any subcontractors that process, manage, access, transmit, or store unclassified electronic information, to include Controlled Unclassified Information (CUI), for NASA in support of NASA's missions, programs, projects and/or institutional requirements shall submit an IT https://www.nasa.gov/content/cybersecurity-policies https://csrc.nist.gov/publications/PubsSPs.html https://lmse.larc.nasa.gov/admin/public_docs/2810-1_H-FinalVersion.pdf https://lmse.larc.nasa.gov/admin/public_docs/2810-1_H-FinalVersion.pdf

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 Technology Security Manager (CITSM), Information System Security Officer (ISSO), COR, D-COR and CO.

The IT Security Management 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.

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.

12. State the Categorization of the information per FIPS PUB 199. Specific information on Categorization is available at NIST SP 800-60, Volume 1 Guide for Mapping Types of Information and Information Systems to Security Categories and NIST SP 800-60, Volume 2 Guide for Mapping Types of Information and Information Systems to Security Categories:

Appendices http://csrc.nist.gov/publications/PubsSPs.html.

Remarks: N/A

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.

http://www.nasa.gov/content/cybersecurity-policies http://www.nasa.gov/content/cybersecurity-policies http://csrc.nist.gov/publications/PubsSPs.html

1. DRD Title: Initial Baseline Financial Management Report (NF 533I)

2. DRD No.: MCHFSS 004 3. Data Type: 3 4. OPR: CFO & OP

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The initial report provided by the contractor shall reflect the original Task Order (TO) value detailed by negotiated reporting categories and be the original TO baseline plan. This plan, plus authorized changes, is subsequently used in columns 7b and 7d of the NF 533 M for comparison of actual to planned cost. The NASA Contracting Officer may require additional detail, such as quarterly or semiannual phasing over the life of the TO, inclusion of unexercised options, or an initial report whenever options are exercised.

11. Distribution: Contract Specialist, Contracting Officer’s Representative, Deputy Contracting Officer’s Representative, and Financial Operations and Services Office Representative

Initial Submission: The contractor shall submit an initial financial management report in the NASA Form 533Q format in accordance with NPR 9501.2E within 30 working days after TO initiation. Initial reports shall be generated for each individual TO.

Submission Frequency: Once

Format: NASA Form 533Q computer generated version in accordance with the instructions on the reverse side of the form and NASA Procedural Requirements (NPR) 9501.2E. Reporting categories will be specified by the CO at time of award of each individual TO.

Interrelationship: NFS 1852.242-73 NASA Contractor Financial Management Reporting

Applicable Documents: NPD 9501.1I, NASA Contractor Financial Management Reporting System; NPR 9501.2E, NASA Contractor Financial Management Reporting

Scope: Provides accounting and break out of actual and planned costs for initial TO(s)

Contents: Reporting categories shall be elements of cost including direct labor hours (excluding subcontract); direct labor hours (major subcontractors); direct labor costs (separated by prime and major subcontractor); overhead; other direct costs (ODCs), G&A; total costs; incentive fee and award fee; total cost plus fee. Overtime is to be reported separately for each of the above categories. ODCs include travel, material purchases, and subcontracts (other than major subcontractors). All of the above data is to be submitted for the base period.

1. DRD Title: Quarterly Financial Management Report (NF 533Q)

2. DRD No.: MCHFSS 005 3. Data Type: 3 4. OPR: OP

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The NF 533Q is a report which provides quarterly time-phased cost and labor hour estimates.

**NOTE- NF 533Q reporting may be waived by the NASA Contracting Officer, with concurrence by the Center Chief Financial Officer and cognizant Project Manager, when NF 533 M reports and other data are sufficient to ensure accurate monthly cost accruals, track the contractors' actual cost against plans, and forecast resource requirements. Waivers will be determined at the TO level.

11. Distribution: Contract Specialist, Contracting Officer’s Representative, Deputy Contracting Officer’s Representative, and Financial Operations and Services Office Representative

Initial Submission: End of first quarter of TO performance.

Submission Frequency: Quarterly- not later than the 15th day of the month preceding the quarter being projected.

Format: NASA Form 533Q computer generated version in accordance with the instructions on the reverse side of the form and NASA Procedural Requirements (NPR) 9501.2E. Reporting categories will be specified by the CO at time of award of each individual TO and may require further breakout by organization or subtask (project).

Interrelationship: NFS 1852.242-73 NASA Contractor Financial Management Reporting

Applicable Documents: NPD 9501.1I, NASA Contractor Financial Management Reporting System; NPR 9501.2E, NASA Contractor Financial Management Reporting

Scope: Provides quarterly accounting and breakout of TO and project costs.

Contents: Reporting categories shall be elements of cost including direct labor hours (excluding subcontract); direct labor hours (major subcontractors); direct labor costs (separated by prime and major subcontractor); overhead; other direct costs (ODCs), G&A; total costs; incentive fee and award fee; total cost-plus fee. Overtime is to be reported separately for each of the above categories. ODCs include travel, material purchases, and subcontracts (other than major subcontractors). All of the above data is to be submitted for the reporting period, the cumulative periods, the Government Fiscal Year cumulative, and the estimated costs to completion and at the contract level and division, branch, project, or category (e.g. maintenance, operations, facility) level. Formats will be agreed upon between the Contractor, COR, and Contracting Officer.

Remarks: Variances more than +/- 5 percent between planned dollars and actual dollars for each reporting category (at the total contract level only and at the TO level only) shall be explained. (Reasonable variance explanation includes the issue, monthly and/or total impacts, corrective actions and dates.).

1. DRD Title: Monthly Financial Management Report (NF 533M)

2. DRD No.: MCHFSS 006 3. Data Type: 3 4. OPR: OP

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The NF 533Q is a report which provides quarterly time-phased cost and labor hour estimates.

**NOTE- NF 533Q reporting may be waived by the NASA Contracting Officer, with concurrence by the Center Chief Financial Officer and cognizant Project Manager, when NF 533 M reports and other data are sufficient to ensure accurate monthly cost accruals, track the contractors' actual cost against plans, and forecast resource requirements. Waivers will be determined at the TO level.

11. Distribution: Contract Specialist, Contracting Officer’s Representative, Deputy Contracting Officer’s Representative, and Financial Operations and Services Office Representative

Initial Submission: End of first quarter of TO performance.

Submission Frequency: Quarterly- not later than the 15th day of the month preceding the quarter being projected.

Format: NASA Form 533Q computer generated version in accordance with the instructions on the reverse side of the form and NASA Procedural Requirements (NPR) 9501.2E. Reporting categories will be specified by the CO at time of award of each individual TO and may require further breakout by organization or subtask (project).

Interrelationship: NFS 1852.242-73 NASA Contractor Financial Management Reporting

Applicable Documents: NPD 9501.1I, NASA Contractor Financial Management Reporting System; NPR 9501.2E, NASA Contractor Financial Management Reporting

Scope: Provides quarterly accounting and breakout of TO and project costs.

Contents: Reporting categories shall be elements of cost including direct labor hours (excluding subcontract); direct labor hours (major subcontractors); direct labor costs (separated by prime and major subcontractor); overhead; other direct costs (ODCs), G&A; total costs; incentive fee and award fee; total cost-plus fee. Overtime is to be reported separately for each of the above categories. ODCs include travel, material purchases, and subcontracts (other than major subcontractors). All of the above data is to be submitted for the reporting period, the cumulative periods, the Government Fiscal Year cumulative, and the estimated costs to completion and at the contract level and division, branch, project, or category (e.g. maintenance, operations, facility) level. Formats will be agreed upon between the Contractor, COR, and Contracting Officer.

Remarks: Variances more than +/- 5 percent between planned dollars and actual dollars for each reporting category (at the total contract level only and at the TO level only) shall be explained. (Reasonable variance explanation includes the issue, monthly and/or total impacts, corrective actions and dates.).

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

2. DRD No.: MCHFSS 007 3. Data Type: 3 4. OPR: SFAB

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

Technical ☐ Administrative ☒

S&MA ☒

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

11. Distribution: Contract Specialist, Safety and Facility Assurance Branch (via NMIS)

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

Submission Frequency: Monthly report is due 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 NASA Mishap Information System (NMIS) located at https://nmis.sma.nasa.gov.

If the Contractor is unable to submit its information electronically via CMAR, then the Contractor shall submit Langley Form 272A 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, Hampton, VA 23681-2143.

Interrelationship: N/A

Applicable Documents: 29 CFR Part 1904.32

Scope/Contents: 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: A NAMS request for NASA Mishap Information System will need to be submitted in iDMAX for access to the system.

Maintenance: None required https://nmis.sma.nasa.gov/

1. DRD Title: Mishap Reporting

2. DRD No.: MCHFSS 008 3. Data Type: 3 4. OPR: SFAB

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

Technical ☐ Administrative ☒

S&MA ☒

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

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

Initial Submission: The Contractor shall verbally notify 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.

Submission Frequency: Per Incident.

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

Interrelationship: Safety and Health Plan.

Applicable Documents: Safety and Health Plan and NPR 8621.1 NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Record keeping. Contract Section H-8 GRC 52.237-91 CONTRACTORS' DUTIES AND RESPONSIBILITIES ON-SITE (DEC 2016), paragraph (c).

Scope/Contents:

In the event of an emergency, the Contractor shall call 911 on a center telephone or 757-864- 2222 from a cellular phone. 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 NASA Mishap Information System (NMIS) Hazard Reporting Website https://nmis.sma.nasa.gov/UI/QuickEntryHazard/QuickEntryHazard.aspx?q=q within 24 hours of occurrence.

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.

Remarks: N/A

Maintenance: None required.

https://nmis.sma.nasa.gov/UI/QuickEntryHazard/QuickEntryHazard.aspx?q=q

1. DRD Title: Notice of Violation (NOV) Response

2. DRD No.: MCHFSS 009 3. Data Type: 3 4. OPR: SFAB

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

Technical ☐ Administrative ☒

S&MA ☒

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

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

Initial Submission: Per incident

Submission Frequency: The Contractor shall submit the response to the to the NASA LaRC Safety and Facility Assurance Branch (SFAB) and the Contracting Officer within three working days of issuance.

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

Interrelationship: N/A

Applicable Documents: NFS 1852.223-70

Scope/Contents: 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.

Maintenance: None required.

1. DRD Title: Conformable Wage Rate Agreement

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

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: Conformable Wage Rate Agreement

11. Distribution: Contract Specialist, Contracting Officer’s Representative, Deputy- 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 as long as all requirements in the applicable documents are addressed.

Interrelationship: N/A

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 the Contract Exhibit titled 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:

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

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

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

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: Contract Specialist, 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/Content below.

Interrelationship: N/A

Applicable Documents: NFS 1852.245-71, Contract Section H.8. GRC 52.237-91 CONTRACTORS' DUTIES AND RESPONSIBILITIES ON-SITE (DEC 2016), paragraph (h), and Requisition and Invoice/Shipping Document, DD Form 1149

Scope/Contents: 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.

Maintenance: N/A

1. DRD Title: Employment Reports on Veterans

2. DRD No.: MCHFSS 012 3. Data Type: 3 4. OPR: OP

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: Annual VETS-4212 Report required by FAR 52.222.37

11. Distribution: Contract Specialist

Initial Submission: N/A

Submission Frequency: Within 30 calendar days following each VETS-4212 Report submission, the Contractor shall submit a letter to the Contract Specialist confirming that it has submitted the most recent annual VETS-4212 Report required by FAR 52.222.37.

Format: Contractor format is acceptable

Interrelationship: N/A

Applicable Documents: VETS-4212 Report, FAR 52.222.37

Scope/content: The Contractor shall submit a Veterans’ Employment Report (VETS-4212 Report) as required by Clause 52.222-37, Employment Reports on Veterans.

Maintenance: None required

1. DRD Title: Evidence of Insurance

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

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

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: Contract Specialist

Initial Submission: Prior to contract effective date.

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

Format: N/A

Interrelationship: N/A

Applicable Documents: NFS 1852.228-75

Scope/Content: 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

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

1. DRD Title: On and Near-Site Staffing Report

2. DRD No.: MCHFSS 014 3. Data Type: 3 4. OPR: OP

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: Report of On-site and near- site Work Year Equivalents (WYE's) performing work on the contract, broken down by skill category.

11. Distribution: Contract Specialist; On and Near-Site Staffing Report, larc-dl- contractorwye@mail.nasa.gov.

The subject line for the e-mail should be "Contractor WYE".

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

Submission Frequency: Subsequent updated reports are due quarterly, within the first 5 workday after the end of the quarter (e.g., on or before the 5th workday in January, April, July, and October of each year).

Format: N/A Interrelationship: N/A Applicable

Documents: N/A

Scope/Contents: The Contractor shall submit a report which includes the number of on-site and near-site Work Year Equivalents (WYE's) performing work on the contract, broken down by skill category and NASA Center.

Provide the below information for each NASA Center separately.

1. These reports shall be e-mailed to the following:

larc-dl-contractorwye@mail.nasa.gov The subject line for the e-mail should be "Contractor WYE".

2. "On-site" WYEs include the time worked by prime Contractor and subcontractor employees on this contract whose primary duty station is on-site at NASA Centers, whether such employees charge direct or indirect in the Contractor's or subcontractor's accounting systems (e.g., management and administrative staff may charge their time to an "indirect" account, but the time worked by such individuals shall still be counted in the on-site WYE).

3. "Near-site" WYEs include the time worked by prime Contractor and subcontractor employees on this contract whose primary duty station is within 50 miles of a NASA Center, whether such employees charge direct or indirect in the Contractor's or subcontractor's accounting systems. Work performed on college campuses shall not be considered "near site" WYE's.

4. The Contractor shall use the number of hours in its productive work year to compute the number of WYE's to be reported. For example, if the Contractor’s standard work-year is 1,860 productive hours (excludes leave, holidays, etc.), the quarterly WYE reported would be calculated as the total labor hours for the quarter divided by the available productive hours in the quarter (in this example 1,860 annual productive hours divided by 4 quarters yields 465 hours). Thus, if 10,000 hours were incurred on the contract during the quarter the WYE would be (10,000/465 = 21.5 WYE). The Contractor shall break out the On-site and Near-site WYE by skill category using mailto:larc-dl-contractorwye@mail.nasa.gov mailto:larc-dl-contractorwye@mail.nasa.gov mailto:larc-dl-contractorwye@mail.nasa.gov mailto:larc-dl-contractorwye@mail.nasa.gov the following categories: Scientist, engineer, technician, administrative professional, and clerical

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

1. DRD Title: Limitations on Subcontracting Report

2. DRD No.: MCHFSS 015 3. Data Type: 3 4. OPR: OP

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The purpose of this report is to obtain information necessary to evaluate contractor compliance with FAR Clause 52.219-14, Limitations on Subcontracting.

11. Distribution: Contract Specialist

Initial Submission: Within 30 calendar days of completion of first year

Submission Frequency: The Contractor shall submit the report annually within 30 calendar days after completion of each contract year period of performance (reference Clause F.2).

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

Interrelationship: N/A

Applicable Documents: FAR Clause 52.219-14, Limitations on Subcontracting.

Scope/Content: The Contractor shall submit a report to the Contracting Officer that demonstrates such compliance;

specifically the report shall contain sufficient information to demonstrate compliance with the following requirement from FAR 19.505(b)(1)(i): ” For a contract or order assigned a North American Industry Classification System (NAICS) code for services (except construction ), the concern will not pay more than 50 percent of the amount paid by the Government for contract performance to subcontractors that are not similarly situated entities.

Any work that a similarly situated entity further subcontracts will count towards the concern 's 50 percent subcontract amount that cannot be exceeded. When a contract includes both services and supplies, the 50 percent limitation shall apply only to the service portion of the contract.

1. DRD Title: Workmanship Standards Training and Certification Plan

2. DRD No.: MCHFSS 016 3. Data Type: 3 4. OPR: OP

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

Technical ☐ Administrative ☒

S&MA ☒

10. Description/Use: The purpose of this plan is to evaluate the contractor’s approach to training and certification of personnel.

11. Distribution: Contract Specialist, Contracting Officer’s Representative

Initial Submission: Within 45 days of contract effective date.

Submission Frequency: Update annually.

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

Interrelationship: N/A

Applicable Documents: N/A

Scope/Contents: The plan shall include at a minimum:

1. Description of participants involved in the training, and their roles and responsibilities.

2. List of types of training to be conducted, including traditional classroom, computer-based training, on-the-job, simulations, etc., and what criteria will be used to select a particular method.

3. Description of proposed facilities, tools, and other support equipment, as well as materials and documentation required to implement the training.

4. Description of certification process (i.e., test administration, attendance, self-test, etc.)

5. Listing of the detailed training curriculum (if other than NASA training is used).

6. Detailed discussions of the processes and activities, which will be performed to plan, develop, implement, administer, and track the training and certification requirements.

7. Describe the recertification process, if one exists.

1. DRD Title: Annual IT Security Training Requirements

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

5. Solicitation No.: 80LARC25R7002 6. Contract No.: TBD

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

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

Format: Contractor format is acceptable if all requirements in the applicable documents is addressed.

Electronic format shall be compatible with Microsoft Office.

Interrelationship: N/A

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…