AEGIS Draft RFP J-Attachments.pdf

AEGIS

80JSC020R0039

J-1-1

Attachment J-1

Data Requirements List And

Data Requirements Descriptions

J-1-2

DATA REQUIREMENTS LIST (DRL) AND

DATA REQUIREMENTS DESCRIPTIONS (DRD)

The following pages set out the documentation requirements of this contract, starting with a DRL, which is an index to the DRDs. Each DRD prescribes the required data product content, schedule, type, and other particulars for specific data submission requirements.

Data Requirements List

DRL

LINE #

DRD # DATA

TYPE

DRD TITLE OPR

AEGIS-CD CD – Contractual Data 1 001 3 Technology Reports ED10

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

AEGIS-MA MA – Management 3 001 1 Contract Management Plan IS01 4 002 1 Contract Phase-In Plan IS40 5 003 2 Information Security Management Plan OCIO 6 004 1 Information Technology (IT) System Security Plan

(SSP)

OCIO

7 005 2 Service Asset and Configuration Management (SACM) Plan

OCIO

8 006 2 Release and Deployment Management (RDM) Plan OCIO 9 007 3 Application Inventory Report OCIO 10 008 2 Capacity Management Plan OCIO 11 009 3 Service and Component Capacity Report OCIO 12 010 2 IT Service Continuity Management (ITSCM) Plan OCIO 13 011 3 Interface Definition Agreement (IDA) OCIO 14 012 3 NASA Enterprise Service Catalog Data Requirements IS01 15 013 3 Problem Documentation IS01 16 014 1/2/3 Documentation IS01 17 015 2 Work Breakdown Structure (WBS) and WBS

Dictionary

CS40

18 016 2 CP Systems Readiness Report IS01 19 017 2 Service Performance Report IS01 20 018 2 Cost Reports IS01 21 019 2/3 Export Control Plan and Reports IS01 22 020 3 Financial Management Report (533M) RS20 23 021 3 Contractor Self-Assessment Report IS01 24 022 1 Fixed Price Transition Plan CO/COR 25 023 2 Corporate Target Architecture (CTA) and 5-Year Service

Line Plans Annual Report

IS40

26 024 2 Organizational Conflicts of Interest (OCI) Plan PS31 27 025 3 AEGIS Monthly Status Review Report IS01 28 026 3 Huntsville Operations Support Center (HOSC)

Program Management and Integration

HP20

29 027 2 Re-procurement Data Package CO/COR

J-1-3

DRL

LINE #

DRD # DATA

TYPE

DRD TITLE OPR

30 028 1 ViTS Asset Transition Value (ATV) Report IS40 31 029 2 WYE Reports IS01 32 030 2 Small Business Subcontracting Plan CO 33 031 2 Total Compensation Plan CO 34 032 2 Notification of Potential Labor Dispute and

Contingency Strike Plan

CO

35 033 1 Close-out Plan CO/COR

AEGIS-QE QE – Quality Engineering 37 001 1 Quality Plan QD21

AEGIS-RM RM – Reliability and Maintainability 38 001 1 Operability/Maintainability Plan IS01

AEGIS-SA SA – Safety 39 001 1 Safety, Healthy, and Environmental (SHE) Plan AS10/

QD12

40 002 3 Mishap and Safety Statistics Reports QD12 41 003 3 Environmental and Energy Consuming Product

Compliance Reports

AS10

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.

J-1-4

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.

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:

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

J-1-5

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.

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.

J-1-6

DATA REQUIREMENTS DESCRIPTION (DRD)

1. ISSUE: DRAFT 2. DRD NO.: CD-001

3. DATA TYPE: 3 4. DATE REVISED:

5. PAGE: 1/3

6. TITLE: Technology Reports

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

8. OPR: ED10 9. DM: IS01

10. DISTRIBUTION: Per Section 13, below

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

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

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

14. INTERRELATIONSHIP: PWS Section 3.11, Table 29, Strategy Generation.

15. DATA PREPARATION INFORMATION:

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

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

J-1-7

DRD Continuation Sheet

TITLE: Technology Reports DRD NO.: CD-001

DATA TYPE: 3 PAGE: 2/3

15. DATA PREPARATION INFORMATION (CONTINUED):

15.3 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)?

J-1-8

TITLE: Technology Reports DRD NO.: CD-001

DATA TYPE: 3 PAGE: 3/3

15.3 CONTENTS: (CONTINUED)

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

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.

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

15.5 MAINTENANCE: None required

J-1-9

1. ISSUE: DRAFT 2. DRD NO.: LS-001

3. DATA TYPE: 1 4. DATE REVISED:

5. PAGE: 1/3

6. TITLE: Government Property Management Plan (PMP)

7. DESCRIPTION/USE: To describe the method of administering and controlling Government personal property and submitting proposed property manager qualifications.

8. OPR: AS41 9. DM: IS01

10. DISTRIBUTION: Cognizant Property Administrator

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

12. SUBMISSION FREQUENCY:

Final Submission: Due 30 days after contract award.

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

14. INTERRELATIONSHIP: PWS Sections 2.4, Logistics; 8.7 Agency Data Center and Cloud

Computing

15. DATA PREPARATION INFORMATION:

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

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)

J-1-10

TITLE: Government Property Management Plan (PMP) DRD NO.: LS-001

DATA TYPE: 1 PAGE: 2/3

15. DATA PREPARATION INFORMATION (CONTINUED):

15.2 APPLICABLE DOCUMENTS (CONTINUED):

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

15.3 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-1-11

TITLE: Government Property Management Plan (PMP) DRD NO.: LS-001

DATA TYPE: 1 PAGE: 3/3

15. DATA PREPARATION INFORMATION (CONTINUED):

15.3 CONTENTS (CONTINUED):

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)

15.4 FORMAT: Contractor format is acceptable.

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

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

J-1-12

1. ISSUE: DRAFT 2. DRD NO.: MA-001

5. PAGE: 1/2

6. TITLE: Contract Management Plan

7. DESCRIPTION/USE: To document the Contractor's overall contract management approach and organization for accomplishing the contract requirements.

8. OPR: CO and COR 9. DM: CO/COR

10. DISTRIBUTION: Electronic submission to Government-provided database.

11. INITIAL SUBMISSION: Preliminary draft 30 days after contract award.

12. SUBMISSION FREQUENCY: Final 30 days after effective date of contract. Submit revisions for

Government approval after any major change in management organization and approach.

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

14. INTERRELATIONSHIP: PWS Section 2.1, Program Management; 8.7 Agency Data Center and

Computing Services.

15. DATA PREPARATION INFORMATION:

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

15.2 APPLICABLE DOCUMENTS: None

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

J-1-13

TITLE: Contract Management Plan DRD NO.: MA-001

DATA TYPE: 1 PAGE: 2/2

15. DATA PREPARATION INFORMATION (CONTINUED):

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

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

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

J-1-14

1. ISSUE: DRAFT 2. DRD NO.: MA-002

5. PAGE: 1/2

6. TITLE: Contract Phase-In Plan

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

8. OPR: IS40 9. DM: IS40

10. DISTRIBUTION: COR

11. INITIAL SUBMISSION: Preliminary draft with proposal.

12. SUBMISSION FREQUENCY: Revised for significant changes that may be required during the implementation of the specific changes in processes and services.

13. REMARKS: None

14. INTERRELATIONSHIP: PWS Section 2.5, Contract Phase-In/Transition Management

15. DATA PREPARATION INFORMATION:

15.1 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 60 calendar days from phase-in start.

15.3 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 a phase-in schedule to accomplish all proposed phase-in steps/milestones and the personnel responsible for those steps/milestones. Describe your approach for how you will implement the schedule.

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

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

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

J-1-15

TITLE: Phase-In Plan DRD NO.: MA-002

DATA TYPE: 1 PAGE: 2/2

15.3 CONTENTS (CONTINUED):

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

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

h. Address property control transfer, including schedule and milestones for completing 100% inventory including but not limited to Government Furnished Property and Installation Accountable Government Property.

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

15.4 FORMAT: Submitted electronically; MS Word

J-1-16

1. ISSUE: DRAFT 2. DRD NO.: MA-003

3. DATA TYPE: 2 4. DATE REVISED:

5. PAGE: 1/2

6. TITLE: Information Security Management Plan

7. DESCRIPTION/USE: To describe the Contractor’s methodology for managing all aspects of information security, including addressing the cross-functional and service-specific information security requirements.

8. OPR: OCIO 9. DM: IS01

10. DISTRIBUTION: Per Contracting Officer’s letter.

11. INITIAL SUBMISSION: 60 days after effective date of the contract.

12. SUBMISSION FREQUENCY: One time; revise as required.

13. REMARKS:

14. INTERRELATIONSHIP: As applicable throughout the PWS

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Information Security Management Plan provides the Contractor’s proposed management approach for meeting cross-functional and service-specific information security requirements.

15.3 CONTENTS: The Information Security Management Plan shall include, at a minimum, the following:

a. Contractor’s information security POC(s) and roles and responsibilities for the POC(s).

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

Plans (IT-SSP) in the NASA system of record and anticipated 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, security assessments, remediation, authorization, continuous monitoring, etc.

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

e. Process for information security incident management 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 requirements, such as IT

Security Awareness training, qualifications for system administrators and others with elevated privileges, etc., and that Contractor employees are knowledgeable of NASA Cybersecurity policies and procedures.

15.4 FORMAT: Contractor format is acceptable with NASA approval.

J-1-17

TITLE: Information Security Management Plan DRD NO.: MA-003

DATA TYPE: 2 PAGE: 2/2

15.5 MAINTENANCE: Update as required to maintain current with program changes.

J-1-18

1. ISSUE: DRAFT 2. DRD NO.: MA-004

5. PAGE: 1/2

6. TITLE: Information Technology (IT) System Security Plan (SSP)

7. 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. This document 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.

8. OPR: OCIO 9. DM: XD042

10. DISTRIBUTION: Per Contracting Officer's letter

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

12. 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 after any significant changes to the IT System.

Updated copies shall be submitted upon any significant changes or annually, whichever comes first.

13. REMARKS:

14. INTERRELATIONSHIP: As applicable throughout the PWS

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Information Technology (IT) System Security Plan includes a description of the IT system 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 Cybersecurity policy, standards and handbooks.

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

J-1-19

TITLE: Information Technology (IT) System Security Plan (SSP) DRD NO.: MA-004

DATA TYPE: 1 PAGE: 2/2

15. DATA PREPARATION INFORMATION (CONTINUED):

15.2 APPLICABLE DOCUMENTS (CONTINUED):

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

15.3 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, 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 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.

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

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

J-1-20

1. ISSUE: DRAFT 2. DRD NO.: MA-005

5. PAGE: 1/1

6. TITLE: Service Asset and Configuration Management (SACM) Plan

7. DESCRIPTION/USE: To describe the Contractor’s approach for managing and protecting the integrity of service assets and configuration items.

8. OPR: OCIO 9. DM: IS01

10. DISTRIBUTION: Electronic submission to Government-provided database.

11. INITIAL SUBMISSION: Draft 60 days after effective date of the contract.

12. SUBMISSION FREQUENCY: Preliminary 120 days after effective date of the contract; Baseline

180 days after effective date of the contract; update as required.

13. REMARKS:

14. INTERRELATIONSHIP: As applicable throughout the PWS.

15. DATA PREPARATION INFORMATION:

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

15.3 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 attributes, relationships, baselines and detail, and status and changes thereto) in the Configuration Management Database (CMDB).

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

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

15.4 FORMAT: Contractor format is acceptable.

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

J-1-21

1. ISSUE: DRAFT 2. DRD NO.: MA-006

5. PAGE: 1/1

6. TITLE: Release and Deployment Management (RDM) Plan

7. DESCRIPTION/USE: To describe the Contractor’s approach for managing release packages and their constituent components, deployment into production, and establishing effective use of the service(s).

8. OPR: OCIO 9. DM: IS01

11. INITIAL SUBMISSION: Draft 60 days after effective date of the contract.

12. SUBMISSION FREQUENCY: Preliminary 120 days after effective date of the contract; baseline

180 days after effective date of the contract; update as required.

13. REMARKS:

14. INTERRELATIONSHIP: As applicable throughout the PWS.

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The RDM Plan provides the Contractor’s approach for managing release packages and their constituent components, deployment into production, and establishing effective use of the service(s).

15.2 APPLICABLE DOCUMENTS: None

15.3 CONTENTS: The RDM Plan shall include, at a minimum, the following:

a. Process for performing RDM in coordination and collaboration with Government, Enterprise

Services contractors, and other contractors.

b. Process for notifying the Enterprise Service Desk regarding release and deployment activities.

c. Process for building, testing, piloting (if required), and packaging of releases.

d. Process for planning for pass/fail situations and executing a back-out plan (if required).

e. Process for verifying deployment, stabilizing service(s), and closing deployment.

15.4 FORMAT: Contractor format is acceptable with NASA approval.

J-1-22

1. ISSUE: DRAFT 2. DRD NO.: MA-007

5. PAGE: 1/1

6. TITLE: Application Inventory Report

7. DESCRIPTION/USE: To collect and provide an inventory of applications being used to support

NASA services.

8. OPR: OCIO 9. DM: IS01

10. DISTRIBUTION: Per Contracting Officer’s letter.

11. INITIAL SUBMISSION: 60 days after effective date of the contract.

12. SUBMISSION FREQUENCY: Annually.

13. REMARKS:

14. INTERRELATIONSHIP: As applicable throughout the PWS.

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Application Inventory Report includes all applications being used to support NASA services.

15.2 APPLICABLE DOCUMENTS: None

15.3 CONTENTS: The Application Inventory Report shall include, at a minimum, the following:

a. Application Name (as documented in the NASA Application Repository).

b. Unique Application ID (as documented in the NASA Application Repository).

c. Application Owner (responsible NASA government official).

d. Technical POC for the application (individual with the most technical knowledge about the application, i.e., government or contractor).

e. Application description/services provided.

f. Total Annual Cost: development, maintenance, enhancement or steady state to include:

1. Total hardware costs e.g., server(s), storage, upgrades, application specific hardware devices.

2. Total software licensing/purchase fees.

3. Total recurring maintenance and support agreement fees.

4. Total application data center hosting costs e.g., infrastructure, facilities, HVAC, power, labor.

5. Total contractor work year equivalent cost (required to directly support the application).

15.4 FORMAT: Contractor format is acceptable with NASA approval.

15.5 MAINTENANCE: Update annually to maintain current with program changes.

J-1-23

1. ISSUE: DRAFT 2. DRD NO.: MA-008

5. PAGE: 1/1

6. TITLE: Capacity Management Plan

7. DESCRIPTION/USE: To describe the Contractor’s methodology and approach for managing capacity and associated performance issues.

8. OPR: OCIO 9. DM: IS01

10. DISTRIBUTION: Per Contracting Officer's letter.

11. INITIAL SUBMISSION: Draft 60 days after effective date of the contract.

12. SUBMISSION FREQUENCY: Preliminary 120 days after effective date of the contract; baseline

180 days after effective date of the contract; update as required.

13. REMARKS:

14. INTERRELATIONSHIP: As applicable throughout the PWS.

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Capacity Management Plan describes the Contractor’s methodology and approach for managing capacity and associated performance issues.

15.2 APPLICABLE DOCUMENTS: None

15.3 CONTENTS: The Capacity Management Plan shall include, at a minimum, the following:

a. Process for identifying service and component capacity including trends and profiles.

b. Process for recommending effective use of existing capacity.

c. Standard templates to support capacity planning.

d. Process for coordinating and collaborating with Government, Enterprise Services contractors, and other contractors, to support capacity planning.

e. Process for providing advice on new technologies.

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

15.4 FORMAT: Contractor format is acceptable with NASA approval.

J-1-24

1. ISSUE: DRAFT 2. DRD NO.: MA-009

5. PAGE: 1/1

6. TITLE: Service and Component Capacity Report

7. DESCRIPTION/USE: To collect and provide service and component capacity data showing trends and utilization.

8. OPR: OCIO 9. DM: IS01

10. DISTRIBUTION: Per Contracting Officer’s letter.

11. INITIAL SUBMISSION: 10 business days following completion of the first monthly reporting period.

12. SUBMISSION FREQUENCY: Monthly within 10 business days after the end of each calendar month.

13. REMARKS:

14. INTERRELATIONSHIP: As applicable throughout the PWS.

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Service and Component Capacity Report provides monthly data showing capacity utilization, volumes, and historical trends against forecast and baselines.

15.2 APPLICABLE DOCUMENTS: None

15.3 CONTENTS: The Service and Component Capacity Report shall provide statistics for the current month as well as the two (2) previous months and shall be reported by NASA location and as a total for NASA. The report shall include, at a minimum, the following:

a. Results of performance monitoring, service capacity analysis, and service performance tuning.

b. Current, historical, and projected capacity thresholds.

c. Reporting against Government-established standards and metrics.

d. Results of formal reviews of projected capacity requirements.

e. Capacity and performance trends and volumes against forecasts and baselines.

f. Results of prototyping and sizing exercises.

g. Testing and sizing models for capacity impacts.

15.4 FORMAT: SIM to provide format for all reports.

15.5 MAINTENANCE: None required.

J-1-25

1. ISSUE: DRAFT 2. DRD NO.: MA-010

5. PAGE: 1/1

6. TITLE: Information Technology (IT) Service Continuity Management (SCM) Plan

7. DESCRIPTION/USE: To describe the Contractor’s method for establishing and maintaining ongoing recovery capability for required IT services and their components.

8. OPR: OCIO 9. DM: IS01

10. DISTRIBUTION: Per Contracting Officer’s letter.

11. INITIAL SUBMISSION: Draft 60 days after effective date of the contract.

12. SUBMISSION FREQUENCY: Preliminary 120 days after effective date of the contract; baseline

180 days after effective date of the contract; update as required.

13. REMARKS:

14. INTERRELATIONSHIP: As applicable throughout the PWS.

15. DATA PREPARATION INFORMATION:

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

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

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

h. Process for testing and documenting results…