# Presentation: 129597

## Core Trajectory Subsystem(CTS)

- Orion to ISS Mission Class

- 3/25/08

## Purpose of Presentation

- Provide and overview of the CTS project
- High Level Functional Overview
- Infrastructure/Language Choices

- 3/25/08

## Project Overview

- 3/25/08

## Project Overview

- In December of 2006, the Flight Design and Dynamics Division (FDDD) at JSC presented a proposal to re-architect their trajectory software to:
- Improve maintainability
- Improve usability
- Reduce cycle time for changes
- Provide Constellation Lunar capabilities
- Reduce long term sustaining costs
- Support ISS and CxP

- 3/25/08

## FDDD Currently has 5 Major Systems

- FDDD

- Trajectory
- Server

- Operations

- Flight Design

- Design/Production
- Analysis
- Limited Ops

- Platform Independent
- Software Components
- for the Exploration
- of Space

- Operations

- Total FDDD KSLOC:  ~9 MSLOC

- Trajectory Subsystem
- Applications

- Operations
- Analysis

- Trajectory Operations
- Officer Stars

- Design/Production
- Analysis

- ~1.5 MSLOC

- ~0.5 MSLOC

- ~0.2 MSLOC

- ~0.8 MSLOC

- ~6 MSLOC

- 3/25/08

## New Architectural Approach

- Greatly reduce FDDD’s maintained code base
- All current FDDD code will be archived upon completion of the project
- CTS makes extensive use of open source and COTS to provide most of the computer science related functions
- Stretch Goals for CTS
- Decrease maintenance costs
- Maintaining one system versus five
- Decrease turn around time for changes due to a modular software approach
- Automated test methodologies will reduce the cost/time required for testing
- Interface isolation will reduce ripple effect in our software which will decrease maintenance costs.
- Choice of Language/Standards will allow for low cost rehosts
- Standards based approach will reduce risks of vendor lock-in
- Reduce development costs
- Upgrade one system with Lunar capability
- Modular architectural approach will make it easier to add new models of an existing type (e.g. atmosphere, engine, etc.)
- Improve scalability
- System design will be able to automatically take advantage of new resource when they become available
- Improve usability and customer satisfaction
- Provide consistency in look and feel across the software base
- Decrease user operations notes relating to the software

- 3/25/08

## New System’s Architecture

- Integration

- Domain

- Traj Apps

- Core Trajectory

- Presentation

- Note: Leverage off of existing 6 DOF simulations

- 3/25/08

## Functional Overview

- 3/25/08

## High Level Functional Description

- Our users perform all of the Trajectory Analysis, Pre-mission Design, Operations, Post-Flight Assessments, and Navigation for the Human Space Flight Program
- They support the Space Shuttle Program (SSP), International Space Station (ISS), Constellation Program (CxP) and other vehicles
- They support Ascent, Orbit, Rendezvous, and Entry Phases

- 3/25/08

## Analysis & Pre-mission Design

- Analysis
- How changes in the vehicle, environment, or procedures impact the vehicles trajectory, performance, and margins.
- Both nominal and off-nominal conditions.
- We answer “what if” type questions
- Pre-Mission Design
- Determines what the specific trajectory will be for an upcoming launch or mission phase
- Determines the trajectory margins for the flight
- Results in products that are consumed by the rest of the program

- 3/25/08

## Operations

- Monitor the vehicle, determine where the vehicle is, tell the vehicle how to get where it needs to go
- During critical phases (Ascent, Rendezvous, and Entry) system failures cannot be tolerated and performance is a key concern
- - Possible loss of crew and loss of vehicle
- Done by flight controllers in a highly collaborative environment.  A lot of concurrent use of data and user interaction with the system.

- 3/25/08

## Post-Flight Assessments

- Answers the question of how did we do?
- What was our actual trajectory?
- Did the vehicles performance match our predictions?
- Covers all phases of flight

- 3/25/08

## Infrastructure/Language

- 3/25/08

## CTS Product Line Overview

- Three basic parts to CTS’s product line
- Infrastructure/Integration
- Contains the computer science functionality of inter-process communications, status and control, availability, resource utilization, etc.
- Domain
- Contains the trajectory computations needed to meet functional requirements (e.g. F=ma)
- Presentation
- Contains common components that allows users to view/interact with the rest of the system

- 3/25/08

## Industry has Solutions for Infrastructure & Presentation

- CTS will use industry solutions for infrastructure and presentations
- Widely available in industry
- Used in multiple critical industries today such as banking, the stock market, automotive, etc.
- Adheres to standards which helps avoid vendor lock-in
- Available on multiple platforms
- Chose Java due to its availability, robust standards, and widespread use in industry.
- Proof of concept performed to verify performance and reliability is acceptable.
- Java Standard Edition and Enterprise Edition to be used for the infrastructure.
- Currently using JBoss Application Server and Clustered MySQL Database technology.
- Growth path to go to Oracle database technology

- 3/25/08

## Domain will Re-use PISCES Software

- CTS is re-using the Platform Independent Software Components for the Exploration of Space (PISCES) software for the domain
- Investigation of industry solutions for the domain layer haven’t yielded an option that meets all of FDDD’s functional requirements.
- No standards between industry domain tools
- If you pick one, you are locked into that vendor

- 3/25/08

## Summary

- 3/25/08

## Summary

- CTS replaces all of FDDD’s software with one integrated set of software deployable to analysis, operations, and production
- Greatly reduces FDDD’s maintained code base
- Decreases maintenance costs
- Reduces development costs
- Improves scalability
- Improves usability and customer satisfaction
- CTS is using a blend of open source solutions and custom code to achieve its goals.
- CTS project is currently 6 months into a 5 year development effort that supports the Orion to ISS Mission Class

- 3/25/08

## Backup Slides

- 3/25/08

## Software Mapping between Items on Chart 5 and MOD Software Inventory

| Items on Chart 5 | MOD Software Inventory |
| --- | --- |
| Trajectory Subsystem Applications | Items marked FDD/TRAJ in Development/Sustaining Division column |
| Trajectory Server | Items marked FDD/TRJ SERVER in Development/Sustaining Division column |
| Flight Design | Items marked FDD, except FDD/TRAJ and FDD/TRJ SERVER in Development/Sustaining Division column |
| Platform Independent Software Components for the Exploration of Space | Application marked VVTaTO in the Application/Script name column |
| Trajectory Operations Officer STARS | Application marked TOPO STARS in the Application/Script name column |

- 3/25/08