CCSC Performance and Lessons An ISI Perspective

1
CCS-C Performance and Lessons -An ISI Perspective

• Steve Roth
• Deputy Program Manager CCS-C
• April 14, 2004

2
CCS-C Performance and Lessons -An ISI Perspective

• Background
• What is CCS-C
• Schedule Highlights
• Lessons Learned

3
CCS Historical Background
1984
1990
1985
1987
1995
1998
1997
2002
Ops transferred to AFSPC
Wing Activated
SSCS Began
CCS Transition Planning
SSCS Cancelled
CCS-C Contract Award
CCS IOC
CCS FOC

• Standard Satellite Control System (SSCS) - common
  core for Telemetry, Tracking, and Commanding
  (TTC) ground systems
• AFSPC/CV cancelled SSCS due to cost/schedule
  considerations
• CCS Sustainment Contract extended beyond Oct 31,
  2003
• CCS Transition Ongoing

4
Command and Control System-Consolidated (CCS-C)

• CCS-C contract awarded to Integral Systems Inc.
  Mar 02 to replace the legacy AFSCN Command and
  Control System used by 3 SOPS and 4 SOPS for
  current and future MILSATCOM operations
• Current - DSCS III and Milstar
• Future WGS, AEHF, and TSAT
• CCS-C FRD based on SSCS TRD The requirement
  document for the system that was intended to be a
  generalized for all USAF satellite command and
  control systems
• As a result, CCS-C is a very extensible system
  providing the flexibility to easily add new
  missions
• CCS-C architecture bridges a Core/MUS paradigm by
  incorporating legacy MUS into the Core CCS-C
  System reducing lines of MUS code, code
  sustainment, and accommodates efficient
  integration of new missions

5
CCS-C Features

• Design uses proven, commercially accepted COTS
  technology
• System integrates all tools to perform satellite
  ops
• Data products move from one tool to the next tool
• System permits operators to select what level of
  automation they want and when they want to change
  it
• Lets operators build confidence and then automate
  at their own pace
• Interactive ops procedures can check telemetry
  send commands
• Cuts operator error and allows automation on a
  per procedure basis

6
CCS-C Features

• TOs and crew logs are on-line
• Allows searches and printing, with hyperlinks to
  ops procedures
• Powerful trending and data analysis tools
• Now all data is available to be plotted quickly
  and easily
• Open APIs simplifies adding new features or
  meeting new data exchange requirements
• New tools can be easily added to the system
• One key requirement was to reduce ops manning by
  30
• CCS-C permits 1 operator to perform up to 4
  simultaneous contacts
• Vital objective requirement to reduce sustainment
  costs by 75
• Plan provides for robust maintenance with 24-hr
  on-site help desk

7
CCS-C Core Products
EPOCH Integrated Product Suite
EPOCH TC/Client Real-time command control
ABE Offline trends analysis
OASYS Orbit estimation and control
Database Adapt to specific missions

• This bundle provides the core functionality
  required to fly Satellites

8
CCS-C Operations Tools
CCS-C Supplemental Items

• This bundle augments the EPOCH Integrated Product
  Suite resulting in an Extensible CCS-C
  Architecture capable of easily supporting future
  satellite programs

9
CCS-C Operations Cycle
Planning Phase
Scheduling Phase
OA performs OD, determines need for station
keeping plans maneuver informs scheduling staff
Scheduling staff imports maneuver generates
SAT/PAP, exports to 22 SOPS receives 24 hr from
22 SOPS generates executable schedule including
TAO procedure with exact maneuver commands
exports schedule for execution
MPS
OASYS
OASYS performs automated OD several passes after
maneuver to verify maneuver quality report is
made available for OA inspection
Start
Schedule Executive
Schedule Executive allows any last minute
schedule change inputs then starts automated
execution of scheduled configuration and
procedures
ABE is used for post pass analysis and trending
it can plot any telemetry point over any period
of time, it can be used to automatically generate
Adobe PDF plots after every pass as shown
EPOCH TC Client
ABE
TAO
EPOCH TC Client permits Ops personnel to monitor
and control support.
TAO executes predefined procedure to perform
maneuver Operator can select three levels of
automation for each procedure from full manual to
full automatic
Real Time Phase
Trending Analysis Phase
10
CCS to CCS-C Comparison
11
CCS-C Schedule Highlights

• First fully functional SOC delivered 26 Sep 03!
• DSCS III/SOC 32 DTE Complete
• 18 months from contract award (as promised!)
• And along the way
• Jun 02 - CCS-C SDR
• Aug 02 - Contractor Development Laboratory
• Aug 02 - Core System Software CDR
• Oct 02 - DSCS Satellite Software CDR
• Oct 02 - CCS-C Test Facility
• Dec 02 - Milstar Satellite Software CDR
• Mar 03 - SOC 32 Facility Readiness
• Jun 03 - Core System Software DTE Complete
• Sep 03 - DSCS III/SOC-32 DTE Complete
• Sep 03 - WGS Satellite Software CDR
• Jan 04 - SOC 42 Facility Readiness
• Apr 04 - MTF Facility Readiness

New since AIAA 2003
12
CCS-C Schedule Highlights

• Upcoming in the next year
• SOC-32 (DSCS) and SOC-42 (Milstar) go operational
• Jul 04 - MTF DTE Complete
• Jul 04 - Milstar/SOC-42 DTE Complete
  (Incremental 2 vehicles)
• Sep 04 - AEHF Satellite Software CDR
• Dec 05 - WGS DTE Complete
• Jan 05 - Milstar/SOC-42 DTE Complete
  (Incremental 4 vehicles)
• Mar 05 - SOC-31 HW Facility Readiness
• Apr 05 - Milstar/SOC-42 DTE Complete (All
  vehicles)

13
Lessons Learned

• Issues and dependencies outside of ISIs control
  are the most difficult to address
• GFE/GFP Challenges
• CCS Source data
• Crypto
• SV Working Relationships
• Legacy
• Future
• Customer Relations Evolving Requirements
• 50 SW HQ AFSPC SMC

14
GFP/GFE Challenges

• CCS Source Data used to populate CCS-C
• Difficulty acquiring correct and timely data
  (i.e., telemetry and command database
  information)
• Legacy programs are still dynamic
• When to cut a baseline?
• Legacy CCS tools are antiquated and cannot
  properly extract data
• No support to correct the legacy tools schedule
  delays
• Resulted in
• Rapid response to correct/work around incorrect
  source data
• Continual schedule adjustments to accommodate
  source data deliveries
• Crypto
• Crypto performance less than legacy units
• Drives CCS-C contact timelines (in a negative
  way)
• Crypto upgrades have been problematic
• Each HW/SW delta has introduced its own new set
  of issues
• ISI has implemented creative, automatic
  workarounds to mitigate this issue
• Upgrades require considerable attention
• Lessons

15
SV Working Relationships

• Success of the ground system depends on effective
  working relationship with SV contractors
• Legacy DSCS/Milstar
• Legacy knowledge pool is a mix of SV factory, AF
  operators, and contractor TAs
• How it is done now can be a difficult question to
  answer
• Legacy system algorithms are not well known
• Legacy system documentation not current/not
  accurate
• Lessons
• Be proactive in notifying the customer of issues
• Be persistent to ensure the issues come to closure

16
SV Working Relationships

• Future Programs
• WGS
• WGS program slips due to vehicle
• Results in re-plan of CCS-C WGS build effort
• Data products tied to launch date
• AEHF
• AEHF program slips due to vehicle
• Lengthy delay between schedule slip and official
  new milestones
• CCS-C CDR moves
• Lessons
• As much as possible, De-couple deliverables to
  the ground system from SV launch!
• Maintain a close relationship with the vehicle
  contractors to stay current with dynamic schedule

17
Customer Relations Evolving Requirements

• Which Customer?
• Requirements HQ AFSPC/DR
• Acquirer SMC/MCC
• End Customer 50 SW (3 4 SOPS)
• 50 SW expectations/needs are not necessarily in
  sync with contracted efforts
• Operational users now fully engaged
• Users who will fly CCS-C are different personnel
  than those who participated in CCS-C fly-off
• Users desires evolving as they use CCS-C
• Process in place for identification of issues
• Discrepancy or enhancement?
• If enhancement, can it be accomplished as
  sustainment effort or is it a new requirement?

18
Customer Relations Evolving Requirements

• HQ AFSPC Requirements continuously evolving
• Transformational Comm!
• SMC/MCC adjusts taking into account cost,
  schedule, and performance.
• Dont get stuck in the middle COMMUNICATE!

19
Summary

• CCS-C is a COTS based distributed architecture
• CCS-C on schedule!
• Significant accomplishments this past year and a
  busy year ahead
• Learned to provide focused attention to our
  external dependencies
• Requires continual schedule assessments and
  re-planning to accommodate updated milestones
• Requires creative solutions to maintain schedule

20
Delivering Operational Capability DSCS III
Operations in SOC 32