ATT B - DRDs - Draft.pdf

ATTACHMENT B

NASA CONSOLIDATED APPLICATIONS AND

PLATFORM SERVICES (NCAPS)

DATA REQUIREMENTS LIST

AND

DATA REQUIREMENTS DESCRIPTIONS

RFP 80TECH22R0002

CONTRACT #TBD

DATE: TBD

Attachment B

80TECH22R0002

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.

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.

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.

Interrelationships: (Identify Statement of Work/Performance Work Statement (SOW/PWS) references, contract line item number (CLIN) references, clauses and/or provisions numbers)

Contract Data Requirements List

DRD

No.

DRD

Type

DRD Title OPR

NCAPS-CD CD – Contractual Data CD-001 3 Technology Reports Engineering CD-002 3 Deliverable Products and Services (DPS) Report OCIO NCAPS-LS LS – Logistics Support LS-001 1 Government Property Management Plan Center Operations LS-002 3 Financial Reporting Contractor-Held Property Center Operations NCAPS-MA MA - Management MA-001 1 Contract Management Plan OCIO MA-002 1 Contract Phase-In Plan OCIO MA-003 2 Cybersecurity Support Management Plan OCIO MA-004 1 Information Technology (IT) System Security Plan (SSP) OCIO MA-005 2 Service Asset and Configuration Management (SACM)

Plan

OCIO

MA-006 (RESERVED)

MA-007 (RESERVED)

MA-008 (RESERVED)

MA-009 (RESERVED)

MA-010 2 IT Service Continuity Management (ITSCM) Plan OCIO

MA-011 (RESERVED)

MA-012 3 NASA Enterprise Service Catalog Data

Requirements

OCIO

MA-013 3 Problem Documentation OCIO MA-014 1/2/3 Documentation OCIO

MA-015 (RESERVED)

MA-016 2 Fixed Price Service Delivery Standards and Metrics Report OCIO MA-017 2 Cost Reports OCIO MA-018 2/3 Export Control Plan and Reports OCIO MA-019 3 Financial Management Report (533M) Chief Financial

Office MA-020 3 Supplemental 533 Variance Report Chief Financial

Officer

MA-021 (RESERVED)

MA-022 2 Corporate Target Architecture (CTA) and 5-Year

Service Line Plans Annual Report

OCIO

MA-023 3 Organizational Conflicts of Interest (OCI) Plan Office of Procurement

MA-024 3 NCAPS Monthly Status Review Report OCIO

MA-025 (RESERVED)

MA-026 2 Re-procurement Data Package Office of Procurement

MA-027 (RESERVED)

MA-028 2 WYE Reports OCIO MA-029 2 Small Business Subcontracting Plan Office of Procurement MA-030 2 Total Compensation Plan Office of Procurement MA-031 2 Notification of Potential Labor Dispute and

Contingency Strike Plan Office of Procurement

MA-032 1 Close-out Plan Office of Procurement MA-033 2 Supplemental FFP Invoicing Data OCIO MA-034 1 Commercial IT Authorizations Report OCIO MA-035 2 NCAPS Systems Readiness Report OCIO

MA-036 (RESERVED)

MA-037 3 TBM Reporting OCIO MA-038 3 Diversity, Equity, Inclusion, and Accessibility (DEIA) Plan OP NCAPS-SA SA - Safety SA-001 1 Safety, Health, and Environmental (SHE) Plan Office of Safety

And Mission Assurance

SA-002 3 Mishap and Safety Statistics Reports Office of Safety And Mission Assurance

SA-003 3 Environmental and Energy Consuming Product Compliance Reports

Office of Center Operations

NCAPS-RM RM – Reliability and Maintainability RM-001 1 Operability/Maintainability Plan OCIO NCAPS-QE QE – Quality Engineering QE-001 1 Quality Plan OCIO QE-002 1 Innovation Plan and Reports OCIO QE-003 1 Software Engineering Quality Plan OCIO

1. DRD Title: Technology Reports

2. DRD No.: CD-001 3. Data Type: 3 4. OPR: Engineering Directorate

5. Solicitation No.: 80TECH22R0002

6. Contract No.: (Insert contract number)

7. Date Issued: Insert the date the baseline was issued.

8. Date Revised: 9. DRD Category:

Technical ☒ Administrative ☐

S&MA ☐

10. 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. Also, provides NASA with data to review for possible patentable items.

11. Distribution: COR

Initial Submission:

Technology Reporting Plan: Upon Contracting Officer’s request.

Disclosure of Invention and New Technology (NF1679): Within 2 months of identification of reportable item.

Interim NASA New Technology Summary Report (NTSR) Form: 12 months from the effective date of the contract.

Submission Frequency:

Technology Reporting Plan: Upon Contracting Officer’s request.

Disclosure of Invention and New Technology (NF1679): For each reportable item as soon as it occurs or within three months of identification.

Interim NASA NTSR Form: Every 12 months.

Final NASA NTSR Form: Immediately or within three months after completion of contracted work. Final Payment is contingent upon submission of the Final NTSR.

Format: The Disclosure of Invention and New Technology (Including Software) report may use NF1679, Disclosure of Invention and New Technology (Including Software), (latest version) or the online system at:

https://invention.nasa.gov/, or provide sufficient information to meet the reporting requirement.

The interim and final NASA New Technology Summary Reports may use the NTSR Form (Interim or Final whichever is applicable) utilizing the online system at: https://invention.nasa.gov/ or provide sufficient information to meet the reporting requirement.

Interrelationship: PWS Sections 3.Item W, Technical Performance Management, and 5, Innovation Service.

Applicable Documents:

FAR 52.227-11 Patent Rights – Ownership by the Contractor (May 2014) AS modified by NASA

FAR Supplement 1852.227-11 (Apr 2015) NFS 1852.227-70 New Technology - Other Than a Small Business Firm or NonProfit Organization

(Apr 2015)

Scope: The Technology Reports should include sufficient technical detail as is necessary to identify and fully describe a "Reportable Item." Per NFS 1852.227-70, New Technology-Other Than a Small Business Firm or NonProfit Organization, "Reportable Item" means any invention, discovery, improvement, or innovation of the contractor, whether or not the same is or may be patentable or otherwise protectable under Title 35 of the United States Code, conceived or first actually reduced to practice in the performance of any work under this contract or in the performance of any work that is reimbursable under any clause in this contract providing for reimbursement of costs incurred prior to the effective date of this contract.

Contents: The Technology Reports consist of:

a. Disclosure of Invention and New Technology (Including Software): In accordance with NFS

1852.227-70 (e)(2), New Technology, the disclosure to the agency shall be in the form of a written report and shall identify the contract under which the reportable item was made and the inventor(s) or innovator(s). It shall be sufficiently complete in technical detail to convey a clear understanding, to the extent known at the time of the disclosure, of the nature, purpose, operation, and physical, chemical, biological, or electrical characteristics of the reportable item. The disclosure shall also identify any publication, on sale, or public use of any subject invention and whether a manuscript describing such invention has been submitted for publication and, if so, whether it has been accepted for publication at the time of disclosure. In addition, after disclosure to the agency, the contractor shall promptly notify the agency of the acceptance of any manuscript describing a subject invention for publication or of any on sale or public use planned by the contractor for such invention. This reporting requirement may be met by completing NF1679, Disclosure of Invention and New Technology (Including Software), (latest revision) online at: https://invention.nasa.gov/. Use of this form and the online system is preferred; however, if the form is not used the following information should be provided in order to meet the reporting requirement:

1. Descriptive title.

2. Innovator(s) name(s), title(s), phone number(s), and home address(es).

3. Employer when innovation made (name and division).

4. Address (place of performance).

5. Employer status (e.g., Government, college or university, non-profit organization, small business firm, large entity).

6. Origin (e.g., NASA grant number, NASA prime contract number, subcontractor, joint effort, multiple contractor contribution, other).

7. NASA Contracting Officer’s Representative (COR).

8. Contractor/grantee New Technology Representative.

9. Brief abstract providing a general description of the innovation:

(a) Description of the problem or objective that motivated the innovation’s development.

(b) Technically complete and easily understandable description of innovation developed to solve or meet the objective.

(c) Unique or novel features of the innovation and the results or benefits of its application.

(d) Speculation regarding potential commercial applications and points of contact (including names of companies producing or using similar products).

10. Additional documentation.

11. Degree of technological significance (e.g., modification of existing technology, substantial advancement in the art, major breakthrough).

12. State of development (e.g., concept only, design, prototype, modification, production model, used in current work).

13. Patent status.

14. Dates or approximate time period during which this innovation was developed.

15. Previous or contemplated publication or public disclosure including dates.

16. Answers to the following questions (for software only):

(a) Using outsiders to beta-test code? If yes, done under beta-test agreement?

(b) Modifications to this software continue by civil servant and/or contractual agreement?

(c) Previously copyrighted (if so, by whom?)?

(d) Were prior versions distributed (if yes, supply NASA or contractor contract)?

(e) Contains or is based on code owned by a non-federal entity (if yes, has a license for use been obtained?)?

(f) Has the latest version been distributed without restrictions as to use or disclosure for more than one year (if yes, supply date of disclosure)?

17. Name(s) and signature(s) of innovator(s).

Interim NASA NTSR: This report shall consist of a listing of reportable items for the reporting period or certification that there are none. This report shall also contain a list of subcontracts containing a patent rights clause or certification that there were no such subcontracts. Completion of the Interim NTSR shall satisfy this reporting requirement. Use of the form utilizing the online system at https://invention.nasa.gov/ is preferred; however, an alternate format is acceptable provided all required information is provided.

a. Final NASA NTSR: This report shall consist of a comprehensive list of all reportable items for the contract duration or certification that there are none. This report shall also contain a list of subcontracts containing a patent rights clause or certification that there were no such subcontracts.

Completion of the Final NTSR shall satisfy this reporting requirement. Use of the form utilizing the online system at https://invention.nasa.gov/ is preferred; however, an alternate format is acceptable provided all required information is provided.

b. Subcontracts: The contractor shall provide copies of subcontracts containing a patent rights clause upon Contracting Officer’s request.

Remarks: Copies of NF1679 and the NASA NTSR Form (Interim and Final) may be obtained and/or filled out at: https://invention.nasa.gov/.

Maintenance: None required.

1. DRD Title: Deliverable Products and Services (DPS) Report

2. DRD No.: CD-002 3. Data Type: 3 4. OPR: Enterprise Business Management Office (EBMO)

Technical ☒ Administrative ☐

S&MA ☐

10. Description/Use: To provide the Government oversight on the quantities of products and services. COR will solicit Technical Monitors review for oversight input.

11. Distribution: CO; COR; TM; Business Office

Initial Submission: The contractor shall provide the DPS report no later than 5 calendar days after the close of the first reporting period which ends on the last calendar day of the first month.

Submission Frequency: The Contractor shall provide the DPS report no later than 5 calendar days after the close of each reporting period which ends on the last calendar day of each month.

Format:

a. The Summary Report shall include at a minimum, the following fields:

1. Catalog ID

2. Catalog Description

3. DPS Name

4. DPS Units of Measure

5. FY Target

6. Current Month Consumed

7. YTD Cumulative

8. Remaining Balance

9. Remaining %

10. Notes

b. The Detail Report shall include at a minimum, the following fields:

1. Catalog ID

2. Catalog Description

3. DPS Name

4. Service #

5. Work Order #

6. Work Order Description

7. Requestor

8. Requestor Org. Code

9. Final Approved Date by Government

10. Actual Finish Date

11. # DPS Consumed

12. Notes

Interrelationship: PWS Section 2.1, L-K, Program Management, Applicable Documents: N/A.

Scope: All Catalog and Cost items that have a defined DPS.

Contents: Monthly DPS activity report accurately reflecting the quantities of products and services delivered during the period consistent with the items specified in ATT P, Deliverable Products and Services (DPS).

Remarks:

Government sample template

Deliverable Products and Services (DPS) Summary Report Template

Catalog

ID

Catalog Description

DPS

Name

DPS Units of Measure

FY

Target

Current Month Consumed

YTD

Cumulative

Remaining Balance

Remaining % Notes

Deliverable Products and Services (DPS) Detailed Report Template

Catalog

ID

Catalog Description

DPS

Name

Service

Work Order

Work Order Description Requestor Requestor

Org. Code

Final Approved Date by

Government

Actual Finish Date

# DPS

Consumed Notes

Maintenance: Changes shall be incorporated by complete reissue.

1. DRD Title: Government Property Management Plan (PMP)

2. DRD No.: LS-001 3. Data Type: 1 4. OPR: EBMO, Center Operations

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: To describe the method of administering and controlling Government personal property and submitting proposed property manager qualifications.

11. Distribution: Cognizant Property Administrator; COR

Initial Submission: The Offeror(s)/Contractors will be notified by the Contracting Officer when the PMP submittal is due.

Submission Frequency: Final Submission: Due 30 calendar days after contract award.

Format: Contractor format is acceptable.

Interrelationship: PWS Sections 2.7.1, Logistics, Property/Inventory Management;

Applicable Documents:

FAR 52.245-1 Government Property FAR 52.245-2 Government Property Installation Operation Services (Apr 2012) NFS 1852.245-70 Contractor Requests for Government Furnished Property (Aug 2015) Alt I (Aug 2015) NFS 1852.245-71 Installation Accountable Government Property (Jun 2018) Alt I (Jan 2011) NFS 1852.245-72 Liability for Government Property Furnished for Repair or Other Services (Jan 2011) NFS 1852.245-73 Financial Reporting of NASA Property in the Custody of Contractors (Jan 2017) NFS 1852.245-74 Identification and Marking of Government Equipment (Jan 2011) NFS 1852.245-75 Property Management Changes (Jan 2011) NFS 1852.245-77 List of Government Property Furnished Pursuant to FAR 52.245-2 (Jan 2011) NFS 1852.245-78 Physical Inventory of Capital Personal Property (Aug 2015) NFS 1852.245-82 Occupancy Management Requirements (Sep 2017) NPR 4100.1 NASA Supply Support and Material Management NPR 4200.1 NASA Equipment Management Procedural Requirements NPR 4300.1 NASA Personal Property Disposal Procedural Requirements NPR 4500.1 NASA Administration of Property in the Custody of Contractors

Scope: The Government Property Management Plan defines the Contractor's use, maintenance, repair, protection, and preservation of Government personal property. It shall describe the Contractor's approach to receiving, handling, stocking, maintaining, protecting and issuing Government property (equipment and material). The Plan should include interaction and Department/ Office responsibilities. The Contractor shall submit to the delegated Government Property Administrator (GPA) detailed supplemental property procedures, which are separate from the Property Management Plan, within 60 calendar days after the contract start date.

The Contractors submitting an initial Property Management Plan as part of their reply to the Request for Proposal in accordance with Contracting Officer direction, will also submit proposed property manager qualifications and experience as specified below.

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

2. Periodic internal reviews, surveillances, self-assessments, and audits

3. Written procedures

b. Acquisition of Property

1. Acquisition authority

2. Classification of property

c. Receipt of Government Property

1. Receiving

2. Identification

d. Records of Government Property

1. Physical Inventory

2. Subcontractor Control

i. Flow down of property clauses to subcontractors

e. Reports

1. Loss, Theft, Damage, Destruction reports

2. Physical Inventory reports

3. Audits and self-assessment reports

4. Corrective Action reports

f. Relief of Stewardship Responsibility and Liability

1. Loss, Theft, Damage, Destruction of property

2. Consumed property

3. Delivered property

4. Contractor Inventory Disposal of property

i. In-house screening of excess

ii. Disclosure of excess

g. Abandonment of Government property (if directed by the Government)

h. Utilizing Government Property

1. Utilization

2. Consumption

3. Movement

4. Storage

i. Maintenance

1. Preventive maintenance

2. Rehabilitation

3. Calibration

j. Property Closeout

1. Screening for further use

2. Final physical inventory

3. Transfers off the contract

4. Final NASA Form 1018

k. Reconcile Contractor Records with NASA Financial Property Records [NASA Form 1018 and the Contractor-Held Asset Tracking System (CHATS) if applicable]

l. Center-Unique Considerations (as they arise or known now)

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.

MANAGEMENT QUALIFICATIONS/EXPERIENCE:

a. The Offeror/Contractor shall specify the name and the qualifications of the proposed property manager.

1. List the Federal agencies or departments supported in managing Government property and the corresponding number of years of experience.

2. List completed personal property management training courses.

3. Specify the level of professional property management certification obtained by the proposed property manager.

4. List professional personal property management organizations in which the proposed property manager has an active current membership.

b. This qualification data shall be a one-time submittal from the Offerors with their initial Property

Management Plan (PMP) when the plan is requested by the Contracting Officer. Insert that data as a separate tab after that PMP. This qualification data shall be excluded from the final PMP from the awarded Contractor.

1. DRD Title: Financial Reporting Contractor-Held Property

2. DRD No.: LS-002 3. Data Type: 3 4. OPR: Center Operations

Administrative ☐

S&MA ☐

10. Description/Use: Report NASA Property in the Custody of Contractors on both a monthly and annual basis, as required.

11. Distribution:

a. NF 1018 reports shall be electronically distributed through NF 1018 Electronic Submission System (NESS), unless otherwise indicated by the JSC IPO.

b. The Monthly Property Financial Reports are electronically distributed through CHATS.

c. Cognizant Property Administrator; COR

Initial Submission: See submission frequency.

Submission Frequency:

a. The Annual Property Reporting via NASA Form (NF) 1018 is due in accordance with NFS 1852.245- 73(c)(1).

b. Submission of a Final NF 1018 shall be in accordance with NFS 1852.245-73(d).

c. Submission of Monthly Property Financial Reporting (also known as Contractor-Held Asset Tracking

System (CHATS) Reporting) is required per NFS 1852.245-73 (c)(3).

d. A Final CHATS report shall be submitted per the CHATS user’s manual.

e. All reports shall be submitted electronically.

Format:

a. Annual Property NF 1018 reports shall be submitted using the NF 1018 Electronic Submission System (NESS) or other format supplied by NASA.

b. Monthly Property Financial Reports shall be submitted using the CHATS (https://chats.nasa.gov) using the format described in the CHATS user's manual.

Interrelationship: LS-001, Government Property Management Plan

NFS 1845.7101 Forms Preparation NFS 1852.245-73 Financial Reporting of NASA Property in the Custody of Contractors (Jan 2017)

Scope:

Contents: NF 1018 Reports

a. The NF1018 report provides annual summary-level property management and financial data on Government-furnished and contractor-acquired NASA property.

b. The NF1018 shall be completed in accordance with NFS Subpart 1845.7101, NFS 1852.245-73, and any supplemental guidance provided by NASA.

c. Contractors shall report all NASA-owned property in US dollars, regardless of location.

d. Negative or zero reports are required.

e. Adjustments to the 1018 shall be thoroughly explained in the 1018 “Comments” section and must be approved by the JSC Industrial Property Officer (IPO) prior to submittal of the report, after first being coordinated with the cognizant Government Property Administrator (GPA).

f. Entries in Type of Deletion 21 "h. OTHER" must be explained in detail in the “Comments” section.

g. Entries should not be placed in Type of Deletion 21 "d" or "e" since they should be reflected in "c”.

h. The 1018 report consists of two pages; a Summary first page and a Deletions second page. Both must be accurately completed for submittal.

Monthly Property Financial Reports The Monthly Property Financial Reports shall be completed in accordance with the CHATS user’s manual (https://epss.nasa.gov/gm/folder-1.11.1123762?mode=EU&primaryCSH=chats) and any supplemental guidance provided by NASA.

a. The Contractor shall request that the JSC Contractor Held Property Accountant in LF3/Property, Cost, and Reporting Branch add contracts meeting the requirement for monthly property financial reporting to the CHATS. The contractor shall also request access to the CHATS via the NASA Account Management System (NAMS).

b. Monthly Property Financial Reports are required with item level supporting data. This data shall be submitted for all items with an acquisition cost of $500,000 or more, in the contractor's and its subcontractors' possession, in the following classifications: real property, equipment, special test equipment, special tooling, and agency peculiar property (if applicable). Monthly reporting is not required for property in the above classifications with an acquisition cost under $500,000.

Monthly data shall also be submitted for items of any acquisition cost in the classifications of materials and contract work-in-process (WIP). Itemized monthly data is required for material line items of $500,000 and over. Itemized monthly line item data is required for WIP. Summary monthly data is required for material items under $500,000. Other software (not integrated into a piece of Government property that is necessary to operate that item) shall be considered an individual reporting item if the acquisition cost is $1,000,000 or more an expected to have a useful life of 2 years or more.

c. Acquisition costs shall be developed using actual costs to the greatest extent possible, especially costs directly related to fabrication such as labor and materials. Supporting documentation shall be maintained and available for all amounts reported, including any amounts developed using estimating techniques.

d. All Adjustments shall be thoroughly explained and directly related to a specific fiscal year. If the fiscal year cannot be determined, the default shall be the previous fiscal year. Adjustments to the monthly report must be coordinated with JSC Finance.

e. Annual Property NF 1018 reports shall be submitted using the NF 1018 Electronic Submission System (NESS) or other format supplied by NASA.

f. Monthly Property Financial Reports shall submitted using the CHATS (https://chats.nasa.gov) using the format described in the CHATS user's manual.

Remarks:

Maintenance: Revisions to the NF 1018 data shall be coordinated with the cognizant Government PA.

Revisions to the Monthly Property Financial Reports shall be coordinated with the JSC Contractor Held Property Accountant in LF3/Property, Cost, and Reporting Branch.

1. DRD Title: Contract Management Plan

2. DRD No.: MA-001 3. Data Type: 1 4. OPR: EBMO

Technical ☐Administrative ☐

S&MA ☐

10. Description/Use: To document the Contractor's overall contract management approach and organization for accomplishing the contract requirements.

11. Distribution: CO; COR; Electronic submission to Government-provided database

Initial Submission: Outline of anticipated Management Plan with proposal; Preliminary draft of plan 30 calendar days after contract award.

Submission Frequency: Final 30 calendar days after effective date of contract. Submit revisions for Government approval after any major change in management organization and approach.

Format: Contractor format is acceptable (not to exceed twenty (20) pages in Times New Roman 12 font, paper size 8-1/2 x 11).

Interrelationship: PWS Section 2.1, B, Program Management;

Applicable Documents: None

Scope: The Management Plan describes the contractor's summary concept plans, practices, and approach for accomplishing the requirements set forth in the contract, i.e., managing and controlling tasks, experimental work, and management interfaces. The plan shall be in such detail as necessary to convey the Contractor's internal procedures.

Contents: The Management Plan shall include the following:

a. The contractor shall describe the overall proposed contract management approach, strategies, policies, processes for work planning, subcontractor management, and indirect cost management including any efficiencies proposed. This description shall include a description of the organizational structure and elements, including a chart depicting the organization and the overall rationale for this approach.

b. Describe the management relationships between the contractor’s key personnel and associated NASA personnel, including communication channels, lines of authority (including the line of succession if Program Manager is unavailable), reporting relationships, and responsibilities of all organizational elements. Include in this discussion any subcontractors, team members, or joint venture partners, to illustrate their relationships within the structure or between the organizational elements and any other subcontractors, team members, or joint venture partners. Describe the reporting responsibilities of the Program Manager to corporate management and the relationship between the Program Manager and the prime’s corporate management as well as the management of any subcontractors, team members, or joint venture partners. Describe the overall authority of the Program Manager to make decisions independent of corporate management.

c. Recruitment and employment methods and policies including any special provisions your company has regarding hiring incumbent employees. Strategy to ensure personnel will maintain the minimum qualification standards described in the Standard Labor Category guidelines.

d. Approach to providing flexible workforce planning. Include discussion on recruiting; communication of promotion opportunities; retention of personnel; and the effects on management, subcontractors, continuity and quality of services, and other factors resulting from changes in staffing levels.

e. Describe the staffing location plans, including lease arrangements, for the contractor’s off-site facilities including a discussion of the on-site and off-site approach. Discuss any other issues related to logistics management.

f. A description of risks anticipated in successful performance of the SOW requirements. Include the decision to accept, mitigate, or other action for each risk and include the rationale for each.

g. The methods to ensure timely delivery of quality services. Describe how the contractor will ensure the Government will receive the services ordered by providing the method, level and frequency of internal surveillance. Describe how the management policies, procedures, and techniques are monitored to ensure their effectiveness and facilitate continuous improvement. Describe the methods of identifying deficiencies and plans for correcting deficiencies. Describe the process for Management reviews/status reviews to NASA management.

h. Describe the process for the coordination and execution of all contract technical and administrative tasks, and how the contractor’s technical personnel (individuals and line managers) will interact with NASA line management. Process of setting goals and establishing policies, practices, procedures, and organizational structure to support the NASA CIO and NASA IT Governance processes, as defined in NPR 2800.1E, Managing Information Technology.

i. Process of setting goals and establishing policies, practices, procedures, and organizational structure to support accomplishment of NCAPS objectives. As a minimum, this includes both transition and transformation management.

j. Process for identification and resolution of as a minimum problems, issues, and weaknesses.

k. Discuss strategies/approach to ensure that the contractor can facilitate a proactive and efficient close out of the contract at contract end in as short a time as practicable including but not limited to possible use of the Quick Closeout procedures of FAR 42.708, NFS 1842.708 and 1842.708-70.

Remarks: This is the contractor’s summary of their management approach and its relationship to their organization.

Maintenance: The Contractor may revise the CMP at any time or at the direction of the Contracting Officer.

Revisions to the CMP are subject to Contracting Officer review and approval. Changes shall be incorporated as required by or complete reissue. Note: Upon Contract Award, the Contractor’s Contract Management Plan becomes a part of the contract.

1. DRD Title: Contract Phase-In Plan

2. DRD No.: MA-002 3. Data Type: 1 4. OPR: EBMO

Administrative ☐

S&MA ☐

10. Description/Use: To describe activities planned to transition from the processes and services as defined at contract start to those accepted by the Government during the proposal and contract award process.

11. Distribution: CO; COR

Initial Submission: Preliminary draft due with initial proposal.

Submission Frequency: Final Plan due 7 calendar days prior to Phase-In. Revised for significant changes that may be required during the implementation of the specific changes in processes and services.

Format: Submitted electronically; MS Word

Interrelationship: PWS Section 2.8, B, Contract Phase-In Management

Applicable Documents: None.

Scope: This plan defines tasks, schedule, responsibilities, and agreements for both the contractor and the Government, necessary to transition from the processes and services as defined at contract start to those accepted by the Government during the proposal and contract award process. The results of the accepted processes and services shall be contained in the Model Contract. The total time allocated for the implementation of the transition of processes and services shall not exceed 90 calendar days from phase-in start.

Contents: The Phase-in Plan shall address, as a minimum, the following:

a. Describe in detail the plan for maintaining continuous and efficient operations at NASA. Describe how you will work with incumbent Contractors and NASA, including resources and interfaces expected from each to ensure an effective transition and continuous service.

b. Provide an innovative phase-in schedule which will accomplish all proposed phase-in steps/milestones within the 90-day phase-in period, while minimizing cost and maximizing efficiency.

c. Include the personnel responsible for the steps/milestones. Describe your approach for how you will implement the schedule.

d. Provide details for initial staffing and training of personnel, including the percentage of incumbent personnel that you plan to hire. Discuss proposed key personnel, if applicable and demonstrate that the key personnel are committed to employment prior to start of contract.

e. Address the office space that is required for phase-in, beyond what is to be provided by the Government, if any.

f. Approach for ensuring completion of badging requirements and personnel security clearances to ensure employees are cleared for access to NASA and associated facilities, as required, prior to start of the contract.

g. Describes how an inventory will be performed with the Incumbent Contractor of all records that will be transitioned. Records transition shall be completed at contract start.

h. Describe your approach and risk mitigation strategies to identify any requirements for application or system connectivity or integration with NASA.

i. Identify the risks associated with your plan and ways to mitigate those risks.

Remarks: None

1. DRD Title: Cybersecurity Support Management Plan

2. DRD No.: MA-003 3. Data Type: 2 4. OPR: EBMO

☐Administrative ☐

S&MA ☐

10. Description/Use: To describe the Contractor’s methodology for managing all aspects of Cybersecurity support, including addressing the cross-functional and service-specific Cybersecurity requirements.

11. Distribution: CO; COR

Initial Submission: 60 calendar days after effective date of the contract.

Submission Frequency: One time; revise as required.

Format: Contractor format is acceptable with NASA approval.

Interrelationship: PWS Section 4, Cybersecurity Services Overview

Applicable Documents: None.

Scope: The Cybersecurity Support Management Plan provides the Contractor’s proposed management approach for meeting cross-functional and service-specific Cybersecurity requirements.

Contents: The Cybersecurity Support Management Plan shall include, at a minimum, the following:

a. Contractor’s Cybersecurity support POC(s) and roles and responsibilities for the POC(s).

b. Proposed grouping of information systems supported under the contract into IT System Security

Plans (IT-SSP) in the NASA system of record in accordance with NASA policy and FIPS 199 security category of each information system.

c. Process for meeting security authorization requirements, including development and maintenance of IT-SSPs, implementation and validation of controls, remediation, authorization, continuous monitoring, etc.

d. Processes for addressing all applicable Cybersecurity requirements, including patch requirements and mitigation, maintaining secure system configurations, patch/configuration management and reporting, malware protection.

e. Process for information security incident identification and response, including coordination with NASA Security Operations Center (SOC) and CISO, Incident Response Managers.

f. Process for providing required data to the NASA SOC.

g. Process for ensuring that Contractor employees meet Cybersecurity and Privacy Program requirements, such as IT Security Awareness training, qualifications for system administrators, security clearance requirements, and others with elevated privileges, etc., and that Contractor employees are knowledgeable of NASA Cybersecurity policies and procedures.

Remarks: None.

Maintenance: Update as required to maintain current with program changes.

1. DRD Title: Information Technology (IT) System Security Plan (SSP)

2. DRD No.: MA-004 3. Data Type: 1 4. OPR: EBMO

☐Administrative ☐

S&MA ☐

10. Description/Use: To provide the Contractor’s compliance with the Cybersecurity requirements in NFS 1852-204-76, Security Requirements for Unclassified Information Technology Resources, and any additions/ augmentations described in NPR 2810.1E, Security of Information Technology and NASA Cybersecurity policy, standards, and handbooks. These documents will be used as part of the NASA Cybersecurity certification and accreditation process and to identify IT system inventories and appropriate Contractor Cybersecurity support points of contact.

11. Distribution: CO; COR

Initial Submission: As required by the NASA Certification and Accreditation (C&A) process, in coordination with the information system’s NASA authorizing official and Cybersecurity Service Line, Office of Cyber Protection.

Submission Frequency: The IT SSP shall be reviewed and updated in the NASA system of record on a continual basis to include any contractor personnel point of contact (POC) information changes. The SSP will be resubmitted for ATO at least annually and/or after any significant changes to the IT System. Updated copies shall be documented in the NASA system of record, upon any significant changes or annually.

Format: The Contractor shall use the format as defined in the Agency’s A&A tool, Risk Information Security Compliance System (RISCS), and following guidelines listed in Section 4.5, I

Interrelationship: As applicable throughout the PWS Section 4.5.

FIPS 200 Minimum Security Requirements for Federal Information and Information Systems FIPS 199 Standards for Security Categorization of Federal Information and Information Systems NFS 1852.204-76 Security Requirements for Unclassified Information Technology Resources NPR 2810.1A Security of Information Technology NIST SP 800-18 Guide for Developing Security Plans for Federal Information Systems NIST SP 800-30 Guide for Conducting Risk Assessments NIST SP 800-34 Contingency Planning Guide for Information Systems NIST SP 800-61 Computer Security Incident Handling Guide NIST SP 800-37 Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy ITS-HBK 2810.02.02-E Security Assessment and Authorization: Information System Security Assessment and Authorization Process ITS-HBK 2810.02-05 Security Assessment and Authorization External Systems

ITS-HBK 2810.02-08 Security Assessment and Authorization: Plan of Action Milestones IT-SOP 2810.02-01 Internal Information Assurance (A&A) Review NIST SP 800-53 Security and Privacy Controls for Federal Information Systems and Organizations NIST SP 800-53A Assessing Security and Privacy Controls in Federal Information Systems and Organizations: Building Effective Assessment Plans

Scope: The Information Technology (IT) System Security Plan includes a description of the IT system, network and data flow diagrams, ports protocols and services used, hardware and software lists and its implementation of security controls, risk assessment, self-assessment of security plans, and contingency plan, in compliance with NIST SP 800-18, Guide for Developing Security Plans for Federal Information Systems, and NIST SP 800-53, Security and Privacy Controls for Federal Information Systems and Organizations and NASA CSPP policy, standards and handbooks.

Contents: The Information Technology (IT) System Security Plan shall include the following:

a. The IT System Security Plan shall be written in accordance with NFS 1852.204-76, Security Requirements for Unclassified Information Technology Resources, NASA ITS Handbooks, and NIST SP 800-18, Guide for Developing Security Plans for Federal Information Systems, and following the process defined in NIST SP 800-37, Risk Management Framework for Information Systems and Organizations:

A System Life Cycle Approach for Security and Privacy. It should also address all the required security controls defined in the latest revision of the NIST SP 800-53, Security and Privacy Controls for Federal Information Systems and Organizations, based upon the security categorization (per FIPS 199, Standards for Security Categorization of Federal Information and Information Systems).

b. Risk Assessment: The IT Risk Assessment report shall be written in accordance with NFS 1852.204-76, Security Requirements for Unclassified Information Technology Resources, and following the guidelines of NIST SP 800-30, Guide for Conducting Risk Assessments.

c. Self-Assessment: The self-assessment shall be conducted and provided in the format defined by NIST SP 800-53A, Assessing Security and Privacy Controls in Federal Information Systems and Organizations: Building Effective Assessment Plans.

d. Contingency Plan: The IT Contingency Plan shall be written in accordance with NASA policy as well as NFS 1852.204-76, Security Requirements for Unclassified Information Technology Resources, and following the guidelines of NIST SP 800-34, Contingency Planning Guide for Information Systems.

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

1. DRD Title: Service Asset and Configuration Management (SACM) Plan

2. DRD No.: MA-005 3. Data Type: 2 4. OPR: EBMO

Administrative ☐

S&MA ☐

10. Description/Use: To describe the Contractor’s approach for managing and protecting the integrity of service assets and configuration items.

11. Distribution: Electronic submission to Government-provided database; CO; COR

Initial Submission: Draft 60 calendar days after effective date of the contract.

Submission Frequency: Preliminary 120 calendar days after effective date of the contract; Baseline 180 calendar days after effective date of the contract; update as required.

Format: Contractor format is acceptable.

Interrelationship: PWS 2.17 A Configuration Management.

Applicable Documents: None.

Scope: The Service Asset and Configuration Management (SACM) Plan provides the Contractor’s proposed management approach for incorporating, managing, and protecting the Agency integrity of Service Assets and Configuration Items in accordance with NASA policies, procedures and configuration baselines as prescribed by

CSET.

Contents: The Service Asset and Configuration Management (SACM) Plan shall include, at a minimum, the following:

a. Process for identifying and maintaining Configuration Items/Service Assets (including relevant tools, attributes, relationships, baselines and detail, and status and changes thereto) in NASA’s system of record.

b. Process for verifying and auditing Configuration Items and Service Assets.

c. Process for implementing corrective actions to resolve Configuration Item/Service Asset discrepancies.

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

1. DRD Title: Information Technology (IT) Service Continuity Management (SCM) Plan

2. DRD No.: MA-010 3. Data Type: 2 4. OPR: OCIO

Administrative ☐

S&MA ☐

10. Description/Use: To describe the Contractor’s method for establishing and maintaining ongoing recovery capability for required Applications, Platforms and their components.

11. Distribution: CO; COR

Initial Submission: Draft 60 calendar days after effective date of the contract.

Submission Frequency: Preliminary 120 calendar days after effective date of the contract; baseline 180 calendar days after effective date of the contract; update as required.

Format: Contractor format is acceptable with NASA approval.

Interrelationship: PWS Sections 5 - 13.

Applicable Documents: None.

Scope: The Information Technology (IT) Service Continuity Management (SCM) Plan provides the Contractor’s proposed management approach for establishing and maintaining ongoing recovery capability for IT services and their components in accordance FISMA compliance requirements.

Contents: The Information Technology (IT) Service Continuity Management (SCM) Plan shall include, at a minimum, the following:

a. Process for managing product and service continuity.

b. Process for notifying the Enterprise Service Desk regarding potential issues.

c. Process for identifying contingency options and impact mitigation actions and strategies.

d. Process for enabling the effective identification, analysis, and management of risk responses.

e. Process for development, production, testing, maintenance, and training of the plan.

f. Process, including criteria, for invoking the plan, executing recovery plans, restoring service to normal operation, and leading and/or coordinating recovery efforts.

g. Process for testing and documenting results of disaster recovery testing.

h. Process for identifying required contingency services that impact the required IT services.

Maintenance: Changes shall be incorporated by complete reissue. Update at least annually or quarterly based on system categorization to maintain current with program changes and requirements.

1. DRD Title: NASA Enterprise Service Catalog Data Requirements

2. DRD No.: MA-012 3. Data Type: 1 4. OPR: OCIO

Administrative ☐

S&MA ☐

10. Description/Use: The NASA Enterprise Service Catalog (ESC) is the authoritative source for all OCIO IT Service offerings and associated service data attributes.

11. Distribution: COR

Initial Submission: 60 calendar days after effective date of the contract.

Submission Frequency: One time; revise as required.

Format: Defined by ServiceNow user interface.

Interrelationship: PWS Sections 5 - 13.

Applicable Documents: None

Scope: The NASA ESC data requirements encompass a broad range of information necessary to describe the various Services offerings of the Enterprise Services contracts.

Contents: The NASA ESC data requirements shall include, at a minimum, the following:

a. A short description of each service offering.

b. Service Components data to the granularity level required for the ESC entry to differentiate components and enable the ESD/ESRS to identify the service provider components and thereby properly display for selection by catalog users the Service, System or component.

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

1. DRD Title: Problem Documentation

2. DRD No.: MA-013 3. Data Type: 3 4. OPR: OCIO

Administrative ☐

S&MA ☐

10. Description/Use: To provide documentation, scripts, and procedures for the…