New Horizons SOC Peer Review

1
New Horizons SOC Peer Review
Science Operations Center Implementation
PlanJuly 21, 2003
John Andrews SOC Project Manager 303-492-6092 andr
ews_at_casa.colorado.edu
2
Topics of Discussion

• Review of SOC Functions Deliverables
• Summary of schedule requirements
• SOC Development schedule
• SOC Phase C/D Staffing Plan
• SOC Phase E Staffing Plan
• Longevity Planning
• Risk Assessment
• Future Work Plans

3
Review of SOC Functions Deliverables
4
Summary of Schedule Requirements

• Key need dates for the SOC development are driven
  by the missions development schedule. Those
  dates and the milestones within the SOC are
• Have CSOC in place at APL by late summer 04 to
  support IT
• Full functionality in Science Ops Sequencing
• Limited functionality in Science Data Pipeline
  (beta version)
• Have TSOC/CSOC in place and verified by 1/05
  prior to MSIM 2a which is scheduled for 2/05
• T/CSOC both to have full functionality in SciOps
  Sequencing
• Goal to have Science Data Pipeline up and able to
  accept instrument data from the 05 MSIMs
• Goal is to place appropriate IT data into
  flat-files for future reference and database
  build
• TSOC/PDS interface should be up and functional
  prior to launch in 1/06
• As shown earlier, Sequencing schedule quite
  active throughout phase C/D to provide MSIM,
  post-launch checkout, Jupiter encounter, annual
  checkout, and Pluto/Charon encounter sequences

5
SOC Development Schedule

• The detailed SOC development schedule is attached
  as a MS Project output.

6
SOC Phase C/D Staffing Plan
7
Tentative SOC Phase E Staffing Plan
8
SOC Longevity Planning

• The SOC will adhere to the overall NH Longevity
  plans
• Specifically the SOC will employ
• Paper oriented documentation system for archiving
  users guides, manuals, etc. Data will not
  inherently be dependent upon a machine
  configuration or specific software package.
• Selection of programming languages, software
  packages, etc. that are readily portable, stable
  and well documented, and in wide-spread use.
• A cross-training effort so that all SOC personnel
  can backfill for one another in emergency
  situations.
• Where possible, a recruitment and staffing plan
  whereby junior personnel are brought in on a
  timely schedule, trained and given experience,
  and then groomed for larger roles on the NH SOC
  and other SwRI flight missions.

9
SOC Risk Assessment

• A summary of the key risks associated with the
  SOC development are
• Communications access to personnel and data
  developing the NH spacecraft and instruments
  during a period when providing info to the SOC is
  perceived to be the least of their concerns.
• Mitigation frequent, and if necessary annoying,
  contacts with development teams to acquire
  necessary materials.
• Scope Creep on a fixed price and fixed schedule
  effort it is imperative that the SOC understand
  the prioritized requirements we must meet and
  work to those requirements.
• Mitigation understand and baseline a well
  understood and agreed to set of requirements that
  we will not diverge from.
• Resources Resource Continuity development
  success lies in the hands of a small team without
  a deep bench, which ultimately must function over
  some 12 years.
• Mitigation start with good and experienced
  personnel then implement a staff development plan
  for recruiting, training, and grooming future
  personnel to support the missions longevity.

10
SOC Upcoming Work Plans

• Key activities in the upcoming months and for the
  balance of this calendar year include
• Initiating the early CAS/Frag development for the
  mature science instruments (LORRI and ALICE)
• Complete the OPUS assessment and baseline it for
  the MDMP
• Complete and baseline the 2 key SOC documents
• SOC Requirements Document
• Science Data Pipeline Requirements Document
• Initiate the detail design of the Science Data
  Pipeline and SOC physical architecture
• Support the Mission CDR, Mission Operations
  Review, and a SOC Design Review