1 / 31

Ground-Segment Reference Environment

Ground-Segment Reference Environment. Y.Doat, P.Fauré, E.Doelling, R.Santos OPS-GSI, OPS-EC, OPS-GIM 06.02.09. Presentation Content. Today’s Environment; Objectives; Building Plans; Communication Infrastructure; Support Facilities; Future Evolution; Project organisation.

oshin
Download Presentation

Ground-Segment Reference Environment

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Ground-Segment Reference Environment Y.Doat, P.Fauré, E.Doelling, R.Santos OPS-GSI, OPS-EC, OPS-GIM 06.02.09

  2. Presentation Content • Today’s Environment; • Objectives; • Building Plans; • Communication Infrastructure; • Support Facilities; • Future Evolution; • Project organisation.

  3. Today’s Environment

  4. Current OPS-GS EnvironmentH.32 • OPS-GS Reference Station: • Ground-Station Test & Validation; • Operational Support; • RFTC. • OPS-GS Laboratories: • NDIU integration and validation; • SVT Support; • PC Support; • Integration and rack validation.

  5. Current OPS-GI EnvironmentD.126 • Software: • Integration and unit validation; • System validation; • Software technology laboratory (e.g. virtualisation); • Build and source repository access. • Investigation of problems.

  6. Objectives

  7. Objectives • Technical Infrastructure: • An innovative end-to-end approach for validation and operational support. • Network and Security: • A flexible and secure approach for testing and support. • Configuration Control & Planning: • An environment under control. • Quality: • Improve the quality without impacting the expertise. • Engineering Public Relation • Do what you say and Show what you do.

  8. End-to-End Objective • Validation from the following perspectives: • Functional: validation of provided services (TM, TC, Tracking, Station M&C, …); • Performance: mission requirements increase; • stability (long duration). • Required by • OPS-O, triggered by MEX, ROS low bit rate problems; • OPS-G, more systematic validation.

  9. Network Objective • Simulated operational network. • Performance testing; • Error cases: bit error rates, latency, … ; • Long duration testing; • Isolated from non-operational data traffic; • Independent from operational use constraints (e.g. freeze). • Required by: • OPS-G, end-2-end representative validation.

  10. Security Objective • Support from external industry: • Secure sessions (remote troubleshooting); • Established and controlled by the T.O. • Internet Access • Testing of ESA infrastructure against new developed equipment outside ESOC (e.g. timing system M&C validation); • Required by: • OPS-G to reduce costs and increase efficiency; • ESA security requirements.

  11. Configuration Control Objective • Ensure the configuration of the environment: • Support various versions of subsystem; • Support various configuration of subsystem and end-2-end; • Validate hardware integration configuration to be in line with Ground-Station System Integration Standard. • Required by: • OPS-G, validation of various versions; • OPS-O, end-2-end validation of configuration changes, backward compatibility, …

  12. Quality Objective • Develop processes associated with: • End-2-End validation; • Security; • Configuration control; • Scheduling of resources (booking capability, visibility to users); • Pre-deployment validation. • Required by: • OPS-G • OPS-O.

  13. Public Relation • Share OPS-G capability with: • ESA colleagues; • ESOC visitors. • Show what engineering is: • Engineering processes; • Ground-Segment: Ground-Station, Control Centre and Network; • Data flows; • … • Temporary vs Permanent Exhibitions • Short term: Poster display (e.g. the ones presented in conferences; • Long term: Explain what a Ground-Segment is? • Required by: OPS-G.

  14. Building Plans

  15. Microlab Equipment Pool Reference Station Current Layout PC Lab Workshop Electronic Lab Wiring Office

  16. Workshop (Reorganised in 2008) Reference OCC Wiring Meeting Reference Station (RF) Comms New layout (Ground) Reference Station (M&C, FEC,NDIU) Short Term Storage

  17. PC Lab New layout (Mezzanine) Office Electronic Lab Equipment Pool Storage

  18. External view of H Building

  19. 3D Representation of the Ground-Segment Reference Environment Area

  20. Communication Infrastructure

  21. Current OPS-GI Integration Environment

  22. Current OPS-GS Reference Station Environment

  23. Internet Corporate DMZ Relay LAN Validation Data Centre ESA sites OPSLAN Halley+Deneb Collaboration Server Corporate Distribution Pre-OPSLAN Distribution Internet Access to Internet Corporate WIFI Corporate Access MCS/NIS Ref. Ground-Station Ref. WAN Emulation Network Detailed Topology MCS/NIS Ref. Infrastructure Service Ground-Station Ref.

  24. Support Facilities

  25. Support Facilities • Workshop: • Hardware preparation and integration of racks & Consoles; • Wiring of racks and Ground-Segment Reference Environment. • PC Lab: • Configuration of deployed PCs; • Support of Linux, Windows, QNX. • Electronic Lab: • Embedded hardware support (design & production).

  26. Future Evolution

  27. Future Evolution • End-to-end including a ground-station: • Possibility to use Vil4 for limited capability (e.g. M&C, Telemetry and Tracking). • End-to-end including MCS: • Possibility to configure for dedicated MCS. • Evolution for SSA reference Environment.

  28. Project

  29. ESOC Project Team Y.Doat OPS-GSI P.Fauré OPS-ECS R.Santos OPS-GIM Team OPS-GSI W.Nzoubou OPS-ECS E.Doelling OPS-ECT

  30. Planning (After D/OPS approval) • 1st semester 2009: Cleaning of area; • 2nd semester 2009 & 1st semester 2010: • Start of building work; • Network architecture; • Reorganisation.

  31. Thank you for your attention

More Related