J.1(a) Attachment 2 Contract Data Requirements List (CDRLs).pdf

RFP 80ARC025R0001 Attachment 2 Section J.1(a)

Attachment 2 Section J.1(a)

Contract Data Requirements List (CDRL)

National Aeronautics and Space Administration Ames Research Center

DOCUMENT CHANGE LOG

DRD

No.

DRD Title Revision Date

INTRODUCTION

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

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

(OPR).

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

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.

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 preferred. 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 entry into an electronic system (e.g., Electronic Document Management System (EDMS/Repository)), 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.

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

1. Contract number

2. Data Requirements Description (DRD) number

3. DRD data type

4. Submission date or milestone being satisfied

5. Document number and revision

6. Document title

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

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

1441.1, NASA Records Retention Schedules)

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

Data Restriction Determination and Marking Requirements The contractor shall properly mark data in accordance with the data rights clause(s) included in the contract. The contractor must make a determination for each individual data deliverable, and shall not apply a default or blanket data restriction marking to all data deliverables (e.g., “data may be export restricted”). If NASA does not agree with the contractor applied data restriction, the CO shall return the data to the contractor, cancel the markings, or ignore the markings consistent with the procedures set forth in the “data rights” clause(s) contained in the contract.

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

DOCUMENT REVISIONS

Documents previously submitted to satisfy a DRD may be revised either by individual page or by a complete reissue of the document. Revisions shall require approval by the CO.

A document shall be completely reissued when, in the opinion of the CO, the document has been revised to the extent that it is unusable in its present state. When a document is completely reissued, 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.

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

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.

Contractor-Initiated Change The contractor shall notify the CO when, in its opinion, a data deliverable is required, but is not yet covered by a DRD in the contract, or when an existing DRD requires revision. Contractor-initiated change shall require approval by the CO.

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

Contract Data Requirements List

DRD

No.

Data Type

DRD Title OPR

001 3 Initial Financial Management Report (NF 533I) JAC

002 3 Monthly Financial Management Report (NF 533M) JAC

003 3 Quarterly Financial Management Report (NF 533Q) JAC

004 2 Government Property Management Plan JAC

005 N/A RESERVED N/A

006 N/A RESERVED N/A

007 3 Certificate of Insurance JAC

008 1 IT Security Management Plan JAC

009 3 IT Security Training Progress Report JAC

010 1 Subcontract Consent Package JAC

011 3 Re-Procurement Incumbent Compensation Data Package JAC

012 1 Organizational Conflicts of Interest (OCI) Plan JAC

013 3 Representation of Limited Rights Data and Restricted Computer Software JAC

014 1 Contract Phase-In Plan JAC

015 3 Monthly Work Schedule (MWS) JCM

016 3 Follow On Plan JCM

017 3 Performance Metrics Report JCM

018 3 Contract Completion Records and Reports JCM

019 2 Quality Control Plan (QCP) Annual JCM

020 3 Training, Licenses, and Certifications JCM

021 2 Joint Inventory of Government Furnished Facilities and Equipment JCM

022 N/A RESERVED -

023 3 PM Accumulative Report JCM

024 3 PM/PGM Monthly Deficiencies Report JCM

025 3 Predictive Technology and Inspection Results Monthly Report JCM

026 3 Acceptance of New Equipment Documentation JCM

027 3 FMCS Plan JCM

028 3 FMCS Weekly Alarm Report JCM

029 3 FMCS Call Tree Notification Sheet JCM

030 3 Integrated Pest Management Program and Chemical Use Monthly Report JCM

031 3 Integrated Pest Management Program Plan JCM

032 3 Engineering Documentation Procedures JCM

033 3 Pressure Systems Inspection Reports JCM

034 3 Equipment/Systems Down List JCM

035 2 Environmental, Safety and Health (ESH) Plan JCM

036 3 Annual Pollution Prevention Plan JCM

037 3 CFC and HCFC Monthly Reports JCM

038 3 Hazardous Material Inventory and Tracking Report JCM

039 3 Hazardous Waste/Substance Spill Report JCM

040 3 Remediation Activity Report JCM

041 3 Contract Task Order Status Report JCM

042 3 Pavement Assessment and Repair Plan JCM

043 3 Annual Alarm System Report JCM

044 3 Fire Extinguisher Annual Inspection Report JCM

045 3 Facility Condition Assessment Report JCM

046 3 Building Maintenance, Repair and Cost Profiles Report JCM

047 3 Energy and Water Reduction Plan JCM

048 3 Equipment Certification- Elevators JCM

049 3 Equipment Certifications- Air Compressor Tanks JCM

050 3 Oily Water Separators Report JCM

051 3 Ground Level Water Tank Calibration Report JCM

052 3 Emergency Shower/Eyewash Inspection Report JCM

053 3 Backflow Prevention Devices Inspection Report JCM

054 3 Meter Reading Monthly Report JCM

055 3 Fuels Reading Monthly Report JCM

056 -

- RESERVED

061 3 Ground Level Water Tanks Cathodic Annual Report JCM

062 3 Ground Level Water Tanks Diving Inspection JCM

063 3 Chemical Dosing and Monitoring System (PAX) JCM

064 2 Boiler Monthly Status Report JCM

065 3 Boiler and Chiller Annual Report JCM

066 2 Chemical Water Treatment Report JCM

067 2 HVAC Water Sampling Laboratory Results JCM

068 3 Steam Trap Survey Report JCM

069 3 Transformer Quarterly Report JCM

070 3 Transformer Annual Report JCM

071 3 Generators Operating Hours Monthly Report JCM

072 3 Generators Monthly Inspection Report JCM

073 3 Generators Annual Inspection Report JCM

074 3 Lifting Devices Inspections and Testing Monthly Report JCM

075 3 Lifting Devices Inspections and Testing Annual Report JCM

076 2 Lifting Devices Maintenance Procedures Plan JCM

077 2 Annual Plan and 5-Year Work Plan JCM

078 N/A RESERVED

079 3 Sustainable Acquisition Report JCM

080 3 Work Control Report JCM

081 3 Solid Waste Prevention and Recycling Goals JCM

082 3 Lessons-Learned Report JCM

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

2. DRD No.: 001 3. Data Type: 3 4. OPR: JAC

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

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: An initial financial management report shall be submitted by the Contractor and each major subcontractor on NASA Form 533Q (or computer-generated version) in accordance with the instructions on the reverse side of the forms and the NASA Procedural Requirements (NPR) 9501.2, NASA Contractor Financial Management Reporting, at URL: http://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPR&c=9501&s=2E.

11. Distribution: Electronic submission to: Contracting Officer (CO), Contracting Officer Representative (COR), Financial Management Division, Code CF, and Resources Management Office, Code CR.

Initial Submission: 30 working days after contract award.

Submission Frequency: Once.

Format: Electronic.

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: NPR 9501.2 & NFS 1852.242-73.

Scope: For core requirement, cost categories shall be reported by CLIN (Core Management).

For IDIQ requirements, cost categories shall be reported for each task order.

Contents: Reports shall be broken out by total direct labor hours (excluding subcontract);

direct labor hours (major subcontractors); direct labor costs; overhead and G&A (prime contractor); total direct labor, overhead, and G&A (major subcontractors); other direct costs (ODCs) include travel, material purchases, and subcontracts (other than major subcontractors), G&A/handling charge on ODCs; total other direct costs; award fee; total cost plus award fee.

Remarks: N/A

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

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

2. DRD No.: 002 3. Data Type: 3 4. OPR: JAC

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

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The Contractor shall deliver the NF 533M report in accordance with the instructions on the reverse side of the forms and the NASA Procedural Requirements (NPR) 9501.2E, NASA Contractor Financial Management Reporting, at URL:

http://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPR&c=9501&s=2E and as set forth below. It is used to monitor financial performance on the contract.

11. Distribution: Electronic submission to: Contracting Officer (CO), Contracting Officer

Initial Submission: No later than 10 working days following the close of the contractor’s accounting period after initial incurrence of cost.

Submission Frequency: Monthly, no later than 10 working days following the close of the contractor's monthly accounting period.

Format: Excel.

Interrelationship:

Applicable Documents: NPR 9501.2 & NFS 1852.242-73.

Scope: For core requirement, cost categories shall be reported by CLIN (Core Management).

For IDIQ requirements, cost categories shall be reported for each task order.

Contents: Reports shall be broken out by total direct labor hours (excluding subcontract);

direct labor hours (major subcontractors); direct labor costs; overhead and G&A (prime contractor); total direct labor, overhead, and G&A (major subcontractors); other direct costs (ODCs) include travel, material purchases, and subcontracts (other than major subcontractors), G&A/handling charge on ODCs; total other direct costs; award fee; total cost plus award fee. Variances exceeding 5 percent between planned dollars and actual dollars for each reporting category (at the total contract level only) shall be explained.

Remarks: N/A.

Maintenance: Changes shall be incorporated by complete reissue.

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

2. DRD No.: 003 3. Data Type: 3 4. OPR: JAC

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

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The Contractor shall submit the NF 533Q being projected in accordance with the instructions on the reverse side of the forms and the NASA Procedural Requirements (NPR) 9501.2E, NASA Contractor Financial Management Reporting, accessible from http://nodis3.gsfc.nasa.gov/ and as set forth below. It is used to monitor financial performance on the contract.

11. Distribution: Electronic submission to: Contracting Officer (CO), Contracting Officer

Initial Submission: No later than the 15th day of the month preceding the Government Fiscal quarter being projected.

Submission Frequency: Quarterly, no later than the 15th day of the month preceding the Government Fiscal quarter being reported.

Format: NASA Form 533M

Interrelationship: NFS 1852.242-73, NASA Contractor Financial Management Reporting

Applicable Documents: NPD 9501.1, NASA Contractor Financial Management Reporting System. NPR 9501.2, NASA Contractor Financial Management Reporting.

Scope: For core requirement, cost categories shall be reported by CLIN (Core Management) quarterly. For IDIQ requirements, cost categories shall be reported for each task order quartely. Provides quarterly accounting and breakout of Core and Task order 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: Government Property Management Plan

2. DRD No.: 004 3. Data Type: 2 4. OPR: JAC

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

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The Contractor will submit the information required by NFS Provision 1852.245-80, Government Property Management Information, with its proposal, as specified in the solicitation. The Plan will be reviewed and approved by the Contracting Officer and finalized prior to the end of the Phase-In period.

11. Distribution: Electronic submission to Contracting Officer (CO), Contracting Officer Representative (COR).

Initial Submission: With Contract Proposal

Submission Frequency: Plan shall be updated as necessary to address changes in Government Property, applicable regulation, management practices, etc., for Government Review. Updated versions shall be provided within 30 days of update.

Format: The electronic format shall be compatible with Microsoft Word or Microsoft PowerPoint file format.

Interrelationship: None

Applicable Documents:

FAR 52.245-1 Government Property FAR 52.245-9 Use and Charges NFS 1852.245 NASA/FAR Supplement and latest revisions thereto NFS 1852.245-80 Government Property Management Information NPR 4100.1 NASA Supply Support and Materials Management NPR 4200.1 NASA Equipment Management Procedural Requirements NPR 4300.1 NASA Personal Property Disposal Procedural Requirements NPR 4500.1 NASA Administration of Property in the Custody of Contractors

Scope: The Government Property Management Plan defines the contractor's methods of care, accounting, and control of Government property.

Contents: The Government Property Management Plan shall satisfy the requirements of the documents listed in above, and the contract. This plan shall consist of those procedures which constitute the contractor's property management system and shall include the following categories:

a. Property management.

1. Roles and responsibilities.

b. Property outcomes.

1. Acquisition.

2. Receiving.

(a) Identification.

3. Records.

4. Physical inventory.

5. Subcontractor control.

6. Reporting.

7. Relief of stewardship responsibilities.

(a) Disposal.

8. Utilization.

(a) Consumption.

(b) Movement.

(c) Storage.

9. Maintenance.

10. Property Closeout.

c. The Government Property Management Information Plan shall include all required content stated in NFS provision 1852.245-80, Government Property Information.

References: In accordance with the FAR as listed in the Contract, NPD 4100.1, NPR 4100.1, NPD 4200.1, NPR 4200.1, NPR 4200.2, NPD 4300.1, and NFS 1852.245-8d

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

Maintenance: Changes shall be incorporated by complete reissue. The plan shall be updated when applicable for Government review.

1. DRD Title: Certificate of Insurance Report

2. DRD No.: 007 3. Data Type: 3 4. OPR: JAC

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

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: Indicates the type and amount of insurance coverage maintained by the Contractor during the period of contract.

11. Distribution: Electronic Submission to CO & COR

Initial Submission: Initial submission to be made 45 days after the last day of Phase-in.

Updated certificates are required prior to expiration of previous certificates. Revised certificate required if coverage changes.

Submission Frequency: Annually (each year on the anniversary of delivery of the initial submission, or the first workday following the anniversary if it falls on a holiday/weekend)

Format: Electronic submission of Certificate of Insurance

Interrelationship: NASA Policy Requirement (NPR) 9501.2, NASA Contractor Financial Management Reporting; FAR 52.228-7

Applicable Documents: NASA Policy Requirement (NPR) 9501.2, NASA Contractor Financial Management Reporting

Scope: Provide the Government proof of valid and current insurance sufficient to cover the Contractor and any subcontractor’s activities on center.

Contents: The Contractor shall provide evidence of insurance via a Certificate of Insurance.

Maintenance: Changes to the DRD requirement shall be incorporated by contract modification

1. DRD Title: IT Security Management Plan

2. DRD No.: 008 3. Data Type: 1 4. OPR: JAC

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

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The IT Security Management Plan is required to safeguard IT services provided to NASA such as the management, operation, maintenance, development, and administration of hardware, software, firmware, computer systems, networks, and telecommunications systems.

11. Distribution: Electronic submission to: Contracting Officer (CO), Contractor Officer Representative (COR).

Initial Submission: 15 Days after start of Phase-In.

Submission Frequency: Reviewed annually on the anniversary of the initial delivery of the plan. If updates or changes are required anytime during performance, a revised IT Security Management Plan is due within 15 days to the COR, CO, Cybersecurity Risk Manager (CSRM), and Center Chief Information Security Officer (CISO) for review.

Format: Word document with any required records to be transferred.

Interrelationship: NFS clause 1852.204-76, Security Requirements for Unclassified Information Technology Resources.

Applicable Documents: ARC IT Security Management Plan template.

Scope: The contractor shall provide an IT Security Management Plan which will be reviewed and approved by the CO, COR, and CSRM, and the Center CISO.

Contents: The Contractor shall submit an IT Security Management Plan, describing the management and technical controls required to implement and operate an effective IT Security process for the COSMC contract. This plan shall adhere to the NASA ARC IT Security Management Plan Template and describe the processes and procedures that will be followed to ensure appropriate security of IT resources that are developed, processed, or used under this contract. The template includes an IT Security Management Statement that addresses:

• Protecting Sensitive Information.

• IT Information Types.

• Security Plan Compliance.

• Assessment and Authorization.

• Configuration Control.

• Incident Response.

• System Configuration.

• Vulnerability Mitigation.

• Security Training.

• General Rules of Behavior.

Remarks: The IT Security Management Plan will be reviewed and approved after award and incorporated into the contract.

1. DRD Title: IT Security Training Progress Report

2. DRD No.: 009 3. Data Type: 3 4. OPR: JAC

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

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The Contractor shall provide a monthly count of contractor employees who have completed the appropriate IT security training pursuant to NFS Clause 1852.204-

76. IT Security Training is mandatory for all federal employees, contractors, students and associates who use NASA Federal IT assets and information, and is available through the System for Administration, Training, and Educational Resources for NASA (SATERN) at https://satern.nasa.gov/.

11. Distribution: Electronic submission to: Contracting Officer (CO), Contractor Officer Representative (COR).

Initial Submission: 30 days after last day of Phase-In.

Submission Frequency: Due no later than 5 working days after the end of each month.

Format: Plan shall be submitted as an Excel document listing status and due dates for training for each individual.

Interrelationship: NFS 1852.204-76, Security Requirements for Unclassified Information Technology Resources.

Applicable Documents: N/A.

Scope: Provides up to date list of employee status as regards IT security training, which is critical to assuring continued access to IT resources by contractor employees.

Contents: The IT Training report shall indicate the specific IT training required; the date required by, and date of last completion for each contractor personnel performing requirements under the COSMC contract. The training report shall indicate any employee with outstanding training requirements due within 30 days. This report shall include the status for all NASA-mandated training requirements for all staff, as specified in the IT Security Management Plan.

Remarks: The report shall be provided monthly from the point of issuance of new annual training until 100 percent of Contractor and subcontractor personnel have completed training.

Thereafter, the report shall be updated no later than 5 working days after the end of each month in which new Contractor personnel are hired and require training. Center-wide progress toward 100 percent completion of this requirement will be tracked by organization and reported to center management. To ensure that Ames Research Center meets the required agency metrics, the center must be 100 percent complete in IT security training each year by the deadline of May 30. An individual’s failure to meet the training deadline will result in his or her computer system’s being disconnected from the network.

1. DRD Title: Subcontract Consent Package

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

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

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

Technical ☒ Administrative ☐

S&MA ☐

10. Description/Use: The Contractor shall submit subcontract consent package(s) in accordance with FAR 52.244-2.

11. Distribution: Electronic distribution to Contracting Officer.

Initial Submission: 10 calendar days prior to any subcontract award.

Submission Frequency: 10 calendar days prior to any subcontract award and as required by FAR 52.244-2 or as specifically requested by the Contracting Officer.

Format: Electronic.

Interrelationship:. Applicable Documents: FAR 52.244-2.

Scope: The Subcontractor Consent package is applicable to core management and each task order.

Contents: The Subcontractor Consent package shall include the following information:

• A description of the supplies or services to be subcontracted.

• Identification of the type of subcontract to be used.

• Identification of the proposed subcontractor.

• The proposed subcontract price.

• The subcontractor’s current, complete, and accurate certified cost or pricing data and Certificate of Current Cost or Pricing Data, if required by other contract provisions.

• The subcontractor’s Disclosure Statement or Certificate relating to Cost Accounting Standards when such data are required by other provisions of this contract. A negotiation memorandum reflecting o The principal elements of the subcontract price negotiations;

o The most significant considerations controlling establishment of initial or revised prices;

o The reason certified cost or pricing data were or were not required;

o The extent, if any, to which the Contractor did not rely on the subcontractor’s certified cost or pricing data in determining the price objective and in negotiating the final price;

o The extent to which it was recognized in the negotiation that the subcontractor’s certified cost or pricing data were not accurate, complete, or current; the action taken by the Contractor and the subcontractor; and the effect of any such defective data on the total price negotiated; The reasons for any significant difference between the Contractor’s price objective and the price negotiated; and o A complete explanation of the incentive fee or profit plan when incentives are used. The explanation shall identify each critical performance element, management decisions used to quantify each incentive element, reasons for the incentives, and a summary of all trade-off possibilities considered.

Remarks: N/A.

Maintenance: Changes shall be incorporated by complete reissue.

1. DRD Title: Re-Procurement Incumbent Compensation Data Package

2. DRD No.: 011 3. Data Type: 3 4. OPR: JCM

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

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: Provides NASA with information on specific items and supporting documentation related to labor resources and associated cost information, to be used for follow-on procurement activities such as independent Government cost estimate preparation. In the event of a competitive solicitation for a follow-on effort, NASA intends to publish nonproprietary historical information such as incumbent average composite direct labor rates, number of work year equivalents, and seniority levels to all interested parties in order to increase the probability of realistic pricing. By submitting this financial data, the contractor agrees to such use and publication.

11. Distribution: Electronic distribution to Contracting Officer (CO), Contracting Officer Representative

(COR).

Initial Submission: No later than 15 calendar days after last day of the phase-in period or as instructed by the CO.

Submission Frequency: Frequency shall be annually, no later than the 15th calendar day of the month following the end of contract year of performance (i.e., annually); or not later than 15 calendar days after request submitted by the CO. If deemed necessary by the CO, the contractor and all subcontractors shall submit the data package at times other than stated.

Format: Contractor’s format is acceptable.

Interrelationship: N/A

Applicable Documents: None

Scope: The Re-Procurement Incumbent Compensation Data Package provides the NASA CO with information on specific items and supporting documentation related to labor resources and associated cost information, to be used for follow-on procurement activities.

Contents:

The Re-Procurement Incumbent Compensation Data Package shall contain the following labor resource/cost information. This data is required from the prime and each subcontractor with at least # Work Year Equivalents (WYEs).

Labor Resources and Cost Information:

1. Data package shall include all direct labor supporting this contract, segregated by contract labor

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

2. DRD No.: 012 3. Data Type: 1 4. OPR: NASA Office of Procurement

5. Solicitation No.: 80ARC025R0001 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: Electronic Submission shall be as instructed by the contracting officer.

Initial Submission: Plan shall be submitted with the Contractor’s initial proposal.

Submission Frequency: Upon request from the Contracting Officer

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

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.

Applicable Documents: FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest, NFS 1809.5, Organizational and Consultant Conflicts of Interest, 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 contracts and subcontracts the prime and its subcontractors currently have with NASA. This will assist the CO in gaining 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

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

15. Require periodic self-audits to ensure compliance with established OCI

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

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

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: Representation of Limited Rights Data and Restricted Computer Software

2. DRD No.: 013 3. Data Type: 3

4. Solicitation No.: 80ARC025R0001 5. Contract No.: TBD

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

Technical ☒ Administrative ☐

S&MA ☐

9. Description/Use: Restrictions proposed by the Offeror/Contractor on the Government’s use, release, or disclosure of technical data or computer software, in accordance with ARC Provision 52.227-97 and ARC Clause 52.227-98.

10. Distribution: Email distribution to the Contracting Officer (CO)

Initial Submission: Initial submission shall be with the Offeror’s proposal in accordance with ARC Provision 52.227-97, Pre-Award Data Rights, Subcontracting, and Representation of Background Limited Rights Data/Restricted Computer Software, and ARC Clause 52.227- 98, Data Rights, Subcontracting, and Representation of Background Limited Rights Data/Restricted Computer Software.

Submission Frequency: Shall be as submitted when an update is required in accordance with ARC Clause 52.227-98.

Format: See Content Section of this DRD for Format.

Interrelationship: ARC Provision 52.227-97, Pre-Award Data Rights, Subcontracting, and Representation of Background Limited Rights Data/Restricted Computer Software, and ARC Clause 52.227-98, Data Rights, Subcontracting, and Representation of Background Limited Rights Data/Restricted Computer Software.

OPR: OGC

Applicable Documents: PWS of the Contract and/or Task Orders.

Scope: Provides proposed restrictions by the Offeror/Contractor on the Government’s use, release, or disclosure of technical data or computer software in performance of the requirements stated in the PWS of the Contract and/or Task Orders.

Contents: As required in ARC Provision 52.227-97 and ARC Clause 52.227-98, the offeror shall identify and provide the following representations regarding data it proposes for fulfilling data delivery requirements under the contract. It shall provide its proposed restrictions on the Government’s use, release, or disclosure of technical data or computer software using the format below:

Such representation is hereby clarified whereby the offeror further represents it has accurately identified, through recorded information, the stages of development and the source of funds at a lowest segregable level. Furthermore, the offeror represents it has verified such recorded information, and hereby certifies that the data identified below qualify as limited rights data or restricted computer software in accordance with their respective definitions in FAR 52.227-14(a).

The Contractor identifies and represents for itself, or the persons identified below, that the Government's rights to use, release, or disclose the following technical data or computer software should be restricted—

Technical Data* Or Computer Software** to be Furnished With Restrictions

Basis for Representation***

Represented Rights Category****

Name of Person Representing Restrictions*****

(LIST) (LIST) (LIST) (LIST)

* A representation of limited rights data is applicable to a lowest segregable level pertaining to an item, component, or process. Identify the data and lowest segregable level pertaining to each item, component, or process.

** A representation of restricted computer software is applicable to a lowest segregable level pertaining to computer software. Identify the lowest segregable level pertaining to computer software.

*** A representation of data shall be made at a lowest segregable level (i.e., broad descriptions are generally unacceptable due to indefiniteness). Generally, the development of an item, component, process, or computer software at private expense is the only basis for representing limited or restricted rights to the Government. If development was not at private expense, enter the specific reason for asserting that the Government’s rights should be so limited or restricted.

**** Enter asserted rights category (e.g., Limited Rights Data or Restricted Computer Software, as defined in FAR 52.227-14, Rights in Data – General or FAR 52.227-20, Rights in Data – SBIR Program, under this or a prior contract).

***** Corporation, individual, or other person, as appropriate.

Date

Printed Name and Title

1. DRD Title: Contract Phase-In Plan

2. DRD No.: 014 3. Data Type: 1 4. OPR: JAC

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

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The Phase-in plan shall document the approach and processes the contractor will use to perform all the activities necessary to ensure an effective and efficient transition from the current contract. At the completion of the contract phase-in period of performance, the Contractor shall be able to commence performance of all contractual requirements. NASA will use the phase-in plan to monitor contractor performance and assess viability of the Contractor’s approach to phase-in the contract.

11. Distribution: Email distribution to the Contracting Officer (CO) and Contracting Officers Representative (COR)

Initial Submission: No later than 30 calendar days after contract award.

Submission Frequency: Once only, however, subsequent submissions may be required if contractual requirements for the phase-in plan are not met or if changes are required to the plan during performance of the phase-in period of performance.

Format: Microsoft word or PDF

Interrelationship: PWS Section 4.01

Applicable Documents: Section 4 of the AFSS II PWS

Scope: The Contractor shall successfully perform all contractual requirements stated in the phase-in section of the PWS. The Contractor is responsible for managing all transition activities, hiring of personnel, obtaining personnel badges and clearances, training of personnel, subcontract management, scheduling contractual requirements to be performed, and delivery of contractual data requirements during phase-in period of performance. The Phase-in plan shall document the approach and processes the contractor will use to perform all the activities necessary to ensure an effective and efficient transition from the current contract. The scope of this DRD applies to the Prime Contractor and all of its subcontractors.

Contents: The Contractor shall submit a Phase-in Plan which shall detail the proposed implementation strategies, process, and milestones it will use to perform an effective and efficient phase-in of the contract ensuring a smooth transition from the previous contractor.

The Plan shall contain, at a minimum, detailed rationale, schedule, deliverables, and specific approach to successfully complete the following:

(a) The approach that will be used to perform an effective phase-in that maintains efficient continuity of services for the 60-day period from the effective date of the contract.

Describe in detail the plan for maintaining continuous and effective operations at each of the location’s being transitioned. Describe how the offeror will work with the incumbent Contractor(s) and NASA, including resources and interfaces expected from each to ensure an effective transition and continuous service.

(b) Detailed Phase-in milestone plan that shows a complete phase-in schedule to accomplish all proposed phase-in steps/milestones. Describe approach for implementing the schedule. Identify any critical milestones that are key to successful phase-in of contract requirements

(c) Proposed personnel (by title and function) that will conduct phase-in activities, their availability during phase-in, and the reasons for including those personnel in the phase-in process.

(d) Explanation of initial staffing needed at the completion of phase-in, process that will be used to hire those personal, and any needed training of those personnel.

(e) Approach that will be used to obtain understanding of all in process work that will be transitioned and operation of any applicable NASA systems for performance of all contractual requirements.

(f) Approach for ensuring completion of badging requirements and personnel security clearances to ensure personnel are cleared to access to each location, prior to the start of contract.

(g) Approach for purchasing equipment needed by the completion of the contract to start performance of all contractual requirements.

(h) Process that will be used to award all task orders, if applicable, prior to the completion of Phase-in.

Maintenance: Provide redlined revisions to the original phase-in plan if changes to the plan are necessary during performance of the phase-in period or performance to ensure the phase-in plan is accurate.

1. DRD Title: Monthly Work Schedule (MWS)

2. DRD No.: 015 3. Data Type: 3 4. OPR: JCM

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

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

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: 30 day look-ahead schedule as part of the Contractor's overall maintenance operations program

11. Distribution: Electronic Submission and Distribution to CO, COR.

Initial Submission:. Within 45 calendar days after the last day of Phase-In.

Submission Frequency: To be submitted no later than 5 calendar days prior to the end of the month for the following month’s schedule.

Format: Microsoft Excel. Submit via email.

Interrelationship: PWS Sections 5.01.a.i and 7.03.f

Applicable Documents: Attachment 2.05.03, Section J2.

Scope: To understand statuses of all work…