scope and benefits ops gib margherita di giulio n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
ESTRACK MANAGEMENT SYSTEM EMS PowerPoint Presentation
Download Presentation
ESTRACK MANAGEMENT SYSTEM EMS

Loading in 2 Seconds...

play fullscreen
1 / 38

ESTRACK MANAGEMENT SYSTEM EMS - PowerPoint PPT Presentation


  • 208 Views
  • Uploaded on

scope and benefits OPS-GIB Margherita di Giulio. ESTRACK MANAGEMENT SYSTEM EMS. 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

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

ESTRACK MANAGEMENT SYSTEM EMS


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
    Presentation Transcript
    1. scope and benefitsOPS-GIB Margherita di Giulio ESTRACK MANAGEMENT SYSTEMEMS

    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) • 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. EPS ESS Users refinements G/S Schedules Master Plan

    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. ESTRACK Real-Time Overview ECS G/S Schedule MVL Master Plan

    7. objectives -- architecture -- functions OPS-GIB Gerhard Theis A Brief Introduction to theESTRACK MANAGEMENT SYSTEMEMS

    8. EMS - overview MISSION OPERATIONS ESTRACK MANAGEMENT SYSTEM mediating between service requirements of space missions and capabilities of the ESTRACK ground station network ESTRACK GROUND STATIONS 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 Mission Planning | Flight Dynamics | Mission Control ESTRACK Scheduling Office EPS - ESTRACK Planning System ESTRACKPerformance Evaluation ESS - ESTRACK Scheduling System ESTRACK Control Centre ECSCentralRepository ECS - ESTRACK Coordination System GSCRemoteWorkstation Ground Station Controller - GSC: STC2, CSMC, GSMC

    11. EMS - information exchanges Mission Planning | Flight Dynamics | Mission Control EMP View ground station status EMPchange SLE provisionstatus missionevents flight-dyn. events EPS - ESTRACK Planning System mission agreement ESTRACK Management Plan EMP ESS - ESTRACK Scheduling System ESTRACK Schedule - 12 days ECSCentralRepository all information produced and consumed by ECS ECS - schedule distribution | ground station monitoring ECS - ESTRACK Coordination System status parameterslog messages ESTRACK Schedule - 12 days Ground Station Controller - GSC: STC2, CSMC, GSMC

    12. EMS - ESTRACK Planning System - overview Mission Planning | Flight Dynamics | Mission Control EPS - ESTRACK Planning System EPS - ESTRACK Planning System ESS - ESTRACK Scheduling System ECSCentralRepository ECS - ESTRACK Coordination System Ground Station Controller - GSC: STC2, CSMC, GSMC

    13. EPS - objectives 1 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

    14. EPS - outline of EMP planning process EPS operator preplanning planning period specification ground station model flight dynamics and mission events FACTs generation ground station resources mission agreement BSOPs derivation Operational Service Instances Templates with- resource requirements standing order definition with - event processing rules - service periodicity - temporal constraints SOWs generation BSOPs Service Opportunity Windows Event Processing Templates mission specific - planning rules- non-temporal constraints planning user service definition with- operational service requests - operational service groups BSOP = Basic Standing Order Period SOW = ServIce Opportunity Window

    15. mission agreement standing order definition with - event processing rules - service periodicity - temporal constraints mission specific - planning rules- non-temporal constraints user service definition with- operational service requests - operational service groups EPS - outline of EMP planning process 1 of 1 BSOPsService Opportinity Windows SSOW generation SSOW selection COSS generation planning COSS selection partial plan production • EMP-segment with: • candidate OSSs • committed OSSsof other missions partial plan conflict detection mission priorities and preferences conflict resolution order refinement request BSOP = Basic Standing Order Period XML encoding SOW = ServIce Opportunity Window SSOW = Super Service Opportunity Window EMPview ESTRACK Management Plan COSS = Candidate Operational Service session

    16. EPS input - Mission Agreement and User Service realUML

    17. EPS input - Ground Station Model realUML

    18. Basic Standing Order Period Basic Standing Order Period Basic Standing Order Period Basic Standing Order Period EPS - a closer look to planning1 Mission Agreement and Basic Standing Order Period • one pass per week • during working days • with duration of 3 h • the separation from previous to next pass shall not be more than 9 days and no less than 4 days

    19. G/S A G/S B G/S C specialconstraints EPS - a closer look to planning 2 preplanning in a Basic Standing Order Period 1 of 2 BSOP - Basic Standing Order Period SSOW - Super Service Opportunity Window spacecraft operator on shift spacecraft antenna occultation 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 visibility period at ground station step 4: generation of the Super Service Opportunity Window SSOW SOW - Service Opportunity window

    20. these SOWs at ground station A are too short for the desired OSS G/S A G/S B G/S C EPS - a closer look to planning 3consistency checking in a Super Service Opportunity Window 1 of 2 the green mission has its OSS already committedso, the blue mission must move SSOW - Super Service Opportunity Window 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 COSS - Candidate OperationalService Session SOW - Service Opportunity window

    21. G/S A G/S B G/S C EPS - a closer look to planning 4 conflict resolution in a Super Service Opportunity Window 1 of 2 the red mission has some constraints on ground station C so, the blue mission must move 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 SSOW - Super Service Opportunity Window 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 step 11: resolve conflicts step 12: consider mission priority and preference for ground station COSS - Candidate OperationalService Session SOW - Service Opportunity window

    22. scheduled Events EPS - inside an ESTRACK Management Plan 1 of 2 - reference to ground station allocated for this OSS- reference to requesting mission- reference to related BSOP Operational Service Session Operational Service Instance for telemetry reception ------------------------------------------------- end of track-- ---------------------------------------------- begin of track-- ----------------------------------------------- end of service -------------------------------------------- begin of service OSI for Telecommanding OSI for radiometric measurements a segment of the ESTRACK MANAGEMENT PLAN

    23. EMS - ESTRACK Scheduling System - overview Mission Planning | Flight Dynamics | Mission Control EPS - ESTRACK Planning System ESS - ESTRACK Scheduling System ESS - ESTRACK Scheduling System ECSCentralRepository ECS - ESTRACK Coordination System Ground Station Controller - GSC: STC2, CSMC, GSMC

    24. ESS - functions 1 of 1 • 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

    25. mission agreement • planning rules • planning constraints • user service specification with: • standing order definition • operational service requests • operational service groups ESS - schedule production - outline Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Fri ESTRACK Management Plan12- day segment ground station configuration OSSprocessing operational service instance template schedule production OSIprocessing event processing template event processing PASSgeneration schedule template SCHEDULEcompilation standard JOBs XML document generation ESTRACK Schedule

    26. ESS product - ESTRACK Ground Station Schedule 1 of 1 pseudo XML <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> real XML <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>

    27. fromStandard Mission Scheduling Jobs ESS input - repertoire of standard mission scheduling JOBs with DFT_STOP schedule-monitoring will be demonstrated

    28. EMS - ESTRACK Coordination System - overview Mission Planning | Flight Dynamics | Mission Control EPS - ESTRACK Planning System ESS - ESTRACK Scheduling System ECSCentralRepository ECS - ESTRACK Coordination System ECS - ESTRACK Coordination System Ground Station Controller - GSC: STC2, CSMC, GSMC

    29. ECS - objectives 1 of 1 • 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

    30. ECS - functions 1 of 1 ESTRACKperformanceevaluation ESS EPS Mission Control ESTRACK Schedule ESTRACK Management Plan correlation of OSSs in ESTRACK Management Plan with progress of schedule execution EMP editing and scheduleadaptation Data Warehousesupport ECSCentralRepository schedule distribution parameter conditioning for MOCs online parameter injection ESTRACK COORDINATION SYSTEM schedule execution monit. ground stationhealth monitoring JOBs execution monitoring online log-message acquisition ground station parameter acquisition ESTRACK Schedule Ground Station Controller - GSC: STC2, CSMC, GSMC

    31. ECS - monitoring of schedule execution with messages from a JOB - a real standard JOB as tailored and executed at a ground station 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 "Stop Data Flow Test"; 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 "DFT_STOP Setup failed"); ELSE EXIT (%OK, MSG "DFT_STOP Setup successfully completed"); ENDIF; END time="2009-02-23T22:30:16Z the message is time-stamped when entered into the STC journal and then forwarded from there to ECS - via CORBA and SMF

    32. ECS - monitoring the health of a ground station with a Monitored Variable List 1 of 1 a pseudo MVL status STC interface status ground station equipment for ground station health monitoring, a standard MVL will be tailored for all STC-stations

    33. ECS - monitoring the health of a ground station with a Monitored Variable List 1 of 1 status STC interface status ground station equipment a delta-MVL is generated and sent to ECS - via CORBA and SMF

    34. EMS - implementation technologies and EGOS components Mission Planning | Flight Dynamics | Mission Control EKLOPSplanning algorithms ECLIPSE SWTEPS / ESS MMI C++ EPS - ESTRACK Planning System JAVA POST++planning products database RationalRose UML software designstub-code production GFTSfile transfer LINUXSLES8, 9, 11 ESS - ESTRACK Scheduling System SMF*- data injection to Mission Control - ground station data acquisition XMLencoding Enterprise ArchitectUMLsoftware design SCOSauthenticationlogging MATIS*MMIPLUTO processing ECSCentralRepository FARC* ECS - ESTRACK Coordination System DARC* FIDESfile transfer CORBA IDLonline parameters online journals Station Tailoring for JOBs and MVLs Ground Station Controller - GSC: STC2, CSMC, GSMC

    35. EPS / ESS - further reading 1 of 2 EPS / ESS operator training course EMS / ECS SOFTWARE REQUIREMENTS SPECIFICATION EPS / ESS developer training course

    36. EMS - history and current development status 1 of 1 oct. 2003 Study 'ESTRACK Management and Scheduling' by ANITE nov. 2004 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

    37. EMS - strategic evolution - challenges 1 of 1 • 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

    38. EMS - acknowlegements Francesca Bellu Gian Paolo Calzolari Marta Rodrigez Perulero Marc Niezette Joerg Noll Martin Unal Elias Taylor Kate Adamson Martin Karch Michele Fischer Felix Flentge Heribert Weickenmeier Alexander Hoffmann Kenneth Scott Richard van Holtz Francesco Croce Volker Dreihahn Martin Goetzelmann Alejandro Pena Michela Alberti Ian Shaw Nestor Peccia Daniele di Nisio Margherita di Giulio Ramesh Chellathurai Catherine Lannes Gary Whitehead Ian Harisson Thomas Beck Angelika Slade Sylvie Haag Zahoor Khan Mauro Pecchioli Sylvain Daminai Michel Dugast Simone Dionisi Alessandro Loretucci Elsa Montagnon