Attachment_(C)_-_Data_Procurement_Document_(3-6-18)_Amend_1.docx

RFP: 80NSSC18R0025

80NSSC18R0025

CONTRACT/RFP

C

ATTACHMENT NUMBER

Agency-Wide Acquisition Support Services

PROJECT/SYSTEM

DATA PROCUREMENT DOCUMENT

To Be Determined

CONTRACTOR

DATE

National Aeronautics and Space Administration MSFC - Form 3461 (Rev September 1989) National Aeronautics and Space Administration

DOCUMENT CHANGE LOG

DATA PROCUREMENT DOC.

NO. ISSUE

N/A RFP

XX/XX/2017

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) 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, Order of Precedence – Uniform Contract Format (OCT 1997).

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 Descriptions (DRDs)

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 The DRDs 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

1* All issues and interim changes to those issues require written approval from the requiring organization before formal release for use or implementation.

2* NASA reserves a time-limited right to disapprove in writing any issues and interim changes to those issues. The Contractor shall submit the required data to NASA for review not less than forty-five (45) calendar days** prior to its release for use. The Contractor shall clearly identify the release target date in the “submitted for review” transmittal***. If the data is unacceptable, NASA will notify the Contractor within forty-five (45) calendar days** 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 NASA within forty-five (45) calendar days**.

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 Technical Representative 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 forty-five (45) calendar days from the date of submission, the forty-five (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 Attachment (A), Performance Work Statement, 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 will be indicated in Item 13 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 include 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 e-mail (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 Office Open XML file format (e.g., Microsoft Word, Excel, PowerPoint, Project, and Visio) or AutoCAD 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, etc.). The software versions shall be confirmed prior to submittals.

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

2.3.4.1 Data shall be transmitted to NASA by e-mail, CD or DVD, hardcopy, or other mechanism agreed to by the Contracting Officer, COR, and Project representatives who are responsible to receive, index, and store the data deliverables.

2.3.4.2 If e-mail is used to transmit data deliverables, the e-mail size shall be 10 Megabytes or less to ensure receipt by the NASA e-mail servers. Encrypted e-mail format shall be used to transmit data which has been judged sensitive by the Contractor or by NASA (e.g., export controlled, limited rights data, SBIR, restricted computer software, copyrighted, etc.).

9. Requested response date.

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

11. NASA Records Retention Schedule (NRRS) number, if applicable. (See NPR 1441.1E, NASA Records Retention Schedules).

b. Printable electronic files or hardcopy data.

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 ECPs 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 should 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 paragraph 2.7 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.3 A Type 1 document shall be completely reissued when, in the opinion of the Contractor and/or NASA, the document has been revised to the extent that it is unusable in its present state, or when directed by the Contracting Officer. When complete reissues are made, the entire contents of the document shall be brought up to date and shall incorporate revised pages. All revisions shall be recorded. A revision log shall identify complete reissues except for periodic reports and documents which are complete within themselves as final.

2.8.4 Changes of a minor nature to correct obvious typing errors, misspelled words, etc., shall only be made when a technical change is made, unless the accuracy of the document is affected.

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 documents 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 twenty (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.1 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 entitled “Incorporated Revisions” shall be changed to indicate the modification 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 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. 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.

Agency-Wide Acquisition Support Services Data Requirements List

DATA REQUIREMENTS DESCRIPTION (DRD)

7. DESCRIPTION/USE: To provide a monthly summary of progress and status of activities.

8. OPR: XD-042 9. DM: XD-042

10. DISTRIBUTION: Administrative Contracting Officer and Task Managers at each Center.

11. INITIAL SUBMISSION: TBP

12. SUBMISSION FREQUENCY: Monthly Progress & Status report due NLT ten (10) working days following the end of each calendar month.

13. REMARKS: None.

14. INTERRELATIONSHIP: PWS, Section 4.5, Reporting Deliverables.

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The report provides status of acquisition and contract closeout support activity at each Center.

15.2 APPLICABLE DOCUMENTS: None.

15.3 CONTENTS: The Monthly Progress & Status report covers a specific reporting period, and shall include the following:

· Number of instruments (by type) received at beginning of period, closed during period, and remaining open at end of period

· Totals for inception to date

· Totals for current period of performance to date

· Unliquidated obligations (deobligated during period, remaining at end of period)

15.4 FORMAT: Electronic submission, Contractor format is acceptable following guidelines in 15.3.

15.5 MAINTENANCE: None required.

7. DESCRIPTION/USE: To provide a monthly closeout summary to HQ.

8. OPR: XD-042 9. DM: XD-042

11. INITIAL SUBMISSION: TBP

12. SUBMISSION FREQUENCY: Monthly charts due nineteen (19) calendar days following the end of each calendar month.

13. REMARKS: None.

14. INTERRELATIONSHIP: PWS, Section 4.5, Reporting Deliverables.

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Report identifies monthly and yearly closeout trends.

15.2 APPLICABLE DOCUMENTS: None.

15.3 CONTENTS: The Monthly Closeout Trending Charts cover a specific reporting period, and shall include the following:

a. Eleven (11) pie charts (1 representing each Center)

· Number of documents closed out that month

· Amount deobligated in dollars

· Awards broken down by type (Purchase order, Fixed Price, Grant/Cooperative Agreement, Interagency, & Cost Reimbursable)

b. Eleven (11) bar charts (1 representing each Center) Showing 12 month trend of documents closed

· Dollars deobligated for current year and previous year (not broken out by types)

· Closed documents shown in two lines ( 2 colors: current year & previous year)

· Deobligated amounts shown in bars (2 bars for each month: month of prior year & month of current year)

c. One (1) Agency chart

· Trend chart of 12 months of closed and deobligated-prior year and current year

· Closed documents shown in two lines (2 colors: prior year and current year)

· Bars indicate deobligated amounts (2 bars for each month: month of prior year & month of current year)

15.4 FORMAT: Electronic submission, Contractor format is acceptable following guidelines in 15.3.

15.5 MAINTENANCE: None required.

7. DESCRIPTION/USE: Contractor report used for various security and physical access to facility requirements.

8. OPR: XD-042 9. DM: XD-042

10. DISTRIBUTION: Administrative Contracting Officer.

11. INITIAL SUBMISSION: TBP

12. SUBMISSION FREQUENCY: Employee Listing due yearly on the Tenth (10th) working day after the beginning of the fiscal year

13. REMARKS: None.

14. INTERRELATIONSHIP: PWS, Section 4.5, Reporting Deliverables.

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Employee Listing shall provide a listing of all employees for use with various security and administrative requirements.

b. An Agency report that includes the total number of employees: employee’s name, position, Center location, and area of support (closeout, procurement support).

c. The employee listing shall include personnel working both on-site and off-site.

15.4 FORMAT: Electronic submission, Contractor format is acceptable following guidelines in 15.3.

15.5 MAINTENANCE: None required.

7. DESCRIPTION/USE: To provide a monthly list of any FFP-LOE task orders issued or modifications to existing FFP-LOE task orders by Center Procurement Offices.

8. OPR: XD-042 9. DM: XD-042

10. DISTRIBUTION: Administrative Contracting Officer.

11. INITIAL SUBMISSION: TBP

12. SUBMISSION FREQUENCY: FFP-LOE Task Order List due NLT ten (10) working days following the end of each calendar month.

13. REMARKS: None.

14. INTERRELATIONSHIP: PWS, Section 4.5, Reporting Deliverables.

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Report identifies FFP-LOE task orders issued by Center Procurement Office, description of services ordered, period of performance, and amount of task order.

15.2 APPLICABLE DOCUMENTS: None

15.3 CONTENTS: The FFP-LOE Task Order List covers a specific reporting period, and shall include the following:

a. FFP-LOE Task Order Number

b. Description of Services

c. Period of Performance

d. Center

e. Amount

15.4 FORMAT: Electronic submission, Contractor format is acceptable following guidelines in 15.3.

15.5 MAINTENANCE: None required.

7. DESCRIPTION/USE: To provide report of monthly telecons.

8. OPR: XD-042 9. DM: XD-042

10. DISTRIBUTION: Administrative Contracting Officer and Center Technical Monitors.

11. INITIAL SUBMISSION: Second (2nd) working day following first monthly telecon.

12. SUBMISSION FREQUENCY: Monthly Telecon Minutes due NLT two (2) working days following the monthly telecon.

13. REMARKS: None.

14. INTERRELATIONSHIP: PWS, Section 4.5, Reporting Deliverables; Section 4.8, Status Meetings.

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Report summarizes actions and discussions during monthly telecons.

15.2 APPLICABLE DOCUMENTS: None.

15.3 CONTENTS: The Monthly Telecon Minutes report covers a specific reporting period, and shall include the following:

a. Typed and proof-read minutes from monthly telecon

b. List of participants

c. Action items

d. Date and Time

15.4 FORMAT: Electronic submission, Contractor format is acceptable following guidelines in 15.3.

15.5 MAINTENANCE: None required.

7. DESCRIPTION/USE: To demonstrate to the Government that the Contractor will avoid, neutralize, or mitigate organizational conflicts of interest and ensure that the Contractor provides unbiased impartial advice and adequately protects sensitive, proprietary data belonging to other contractors.

8. OPR: XD-042 9. DM: XD-042

10. DISTRIBUTION: Administrative Contracting Officer.

11. INITIAL SUBMISSION: The plan is required with proposal submission and for FFP/FFP-LOE Task Orders specific plans when required. If required, for FFP/FFP-LOE Task Orders, the updated plan shall be submitted within 10 days after award of the order.

12. SUBMISSION FREQUENCY: The plan shall be provided by the contractor with submission of the proposal. The plan shall include NFS 1852.237-72 Access to Senstive Information. and NFS 1852.237-73 Release of Sensitive Information. The Contractor shall submit to the CO and COR any updates to this plan necessary during performance of this contract and shall deliver a FFP-LOE task order specific plan when required.

13. REMARKS: None.

14. INTERRELATIONSHIP: Statement of Work, Section 4.5, Reporting Deliverables; and Provision NFS 1852.237-72, Access to Sensitive Information and NFS 1852.237-73, Release of Sensitive Information.

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Organizational Conflict of Interest (OCI) Plan describes the Contractor’s approach to identify, resolve, and report potential OCI issues. The DRD provides information detailing the Contractor’s methods for resolving potential OCIs.

15.3 CONTENTS: The Organizational Conflict of Interest (OCI) Mitigation Plan should include (1) the Contractor’s approach to identify, resolve, and report potential OCI issues and (2) an appendix of specific mitigation strategies for resolving identified OCIs. At a minimum, the plan shall include the following:

1. Describe the actions the contractor intends to take to mitigate if any OCIs. If using a firewall, explain how these actions will operate to successfully address the conflict without adversely affecting performance of the contract. Additionally, identify any potential OCIs created by the requirements of this RFP which the contractor intended to re-solves using methods other than mitigation. Specific mitigation strategies shall be appended to the mitigation plan.

2. Require the reporting of all potential/actual OCIs 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 vis-à-vis contract per-formance associated with plan approval/acceptance.

DRD Continuation Sheet

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

4. Define company roles, responsibilities, and procedures for screening (i.e., identifying/recognizing, analyz-ing/evaluating, resolving, and reporting) existing and new business opportunities for actual/potential OCIs.

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

6. Explain how the contractor will flow down the provisions of this mitigation 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 OCIs associated with this contract.

7. Establish and require entrance training for new employees, refresher training for existing employees, and exit train-ing for departing employees.

8. Define organizational and employee sanctions for violations of established OCI procedures/requirements/guidelines.

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

10. Define records related to the OCI plan (e.g., training and audit records) that will be made available to the Government upon request.

15.4 FORMAT: Contractor format is acceptable.

15.5 MAINTENANCE: Changes shall be incorporated as required by change page(s) or complete reissue.

7. DESCRIPTION/USE: To provide the Contractor’s policies and procedures for complying with the IT security requirements of NFS 1852-204-76, Security Requirements for Unclassified Information Technology Resources (JAN 2011), and any additions/augmentations described in NPR 2810.1, Security of Information Technology. This document will be used as part of the NASA IT security certification and accreditation process and to identify IT system inventories and appropriate Contractor IT security points of contact.

8. OPR: XD-042 9. DM: XD-042

10. DISTRIBUTION: Administrative Contracting Officer.

11. INITIAL SUBMISSION: Due 30 days after contract award.

12. SUBMISSION FREQUENCY: Once/Updated as needed.

13. REMARKS: None.

14. INTERRELATIONSHIP: PWS, Section 4.5, Reporting Deliverables; NFS 1852.204-76, Security Requirements For Unclassified Information Technology Resources.

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Information Technology (IT) Security Plan includes a description of planned implementation of security controls, risk assessment, self assessment of security plans, and contingency plan, in compliance with NIST SP 800-18 and NIST SP 800-53.

DRD Continuation Sheet

TITLE: Information Technology (IT) Security Plan DRD NO.: 7

DATA TYPE: 1 PAGE: 2/2

15.4 FORMAT: Contractor format is acceptable following guidelines in 15.3.

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

5. PAGE: 1/2

6. TITLE: Safety and Health Plan

7. DESCRIPTION/USE: The Safety and Health Plan describes the Contractor’s approach for assuring compliance with NASA safety and health care program requirements. The Contractor’s Plan shall describe how the Contractor will (1) prevent employee fatalities, (2) reduce the number of incidents, (3) reduce the severity of employee injuries and illnesses, and (4) protect the environment through the ongoing planning, implementation, integration and management control of the Contractor's industrial safety, occupational health, and environmental program in accordance with NFS 1852.223-73, Safety and Health Plan.

8. OPR: XB000 9. DM: XD-042

10. DISTRIBUTION: Administrative Contracting Officer and NSSC Safety, Security & Environmental Health Manager

11. INITIAL SUBMISSION: Due 30 days after contract award.

12. SUBMISSION FREQUENCY: Once/Updated as needed.

13. REMARKS: None.

14. INTERRELATIONSHIP: PWS, Section 4.5, Reporting Deliverables, NFS 1852.223-72, Safety and Health Plan (Short Form).

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Safety and Health Plan describes the Contractor’s methods of planning, implementing, and controlling industrial safety, occupational health, and environmental requirements.

15.3 CONTENTS: The Contractor’s Safety and Health Plan shall clearly describe their approach and methods for assuring compliance with the Agency’s and Centers’ safety and health care program requirements. The Plan shall include the following:

DRD Continuation Sheet

15.4 FORMAT: Contractor format is acceptable following guidelines in 15.3

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

7. DESCRIPTION/USE: To describe the Contractor’s method for establishing and maintaining an ongoing training program for all personnel under this contract.

8. OPR: XD-042 9. DM: XD-042

10. DISTRIBUTION: Administrative Contracting Officer.

11. INITIAL SUBMISSION: Due 30 days after contract award.

12. SUBMISSION FREQUENCY: Once/Updated as needed.

13. REMARKS: None.

14. INTERRELATIONSHIP: PWS Section 3.5, Reporting Deliverables

15. DATA PREPARATION INFORMATION:

15.4 FORMAT: Contractor format is acceptable with NASA approval.

15.5 MAINTENANCE: Changes shall be incorporated by complete reissue.

7. DESCRIPTION/USE: To provide a detailed description of the Contractor’s phase-in approach for transitioning Agency-wide Contract Closeout and Procurement Support Services from incumbent contractor(s) to the new Agency-wide Contract Closeout and Procurement Support Services Contract.

8. OPR: XD-042 9. DM: XD-042

10. DISTRIBUTION: Administrative Contracting Officer.

11. INITIAL SUBMISSION: Due with proposal submission.

12. SUBMISSION FREQUENCY: Once.

13. REMARKS: None.

14. INTERRELATIONSHIP: PWS Section 3.5, Reporting Deliverables

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Phase-In Plan describes in detail the Contractor’s plan for transitioning closeout and procurement support services from incumbent contractor(s) to the new Agency-wide Acquisition and Contract Closeout Support Services.

15.3 CONTENTS: The Phase-in Plan shall provide a description of the Contractor’s approach for transitioning closeout and procurement support services from incumbent contractor(s) to the new Agency-wide Contract Closeout and Procurement Support Services contract. The plan and integrated schedule shall clearly identify critical tasks, duration, key milestones, responsible parties, associated risks, and risk mitigation strategies.

15.4 FORMAT: Contractor format is acceptable following guidelines in 15.3.

15.5 MAINTENANCE: Changes shall be incorporated by complete reissue. Update as required to maintain current with program changes.

7. DESCRIPTION/USE: To provide copies of non-disclosure agreements for all employees.

8. OPR: XD-042 9. DM: XD-042

10. DISTRIBUTION: Administrative Contracting Officer.

11. INITIAL SUBMISSION: Five days after employee begins work on the contract/FFP/FFP-LOE Task Order.

12. SUBMISSION FREQUENCY: As required.

13. REMARKS: None.

14. INTERRELATIONSHIP: PWS, Section 4.5, Reporting Deliverables; Section 4.3 Standards of Conduct, NFS 1852.237-72 Access to Sensitive Access to Sensitive Information,and NFS 1852.237-73, Release of Sensitive Information.

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: All contractor personnel shall be required to sign non-disclosure agreements prior to starting work and may be required to sign activity-specific non-disclosure agreements before working on a particularly sensitive project.

15.2 APPLICABLE DOCUMENTS: None

15.3 CONTENTS: Transmittal letter plus copies of signed non-disclosure forms.

15.4 FORMAT: Contractor format is acceptable

15.5 MAINTENANCE: None required.