Attachment_A_-_Draft_LSO_SOW_12Nov2024_1.pdf

LANDSAT SATELLITE OPERATIONS

STATEMENT OF WORK (SOW) - DRAFT

Table of Contents

1.0 Introduction

1.1 Purpose

1.2 Scope Summary

1.3 Period and Place of Performance

1.4 Applicable Documents

1.5 Reference Documents

2.0 Work Breakdown Structure

3.0 Project Management

3.1 Task Management

3.1.1 Personnel Staffing

3.1.2 Personnel Training and Certification

3.2 Schedule Management

3.3 Procurement Management

3.4 Property Management

3.5 Resource Management

3.6 Risk Management

3.7 Document Management

3.8 CDRL Management

3.9 Discrepancy and Problem Tracking

3.9.1 Mission-Level Discrepancy Tracking

3.9.2 Root Cause and Corrective Actions

3.10 Project Status Meetings and Reviews

3.10.1 Mission Annual Review

3.10.2 Monthly Project Status Review

3.10.3 Landsat Satellite Operations (LSO) Management Meeting

3.10.4 Landsat FOT Management Meeting

3.10.5 SGO Inter-organizational Technical Working Group

3.11 Travel

4.0 Flight Systems Operations and Sustaining Engineering

4.1 Observatory Sustaining Engineering

4.2 Observatory Performance Monitoring and Assessment

4.3 LMOC Performance Monitoring and Assessment

4.4 Observatory and Ground System Contingency Support

4.5 Flight Systems Meetings and Reviews

4.5.1 Engineering Meetings

5.0 LMOC Operations and Sustaining Engineering

5.1 LMOC Operations Engineering

5.2 LMOC Systems Sustaining Engineering

5.2.1 LMOC Hardware

5.2.2 LMOC Software

5.2.3 LMOC System Deliveries

5.3 Ground Systems Contingency Support

5.3.1 bLMOC Operations and Readiness

5.4 LMOC Infrastructure Support

5.4.1 Systems Administration

5.4.2 Network Infrastructure Support

5.4.3 Database Administration

5.4.4 IT Security

5.4.5 Configuration Management

5.4.6 Facilities

5.4.7 Property Management Support

5.4.8 Simulator Maintenance

5.5 LMOC Meetings, Boards, and Reviews

5.5.1 LMOC Discrepancy Review Board

5.5.2 LMOC Build/Release Reviews

5.5.3 Landsat Data Ops and Ground Network Status Meeting

6.0 Real-time Operations Engineering

6.1 Real-time Operations Activities

6.1.1 Command and Control

6.1.2 Mission Monitoring and Analysis

6.1.3 Mission and Science Data Collection Planning

6.1.4 Flight Dynamics

6.2 Operations Status and Planning Meetings

6.2.1 Daily Status Meeting

6.2.2 Operations Planning Meeting

6.3 International Collaborators Support

7.0 Mission Activity Performance Metrics

Appendix A Meetings, Boards, and Reviews – Summary Table

Appendix B Deliverables – Summary Table

Appendix C Acronyms

1.0 Introduction

1.1 Purpose

The purpose of this statement of work is to define the scope of Contractor support to maintain operations of the Landsat 8

(L8) and Landsat 9 (L9) observatories, the Landsat Multi-satellite Operations Center (LMOC), and the backup LMOC

(bLMOC). The LMOC and bLMOC shall be collectively referred to as the LMOC hereafter unless otherwise specified.

1.2 Scope Summary

The scope includes:

• Flight systems operations for Landsat 8 and Landsat 9.

• Realtime operations for Landsat 8 and Landsat 9

• Maintenance and sustaining engineering of the LMOC.

1.3 Period and Place of Performance

The Period of Performance (POP) is TBD.

All work will occur on-site at the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center

(GSFC) located in Greenbelt, Maryland, at the bLMOC in Sioux Falls, South Dakota, or at the Contractor’s location, either the corporate offices or elsewhere as defined in the offeror’s proposal, and as agreed to by the Government.

Remote work with a GSFC duty station is allowed with approval by the Government. The Contractor shall specify a remote work plan in the proposal.

1.4 Applicable Documents

The following documents apply to the performance of this task. Unless otherwise specified, the current document version shall apply. Any technical specifications or interface documents developed as part of the scope of this contract are also considered applicable documents. Any inconsistency in other documents, exhibits, and attachments shall be resolved by seeking clarification with the U.S. Geological Survey (USGS) Contracting Officer’s Representative (COR).

a. Landsat Satellite Operations (LSO) Data Item Descriptions (DID), LSDS-1672

b. Land Satellites Data System (LSDS) Multi-Satellite Operations Center (LMOC) Operations Configuration

Control Board (O-CCB), LSDS-1346

c. Landsat Mission Operations Satellite Control Authority (SCA) Definition and Delegation Policy LSDS-2333

d. Landsat Flight Operations (LFO) Project Operations Configuration Management Policy, LSDS-2119

e. Landsat Mission Operations Trending and Analysis Policy, LSDS-2206

f. Landsat Flight Operations (LFO) Project On-Orbit Mission Assurance Policy, LSDS-2120

g. Landsat Mission Operations Conjunction Assessment and Management Plan, LSDS-1364

h. LSDS Mission Operations Project Training and Certification Policy, LSDS-2157

i. Landsat Mission Operations Anomaly Resolution Plan, LSDS-2338

j. Landsat Mission Operations Discrepancy Reporting Plan, LSDS-2156

k. Landsat 8 Flight Software Maintenance Plan, LDCMOPS-FSW-Plan-001

l. Landsat 9 Flight Software Maintenance Plan, LSDS-2098

1.5 Reference Documents

In addition, the following documents also contain information that may be useful in enhancing the understanding of the work required by this SOW.

a. TBD

2.0 Work Breakdown Structure

The following Work Breakdown Structure (WBS) and descriptions reflect the scope of work. The WBS shall be used as the structure for technical reporting.

Figure 2-1 Work Breakdown Structure

WBS 1.1: LSO Project Management:

• Perform resource and task management functions

• Perform risk management

• Perform documentation and Contract Data Requirements List (CDRL) management

• Perform action item tracking and problem tracking

• Provide Contractor’s primary interfaces to USGS

WBS 1.2: LSO Flight Systems Operations and Sustaining Engineering

• Perform spacecraft and instrument sustaining engineering

• Performance observatory monitoring and assessment

• Perform observatory contingency support

• Perform Root Cause and Corrective Action (RCCA) analysis on operations errors as defined in the ARP WBS 1.3 LSO LMOC Operations and Sustaining Engineering:

• Perform ground systems sustaining engineering

• Perform ground software sustaining engineering

• Perform ground systems performance monitoring and assessment

• Perform ground systems contingency support

• Perform LMOC infrastructure support

WBS 1.4: Landsat Multi-satellite Real-time Operations Engineering:

• Perform real-time operations activities

• Perform anomaly detection, isolation, and recovery

• Perform real-time operations sustaining engineering

3.0 Project Management

The Contractor shall deliver a Project Management Plan (CDRL-123 TBD) within three weeks of issuance of this task order and provide subsequent updates as needed.

The Contractor shall put in place a management structure for overall project control to assure all scope and requirements of this task are accomplished. The Contractor shall have responsibility for the overall technical performance, resource

Landsat Satellite

Operations (LSO)

LSO Realtime Operations

Engineering

LSO LMOC Operations and

Sustaining Engineering

LSO Flight Systems Operations and Sustaining Engineering

LSO Project Management management, and schedule management of this effort.

3.1 Task Management

3.1.1 Personnel Staffing

The Contractor shall provide project management support necessary to oversee staff availability, competence, reliability, and performance of the work force required to operate and maintain the L8 and L9 satellites and LMOC systems.

The Contractor shall ensure availability and competence of the contract work force to execute the management and technical activities specified in this document. This shall be accomplished through recruitment, training, certification, and the analysis of comparable work environments and associated compensation. The Contractor shall manage staff allocation to the required tasks.

In the event of a facility closure or reduced access, the Contractor shall provide sufficient essential personnel to maintain mission functionality.

The Contractor shall deliver a Staffing Plan (CDRL-123 TBD) that identifies all contract and subcontract staff required for the fulfillment of this task order and a corresponding organizational structure within three weeks of issue of this task order, with subsequent updates as needed.

3.1.2 Personnel Training and Certification

The Contractor shall maintain and execute a formal training and certification program in accordance with the Operations

Project Training Policy, LSDS-2157. The objective of this program shall be to assure mission success by cultivating a diverse, competent staff of FOT professionals. This program shall include an active process of progressive skills enhancement, cross-training and contingency operations readiness. The program shall include a matrix of FOT positions and skills with defined certification levels and targeted staff certification goals. The Contractor shall report metrics on training and certification monthly.

The contractor shall provide a detailed plan of instruction for Observatory Subsystem Engineers that includes the required training materials, technical documents, simulation activities, and knowledge base for achieving effective and competent execution of their responsibilities.

The Contractor will deliver and maintain a Staff Training and Certification Plan (CDRL-123 TBD).

3.2 Schedule Management

The Contractor shall provide and maintain a schedule that addresses major discrete activities spanning this task order, including relevant operations activities. Example activities to include are:

• CDRL deliveries

• Software builds

• Infrastructure activities such as operating system updates and hardware refresh

• Mission Annual Review (MAR) preparation

• Anomaly Review Board (ARB) activities and Anomaly Reports

• RCCA Reports

• Operations Improvement initiatives (if applicable)

The schedule shall show planned start / finish dates and indicate progress towards the finish date with the objective being to provide the Contractor and the Government early insight of any schedule delays so that remediation can be discussed.

The schedule and progress shall be reported at the Monthly Project Status Reviews (MPSRs). In addition, the Contractor shall make the schedule available to the Government on a monthly basis in an agreed upon format. The schedule shall decompose work into units with a maximum duration of 2-weeks.

3.3 Procurement Management

Equipment, Software, and Maintenance:

The Contractor shall deliver and maintain a Hardware and Software Maintenance Plan (CDRL-123 TBD).

In accordance with the Hardware and Software Maintenance Plan, the Contractor shall:

• establish equipment and software maintenance agreements necessary to ensure availability and operability of the

LMOC.

• renew software licenses needed for the operation and sustainment of the LMOC.

• provide an annual equipment refresh recommendation to the Government.

The procurement of new hardware and software in support of activities contained in this SOW shall be carried out through the USGS. Procurement needs must be provided to the USGS Landsat project. In some cases, the Contractor may be requested to purchase hardware or software. In that event, a formal request will be made through the USGS Contracting

Officer (CO).

Personal Computers: Government-provided personal computers, which may be laptop or desktop computers, utilized by Operations staff or any Contractor staff member that has a need to be connected to the LMOC network, will be supplied by the Government.

Consumables: The Contractor shall provide its contractor personnel with office supplies (paper, pen/pencils, markers, etc.) used in the daily execution of this contract. The Government will procure (via government bankcard purchases) any

IT system-related items which may include, but are not limited to, printer cartridges, removable media, and cables.

3.4 Property Management

The Contractor shall deliver an Inventory Management Plan (IMP) (CDRL-123 TBD) that identifies the process used in tracking and maintaining an accurate inventory of Government Furnished Equipment (GFE) for its entire lifecycle

(procurement to disposal). GFE consists primarily of USGS equipment but may include some NASA GFE. The IMP shall also include processes used in excessing or sanitization/disposal of old hardware, methods used in routine inventory management, and methods used in an annual audit of all government property maintained by the contractor. The contractor shall work closely with the USGS Landsat Receiving Officer/Property Clerk (ROPC) and Landsat Custodial

Property Officer (CPO) to maintain the hardware inventory, process new hardware, process removal and sanitization and disposition of old hardware, and the exchange of repaired components with equipment maintenance providers. The contractor shall coordinate with USGS-EROS Property Management and NASA-GSFC for the destruction of sanitized hardware.

3.5 Resource Management

The Contractor shall actively manage LMOC resources and their personnel to ensure the timely completion of operations and maintenance activities, and identified schedule milestones.

3.6 Risk Management

The Contractor shall leverage the comprehensive and continuous risk management program delivered as CDRL-123 TBD for the contract to manage risks for the scope of this task order. The Contractor shall generate a Risk Report that uses the standard 5x5 risk matrix reporting structure and is presented and reviewed as part of the MPSRs.

The Contractor shall document the Landsat Operations specific implementation of the continuous risk management process in a risk management plan. The Government may choose to elevate risks to the USGS Landsat Flight Operations

Project Risk Management Board (RMB).

The Contractor shall maintain a Risk Register throughout the L8/L9 Operations project life cycles, including residual risks, along with programmatic effects.

For technical risks, the contractor shall lead and facilitate a Risk Management Board (RMB) that is jointly attended by the

Contractor and the USGS. USGS shall be a voting member of the RMB.

3.7 Document Management

The Contractor shall maintain the Landsat Flight Operations Technical Library. This electronic library shall contain completed reports, analyses, requirements documentation, internal technical memoranda, change requests and documentation, CDRLs, and all other LMOC-specific documents and files prepared by the Contractor for L8 and L9 operations activities. The technical library will include space segment reference documentation and CDRLs provided by

NASA at transition, and any relevant documentation updated by supporting vendors thereafter. Within this library, the

Contractor shall maintain an index of the material (updated monthly) and a search engine for document access. The non-

CDRL material contained in these electronic databases may be in Contractor format. The Contractor shall make the contents of the electronic library available to the Government and remotely downloadable. The Contractor shall include engineering drawings in this library or provide some other storage/retrieval arrangement, at their option. The Contractor shall comply with the LFO Project Operations Configuration Management Policy, LSDS-2119.

The Contractor shall perform, at least annually, a review of all delivered documents for relevancy and accuracy, and update documents accordingly.

3.8 CDRL Management

The Contractor shall provide all deliverables identified in Appendix B.

3.9 Discrepancy and Problem Tracking

The Contractor shall support and maintain the following discrepancy and problem tracking processes, at a minimum.

3.9.1 Mission-Level Discrepancy Tracking

The Contractor shall support the Government’s Landsat Discrepancy Report (LDR) problem-tracking process, on behalf of flight operations, that includes discrepancy reporting, analysis, corrective action, and closure for all discrepancies across the Landsat Satellite Ground Operations (SGO) related to L8 and/or L9 flight operations. This shall be done in accordance with Landsat Mission Operations Discrepancy Reporting Plan, LSDS-2156.

The contractor shall support the LDR board as subject matter experts on problems which originate from Landsat Flight

Operations, or in support of tickets from other Landsat operations groups.

3.9.2 Root Cause and Corrective Actions

The Contractor shall deliver a RCCA Plan (CDRL-123 TBD).

The Contractor shall utilize an RCCA investigation process to address all operator errors, at a minimum, and any operations problems warranting a structured analysis. Operator errors are to be reported to the USGS FSM immediately, and an initial RCCA report, to be accepted by the FSMs and Mission Management Office (MMO), provided within five business days of discovery of the error. A detailed description of an operator error and reporting requirements can be found in the LFO Anomaly Resolution Plan, LSDS-2338.

3.10 Project Status Meetings and Reviews.

The Contractor shall, at a minimum, participate in the following meetings. It should be assumed that actions or advisories from meetings or reviews will be captured and addressed. See Appendix A for more information.

3.10.1 Mission Annual Review

The Contractor shall deliver and present a multi-satellite MAR (CDRL-123 TBD), describing the operational accomplishments and highlights from the prior year. The content of the review will include, at a minimum, key operational events, anomalies, subsystem status, life limiting items and component assessments, future key observatory events, LMOC status, future ground system activities and events, operations improvement initiatives, staffing, training, and turnover, and lessons learned.

3.10.2 Monthly Project Status Review

The Contractor shall deliver and present the Monthly Project Status Review (MPSR) package (CDRL-123 TBD detailing the status of LSO to the Government. The MPSR package will contain the Mission Activity Performance Metrics (see

Section 7.0 below), at a minimum.

As part of the MPSR inputs, the Contractor shall provide monthly Financial Reports (CDRL-123 TBD) as well as the

Contractor Risk Report consistent with the Contractor’s Risk Management Plan (CDRL-123 TBD). All reports shall be made available electronically in Microsoft Office readable format.

3.10.3 Landsat Satellite Operations (LSO) Management Meeting

The Contractor shall lead and facilitate monthly and ad hoc teleconferences with the Government to communicate project status, collaboratively discuss issues, special topics, and high-level priorities. The Contractor shall establish the meeting agenda and distribute meeting minutes, action items, and other documentation as required. This meeting may be held in conjunction with the MPSR.

The Contractor shall provide and apply a process for capturing and responding to action items assigned by the

Government. The Contractor shall provide the Government remote access to the action item tracking solution or exported lists from the system as needed.

3.10.4 Landsat FOT Management Meeting

The Contractor shall lead and facilitate a weekly meeting with the USGS FSMs to communicate operations status and near-term activities, discuss issues and special topics, and plans and readiness for pending activities. The Contractor shall establish the meeting agenda and distribute meeting minutes, action items, and other documentation as required.

3.10.5 SGO Inter-organizational Technical Working Group

The Contractor supports and participates in a monthly meeting with the SGO Segment leaders and subject matter experts to discuss issues and special topics related to cross-segment and integrated mission support. The Contractor provides the appropriate flight operations subject matter experts to engage in the relevant agenda topics.

3.11 Travel

A maximum of 3 contractor personnel shall travel to the bLMOC location in Sioux Falls, South Dakota for proficiency operations and/or maintenance twice annually.

Contractor personnel may need to travel to domestic technical meetings during this POP. For planning purposes, the contractor shall assume eight (8) domestic trips of three (3) working days each (not including travel). These technical meetings could include flight operations areas such as: Space Situational Awareness meetings, Mission Operations

Working Groups, calibration and validation working groups and Landsat Technical Working Groups.

All contractor travel requests shall be submitted to the COR using the Government provided template for travel authorization approval.

4.0 Flight Systems Operations and Sustaining Engineering

The Contractor shall perform on-orbit flight operations of the L8 and L9 observatories and support the Government in the management of these space assets in accordance with USGS policies and practices. This requirement includes all activities necessary to maintain observatory health and safety and achieve the objectives of the missions and Landsat

Program.

The Contractor shall provide daily operations activities by performing ongoing observatory performance monitoring, analysis, troubleshooting, anomaly identification and resolution, flight software maintenance operations tasks (routine onboard table loads, and coordinating with vendors for flight software alterations), observatory configuration management, and support strategic assessment and planning of observatory subsystems and systems to promote mission longevity.

The Contractor shall create and maintain the Mission Operations Plan (MOP) (CDRL-123 TBD) in accordance with the

DID to lay out processes and plans to be used in Flight System Operations and Sustainment Engineering.

The Contractor shall prepare and present a MAR to the Government. The MAR will include Landsat 8 and Landsat 9 subsystem status, instrument status, performance history, risks, and life-limiting items analysis.

4.1 Observatory Sustaining Engineering

The Contractor shall provide sustaining engineering for the L8 and L9 Observatories and subject matter expertise support to nominal, special, and contingency operations.

The Contractor shall update and maintain all Standard Operating Procedures (SOPs) and Contingency Operations

Procedures (COPs) for flight activities and maintain the Flight Operations Handbook(s) (CDRL-123 TBD) per subsystem.

The Contractor shall update and maintain the Landsat 8 and Landsat 9 Constraints and Restrictions Documents (CARD).

The Contractor shall update and maintain the Ground Reference Image (GRI) for Landsat 8 and Landsat 9.

The Contractor shall be responsible for scheduling and executing periodic maintenance of onboard systems as defined in the SOPs and Observatory vendor documentation and in-work or internal documentation resultant from anomalies.

Associated ground configuration parameters (alerts, limits, displays, and simulator parameters) are to be managed and updated to match the configuration of the Observatory. The Contractor shall support development of revised operations concepts and/or modification and testing of new flight constraints.

The Contractor shall develop and/or maintain appropriate spacecraft models and tools necessary to accomplish sustaining engineering activities. The Contractor shall maintain simulator scripts and checkpoints and maintain the operational configuration of the Spacecraft/Observatory Simulator (S/OS).

The Contractor shall maintain the command and telemetry database for the L8 and L9 Observatories.

The Contractor shall provide sustaining engineering of the L8 and L9 observatory Telemetry Monitors (TMONs) Relative

Ops Sequence (ROSs) and Real Time Sequences (RTSs) and provide sustaining engineering support to flight software maintenance. The Contractor shall comply with the Landsat 8 Flight Software Maintenance Plan, LDCMOPS-FSW-Plan-

001 and Landsat 9 Flight Software Maintenance Plan, LSDS-2098.

The Contractor shall ensure ongoing knowledge of the Observatories’ configuration, perform regular configuration audits, and include and maintain the L8 and L9 observatories configuration items in the Configuration Item Identification List

(CIIL) (CDRL-123 TBD).

4.2 Observatory Performance Monitoring and Assessment

The Contractor shall support L8 and L9 operations engineering, trending, and functional analysis of the Attitude Control

System, Propulsion System, Electrical Power System, Command and Data Handling System, Instruments (OLI-1, TIRS-1, OLI-2, and TIRS-2), Communications System, Thermal Control System, and Flight Software, at a minimum.

The Contractor shall maintain the Landsat 8/9 Trending and Analysis Plan (CDRL-123 TBD) that describes how the

Contractor will process, trend and analyze routine housekeeping and engineering data on a daily, short term, long-term, and periodic basis required for observatory health, safety, and performance analyses. This plan shall be reviewed and updated at least annually.

The Contractor shall deliver an Observatory Annual Trending Report (CDRL-123 TBD) containing the trending analysis of all observatory subsystems.

The Contractor shall assess and report on system and architecture life-limiting items and components.

The Contractor shall comply with the Landsat Mission Operations Trending and Analysis Policy, LSDS-2206. The FSMs and/or LMM will be the primary points of contact for any discretionary decisions relating to the Contractor’s adherence to the LSDS-2119 policy.

4.3 LMOC Performance Monitoring and Assessment

The Contractor shall support LMOC operations engineering, trending, and functional analysis of the operational and redundant LMOC infrastructure, networks, ground system software, and ground system support software at a minimum.

The Contractor shall comply with the Landsat Mission Operations Trending and Analysis Policy, LSDS-2206. The FSMs and/or LMM will be the primary points of contact for any discretionary decisions relating to the Contractor’s adherence to the LSDS-2119 policy.

The Contractor shall maintain the Landsat 8/9 Trending and Analysis Plan (CDRL-123 TBD) that describes how the

Contractor will trend and analyze key parameters and markers to monitor and assess the performance of the LMOC systems to promote operability, maintain up-time, and anticipate degradation and risks. These metrics and analysis will be incorporated into the routine communications and reporting to the Government. This plan shall be reviewed and updated at least annually.

The Contractor shall prepare and present a MAR to the Government. The MAR will include LMOC subsystem status, performance history, risks, and life-limiting items analysis.

The Contractor shall deliver an LMOC Annual Trending Report (CDRL-123 TBD) containing the trending analysis of the

LMOC subsystems.

4.4 Observatory and Ground System Contingency Support

The Contractor shall provide support for anomaly identification, isolation, analysis, recovery, and closeout activities in accordance with the Anomaly Response Plan LSDS-2338.

The Contractor shall perform pre-authorized response procedures, when required and appropriate, for defined anomalies requiring immediate attention.

The Contractor shall establish a team of appropriate subject matter experts which is responsible for the initial response to the anomaly and ensuring the Observatory is in a known safe state.

The Contractor shall be responsible for maintaining a COP for escalating anomaly notification and response. The

Contractor shall summarize and report the events within one business day to the Government. If an incident is determined to be mission threatening or exceeds specified performance or mission objective thresholds, the Government shall be immediately notified.

In the event an anomaly warrants further investigation or recovery planning, the USGS FSM will charter an Anomaly

Resolution Board (ARB). The USGS FSM chairs the ARB. The Contractor shall lead the investigation, facilitate ARB meetings, and provide the necessary subject matter expertise by FOT members, commensurate with the anomaly’s scope and severity. The Government will be responsible for any augmentation to the ARB by non-LSO-Contractor technical staff to support anomaly analysis and recovery. The Contractor shall also implement corrective actions as authorized by the FSM.

The Contractor shall generate an anomaly report, and as part of anomaly closeout, the Contractor shall support the USGS

FSM in populating the NASA Meta/SOARS system.

4.5 Flight Systems Meetings and Reviews

The Contractor shall participate, at a minimum, in the meetings denoted in Appendix A.

4.5.1 Engineering Meetings

The Contractor shall lead and facilitate a monthly flight system engineering meeting, per mission, with the L8 and L9

FSM to convey observatory subsystems’ performance, trending and analysis, flight systems’ status and issues, along with planned upcoming flight systems operations activities.

The Contractor shall lead and facilitate a monthly satellite subsystem deep-dive engineering meeting, per mission, focusing on a targeted subsystem each meeting, which will collectively combine to provide a total review of each satellite in their entirety at least annually. This meeting will convey subsystem performance both on the short-term and over the life of the mission, supported by the trending and analysis of the flight subsystems’ status and identifying the progression of known issues, and identification of potential new issues.

The Contractor shall lead and facilitate flight system engineering meetings on a quarterly basis, per mission, focusing on observatory subsystems’ long-term subsystem performance, trending and analysis, and flight systems’ status and issues, along with planned upcoming flight systems’ operations activities. Note: These quarterly meetings may take the place of the corresponding Monthly Engineering Meetings.

5.0 LMOC Operations and Sustaining Engineering

The Contractor shall maintain the LMOC ground systems and infrastructure provided as Government Furnished Property

(GFP) listed in Attachment B – Government Furnished Property. This includes operational configuration maintenance, hardware and software maintenance, script and glueware maintenance, systems administration, network administration, database administration, configuration control and management, facility support, equipment installation/de-installation, integration support, and IT Security.

5.1 LMOC Operations Engineering

The Contractor shall perform operations engineering of the LMOC environment. This requirement includes all activities necessary to maintain ground environment health and safety, ensuring the on-going configuration for operability, while working to achieve the objectives of the mission. The Contractor shall provide LMOC systems functional continuity and availability for daily operations activities, while performing on-going maintenance and associated testing.

The Contractor shall provide LMOC systems and network engineering support for LMOC operations. The Contractor shall proactively evaluate systems, networks, interfaces, and software to identify planned obsolescence and develop recommended plans to maintain systems viability.

The Contractor shall maintain LMOC systems automation capabilities for routine real-time and off-line operations.

5.2 LMOC Systems Sustaining Engineering

The LMOC systems have reached a steady state, software patches will primarily be limited to product line updates and security patches. Other updates or improvements shall be evaluated through an existing return on investment prioritization process that weighs the cost of the proposed change against the value to Operations.

5.2.1 LMOC Hardware

The Contractor shall perform routine preventative and remedial maintenance and support for the LMOC equipment as recommended by equipment vendors and established standards. The Contractor shall implement improvements to LMOC infrastructure services to improve reliability, efficiency, and required IT security compliance as approved by the

Government.

The Contractor shall update and maintain the CIIL (CDRL-123 TBD) for all LMOC hardware configuration changes.

5.2.2 LMOC Software

The Contractor shall perform software sustaining engineering of all systems for the LMOC. As part of this work, the

Contractor shall identify needed fixes, plan, develop and test all associated software releases and patches, and deploy these software upgrades into the operational system, with no impact to ongoing operations.

The S/OS, Softsim, and Softbench system software upgrades and patches will be provided through the Government’s contract with the spacecraft vendor. (See section 5.4.8 Simulator Maintenance).

The Contractor shall update and maintain the CIIL (CDRL-123 TBD) for all LMOC software configuration changes.

5.2.3 LMOC System Deliveries

All LMOC deliveries shall follow the prescribed process and delivery content as defined below. The Contractor shall include detailed installation, regression test and checkout activities necessary for each delivery.

All LMOC system deliveries shall consist of the following items as part of the Delivery Package:

1. Version Description Document (VDD) (CDRL-123 TBD) to include:

• Source Code (where appropriate)

• Executables

• Matrix of work requests/trouble tickets addressed by the release

2. Hardware Inventory and intended usage description

3. Development Test Results/Reports

4. Initial or updated User’s Manuals

5. The LMOC CIIL (CDRL 123 TBD), which describes the configuration of all Hardware Configuration Items (CIs) and

Computer Software Configuration Items (CSCIs)

6. Release LMOC Installation, Setup and Configuration Procedures (CDRL 123 TBD)

7. LMOC regression test plans

8. Other documentation, as appropriate

5.3 Ground Systems Contingency Support

The Contractor shall provide support for flight operations ground system anomaly identification, isolation, analysis, and recovery.

The Contractor shall escalate the anomaly notification and response, consistent with the COP and guidelines identified in section 4.4 Observatory and Ground System Contingency Support.

The Contractor shall establish a team of appropriate subject matter experts which is responsible for the initial response to the anomaly and ensuring on-going operations. In the event an anomaly warrants an investigation or recovery planning, the USGS FSM will convene an Anomaly Resolution Board (ARB).

The Contractor shall generate an anomaly report for each anomaly in accordance with the Anomaly Response Plan.

5.3.1 bLMOC Operations and Readiness

The Contractor shall maintain bLMOC operational readiness to ensure availability in response to ground system contingencies and resource contentions. Periodic exercise of the bLMOC operational capabilities will be accomplished through proficiency contacts. The contractor shall perform quarterly bLMOC proficiency exercises alternating between

GSFC and EROS.

The Contractor shall maintain a bLMOC failover (COP) for efficient and seamless transfer of operations to and from the bLMOC remotely from GSFC in Greenbelt Maryland or directly from the bLMOC in the EROS Center in Sioux Falls SD.

The failover COP shall dictate the overall process of failovers and may consist of one or more SOPs or COPs. Operations transfer may occur at the direction and authorization of the Government in accordance with the SCA policy, LSDS-2333.

Whenever possible, the Contractor shall maintain the bLMOC to be identical to the LMOC in operational configuration, functional capability, and user-experience.

5.4 LMOC Infrastructure Support

5.4.1 Systems Administration

The Contractor shall perform system administration of all LMOC systems, unless otherwise noted.

The Contractor shall perform system administration of Government-provided personal computers (laptop or desktop computers) for Contactor staff and USGS LFO Project civil servant and Federally Funded Research & Development

Centers (FFRDC) staff stationed at GSFC.

5.4.2 Network Infrastructure Support

The Contractor shall maintain the network infrastructure to support the LMOC systems, connectivity, data flows, external interfaces, and IT Security requirements. The Contractor shall support the configuration and operations of connectivity into the LMOC environments. The Contractor shall serve as technical point-of-contact for NASA/GSFC’s

Communications Services Office (CSO) for network outages, troubleshooting, testing, and requirements definition.

5.4.3 Database Administration

The Contractor shall provide database administration for the LMOC. This includes the command and telemetry database, software databases, configuration management databases, and any other Contractor developed database used to satisfy this

Multi-satellite Operations task order SOW.

5.4.4 IT Security

The Contractor shall provide technical and IT Security expertise to the USGS FSM(s) in support of L8 and L9 Flight

Systems Management. The Contractor shall interpret, implement, and comply with USGS, Department of the Interior

(DOI), and NASA Federal IT security requirements including Department of Homeland Security (DHS) High Value Asset

(HVA) controls. The Contractor shall serve as the computer security representative for L8 and L9 flight operations and coordinating security activities with USGS EROS Center IT Security personnel. The Contractor shall maintain the

LMOC IT Security implementation and documentation, facilitate center and agency reporting requirements, and perform annual IT Security Assessments, and assessments for new configurations. The Contractor shall lead the coordination effort with all equipment and system vendors to maintain network compatibility and adherence with IT Security requirements.

The Contractor shall maintain the LMOC IT Security Compliance Matrix (CDRL-123 TBD). The Government will review and approve the compliance matrix and the Contractor’s implementation of IT security requirements. The

Contractor shall coordinate the implementation of IT security requirements with the Government.

The Contractor shall perform monthly credentialed scans, intrusion detection and prevention, firewall configuration and monitoring, and coordinate enforcement of security risk mitigations within the Contractor-managed networks. The

Contractor shall maintain a systems security posture to include, but not limited to, monthly patching and software updates, emergency patching, implementation of scan resolutions, monitoring of system logs, and inventory, and electronic delivery of Contractor-managed system configuration.

The Contractor shall install, support, and operate the Government-furnished security tools, including the vulnerability assessment tool, the security incident event management tool, and system configuration inventory tool to ensure proper population of DOI agency databases. Government-furnished security tool support includes, but is not limited to, provision of hardware to run the tools if applicable, tool installation, tool configuration, configuration and adjustment of associated firewall rules to allow egress of tool-generated network traffic, and support of related troubleshooting activities.

The Contractor shall document any deviations, Plan of Action and Milestone (POA&M), or findings as a result of scans, or known vulnerabilities or non-compliance, and implement any corrective actions following approval. The Contractor shall report computer security incidents to the Government in accordance with the DOI Computer Security Incident

Response Handbook. The Contractor shall periodically generate and deliver IT security status reports to the Government on a monthly basis, at a minimum, as part of the MPSR.

5.4.5 Configuration Management

The Government will exercise control of any changes to the configuration of LMOC systems and Observatories and will approve any changes to the support elements or facilities within the flight operations domain via the Landsat Operations

Configuration Control Board (OCCB), which the Government charters and chairs. The Contractor shall administer the

Landsat OCCB. The Contractor shall support configuration management of the L8 and L9 Observatories, all LMOC system environments, operations products, and any GFE-delivered items including, but not limited to, flight software, simulators, Telemetry and Command (T&C) databases, and all other contractor deliverable items throughout all phases of

Multi-satellite Operations and Sustainment via the LSDS-OCCB process.

The Contractor shall use, administer, and maintain tools and software applications utilized in support of Flight Operations

Configuration Management (CM). The Contractor shall maintain documentation, plans, and procedures as required for supporting Operations CM. The Contractor shall maintain and update (as needed) the government, and vendor-provided spacecraft and instrument documentation. The Contractor shall follow established configuration management processes

(e.g., peer review and internal sign-off) for all operations systems and products including documentation of new or updated products. The Contractor shall maintain a set of configuration-controlled flight operations products, which include procedures for nominal, special and contingency operations. The Contractor shall support the Government to coordinate configuration changes across other mission components.

The Contractor shall follow the Landsat Flight Operations (LFO) Project System Configuration Management (CM)

Policy, LSDS-2119, for guidance regarding configuration management.

The contractor shall maintain the CIIL, CDRL-123 TBD. The CIIL shall be delivered at least annually with updates provided prior to major builds. Between deliveries, the Contractor shall continuously maintain the CIIL using established

CM processes.

5.4.6 Facilities

The LMOC facilities structure, external network connections, and environmental control will be provided by the

Government.

The Contractor shall support basic facility modifications in the Government-furnished facilities as permitted.

For all facility activities, the Contractor shall maintain the appropriate safety training and equipment that is utilized for the lifting, installation, delivery, and relocation of heavy materials and equipment, including but not limited to servers, racks, consoles, packages, and crates.

5.4.7 Property Management Support

The Contractor shall adhere to property disposal and excessing procedures consistent with USGS property and IT Security guidelines ensuring sanitization of hard drives and storage media.

5.4.8 Simulator Maintenance

The Contractor shall support the installation of software updates to the S/OS(s), SoftSim(s) and Softbenches, led by the

Observatory vendors.

The Contractor shall support the installation of software updates and IT Security patching and scanning to the Wideband

Data Capture (WDC) (demodulator) and Command and Telemetry Processor (CTP) systems at GSFC, led by

USGS/EROS.

The Government has support contracts with the simulator vendors. The Contractor shall coordinate with and support vendor-led simulator hardware maintenance activities including investigation, assessment for resolution of hardware anomalies.

The Contractor shall implement a system backup plan, as approved by the Government, for the S/OSs, SoftSims, and

Softbenches to mitigate risk to the system configuration and content brought about by component failure, software upgrade and patching incompatibility, and other vulnerabilities.

The Contractor shall maintain the Landsat simulator maintenance plan within the Hardware and Software Maintenance

Plan (CDRL-123 TBD).

5.5 LMOC Meetings, Boards, and Reviews

The Contractor shall participate in the following meetings, at a minimum. See Appendix A for more information.

5.5.1 LMOC Discrepancy Review Board

The Contractor shall lead and facilitate the LMOC Discrepancy Review Board (DRB) and oversee the problem tracking process, including coordination of problem analysis and investigation, accurate documentation of identified discrepancies, prioritization of discrepancies, and the assignment of software problem fixes to planned patches or releases, in collaboration with the USGS FSM(s).

The Contractor shall support the management of the problem tracking system, including user access, and generation of summary problem status metrics and reports.

5.5.2 LMOC Build/Release Reviews

The Contractor shall convene LMOC build and release reviews, per the Systems Engineering Management Plan (SEMP), as dictated by the software release schedule. At a minimum, the Contractor shall facilitate, prepare, and present the following sustainment reviews and provide the associated CDRLs:

• Build Review (BR) (CDRL-123 TBD)

• Test Readiness Reviews (TRR) (CDRLs TBD)

• LMOC Release Post Test Reviews (PTR)/Pre-Ship Review (PSR) (CDRLs TBD)

The Contractor shall conduct Engineering Peer Reviews (EPRs), as applicable, where the review is useful and commensurate with the scope, complexity, and level of risk of the technical topic. The Government may also request

EPRs where appropriate.

5.5.3 Landsat Data Ops and Ground Network Status Meeting

The Contractor shall participate in the Landsat Data Ops and Ground Network Status meeting, held bi-weekly and led by

USGS MMO for discussing and deconflicting data operations and ground network issues which could impact all Landsat missions.

6.0 Real-time Operations Engineering

The Contractor shall perform real-time operations activities including, but not limited to, command and control, telemetry monitoring and analysis, Mission Planning (MP), Flight Dynamics (FD), and anomaly detection, isolation, and recovery operations for L8 and L9 normal, special, and contingency operations.

The Contractor shall plan, rehearse, and execute all unique and non-routine activities with the highest fidelity models and simulators available. Applicable activities include, but are not limited to, orbital maneuvers, special events, flight software modifications, and anomaly recovery activities which involve or affect one or more Observatory subsystems.

New and modified flight operations products will also be verified with a simulator.

6.1 Real-time Operations Activities

The Contractor shall support all daytime and lights-out, in person and remote real-time operations of the L8 and L9 observatories through contacts from both ground and space networks. Real-time operations consist of those activities that are necessary to support direct communication with the observatory and include pre/post-pass operations, telemetry acquisition, tracking and command, orbit and attitude maintenance maneuvers, system configuration, Observatory state of health assessment, housekeeping telemetry processing, command load uplink and verification, table and memory load/dump operations, mission data management, and management of the Solid State Recorders (SSR) to capture and downlink all science and observatory engineering data.

The Contractor shall perform periodic proficiency operations of LMOC systems, as well as proficiency contacts with infrequently used ground stations, to validate routine and contingency procedures, system configuration, and ensure proper training and certification of the FOT. The Contractor shall define their approach to proficiency testing and the associated training and certification required of the FOT in the Operations Staff Training and Certification Plan (CDRL-

123 TBD).

The Contractor shall maintain a console log and collect metrics on contact activities, automation, mission data management, and ground system performance for regular reporting.

The Contractor shall perform off-line operations activities, necessary to enable the real-time operations for on-going nominal operations of the Observatories. The offline activities include planning and scheduling, orbit determination, maneuver planning, stored command load generation, attitude modeling, and trending and statistical analysis of observatory performance.

The Contractor shall develop and maintain flight and ground SOPs and COPs for real-time and off-line activities in the

Flight Operations Handbook (CDRL-123 TBD).

6.1.1 Command and Control

The Contractor shall perform commanding of the Observatories for nominal, special, and contingency operations.

Realtime command and control operations will be staffed by trained and certified FOT members in accordance with the

Operations Staff and Training Certification Plan (CDRL-123 TBD).

For non-nominal, special, and contingency events, the Contractor shall at the discretion of the FSM schedule and lead a

Command Authorization Meeting (CAM), chaired by the USGS FSM.

The Contractor shall develop, maintain, and implement all SOPs and COPs consistent with the delegation of SCA defined in LSDS-2333 Landsat Mission Operations Project (LMOP) SCA Definition and Delegation Policy.

6.1.2 Mission Monitoring and Analysis

The Contractor shall monitor and assess all Observatory housekeeping and engineering data upon delivery to the LMOC system to ensure the health, safety, and proper configurations of L8 and L9.

The Contractor shall develop and maintain alerts, indicators, telemetry pages, configuration monitors, scripts, charts, graphs, reports, and other tools to augment the operators’ ability to recognize and the Observatories’ condition.

The Contractor shall collect and store all housekeeping and engineering data delivered to the LMOC for the life of the missions. The Contractor shall maintain and ensure availability of all housekeeping and engineering data collected from the L8 and L9 Observatories within the LMOC trending and analysis system.

In addition, the Contractor shall produce and provide reports as needed to support anomaly investigations, maneuver planning, special operations, definitive reporting, and on-demand requests by the Government.

6.1.3 Mission and Science Data Collection Planning

The Contractor shall perform mission planning activities and generate command loads for all L8 and L9 Observatory activities. These mission planning and load building activities include, but are not limited to, scheduling of ground and space network communications contacts, instrument activities, science data collection, calibration observations, and orbital maneuvers.

The Contractor shall ensure adequate S and X-Band communications services are requested through the Landsat Ground

Network (LGN), NASA Direct to Earth (DTE)…