OPS Forum ESTRACK Management System 19.06.2009

G-FORUM 19. June 2009, OPS-GIB Gerhard Theis

ESTRACK MANAGEMENT SYSTEM

EMSscope and benefits

OPS-GIB Margherita di Giulio


Scope of the ESTRACK Management System

- Nine stations owned by ESA plus three cooperative stations support ten operational ESA scientific missions and several missions of external users

- In order to coordinate the number of ESTRACK users and the network efficiently, an automated planning and coordination system is being developed.

- The previous (manual) scheme originated from a time of different ownership structures, low resources utilisation, low process complexity and low computing capability


Scope of the ESTRACK Management System

ESTRACK Management & Scheduling System (EMS) automates planning, scheduling and coordination :

Incorporation of user’s service requirements

efficient, conflict free and balanced resource allocation

maximisation of service provision


Advantages of the ESTRACK Management System

Advantages for ESTRACK users:

Efficient, centralized and time-saving conflict solving

Long-Term resource allocation simulations

User support for complete Planning & Scheduling life-cycle

Data exchange based on XML files, to facilitate further automation

Monitoring the execution of the schedule at the ground stations


Main Blocks of the EMS (1/2)

EPS

Master Plan

Users refinements

ESS

G/S Schedules

ESTRACK PLANNING SYSTEM (EPS) : • creates and maintains the ESTRACK planning database, combining

Event Files and Mission Agreement • it generate the ESTRACK master plan

ESTRACK SCHEDULING SYSTEM (ESS):• It “compiles” the ESTRACK plan from the EPS to produce ground

station schedules.


Main Blocks of the EMS (2/2)

ESTRACK COORDINATION SYSTEM (ECS) ECS is a network controller. It allows ECC to monitor the execution of

the ESTRACK G/S schedules from a central position. ECS uses the EPS and ESS products for distribution, monitoring and

(eventually) control of schedules.

G/S

Schedule

Master Plan

ESTRACK

Real-Time

Overview

ECS

MVL


A Brief Introduction to the ESTRACK MANAGEMENT SYSTEM

EMSobjectives -- architecture -- functions

OPS-GIB Gerhard Theis

slide 8G-FORUM 19. June 2009, OPS-GIB Gerhard Theis

EMS - overview

ESTRACK GROUND STATIONS NETWORK

MISSION OPERATIONS

ESTRACK MANAGEMENT SYSTEM

mediating between service requirements of space missions

and capabilities of the ESTRACK ground station

network


EMS - stakeholders and their objectives1 of 1

CUSTOMER - MISSIONS - OA / OE / External Missions

• short and long term planning of ESTRACK service availability• synthetic view of ESTRACK operations for committed services• permanent awareness of ESTRACK health

ESTRACK OPERATION - ONF

• optimal provision of ground station services to missions• conflict-free sharing of ground stations between multiple missions• automation of ground station operations

ESTRACK ENGINEERING - ONN

• safe ground station configuration with automated schedules and standardised JOBs

GROUND SEGMENT INFRASTRUCTURE - GI

• efficient software production, maintenance and evolution• reuse of proven components from mission operation domain


EPS - ESTRACK Planning System

ESS - ESTRACK Scheduling System

ECS - ESTRACK Coordination SystemECS

CentralRepository

ESTRACKPerformance

Evaluation

EMS - environment and basic architecture

ESTRACK Scheduling Office

ESTRACK Control Centre

GSCRemote

Workstation

Mission Planning | Flight Dynamics | Mission Control

Ground Station Controller - GSC: STC2, CSMC, GSMC





ECS - ESTRACK Coordination System


EMS - information exchanges

EMP View

flight-dyn.

events

ESTRACK Schedule - 12 days

ESTRACK Schedule - 12 daysstatus

parameterslog messages

ground

station

status

all information produced

and consumed

by ECS

ECSCentral

Repository

ECS - schedule distribution | ground station monitoring

ESTRACK Management Plan EMP

mission

events

mis

sio

n a

gre

em

en

t

EMPchang

e

SLE provisio

nstatus





ECSCentral

Repository


EMS - ESTRACK Planning System - overview




EPS - objectives1 of 1

The ESTRACK Planning System EPS

• maps Standing Service Orders from mission-agreements to the capabilities of ESTRACK ground stations- applies mission specific planning rules and respects temporal and factual constraints

• produces a conflict-free service allocation plan, the ESTRACK Management Plan EMP- exploits flexibility in standing orders and applies mission priorities and preferences

• allows missions to edit the ESTRACK Management Plan- within the bounds of their Basic Service Order Periods

• supports efficient medium-term planning (6 - 12 month in 6 - 36 hours))- by planning multiple overlapping segments of the working plan

• allows load analysis of ground stations- in terms of OSSs, conflicts, station idle time - even for hypothetical ground stations


pla

nn

ing

EPS - outline of EMP planning process

flight dynamics and mission events

mission specific- planning rules- non-temporal constraints

pre

pla

nn

ing

BSOPsService Opportunity Windows

user service definition with- operational service requests- operational service groups

FACTs generation

BSOPs derivation

SOWs generation

mission agreementstanding order definition with

- event processing rules- service periodicity- temporal constraints

ground station model

Operational Service Instances Templates with- resource requirements

Event Processing Templates

ground station resources

planning period specification

BSOP = Basic Standing Order PeriodSOW = ServIce Opportunity Window

EPS operator


mission specific- planning rules- non-temporal constraints

user service definition with- operational service requests- operational service groups

mission agreementstanding order definition with

- event processing rules- service periodicity- temporal constraints

pla

nn

ing

EPS - outline of EMP planning process1 of 1

conflict detection

ESTRACK Management Plan

BSOPsService Opportinity Windows

EMP-segment with:• candidate OSSs• committed OSSsof other missions

order refinement request

SSOW selection

COSS generation

XML encoding

EMPview

partial plan

conflict resolution

partial plan production

COSS selection

COSS = Candidate Operational Service session

SSOW generation

SSOW = Super Service Opportunity Window

BSOP = Basic Standing Order PeriodSOW = ServIce Opportunity Window

mission priorities and preferences


EPS input - Mission Agreement and User Service

realUML


EPS input - Ground Station Model

realUML


EPS - a closer look to planning 1 Mission Agreement and Basic Standing Order Period

Basic Standing Order Period Basic Standing Order Period Basic Standing Order Period Basic Standing Order Period

• one pass per week

• the separation from previous to next pass shall not be more than 9 days and no less than 4 days

• with duration of 3 h

• during working days


EPS - a closer look to planning 2 preplanning in a Basic Standing Order Period 1 of 2

G/S B

G/S A

G/S C

BSOP - Basic Standing Order Period

spacecraft operator on shift

spacecraft antenna occultation

SSOW - Super Service Opportunity Window

visibility period at ground station

SOW - Service Opportunity window

specialconstraint

s

step 1: generation of FACTs: visibility-window from flight dynamics events

step 2: generation of FACTs: temporal constraints from user defined events

step 3: generation of service opportunity windows SOWs at individual ground stations

step 4: generation of the Super Service Opportunity Window SSOW


G/S B

G/S A

G/S C

EPS - a closer look to planning 3

consistency checking in a Super Service Opportunity Window 1 of 2



COSS - Candidate OperationalService Session

these SOWs at ground station A are too short for the desired OSS

step 5: generation of Candidate OSSs - assuming that the ground station is dedicated to blue

step 6: check SOW duration

step 7: check with OSSs from green mission

step 8: adjust the OSSs within the bounds of their SSOW - if not possible, mark as conflict

the green mission has its OSS already committedso, the blue mission must move


EPS - a closer look to planning 4

conflict resolution in a Super Service Opportunity Window 1 of 2

G/S B

G/S A

G/S C



COSS - Candidate OperationalService Session

step 11: resolve conflicts

step 12: consider mission priority and preference for ground station

the red mission has some constraints on ground station Cso, the blue mission must move

the blue mission has a preference for ground station C

step 9: check with OSSs from red mission

step 10: adjust the OSSs within the bounds of their SSOW - if not possible, mark as conflict

on ground station B, the red mission has a lower priority than the blue mission - this is a conflict - and red must move to another ground station


EPS - inside an ESTRACK Management Plan1 of 2

Operational Service Session

OSI for Telecommanding

- reference to ground station allocated for this OSS- reference to requesting mission- reference to related BSOP

---

----

----

----

----

----

----

----

----

----

----

- b

eg

in

of

serv

ice

Operational Service Instance for telemetry reception

scheduled Events

OSI for radiometric measurements

a segment of the ESTRACK MANAGEMENT PLAN

---

----

----

----

----

----

----

----

----

----

----

----

en

d

of

serv

ice

---

----

----

----

----

----

----

----

----

----

----

---

beg

in

of

track--

---

----

----

----

----

----

----

----

----

----

----

----

-- e

nd

of

track--


EMS - ESTRACK Scheduling System - overview



ECSCentral

Repository


ESS - ESTRACK Scheduling SystemESS - ESTRACK Scheduling System



ESS - functions

The ESTRACK Scheduling System ESS

• translates the Operational Service Sessions from a conflict-free segment of the EMP into requests for ground station services and configurations- by means of many predefined templates and rules

• generates 'passes', i.e. sequences of time tagged calls of ready-made Jobs to be executed at ground stations- a repertoire of some 25 standard Mission Scheduling Jobs is available

• compiles these 'passes' into a single 12-days schedule valid for all missions and all ground stations- ground stations must filter their activities

1 of 1


ESS - schedule production - outline

ESTRACK Management Plan12- day segment

ground station configuration

• planning rules • planning constraints

user service specification

with:

standing order definition

operational service

requests

operational service groups

mission agreement

sch

ed

ule

pro

du

cti

on

schedule template

ESTRACK Schedule

OSSprocessing

OSIprocessing

PASSgeneration

XML document generation

Tue Wed TueFri Sat Tue Fri SatWed SunThu Thu MonSun MonSun MonSat Fri

operational service instance

template

SCHEDULEcompilation

event processing templateevent

processing

standard JOBs


ESS product - ESTRACK Ground Station Schedule1 of 1

<ESTRACK schedule><version number> <name> <comments> <schedule generation time><schedule start time><schedule stop time><schedule processing mode (i.e. overwrite, append or manual) >

<pass><begin of support><end of support><begin of track><end of track><reference to an Operational Service Session from EMP><spacecraft><ground station><terminal ><time tagged call of a standard job> <time tagged call of a standard job> <time tagged call of a standard job “Operator Instruction">....more <time tagged call of a standard job>< time tagged “Operator Instruction"> </pass>… more <pass>

</ESTRACK schedule>

pseudoXML

<ems:Job number="3" execSpec="sequential" criticalEntry="critical" procName="ENVDFTOF"> <ems:description>This job stops the dataflow test telemetry for the ENVISAT spacecraft</ems:description> <ems:startSpec delay="ignoreDelay" time="2009-02-23T22:30:16Z" /> </ems:Job>

realXML


ESS input - repertoire of standard mission scheduling JOBs

with DFT_STOP schedule-monitoring will be demonstrated

fromStandard Mission Scheduling Jobs


EMS - ESTRACK Coordination System - overview



ECSCentral

Repository






The ESTRACK Coordination System ECS

• distributes the ESTRACK schedule to all ground stations

• monitors the execution of the schedule at the ground stations

• correlates OSS specifications from EMP with schedule execution

• monitors the general health of the ground stations

• reports ground station configuration and operational status to customer missions

• supports urgent limited editing of the EMP and adjusts the schedule accordingly

• provides a synthetic view of current ground stations health and of ongoing schedule executions

• logs all data consumed or produced in a Central Repository for a future ESTRACK Data Warehouse

ECS - objectives1 of 1


1 of 1

ESTRACK Management Plan

ECSCentral

Repository

ESTRACK Schedule

Mission ControlEPSESS

ESTRACK Schedule


sch

ed

ule

dis

trib

uti

on

ground stationhealth monitoring

on

lin

e p

ara

mete

r in

jecti

on

ground station parameter acquisition

online log-message acquisition

schedule execution monit.

ECS - functions

JOBs execution monitoring

correlation of OSSs in ESTRACK Management Plan

withprogress of schedule execution

EMP editing

andscheduleadaptati

on

ESTRACK COORDINATION SYSTEM

para

mete

r con

dit

ion

ing

for

MO

Cs

ESTRACKperformanceevaluation

Data Warehousesupport


ECS - monitoring of schedule execution with messages from a JOB - 1 of 1

-- Procedure compiled on 2008/08/21 10:01:37 in database NNO/dvl V5.7.2-- ==================================---- 2006/06/20 09:08 jrb/LS Copied from CEB DB-- 2007/08/17 08:26 sm The job stops the DFT either on PSS MK2 or MK3-- -----------------------------------------------------------------PROCEDURE JS/DFT_STOPTITLE "Stop Data Flow Test";HELPThis Job removes the Dataflow test configuration.It just call the standard job TTLL_STP without any argumentENDHELP;PRIVILEGE CTRL;WINDOW MANDATORY;DEFINE&RetCode : @PSTATUS := %OK;&msg : STRING;&Failed : BOOLEAN;

BEGIN -- Procedure Body --

-- CommandSET &RetCode := CALL JS/TTLL_STP ();

IF &RetCode <> %OK THEN &Failed := TRUE; ENDIF;

IF &RetCode <> %OK OR /STC/PRC/JT.VALUE = %ONTHEN LOG &EXITMSG; ENDIF

IF &Failed = TRUE THENEXIT (%ERROR, MSG "DFT_STOP Setup failed");ELSEEXIT (%OK, MSG "DFT_STOP Setup successfully completed");ENDIF;

END

the message is time-stamped when entered into the STC journal and then forwarded from there to ECS - via CORBA and SMF

a real standard JOBas tailored and

executed at a ground station

time="2009-02-23T22:30:16Z


ECS - monitoring the health of a ground station with a Monitored Variable List 1 of 1

a pseudo MVL

variable id

STC/003

STC/009

STC/011

MCI/MCM1

MCI/FEC1

MCI/IFMS1

MCI/IFMS2

MCI/IFMS3

MCI/TMTC1

MCI/TMTC2

MCI/TMTC3

MCI/PSS1

MCI/PSS2

value

RWS 2

SCE 260

prime

ok

ok

ok

ok

ok

ok

ok

ok

ok

ok

Master Control Position

Server id

Server Role

MCM1 Summary Alarm

FEC1 Summary Alarm

IFMS1 Summary Alarm

IFMS2 Summary Alarm

IFMS3 Summary Alarm

TMTC1 Summary Alarm

TMTC2 Summary Alarm

TMTC3 Summary Alarm

PSS1 Summary Alarm

PSS2 Summary Alarm

inte

rface s

tatu

s

gro

un

d s

tati

on

eq

uip

men

t

sta

tus

STC

qualifier

valid

valid

valid

valid

valid

valid

valid

valid

valid

valid

valid

valid

valid

for ground station health monitoring, a standard MVL will be tailored for all STC-stations


ECS - monitoring the health of a ground station with a Monitored Variable List 1 of 1

variable id

STC/003

STC/009

STC/011

MCI/MCM1

MCI/FEC1

MCI/IFMS1

MCI/IFMS2

MCI/IFMS3

MCI/TMTC1

MCI/TMTC2

MCI/TMTC3

MCI/PSS1

MCI/PSS2

value

RWS 2

SCE 260

prime

ok

ok

ok

ok

failure

ok

ok

ok

ok

Master Control Position

Server id

Server Role

MCM1 Summary Alarm

FEC1 Summary Alarm

IFMS1 Summary Alarm

IFMS2 Summary Alarm

IFMS3 Summary Alarm

TMTC1 Summary Alarm

TMTC2 Summary Alarm

TMTC3 Summary Alarm

PSS1 Summary Alarm

PSS2 Summary Alarm

inte

rface s

tatu

s

gro

un

d s

tati

on

eq

uip

men

t

sta

tus

STC

qualifier

valid

valid

valid

valid

valid

valid

valid

valid

valid

valid

valid

unavail

valid

MCI/IFMS3

failure valid

MCI/PSS1 unavail

a delta-MVL is generated and sent to ECS - via CORBA and SMF


EMS - implementation technologies and EGOS components





ECSCentral

Repository

FIDESfile

transferCORBA IDL

online parameters

online journals

FARC*

DARC*

RationalRose

UML software design

stub-code production

EKLOPSplanning

algorithms

MATIS*MMI

PLUTO processing

SCOSauthenticatio

nlogging

C++

JAVA

LINUXSLES8, 9,

11

Enterprise Architect

UMLsoftware design

Station Tailoringfor JOBs and MVLs

GFTSfile

transferSMF*

- data injection to Mission

Control

- ground station data acquisition

POST++planning products database

ECLIPSE SWT

EPS / ESS MMI

XMLencoding



EPS / ESS - further reading1 of 2

EPS / ESS operator training course

EPS / ESS developer training course

EMS / ECS SOFTWARE REQUIREMENTS SPECIFICATION


EMS - history and current development status1 of 1

EPS / ESS development

nov. 2005 WO 'Design and Development of EPS' awarded to VEGAsep. 2007

apr. 2006 WO 'Design and Development of ESS' jan. 2008

nov. 2007 CCN 'EPS / ESS Improvements' jun. 2008

aug. 2008 CCN 'Constellation Handling' nov. 2008

nov. 2008 CCN 'Long Term Planning and Load Analysis' jul. 2009ECS development

jun. 2008 WO 'Design and Development of ECS' awarded to TERMA / VTS

nov. 2008 review of ECS requirements

jan. 2009 CCN 'Implementation of Revised Requirements'

jun. 2009 CCN 'Development with EGOS components'

jul. 2009 Preliminary Design Review

may 2010 Critical Design Review

nov. 2010 Acceptance Review and start of warranty

may. 2011 Final Acceptance and end of warranty

production dates are tentative

oct. 2003 Study 'ESTRACK Management and Scheduling' by ANITE nov. 2004


EMS - strategic evolution - challenges

• more spacecraft - hopefully

• more ground stations - at least DS3 is coming

• more coordinated operations for constellation missions

• more good ideas will emerge during operational use• need for optimisation, exchangeable planning strategies

• adaptation to STC successor - the GSMC is in preparation

• adaptation to a future common Mission Planning System

• support of CCSDS Service Management - Blue Book is imminent

• support of dynamic SLE Service Instance Files (SICF) • more non-ESA mission customers• more coordination with non-ESA service providers • more competition with non-ESA service providers

1 of 1


EMS - acknowlegements

Volker Dreihahn

Gian Paolo Calzolari

Elias Taylor

Richard van Holtz

Alexander Hoffmann

Martin Unal

Ian Shaw

Martin Goetzelmann

Marc Niezette

Daniele di Nisio

Michel Dugast

Joerg Noll

Martin Karch

Francesco Croce

Michela Alberti

Thomas Beck Ian HarissonGary Whitehead

Elsa Montagnon

Marta Rodrigez Perulero

Michele Fischer

Alejandro Pena

Nestor Peccia

Sylvain Daminai

Alessandro Loretucci

Angelika Slade

Simone Dionisi

Felix Flentge Heribert Weickenmeier

Catherine Lannes

Zahoor Khan

Francesca Bellu

Kenneth Scott

Margherita di Giulio

Ramesh Chellathurai

Sylvie Haag

Mauro Pecchioli

Kate Adamson

Technology

OPS Forum ESTRACK Management System 19.06.2009