Release 1

1

• SMART-1
• GROUND OPERATIONS AUTOMATION

Wolfgang Heinen Rhea System at ESOC
www.rheagroup.com
2
The Smart-1 Mission

• ESA SMART Programmes
• Small Missions for Advanced Research in
  Technology
• Spacecraft payload technology demonstration for
  future cornerstone missions
• Early opportunity for Science
• Management faster, cheaper, smarter (harder)

• SMART-1
• Test Solar Electric Propulsion to the Moon for
  Bepi Colombo / Solar Orbiter
• 15 kg payload
• 370 kg spacecraft ( 1 m3 box, 3 axes stabilised)
• SMART-1 reports are available in web page
  (http//sci.esa.int/smart-1/)

• ESOC
• SMART-1 is controlled from the European Space
  Operations Centre (ESOC)
• Research in Technology for Ground Operations

3
The Operations Automation Elements

• On-Board Autonomy
• Increasingly incorporated in spacecraft by the
  manufacturer, especially deep space missions
• Main problem remains in the high costs related to
  the software testing and validation

On-Board Control Procedures (OBCP) On-board
software maintenance can be covered by OBCPs
Advantage can be easily modified, can be
up-linked on-board completely independently from
the rest of the on-board software Study for a
generic OBCP editor
Mission Planning Systems (MPS) Used to build a
list of activities sequentially queued and
executed on board. Ground station coverage
limitations and manpower savings Planning of
Payload and Platform activities Smart1 uses an
affordable, cost effective generic MPS see
MPS04 Publication
Ground Operations Automation Systems
(GOAS) Routine phase (mission operations) Required
for Monitoring and Alarming, Routine Operations
and Contingency Operations and Recovery see
RCSGSO05 Publication on Envisat
4
The MOIS Toolset

• Smart1 has used the MOIS Toolset
• Used by most of the ESA/ESOC missions (Cluster,
  Envisat, MSG12, Smart1, Rosetta, Mars Express,
  Venus Express, Cryosat, GOCE, Herschel-Planck,
  Metop LEOP, XMM)
• Traditionally used to produce the formal Flight
  Operations Plan (FOP), a printed, configuration
  controlled document set.
• Operations Preparation Tools
• Procedure Editors Writer, Flowcharter,
  Timeliner
• Configuration Control Library Browse,
  Administration
• Validation Tools Manual, Test Harness,
  Automatic
• Reporting and Publishing
• Mission Planning / Scheduling
• Scheduler

5
The MOIS Procedure Constructs

• Procedure Flow Logic
• Use of Precondition, If, Switch, While,
  Repeat branching using Statement evaluations
  conditions e.g. check telemetry value, check
  variable value
• Procedure Statements
• Telecommand Telemetry Statement execute TC or
  check TM from MCS
• CEV Statement ask CEV result from MCS
• Procedure Call Statement execute sub-procedures
• Variables local and global store telemetry (,)
  for later checks global/system variables used
  for procedure synchronisation
• Directive and Function Statements send to MCS
  e.g. Control GS Link,
• Internal Function Statement executor interpreter
  e.g. Log a message, calculate seconds until Abs.
  Time,

6
Operations Automation Preparation

• Produced easily human readable automation
  procedures
• Used Toolset MOIS providing Flowchart
  tabular/sequential view
• Use the same editing tool for Flight Control
  Procedures, Mission Planning Procedures,
  Operational Procedures and Automation Procedures
• Integrate all 4 procedure types into one
  environment Configuration Control, Flight
  Operations Plan production, Mission Readiness
  reporting
• Flight control team has only to be trained on one
  tool
• Prefer Readability to Complexity S/C Engineers
  do not want to write code !
• Readable automation procedures can be visually
  inspected by non-experts
• Key for Procedure Validation, Review Acceptance

7
Human Readable Automation Procedures
Same Procedure Format visible at Design Time
Execution
8
Using Mission Planning for Automation

• Used Mission Planning System to schedule and
  drive Automation
• The same Scheduling system is used for on-board
  execution planning and real-time execution
• Provides all MPS features for automation !
  (Scheduling Constraints Checking)
• Constraints checks can be done cross-referencing
  both scheduling types when using shared
  resources.

MOIS
MOIS Library
Sequences
PayloadOperation Requests
FlightDynamic Requests
Procedures
EventFile
StationFile
MOIS Scheduler
Pass Plan
Mission Plan
SpacecraftOperation Requests
MOIS Scheduler
MOIS Executor
Schedule for uplink
Telecommand
Telemetry
MISSION CONTROL SYSTEM
9
The Operational Environment
MOIS
10
Operations Automation Preparation

• Testing and validation of the operations
  automation procedures is conducted at three
  levels
• Procedure level validation
• Test of individual procedures
• Using the MOIS Test Harness
• System level validation
• Running under the control of the MOIS
  Scheduler\Executor
• Driven by simulated spacecraft telemetry
• Operational validation
• Running under the control of the MOIS
  Scheduler\Executor
• Driven by real spacecraft telemetry
• Key to dispose of a set of integrated tools
  for Automation Concept
• Validation, Review Acceptance

11
Procedure Level Testing
MOIS
12
Procedure Level Testing
MOIS
MOIS Library
13
System Level Testing
MOIS
14
System Level Testing
MOIS
MCS SCOS 2000
S2K Interface
Simulator
MOIS Library
TM
Executor
TC
15
Operational Validation
MOIS
16
Operational Validation
MOIS
MCSB SCOS 2000
S2K Interface
Simulator
TM
Spacecraft
Test Harness
TC
17
Smart1 Automated Operations

• Objectives
• Automate routine activities for ground operations
  currently done manually by the FCT
• Spacecraft operations are largely automated
  through MPS (on-board TT Schedule)
• Routine Activities to be automated
• Routine download of platform housekeeping
  telemetry and events
• Intelligent download of payload telemetry
• Detection and download of gaps in telemetry
• Uplink of mission plans
• Level of Automation
• Automatic Execution - Operator assisted tool that
  executes procedures automatically
• Automation System - System that schedules and
  executes procedures used by the on-console team
  and that can be left unattended
• Lights-off System - System that schedules and
  executes procedures unattended and that can be
  remotely monitored

18
Automation Execution Planning
Mission Planning Standing Orders / Operations
Requests Dispose of a set of Procedures that
can be referenced by Operations
Requests Operations Request Files can be reused
! Mission Planning Attach ORs to Events
Flight Dynamics Events (Moon occultation, High
Rate,) Ground Station Coverage Events (AOS,
LOS) Synthetic Events events generated from
others following rules (HR Coverage) Routine
Automation Execution Planning needs minimal
effort from the FCT
19
Automation Execution Planning

• Flight
• Dynamics
• Events

Synthetic Events
20
Automation Execution Monitoring
Procedure Development and Global Cache Global
Variables provide a state vector these are User
Defined ! Procedures communicate and synchronise
against Monitoring via MMI on the automation
system Monitoring the State
vector via MMI gives an immediate Health Status
of the AS
21
Automation Execution Monitoring Automatic
Execution vs. Automation System
Alarms (Repeated Auditable Tone) Watchdog for any
failure in the automation system or link to the
MCS Configurable set of global variable values
raise alarms Disable Commanding Single action to
disable Resume must be handled in the
procedure Activity Logging Procedure Execution
statuses Changes in global variables (with
filter) Any message inserted at procedure design
time as a procedure statement Remote
Monitoring The activity log is published via
WWW An Automation System raises a new set of
requirements compared to an automatic execution
system !
22
Automation Execution Monitoring
Current Time
23
Automation Execution Monitoring
24
Automation Execution Monitoring
25
More Information
Visit the ESA SMART-1 Stand or the Rhea Stand _at_
SpaceOPS Publications from previous
Symposia Questions ?