80TECH24Q0023 Attachment B Contract Data Requirements List (00003).pdf

Attachment B RFQ 80TECH24Q0023 (00003)

ATTACHMENT B

ATTACHMENT B

CONTRACT DATA REQUIREMENTS LIST

National Aeronautics and Space Administration Information Technology Procurement Office

DOCUMENT CHANGE LOG

DRD

No.

DRD Title Revision Date

Attachment B RFQ 80TECH24Q0023(00003)

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

Electronic deliverables shall be printable. Data deliverables shall be delivered to NASA in the format specified below unless a specific format is required by a DRD. Data submittals shall consist of a single Adobe Acrobat PDF file and the native format electronic file(s). The preferred native formats include Microsoft Word, Excel, or PowerPoint, as appropriate.

Transmittal Data shall be transmitted to NASA by email.

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.

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

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:

Revisions of documentation previously submitted may be accomplished either by individual page revision or by a complete reissue of the document.

A document shall be completely reissued when, in the opinion of the contractor and/or NASA, the document has been revised to the extent that it is unusable in its present state, or when directed by the CO. When complete reissues are made, the entire contents of the document shall be brought up to date and shall incorporate revised pages. All revisions shall be recorded. A revision log shall identify complete reissues except for periodic reports and documents which are complete within themselves as final.

Individual page revisions shall be made as deemed necessary by the contractor or as directed by the CO.

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

All revised pages shall be identified by a revision identifier and a new date. Each document shall contain a log of revised pages that identify the revision status of each page with the revision symbol. This list shall follow the table of contents in each document. The line or lines revised on a given page shall be designated using vertical line in the margin of the page, and the change authority shall be indicated adjacent to the change.

CDRL/DRD MAINTENANCE PROCEDURES

NASA-Initiated Change: New and/or revised data requirements shall be incorporated by contract modification to which the new or revised portion shall be appended. The contractor shall notify the CO in the event a deliverable data requirement is imposed and is not covered by a DRD, or when a DRD is changed by a contract modification and for which no revision is appended.

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

Contract Data Requirements List

DRD

No.

DRD

Type

DRD Title OPR

C.01 1 IT Security Management Plan OP

C.02 3 Property Management Plan (PMP) OP

C.03 1 Master Project Plan JSC/SA4

C.04 3 Weekly Status Reports JSC/SA4

`1. DRD Title: IT Security Management Plan

2. DRD No.: C.01 3. Data Type: 1 4. OPR: OP

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

7. Date Issued: Solicitation Issuance Date

8. Date Revised: N/A 9. DRD Category:

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: To provide Government documentation of the contractor’s methodology for managing all aspects of information security, risk management and safeguards to ensure critical components and NASA IT systems associated with transformational proposals are implemented in accordance with NASA policies and procedures.

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

Initial Submission: Within 30 Days After award effective date.

Submission Frequency: Approved IT Security Management Plans shall be reviewed and updated annually.

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

Interrelationship:

PWS Section 3.1 Technical Requirements, 3.2 Additional Cloud Specific Implementation Requirements, 11.0 Standards, Regulations & Compliance References

Applicable Documents:

NPR 2810.1F, Security of Information and Information Systems NPR 1600.1A, NASA Security Program Procedural Requirements NFS 1804.470, Security Requirements for Unclassified Information Technology (IT) Resources NFS 1852.204-76, Security Requirements for Unclassified Information Technology (IT) Resources M-22-09 Zero Trust Cybersecurity Principles FIPS 140-3, Security Requirements for Cryptographic Modules FIPS 199, Standards for Security Categorization of Federal Information and Information Systems NIST SP 800-37 Rev2 Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy NIST SP 800-61, Computer Security Incident Handling Guide

Scope: The IT Security Plan provides an overview of the security requirements of IT systems and describes the implementation details of the management, operational, and technical security controls in place or planned, and responsibilities and expected behavior of all individuals who access the system

Contents: The IT Security Management Plan shall document the safeguards necessary to ensure sufficient availability, integrity, and confidentiality of that information accessed or managed within the systems and/or applications as well as key and media control. The IT Security Plan shall meet the requirements of the applicable documents in the references noted above and document how the contractor personnel will utilize, in a secure manner commensurate with the sensitivity of the information involved, those Federal computer systems and software applications managed by others. The Plan shall describe the contractor’s processes for implementing information security including personnel background screening, personnel awareness and training, information protection and security incident response.

Remarks: Product shall be compatible with Microsoft Office Suite of software.

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

1. DRD Title: Property Management Plan (PMP)

2. DRD No.: C.02 3. Data Type: 1 4. OPR: OP

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

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

Technical ☐

Administrative ☒

S&MA ☐

10. Description/Use: To describe the method of administering and controlling Government Furnished Property/Equipment/Information (GFP/E/I) as needed for this requirement.

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

Initial Submission: Within 15 calendar days after the GFP/E/I is received.

Submission Frequency: As needed

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

Interrelationship: 52.245-9 Use and Charges (APR 2012), 1852.245-75 Property Management Changes (JAN 2011), 1852.245-76 List of Government Property Furnished Pursuant to FAR 52.245-1. (JAN 2011)

Applicable Documents: Terms and Conditions of Order

Scope: The Government Property Management Plan defines the Contractor's use, protection, and preservation of Government personal property.

Contents:

This plan shall reference those policies and procedures which are part of the Contractor's Property Management System and shall include at a minimum, but not limited to, the following functions/outcomes/activities:

a. Property Management

(1) Voluntary consensus standards, industry-leading practices and standards, customary commercial practices.

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

Maintenance: Changes to the PMP shall be incorporated by change pages or complete reissue after coordination with the Government PA.

1. DRD Title: Master Project Plan

2. DRD No.: C.03 3. Data Type: 1 4. OPR: JSC/SA4

5. Solicitation No.: 80TECH24Q0023

6. Contract No.: TBD

7. Date Issued: Solicitation Issuance Date

8. Date Revised: TBD 9. DRD Category:

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use:

The plan will communicate the contractor’s overall plan for the project and be used as a roadmap for project completion, accounting for schedule, performance, review, milestones, expected travel, and other key components of the overall project. It should be categorized by project phases, including a definition phase, planning phase, and implementation phase, and contain sections containing details/plans for the following at a minimum: Key Project Personnel, Goals and Success Criteria, Communication, Milestones, Risk Management, Current State Assessment, Configuration, Training, Testing and Support, Go-live/System Launch, and Post Go-Live/System Launch Support.

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

Initial Submission: Within 30 days after award effective date

Submission Frequency: As needed.

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

Interrelationship: PWS Section 3.3.2 Master Project Plan, 4.1 Master Project Plan

Applicable Documents: Order Terms and conditions

Scope: The Master Project Plan describes the contractor’s comprehensive approach to completing the project and can be used as a roadmap for project completion, accounting for schedule, performance, review, milestones, expected travel, and other key components of the overall project. It should be categorized by project phases, including a definition phase, planning phase, and implementation phase, and contain sections containing details/plans for the following at a minimum: Key Project Personnel, Goals and Success Criteria, Communication, Milestones, Risk Management, Current State Assessment, Configuration, Training, Testing and Support, Go-live/System Launch, and Post Go-Live/System Launch Support.

Contents: The Master Project Plan shall include the following information at a minimum and be organized by project phases utilizing sections below

1) Key Project Personnel listing with brief description of individual’s experience relevant to this project. No more than half a page per person.

2) Goals and Success Criteria developed with customer input that outlines project goals and jointly defines project success utilizing goal-based criteria.

3) Communication Plan developed with customer that addresses internal and external stakeholder communication needs, reflecting best practices for keeping everyone impacted appropriately informed for the project's lifetime.

4) Milestone Plan including all milestones for the Definition, Planning, and Implementation phases with estimated durations, responsible parties, dependencies, and a target launch date of 7/7/2025.

5) Current State Assessment. The contractor will need to understand the current system state to develop configuration plans.

NASA will provide documentation with supporting diagrams and current system specifications. Stakeholder interviews will be conducted to confirm and supplement the information provided as required. The contractor shall identify any specific needs not already discussed for the Current State Assessment in this section.

6) Configuration Plan based on the NASA provided information, stakeholder interviews, requirements, desired end states, and software configuration support for features and functionalities. This plan will document tasks, durations, resources required, and testing.

7) Comprehensive Training Plan that includes general user and specific role training tracks and classes. Roles include but are not limited to, super-users, systems analysts, technical support analysts, clinical and administrative staff, healthcare providers, and at-the-elbow support for go-live.

-This plan shall include customizing training as appropriate to reflect customizations specific to JSC.

-This plan shall include requirements and recommendations for in-person and remote training for current stakeholders, including remote US and international users.

-This plan shall include training that can be utilized when new staff need to be trained in the future.

8) Go-live/System Launch Plan including all requirements that need to be satisfied before going live receives approval. It will also include user requirements that must be met before allowing system access as well as specific activities for the week before, the day before, and the day of going live. Remote US and international sites should be included.

9) Post Go-live/System Launch support plan specifically for the first and second weeks after go-live/system launch and shall include needs-based reductions in specific areas of support.

Remarks: N/A

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

1. DRD Title: Weekly Status Report

2. DRD No.: C.04 3. Data Type: 1 4. OPR: JSC/SA4

5. Solicitation No.: 80TECH24Q0023

6. Contract No.: TBD

7. Date Issued: Solicitation Issuance Date

8. Date Revised: TBD 9. DRD Category:

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use:

The Weekly Status Report will be utilized to monitor the project. The weekly report shall include, at a minimum, completed and upcoming milestones; significant tasks completed, underway, and upcoming; active and resolved issues; identified risks and their status; matters for management attention and significant decisions made.

11. Distribution: Contracting Officer’s Representative

Initial Submission: Within 5 business days after contract award effective date

Submission Frequency: Every Friday prior to 1200 CST (Thursday prior if Friday is a federal holiday.) Specific time for report submission can be adjusted if agreed upon by contractor and Contracting Officer’s Representative.

Format: Contractor format is acceptable, must be compatible with Microsoft PowerPoint or other agreed upon MS Office product

Interrelationship: PWS Section 4.2 Weekly Status Report

Applicable Documents: N/A

Scope: The Weekly Status Report will be utilized to monitor the project. The weekly report shall include, at a minimum, completed and upcoming milestones; significant tasks completed, underway, and upcoming; active and resolved issues; identified risks and their status; matters for management attention and significant decisions made.

Contents: The weekly report shall include, at a minimum, completed and upcoming milestones; significant tasks completed, underway, and upcoming; active and resolved issues; identified risks and their status; matters for management attention and significant decisions made.

Remarks: N/A

Maintenance: As needed