OPS Forum Ground Segment Reference Facility 06.02.2009


Published on

Testing and validation of the ground segment and ground segment components are prerequisites for operations success. To improve the current approach, OPS-G is working on an innovative concept that will allow developers to validate and demonstrate their system in a pre-operational environment.

The environment will ensure validation at subsystem level and end-to-end testing from radio-frequency systems to the Mission Control System. While the facility partly exists today, it is not yet formally organised.

In order to achieve the new functionality, a reorganisation of the Ground Station Reference Station in ESOC's H building into a Ground Segment Reference Environment will take place, including:

* Ground Station Environment
* Mission Control System Infrastructure Environment
* Network Environment
* Workshop for hardware integration and wiring

The presentation will introduce the concept and the steps required to achieve the new functionality.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

OPS Forum Ground Segment Reference Facility 06.02.2009

  1. 1. Ground-Segment Reference Environment Y.Doat, P.Fauré, E.Doelling, R.Santos OPS-GSI, OPS-EC, OPS-GIM 06.02.09
  2. 2. Presentation Content <ul><li>Today’s Environment; </li></ul><ul><li>Objectives; </li></ul><ul><li>Building Plans; </li></ul><ul><li>Communication Infrastructure; </li></ul><ul><li>Support Facilities; </li></ul><ul><li>Future Evolution; </li></ul><ul><li>Project organisation. </li></ul>
  3. 3. Today’s Environment
  4. 4. Current OPS-GS Environment H.32 <ul><li>OPS-GS Reference Station: </li></ul><ul><ul><li>Ground-Station Test & Validation; </li></ul></ul><ul><ul><li>Operational Support; </li></ul></ul><ul><ul><li>RFTC. </li></ul></ul><ul><li>OPS-GS Laboratories: </li></ul><ul><ul><li>NDIU integration and validation; </li></ul></ul><ul><ul><li>SVT Support; </li></ul></ul><ul><ul><li>PC Support; </li></ul></ul><ul><ul><li>Integration and rack validation. </li></ul></ul>
  5. 5. Current OPS-GI Environment D.126 <ul><li>Software: </li></ul><ul><ul><li>Integration and unit validation; </li></ul></ul><ul><ul><li>System validation; </li></ul></ul><ul><ul><li>Software technology laboratory (e.g. virtualisation); </li></ul></ul><ul><ul><li>Build and source repository access. </li></ul></ul><ul><li>Investigation of problems. </li></ul>
  6. 6. Objectives
  7. 7. Objectives <ul><li>Technical Infrastructure: </li></ul><ul><ul><li>An innovative end-to-end approach for validation and operational support. </li></ul></ul><ul><li>Network and Security: </li></ul><ul><ul><li>A flexible and secure approach for testing and support. </li></ul></ul><ul><li>Configuration Control & Planning: </li></ul><ul><ul><li>An environment under control. </li></ul></ul><ul><li>Quality: </li></ul><ul><ul><li>Improve the quality without impacting the expertise. </li></ul></ul><ul><li>Engineering Public Relation </li></ul><ul><ul><li>Do what you say and Show what you do. </li></ul></ul>
  8. 8. End-to-End Objective <ul><li>Validation from the following perspectives: </li></ul><ul><ul><li>Functional: validation of provided services (TM, TC, Tracking, Station M&C, …); </li></ul></ul><ul><ul><li>Performance: mission requirements increase; </li></ul></ul><ul><ul><li>stability (long duration). </li></ul></ul><ul><li>Required by </li></ul><ul><ul><li>OPS-O, triggered by MEX, ROS low bit rate problems; </li></ul></ul><ul><ul><li>OPS-G, more systematic validation. </li></ul></ul>
  9. 9. Network Objective <ul><li>Simulated operational network. </li></ul><ul><ul><li>Performance testing; </li></ul></ul><ul><ul><li>Error cases: bit error rates, latency, … ; </li></ul></ul><ul><ul><li>Long duration testing; </li></ul></ul><ul><ul><li>Isolated from non-operational data traffic; </li></ul></ul><ul><ul><li>Independent from operational use constraints (e.g. freeze). </li></ul></ul><ul><li>Required by: </li></ul><ul><ul><li>OPS-G, end-2-end representative validation. </li></ul></ul>
  10. 10. Security Objective <ul><li>Support from external industry: </li></ul><ul><ul><li>Secure sessions (remote troubleshooting); </li></ul></ul><ul><ul><li>Established and controlled by the T.O. </li></ul></ul><ul><li>Internet Access </li></ul><ul><ul><li>Testing of ESA infrastructure against new developed equipment outside ESOC (e.g. timing system M&C validation); </li></ul></ul><ul><li>Required by: </li></ul><ul><ul><li>OPS-G to reduce costs and increase efficiency; </li></ul></ul><ul><ul><li>ESA security requirements. </li></ul></ul>
  11. 11. Configuration Control Objective <ul><li>Ensure the configuration of the environment: </li></ul><ul><ul><li>Support various versions of subsystem; </li></ul></ul><ul><ul><li>Support various configuration of subsystem and end-2-end; </li></ul></ul><ul><ul><li>Validate hardware integration configuration to be in line with Ground-Station System Integration Standard. </li></ul></ul><ul><li>Required by: </li></ul><ul><ul><li>OPS-G, validation of various versions; </li></ul></ul><ul><ul><li>OPS-O, end-2-end validation of configuration changes, backward compatibility, … </li></ul></ul>
  12. 12. Quality Objective <ul><li>Develop processes associated with: </li></ul><ul><ul><li>End-2-End validation; </li></ul></ul><ul><ul><li>Security; </li></ul></ul><ul><ul><li>Configuration control; </li></ul></ul><ul><ul><li>Scheduling of resources (booking capability, visibility to users); </li></ul></ul><ul><ul><li>Pre-deployment validation. </li></ul></ul><ul><li>Required by: </li></ul><ul><ul><li>OPS-G </li></ul></ul><ul><ul><li>OPS-O. </li></ul></ul>
  13. 13. Public Relation <ul><li>Share OPS-G capability with: </li></ul><ul><ul><li>ESA colleagues; </li></ul></ul><ul><ul><li>ESOC visitors. </li></ul></ul><ul><li>Show what engineering is: </li></ul><ul><ul><li>Engineering processes; </li></ul></ul><ul><ul><li>Ground-Segment: Ground-Station, Control Centre and Network; </li></ul></ul><ul><ul><li>Data flows; </li></ul></ul><ul><ul><li>… </li></ul></ul><ul><li>Temporary vs Permanent Exhibitions </li></ul><ul><ul><li>Short term: Poster display (e.g. the ones presented in conferences; </li></ul></ul><ul><ul><li>Long term: Explain what a Ground-Segment is? </li></ul></ul><ul><li>Required by: OPS-G. </li></ul>
  14. 14. Building Plans
  15. 15. Current Layout PC Lab Electronic Lab Wiring Workshop Office Equipment Pool Microlab Reference Station
  16. 16. New layout (Ground) Short Term Storage Reference Station (M&C, F EC, NDIU) Comms Reference Station (RF) Reference OCC Meeting Workshop (Reorganised in 2008) Wiring
  17. 17. New layout (Mezzanine) Office Electronic Lab Equipment Pool Storage PC Lab
  18. 18. External view of H Building
  19. 19. 3D Representation of the Ground-Segment Reference Environment Area
  20. 20. Communication Infrastructure
  21. 21. Current OPS-GI Integration Environment
  22. 22. Current OPS-GS Reference Station Environment
  23. 23. Network Detailed Topology MCS/NIS Ref. Ground-Station Ref. Infrastructure Service Ground-Station Ref. WAN Emulation MCS/NIS Ref. Access to Internet Internet Collaboration Server Corporate DMZ Corporate Access Corporate WIFI Corporate Distribution ESA sites Internet Pre-OPSLAN Distribution Data Centre Relay LAN Validation OPSLAN Halley+Deneb
  24. 24. Support Facilities
  25. 25. Support Facilities <ul><li>Workshop: </li></ul><ul><ul><li>Hardware preparation and integration of racks & Consoles; </li></ul></ul><ul><ul><li>Wiring of racks and Ground-Segment Reference Environment. </li></ul></ul><ul><li>PC Lab: </li></ul><ul><ul><li>Configuration of deployed PCs; </li></ul></ul><ul><ul><li>Support of Linux, Windows, QNX. </li></ul></ul><ul><li>Electronic Lab: </li></ul><ul><ul><li>Embedded hardware support (design & production). </li></ul></ul>
  26. 26. Future Evolution
  27. 27. Future Evolution <ul><li>End-to-end including a ground-station: </li></ul><ul><ul><li>Possibility to use Vil4 for limited capability (e.g. M&C, Telemetry and Tracking). </li></ul></ul><ul><li>End-to-end including MCS: </li></ul><ul><ul><li>Possibility to configure for dedicated MCS. </li></ul></ul><ul><li>Evolution for SSA reference Environment. </li></ul>
  28. 28. Project
  29. 29. ESOC Project Team Y.Doat OPS-GSI P.Fauré OPS-ECS W.Nzoubou OPS-ECS E.Doelling OPS-ECT R.Santos OPS-GIM Team OPS-GSI
  30. 30. Planning <ul><li>(After D/OPS approval) </li></ul><ul><li>1 st semester 2009: Cleaning of area; </li></ul><ul><li>2 nd semester 2009 & 1 st semester 2010: </li></ul><ul><ul><li>Start of building work; </li></ul></ul><ul><ul><li>Network architecture; </li></ul></ul><ul><ul><li>Reorganisation. </li></ul></ul>
  31. 31. Thank you for your attention