Attachment J-C Data Requirements List (DRL) and Data Requirements Descriptions (DRD).pdf

Enterprise Multimedia and Integrated Technical

Services (eMITS)

RFP - 80TECH22R0001

Contract: TBD

Data Requirements List (DRL) and

Data Requirements Descriptions (DRD)

Attachment J-C

FEBRUARY 2022

80TECH22R0001

pg. 2

DRD

Line

DRD # Data

Type eMITS DRD Title OPR eMITS-CD

1 1 3 Technology Reports Space Technology Mission Directorate eMITS-LS

2 1 1 Government Property Management Plan Center Operations

3 2 Reserved eMITS-MA

4 1 1 Contract Management Plan OCIO

5 2 1 Contract Phase-In Plan OCIO

6 3 2 Information Security Management Plan OCIO

7 4 1 Information Technology (IT) Security Plan (SSP) and Reports

OCIO

8 5 1 Information Technology (IT) Capital Planning and Investment Control (CPIC)

OCIO

9 6 2 Rough Order of Magnitude (ROM) Estimates OCIO

10 7 1 Annual Work Plan OCIO

11 8 2 Information Technology (IT) Service Continuity Management (SCM) Plan

OCIO

12 9 2 Project Plans OCIO

13 10 2 System Health Management, Reliability/Operability Plan and Report

OCIO

14 11 2 Preventive Maintenance and Obsolescence Plan OCIO

15 12 3 Standard Operating Procedures OCIO

16 13 3 Mission Support Planning Document OCIO

17 14 3 Lessons Learned Documentation and Corrective Actions Report

OCIO

18 15 3 Problem Documentation OCIO

pg. 3

19 16 Reserved OCIO

20 17 3 Financial Management Report OCIO

21 18 2 Cost Reports OCIO

22 19 3 Contractor Self-Assessment report OCIO

23 20 1 Fixed Price Transition Plan (FPTP) OCIO

24 21 3 Contract Management Review (CMR) OCIO

25 22 2 Organizational Conflicts of Interest (OCI) Plan OCIO

26 23 2 Diversity Equity and Inclusion Plan Office of Procurement

27 24 2 Notification of Potential Labor Dispute and Contingency Strike Plan

Office of Procurement

28 25 1 Technology, Innovations, and Process Improvement Plan and Report

OCIO

29 26 1 Contract Close-Out Plan Office of Procurement

30 27 1 eMITS Product and Services Catalog OCIO

31 28 2 Re-procurement Data Package Office of Procurement

32 29 2 Supplemental FFP Invoicing Data OCIO

33 30 2 Commercial IT Authorization Report OCIO eMITS-QE QE – Quality Engineering

34 1 1 Quality Plan Safety and Mission Assurance Office eMITS-RM RM – Reliability and Maintainability

35 1 1 Operability/Maintainability Plan Safety and Mission Assurance Office eMITS -SA

36 1 1 Safety, Healthy, and Environmental (SHE) Plan Safety and Mission Assurance Office

37 2 3 Mishap and Safety Statistics Reports Safety and Mission Assurance Office

38 3 3 Environmental and Energy Consuming Product Compliance Reports

Center Operations

pg. 4

Subject to FAR 52.227-14 Rights in Data-General, Alternate II and Alternate III, as modified by NFS 1852.227-14 Rights in Data-General, 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 this contract. The contractor shall furnish data defined by the DRDs listed on the Data Requirements List (DRL) by category of data. 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) regulation or clause, the regulation shall take precedence over the DPD, per FAR 52.215-33 Order of Precedence. NASA-Owned/Contractor-Held records shall be managed by the contractor in accordance with Title 36 of the Code of Federal Regulations, Chapter XII B, Records Management, and NPD 1440.6I, NASA Records Management Program.

The records shall be organized in accordance with the instructions in NPR 1441.1E, NASA Records Retention Schedules, as applicable. The contractor shall disposition records and non-records in accordance with NPR 1441.1E, NASA Records Retention Schedules, which has been approved by NASA and the National Archives and Records Administration (NARA). All questions on records management issues shall be directed to the Contracting Officer.

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

DESCRIPTION

This document identifies and defines the requirements and data types for information and data required under this contract. The Data Requirement Descriptions (DRDs) define, by an individual Data Requirement (DR), the information and data required for each deliverable document. The data types are used to identify the approval and control required for each DR. The Data Requirements List (DRL) is an index of all the DRs by category. OPR indicates the program office for the respective DRD. DM indicates the document manager or owner.

Documentation submitted pursuant to this clause may incorporate references to other current approved documentation, provided the references are adequate and include such identification elements as title, document number, and approval date (where applicable). However, if the pertinent information is of relatively minor size, the contractor shall incorporate the information itself, in lieu of using a reference. The contractor shall assure that any referenced information is readily available to appropriate users of the submitted document.

DATA TYPES

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

pg. 5

Type 1 That information and documentation which requires NASA approval prior to release. Approved type 1 information and documentation shall be controlled, and deviations from or changes to the concepts, techniques, and/or requirements stated therein shall require NASA approval prior to implementation. All work under this contract covered by approved type 1 documents shall be performed in accordance with those approved documents. The Contracting Officer’s Representative shall have approval authority and shall sign the data prior to its release. Contractually binding documents shall not be implemented nor revised without contractual authorization. In addition, 30 calendar days in advance of the DRD due date the Contractor shall notify the Contracting Officer in writing of their intent to submit a type 1 deliverable marked as proprietary, reference FAR 52.227-14, Rights in Data - General.

Type 2 That information and documentation for which NASA reserves a time-limited right to disapprove, in whole or in part. Type 2 data shall be submitted to NASA for review not less than 30 calendar days prior to its release for use or implementation. The contractor shall clearly identify the release target date in the "submitted for review" transmittal. If the contractor has not received any comment prior to the released target date, the document may be released for appropriate use. Any NASA comment received shall be appropriately dispositioned before the document is to be used. Type 2 data may be approved by NASA prior to its submittal. In addition, 30 calendar days in advance of the DRD due date the Contractor shall notify the Contracting Officer in writing of their intent to submit a type 2 deliverable marked as proprietary, reference FAR 52.227-14, Rights in Data - General.

Type 3 That information and documentation which is provided to NASA for surveillance, information, review, and/or management control. This information does not require formal NASA review and approval. Information in this category would include design solutions, status, and schedule reporting; analyses and test results, handbooks; and other designated lists, reports, etc. Type 3 deliverables shall not contain proprietary information.

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

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

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

pg. 6

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

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

DISTRIBUTION REQUIREMENTS

The contractor shall provide one copy of each DR to the standard distribution list stated in the DRD. Additional distribution shall be made as directed, in writing, by the Contracting Officer.

Data Transmittal Forms shall be used to confirm delivery of electronically resident DR deliverables.

ELECTRONIC FORMAT

DRDs shall be maintained electronically in the contractor's own format, unless a specified format is defined in the DRD. The Government may define specific DRD data format to support the utilization of this data in the Management Information System. “Program Authorized Repository” should always be assumed as the ISS Program’s Electronic Document Management System (EDMS), unless another Program’s repository is specified.

pg. 7

1. DRD Title: Technology Reports

2. DRD No.: CD-01 3. Data Type: 3 4. OPR: Space Technology Mission Directorate

5. Solicitation No.: 80TECH22R0001 6. Contract No.:

7. Date 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: Applicable throughout the PWS

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

pg. 8 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.

pg. 9

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

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

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

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

pg. 10

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

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

5. Solicitation No.: 80TECH22R0001 6. Contract No.:

7. Date Issued: 8. Date Revised: 9. DRD Category:

☐ 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: Applicable throughout the PWS

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

pg. 11

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.

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

pg. 12

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)

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.

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.

pg. 13

1. DRD Title: Contract Management Plan

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

5. Solicitation No.: 80TECH22R0001

6. Contract No.:

7. Date Issued:

8. Date Revised: 9. DRD Category:

☐ Technical ☒ Administrative

☐ S&MA

10. Description/Use: The Contractor shall provide plans to coordinate, integrate, and manage all technical, administrative, and contract management requirements of the eMITS contract.

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

Initial Submission: After contract award

Submission Frequency: Initial submission with the proposal shall include the following sections:

Contractor’s Management Plan: Items a through m.

a. For Item 1g: Outline the framework for a Records Management Program (vs full instructions given in DRD-1, section B.1.g). The Offeror shall identify contractor owned records of interest to the Government (for example, contractor purchase records) and the plan(s), standards, and guidelines used to manage, retain, disposition, and destroy these records (both contractor-originated and Government records handled in the implantation of requirements in SOW sections 3.0 – 9.0) over the life of the contract.

b. Within 30 days of notification of award, the plan shall be modified to include a full, detailed discussion of the Records Management Program. DRD-1 shall include points of contact (POCs) for Contractor-owned and Contractor-managed records (as appropriate), and shall outline how contract-related, Contractor-owned records are to be handled, retained, and dispositioned or terminated.

Communications Plan as detailed above, except items 2c and 2e.

Data Management Plan Continuous Service and Continuous Process Improvement Plan(s): Item a only.

Innovation Management Plan:

All DRD-1 requirements shall be submitted and must be fully approved by NASA prior to the beginning of contract performance. The approved Contract Management Plan becomes a contractual requirement under Section J of the contract.

Format: Contractor format acceptable

Interrelationship: PWS 3.0 Contract Management and Administration

pg. 14

Applicable Documents: None

Scope: The Contractor shall provide an overall management plan to oversee and execute all requirements of the eMITS contract. This will include plans to manage and oversee all contract activity performed at both the Agency and local Center levels as required by work package or task order.

Contents: The Contract Management Plan includes the following seven sections:

1. Contract Management

2. Contract Integration Services

3. Communications

4. The Service Asset and Configuration Management (SACM) Plan (This section is to be delivered prior to contract performance and is not due with proposal.

Baselined 180 days after effective date of the contract)

5. Data Management

6. Continuous Service and Continuous Process Improvement

7. Innovation Management

The Contract Management Plan contains the plans for oversight, coordination and execution of all contract technical and administrative tasks. The initial Contract Management Plan will be considered a baseline document and shall be updated annually or more frequently as needed to reflect significant changes. Significant changes may include new business practices or methodologies as well as scope/descope of the plan. All updates to the Contract Management Plan will be approved by the Contracting Officer (CO) and the Contracting Officer’s Representative (COR). The Contract Management Plan is an umbrella document that encompasses and integrates all IT Management, Data Management, Multimedia, and Service Integration activities. The Contract Management Plan shall include:

1. Contract Management: The Contractor’s approach and plan to:

a. Oversee and manage the activities of the contract to include management and integration of the Contractor “team” (e.g., plan for seamless interface between eMITS contractors [prime and subcontractors, both large and small])

b. Establish effective communications and collaboration between the contractor, NASA OCIO, NASA OCOMM, customer management, Government IT and Technical Service Managers, and the Government contract management team (e.g., communications and collaboration on the roles, responsibilities, interactions, and expectations, to include the provision of a seamless interface between eMITS contractors and civil service employees). Include a discussion on Governance process(es), to include any key, internal contractor boards integral in the implementation of the Contractor’s management plan.

c. Define the Contractor’s Organizational (prime and subcontractors) structure:

pg. 15

i. Include organization charts, with emphasis on roles and responsibilities of organizational elements

ii. Define operating parameters for the Contractors and expectations the Contractor has of the Government’s role to achieve mission success.

iii. Identify points-of-contact (position/location/phone) for incidents which involve the security of information technology for the eMITS contract.

iv. Identify key operational areas.

v. Identify flow of authority and approval levels.

vi. Describe functional relationships between internal organizational elements that differ from the flow of line authority.

d. Provide eMITS products and services to the Government, including the plan to transition services from a center managed framework to an Agency (enterprise) managed framework, while remaining flexible to center and site requirements.

e. Determine employee work locations (e.g., remote, telework, on-site, transitory). The contractor shall include the expected cost benefit analysis and potential cost avoidance of maximizing the contractor’s employees ability to work from anywhere.

Additionally, include how the contractor will provide effective services at a high standard utilizing maximum remote or telework practices.

f. Attract and retain a qualified workforce and provide on-demand staffing.

g. Providing products and services to multiple NASA organizations and all NASA

Centers/sites. The plan should outline how the contractor willto evaluate multiple organizational governance structures to recommend innovative and efficient plans to deliver eMITS products and services.

h. Identify, elevate, resolve, and report issues and problems on the contract.

i. Conduct a root-cause analysis and corrective actions – whether requested/required by the Government or internally-directed.

j. Maintain an accurate schedule and cost estimates made to the Government.

k. Implement a Records Management Program (in accordance with NPR 1441.1) – to include: the identification of Contractor-generated and Contractor-owned records of interest to the Government (i.e., purchase records) and the plan to manage, retain, disposition and destroy those records throughout the life of the contract. The plan should include:

i. The strategic plan for handling and delivering the Government records identified in the eMITS PWS.

ii. A strategic plan for preserving, migrating, and accessioning media formats including but not limited to multimedia records.

l. Develop a strategy and implementation plan for innovation and modernization.

m. Manage risk (technical, schedule, cost, safety, and IT security risks) and develop measures to demonstrate success in these areas.

pg. 16

2. Contract Integration Plan The Contract Management Plan shall include a discussion on and the Contractor’s approach to integration of services across the eMITS performance work statement as well as how the services of eMITS will be integrated with the services performed across the portfolio of Agency IT contracts and associated non-IT contracts. This section shall include:

a. A discussion on how the eMITS contractor will provide eMITS services in an integrated manner to all customers of the contract to include a discussion on integration planning and communications with customer organizations.

b. An approach to establish and maintain effective, collaborative communications with management teams and points of contact with other Agency IT contractors, including the plan to establish effective working relationships with those associated contractor management and operational teams.

c. An Integration Management structure and plan for the management and oversight of integrated services. Include the contractor’s approach for integrating non-eMITS IT services and applicable services of other associated Agency contractors into effective service packages for meeting the needs of NASA customers that mitigate and minimize the need for government integration of services provided in a multi-vendor environment. The plan shall identify the contractor employee who will serve as the Contract Integration Manager responsible for leading and managing the integration of services.

d. An approach to the analysis, planning, development, and maintenance of the OCIO Integrated Services Catalog (ISC) as outlined in the eMITS work statement, including how services provided by other Agency IT contractors may be included in the catalog. This section shall also discuss the contractors plan to communication and facilitate adoption of use of the ISC by Agency customers.

3. The Communications section shall outline the plan to communicate with Government technical personnel.

Technical, Cost, Schedule, and Risk (TCSR) Reviews:

The Contractor shall outline how they will ensure that team members clearly understand the contract plan(s) for evaluation of performance. The reviews should include the following:

a. Technical, Cost, Schedule, and Risk (TCSR) reviews and monthly reviews.

b. Concerns/deficiencies identification. Specifically, outline the Contractor responsibilities to facilitate corrections for concerns or deficiencies and minimize impact to mission success.

c. Identification (by role) of board members/representatives involved in the evaluation process

pg. 17

d. Opportunities for the Contractor to present/emphasize aspects of their performance to the Government.

e. Criteria identified by the Government with respect to the evaluation process.

4. 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. The Plan shall include, at the 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.

5. Data Management Plan

The Contractor shall describe the plan to be implemented to analyze, manage, and administer Government-owned and Contractor-managed data across the contract. The plan shall include a detailed discussion on how data is identified, tagged (for keyword searching), and modeled across repositories, collections, and websites contract wide.

6. Continuous Service Improvement (CSI) and Continuous Process Improvement (CPI)

a. The Contractor shall prescribe the process to be implemented to ensure that CSI/CPI is incorporated into the contract. CSI provides instructions for customer added value in the form of improvements. It combines principles, practices and methods of quality management, change management and process improvements in order to optimize the service strategy, design and transitional phases. CPI strives to make small step efficiencies in standard processes. CPI may include standardizing/streamlining existing processes, removing items/processes that have no value, and/or improving customer satisfaction.

b. At the first major revision of the Contract Management Plan (end of contract year 1), the Contractor shall provide its plan for identifying portions of this contract that could progress from cost reimbursable to a fixed price methodology. This plan shall be revisited and revised as appropriate on an annual basis.

c. The Contractor shall provide its plan for developing new technologies, innovations, and process improvements that when implemented, shall result in improved quality of

pg. 18 products and services while maintaining or reducing costs to the OCIO and OCOMM.

The plan shall include the Contractor’s process for continuous assessment and prioritization.

i. Define how continuous improvement will be recorded and documented.

ii. Identify the specific part of the organization responsible for administering continuous improvement.

iii. Describe the procedures to ensure the organization is actively working

CSI/CPI.

iv. Define how NASA will be involved in final decisions in the change process.

v. Plan to report realized benefits to the government of implemented CSI/CPI methods (e.g., cost, schedule, efficiency, etc.).

7. Innovation Management

The Contractor shall outline its plan to foster a work environment conducive to developing innovative plans through the creation, adoption, and implementation of new ideas. The Contractor shall identify the process(es), procedure(s), and guideline(s) to be used to ensure innovations and technology infusion is encouraged, managed, and addressed.

a. Define how innovations will be recorded and documented.

b. Identify the specific contract elements involved and how they are impacted.

c. Define how innovations will be vetted internally and the criteria by which innovations to be brought forward to the Government will be internally evaluated.

d. Define how NASA will be involved with final decisions in the change process.

e. An innovation cannot be considered fully accepted until it has been approved and accepted by the appropriate Government Control Board or the Contract has been updated via official change processes.

The Contractor shall consider the PWS in its plans but shall not limit the proposed changes to processes currently used or described in the PWS. The contractor may propose innovations in services and service delivery across the portfolio of Agency IT contracts or other associated contracts as applicable.

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

Maintenance: The Contactor 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.

pg. 19

1. DRD Title: Contract Phase-In Plan

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

☒ Administrative

☐ S&MA

10. Description/Use: To describe the Contractor’s activities and planned approach to contract phase-in.

11. Distribution: Electronic submission to COR and the Contracting Officer

Initial Submission: Preliminary draft with proposal.

Submission Frequency: Revisions are required for significant changes or expanding to additional locations, and during the implementation of significant changes in processes and services.

Format: Submitted electronically, unless otherwise directed. The data shall be delivered to the Government via an electronic transfer (e.g., electronic mail, flash drive, or file transfer protocol) in a format readable by a Government device utilizing the NASA-STD-2804, Minimum Interoperability Software Suite standards.

Interrelationship:

FAR 52.237-3, Continuity of Services DRD: MA-01, Contract Management Plan DRD: LS-01 Government Property Management Plan

Scope: This document is the Contractor’s approach to contract phase-in. Assume a minimum of 100 work packages to be issued prior to contract start. The plan defines tasks, schedule, responsibilities, and agreements for both the contractor and the Government. 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 Contractor shall meet full performance requirements from the start date of the base contract period. Prior to performance of services ordered by the Government under this

pg. 20 contract, the Contractor shall accomplish all tasks required to begin work pursuant to this contract.

Some examples of activities that remain the sole responsibility of the Contractor include managing transition activities, hiring personnel, securing personnel badges and clearances, training personnel, scheduling the performance of ordered work, ensuring approval of safety plan, and compliance with contractual data requirements.

The Contractor shall submit a Phase-In Plan that details the implementation plans for proposed processes and strategies for effecting a smooth transition. The plan shall provide, at a minimum, detailed rationale and a specific approach to successfully complete each item described below. For each item, provide a schedule and point of contact responsible for completing the item and propose objective measures that can be used to determine if the item has been achieved. Plan details shall include at a minimum the following:

1. Provide a plan for ensuring a smooth phase-in consistent with maintaining efficient continuity of services for the 60-day period prior to contract start. The plan shall describe how you will maintain continuous and efficient operations.

2. Provide a schedule for all phase-in steps/milestones, and your approach meeting the schedule. Included in the schedule shall be a plan to support the proposal to, and negotiation of, the first work package to be placed under the resultant contract.

Provide a phase-in schedule for management items to be met.

3. Describe in detail plans for initial staffing and training of personnel. Discuss proposed key personnel and demonstrate that they are committed to employment prior to start of contract.

4. Describe how you will work with the incumbent contractors and NASA, include necessary resources and interfaces needed from each to ensure an effective transition and continuous service.

5. Provide your plan for securing badges and necessary security clearances for personnel to access NASA Centers and its associated facilities, as required, prior to start of the contract.

6. Complete a physical inventory of Government-furnished provide evidence of a system to manage property in its possession, and sign for accountability of the property prior to start of contract.

7. Complete all certification and license requirements for your company and all personnel prior to start of contract.

8. Proposed Firm Fixed Price for your Phase-in Plan, in accordance with the Cost/Price Proposal Instructions and Excel Pricing Template “Phase-In Plan” that reconciles to contract clause B.6.

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

Remarks: None

Maintenance: None

pg. 21

1. DRD Title: Information Security Management Plan

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

☒ Technical ☐ 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 3.0 and where applicable throughout the PWS.

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

pg. 22 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.

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

pg. 23

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

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

☐ 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 OCSS.

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: Contractor format is acceptable

Interrelationship: PWS: 3.0 and as applicable throughout the PWS

Applicable Documents:

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

pg. 24

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.

pg. 25

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

pg. 26

1. DRD Title: Information Technology (IT) Capital Planning and Investment Control

(CPIC)

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

☒ Administrative

☐ S&MA

10. Description/Use: To document the Contractor's compliance with Federal and NASA IT CPIC Planning and Reporting regulations and reporting requirements

11. Distribution: CO; COR

Initial Submission: As requested; Due within 30 days of request

Submission Frequency: see above

Format: Unless otherwise directed, the data requested in this DRD shall be delivered to the Government in soft-copy via an electronic transfer…