9s.__Enclosure_EE_-_Phase-In_Data_Requirements_List.pdf

RFP 80GSFC17R0018

Enclosure EE

SPACE EXPLORATION NETWORK SERVICES AND EVOLUTION (SENSE)

Phase-In Data Requirements List Introduction The Phase-In Data Requirements List governs data required by the contract. The contractor shall deliver data as required by the Data Requirements Descriptions (DRDs) included herein and listed on the Data Requirements List (DRL) during the SENSE phase-in.

The DRL uses functional categories to segregate of DRDs as follows:

Designation Description MGT Management SUS Sustaining OPS Operations FAC Facilities SEC Security SMA Safety and Mission Assurance

Data Requirements List The DRL provides a listing of the DRDs that are required.

For each DRD, the DRL indicates the following.

• ID – DRD Identifier.

• Title – DRD Title

• Submission Requirements – The Contractor shall deliver the CDRL item per the timing specified in the Submission Requirements field unless otherwise directed in the task order.

• Approval/Review/Information (A/R) -

1. Approval: The Contractor shall receive approval from the Government prior to implementing CDRL items designated with an A code. If the contractor has not received a written response from the government within thirty (30) calendar days of delivery of a CDRL item, the contractor may proceed as if the CDRL item has been approved. The Contractor shall resubmit the document within fourteen (14) calendar days of receiving written feedback from the Government.

2. Review: The Contractor shall implement CDRL items designated with an R upon submission to the Government. The Government will review the CDRL item and may provide feedback. The Contractor shall resubmit the CDRL item within fourteen (14) calendar days of receiving written feedback from the Government.

Markings The Contractor shall not deem any documentation produced, or other information gathered, as a result of work under this Performance Work Statement, as proprietary to the Contractor.

Unless specifically required, the Contractor shall not place any corporate identification on anything produced under this Performance Work Statement except for the company name, address, telephone number, e-mail address and website on a single page inside the cover of multi-page documents or a single slide at the beginning of a multimedia presentation.

Delivery The Contractor shall deliver DRL items to the Government electronically, through a communally used mechanism such as email or a web portal. The contractor shall provide the DRL items in commonly used formats such at PDF, MS Word, MS Excel, MS Project, JPEG, etc.

The Contractor shall notify the Contracting Officer, Contracting Officer’s Representative, and configuration manager of DRL item delivery. The Contractor shall include revision level, date, and a detailed description of the changes for updated DRL items. Where available (i.e., MS Word, MS Excel, MS Visio), the Contractor shall deliver updated DRL items with the track changes function on.

ID Title Submission Requirements A/R Management

MGT-01 Integrated Management Plan Phase-in start +4 weeks A

MGT-09 Configuration Management Plan Phase-in start +6 weeks R

MGT-11 Risk Management Plan and Risk List Phase-in start +4 weeks R

MGT-12 Systems Engineering Management Plan (SEMP) Phase-in start +4 weeks R

Sustaining

SUS-01 Reliability, Maintainability, and Sustaining Plan Phase-in start +10 weeks R

Operations

OPS-02 Continuity of Operations Plan and Procedures Phase-in start +8 weeks A

OPS-03 Government Property & Logistics Management Plan Phase-in start +6 weeks R

Facilities

FAC-02 Environmental Management Plan Phase-in +10 weeks A

Security SEC-01 Security Management Plan Phase-in start +4 weeks A SEC-02 IT System Security Plan Phase-in start +8 weeks A SEC-04 TDRS Protection Plan Phase-in start +8 weeks A SEC-05 IT Security Management Plan Phase-in start +6 weeks A

Safety and Mission Assurance

SMA-01 Mission Assurance Implementation Plan (MAIP) Phase-in start +10 weeks and upon update A

ID Title Submission Requirements A/R

SMA-02 Mission Assurance Compliance Matrix With Mission Assurance Management Plan A

SMA-04 Emergency Preparedness and Disaster Recover Plans Phase-in start +8 weeks A

SMA-15 Laser Safety Manual Phase-in start +6 weeks A

Management

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: MGT-01

2. TITLE: Integrated Management Plan 3. DATE: 6 February 2017

4. DESCRIPTION/PURPOSE:

Describes the contractor's integrated management processes, organization, and standards for overall management of all SENSE task orders.

5. DATA REQUIREMENTS:

CONTENT:

The Integrated Management Plan shall address the contractor's process for work definition and authorization, schedules and scheduling, budgeting, data accumulation, health and safety, mission assurance, corrective action, subcontract management, indirect cost management, baseline control, organization structure identifying critical positions, and information and data management.

The plan shall describe the comprehensive integration of all management processes of the prime, subcontractors, and major vendors, and interaction with the Government.

The plan shall identify:

• Interoperability standards applicable to the contractor’s Government interaction.

• Systems specifically required to accomplish the Statement of Work

• Systems and procedures that are to be set in place by the contractor.

The plan shall include:

• Interrelationships of technical management, business management, and subcontract management.

• An organizational chart identifying all managerial positions by title, position qualifications, and physical location.

• An Operations Plan that includes a detailed description of the responsibilities and authorities for operation and management of this program, from lower levels through intermediate management to top-level management.

• Management elements such as the span of control, degree of autonomy, and lines of communication.

• All interfaces with NASA personnel, and major subcontractors shall be clearly delineated.

The plan shall provide a process to ensure all services are in a state of operational readiness at all times, including preparations for mission launches and sustaining levels of performance throughout mission lifetimes. The plan shall provide for regular monitoring of all activities under this contract and provide visibility to NASA.

The plan shall show interrelationships with more detailed plans and procedures for assuring the operational readiness of all services required by task orders. This plan shall reference more detailed plans, as applicable, such as those for configuration management, risk management, systems engineering, security, continuity of operations, property management, facilities management, safety, and mission assurance.

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: MGT-09

2. TITLE: Configuration Management Plan 3. DATE: 1/23/17

4. DESCRIPTION/PURPOSE:

To describe and enforce the contractor’s approach for accomplishing the configuration requirements of the contract for all SENSE sites, systems, and test facilities as defined in the awarded RTOs, throughout the project lifecycle, to include hardware, software, firmware, operations/test configurations, and documentation

5. DATA REQUIREMENTS:

CONTENT:

The CM plan shall describe how CM will be conducted throughout the project lifecycle. The plan shall cover all hardware, software, firmware, operations/test configurations, and documentation for all ESC sites and systems as defined in the awarded task orders. Documentation includes drawings, facilities documents, operations and maintenance documentation, test documentation, training/certification documentation and other records as required by task order.

The plan shall prescribe the configuration management processes to be implemented and methods to be used for configuration identification, interface control, change control, documentation control, status accounting, and configuration verification.

The plan shall describe the contractor’s CM organization, policies, roles and responsibilities, configuration management (CM) definitions, procedures, implementation approach, and control systems that are to be used to ensure proper performance of all required contract CM activities.

The plan shall describe the NASA participation in the contractor Configuration Management process.

The plan shall describe the process for providing a brief description of all proposed changes to be prepared and transmitted to the designated NASA engineering representative prior to each configuration control board or forum meeting held by the contractor.

The contractor’s configuration management processes and control systems shall include maintaining configuration information in a form and structure such that configuration information is available to the government as needed.

The Plan shall include the following documentation trees to provide a reference for the primary ESC documentation to be managed under SENSE. These trees shall be organized and identified to serve as a ready reference list. Updates to these trees shall be delivered when changes are implemented.

ESC Networks Document Tree shall depict the hierarchy and interrelationships of the Government and contractor documents and deliverables on the contract, and shall contain a graphical illustration of project management, system engineering, facilities, integration, test, maintenance, operations, and sustainment documents for each ESC network, their hierarchy, and interrelationships, as appropriate.

The Networks Document Tree shall:

• Include all documents for the ESC networks and show relationship(s), delivery phasing, and maturation phasing.

• Incorporate, through and as directed by ESC, document tree contents provided by GFP vendors.

• Identify documents by name and number.

• Include a brief description defining the scope of each document.

ESC Networks Drawing Tree shall provide a reference list for all ESC Networks drawings, and shall:

• List all drawings for ESC Networks.

• Incorporate, through and as directed by ESC, any drawing tree information provided by GFP vendors.

• Identify drawings by name and number.

• Include a brief description of each drawing.

ESC Networks Specification Tree shall provide a reference list for all ESC Networks specifications, and shall:

• List all specifications for ESC Networks.

• Incorporate, through and as directed by ESC, any specification tree information provided by

GFP vendors.

• Display traceability relationships among the specifications

• Identify specifications by name and number.

• Include a brief description of each specification, design description, and interface control document

APPLICABLE DOCUMENTS:

a. 450-PG-1410.2.1K, 450/ESC - Configuration Management Procedure

b. NASA-STD-2804: Minimum Interoperability Software Suite

c. NASA-STD-2805, Minimum Hardware Configurations

d. SGP-MGMT-PROC-0002, Space Geodesy Project Information and Configuration

Management Procedure

REFERENCE DOCUMENTS:

a. NENS-SNE-E-PM10-0009, Document Tree

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: MGT-11

2. TITLE: Risk Management Plan and Risk List 3. DATE: 30 January 2017

4. DESCRIPTION/PURPOSE:

To describe the Contractor’s process for identifying and managing risk.

5. DATA REQUIREMENTS:

CONTENT:

The Risk Management Plan (RMP) shall:

• Describe the overall process, procedures, roles and tools that will be used.

• Specify the contractor risk objectives and policy toward risk.

• Explain the purpose, scope, assumptions, constraints, key ground rules, and policy pertaining to the SENSE risk management process.

• Provide an overview of the SENSE risk management process and information flow; describe how the process integrates and relates to other operations, maintenance, sustaining, development, project management and system engineering activities.

• Include risk mitigation strategies to be employed throughout the contract term.

• Show the organization, roles, and responsibilities of the SENSE Contractor and subcontractors with regard to risk management, and NASA’s involvement in the contractor’s process.

• Document how team members will be trained in the application of risk management methodology.

• Provide process details and related procedures, methods, tools, and metrics.

• Include here, or in an appendix, the specific methodologies to be used for risk identification, analysis, planning, tracking, and controlling.

• Include the process to be used for continual assessment of the risk profile.

• Describe how risk information will be communicated both internally to the contractor staff and throughout the NASA management chain.

• Specify the format and data elements (the contractor shall use “GSFC 5x5 Risk Matrix for

Class A-C Type Missions” likelihood and severity definitions for risks and their categories) that will comprise the SENSE Risk List, how configuration control will be applied, and how the list will be used and updated.

• Specify how NASA and contractor team members will be able to access the current Risk List at any time.

• The Risk List shall be current, and the current version accessible to the government, as of the contractor’s cut-off date for creating any reports or reviews that contain risk information, such that the status report or review is consistent with the Risk List.

The initial risk list, provided with the initial Risk Management Plan, shall include in the initial set of identified risks and the action plan (for research, acceptance, tracking, or mitigation) for each risk.

APPLICABLE DOCUMENTS:

a. NID 8000.108 (interim directive to NPR 8000.4A), Agency Risk Management Procedural Requirements

b. GPR 7120.4, Risk Management

c. 450-PLAN-0007, Exploration and Space Communications (ESC) Projects Division Risk

Management Plan (RMP)

d. GSFC 5x5 Risk Matrix For Class A-C Type Missions (NASA provided definitions of likelihood and severity for risks and their categories)

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: MGT-12

2. TITLE: Systems Engineering Management Plan

(SEMP)

3. DATE: 1/31/17

4. DESCRIPTION/PURPOSE:

To describe the contractor’s systems engineering methodology, which once approved, will become an Applicable Document for systems engineering tasks performed on the SENSE contract.

5. DATA REQUIREMENTS:

CONTENT:

The Systems Engineering Management Plan (SEMP) shall be coordinated with the Integrated Management Plan (MGT-01) for integration of the technical planning and modifications related to the allocated resources, including cost, schedule, personnel, facilities, and deliverables required.

The SEMP shall:

1. Specify the systems engineering processes and procedures as applied to development of new systems and modifications to existing systems, including control boards, operational concepts, operational requirements, system requirements, functional analysis, system analysis, trade-off strategies, configuration management, and system test and evaluation strategies. Separate processes and procedures shall be tailored according to the scope of the development effort.

2. Identify systems engineering activities associated with concept development including needs analysis, concept exploration, concept definition and Technology Readiness Levels (TRL).

Items to be addressed shall include the processes associated with the identification of operational deficiencies, technological opportunities, system trade studies, feasibility experiments, system operational requirements, system requirements definition, system performance requirements, and functional architecture definition.

3. Identify systems engineering activities associated with engineering development including TRL, advanced design, engineering design, and integration and test. Items to be addressed include risk abatement through the development of proof of concept and prototype articles, the development of reliability engineering, requirements verification and validation, integration, and operational evaluation.

4. Identify systems engineering activities associated with the post development operation and support phase. The focus shall be on the role that systems engineering will play in achieving a seamless transition to an operational environment without impacting current operational activities. Items to be addressed shall include the transition activities required for transition from a development to operational environment including system preparation, configuration management, documentation, training and continued sustainment through enhancements.

5. Specify how the areas of specialty integration are to be integrated into the system design and development, including reliability, maintainability, and availability engineering, producibility engineering, safety engineering, and human factors engineering.

6. Show the organization, roles, and responsibilities of the SENSE Contractor and subcontractors with regard to systems engineering function and NASA’s involvement in the contractors’ process and boards. Document how team members will be trained in the application of systems engineering methodologies.

7. Describe the process the approval and maintenance of decisions attained pertaining to systems engineering activities.

8. Identify all active participants in the process and their prospective roles and responsibilities to one another.

9. Provide the systems engineering process details and related procedures, methods, tools, and metrics. Include here, or in an appendix, the specific methodologies to be used for systems engineering activities identification, analysis, planning, tracking, and controlling.

10. Describe how systems engineering information will be communicated both internally to the contractor staff, externally to subcontractor staff and throughout the NASA management chain.

11. Provide an overview of the systems engineering process and information flow; describe how the process integrates and relates to other operations, maintenance, sustaining, development, and project management activities.

12. Describe how technical performance measurement; risk management, and program management activities will be incorporated with systems engineering strategies as they pertain to the development of SENSE wide systems.

The SEMP shall incorporate a Transition to Operations (T2O) Plan which shall define in detail the procedure for transitioning the ESC Systems into Operations. The T2O Plan shall include:

• The Transition to Operations Plan.

• The conditions to be met prior to transition, any phasing of transition, inclusion of over-the-shoulder monitoring on the part of both the Government prior to transition and the Contractor personnel just prior to Government acceptance.

• The initial transition of the ESC Systems capabilities into Operations and the subsequent transition of the operations support and sustainment.

• The steps taken to ensure that the safety of ESC Systems is maintained through the transition process.

• A transition and operations support schedule including milestone events, consistent with the IMP/IMS, detailing the entrance, success, and exit criteria.

• A document overview that summarizes the purpose and contents of this document and any security or privacy considerations associated with its use.

• The relationship of the T2O plan to other plans.

• A list containing the number, title, revision, and date of all documents cited within.

• The resources needed to support the deliverable hardware and software, including items needed to control, copy, and distribute the software and its documentation, to specify, design, implement, document, test, evaluate, control, copy, and distribute modifications to the software and to maintain, trouble shoot, repair, replace, and upgrade hardware.

• The purpose of the facilities needed to support the ESC Systems deliverables, including special buildings, rooms, mock-ups, building features such as raised flooring or cabling; building features to support security and privacy requirements, building features to support safety requirements (smoke alarms, safety glass, etc.), and special power requirements. Diagrams may be included as applicable.

• The delivered hardware and associated documentation, which may include computers, peripheral equipment, hardware simulators, stimulators, emulators, diagnostic equipment, and non-computer equipment.

• The Hardware description which shall include specific models, versions, and configurations, rationale for the selected hardware, reference to user/operator manuals or instructions for each item, as applicable, information about manufacturer support, licensing, and data rights, including whether the item is currently supported by the manufacturer, whether it is expected to be supported at the time of delivery, whether licenses will be assigned to the Government, and the terms of such licenses, and security and privacy considerations, limitations, or other items of interest.

• The software and associated documentation needed to support the deliverable software, including specific names, identification numbers, version numbers, release numbers, and configurations, as applicable; rationale for the selected software; reference to user/operator manuals or instructions for each item, as applicable; information about vendor support, licensing, and data rights, including whether the item is currently supported by the vendor, whether it is expected to be supported at the time of delivery, whether licenses will be assigned to the Government, and the terms of such licenses; and security and privacy considerations, limitations, and other items of interest.

• Any other documentation needed to support the deliverable hardware and software including, for example, plans, reports, studies, specifications, design descriptions, test cases/procedures, test reports, user/operator manuals, and support manuals for the deliverable hardware and software. This Other Documentation shall provide names, identification numbers, model and serial numbers, version numbers, and release numbers, as applicable; rationale for including each document in the list; information about licensing and data rights; and security and privacy considerations, limitations, or other items of interest.

• The personnel needed to support the deliverable hardware and software, including anticipated number of personnel, types and levels of skills and expertise.

• Any other resources needed to support the deliverable hardware and software, including any consumables together with an estimate of the type and number that should be acquired.

• The interrelationships of the components identified in the preceding requirements, using diagrams as appropriate.

• All procedures, including and reflecting lessons learned, for supporting the deliverable hardware and software and associated support capabilities.

• Contractor’s plans for training, including the schedule, duration, and location for the training;

the delineation between classroom training and "hands-on" training; and the provision (either directly or by reference) for familiarization with the operational hardware and software and familiarization with the support hardware and software and host systems.

• Anticipated areas of change to the deliverable hardware and software.

• All activities to be performed to transition the deliverable hardware and software to the

Government, including planning/coordination meetings; preparation of items to be delivered to the Government; packaging, shipment, installation, and checkout of the hardware and software support environment; packaging, shipment, installation, and checkout of the operational hardware and software; and training of support personnel.

• Roles and responsibilities for each transition and operations activity, the resources needed to carry out the transition and operations support activities, and the source from which each resource will be provided

• Activity schedules and milestones, consistent with the IMP and IMS, for conducting the transition and operations support activities.

• The proposed Operations Support metrics and the process for utilizing the metrics to adjust the operations support and logistics support activities based on cost and mission performance considerations.

APPLICABLE DOCUMENTS:

a. GPR 7123.1 - Systems Engineering

b. Approved SENSE Integrated Management Plan (MGT-01)

Sustaining

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: SUS-01

2. TITLE: Reliability, Maintainability, and Sustaining

Plan

3. DATE: 30 Jan 2017

4. DESCRIPTION/PURPOSE:

Plan to establish and document Reliability and Maintainability operational performance requirements and maintenance concepts for the SENSE systems consistent with the networks mission requirements and performance metrics.

5. DATA REQUIREMENTS:

CONTENT:

Plan shall establish a cost effective approach to ensure reliability, maintainability, and availability of SENSE systems. Plan shall address maintenance schedule, and implementing procedures, systems calibration, and metrics which demonstrate ability to support missions. Plan shall address the replacement of obsolete and non-maintainable systems mitigating risk to SENSE service.

The annual listing of candidates for replacement shall include the technical details for upgrade including risk and lifecycle cost benefit to NASA and be ranked in priority order for each network.

a. NPD 8720.1, NASA Reliability and Maintainability (R&M) Program Policy

b. NASA-STD-8729.1, Planning, Developing and Managing an Effective Reliability and

Maintainability (R&M) Program

Operations

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: OPS-02

2. TITLE: Continuity of Operations Plans and Procedures 3. DATE: 30 Jan 2017

4. DESCRIPTION/PURPOSE: Plan and procedures to implement and provide Continuity of Operations for all networks.

5. DATA REQUIREMENTS:

CONTENTS:

The Continuity of Operations Plans (COOP) shall be updated and exercised on a regular basis.

The plan shall incorporate strategies for maintaining the four critical areas of leadership, staffing, communications/technology and facilities for information systems that are categorized by Federal Information Security Modernization Act (FISMA) as Mission Essential Infrastructure (MEI)-High and facilities that are designated as NASA Critical Infrastructure (NCI).

Emergency Preparedness and Disaster Recovery Plans for the SN facilities are delivered with DRD

SMA-04.

The plan shall include resolution of unusual or emergency situations. The plan shall identify how the Contractor will assist NASA, within the general scope of work, but in currently unidentified ways, in preparation for, or in response to emergencies.

APPLICABLE DOCUMENTS:

a. NPD 1040.4: NASA Continuity of Operation

b. NPR 1040.1: NASA Continuity of Operations (COOP) Planning Procedural Requirements

c. FAR 18.001: Emergency Acquisitions

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: OPS-03

2. TITLE: Government Property Management &

Logistics Plan

3. DATE: 1/23/17

4. DESCRIPTION/PURPOSE:

Describe the method of administering Government property.

5. DATA REQUIREMENTS:

CONTENT:

The Property Management Plan shall describe the approach to account for NASA property, supplies, equipment, and transportation assets and services acquired or utilized by their respective program or project. This plan shall consist of those procedures which constitute the contractor's Property Management & Logistics Manual and shall include at a minimum the following categories:

• Property Management

• Acquisition

• Receiving

• Identification

• Records

• Utilization

• Maintenance

• Subcontractor Control

• Disposition

• Contractor Closeout

• Movement

• Storage

• Physical Inventories

• Reconcile Contractor Records with Financial Records

• Facility-Unique Considerations

• Transportation and Packaging

• Decommissioning and Disposal

a. FAR Part 45, Government Property

b. NFS Part 1845, Government Property

c. NPR 1620.3, Physical Security Requirements for NASA Facilities and Property

d. NPD 4200.1, Equipment Management

e. NPR 4200.1, NASA Equipment Management Procedural Requirements

f. NPD 4300.1, NASA Personal Property Disposal Policy

g. NPR 4300.1, NASA Personal Property Disposal Procedural Requirements

h. NPR 6000.1, Requirements for Packaging, Handling, and Transportation for Aeronautical and

Space Systems, Equipment, and Associated Components

i. NPR 6200.1, NASA Transportation and General Traffic Management

j. NPD 7500.1, Program and Project Life-Cycle Logistics Support Policy

k. GPR 6400.1, Logistics Support

Facilities

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: FAC-02

2. TITLE: Environmental Management Plan 3. DATE: 1/23/17

4. DESCRIPTION/PURPOSE:

To describe the contractor’s management approach, processes, organization, and standards for environmental management.

5. DATA REQUIREMENTS:

CONTENT:

The Environmental Management Plan shall describe the contractor’s management approach, processes, organization, and standards for environmental management, in compliance with the SENSE SOW, Applicable Documents, and task order requirements. At a minimum, the Plan shall describe:

• The contractor’s approach to meet environmental procedural requirements for each site/facility as required by task order;

• The organization, roles, and responsibilities of program, project, customer, and supplier personnel with regard to the environmental management;

• Documented procedures, engineering controls or other appropriate methods to maintain compliance with NASA and GSFC requirements and goals;

• Methodology for handling corrective and preventive action to resolve environmental nonconformance or non-compliance when identified;

• System for maintaining, calibrating, and repairing all equipment in order to prevent an environmental nonconformance or noncompliance; and

• Records maintenance and reports submittal required by directives and procedures, as applicable.

a. GPD 8500.1 – Environmental Policy and Program Management

b. GPR 8500.1 – Environmental Planning and Impact Assessment

c. GPR 8500.3 – Waste Management;

d. GPR 8500.4 – Air Quality Management Program

e. GPR 8500.5 – Water Management

f. GPR 8500.8 – Site Investigation and Remediation

g. GPR 4100.2 – Hazardous Material Data Management

h. NPR 8553.1 – NASA Environmental Management System

i. NPR 8580.1 – NASA National Environmental Policy Act Management Requirements

j. NEPA – National Environmental Policy Act

k. ASTM E1527-13 – Phase I Environmental Site Assessment

l. Exec. Order 12114: “Environmental Effects Abroad of Major Federal Actions”

m. NHPA, Section 106: “Section 106 of the National Historic Preservation Act”

REFERENCE DOCUMENTS:

a. Approved SENSE Facilities Management Plan (FAC-01)

b. Approved SENSE Facilities Master Plan (FAC-04)

Security

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: SEC-01

2. TITLE: Security Management Plan 3. DATE: 2 February 2017

4. DESCRIPTION/PURPOSE: The plan shall describe the contractor’s management approach and processes for accomplishing the security requirements of the contract.

5. DATA REQUIREMENTS:

Applicable Documents

DD 254

Contents The plan shall describe the industrial, physical, personnel, information (INFOSEC) and communications (COMSEC) safeguards for use in performance of this contract.

The Security Management Plan shall identify security controls in place at contractor, subcontractor and commercial provider sites, and for NASA GFP. This Plan shall address

• industrial

• physical

• personnel

• information (INFOSEC)

• communications (COMSEC)

• Inspections

• Reporting

• Waivers

Additionally, the Plan shall define the process for addressing Risk/Vulnerability and define a process for delivering reports as need. This section of the Plan shall identify and potential Risk or Vulnerability to any SENSE network site, facility, and/or asset that could cause potential harm to the personnel or disrupt network operations, etc.

The Plan shall include a section specifically addressing Physical Security, and a section specifically addressing Operations Security. The section of the Plan shall include the necessary information to demonstrate the contractor understands all aspects of providing physical security for SENSE personnel, sites and facilities and all network assets.

• SENSE DD 254

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: SEC-02

2. TITLE: IT Systems Security Plan 3. DATE: 2 February 2017

4. DESCRIPTION/PURPOSE: Identify the information technology (IT) system authorization boundary, IT system components in detail, and the operating environment of the system.

Identify the IT security requirements of the system, the IT security controls applicable to the system as well as any tailoring or scoping with rationale, description of interconnectivity to other systems, and implementation details for each security control for each unique set of components. Provide assessment of information security risk of the system and contingency plans for maintaining the operation of the system.

5. DATA REQUIREMENTS:

Contents The plan shall be divided into separate documents by subsystems, information security levels, or other logical boundaries for readability, maintainability, and usability.

The IT System Security Plan (SSP) shall cover all information technology components developed, operated, or maintained under the scope of the contract. Note that the SSP may be divided as indicated in the data preparation information such that the aggregate of all SSPs cover all components in scope.

A. Description of Information System

a. Operational Environment

b. Information Types

c. Security Categories

d. System Boundary

e. Hardware

f. Software

g. Networks

h. Interconnections with Other Systems

i. Points of Contact

B. Requirements and Control Implementation

a. Selected security controls

b. Tailoring and scoping of security controls

c. Inherited or common controls

d. Implementation details of security controls

C. Risk Assessment Report

a. Threats and vulnerabilities relevant to the system

b. Assessment of likelihoods

c. Assessment of impacts

d. Assessment of residual risk

D. Contingency Plan

a. Mission essential and business functions and associated contingency requirements

b. Recovery objectives, restoration priorities, and metrics

c. Contingency roles, responsibilities, and assigned individuals with associated activities and contact information

d. Essential functions that must continue regardless of disruption, compromise or failure

e. Business impact assessment

A separate IT SSP may be required for IT systems that support the different SENSE networks.

• NPR 2810.1A Security of Information Technology

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: SEC-04

2. TITLE: TDRS Protection Plan 3. DATE: 2 February 2017

4. DESCRIPTION/PURPOSE: The plan shall identify security control procedures that can be exercised on a routine basis to ensure protection strategies are satisfied and TDRS space system vulnerabilities are mitigated, in compliance with the requirements set forth in the most current version of GPD 7120.1.

5. DATA REQUIREMENTS:

Contents At a minimum, the Plan shall describe:

a. The contractor’s approach to the preparation of threat summaries;

b. Information details regarding TDRS protection plans;

c. Protection strategies appropriate for the threats and risk levels identified, and;

d. The processes for compliance with the TDRS’s space asset protection requirements.

GPD 7120.1, Goddard Space Flight Center (GSFC) Space Asset Protection Policy

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: SEC-05

2. TITLE: IT Security Management Plan 3. DATE: 23 February 2017

4. DESCRIPTION/PURPOSE: Deliver an overarching plan for managing all the IT systems across the SENSE Task orders and networks

5. DATA REQUIREMENTS: The IT Security management Plan shall include the following information

1. Contract Identification

1.1.Contract Name 1.2.Contract Number 1.3.Responsible Organization 1.4.Contact Information 1.5.General Contract Description

1.5.1. Information System Categorization

1.5.2. Security Categorization

1.5.3. Information System

1.5.4. Contractor Badging

1.5.5. Supply Chain Risk Management

1.5.6. Related Laws/Regulations/Policies

2. Security Controls Implementations

APPLICABLE DOCUMENTS:

• NPD 2810.1E: NASA Information Security Policy

• NPR 2810.1A: Security of Information Technology, including all referenced IT Security

Handbooks

• NFS 1852.204-76: Security Requirements for Unclassified Information Technology Resources

• NASA-STD-2804: Minimum Interoperability Software Suite

• NASA-STD-2805: Minimum Hardware Configurations

• CNSSP No. 11: National Policy Governing the Acquisition of Information Assurance and IA-

Enabled Information Technology Products

• NIST Special Publication (SP) 800-37: Guide for Applying the Risk Management Framework to

Federal Information Systems: a Security Life Cycle Approach

• NIST SP 800-30: Guide for Conducting Risk Assessments

• NIST SP 800-39: Managing Information Security Risk: Organization, Mission, and Information

System View

Reference Documents SEC-02,IT Systems Security Plan

Safety and Mission Assurance

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: SMA-01

2. TITLE: Mission Assurance

Implementation Plan (MAIP)

3. DATE:

4. DESCRIPTION/PURPOSE: Documents the Offeror’s plan for providing safety and mission assurance services

5. DATA REQUIREMENTS:

Prepare a MAIP addressing all requirements in the MAR.

The MAIP shall parallel the structure and content of the MAR and should contain the following.

1. The MAIP shall define a process for continually monitoring, identifying an correcting deficiencies.

2. The methodology shall identify (e.g. 100% inspection, planned sampling, random sampling customer complaints, third party registration, or incidental inspections) the process to determine whether performance requirements in the IDIQ task orders are met.

3. The plan shall describe where measurements of performance are subjective or objective and shall identify the quality, quantity and timeliness of the services provided.

4. The plan shall describe the approach to implement the required quality and workmanship standards

a. Explaining how they will be applied to reduce program risk

b. Address, as a minimum the role of the quality management approach in design and development (with particular emphasis on addressing key product characteristics), manufacturing, planning and key program events (as applicable).

5. The plan shall identify any current company and site certifications including:

a. Evidence of SAE AS9100 third party certification or registration of the

Offeror’s quality management system by a AS9100 accredited registrar

b. Evidence of CMMI®-DEV Capability Level 3, or higher, as measured by a

Software Engineering Institute (SEI).

6. System Safety Program Plan (SSPP): Describe how the project will implement its safety program in compliance with MAR requirements. Integration of system/facility safety provisions into the SSPP is vital to the early implementation and ultimate success of the safety effort.

7. Reliability, Maintainability and Availability approach.

8. Software Assurance Program demonstrating compliance with NASA standards for software assurance and software safety. (NASA-STD-8739.8 NASA Standard for Software Assurance, NASA-STD-8719.13C Software Safety Standard)

9. Verification and Validation Approach.

Applicable Documents

a. NASA-STD-8739.8 NASA Software Assurance Standard

b. NASA-STD-8719.13C Software Safety Standard

c. Mission Assurance Requirements (MAR) for the SENSE Contract

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: SMA-02

2. TITLE: Mission Assurance Compliance

Matrix

3. DATE: 30 Jan 2107

4. DESCRIPTION/PURPOSE:

Documents the Contractor’s compliance with the contractual system safety and mission assurance requirements.

5. DATA REQUIREMENTS:

Place/Time/Purpose of Delivery:

- Deliver plan to the applicable ESC Project(s) sixty (60) days after contract award for information

Deliver updates to the plan to the applicable ESC Project(s) thirty (30) days prior to implementation for information

Preparation Information:

The Mission Assurance Compliance Matrix shall address the contractual system safety and mission assurance requirements as applied to:

- All ground system hardware and software that is designed, built, or provided by the

Contractor and its subcontractors, or furnished by the government, from project initiation through launch and mission operations

- Ground system facilities

- Simulation/Modeling and test tools

- Antennas and associated housing

The Mission Assurance Compliance Matrix shall identify variances and acceptance rationale for processes, procedures, and standards that are proposed as alternatives to the contractual requirements.

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: SMA-04

2. TITLE: Emergency Preparedness and

Disaster Recover Plans

3. DATE: 30 Jan 2017

4. DESCRIPTION/PURPOSE: To describe the contractor's approach for emergency preparedness and disaster recovery plans to reduce operational effects of a disaster on NASA mission-critical and/or time-sensitive essential operations through a set of predefined and flexible procedures.

SCOPE: The Disaster Recovery Plans for the Space Network, Ground Network, SLR, VLBI, ESTL sites

APPLICABLE DOCUMENTS:

a. NPD 8710.1, Emergency Preparedness Program

b. NPR 8710.1, NASA Emergency Preparedness Program

c. NPR 8715.2, NASA Emergency Preparedness Plan, Procedures and Guidelines

d. NPR 8715.3, NASA Safety Manual

e. QS-EPP-95-001 NASA Emergency Preparedness Plan

f. GPR 8710.2, Emergency Preparedness Program Plan for Greenbelt

g. JPD 1040.2D, JSC Emergency Preparedness Program (JEPP)

h. KNPD 8710.1, KSC Emergency Preparedness Program Policy

i. JHB 2000, Consolidated Comprehensive Emergency Management Plan (KSC)

j. JDP-KSC-P-3006, Hurricane Preparation and Recovery

k. 803-PLAN-0002, Hurricane Nor’Easter Preparedness Plan For Wallops Flight

Facility

l. Near Earth Networks Services Emergency Preparedness and Disaster Recovery

Plan (EPDRP), NENS-PMO-PLAN-0030

m. White Sands Complex Emergency Preparedness and Disaster Recovery Plan

(EPDRP), NENS-SN-PLAN-0001.

n. Wallops Flight Facility Emergency Preparedness and Disaster Recovery Plan

(EPDRP), NENS-GN-PLAN-0002.

o. Merritt Island Launch Annex Emergency Preparedness and Disaster Recovery

Plan (EPDRP), NENS-GN-PLAN-0016.

p. Kokee Park Geophysical Observatory Emergency Preparedness and Disaster

Recovery Plan (EPDRP), NENS-CCE-PLAN-0040.

q. MOBLAS-4 Laser Tracking Station Emergency Preparedness and Disaster

Recovery Plan (EPDRP), NENS-CCE-PLAN-0041.

CONTENTS: The Disaster Recovery Plan shall include or reference, as applicable, the following: a risk analysis of all critical facilities/systems; identification of specific equipment/facilities that require backup or alternate sites; identification of backup strategies; emergency response plans; backup facility/alternate sites operating plans.

DATA REQUIREMENTS DESCRIPTION (DRD) 1. IDENTIFIER: SMA-15

2. TITLE: Laser Safety Plan 3. DATE:

4. DESCRIPTION/PURPOSE: laser safety manual

5. DATA REQUIREMENTS:

1. DATA REQUIREMENTS:

Contents

A detailed Laser Safety Plan shall be developed and address the authorized coordination, use, and safety/hazard analysis for laser systems used in Satellite Laser Ranging.

Applicable Documents

GPR 1860.2C, Laser Radiation Protection GSFC Form 23-6L, Laser Radiation Source Approval GSFC Form 23-35LU, Laser Radiation Source Personnel Approval AC No: 70-1, Federal Aviation Administration Advisory Circular on Outdoor Laser Operations.

MOBLAS 7 04-0034b GSFC 23-28L 532nm: Request for Radiation Safety Committee Action – Laser Radiation Source Questionnaire

Reference Documents

SCNS-SLR-PLAN-0003, Laser Safety Plan.

SCNS-PMO-PLAN-0017, SCNS Safety and Health Plan.

SCNS-PMO-SOP-0023, SCNS Standard Operating Procedure for the Control of Hazardous

Energy (Lockout Tagout).

SCNS-PMO-SOP-0024, SCNS Standard Operating Procedure for Performing Live

Electrical Work.

NSLR-06-0012, SLR Safety Logbook.

NSLR-06-0003, Laser Hazard Reduction System and Laser Interlock Verification

Procedure.

NSLR-06-0013, SLR Safety Handbook.