5._Section_4.2_Data_Requirements_List.pdf

RFP NNJ15553635R SECTION 4.2

4.2 - 1

ATTACHMENT 4.2 – DATA REQUIREMENTS LIST (DRL)

The following pages set out the documentation requirements of this contract, starting with a DRL, which is an index to the DRDs. Each DRD prescribes the required data product content, schedule, type, and other particulars for specific data submission requirements.

Subject to the Clause 52.227-14, Rights in Data – General, this document sets forth the data requirements in each DRD and shall govern that data required for this contract. The contractor shall furnish data defined by the DRDs listed on the DRL by category of data. 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) regulation or clause, the regulation will take precedence over this document, per FAR 52.215-33. NASA-Owned/Contractor-Held records shall be managed by the Contractor in accordance with Title 36 of the Code of Federal Regulations, Chapter XII B, Records Management, and NMI 1440.6, NASA Records Management Program. The records shall be organized in accordance with the instructions in NHB 1442.1, NASA Uniform Files Index, as applicable. The contractor shall disposition records and non-records in accordance with NHB 1441.1, NASA Retention Schedules, which has been approved by NASA and the National Archives and Records Administration (NARA).

All questions on records management issues shall be directed through the Contracting Officer to the JSC Records Management Officer.

Documents included as applicable documents in the data requirements form a part of this document to the extent specified herein. References to documents other than applicable documents in the data requirements of this document may sometimes be utilized. These do not constitute a contractual obligation on the contractor. They are to be used only as a possible example or to provide related information to assist the contractor in developing a response to that particular data requirement.

Description

This document identifies and defines the requirements and data types for information and data required under this contract.

The Data Requirements Descriptions (DRDs), along with the Data Requirements List (DRL), define, by an individual Data Requirement, the information and data required for each deliverable document.

The data types are used to identify the approval and control required for each DRD. The DRL is an index of all the DRDs and includes additional requirements for each DRD and the data types, as described below.

Documentation submitted pursuant to this clause may incorporate references to other current approved documentation, provided the references are adequate and include such identification elements as title, document number, and approval date (where applicable). However, if the pertinent information is of relatively minor size, the contractor shall incorporate the information

4.2 - 2 itself, in lieu of using a reference. The contractor shall assure that any referenced information is readily available to appropriate users of the submitted document.

DATA TYPES

For the purpose of this clause, the following information/documentation types are applicable:

(1) Type1 - Written approval -- Data and changes thereto requiring written approval by the NASA office of primary responsibility (OPR) before formal release or implementation

(2) Type2 - Mandatory submittal -- Data provided to NASA for coordination, information, review, and/or management control

(3) Type3 - Submitted upon request -- Data prepared and retained under a specific contract to be made available to NASA upon request

Type 1 submissions shall be marked “TYPE 1 PRELIMINARY pending NASA approval or Type I APPROVED BY NASA, as appropriate." Additional special designations and deviations may be required on specific submissions in accordance with configuration management requirements.

Type 2 submissions shall be marked “TYPE 2 PRELIMINARY - RELEASE TARGET DATE, xx/xx/xx" or "TYPE 2 FINAL - NASA COMMENTS INCLUDED" or “TYPE 2 FINAL DOCUMENT," where NASA comments were not received.

NOTE: Documents submitted under this clause, even though directly (Type 1) or implicitly (Type 2) approved by NASA, shall not take precedence over the requirements as set out in Section 4.1, Statement of Work.

The contractor shall normally deliver a complete revised Type 1 or Type 2 data requirement with NASA comments incorporated within 45 days of receipt of comments.

Type 3 submissions shall be marked "TYPE 3 DOCUMENT - FOR INFORMATION, SURVEILLANCE, REVIEW, or MANAGEMENT CONTROL".

NUMBER OF COPIES AND DISTRIBUTION REQUIREMENTS

The contractor shall provide one copy of each DRD to the standard distribution list shown in Block 8 of the DRLs. Additional distribution shall be made as directed, in writing, by the Contracting Officer. The number of copies required will not exceed the limits set forth in Clause 1852.208-81, Restrictions on Printing and Duplicating, without prior Contracting Officer approval. Electronic Data Transmittal Forms will be used to confirm delivery of electronically resident DRD deliverables.

4.2 - 3

ELECTRONIC FORMAT

All the data requirements shall be delivered in the format as depicted in each DRD and compatible with JSC software loads.

DRDs shall be maintained electronically.

FURTHER EXPLANATION OF DRL

Contract Start is defined as October 1, 2016.

Block 3 – Frequency of Submittal/Maintenance:

Code Description Code Description Code Description AD As Directed DA Daily RD As Released AN Annually DD Deferred Delivery RT One Time and Revisions AR As Required MO Monthly SA Semi Annually BE Biannually OT One Time TY Three Per Year BM Bimonthly PV Per Vehicle UR Upon Request BW Biweekly QU Quarterly WK Weekly

Block 4 – As of Date- If reports are of a recurring nature, an as of date will be included in this block (cutoff date and due date: e.g., 15/1 indicated input cutoff date of 15th and due date of 1st)

Block 5 – 1st Submittal Date

Block 6 – Copies –

Code Description

EM E-mail ES E-mail with Signature CD Compact Disk HC Hard Copy

Block 7 – Data Type

For the purpose of this clause, the following information/documentation types are applicable:

(1) Type1 - Written approval -- Data and changes thereto requiring written approval by the NASA Office of Primary Responsibility (OPR) before formal release or implementation

(2) Type2 - Mandatory submittal -- Data provided to NASA for coordination, information, review, and/or management control

4.2 - 4

(3) Type3 - Submitted upon request -- Data prepared and retained under a specific contract to be made available to NASA upon request

Block 8 – Distribution

Block 9 – Remarks: Additional requirements, clarification or amplification of requirements from other blocks.

4.2 - 1

a. Title of Contract, Project, SOW, etc. b. Contract/RFP No. c. DRL Date/Mod Date

Custodial, Housekeeping, Waste-Removal, and Insect Extermination NNJ15553635R Basic

1. Line item 2. DRD Title 3. Data Type 4. Frequency 5. As-of-date 6. 1st Submission

Date 7. Copies (1) Written approval 001 Safety & Health Plan (S&HP) (2) Mandatory Submittal One Time with Revisions

07/2014 With Proposal

a. Type b. Number

(3) Submitted upon request Elec. 1

8. Electronic Distribution 9. Remarks NS/Safety and Test Operations Division SD3/Occupational Health Branch JSC Emergency Preparedness Office BJ5/Contracting Officer JM/Contracting Officer’s Representative JM/Alternate Contracting Officer’s SPICE Administration Representative

Copies with proposal as provided in RFP instructions;

distribute after Government approval.

1. Line item 2. DRD Title 3. Data Type 4. Frequency 5. As-of-date 6. 1st Submission

Date 7. Copies (1) Written approval 002 Hazardous Materials Inventory (2) Mandatory Submittal Quarterly 01/2016 See 9 a. Type b. Number

SD3/Occupational Health Branch SPICE Administration JM/Contracting Officer’s Representative JM/Alternate Contracting Officer’s Representative

15 days following the end of the previous quarter.

1. Line item 2. DRD Title 3. Data Type 4. Frequency 5. As-of-date 6. 1st Submission

Date 7. Copies (1) Written approval 003 Notification of Potential Labor

Dispute & Contingency Strike Plan (Labor Relations)

(2) Mandatory Submittal As Required

10/02/2015 See 9 a. Type b. Number

(3) Submitted upon request Elec. 1

JSC Form 2323 (Rev November 9, 2004)

4.2 - 2

BJ5/Contracting Officer JM/Alternate Contracting JM/Contracting Officer’s Representative Officer’s Representative BD/JSC Labor Relations Officer SPICE Administration

Start of Contract.

1. Line item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

004 JSC Emergency Preparedness Plan

(2) Mandatory Submittal One Time with

Revisions

01/2016 See 9 a. Type b. Number

BJ5/Contracting Officer JSC Emergency Preparedness Office JM/Contracting Officer’s Representative SPICE Administration JM/Alternate Contracting Officer’s Representative

Plan is due to the CO 30 days after start of Contract for review and approval.

item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

005 Environmental & Energy Consuming Product Compliance Report

(2) Mandatory Submittal Annually 05/08/2013 See 9 a. Type b. Number

NS/Safety & Test Division JM/Contracting Officer’s Representative SD3/Occupational Health Branch JM/Alternate COR JE/JSC Environmental Office SPICE Administration

Due December 1st of each year.

The report shall be submitted within 30 days of the contract end date.

1. Line item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

006 Recycling and MSW Report (2) Mandatory Submittal Monthly 01/2016 See 9 a. Type b. Number

(3) Submitted upon request Elec. 1

8. Electronic Distribution 9. Remarks

JE/JSC Environmental Office SPICE Administration JM/Contracting Officer’s Representative JM/Alternate Contracting Officer’s Representative

Submit by the 20th of each month.

4.2 - 3

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

007 Quality Assurance Plan (2) Mandatory Submittal One Time 01/2016 See 9 a. Type b. Number

BJ5/Contracting Officer SPICE Administration JM/Contracting Officer’s Representative

The plan shall be submitted within 60 days after contract start for review and approval by the Contracting Officer.

1. Line item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

008 Custodial Services Management Plan

(2) Mandatory Submittal One Time 01/2016 See 9 a. Type b. Number

With proposal.

item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

009 IT Security Management Plan (2) Mandatory Submittal Annually 01/2016 See 9 a. Type b. Number

Submit within 60 days of contract start.

item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

4.2 - 4

010 Contractor Furnished Items (2) Mandatory Submittal One Time with

Revisions

01/2016 See 9 a. Type b. Number

JM/Contracting Officer’s Representative JM/Alternate Contracting Officer’s Representative

Plan shall be submitted 20 days prior to contract start.

1. Line item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

011 Custodial Cleaning Schedule (2) Mandatory Submittal Annually 01/2016 See 9 a. Type b. Number

SPICE Administration

Initial schedule submitted 20 days prior to contract start.

Annually, 30 days prior to anniversary date of contract start.

1. Line item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

012 Annual Work Plan (2) Mandatory Submittal Annually 01/2016 See 9 a. Type b. Number

JM/Alternate Contracting Officer’s Representative SPICE Administration

30 days after contract start.

Annually, 30 days prior to anniversary date of contract start.

1. Line item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

013 Pest Control Inspection and (2) Mandatory Submittal Annually 01/2016 See 9 a. Type b. Number

4.2 - 5

Maintenance Plan (3) Submitted upon request Elec. 1

20 days prior to contract start.

Annually, 30 days prior to anniversary date of contract start.

1. Line item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

014 Pest Control Application Report (2) Mandatory Submittal Monthly 01/2016 See 9 a. Type b. Number

SPICE Administration

By the 15th of each month.

item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

015 Termite Services Report (2) Mandatory Submittal Quarterly 01/2016 See 9 a. Type b. Number

JM/Alternate Contracting Officer’s Representative SPICE Administration

Due 15 days following end of previous quarter.

1. Line item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

016 Custodial Phase-In Plan (2) Mandatory Submittal One Time with

Revisions

01/2016 See 9 a. Type b. Number

4.2 - 6

With proposal.

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

017 RESERVED (2) Mandatory Submittal a. Type b. Number

(3) Submitted upon request

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

018 Labor Relations Plan (2) Mandatory Submittal One Time 10/02/2015 See 9 a. Type b. Number

BJ5/Contracting Officer SPICE Administration With proposal.

1. Line item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

019 Fall Protection Plan (2) Mandatory Submittal One Time 01/2016 See 9 a. Type b. Number

(3) Submitted upon request Elec. 1

4.2 - 7

JM/Contracting Officer’s Representative SPICE Administration

NS/Safety & Test Operations Division

Due within 90 days of contract start.

1. Line item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

020 Government Property Management Plan (PMP)

(2) Mandatory Submittal One Time with

Revisions

06/02/2014 As directed by the Contracting Officer

a. Type b. Number

JM/Contracting Officer’s Representative, JB3/Property Admin JM/Alternate Contracting Officer’s Representative

Initial submission - The Offeror(s) will be notified by the Contracting Officer if and when the PMP submittal is due.

Final submission - Due 30 days after contract award.

1. Line item 2. DRD Title

3. Data Type

4. Frequency 5. As-of-date

6. 1st Submission

Date

7. Copies (1) Written approval

021 Re-procurement Data Package (2) Mandatory Submittal Upon CO Request

02/29/2016 See 9 a. Type b. Number

JM/Contracting Officer’s Representative

Plan submitted within 30 days of contract end.