OPS Forum ESTRACK Management System 19.06.2009

  • 429 views
Uploaded on

The EMS translates service requests from multiple missions into a schedule for ground stations and monitors both execution of the schedule and general health of ground stations.

The EMS translates service requests from multiple missions into a schedule for ground stations and monitors both execution of the schedule and general health of ground stations.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
429
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
9
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. ESTRACK MANAGEMENT SYSTEM EMS scope and benefits OPS-GIB Margherita di Giulio
  • 2. 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
  • 3. 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
  • 4. 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
  • 5. 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.
  • 6. 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
  • 7. A Brief Introduction to the ESTRACK MANAGEMENT SYSTEM EMS objectives -- architecture -- functions OPS-GIB Gerhard Theis
  • 8. 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
  • 9. EMS - stakeholders and their objectives 1 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
  • 10. EMS - environment and basic architecture EPS - ESTRACK Planning System ESS - ESTRACK Scheduling System ECS - ESTRACK Coordination System ECS Central Repository ESTRACK Performance Evaluation ESTRACK Scheduling Office ESTRACK Control Centre GSC Remote Workstation Mission Planning | Flight Dynamics | Mission Control Ground Station Controller - GSC: STC2, CSMC, GSMC
  • 11. EMS - information exchanges Mission Planning | Flight Dynamics | Mission Control EPS - ESTRACK Planning System ESS - ESTRACK Scheduling System ECS - ESTRACK Coordination System Ground Station Controller - GSC: STC2, CSMC, GSMC EMP View flight-dyn. events ESTRACK Schedule - 12 days ESTRACK Schedule - 12 days status parameters log messages ground station status all information produced and consumed by ECS ECS Central Repository ECS - schedule distribution | ground station monitoring ESTRACK Management Plan EMP mission events mission agreement EMP change SLE provision status
  • 12. EMS - ESTRACK Planning System - overview ESS - ESTRACK Scheduling System ECS - ESTRACK Coordination System Ground Station Controller - GSC: STC2, CSMC, GSMC ECS Central Repository EPS - ESTRACK Planning System EPS - ESTRACK Planning System Mission Planning | Flight Dynamics | Mission Control
  • 13. EPS - objectives
    • 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
    1 of 1
  • 14. EPS - outline of EMP planning process planning flight dynamics and mission events mission specific - planning rules - non-temporal constraints preplanning BSOPs Service Opportunity Windows user service definition with - operational service requests - operational service groups FACTs generation BSOPs derivation SOWs generation mission agreement standing 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 Period SOW = ServIce Opportunity Window EPS operator
  • 15. EPS - outline of EMP planning process planning 1 of 1 conflict detection ESTRACK Management Plan BSOPs Service Opportinity Windows
    • EMP-segment with:
    • candidate OSSs
    • committed OSSs of other missions
    order refinement request SSOW selection COSS generation XML encoding EMP view 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 Period SOW = ServIce Opportunity Window mission priorities and preferences mission specific - planning rules - non-temporal constraints user service definition with - operational service requests - operational service groups mission agreement standing order definition with - event processing rules - service periodicity - temporal constraints
  • 16. EPS input - Mission Agreement and User Service real UML
  • 17. EPS input - Ground Station Model real UML
  • 18. EPS - a closer look to planning 1 Mission Agreement and 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
    Basic Standing Order Period Basic Standing Order Period Basic Standing Order Period Basic Standing Order Period
  • 19. EPS - a closer look to planning 2 preplanning in a Basic Standing Order Period 1 of 2 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 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 special constraints
  • 20. EPS - a closer look to planning 3 consistency checking in a Super Service Opportunity Window 1 of 2 SOW - Service Opportunity window SSOW - Super Service Opportunity Window COSS - Candidate Operational Service Session 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 committed so, the blue mission must move G/S B G/S A G/S C these SOWs at ground station A are too short for the desired OSS
  • 21. EPS - a closer look to planning 4 conflict resolution in a Super Service Opportunity Window 1 of 2 SOW - Service Opportunity window SSOW - Super Service Opportunity Window COSS - Candidate Operational Service Session step 11: resolve conflicts step 12: consider mission priority and preference for ground station the red mission has some constraints on ground station C so, 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 G/S B G/S A G/S C
  • 22. EPS - inside an ESTRACK Management Plan 1 of 2 Operational Service Session OSI for Telecommanding - reference to ground station allocated for this OSS - reference to requesting mission - reference to related BSOP -------------------------------------------- begin of service Operational Service Instance for telemetry reception OSI for radiometric measurements a segment of the ESTRACK MANAGEMENT PLAN ----------------------------------------------- end of service ---------------------------------------------- begin of track-- ------------------------------------------------- end of track-- scheduled Events
  • 23. EMS - ESTRACK Scheduling System - overview ECS - ESTRACK Coordination System Ground Station Controller - GSC: STC2, CSMC, GSMC ECS Central Repository EPS - ESTRACK Planning System ESS - ESTRACK Scheduling System ESS - ESTRACK Scheduling System Mission Planning | Flight Dynamics | Mission Control
  • 24. 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
  • 25. ESS - schedule production - outline ESTRACK Management Plan 12- day segment ground station configuration schedule production schedule template ESTRACK Schedule OSS processing OSI processing PASS generation XML document generation Tue Wed Tue Fri Sat Tue Fri Sat Wed Sun Thu Thu Mon Sun Mon Sun Mon Sat Fri operational service instance template SCHEDULE compilation event processing template event processing standard JOBs
    • planning rules
    • planning constraints
    • user service specification with:
    • standing order definition
    • operational service requests
    • operational service groups
    mission agreement
  • 26. ESS product - ESTRACK Ground Station Schedule 1 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&quot; > ....more <time tagged call of a standard job> < time tagged “Operator Instruction&quot; > </pass> … more <pass> </ESTRACK schedule> pseudo XML <ems:Job number=&quot;3&quot; execSpec=&quot;sequential&quot; criticalEntry=&quot;critical&quot; procName=&quot;ENVDFTOF&quot;> <ems:description>This job stops the dataflow test telemetry for the ENVISAT spacecraft</ems:description> <ems:startSpec delay=&quot;ignoreDelay&quot; time=&quot;2009-02-23T22:30:16Z&quot; /> </ems:Job> real XML
  • 27. ESS input - repertoire of standard mission scheduling JOBs with DFT_STOP schedule-monitoring will be demonstrated from Standard Mission Scheduling Jobs
  • 28. EMS - ESTRACK Coordination System - overview ECS - ESTRACK Coordination System Ground Station Controller - GSC: STC2, CSMC, GSMC ECS Central Repository EPS - ESTRACK Planning System ESS - ESTRACK Scheduling System ECS - ESTRACK Coordination System Mission Planning | Flight Dynamics | Mission Control
  • 29.
    • 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 - objectives 1 of 1
  • 30. 1 of 1 ESTRACK Management Plan ECS Central Repository ESTRACK Schedule Mission Control EPS ESS ESTRACK Schedule Ground Station Controller - GSC: STC2, CSMC, GSMC schedule distribution ground station health monitoring online parameter injection ground station parameter acquisition online log-message acquisition schedule execution monit. ECS - functions JOBs execution monitoring correlation of OSSs in ESTRACK Management Plan with progress of schedule execution EMP editing and schedule adaptation ESTRACK COORDINATION SYSTEM parameter conditioning for MOCs ESTRACK performance evaluation Data Warehouse support
  • 31. 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_STOP TITLE &quot;Stop Data Flow Test&quot;; HELP This Job removes the Dataflow test configuration. It just call the standard job TTLL_STP without any argument ENDHELP; PRIVILEGE CTRL; WINDOW MANDATORY; DEFINE &RetCode : @PSTATUS := %OK; &msg : STRING; &Failed : BOOLEAN; BEGIN -- Procedure Body -- -- Command SET &RetCode := CALL JS/TTLL_STP (); IF &RetCode <> %OK THEN &Failed := TRUE; ENDIF; IF &RetCode <> %OK OR /STC/PRC/JT.VALUE = %ON THEN LOG &EXITMSG; ENDIF IF &Failed = TRUE THEN EXIT (%ERROR, MSG &quot;DFT_STOP Setup failed&quot;); ELSE EXIT (%OK, MSG &quot;DFT_STOP Setup successfully completed&quot;); 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 JOB as tailored and executed at a ground station time=&quot;2009-02-23T22:30:16Z
  • 32. ECS - monitoring the health of a ground station with a Monitored Variable List 1 of 1 a pseudo MVL interface status ground station equipment status STC for ground station health monitoring, a standard MVL will be tailored for all STC-stations 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 qualifier valid valid valid valid valid valid valid valid valid valid valid valid valid
  • 33. ECS - monitoring the health of a ground station with a Monitored Variable List 1 of 1 interface status ground station equipment status STC a delta-MVL is generated and sent to ECS - via CORBA and SMF 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 qualifier valid valid valid valid valid valid valid valid valid valid valid unavail valid valid failure MCI/IFMS3 unavail  MCI/PSS1
  • 34. EMS - implementation technologies and EGOS components EPS - ESTRACK Planning System ESS - ESTRACK Scheduling System ECS - ESTRACK Coordination System Ground Station Controller - GSC: STC2, CSMC, GSMC ECS Central Repository FIDES file transfer CORBA IDL online parameters online journals FARC* DARC* RationalRose UML software design stub-code production EKLOPS planning algorithms MATIS* MMI PLUTO processing SCOS authentication logging C++ JAVA LINUX SLES8, 9, 11 Enterprise Architect UML software design Station Tailoring for JOBs and MVLs GFTS file transfer SMF* - data injection to Mission Control - ground station data acquisition POST++ planning products database ECLIPSE SWT EPS / ESS MMI XML encoding Mission Planning | Flight Dynamics | Mission Control
  • 35. EPS / ESS - further reading 1 of 2 EPS / ESS operator training course EPS / ESS developer training course EMS / ECS SOFTWARE REQUIREMENTS SPECIFICATION
  • 36. EMS - history and current development status 1 of 1 EPS / ESS development nov. 2005 WO 'Design and Development of EPS' awarded to VEGA sep. 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. 2009 ECS 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
  • 37. 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
  • 38. 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 Harisson Gary 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