# Presentation: 809709

## Mission Control Center Systems (MCCS)Development for the Constellation Program (Cx)Summary Overview

- March 25th, 2008

- Mission Operations Division
- DD221/Larry Bishop
- MCCS Project Management

## Mission Control Center Systems (MCCS) Overview Agenda

- MCCS Development Objectives/Purpose
- Project Scope
- Functional Breakdown Hierarchy
- Reviews/Products Summary
- Systems Definition Review Process
- Schedule
- Current MCCS Functional Overview
- Work Overview
- Project Risks
- Lifecycle Cost Strategy
- Principal drivers and constraints
- Transition Concepts/Strategy
- C3I/CSI Concepts
- MCCS Level A, B Requirements and IRD/ICDs
- Document Tree
- Forward Plan

- MOD DA, DD2 MCCS

- 3/25/08

## MCCS Development Objectives/Purpose

- The overall objective for Cx’s Orion-to-ISS mission is to modify/augment the Mission Control Center System (MCCS) to successfully support the Cx Ares test flights and the initial Cx Mission Class, Orion to ISS.  The proposed modifications and augmentation should cost effectively lead to the next Mission Class, Lunar Sortie.

- MOD DA, DD2 MCCS

- 3/25/08

## Project Scope

- MCCS Scope:
- MCCS consists of the Mission Control center (MCC), Integrated Planning System (IPS) and MCC Automation System (MAS) systems. All three systems are multi-program, supporting Shuttle, ISS and Constellation missions.
- Cx Missions supported for this review includes Ares 1-Y test flight, Orion 1 and subsequent Orion to ISS missions.
- Does not include:
- Lunar Sortie mission class except where otherwise noted.
- MCCS effort to decommission Shuttle (2010), but does rely on Shuttle MCCS equipment that is decommissioned for MCCS Cx development.
- Any plan for decommissioning of ISS support (assumed post 2020).

- MOD DA, DD2 MCCS

- 3/25/08

## Slide 5

- MOD DA, DD2 MCCS

- 3/25/08

## MCCS Reviews and Product Summary

|  | Pre-Phase A | Pre-Phase A | Phase A | Phase B | Phase B | Phase C | Phase D |
| --- | --- | --- | --- | --- | --- | --- | --- |
|  | Requirements
Review (RR) | MissionConcept Review (MCR)/
MCTR | System Requirements Review (SRR) | System Definition Review (SDR) | Preliminary Design Review (PDR) | Critical Design Review (CDR) | PRR, TRR, SAR, DRR, ORR |
| 1. Mission objectives, constraints, assumptions, goals,guidelines | Detailed list | Updates | Updates | Updates | Updates | - | - |
| 2. Requirements | High level (A) | High level (A) Updates | Detailed Level (B) | Updates | Updates | Updates
(Baseline) | Updates |
| 3. Operational Concepts | High Level Operational Concepts (Cx) | Updates | Detailed Operational Concepts (MOP, BOP) | Updates | Updates | Updates
(Baseline) | Updates |
| 4. Interfaces | High level Requirements | High Level (IRDs) | Detailed I/F Concepts | Updates | ICDs including signoff | Updates
(Baseline) | Updates |
| 5. Systems Engineering analyses and trade studies | As needed | Trade Study focus | As needed | System engineering analyses focus | As needed | As needed | As needed |
| 6. Prototyping | As needed | As needed | As needed | As needed | As needed | - | - |
| 7. Architecture | Concepts | Functional, Data, HW, SW, ETE Data Flows | Updates | Functional, data, hardware, software, ETE | Architecture fully developed | Develop build-to specifications | - |
| 8. Transition Plan | Concepts | Concepts | Concepts | Initial plan developed | Complete Plan developed | Updates
(Baseline) | Updates |
| 9. Implementation | Prototyping (C3I/Center Collaboration) | Prototyping (C3I/Center Collaboration) | Prototyping (C3I/Center Collaboration) | Prototyping (C3I/Center Collaboration) | Prototyping (C3I/Center Collaboration) | - | Procurement and software development |
| 10. Test | - | Initial Test Concepts | Test Landscape, VerificationReq | - | Final Test Concepts | - | All levels of testing |

- Note:  1.Bold underlined format is a primary product for that review.  2.Plans, risk, cost & schedule are managed on all reviews.

- MOD DA, DD2 MCCS

- 3/25/08

## Scope- SDR Process

- MOD DA, DD2 MCCS

- 3/25/08

## Slide 8

- MOD DA, DD2 MCCS

- 3/25/08

## Slide 9

- MOD DA, DD2 MCCS

- 3/25/08

## Work Overview

- Following work items have been identified to prepare the MCCS for support to the Orion to ISS missions
- Develop MCC Command, Control, Communication and Information (C3I) Compliant Command/Control (C2) Subsystem (i.e. Front End Processors and Command)
- Develop Core Trajectory Subsystem capability
- Develop MCC & Cx MAS TLM/CMD user applications
- Procure MCC two-way FEP-voice and video subsystem interfaces
- Modify Timing for CxP (if required)
- Modify Platform services (e.g. activity separation)
- Procure additional:  MCC workstations, servers, Data Storage and Web interface to this data
- Procure additional Mission Data Storage Complex (MDSC) storage
- Modify MCC/IPS LANs as required
- Document and modify external interfaces as required
- Develop IPS web-based interface to Constellation Planning Systems (CPS)
- Develop resource utilization & planning system models for CEV electrical, thermal and environmental
- Procure: additional IPS workstations and servers
- Modify PIM screening for additional data types as required
- Provide required interfaces to connect the Cx MAS to the MCCS LAN
- Modify IPS – Cx MAS and MCC – Cx MAS interfaces
- Procure: additional workstations, servers and LAN equipment in support of Core Trajectory Subsystem
- Note that no changes to this list has occurred from the MCCS Mission Concept Review (MCR), but change within work items have occurred as better details become available (e.g. Core Trajectory Subsystem)

- MOD DA, DD2 MCCS

- 3/25/08

## Project Risks

- Level 4 (MCCS) Schedule and Cost Risks
- Safety issues identified later in this presentation (Orion-MCCS C3I/CSI interface issues) will not be resolved as needed by the current schedule (prior to today’s review). Currently participating in C3I Volume CR reviews to mitigate risk.
- Shuttle equipment planned for reuse will not be available as needed by this schedule (between June 2010 to January 2011), causing either a delay in schedule or a significant cost impact to procure additional workstations, servers and other MCCS hardware.
- Level 3 (Mission Systems) Risk
- Cx IRMA #1566: C3I/CSI requirements maturity and change traffic. Currently participating in C3I Volume CR reviews to mitigate risk.
- Cx IRMA #2085: MCCS Costing Architecture content versus budget (FY10-20). Currently in analysis mitigation step to reduce deltas or modify architecture for MCCS SDR.

- MOD DA, DD2 MCCS

- 3/25/08

## Lifecycle Cost Strategy

- A significant Cx MCCS development cost avoidance has been planned by:
- Reuse of current MCCS strategy
- Reuse of Shuttle equipment planned for decommissioning
- Leveraging from Equipment Replacement projects such as LANs, MWSOR, and IPS Platform
- MCCS has been challenged to reduce ISSP/CxP Life Cycle Costs (LCC).  DD2 has identified the following opportunities for LCC reductions (including sustaining cost avoidance).  These items are planned for further analysis as part of MCCS SDR (no specific order, all will be assessed as part of SDR):
- Use of same/similar hardware & software for ISS and Orion (e.g., MCC & IPS workstations & servers, LANs, Voice, Video, Linux OS, RDBMS)
- Use of same/similar hardware that MORS and CxTF are planning to use
- JSC Baseline Operations Plan will drive numbers of workstations/positions in 2008, and may reduce sustaining costs of hardware and software licensing
- Decommission and reuse of a subset of the Shuttle workstations
- Greater use of Office MPSRs (e.g. MCC situational Awareness and Secure Planning (most) Anywhere concept) will reduce workstation numbers
- Automation to reduce Ops Support Team costs

- MOD DA, DD2 MCCS

- 3/25/08

## Lifecycle Cost Strategy (cont)

- Opportunities for sustaining cost avoidance are planned for further analysis as part of MCCS SDR are exampled by:
- Consolidation of:  Database systems (Oracle or SQL Server) to a single RDBMS to reduce total licensing cost for IPS and CxMAS; web services to a single web service for IPS and CxMAS; MCCS Firewalls and licensing; multiple Core Trajectory Subsystems with one subsystem, reducing overall code count and sustaining costs
- MCCS solution for security software login/audit services (e.g. LDAP, ARM, IDS)
- Decommissioning of MCCS elements used for Shuttle only (not shared with ISSP):
- Flight Design
- MCC SSP User Applications
- SSP Command software
- SSP FEP software
- OCA (SSP elements)
- ODRC (SSP elements)
- Shared development and sustaining of CxTF and MCCS RUPSM models
- Reuse of MDSC data storage to be shared by CxTF, MORS and MCCS
- Potential Center collaboration to reduce development and sustaining cost of CxP vehicle Data Storage
- Potential extension of Secure Planning (most) Anywhere concept to IMARS to reduce number of workstations
- Opportunities for sustaining cost avoidance are planned for further analysis as part of MCCS SDR

- MOD DA, DD2 MCCS

- 3/25/08

## Objectives/Primary Requirements   (Orion to ISS)

- Modify/augment the current Mission Control Center System (MCCS) in order  to successfully support the Constellation (Cx) test flights and initial Cx Mission Class, Orion to ISS.
- Ensure the proposed modifications and augmentation will cost effectively lead to the next Mission Class, Lunar Sortie.
- Minimize operational impacts within MCCS amongst SSP, ISSP, and CxP
- Reduce MCCS life cycle costs:
- Leverage from Equipment Replacement (ER) projects to reduce life cycle costs.  Three example projects are IPS Platform ER, LAN ER, and MCC Workstation, Server, Operating /system Replacement (MWSOR)
- Reuse Shuttle equipment in the MCCS where practical (e.g. LAN switches, Linux Workstations, Linux rack mounted & blade servers) to avoid development and sustaining costs
- Reuse legacy external interfaces where practical
- Procure small delta quantity of WS’s & Servers for development & testing.  Use these until Shuttle equipment can be transitioned.  Last flight is June 2010.
- Minimize dual capability sustaining
- Implement MCC Benchmarking Final Report recommendations where actions/analysis shows benefits (e.g. More office environment usage)
- Automate Operations Support Team functions where practical
- Look for opportunities for center collaboration and incorporate into the MCCS development effort if possible (e.g. Data Storage/Archive)
- Be interoperable with the CxP Projects and elements by meeting the C3I/CSI requirements where possible
- Apply MOS Design principles where applicable for MCCS development

- MOD DA, DD2 MCCS

- 3/25/08

## MCCS Transition Concepts

- The Mission Control Center System (MCCS) is to be developed as a single integrated institutional system, with few unique requirements for the Mission Control Center (MCC), Integrated Planning System (IPS), and MCC Automated Systems (MAS).
- MCCS is to be developed as a multi-program element that supports Shuttle (until decommissioned), ISS, and CxP
- MAS that supports CxP is to be brought inside the MCC/IPS firewall, and become an integrated part of MCCS, supporting planning and control center functions.  Secure remote access to Cx MAS will be maintained.  At least part of ISS MAS will remain on the INS, and secure remote access by the ISS International partners will be maintained
- A single MCCS multi-program set of documentation (e.g. Level A and Level B Requirements, System Design Notebook) is to be developed and sustained.  The intent is to merge these documents with their Shuttle/ISS counterparts at a time to be determined by the L4 Project Managers.
- A core trajectory analysis capability will be developed that supports both MCC Trajectory function and Cx IPS Flight Design function.
- Re-use of some MCCS shuttle equipment after decommission is planned in order to reduce CxP development costs.
- Remote operations from the JSC Office environment are to be greatly increased including, but not limited to, access to all planning functions, real-time and stored telemetry data, trajectory, voice and video (within the constraints of the Privacy Act and ITAR).
- The Limited Station Operations Support (LSOS) area will be used to continue to support MCC operations with ISS during selected transition activities (e.g. Shuttle decommission, destructive MCCS functional  testing).  Analysis to be done will determine how many, which rooms, and when Flight Control rooms and Multipurpose Support Rooms will be required to support ISS/CxP concurrent operations.  The current MS SRD requirement is to support ISS, 3 (TBR) active CEV operations, and 3 (TBR) quiescent CEV concurrent operations.
- Decouple the MCCS at the interface to the SCIP, and also at the applications layers to the vehicle and to the MCC Framework to the extent possible to facilitate cost effective development, testing and phasing.

- MOD DA, DD2 MCCS

- 3/25/08

## Basic Transition Strategy

- Basic Transition Strategy is:
- Continue to support continuous ISS operations (24 x 7)
- Support SSP Flight Manifest including 30-60 day lockdowns and Post processing until last flight in August 2010.
- During non-critical operations time, support ISS using Limited Station Operations Support (LSOS) area.
- While ISS is being supported in LSOS, the remaining part of MCCS can be modified.  Method has been previously used to transition from FDDI to Switch Ethernet LANs and MWSOR.
- Cx FEPs, Command and other MCCS development projects are prototyped in the OTF, built in the GSDE and/or User Development Labs, integrated in the CDE and then moved to the MCC Operations area for TRR, SAR and ORR activities.

- MOD DA, DD2 MCCS

- 3/25/08

## C3I/CSI Concept for CxMCCS Downlink

- Serial Converter Processors (SCPs) have been transitioned to Space Communications and Networks (SCaN) at GSFC
- Performs de-commutation, CCSDS, 1/2LDPC, HDLC processing
- Sends IP to the MCC FEP
- MCC Front End Processors are planned to be located in the MCC
- Performs IP processing
- Strips voice from the telemetry and sends to converters for the MOVE subsystem voice distribution
- Strips video from the telemetry and sends to converters for the Video subsystem analog (NTSC, RGB) and digital (SD/HD/SDI) distribution
- Converts remaining telemetry to Processed Telemetry Messages and Network Data Messages using Reconfiguration products from MORS.  PTMs/NDMs are multicast on the MCCS LANs, and re-distributed over the SCaN networks as required.
- Raw and Processed telemetry messages are received at the MCC workstations within the activity separation concept, and processed by Data Acquisition (Acq) software.  MCC User applications can access the data from Data Acq or Information Sharing Protocol (ISP) via publish/subscriber
- Voice, Video and telemetry distribution via Framework within the MCC do not follow the C3I standard, but rather use legacy subsystems and methods.  A Decision Package has been submitted to allow use of C3I concepts within the MCC either as part of CEV-ISS or Lunar Sortie mission classes.
- Note: this concept applies to MCC interfaces to CxP vehicles, DSIL/CAIL, and CxTF.

- MOD DA, DD2 MCCS

- 3/25/08

## C3I/CSI Concept for CxMCCS Uplink

- Commands are initiated from the authorized users located at MCC workstations
- Separate login is required. Compliant with two factor authentication required by HSPD12.
- Commands include standard, scripts, time-tagged, event triggered and automated command execution.
- Commands are also required to be initiated from remote facilities per the MS SRD.  Remote command capability phasing is TBD.  Remote commanding will use MCC Command and Communication (FEPs) subsystems.
- Commands may also be required to be initiated from a Backup Control Center.  Addition of a BCC requirement is pending RMA analysis (TBR-MOPOC-1).  BCC capabilities are listed in the CxP 72131 MOP Operations Concept.
- Uplink Front End processors (FEPs) generate an IP format uplink containing voice data (from MOVE), video data (from Video subsystem) and commands (from Command subsystem)
- Command data is encrypted per CxP security standards
- SCaN SCPs process the IP data into C3I format for uplink to the CxP vehicle

- MOD DA, DD2 MCCS

- 3/25/08

## C3I/CSI Concept for CxMCCS Ground to Ground

- External interfaces are under analysis to determine which ones can be C3I compliant, and which ones will remain legacy or change to another standard.
- See MCCS Technical Description, Interface Definition Table

- MOD DA, DD2 MCCS

- 3/25/08

## C3I/CSI Concept for CxMCCS Data

- MCCS Front End Processors (external side) and MCCS Command applications plan to use (C3I) Interoperability Standards Book, Volume 4:  Information Representation Specification
- The Data Storage subsystem plans to use C3I Volume 4 if implemented via Center Collaboration.  If reuse, then the legacy formats will be used.
- All other MCCS data plans to use legacy formatting for Orion-ISS.

- MOD DA, DD2 MCCS

- 3/25/08

## C3I/CSI Concept for CxMCCS Reconfiguration

- MCCS Front End Processors and Command subsystem will use C3I reconfiguration products and processes supplied by the Mission Operations Reconfiguration System (MORS)
- The following MCCS subsystems will use legacy reconfiguration products (e.g. ISP data dictionaries).
- Front End Processors
- Data Display Complex System (DDCS) workstations
- Platform Services (including ISP)
- Core Trajectory Subsystem
- Data Storage
- Test facilities such as OTF, GSDE, CDE will use a mix of C3I and legacy reconfiguration products
- MCCS also generates Recon products (e.g. Initialization files (I Loads) )

- MOD DA, DD2 MCCS

- 3/25/08

## MCCS Level A Requirements (JSC-63796) 

- Development Method
- Generated from CARD/MS SRD flowdown and existing SSP/ISS MCC/IPS/MAS Level A Requirements documents
- Presented at MCCS Requirements review (July 2006) and at the MCCS MCR (April 2007).  Disposition 123 and 98 RIDs, respectively for the two reviews.
- Merged the 3 documents into a single MCCS Level A Requirements document
- Updated MS SRD flowdown and traceability based on MS SRD changes during the MOP SRR baselining process.
- Developed an MCCS Requirements Unique ID, including allocation of each requirement to an MCCS subsystem
- Specified the program supported (SSP, ISS, CxP) for each requirement
- Phased each MCCS CxP requirement based on Mission Class and PPBE in guideline
- 1071 MCCS Level A Requirements identified.  Note that SSP/ISS Level A Requirements total for MCC, IPS and MAS is approximately 900.
- MCCS Level A to MS SRD Traceability matrix is included in the Appendix.  MCCS Level A traceability to SSP/ISS Level A’s is in Appendix G, MS SRD to MCCS Level A flowdown matrix available by request
- Requirements will be posted (as applicable) to the FDOC Library

- MOD DA, DD2 MCCS

- 3/25/08

## MCCS Level B Requirements,Interface Requirements Documents and Interface Control Documents

- Level B Requirements
- Each MCC Subsystem Level B requirements document will be updated to reflect the flow down of the MS, Systems Requirements Document (SRD)
- Documents will be published, to the FDOC Library, accordingly
- Cx Interface Requirements Documents (IRDs)
- IRDs will be the Level A equivalent of an Interface Control Document (ICD)
- IRDs will be published, to the FDOC Library, accordingly
- MCCS Level A traceability to SSP/ISS Level A’s is in Appendix G, MS SRD to MCCS Level A flowdown matrix available by request
- Requirements traceability will be posted (as applicable) to the FDOC Library
- MS/MCCS Mission Concept Review (MCR) and Systems Requirements Review (SRR) documentation will be published to the FDOC library accordingly
- A documentation tree (following page) depicts all development documentation. These
- documents will be published to the FDOC library when approved by the FDOC
- Contracting Officer and JSC Procurement.

- MOD DA, DD2 MCCS

- 3/25/08

## JSC xxxxx MCCS 

- JSC xxxxx MCCS

- Operational Concept

- MCCS

- Interface

- Control

- Documents

- (

- Part

- 2

- )

- MCCS

- System

- Design

- Notebook

- MSOC

- -

- DRD

- -

- 0068

- Test

- &

- Verification

- Plan

- (

- MCC

- ,

- IPS

- )

- JSC

- 64019

- MCCS System

- Engineering

- Management

- Plan

- MCCS

- Subsystem

- SEMPs

- (

- as

- required

- )

- MOD DA, DD2 MCCS

- 3/25/08

## MCCS Plan Forward

- Conduct MCCS SRR RID & Comment cycle and improve products
- Develop formal trade studies for each subsystem to determine the system and subsystem architecture for MCCS SDR in June 2008.  Use options identified in the Decision tree, and in OTF prototyping efforts.
- Support MOP and MCCS System Engineering Analysis trade studies
- Update the MOP ADD and provide other support to the MOP SDR
- Continue to track prototyping efforts in the DD Operations Technology Facility (OTF) to determine baseline architecture changes
- Continue to work with the Orion contractor on space-ground interface definition and resource utilization planning models.
- Review and assess CxP CRs that impact MCCS (C3I/CSI Volumes) operational concepts, requirements, and architecture.

- MOD DA, DD2 MCCS

- 3/25/08

## Slide 26

- MOD DA, DD2 MCCS

- 3/25/08

## Slide 27

- MOD DA, DD2 MCCS

- 3/25/08