ESSCA_RFP_Attachment_J-2_Data_Procurement_Document.docx

NNM16568754R ATTACHMENT J-2

NATIONAL AERONAUTICS AND SPACE ADMINISTRATION (NASA)

ENGINEERING SERVICES AND SCIENCE CAPABILITY AUGMENTATION (ESSCA)

ATTACHMENT J-2

DATA PROCUREMENT DOCUMENT

NNM16568754R

CONTRACT/RFP

EXHIBIT NUMBER

J-2

ATTACHMENT NUMBER

Engineering Services and Science Capability Augmentation (ESSCA)

PROJECT/SYSTEM

DATA PROCUREMENT DOCUMENT

Contractor

CONTRACTOR

September 7, 2016

DATE

National Aeronautics and Space Administration

NNM16568754R ATTACHMENT J-2

J-2-9 National Aeronautics and Space Administration

DOCUMENT CHANGE LOG

DATA PROCUREMENT DOCUMENT

NO. ISSUE

1563 RFP

09-07-16

SUPERSEDING:

PAGE:

1.0 INTRODUCTION

1.1 Scope: Subject to the Rights in Data clause, this Data Procurement Document (DPD) sets forth the data requirements in each Data Requirements Description (DRD) and shall govern that data required by the DPD for the contract. The contractor shall furnish data defined by the DRDs listed on the Data Requirements List (DRL) by category of data, attached hereto, and made a part of this DPD. Such data shall be prepared, maintained, and delivered to NASA in accordance with the requirements set forth within this DPD. In cases where data requirements are covered by a Federal Acquisition Regulation (FAR) or NASA FAR Supplement (NFS) clause, that clause shall take precedence over the DPD, consistent with clause FAR 52.215-8.

1.2 DPD Description: This DPD consists of a Document Change Log, an Introduction, a Statement of General Requirements, DPD maintenance procedures, a DRL, and the DRDs.

1.2.1 General Requirements: The general requirements, as specified in paragraph 2.0 of this DPD, prescribe those requirements applicable to the preparation, maintenance, and delivery of data that are better defined in aggregate than in the individual DRDs.

1.2.2 Data Requirements List (DRL): Throughout the performance of the contract, the DRL provides a listing by data category of the data requirements of the DPD.

1.2.3 Data Requirements Description (DRD)

1.2.3.1 Each data requirement listed on the DRL is given complete definition by a DRD. The DRD prescribes content, format, maintenance instructions, and submittal requirements.

1.2.3.2 For the purpose of classification and control, DRDs of this DPD are grouped into the following broad functional data categories:

1.2.3.3 The symbols representing these data categories form part of the prefix of the DRD identification number. The first numerical characters reflect the DPD number.

1.2.3.4 To facilitate the usage and maintenance of the DPD, the DRDs have been sectionalized in accordance with the above data categories.

1.2.3.5 The DRDs are filed by data category and are in alpha-numeric sequence as listed on the DRL page (or pages) that precedes the DRDs.

1.2.4 Document Change Log (DCL): The Document Change Log chronologically records all revision actions that pertain to the DPD.

1.2.5 DPD Maintenance Procedures: Maintenance procedures define the detailed methods to be employed in maintaining the DPD. Detailed maintenance procedures are specified in paragraph 3.0 of this DPD.

1.3 Data Types for Contractual Efforts: The types of data and their contractually applicable requirements for approval and delivery are:

TYPE DESCRIPTION

3 These data shall be delivered by the contractor as required by the contract and do not require NASA approval. However, to be a satisfactory delivery, the data shall satisfy all applicable contractual requirements and be submitted on time.

4 These data are produced or used during performance of the contract and are retained by the contractor. They shall be delivered only when NASA requests in writing and shall be delivered in accordance with the instructions in the request. The contractor shall maintain a list of these data and shall furnish copies of the list to NASA when requested to do so.

5 These data are incidental to contract performance and are retained by the contractor in those cases where contracting parties have agreed that formal delivery is not required. However, the Contracting Officer or the Contracting Officer’s Representative (COR) shall have access to and can inspect this data at its location in the contractor’s or subcontractor’s facilities, or in an electronic database accessible to the Government.

* Note: Type 1 and Type 2 data may be placed under NASA configuration management control when designated by NASA. CM control requires the contractor to submit Type 1 and Type 2 data updates through Engineering Change Proposals (ECPs).

** Note: This time limit may be tailored for individual DRDs to meet the requirements of the procuring activity.

*** Note: If the contractor does not identify a release target date or if the intended release date is shorter than 45 calendar days from the date of submission, the 45 calendar days review cycle stands (or the tailored Type 2 time limitation for the specific procurement).

2.0 STATEMENT OF GENERAL REQUIREMENTS

2.1 Applicable/Reference Documents: Documents included as applicable documents in this DPD are the issue specified in the Statement of Work, and form a part of the DPD to the extent specified herein. Applicable documents listed in Item 15.2 of a DRD are applicable only to the preparation of the deliverable documentation described by that DRD.

References to documents other than applicable documents in the data requirements of this DPD may sometimes be utilized, and shall be indicated in 13. Remarks of the DRD. 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.

2.2 Subcontractor Data Requirements

2.2.1 The Contractor shall specify to subcontractors and vendors, if any, the availability source of all data required for the satisfactory accomplishment of their contracts. The Contractor shall validate these requirements for documents when appropriate; where the requirement concerns other contractor data, the Contractor shall provide his subcontractor or vendor with the necessary documents. All such requests shall be accomplished under the auspices of the Contractor.

2.2.2 Reference to subcontractor data in the Contractor’s responses is permissible, providing the references are adequate and includes such identification elements as title, number, revision, etc., and a copy of the referenced data is supplied with the response document at time of delivery to NASA.

2.3 Data Distribution, Format, Data Restriction Marking, and Transmittal

2.3.1 Distribution: Distribution of required documentation shall be in quantities determined by the Contracting Officer. Recipient names and email (if applicable) addresses shall be noted on a separate distribution list to be furnished by the Contracting Officer. The Contracting Officer’s letter may include other information pertinent to delivery of data, as required.

2.3.2 Format

2.3.2.1 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®, PowerPoint® or CAD drawing plot file, as appropriate. Where a single native format file is not possible, multiple files may be integrated into a single ZIP file for submission. The organization of the contents of the integrated ZIP file shall be made readily apparent to the reader, and each file within the integrated product shall be clearly identifiable and traceable within the organization of the integrated product. If files are fragmented, file names shall be labeled logically and contiguously, and the files shall be easily reassembled or merged (e.g., 1 filename, 2 filename, 2a filename). The software versions shall be confirmed prior to submittals.

2.3.2.2 Hardcopy Format: In addition to the electronic submittal, one hardcopy package of specific data deliverables shall be delivered to the NASA Contracting Officer for the Government contract file. The hardcopy package shall consist of the contractor’s Transmittal Memo and one copy of the data deliverable.

2.3.3 Data Restriction Marking

0. Data Restriction Determination and Marking Requirements: The contractor shall determine the data restriction that applies to each data deliverable and mark the data restriction on the data coversheet, or indicate the data restriction in the data transmittal package if the data format precludes identification of data restriction directly in the data. The contractor shall make a determination for each individual data deliverable item, 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 NASA Contracting Officer 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.

0. Data Restriction Categories and Marking Statements: The contractor shall consider the following data restriction categories, as a minimum, and utilize specified marking statements.

If data delivered under this contract is subject to the International Traffic in Arms Regulations (ITAR), the data shall contain an “ITAR Notice” as follows:

International Traffic in Arms Regulations (ITAR) Notice This document contains information which falls under the purview of the U.S. Munitions List (USML), as defined in the International Traffic in Arms Regulations (ITAR), 22 CFR 120-130, and is export controlled. It shall not be transferred to foreign nationals, in the U.S. or abroad, without specific approval of a knowledgeable NASA export control official, and/or unless an export license/license exemption is obtained/available from the United States Department of State. Violations of these regulations are punishable by fine, imprisonment, or both.

If data delivered under this contract is subject to the Export Administration Regulations (EAR), the data shall contain the “EAR Notice” as follows:

Export Administration Regulations (EAR) Notice This document contains information within the purview of the Export Administration Regulations (EAR), 15 CFR 730-774, and is export controlled. It may not be transferred to foreign nationals in the U.S. or abroad without specific approval of a knowledgeable NASA export control official, and/or unless an export license/license exception is obtained/available from the Bureau of Industry and Security, United States Department of Commerce. Violations of these regulations are punishable by fine, imprisonment, or both.

If the contract contains FAR 52.227-14 Alternate II, the “Limited Rights Notice” may be applicable to data (other than computer software) delivered under this contract.

If the contract contains FAR 52.227-14 Alternate III, the “Restricted Rights Notice” may be applicable to computer software delivered under this contract.

If the contract contains FAR 52.227-20, the “SBIR Rights Notice” may be applicable to SBIR data delivered under this contract.

If the contract contains NFS 1852.237-73, a sensitive information legend may be applicable to information delivered under this contract.

In accordance with the applicable data clause (e.g., FAR 52.227-14(c) or FAR 52.227-20(c)), the contractor may be able to assert a copyright claim in data delivered under this contract. When claim to copyright is made, the Contractor shall affix the applicable copyright notices of 17 U.S.C. 401 or 402 and acknowledgment of Government sponsorship (including contract number) to the data when such data are delivered to the Government.

0. Transmittal

1. Requested response date.

1. Contractor assigned data restriction (export controlled, limited rights data, SBIR, restricted computer software, copyrighted, etc.) if not marked on data.

1. NASA Records Retention Schedule (NRRS) number, if applicable (See NPR 1441.1, NASA Records Management Program Requirements).

b. Printable electronic files or hardcopy data.

2.3.5 When electronic data deliverables are transmitted directly to the MSFC Repository, the Digital Asset Manager web interface shall be utilized. Instructions for electronic data submittals can be found at http://avmcc.msfc.nasa.gov/repository/repository_submittal.php. Document submitters to the Repository must register for a MSFC EDMS (Documentum) user account, through the Identity Management and Account Exchange (idMAX) system. Computer-Aided Design (CAD) drawings shall be submitted in the original native vector, Hewlett-Packard Graphic Language (HPGL), and raster image formats.

2.5 Contractor’s Internal Documents: The contractor’s internal documents shall be used to meet the data requirements of this DPD unless a specific format is required by the applicable DRD.

2.6 Document Identification: Type 1 and 2 documents published by the contractor and submitted in response to the data requirements of this DPD shall be identified within an organized identification numbering system prescribed to NASA by the contractor and, if applicable, as approved by NASA. 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. In the front matter of each document, identify the DPD number and applicable DRD number(s) required for document preparation. Successive issues or revisions of documents shall be identified in the same manner as the basic issue and shall have appropriate change identification. Drawings and ECP's are excluded from the marking provisions of this paragraph. All Type 1 documentation, excluding configuration management requirements, 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.

2.7 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. The contractor shall make sure that the references are available to NASA in a manner which does not incur delays in the use of the response document. Reference may be made, within one data submittal, to other data submittals delivered in response to this DPD in those cases where the data required by one DRD may have been delivered by the contractor in response to another DRD. The reference to previously-submitted data shall include the applicable DRD number, data submittal version date, and location within the referenced document.

2.8 Maintenance of Type 1 Document Submittals

2.8.1 Revisions of Type 1 documentation may be accomplished either by individual page revision or by a complete reissue of the document identified in accordance with requirements of 2.6 above, with the exception of drawings (which shall be revised in accordance with contract configuration management requirements).

2.8.2 Individual page revisions shall be made as deemed necessary by the contractor or as directed by the Contracting Officer.

2.8.5 All revised pages shall be identified by a revision symbol 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 by the use of vertical line in the margin of the page, and the change authority shall be indicated adjacent to the change.

2.8.6 Contractor Type 1 document shall not be submitted containing pen and ink markups which correct, add to, or change the text, unless schedule problems exist and approval is obtained in writing from the Contracting Officer. Such markups, however, shall not exceed 20 percent of the page content and shall be acceptable provided that the reproduced copies are legible. In addition, hand-drawn schematics, block diagrams, data curves, and similar charts may be used in original reports in lieu of formally prepared art work, as long as legibility of copies is not impaired. Acceptability shall be determined by the Contracting Officer.

3.0 DPD MAINTENANCE PROCEDURES

3.1 NASA-Initiated Change: New and/or revised data requirements shall be incorporated by contract modification to which the new or revised portion of the DPD shall be appended. The Contractor shall notify the Contracting Officer in the event a deliverable data requirement is imposed and is not covered by a DRD, or when a DRD is changed by a contract modification and for which no revision to DPD is appended. In such cases, the Contractor shall submit the requested changes to NASA for approval. See paragraph 3.3 for change procedures.

3.2 Contractor-Initiated Change: Contractor-proposed data requirements or proposed changes to existing requirements shall be submitted to NASA for approval.

3.3 DPD Change Procedures

3.3.1 Changes to a contractual issue of this DPD shall be identified by NASA on the Document Change Log.

3.3.2 The date of the DPD shall be entered under the “as of” block of the Document Change Log. The date that was in the “as of” block shall be entered in the “Superseding” block.

3.3.3 The Document Change Log section entitled “Incorporated Revisions” shall be changed to indicate the revision number, portions affected, and remarks. All changes to the DPD/DRDs shall be identified in the “Remarks” column.

3.4 DPD Reissues

3.4.1 When conditions warrant, the DPD shall be reissued by NASA for each contract modification that affects the DPD and shall supersede the existing DPD in its entirety. Reissues shall be issued by contractual direction.

3.4.2 All revision dates shall remain in the Date Revised block on all DRDs. The issue symbol, which shall commence with "A" and progress through "Z," shall be entered in the DPD identification block of each DRD page of the DPD.

Engineering Services and Science Capability Augmentation (ESSCA)

Data Requirements List

DRD DATA TYPE TITLE OPR

CD – Contractual Data

EE – Environmental 1563EE-001 3 Environmental Compliance Reports AS10

LS – Logistics Support 1563LS-001 2 Government Property Management Plan AS41

MA – Management

SA – Safety

DATA REQUIREMENTS DESCRIPTION (DRD)

7. DESCRIPTION/USE: To assist Marshall Space Flight Center (MSFC) or Michoud Assembly Facility (MAF) in conducting Contractor floor checks.

8. OPR: PS12 9. DM: ED01

10. DISTRIBUTION: Per Contracting Officer's letter

11. INITIAL SUBMISSION: Within 15 calendar days after commencement of contract

12. SUBMISSION FREQUENCY: Update quarterly, or as requested by the Contracting Officer

13. REMARKS: Reference is made to Federal Acquisition Regulation (FAR) Clause, FAR 52.215-2, Audit and Records--Negotiation.

14. INTERRELATIONSHIP: PWS paragraph 2.2.2

15.2 APPLICABLE DOCUMENTS: None

15.3 CONTENTS: The On-Site Employee Location Listing shall include the following information for each employee: employee's name, position, location (building/room number), shift assignment, supervisor's name, and supervisor's location (building/room number).

15.4 FORMAT: Contractor format is acceptable.

15.5 MAINTENANCE: None required

6. TITLE: Technology Reports

7. DESCRIPTION/USE: Provides NASA with technical information concerning any invention, discovery, improvement, or innovation made by a Contractor in the performance of work under this contract for the purpose of disseminating this information to obtain increased use and provide NASA with data to review for possible patentable items.

8. OPR: ZP30 9. DM: ED01

10. DISTRIBUTION: Per Contracting Officer's letter

12. SUBMISSION FREQUENCY:

Technology Reporting Plan: Upon Contracting Officer’s request.

Disclosure of Invention and New Technology (NASA Form 1679): Upon identification of each reportable item.

Interim NASA New Technology Summary Report (NTSR) Form: Every 12 months.

Final NASA New Technology Summary Report (NTSR) Form: Immediately or within two months after completion of contracted work. Final Payment is contingent upon submission of the Final NTSR.

13. REMARKS: Copies of NASA Form 1679 and the NASA New Technology Summary Report (NTSR) Form (Interim and Final) may be obtained and/or filled out at: https://ntr.ndc.nasa.gov/ or https://invention.nasa.gov/. These forms may also be obtained from the New Technology Representative (mailto: Carolyn.E.McMillan@nasa.gov).

14. INTERRELATIONSHIP: PWS paragraph 2.1.9

DRD Continuation Sheet

15.5 MAINTENANCE: None required

6. TITLE: Environmental Compliance Reports

7. DESCRIPTION/USE: To provide the Government data related to Contractor compliance with green purchasing, waste reduction, and ozone depleting substances environmental requirements.

8. OPR: AS10 9. DM: ED01

10. DISTRIBUTION: Per Contracting Officer’s letter

11. INITIAL SUBMISSION: Annual Green Purchasing Report - End of contract year. Waste Reduction Activity Report - End of contract year. Ozone Depleting Substances (ODS) Notifications - End of contract year. Equipment Notifications - Prior to purchasing.

12. SUBMISSION FREQUENCY: Annually, at the end of contract year, except for equipment notifications that shall be submitted prior to purchasing.

13. REMARKS: For 15.3a and 15.3c, where the Contractor does not purchase any designated product or equipment during the contract year or duration of contract, the report shall be a statement to that effect. For 15.3d, if the Contractor does not purchase, own, operate, maintain, or repair Ozone Depleting Substances (ODS) equipment on-site, the report shall be a statement to that effect.

14. INTERRELATIONSHIP: DRD 1563SA-001, On-site Safety, Health, and Environmental (SHE) Plan. PWS paragraph 2.1.7

DRD Continuation Sheet

d. Equipment Notifications:

15.5 MAINTENANCE: None required

DATA REQUIREMENTS DESCRIPTION (DRD)

6. TITLE: Government Property Management Plan

7. DESCRIPTION/USE: To describe the method of controlling and managing Government property.

8. OPR: AS41 9. DM: ED01

10. DISTRIBUTION: Cognizant property administrator

11. INITIAL SUBMISSION: Preliminary with proposal. Final two months after commencement of the contract.

12. SUBMISSION FREQUENCY: Update as required

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

14. INTERRELATIONSHIP: PWS paragraph 2.1.4

DRD Continuation Sheet

15.4 FORMAT: Contractor format is acceptable.

15.5 MAINTENANCE: Changes shall be incorporated by complete reissue.

6. TITLE: Management Plan

7. DESCRIPTION/USE: To provide a description of the Contractor's overall management system and organization for accomplishing the requirements set forth in the contract.

8. OPR: ED01 9. DM: ED01

10. DISTRIBUTION: Per Contracting Officer's letter

11. INITIAL SUBMISSION: During contract phase-in, 30 calendar days prior to commencement of contract

12. SUBMISSION FREQUENCY: Update as required

13. REMARKS:

14. INTERRELATIONSHIP: Reference is made to Clauses I.9, 1852.216-80 Task Ordering Procedure, I.10, Supplemental Task Ordering Procedures, and 1852.204-76, Security Requirements for Unclassified Information Technology Resources. PWS paragraph 2.1.2

15.3 CONTENTS: The Contractor’s Management Plan shall include:

a. Management approach for accomplishing the requirements set forth in the contract, i.e., negotiating, managing and controlling all aspects of the Task Order process. The plan shall be in such detail as necessary to address how the ATOMS will be an effective tool in accomplishing these requirements, as well as convey the Contractor's internal procedures. The plan shall include a description of the approach to assure maximum availability of the ATOMS system to users as well as frequency and scope of data backup efforts for data retention.

b. Management concepts, plans, practices, organizational approach, and communication channels between the Contractor, subcontractors, teammates and the Government. This shall include descriptions, flow charts, authority channels (including level of local autonomy), schedules, and how the work maps to its organization and other documentation necessary to give a comprehensive plan.

c. Management approach for cost control, managing indirect cost rates, tracking and allocating all costs (labor and non-labor) associated with each Task Order.

d. Process of setting goals and establishing policies, practices, procedures, and organizational structure to support the MSFC Governance processes.

e. Staffing approach to include recruitment and retention plans, flexibility to accommodate changes in requirements, fluctuation in workload and unexpected attrition.

f. Approach to ensure technical excellence in products and personnel.

g. Approach to requirements compliance, continuous improvement and innovation.

h. Approach to Organizational Conflicts of Interest issues.

i. Definition of management structure and lines of authority to support reporting requirements as defined in the DPD in a fashion that contributes to the timely notice and resolution of problems and concerns that arise in the performance of this contract.

j. How the Contractor will develop, implement, and maintain IT Security. This section shall describe the processes and procedures that will be followed to ensure the appropriate security of IT resources that are developed, processed, or used under this contract. This shall include the IT Security Management Plan in accordance with NFS 1852.204-76 which includes an IT Security Plan.

k. How the Contractor will develop, implement, and maintain export control. This section shall describe the processes and procedures that will be followed to ensure compliance with the appropriate regulations.

l. Approach for education and public outreach.

15.4 FORMAT: Contractor format is acceptable.

15.5 MAINTENANCE: Changes shall be incorporated by complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

6. TITLE: Technology, Innovations, and Process Improvement Plan (TIPI)

7. DESCRIPTION/USE: To identify and promote Technology, Innovations, and Process Improvements that will improve MSFC and MAF products, processes, and operations.

8. OPR: ED01 9. DM: ED01

10. DISTRIBUTION: Per Contracting Officer’s letter

11. INITIAL SUBMISSION: During contract phase-in, 30 calendar days prior to commencement of contract

12. SUBMISSION FREQUENCY: Annually - First update due 60 calendar days after commencement of contract, subsequent updates due 30 calendar days following anniversary of contract start, or sooner should new Technology, Innovations or Process Improvements be identified.

13. REMARKS:

14. INTERRELATIONSHIP: DRDs 1563MA-001, Management Plan and 1563MA-008, Weekly Contract Status Briefing. PWS paragraph 2.6

Upon approval, the plan will become a part of the contract as an Appendix to J-1. Development of the Implementation Plan and implementation of proposed innovations and/or improvements and any detailed assessments of such proposals may be authorized on a Task Order under Section 3 of the PWS.

15.2 APPLICABLE DOCUMENTS: None

15.4 FORMAT: Contractor’s format is acceptable.

15.5 MAINTENANCE: Changes shall be incorporated by complete reissue.

7. DESCRIPTION/USE: Provides Marshall Space Flight Center (MSFC) with information on specific items and supporting documentation related to labor resources and associated cost information, to be used for re-procurement activities. In the event of a competitive solicitation for a follow-on effort, MSFC may provide non-proprietary historical information such as average composite direct labor rates to all interested parties in order to increase the probability of realistic pricing. Specific rates for individual labor categories will not be disclosed.

8. OPR: PS60 9. DM: ED01

10. DISTRIBUTION: Per Contracting Officer's letter

11. INITIAL SUBMISSION: 15 calendar days after commencement of contract (for baseline purposes)

12. SUBMISSION FREQUENCY: Annually, no later than the fifteenth day of the month following the end of each twelve month period of contract performance. If deemed necessary by the Contracting Officer, the Contractor and all subcontractors shall submit the data package at times other than stated.

13. REMARKS: Subcontractors may submit the required information directly to the Government.

14. INTERRELATIONSHIP: PWS paragraph 2.0

15.2 APPLICABLE DOCUMENTS: None