MSOC Statement of Work (SOW).pdf

Mission Systems Operations Contract (MSOC) Mod 5 Section C: Statement of Work Contract # 80JSC017C0006

C-1

Mission Systems Operations Contract (MSOC)

Statement of Work

Section C

Mission Systems Operations Contract (MSOC) Mod 5

C-2

TABLE OF CONTENTS

TABLE OF CONTENTS 2

1.0 MISSION SYSTEMS OPERATIONS CONTRACT OVERVIEW 5

1.1 Description of Programmatic Support 5

1.2 Description of Flight Operations Mission Systems 5

1.2.1 Mission Control Center Systems (MCCS) 6

1.2.2 Training Systems (TS) 7

1.2.3 Integration & Test Environments 8

1.2.4 Development Environments 8

1.2.5 Space Vehicle Mockup Facility (SVMF) 9

1.2.6 Mission Systems Security Center (MSSC) 10

2.0 CONTRACT MANAGEMENT 11

2.1 Financial and Contract Performance 11

2.1.1 Financial Reporting Form NF533 11

2.1.2 Supplemental Cost Reports (SCRs) 12

2.1.3 Other Financial Information 12

2.1.4 Information Technology (IT) Plan 12

2.2 Contract Communications 12

2.2.1 Subcontracts 12

2.2.2 Organizational Conflict of Interest (OCI) 12

2.2.3 Associate Contractor Agreements (ACAs) 13

2.3 Technical Metrics 13

2.4 Logistics 13

2.5 Collaboration 13

2.6 Security 14

2.6.1 Emergency Preparedness 14

2.6.2 Information Technology (IT) Security 14

2.6.3 Export Control 15

2.7 Documentation Management 15

2.8 Safety and Health Management 15

2.9 Environmental and Energy Conservation 16

Mission Systems Operations Contract (MSOC) Mod 5

C-3

2.10 Quality Assurance (QA) 17

2.11 Risk Management 18

2.12 Certification of Flight Readiness (CoFR) 18

2.13 Contract Configuration Management 18

2.14 Property 19

2.14.1 Government Property 19

2.14.2 Contractor-Owned Capital Property 20

2.15 Contract Management Special Projects (Indefinite Delivery, Indefinite Quantity (IDIQ))

3.0 MISSION SYSTEMS SUPPORT 21

3.1 Common Mission Systems Support 21

3.1.1 Management 22

3.1.2 Development, Modification, and Systems Engineering 25

3.1.3 Maintenance and Sustaining Engineering 27

3.1.4 Operations 28

3.1.5 Performance Standards 30

3.1.6 Test and Checkout 32

3.1.7 Interface Support 32

3.1.8 Certification and Training 33

3.1.9 Metrics/Data and Reports 33

3.1.10 Requirements Documentation 33

3.1.11 Special Projects (Indefinite Delivery, Indefinite Quantity (IDIQ)) 34

3.2 Unique Mission Systems Support 34

3.2.1 Mission Control Center Systems (MCCS) Support 34

3.2.2 Training Systems (TS) Support 37

3.2.3 Integration and Test Environment Support 39

3.2.4 Development Environments Support 41

3.2.5 Space Vehicle Mockup Facility (SVMF) Support 42

3.3 Mission Systems Engineering and Support Services (Level of Effort

(LOE))

3.3.1 Ground Segment Control Board (GSCB) 46

3.3.2 Program Requirements Document (PRD) 47

3.3.3 Human Space Flight (HSF) Network Operations Integration 47

C-4

Mission Systems Operations Contract (MSOC) Section C: Statement of Work

Mod 5 Contract # 80JSC017C0006

3.3.4 Systems Engineering and Integration Support 49

3.3.5 Architectural and Engineering Support 49

3.3.6 Mockup Management 49

3.3.7 Test Direction 50

3.3.8 Facility Management 50

ACRONYMS 51

C-5

Section C: Statement of Work

1.0 MISSION SYSTEMS OPERATIONS CONTRACT OVERVIEW

The Mission Systems Operations Contract (MSOC) specifies technical, managerial, and administrative work needed to ensure the availability, integrity, reliability, and security of the Flight Operations Directorate’s (FOD) Mission Systems supporting National Aeronautics and Space Administration (NASA) space flight programs requiring mission operations support. For this contract, “Mission Systems” is defined as the systems and subsystems of integrated hardware, software, networks, data, displays, and mockups used in the preparation for and performance of mission operations.

The objective of this contract is to maintain and improve safe, secure, effective, and cost efficient operations of the Mission Systems. Improvements in efficiency will increase the capacity to perform problem resolution, system improvements, and new development without compromising Mission Systems functionality or performance.

Section 1 serves as an information-only introduction to the Statement of Work (SOW).

1.1 Description of Programmatic Support

Mission Systems currently support the International Space Station (ISS) Program, including International Partner (IP) and Commercial Visiting Vehicles, the Orion Program, the Space Launch System (SLS) Program, and the Commercial Crew Program (CCP). Mission Systems supporting these programs are under development and/or modification in concert with program formulation and implementation. MSOC applies to the Mission Systems for all of these programs, and any other programs or missions requiring Mission Systems support. In addition, future (currently undefined) Mission Systems and capabilities are within the technical scope of this SOW, and MSOC work associated with these Mission Systems will be enabled through Indefinite Delivery, Indefinite Quantity (IDIQ) Delivery Orders.

Mission Systems support the following functions:

• Planning – Design, analysis, and management of trajectories and vehicle systems; and plan flight and crew activities relative to mission requirements, before, during, and after missions.

• Training – Execution of crew, flight controller, and instructor training and certification.

• Flight Operations – Real-time command and control of vehicle and crew systems involving telemetry monitoring, commanding, analysis (real-time and post-flight), communications, real-time and near real-time support for troubleshooting of on-orbit anomalies, data distribution, data storage, and data archiving.

• Vehicle Development –Test and checkout of new and existing space vehicles.

1.2 Description of Flight Operations Mission Systems

The following paragraphs describe the Mission Systems that are within the scope of

MSOC.

C-6

Section C: Statement of Work

1.2.1 Mission Control Center Systems (MCCS)

The Mission Control Center Systems (MCCS) provides a set of functional capabilities for command, control, and support of space vehicles and their payload elements. The MCCS enterprise spans two security zones: high and moderate. The high security zone is a physically separated set of information technology (IT) infrastructure and computing devices that are required to ensure the safety, reliability, and availability of MCCS controlled/operated spacecraft and their crew. The moderate security zone is a set of IT infrastructure and computing devices that provide mission support functions and capabilities which reside on the institutional Johnson Space Center (JSC) campus network, controlled and managed by MCCS resources.

For contingency operations, Backup Control Center (BCC) capabilities and services are provided for each major MCCS subsystem element or function. As such, an environment in both a high security zone and a moderate security zone is provided to enable BCC operability.

1.2.1.1 Mission Control Center – Houston (MCC-H)

The Mission Control Center (MCC) – Houston (MCC-H) is an integrated spacecraft command and control facility capable of supporting multiple space flight programs. The MCC-H provides command, telemetry, trajectory, real-time mission re-planning, user applications, weather, video, and voice communication services to support mission operations, flight control team training, and testing.

Within the MCC-H, the Mission Critical Environment (MCE) in the high security zone provides capabilities for command and control, trajectory evaluation, and “safe haven” in the event the moderate security zone is unavailable. The Mission Support Environment (MSE) in the moderate security zone provides for administrative services, planning, and analysis.

The majority of the MCC-H is physically located at the JSC in the Building 30 Complex.

Some MCC-H assets are situated in locations other than the Building 30 Complex.

Refer to Attachment J-9, JSC On-Site Government Installation Accountable Property and Attachment J-18, List of Facilities for the locations.

Mission operations rooms within the MCC-H provide the physical location from which flight controllers support and operate spaceflight missions and vehicles. Rooms provided for this purpose include three large, dedicated Flight Control Rooms (FCRs), two Operations Suites, and multiple backrooms or Multi-Purpose Support Rooms (MPSRs) for flight controllers supporting FCR positions. Vehicle engineering support groups may support from Mission Evaluation Rooms (MERs) within Building 30, but the remote MCC-H services are frequently utilized for engineering support in lieu of dedicating floor space.

Most payload and science activities for the ISS Program are conducted out of the Payload Operations Integration Center (POIC) at the Marshall Space Flight Center (MSFC) with indirect support from MCC-H. However, MCC-H has been used for some payload operations with payload customers located in one of several payload support rooms.

C-7

Section C: Statement of Work

In addition to the operational support areas, MCC-H provides computational rooms for the IT infrastructure, warehousing and maintenance areas, and office space. MCC-H also includes the historic Apollo FCR.

1.2.1.2 Backup Control Center – Huntsville Operations Support Center (BCC-

HOSC) and White Sands Test Facility (WSTF) The BCC for mission critical systems is located at the MSFC, and the BCC for some of the mission support systems is located at the White Sands Test Facility (WSTF). These systems provide backup command and control functions to support ISS operations in case of the loss of command and control capabilities at MCC-H. The Contractor coordinates with the MSFC HOSC and the WSTF for services at these locations.

After a threat to the MCC-H has been identified, but prior to BCC activation, FOD may elect to deploy the BCC Advisory Team (BAT) to a remote, temporary location. If fully activated, the BAT would be responsible for MCC-H command and control until either handover to a team located at BCC-HOSC or until control is returned to MCC-H.

1.2.2 Training Systems (TS)

The TS consist of simulators and trainers that support full task and part task training required for crew, flight controller, and instructor training. These simulators and trainers operate on different types of simulator architectures.

The ISS Full Task Trainer (FTT) is located in Building 5S, and is capable of three simultaneous, independent simulation sessions. The Space Station Training Facility (SSTF) is the FTT and is composed of computing hardware, platform software, special-purpose interface devices, visual image processing, audio communications, mockups of ISS modules, and high fidelity simulation applications.

The U.S. modules/systems are integrated with the IP provided Russian Segment Trainer (RST), the Japanese Experiment Module (JEM) Systems Trainer (JST), and Columbus Trainer - U.S. (COL-TRU). Certain assets, like visual processing and crew station mockups, are allocated in a shared manner to one of the three simultaneous sessions.

The FTT is configured to provide generic or mission-specific ISS training. It utilizes actual ISS flight software and specific flight-equivalent hardware, such as the Portable Computer System (PCS) and Robotics Workstation (RWS). The FTT also supports MCC- H testing and ISS Procedure Verification (PV). ISS FTT simulations may be run in a standalone mode, integrated with the MCC-H or POIC at MSFC (this is commonly referred to as an integrated simulation).

The TS Part Task Trainers (PTTs) are located in Buildings 5S and 9 at JSC. These PTTs provide training for crew, flight controllers, and instructors with focus on one vehicle system at a time. The PTTs support limited integration of avionics and system resources (e.g., command and data management, power and thermal conditioning).

Each PTT is composed of a student station, instructor station, simulation computer, and realistic user interfaces like PCS and Station Support Computer (SSC) laptops. The PTT simulation fidelity is sufficient to support procedure development and analysis in addition to training. There are six PTT units, three located in Building 5S and three in Building 9 at JSC. One of the PTT rooms in Building 5S is host to a Soyuz trainer

C-8

Section C: Statement of Work consisting of simulation software provided by Russia running on hardware provided by NASA. The PTTs in Building 9 focus on Environmental Control and Life Support System (ECLSS) training for crewmembers in the ISS mockups within the Space Vehicle Mockup Facility (SVMF). In addition, PTT simulation loads are distributed to Russia, Europe, and Japan (and updated at those locations semi-annually) to provide an American Segment Trainer (AST) interface in support of IP training. The TS Flight Controller Part Task Trainers (FCPTTs) are located in six rooms on the first floor of Building 5S. Each FCPTT is composed of five flight controller workstations which can also serve as instructor stations. The FCPTT supports single system training and mini-simulation training activities. The TS Robotics Flight Controller Part Task Trainer (RFCPTT) is located on the third floor of Building 5S. The RFCPTT is used to train the robotics flight controller positions, for procedure verification, and command script building. It is also used for playback simulations, procedure development, and visiting vehicle grappling simulations.

The TS Dynamic Skills Trainer (DST) is a robotics trainer focusing on skills required by the crew to operate the ISS Mobile Servicing System (MSS) robotic arm. Each DST has a set of robotics hand controllers, a virtual Display Control Panel (DCP), monitors, a PCS, and an SSC. There are four DSTs located in Building 4S, one DST in Building 30A, and one DST at the Neutral Buoyancy Lab. There is also a DST in Star City, Russia, but the Contractor is only responsible for this DST’s hand controllers.

1.2.3 Integration & Test Environments

For select Mission Systems, the Integration and Test Environments provide an environment to verify functional requirements of system modifications and to perform regression testing. Some of these environments also provide the ability to test the Mission System’s response to hardware failures.

The Moderate Integration and Test Environment (MITE) provides an environment for verification and validation of application software targeted for the moderate security MSE as well as for integration and validation of external services, security services, and Mission Systems operations services.

The High Integration and Test Environment (HITE) provides a high-fidelity environment for verification and validation of platform services, internal services, security services, and application software targeted for deployment and operational use in the high security MCE. HITE also supports the development of ISS reconfiguration products.

The TS Software Production Environment (SPE) supports integration and testing of simulation loads. The SPE includes simulation host computers, workstations, and associated networks and servers to provide a testing environment equivalent to the operational environment.

1.2.4 Development Environments

Development environments for the MCCS and the TS allow the introduction and evaluation of development and sustaining modifications.

C-9

Section C: Statement of Work

The Mission Systems Development Environment (MSDE) environment provides software development, integration and test, and sustaining engineering support for all JSC MCCS software. The MSDE provides a set of functional capabilities necessary to establish an environment which facilitates all lifecycle phases and activities of hardware and software development for the MCCS. These environments support the critical and non-critical application software developed for the MCCS mission system.

The TS Software Development Environment (SDE) supports development, integration, and testing of simulation software. The SDE includes simulation host computers, workstations, and associated networks and servers to provide a testing environment equivalent to the operational environment.

1.2.5 Space Vehicle Mockup Facility (SVMF)

The SVMF is located in Building 9N and 9NW at JSC. It uses full-scale vehicle mockups, flight-like trainers, and engineering test articles to provide a unique environment that closely emulates the physical characteristics of crewed spacecraft. It provides capabilities for astronaut training, real-time mission trouble-shooting, mission development, flight procedures development and verification, flight vehicle sustaining engineering, and developmental engineering analysis. The SVMF also has visibility to NASA management, the media, and the general public.

The SVMF high bay area is ~57 feet high and covers ~73,125 square feet. Two overhead bridge cranes each have one 20-ton capacity hook and one 5-ton capacity hook. There is pressurized breathing air for use in space suits available from both bottles and human-rated air pumps located in the building. The SVMF includes two classrooms/changing rooms and a large (99 person capacity), SVMF-managed conference room. Audio and video links exist between most mockups in the SVMF and other buildings on site. An elevated enclosed walkway along the north wall provides visitors a view of the daily activities.

The SVMF has over 50 mockups and trainers for the ISS Program (including commercial partners), Orion, and past program training hardware. The mockups used in the SVMF are full-scale (1:1) models of spacecraft or spacecraft components.

Depending on their purpose, mockups can vary from low fidelity, which models the basic volume and shape of the spacecraft/component, to high fidelity which very closely matches the “look and feel” of the spacecraft/ component. Mockups may be built from corrugated plastic for temporary use (e.g., for short-term engineering evaluations) or from aluminum or steel for years of use. Small components for the mockups may be built using the SVMF’s 3-D printers. Simple mockups may be designed and modified/built by MSOC. Large, complex mockups may be provided by an external supplier. The SVMF also includes several unique capabilities to simulate weightless or partial gravity environments. The Precision Air Bearing Facility (PABF) provides a two-dimensional, three degree of freedom simulation of a weightless environment by floating objects on a thin cushion of air, similar to an air hockey table. The partial gravity simulator (POGO) uses a vertically oriented, manually adjusted, servo-controlled pneumatic cylinder to create a selectable offload that can simulate weightless or partial gravity environments.

C-10

Section C: Statement of Work

There are several computer systems within the SVMF. Some of these systems and their associated networks provide for training simulation capability within selected mockups while other computer systems are used to maintain the mockups and to configure them for use.

The SVMF includes storage space and a “light shop” with limited metalworking and woodworking capability in Building 59. Nearly all of the Building 59 shop work is performed by MSOC personnel. There are minimal shop assets in Building 9 with sewing capability and electrical workbench areas. There is also a large outdoor storage area (i.e. laydown yard) adjacent to the SVMF.

1.2.6 Mission Systems Security Center (MSSC)

The Mission Systems Security Center (MSSC) is located in Building 30. The MSSC monitors all Mission Systems elements and manages three Communications Security (COMSEC) Equipment Facilities (CEFs). MSSC personnel perform security operations and engineering services that include operations monitoring, incident management and reporting, threat intelligence management, and compliance management. MSSC personnel also manage classified equipment and manage the creation, storage, and destruction of classified materials.

C-11

Section C: Statement of Work

2.0 CONTRACT MANAGEMENT

All scope within this SOW will be considered baseline unless specifically identified as either IDIQ or Level of Effort (LOE).

The Contractor shall collaborate with NASA on strategic, innovative, and cost effective solutions for current and future operations that align with the NASA and FOD vision as it relates to this SOW.

The Contractor shall provide an efficient and aggressively cost effective management approach implementing the appropriate structure, processes, and controls and understanding the MSOC Contractor/Government relationship to manage delivery of the key Mission Systems support while meeting technical and performance requirements specified in this SOW. The Contractor shall organize and institute integrated processes and tools for managing the products and services specified in this SOW in accordance with the Management Plan (DRD-MSOC-0002) and in compliance with the definitions provided in the Attachment J-1, Glossary.

The Contractor shall define and institute processes to improve cost effectiveness in management, administration, development, modification, sustaining, maintenance, reconfiguration, operations, and decommissioning across all Mission Systems to increase the capacity to perform problem resolution, system improvements, and new development without compromising Mission Systems functionality or performance as specified via this SOW. The Contractor shall perform continuous improvement in accordance with the Continuous Improvement Plan (DRD-MSOC-0020).

The Contractor shall transition the work within this SOW to the follow-on contractor pursuant to the Phase-Out Plan (DRD-MSOC-0006).

2.1 Financial and Contract Performance

The Contractor shall provide and maintain financial and contract performance management data for the planning, tracking, accumulation, monitoring, contract cost, and contract performance to meet the budgeting, cost reporting, billing, and disclosure requirements of the contract.

The Contractor shall provide integrated financial and contract performance information at individual and assorted MSOC work breakdown structure (WBS) levels per MSOC Work Breakdown Structure (WBS) and Dictionary (DRD-MSOC-0001).

The Contractor shall provide financial management reports NF533 Cost Reporting (DRD-MSOC-0016), Status Reports and Reviews (DRD-MSOC-0012), and other business management and administrative reports as required.

2.1.1 Financial Reporting Form NF533

The Contractor’s financial reports shall comply with the most current version of NPR 9501.2, NASA Contractor Financial Management Reporting for procedures and guidelines. The supplemental cost data identified in Section 2.1.2, Customer Cost

C-12

Section C: Statement of Work

Report shall be reconcilable back to the NF533 per NF533 Cost Reporting (DRD- MSOC-0016) for the same accounting period.

2.1.2 Supplemental Cost Reports (SCRs)

The Contractor shall provide FOD Supplemental Cost Reports (SCRs) (DRD-MSOC- 0015) that provides full cost information by program and project.

2.1.3 Other Financial Information

The Contractor shall provide financial planning, historical information, technical support information, and support special requests for budget impacts upon NASA request (see Section 2.2, Contract Communications).

The Contractor shall provide and adhere to a Fiscal Year (FY) Technical Operating Plan (Tech Plan) and Planning, Programming, Budgeting, and Execution (PPBE)

(DRD-MSOC-0018).

2.1.4 Information Technology (IT) Plan

The Contractor shall institute processes for information technology (IT) planning and management, as defined by NPD 2800.1, Managing Information Technology for each Mission System.

The Contractor shall comply with federal and NASA IT planning and reporting regulations and requirements in accordance with Information Technology (IT) Capital Planning and Investment Control (CPIC) (DRD-MSOC-0010).

2.2 Contract Communications

Formal communications between NASA and the Contractor shall be via the Government provided electronic system. The system will be used for general communications, requests for information, submission of documentation, and as a cover for all technical direction. The system will also be used as a receipt/acknowledgment of and response to direction.

2.2.1 Subcontracts

The Contractor shall institute a plan for small business subcontracting and provide associated reports in accordance with the Small Business Subcontracting Plan and Reports (DRD-MSOC-0009).

The Contractor shall perform subcontract administration in accordance with the Management Plan (DRD-MSOC-0002).

2.2.2 Organizational Conflict of Interest (OCI)

The Contractor shall institute processes to assess, avoid, neutralize, mitigate, and report organizational conflicts of interest (OCI) in accordance with the Organizational Conflict of Interest (OCI) Plan (DRD-MSOC-0032). See also Attachment J-15, Government OCI Assessment of MSOC.

C-13

Section C: Statement of Work

The Contractor shall provide training to Contractor personnel regarding potential OCIs on the MSOC.

2.2.3 Associate Contractor Agreements (ACAs)

The Contractor shall establish Associate Contractor Agreements (ACAs) as required by NASA. Reference Clause H.10, ASSOCIATE CONTRACTOR AGREEMENT (ACA) FOR MSOC ACTIVITIES. The ACAs will specifically address all contractor roles, responsibilities, expectations, and a remedy process for problem resolution.

Additionally, the Contractor shall enter into ACAs with other contractors who depend on MSOC products to complete timely and quality work for FOD. The Contractor shall submit all ACAs to the MSOC Contracting Officer's Representative (COR) for acknowledgement.

2.3 Technical Metrics

The Contractor shall develop, implement, and maintain a set of technical performance measures aligned with MSOC functional areas in accordance with Technical Metrics Plan and Reports (DRD-MSOC-0007).

The Contractor shall utilize the technical metrics to formulate technical and managerial strategies and tactics for optimizing work and improving performance.

The Contractor systems for documenting and managing technical measures and tracking associated measurement values shall support electronic exchange of information with NASA as specified in the applicable Data Requirements Descriptions (DRDs).

2.4 Logistics

The Contractor shall provide logistical support (e.g., sparing, checkin/checkout, shipping, courier services, headset provision, and maintenance) to ensure sufficient planning, arrangements, and support for the activities comprising the technical, managerial, and administrative services specified in this SOW.

The Contractor shall be responsible for transporting items from JSC central receiving to MSOC on-site warehouses or on-site buildings as needed.

2.5 Collaboration

The Contractor shall cooperate with external organizations including NASA programs, other NASA field centers, and affiliated organizations that are tasked to provi de equipment or support to the MSOC Mission Systems as requested by NASA.

The Contractor shall support coordination of technical and schedule information pertaining to MSOC Mission Systems with these organizations subject to concurrence by the applicable NASA project manager and compliant with OCI provisions in Section 2.2.2, Organization Conflict of Interest (OCI).

C-14

Section C: Statement of Work

2.6 Security

The Contractor shall provide physical, administrative, information, communications, and IT security in accordance with the Contractor Security Management Plan (DRD-MSOC- 0030). The Contractor shall provide, maintain, and adhere to a Mission Systems Security Plan (DRD-MSOC-0031) that describes the security controls put in place for each MSOC Mission System and applicable missions supported by FOD.

The Contractor shall ensure completion of badging requirements and personnel security clearances to ensure employees are cleared for access to JSC and its associated facilities, as required.

The Contractor shall provide security engineering of secure Mission Systems through the implementation of and adherence to NASA and Department of Defense (DoD) regulations governing national security and national resource protection of COMSEC equipment. Refer to Attachment J-2, Applicable Documents.

The Contractor shall protect and manage both sensitive (non-classified) and classified information created, transmitted, processed, stored, or destroyed.

The Contractor shall conduct all IT security training through the System for Administration, Training, and Educational Resources for NASA (SATERN).

The Contractor shall provide and obtain COMSEC training and perform administrative COMSEC services (e.g. certification, accreditation, liaison support, audit support) as required.

The Contractor shall obtain National Security Facility Clearance Level (FCL) per Clause I.14, SECURITY CLASSIFICATION REQUIREMENTS up to TOP SECRET/SENSITIVE COMPARTMENTED INFORMATION (SCI) and as identified by the Government, obtain SECRET or TOP SECRET/SCI security clearances for personnel supporting functions identified by NASA as requiring these levels of clearance. NASA will sponsor TOP SECRET/SCI clearances.

2.6.1 Emergency Preparedness

The Contractor shall institute and implement processes and procedures to ensure emergency preparedness and disaster recovery in accordance with the Emergency Preparedness and Disaster Recovery Plan (DRD-MSOC-0011).

2.6.2 Information Technology (IT) Security

The Contractor shall implement an IT security program in compliance with NPD 2800.1, Managing Information Technology and in accordance with NPD 2810.1, NASA Information Security Policy.

The Contractor shall assist with the formulation of and comply with the JSC and FOD IT security programs which include a proactive cyber security element encompassing threat analysis and response. The Government will provide security intelligence, and the Contractor shall utilize additional sources as appropriate.

C-15

Section C: Statement of Work

The Contractor shall protect classified and sensitive information as well as Privacy Act information, proprietary data, export controlled data, and technology embargoed from foreign dissemination that is transmitted, stored, or processed in the Mission Systems.

The Contractor shall ensure that IT security is an integral part of all MSOC development, modification, maintenance, sustaining, and operations activities supporting FOD associated programs and missions.

NASA owns the architecture and the requirements as derived from federal, NASA, and FOD-unique mission policies, and is responsible for approving any changes to the Mission Systems architecture and the associated risk accompanying that change. The Contractor shall work with the NASA project manager to identify, assess, quantify, and recommend mitigation for the residual IT security risk in each applicable Mission System. Where changes to the baseline introduce IT security risks, the NASA project manager and the IT Security manager shall be the deciding officials, including the authority to change or waive the Mission Systems IT security requirement through the configuration management process in Section 3.1.1.1, Configuration Management. The NASA project manager and the IT Security manager have the joint responsibility for formally obtaining risk acceptance approvals from FOD management.

2.6.3 Export Control

The Contractor shall adhere to export control laws and regulations. The Contractor shall adhere to export control requirements in NPR 2190.1, NASA Export Control Program and JWI 2190.1, JSC Export Compliance.

2.7 Documentation Management

The Contractor shall manage and maintain the Government provided electronic documentation library.

The Contractor shall utilize the Government provided electronic documentation library to manage MSOC documentation to ensure controlled identification, versioning, retention, archiving, and access in accordance with the Records Management Plan (DRD-MSOC- 0033) and the Configuration Management Plan (DRD-MSOC-0044).

The Contractor shall accommodate the NASA review and approval cycle described in each Type 1 DRD prior to the Contractor’s work effort aligning with or accommodating the specifications for those DRDs.

The Contractor shall deliver DRDs on the date specified in the DRD. However, if the delivery date falls on a weekend or Federal holiday, then the Contractor shall deliver the DRD no later than the next NASA business day.

2.8 Safety and Health Management

The Contractor shall develop, document, implement, and maintain a safety and health program per System Safety Program Plan and Reports (DRD-MSOC-0024) in accordance with JPR 1700.1, JSC Safety and Health Handbook and JSC-36528, Volume 1, Flight Operations Directorate (FOD) Safety, Reliability and Quality Assurance (SR&QA) Plan.

C-16

Section C: Statement of Work

In accordance with this System Safety Program Plan, the Contractor shall:

• Develop and implement risk management techniques (including risk assessment) to be applied to hazards derived from analyses of activities and products for the purpose of eliminating or controlling hazards as specified in NASA policies and in accordance with requirements for hazard reduction in the Safety and Health Plan and Reports (DRD-MSOC-0021).

• Publish the annual safety and health self-evaluation report.

• Provide monthly safety and health metrics.

• Implement system safety engineering tasks for flight and institutional program activities and products in accordance with the schedule and applicable flight and institutional requirements as documented in a System Safety Program Plan and Reports (DRD-MSOC-0024).

• Provide feedback and lessons learned to employees following a mishap or incident.

The Contractor shall ensure that all users comply with the appropriate safety rules, regulations, documentation, and hazard analyses during all activities performed.

The Contractor shall comply with the latest revision of JPD 1710.1, Design, Inspection, and Certification of Pressure Vessels and Pressurized Systems and JPR 1710.13, Design, Inspection, and Certification of Ground-Based Pressure Vessels and Pressurized Systems.

2.9 Environmental and Energy Conservation

NASA is the owner and operator of record for all environmental activities conducted at NASA-owned properties, unless otherwise documented in a signed agreement between NASA and the Contractor. The Contractor is advised that activities performed at JSC and associated Mission Systems are subject to federal, state, and local regulatory agency inspections to review compliance with environmental laws and regulations. For on-site issues, JSC's Environmental Office is the single point of contact with federal, state, and local regulatory agencies and their representatives, unless otherwise directed by the Contracting Officer or the Environmental Office.

The Contractor shall ensure that all work performed and equipment used on-site at JSC, Ellington Field, Sonny Carter Training Facility (SCTF), and the El Paso Forward Operating Location (EPFOL) to fulfill the requirements of this contract are in compliance with all federal, state, and local regulations and public laws, and the following NASA JSC directives:

• JPD 8500.1, JSC Environmental Excellence Policy

• JPR 8550.1, JSC Environmental Compliance Procedural Requirements

• JPR 8553.1, JSC Environmental Management System Manual

• JWI 8553.1, EMS Aspect/Impact Assessment and EMP Process

C-17

Section C: Statement of Work

The Contractor shall provide data on annual sustainable acquisition, waste reduction activity, energy efficient product procurement, and ozone depleting substances in accordance with Environmental and Energy Consuming Product Compliance Reports

(DRD-MSOC-0023).

The Contractor shall immediately notify the JSC Environmental Office when contacted by external regulatory agency representatives and shall cooperate fully. The Contractor shall complete, maintain, and make available to the Contracting Officer, JSC Environmental Office or regulatory agency personnel all documentation relating to environmental compliance matters under applicable laws. The Contractor shall immediately notify the JSC Environmental Office upon issuance of a notice of violation or non-compliance to the Contractor.

Should a notice of violation, non-compliance, deficiency, or similar regulatory agency notice be issued to NASA as a facility owner/operator on account of the actions or inactions of the Contractor or one of its subcontractors in the performance of work under this contract, the Contractor shall fully cooperate with NASA in correcting any problems and defending against regulatory assessment of any civil fines or penalties arising out of such actions or inactions.

2.10 Quality Assurance (QA)

The Contractor shall establish a quality assurance (QA) program that is compliant with the International Organization for Standardization (ISO) document American Society for Quality Control (ASQC) ISO-9001-2008 – Model for Quality Assurance in Design/Development, Production, Installation, and Servicing.

In order to fulfill this quality program, the Contractor shall:

• Perform hardware and software QA.

• Provide a quality plan for on-site and off-site resources within this contract and implement a true peer review (i.e., QA designee) program as the primary method for all product assurance inspections in accordance with Quality Plan and Reports (DRD-MSOC-0025).

• Collect and compile information derived from Contractor data (e.g., test results, analysis reports, inspection records, discrepancy data, nonconformance data, delivery logs, internal audits, work authorization documents) to demonstrate that the products and services delivered to NASA are in compliance with the requirements and specifications as specified in this contract. The Contractor shall deliver compliance information at the request of NASA per the NASA surveillance plan.

• Report non-conformances in accordance with Non-conformance Record Template (DRD-MSOC-0028).

• Share information in accordance with the Government-Industry Data Exchange Program (GIDEP) and NASA Advisory Problem Data Sharing and Utilization Program Documentation and Reporting (DRD-MSOC-0027).

C-18

Section C: Statement of Work

NASA dispositions all nonconforming products except rework to specification. The Contractor shall track and status all nonconforming products per Section 3.1.1.4, Technical Problem Process.

The Contractor may use the Receiving Inspection and Test Facility (RITF) receiving inspection services for metallic and nonmetallic material properties analysis, destructive physical analysis, failure analysis of electronic components, and screen burn-in of electrical and electronic parts and components. The Contractor shall use the RITF training services for initial wire wrap certification.

The Contractor shall conduct internal audits. Process audits shall be performed at the request of the JSC Contracting Officer or the COR to provide a candid assessment of processes to identify generic system anomalies and areas for improvement.

The Contractor shall coordinate equipment calibration, recalibration, and maintenance to ensure that all equipment is fully functional and accurate. The Contractor shall calibrate Government and Contractor-owned inspection, measuring, and test equipment in accordance with JPR 1281.11, Metrology and Calibration.

The Contractor shall develop a software QA plan and provide reports in accordance with the Software Quality Assurance Plan and Reports (DRD-MSOC-0026).

The Contractor shall have an organizational process that produces software in accordance with NPR 7150.2, NASA Software Engineering Requirements and JSC - 63756, Mission Operations Directorate Software Management Plan.

The Contractor shall provide Acceptance Review Package (DRD-MSOC-0053) as required by NASA.

2.11 Risk Management

The Contractor shall institute processes for risk management in compliance with CA-WI- 18, FOD Risk Management Plan and in accordance with the Risk Management Plan

(DRD-MSOC-0003).

2.12 Certification of Flight Readiness (CoFR)

The Contractor shall provide Mission System integration and operations to ensure mission readiness of the Mission System to support the FOD Certificate of Flight Readiness (CoFR) process. The Contractor shall provide a Certificate of Flight Readiness Endorsement (CoFR) (DRD-MSOC-0040) for all Mission Systems for each mission.

2.13 Contract Configuration Management

The Contractor shall institute processes for managing changes to the contract baselines established on MSOC to enable tracking, assessment, disposition, and controlled incorporation of those changes by both the Contractor and NASA in accordance with the Configuration Management Plan (DRD-MSOC-0044).

C-19

Section C: Statement of Work

2.14 Property

The integrated physical equipment and software that represent the Mission Systems defined in this SOW are classified as Government property.

Attachment J-8, Off-Site Government Furnished Property, identifies all off-site Government property provided by NASA for MSOC use off site and to which NASA has title (see Clause G.8, LIST OF GOVERNMENT PROPERTY FURNISHED PURSUANT

TO FAR 52.245–1).

“Contractor-acquired property” means property acquired, fabricated, or otherwise provided by the Contractor as a direct contract charge to NASA for performing a contract and for which NASA has title (see Clause G.5, INSTALLATION-

ACCOUNTABLE GOVERNMENT PROPERTY).

Attachment J-9, JSC On-Site Government Installation Accountable Property identifies the on-site Government property made available on a no-charge basis for use in performance of MSOC (see Clause G.5, INSTALLATION-ACCOUNTABLE

GOVERNMENT PROPERTY).

The Contractor shall submit updates to these attachments not later than 30 days after the beginning of each FY.

Clause G.5, INSTALLATION-ACCOUNTABLE GOVERNMENT PROPERTY, identifies the on-site installation services made available to the Contractor on a no-charge basis for use in performance of MSOC. Office personal computers (PCs) are provided by an Information Resources Directorate (IRD) contractor, which is responsible for support and asset management of the PC hardware and all standard software.

2.14.1 Government Property

The Contractor shall document and maintain MSOC Government property management processes and procedures in accordance with the Government Property Management Plan (PMP) (DRD-MSOC-0008).

The Contractor shall utilize the Government’s property tracking system for MSOC property identified in Attachment J-9, JSC On-Site Government Installation Accountable Property. The Contractor shall provide custodians to input and manage data in the Government’s property tracking system for property provided under this contract.

The Contractor shall track and be accountable for MSOC Government property identified in Attachment J-8, Off-Site Government Furnished Property, and all Contractor-acquired off-site Government property with its own tracking system. The Contractor shall provide reports and inventories in accordance with Financial Reporting of Contractor- Held Property (DRD-MSOC-0014) and Reports Required for Logistics (DRD-MSOC- 0049).

The Contractor shall be the delegated property administrator and shall designate a point-of-contact for MSOC Government property administration and management.

C-20

Section C: Statement of Work

2.14.2 Contractor-Owned Capital Property

The Contractor shall track Contractor-owned capital property separately from Government property.

2.15 Contract Management Special Projects (Indefinite Delivery, Indefinite

Quantity (IDIQ)) All contract management special project support will be enabled through IDIQ.

C-21

Section C: Statement of Work

3.0 MISSION SYSTEMS SUPPORT

The Contractor shall manage, develop, modify, integrate, test, maintain, sustain, and operate all Mission Systems and supporting functions defined in this SOW. The Contractor shall also ensure the availability, integrity, security, and reliability of the Mission Systems.

Mission Systems support is categorized into three subareas: Common Mission Systems Support, Unique Mission Systems Support, and Mission Systems Engineering and Support Services.

3.1 Common Mission Systems Support

Common Mission Systems support is applicable to all Mission Systems and consists of management, system engineering, development, modification, maintenance, sustaining engineering, operations, decommissioning, reconfiguration, Mission System resource scheduling, performance standards, test and checkout, interface support, certification, training, travel, reports, and requirements documentation. The Contractor shall provide and adhere to a Systems Lifecycle Process (DRD-MSOC-0047).

The Contractor shall use the Government provided system for scheduling, allocating, configuring, and de-configuring Mission Systems resources.

The Contractor shall coordinate with JSC’s Center Operations Directorate for installation-provided services (e.g., power, heating, ventilation, air conditioning, and safety controls), and plant engineering and operations in accordance with requirements documents, including JSC-27049, Memorandum of Understanding and Standard Interface Plan Between Center Operations Directorate and Flight Operations Directorate.

The Contractor shall be responsible for technical power distribution (as defined in JSC- 27049) within each Mission System and for coordinating with plant engineering and operations to ensure proper environmental control for personnel and equipment.

The Contractor shall adhere to the standards and processes specified in JSC-63756, Mission Operations Directorate Software Management Plan (SMP) for all FOD software and supporting data files. For new or modified software and supporting data files to meet new requirements that are not compliant with the FOD SMP guidelines regarding software and supporting data files, the Contractor shall be responsible for requesting waivers or exceptions per the FOD SMP guidelines. For existing software and supporting data files that are currently in sustaining, it is assumed that the SMP documentation is adequate until such time that the software is modified to meet new requirements or it is deemed inadequate due to the needs of another project. In this circumstance, the Contractor shall evaluate the adequacy of the documentation and shall provide a recommendation to the Government on compliance, waiver, or exception per the SMP.

The Contractor shall support the addition of externally provided hardware, software, and mockups to the Mission Systems as requested via the change process defined in Section 3.1.1.3, Technical Change Process, via technical direction under Section 2.2, C-22

Section C: Statement of Work

Contract Communications, or via Section 3.1.11, Special Projects (Indefinite Delivery, Indefinite Quantity (IDIQ)).

NASA will permit the Contractor to utilize NASA’s Mission Systems and MSOC technical services (e.g. skills) for purposes other than MSOC contract performance as approved by the Government. The Contractor’s use of such property and capabilities shall be subject to the terms and conditions of this Contract, the Non-Government Use of Mission Systems Package (DRD-MSOC-0029), any related Space Act Agreements, and all other transactional authority or instruments. Utilization of Mission Systems and MSOC technical services shall be in accordance with Clause H.12, NON- GOVERNMENT USE OF NASA FACILITIES and Clause H.13, NO COST

REIMBURSEMENT OR FEE FOR BUSINESS DEVELOPMENT ASSOCIATED WITH

THE NON-GOVERNMENTAL USE OF NASA FACILITIES.

3.1.1 Management

The Contractor shall manage the Mission Systems covered by MSOC. The Contractor shall provide management and control of the Mission Systems hardware, software, and data configurations for the purpose of ensuring the Mission Systems are ready to provide Program and mission support for FOD.

The Contractor shall notify NASA management when out-of-family (off-nominal) events occur in the Mission Systems (e.g., close calls, mishaps, security breaches, critical IRs).

The Contractor shall comply with federal, agency, and JSC requirements for secure communications utilizing the COMSEC system. All personnel performing COMSEC requirements are required to have SECRET or TOP SECRET/SCI clearances as required by NASA. These systems will provide for classified communications and sensitive but unclassified (SBU) communications using administrative and physical controls. Refer to Attachment J-2, Applicable Documents.

The Contractor shall provide for proper handling, storage, and destruction of classified, SBU, and COMSEC documentation.

The Contractor shall provide encryption key management services, in accordance with secure communications requirements.

The Contractor shall assist with the maintenance and administration of the NASA COMSEC account for secure communications.

The Contractor shall provide configuration management and documentation maintenance of the NASA-owned Mission Systems architecture baselines and requirements.

The Contractor shall manage the integration of NASA-provided hardware and software into the Mission Systems as needed.

The Contractor shall provide software source code, executable code, and supporting data files per Government direction.

The Contractor shall provide and adhere to a Software Standards and Development Plan (DRD-MSOC-0057).

C-23

Section C: Statement of Work

The Contractor shall coordinate and integrate minor building upkeep to keep each building in showcase condition and shall at times perform minor building upkeep such as carpet installation, replacement, and cleaning. The Contractor shall monitor all public affairs-related displays and display areas and notify NASA when repairs, maintenance or upgrades are necessary.

3.1.1.1 Configuration Management

The Contractor shall institute and document processes and procedures for managing the configurations of all MSOC responsible assets (e.g., hardware, software, and data) to ensure controlled identification, versioning, and access, in accordance with the Configuration Management Plan (DRD-MSOC-0044).

The Contractor shall provide and update IT information in the System for Tracking and Registering Applications and Websites (STRAW). Additionally, the Contractor shall provide and update IT information for the NASA Data Center and Network worksheets in accordance with Information Technology (IT) Capital Planning and Investment Control (CPIC)…