Attachment_B_-_RFI_Cost_Template_1.xls

120 KB Posted

Attached to
RFI - Landsat 10 MOC & Ops _ FAQs
Solicitation number
DOIGFBO260017
Issued by

About this file

Written by GovTribe AI ·

This is a cost estimate template for the Landsat 10 (L10) Mission Operations Center (MOC) and Operations contract, designed to capture labor hours and Other Direct Costs (ODCs) across three major phases: Development/Integration & Test (pre-MTHR), Mission Operations Readiness and Launch/Early Orbit Commissioning (LEOC) (pre-MTHR), and Operations & Sustainment (post-MTHR). The spreadsheet covers a 10-year period from Q1 CY2027 through Q1 CY2037 and includes notional milestones such as Spacecraft Award (January 2027), Mission Critical Design Review (May 2029), Spacecraft I&T Start (October 2029), and Mission Transition & Handover Review (March 2032). Vendors must populate labor hours for specific tasks including project management, systems engineering, subsystem development and I&T, telemetry and command operations, flight dynamics, planning and scheduling, configuration management, trending analysis, load builder validation, simulator engineering, network infrastructure, and mission operations situational awareness. ODCs are categorized by equipment/hardware, software licenses, cloud services, networks, and other costs, with all costs required to be burdened to include contractor overhead and fees but exclude award fees.

The template requires detailed cost estimation aligned with the L10 MOC functional architecture and test approach, which employs a Test-as-You-Fly methodology involving Ground Readiness Tests (GRTs), Spacecraft Operational Readiness Tests (SORTs), Mission Readiness Tests (MRTs), and Mission Simulations (SIMs) using multiple simulators of varying fidelity (CTSS, SoftSIM, and OOPS). Labor estimates must account for FOT training and certification, ground and flight procedures development, simulator engineering support, GRT/SORT/MRT execution, and mission simulation rehearsals. The Operations & Sustainment phase includes ongoing support for realtime console operations, planning and scheduling, flight dynamics, anomaly investigations, and MOC sustaining engineering to achieve "Steady State" within two years post-MTHR, defined as a condition where no major re-engineering activities remain, system performance is acceptable, and sustainment can be conducted with trained personnel and stable processes. Vendors are instructed to provide basis-of-estimate documentation, particularly for anomaly investigation support, and to note any deviations from the specified functional categories provided in the spreadsheet.

View the file

Other files

File Type Posted
L10_MOC_RFI_(2026)_FAQs_6.pdf PDF
Attachment_M_-_L10_MOC_RFI_Industry_Briefing_Package_4.pdf PDF
L10_MOC___Ops_Update_RFI_-_v4_1.pdf PDF
Attachment_H_-_Landsat_Flight_Operations_Configuration_Management_Policy_1.pdf PDF
Attachment_A_-_RFI_Questions_1.xlsx XLSX spreadsheet
Attachment_D_-_L10_MOC_IT_Security_Guidance_1.pdf PDF
Attachment_E_-_Landsat_Multi-Satellite_Operations_Center_(LMOC)_Requirements_Document_1.pdf PDF
Attachment_J_-_USGS_EROS_Enterprise_Hosting_Statement_of_Capabilities_1.pdf PDF
Attachment_K_-_Landsat_10_Mission_Synopsis_(for_MOC_RFI_-_pre-release)_1.pdf PDF
Attachment_C_-_L10_MOC_Functions_Summary_1.pdf PDF
Attachment_F_-_LMOC_Operations_Concept_-_Redacted_1.pdf PDF
Attachment_G_-_LMOC_Scalability_Study_1.pdf PDF
Attachment_I_-_USGS_CHS_Cloud_Responsibilities_1.pdf PDF
Attachment_L-1-_L10_Design_Reference_Case_-_18_Day_(DRC-18)_Definition_1.pdf PDF
Attachment_L-2_L10_DRC-18_spreadsheet_1.xlsx XLSX spreadsheet
Show all 15

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file
Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Cost Estimate Inputs

Task/ActivityCY2027CY2028CY2029CY2030CY2031CY2032CY2033CY2034CY2035CY2036CY2037Notes
Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1
Notional Mission and Ground System Milestones
S/C Award January 2027▲
MOC Target Award Date October 2027▲
GS SRR August 2027▲
Mission PDR May 2028▲
GS PDR June 2028▲
Mission CDR May 2029▲
GS CDR May 2029▲
S/C I&T Start October 2029 (Notional)▲
GRTs Start November 2029▲
SORTs (S/C mission readiness testing) Start Feb 2030▲
Observatory I&T Start May 2030▲
MRTs (Observatory mission readiness testing) Start July 2030▲
Mission Sims Start September 2030▲
LRD December 2031▲
MTHR - LEOC Ends/Transition to Ops March 2032 (Notionally Launch + 100 days)▲
Achieve Steady State MOC and Operations▲
Enter Labor Hours Below per Quarter and Burdened ODC and Total Labor Cost in Thousands of Dollars, including contractor overhead/fees (Excludes award fee)
DEVELOPMENT, INTEGRATION & TEST (Pre-MTHR)
Labor
Project Management/Admin for pre-MTHR (MOC Dev/I&T, Mission Ops Readiness, & LEOC)0 hrs
MOC Systems Engineering0 hrs
MOC Subsystems/Functions Development and I&T:0 hrs
Telemetry & Command (T&C)0 hrs
Flight Dynamics/Orbit Operations0 hrs
Planning & Scheduling0 hrs
Contact & Activity Orchestration0 hrs
Configuration Management & State Management0 hrs
Trending & Analysis0 hrs
Alerts & Notification0 hrs
Load Builder/Generator and Validation0 hrs
Analytical Modeling & Simulators0 hrs
Network and Infrastructure0 hrs
Mission Operations Situational Awareness0 hrs
Other Tools/Capabilities0 hrs
Total Labor Hours for MOC Dev/I&T0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs
Total Labor Cost per Quarter, including overhead/fees ($K)$ 0.0K
ODCs (For the entire pre-MTHR period)
ODC/Equipment and Hardware$ 0.0K
ODC/Software Licenses$ 0.0K
ODC/Cloud Services (if applicable)$ 0.0K
ODC/Networks$ 0.0K
OCD/Other (make a note what this is for in column AR)$ 0.0K
Total ODC Cost per Quarter, including overhead/fees ($K)$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K
Total Dev/I&T Cost per Quarter, including overhead/fees ($K)$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K
MISSION OPERATIONS READINESS and LEOC (Pre-MTHR)
Mission Ops Readiness
FOT Training/Development0 hrs
Ground Ops Proc Development/
Flight Proc Integration0 hrs
Ground Systems Engineering0 hrs
GRT Support/Execution0 hrs
MRT Support/Execution0 hrs
Mission Sims/Rehearsals0 hrs
Simulator Engineering0 hrs
Network/Infrastructure Support0 hrs
LEO/Commissioning
Observatory Systems Engineering0 hrs
Ground Systems Engineering0 hrs
Realtime Operations0 hrs
Planning & Scheduling0 hrs
Flight Dynamics/
Orbit Operations0 hrs
Anomaly Investigations0 hrs
Network/Infrastructure Support0 hrs
Total Labor Hours for MR and LEOC0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs
Total Mission Readiness/LEOC Cost per Quarter, including overhead/fees ($K)$ 0.0K
Total DEV/I&T/MR Cost per Quarter, including overhead/fees ($K)$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K
OPERATIONS & SUSTAINMENT (Post-MTHR)
Project Management/Admin0 hrs
Observatory Systems Engineering0 hrs
Ground Systems Engineering0 hrs
Realtime Operations0 hrs
Planning & Scheduling0 hrs
Flight Dynamics/
Orbit Operations0 hrs
Simulator Engineering0 hrs
Anomaly Investigations0 hrs
MOC Sustaining Engineering0 hrs
Network/Infrastructure Support0 hrs
Total Labor Hours for Ops0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs0 hrs
Total Ops Labor Cost per Quarter, including overhead/fees ($K)$ 0.0K
ODC/Equipment and Hardware (ops refresh)$ 0.0K
ODC/Software Licenses (renewals)$ 0.0K
ODC/Cloud Services (if required)$ 0.0K
ODC/Networks$ 0.0K
ODC/Other (make a note what this is for in column AR)$ 0.0K
Total Ops ODC Cost per Quarter, including overhead/fees ($K)$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K
Total Ops Cost per Quarter, including overhead/fees ($K)$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K$ 0.0K
Instructions and Background information to fill out this spreadsheet provided below:
Labor and Cost Data ROM Entry (Complete all Yellow highlighted cells above):
For each quarter, enter labor in average level of effort (hours) in that quarter for each task/area
All costs should be burdened and include overhead and fees, but Exclude any notional Award Fee
For each quarter, enter the sum of all labor costs, burdened, including overhead and fees (calculated externally and entered into this spreadsheet)
For each quarter, enter ODC costs for each category, burdened, including overhead and fees (calculated externally and entered into this spreadsheet)
(Spreadsheet calcuates) The sum of all ODC costs, burdened, including overhead and fees (calculated by a formula in the spreadsheet)
(Spreadsheet calcuates) The total burdened development/I&T/mission readiness or Ops costs
Enter any notes in column AR on the far right
Notes: For the MOC Subsystems/Functions Development and I&T hours/cost ROM estimate, it is preferred that the Vendor enters the information per the functional breakdown provided. If your organization uses different categories, please attempt to split hours into categories on spreadsheet based on your estimate of how the work is divided.
For all other hours entered (for Mission Ops Readiness, LEOC, and Operations/Sustaining) please adhere to the categories/support tasks provided.
MOC Development will be responsible for MOC systems and asscoiated staffing through the Mission Transition & Handover Review (MTHR, notionally Launch + 100 days), at which point Operations will take over MOC Sustaining Engineering responsibility. The spreadhseet is grayed out to reflect this.
To support getting the MOC to a "Steady-State" configuration and maturity after MTHR, Development labor will be carried into Operations, to address issues discovered during LEOC, and to implement capabilities and functionality that may have been deferred due to schedule compression in the I&T phase. This is in addition to routine ops patching and update work (that would continue into long-term operations). Steady State is expected to be achieved within 2 years after MTHR.
Steady State: Operations is defined by reaching the following MOC/operational status:
•No re-engineering or major sustainment maturation activities are outstanding including but not limited to:
oMOC software builds planned/needed
oFlight software builds planned/needed
oPayload software builds planned/needed
•No major system performance issues remain within the MOC
•Sustaining operations can be conducted with consistent reliability, acceptable performance, sufficiently trained personnel, and relatively stable processes and procedures
•Sustaining operations can be satisfied with the existing systems’ usability, sustainability, performance, and risk posture
•Current and projected costs of sustainment engineering are satisfactory to the Landsat program
Integration and Test (I&T) Approach for Landsat 10 (L10):
A Test-as-You-Fly (Fly-as-You-Test), TAYF, approach will be used for requirements verification - Requirements will be verified/tested in the context of how they are related to an operational system. Typically, this means verification/testing is done by executing a series of scenarios representing normal operations to demonstrate the system works as expected.
Roll-up verification (of requirements) and testing will be used, so only parent requirements eligible for verification are those that have all their child requirements previously verified (e.g. - system level requirements can't be verified until all the child subsystem requirements have been verified).
Testing for the MOC will be done first by subsystem (L5), then at the MOC system (element, L4) level, Component testing will be done as appropriate for components of a susbsystem. Interfaces will also be tested at the corresponding level (e.g. - subsystem to subsystem interfaces will be tested as part of the integration into a complete system/element)
Integration of the MOC into the ground system (GS, level 3 - L3) will be done via ground readiness tests (GRTs). GRTs are expected to consist of a series of test windows (notionally 2-3 months long) where requirements associated with a release can be tested as they are ready (i.e. a spiral development approach), followed by a capstone that captures any remaining requirements that need verification while also demonstrating compliance with requirements previously verified.
Mission level testing consists of support for spacecraft (bus) testing and Observatory level (integrated S/C bus and LANDIS instrument) testing. Previous missions waited until just prior to Observatory level before starting mission readiness tests (MRTs), but L10 will break the traditional set of MRTs into two phases: 1) SORTs - S/C-led operational readiness tests, and 2) MRTs - A smaller number of traditional end-to-end testing of the integrated instrument and S/C bus (Observatory) and ground system.
SORTs are led and scheduled by the S/C vendor & coordinated with the project. It will be the responsibility of the S/C vendor to schedule (and interleave) these tests with other S/C (bus) I&T activities. The S/C vendor can execute portions of a SORT as part of a planned S/C test, or schedule a specific test event for a SORT. The MOC will support SORTs via delivered MOC capabilities such as TLM and CMD (T&C) services from the MOC as well as ground procs to execute the SORT (flight procs provided by S/C vendor). It is anticipated that primarily MOC T&C and Load Builder capabilities will need to be tested/verified to support SORTs, but additional capabilities/functions may also be required. These dependencies will be coordinated with the S/C vendor once a contract has been awarded for the S/C bus and for the MOC.
As preparation for the SORTs, a series of connectivity tests will be conducted between the MOC and S/C vendor to demonstrate that the MOC can successfully CMD the S/C and receive TLM. These tests will initally be run using S/C deveopment systems (e.g. - EDU, SDVF, etc.) and later progress to connectivity testing with the actual S/C. A mini-MOC may be used for initial testing with the S/C development system, as appropriate for the MOC architecture and design. The mini-MOC will be operated by MOC and/or FOT staff conducting the test at the S/C vendor facility, and use of a mini-MOC provides the ability to make minor modifications to MOC systems to enable successful test execution. A series of connectivitiy tests is planned to provide multiple test/retest opportunities.
MRTs will be executed by the FOT using operational procs and MOC systems. Most of the MOC system capabilities and functionality will need to be tested/verified prior to MRTs. Interfaces between the MOC and other GS elements (ground network and DPAS - data processing and archive system) will also be exercised in MRTs as part of the series of end-to-end mission tests.
GRTs will be used to verify the MOC portion of the GS capabilities and functionality is ready for SORTs or MRTs, following success L5 and L4 MOC (element) testing. It is anticipated that a phased approach could be used for MOC releases, that provide capabilities and functionality needed for a SORT or MRT as a primary objective.
Per the test-as-you-fly (TAFY) approach, SORTs and MRTs will be scenario based and demonstrate execution of various mission phases, e.g. - S/C bus activation, instrument activation, routine scheduling and acquisition of images by the instrument, etc.
Mission Simulations (SIMs) will also be executed as part of the mission readiness campaign. SIMs will be executed at the MOC using a simulator (SoftSIM or OOPS) to stand in for the S/C. The SIMs mirror the SORTs and MRTs in that they will exercise a series of operational scenarios such as launch and early orbit, activation, routine operations, decommissioning, etc. SIMs will be supported by S/C vendior staff, both onsite at the MOC and via remote connection. SIM duration and cadence will mirror S/C operations, and some may be 24×7 to simulate S/C operations. SIMs will initially be conducted using nominal conditions, but later simulations will introduce anomalies to exercise contingency operations. SIMs will be stgaffed with the actual personnel anticipated to perform the operations after launch.
In addition to SORTs, MRTs, and SIMs, the MOC may particiapte in RF compat testing, to send CMDs as part of the S/C receiver threshold testing.
MOC Development and Readiness Support
To support MOC development and readiness, a series of simulators are being developed by the S/C vendor that provide varyng degrees of fidelity: 1) CTSS - CMD and TLM simulator system; 2) SoftSIM - A S/W simulator of the S/C; 3) OOPS - Observatory operational simulator
The CTSS is a moderate fidelity simulator that is intended to provide early access to a S/C-like system for MOC development. It will accept and validate unencrypted CMDs and generate TLM associated with the COP-1 CMD protocol, as well as simulated realtime (RT) and playback/SSOH (stored state-of-health) backorbit TLM. The simulated RT TLM will be based on the S/C T&C database, but be basic in nature and extent, notionally generating nominal values with perhaps some small level of variation. The simulated SSOH TLM is anticipated to be playback of a predefined test file generated by the S/C vendor (which may or may not align with the simulated RT TLM). The CTSS will also be used by the ground network (GN) stations for development and testing to simulate the S/C, and GRTs that integrate the MOC and GN will use the CTSS as a data source/simulator for end-to-end test scenarios.
The SoftSIM is a higher-fidelity simulation of the S/C than the CTSS, and will provide dynamic behavior and responses to simulate expected S/C behavior. The SoftSIM is not necessarily a "digital twin" of the S/C and may have capabilities and functionality that deviate from that of actual flight H/W and S/W. The SoftSim is anticipated to be delivered a few months prior to S/C level testing.
The OOPS is a full-fidelity simulator and is expected to have the same behavior and similar timing as the actual Observatory. The OOPS consists of the integrated LANDIS operational simulator (LOPS) and the S/C bus operational simulator (SOPS), that has been integrated and tested by the S/C vendor before delivery to the MOC. The OOPS will have maintenance and support provided by the S/C vendor during development, including bug fixes and updates as new versions of the FSW and T&C database are released for use on the S/C. The OOPS will be used for MRT test and proc development, and executing mission simulations (SIMs). The OOPS is anticipated to be delivered shortly before S/C level testing.
Additionally, to support SORTs and MRTs, as well as routine pre-launch TLM archival, a two-way wide-area network (WAN) "Listen-Line" connection will be established between the S/C vendor and the MOC. The Listen Line will be used for the MOC to communicate with the S/C for SORTs and MRTs. The Listen-Line also provides access to the S/C TLM stream during Observatory I&T (any time the S/C is powered on) to capture a copy of pre-launch TLM (that may be useful in future for troubleshooting or anomaly invetigations), and to provide a periodic source of live TLM for FOT training.
Validated and tested flight (S/C and instrument) procs will be delivered by the NASA Project, in the MOC T&C launguage. Ground ops procs will need to be developed, validated, and tested by the MOC/FOT vendor.

WBS Dictionary

Scope
PeriodContract Award to MTHRPost-MTHR
WBS Element (Task)MOC DEVELOPMENT, INTEGRATION & TESTMISSION OPS READINESS & LEOCOPERATIONS & SUSTAINMENT
Project Management/AdminManagement of MOC Development/I&T scope; Mission Ops Readiness; and Launch/Early Orbit, and Commissioning; and on-going/long-term on orbit ops.

Contract/Subcontract Management Periodic status reporting Any EVM data capture, analysis and reporting needed Documentation and execution the risk management process (RMB, etc.)

Administrative support for project work and staff Management of reaching Steady State and on-going/long-term on orbit ops.

Contract/Subcontract Management Periodic status reporting Any EVM data capture, analysis and reporting needed Documentation and execution the risk management process (RMB, etc.)

Administrative support for project work and staff MOC Systems Engineering Provide Element-level (MOC system) engineering Documentation and execution of engineering processes Documentation and execution the change management process (CCB, etc.)

Preparation and execution of MOC milestone reviews, including dry-runs/peer reviews Support for GS- and Mission-Level reviews (preparation of materials, participation as needed) Development and management of MOC and subsystem/functional requirements Development and execution of validation/verification for MOC and subsystem/functional requirements Participate in a limited number of GS-level meetings and working groups

Interface Definition:

Engineering and analysis to define interfaces between the MOC and the Observatory, and between the MOC and other GS elements (ground network/GN and data processing and archive system/DPAS) Provide input to GN/MOC ICD, DPAS/MOC ICD, and MOC to Observatory ICDs and other interface documentation (e.g. T&C database, handbook, procedures, etc.) Note that development scope will extend into the operations phase for 1-2 years after MTHR to aid in getting to a Steady State level of systems/operations maturity & stability, and to address any capabilities/functionality deferred past the launch freeze deadline (e.g. - priority 3 or 4 requirements, not needed for launch).

(These costs can be reflected in the MOC Sustaining Engineering costs. See below)

MOC Subsystems/Functions Development and I&TFor each MOC Subsystem/Function listed in the spreadsheet (see MOC Subsystems Functions List below), estimate development, integration, test, and delivery of the capabilities to satisfy the MOC functional capabilities needed to support GRTs, MRTs, SIMs/Rehearsals, LEOC, and On-Orbit Operations.
Mission Ops ReadinessOn-Orbit Operations
FOT Training/DevelopmentProvide operations training and certification of FOT personnel using contactor developed training plan/process, ensuring on-going readiness of personnel to support testing, simulations/rehearsals, LEOC, and operations.
Ground Ops Proc Development/
Flight Proc IntegrationGround Ops: Development of all ground ops procedures and scripts needed to test and execute the MOC and it's subsystems operationally, including scenarios needed within GRTs, SORTs, MRTs and Mission Sims.

Flight (Observatory) Ops: Working with NASA and S/C and Instrument vendors to ingest and configure flight procs for the S/C and the instrument (it is expected that NASA will delivery tested and validated flight procs in the MOC language)

Ground Systems EngineeringDevelop and implement glueware and scripts, where needed, to integrate and streamline MOC operations and processes. After delivery by developers, prepare MOC subsystems for use by establishing/maintaining operational user-defined configurations. Provide project database maintenance.
GRT Support/ExecutionFOT support for ground readiness tests (GRTs).

Construction of operational proc sequences to execute GRTs, including dry-runs.

MRT Support/Execution FOT support for mission readines testing includes Realtime Operations, Planning and Sceduling operations, and Flight Dynamics/Orbit Operations.

FOT support for (S/C) connectivity tests (CTs), S/C-led operational readiness tests (SORTs), and mission readiness tests (MRTs).

Support as follows (Days x Hours):

Five CTs are expected (1×12) and three MRTs (2×24) SORTs are planned and scheduled by the S/C vendor and could either be single tests interleaved with planned S/C I&T activities or a series of formal test events (like MRTs or GRTs) Construction of operational proc sequences to execute CTs, SORTs, and MRTs, including dry-runs Mission Sims/Rehearsals Mission simulations (SIMs) and rehearsals will be conducted at a cadence and staffing to mimic actual flight operations. FOT support should match/fulfill accordingly.

Support as follows (Days x Hours):

SIMs are anticipated to be: SIM 0 (SIM 1 dry-run 2×12), SIM 1 (4×12), SIM 2-3 (5×24), SIM 4 (1×12), using the Observatory simulator with support from project and Observatory vendor staff Additionally there will be day-in-the-life (DITL) simulations run with Observatory simulators and limited support by other organizations: DITL 1-2, 3 (3×8), and the total WRS-in-the-life TWITL (18×8)

Simulator EngineeringThe FOT will configure and operate the spacecraft/instrument simulators for FOT training, the Mission Sims/Rehearsals, procedure validation, and anomaly investigations.
Note: During Mission Readiness and LEOC, NASA will have the primary role to configure and operate the spacecraft/instrument simulators for Mission Sims/Rehearsals, procedure validation, and anomaly investigations.. The FOT will augment this support. THe FOT will be prime for configuring/operating for FOT Training.The FOT will operate and maintain the configuration of the spacecraft/instrument simulators for FOT training, procedure validation, and anomaly investigations.
Launch and Early Orbit/Commissioning (LEOC)On-Orbit Operations
Observatory Systems EngineeringObservatory systems/subsystem engineering staff for LEOC. LEOC activities/support notionally as follows (Days x Hours):

Observatory activities will occur:

- S/C activation during the first 48-hours (24x7)

- Instrument activation during the first 30 days (12x7)

- Instrument commissioning and WRS demonstration for remainder of LEOC period (10x5)S/C system engineering staff for on-going/long-term operations
Ground Systems EngineeringMaintain glueware and scripts, where needed, to integrate and streamline MOC operations and processes. After delivery by developers, prepare MOC subsystems for use by establishing/maintaining operational user-defined configurations. Provide project database maintenance. Support ground anomaly investigations and resolution.Maintain glueware and scripts, where needed, to integrate and streamline MOC operations and processes. After delivery by developers, prepare MOC subsystems for use by establishing/maintaining operational user-defined configurations. Provide project database maintenance. Support ground anomaly investigations and resolution.
Realtime OperationsTrained/certified Console operations staff ("Ops Controller") for realtime Observatory command and control operations.
Expect 24x7 console operations for Observatory health and safety monitoring during LEOC, with lights-out automated operations beginning post-MTHR.Ops (controller) and flight dynamics staff for on-going/long-term operations
Planning & SchedulingTrained/certified Planning and Scheduling staff for LEOC.

Observatory activation and checkout will occur:

- S/C activation during the first 48-hours (24x7)

- Instrument activation during the first 30 days (12x7)

- Instrument commissioning and WRS demonstration for remainder of LEOC period (10x5)Planning and Scheduling staff for on-going/long-term operations
Flight Dynamics/
Orbit OperationsTrained/certified Flight Dynamics/Orbit Operations staff for LEOC.

Observatory activation and checkout will occur:

- S/C activation during the first 48-hours (24x7)

- Instrument activation during the first 30 days (12x7)

- Instrument commissioning and WRS demonstration for remainder of LEOC period (10x5)Flight Dynamics/Orbit Operations staff for on-going/long-term operations
Anomaly InvestigationsBucket of hours to cover contingency and anomaly support and investigations
Provide basis-of-estimate for this scope (e.g. - expect n anomalies requiring x additional staff support)Bucket of hours to cover contingency and anomaly support and investigations

Provide basis-of-estimate for this scope (e.g. - expect n anomalies requiring x additional staff support)

MOC Sustaining EngineeringDevelop and implement any fixes or enhancements defined during the operations phase to minimize on-going operations costs and mitigate risks. On-going ITSecuriity patching, as needed.
Network/Infrastructure SupportProvide network/system adminstration, IT Security, and infrastructure management/support to establish and maintain MOC systems. See Attachment C - L10 MOC Functions Summary for further information.Provide network/system adminstration, IT Security, and infrastructure management/support for MOC systems. See Attachment C - L10 MOC Functions Summary for further information.
ODCsMOC Development and I&T, Mission Ops Readiness, and LEOCOn-Orbit Operations
ODC/Equipment and HardwareAll equipment, hardware, and computer systems required for MOC development, I&T, and LEOC (e.g. servers, racks, cabling, routers/switches, operator consoles, ops center furniture, etc.)
Note: Exclude costs for Launch Support Room (notionally located at NASA/GSFC). LSR to be provided by NASA.Ongoing costs for refresh of equipment, hardware, and computer systems required for MOC on-going/long-term operations
ODC/Software LicensesLicenses for any software needed for development, I&T, and LEOC, including license renewals (as needed) until mission transition & handover review (MTHR) to USGS/EROS ops organization.
Note: Exclude costs for Launch Support Room (notionally located at NASA/GSFC). LSR to be provided by NASA.Ongoing costs for renewal of necessary software licenses for on-going/long-term operations
ODC/Cloud Services (if required)Cloud licenses and other expenses for establishing and maintaining any cloud environment required for MOC development, I&T, and LEOC.

It is expected that any cloud-based MOC capability will need to be in GovCloud and procured via USGS cloud hosting services (CHS 3).

Note: Exclude costs for Launch Support Room (notionally located at NASA/GSFC). LSR to be provided by NASA.Ongoing costs for any cloud services needed for on-going/long-term operations
ODC/NetworksCosts for any network services needed for development, I&T, and LEOC, that are not provided by the project (note that network hardware is covered under the "ODC/Equipment and Hardware" category)

Note: Exclude costs for Launch Support Room (notionally located at NASA/GSFC). LSR to be provided by NASA. Ongoing costs for any network services needed for on-going/long-term operations that are not provided by the (ops) project Note that costs for network hardware refresh are covered in the "ODC/Equipment and Hardware" category

OCD/OtherPlease provide a description of any additional ODCs included in the estimate within the Notes column.Please provide a description of any additional ODCs included in the estimate within the Notes column.
MOC Subsystems/Functions List
Telemetry & Command (T&C)See

Attachment C - L10 MOC Functions Summary for descriptions

Flight Dynamics/Orbit Operations
Planning & Scheduling
Contact & Activity Orchestration
Configuration Management & State Management
Trending & Analysis
Alerts & Notification
Load Builder/Generator and Validation
Analytical Modeling & Simulators
Network and Infrastructure
Mission Operations Situational Awareness
Other Tools/Capabilities

File details come from the government source that posted it. Updated .