1. SpaceOps Stockholm 2012- Th.mueller@dlr.de Page 1 SpaceOps 2012 Stockholm Col-CC Voice System Migration During On-Going Operations Thomas Mueller, DLR, GSOC/Col-CC, Germany

2. SpaceOps Stockholm 2012 - Th.mueller@dlr.de Page 2 Verbal communication is essential for Space Operations Col-CC Voice System: 2020 Users 140 voice terminals / keysets 404 voice loops 198 external voice channels An average of 5 voice formats per external interface Voice communication is essential especially: For manned space flight Payload operations For such highly distributed ground segments as for the ISS

3. SpaceOps Stockholm 2012 - Th.mueller@dlr.de Page 3 The Col-CC Voice System connects The International Partner Control Centers MCC-H, MCC-M, HOSC ATV-CC Dedicated system for ATV operations EAC Dedicated system for training Local Keyset 60 keyset at Col-CC Remote Keysets 80 keysets at 21 ESA facilities

4. SpaceOps Stockholm 2012 - Th.mueller@dlr.de Page 4 Why to change a running system??? Supplier announced to leave this market segment Last buy option for some equipment in 2008 To original system(s) for ESA GS were procured in 2001/2002 Some equipment reached end-of-life (e.g. keyset screens) Maintenance contract for Col-CC ran out end of 2009 a prolongation of this maintenance was very costly NASA announced a transition to digital interfaces within 3 years (Move) Development of digital interface to Move is difficult and costly Limited capacity at all interfaces, also keysets

5. SpaceOps Stockholm 2012 - Th.mueller@dlr.de Page 5 General Rules for a Migration Transition to the new system is performed with minimal disruption to on-going operations A clear focus on minimal impact to real-time operations A balance to be found between: impact on on-going and planned activities (real-time, test/preperation and simulation activities) a cost effective and in-time transition the implementation schedule and constraints (internal and external) test and validation activities Not easy to achieve!

6. SpaceOps Stockholm 2012 - Th.mueller@dlr.de Page 6 Day X Concept Complete built up of the new system in parallel and then switch-over to new system at day X.

7. SpaceOps Stockholm 2012 - Th.mueller@dlr.de Page 7 Day X Concept – Draw backs Parallel installation of System at Col-CC rack space, cabling,… -> real no issue Parallel installation of local keysets console space, redundancy,… Parallel installation of remote keysets console space, double bandwidth, logistics (two travels)… Double interfaces to external systems double bandwidth, capability of interfaces (technical and sizing), logistics … Clear NoGo(s) for this approach!

8. SpaceOps Stockholm 2012 - Th.mueller@dlr.de Page 8 Step-by-step Approach Build up of the new system while the old system is still in operations followed by coupled operations of both systems with a step-by-step migration to the new system. Migration Steps: 1.Preparation work at Col-CCno impact on ops rack space, cabling (including control rooms),… 2.Installation of main matrix at Col-CCno impact on ops stand alone testing 3.Coupling of old and new systemno impact on ops limited 96 shared loops, special conversion equipment 4.Installation of first set of local keysetsimpact on sim dedicated control rooms for simulation, training, testing

9. SpaceOps Stockholm 2012 - Th.mueller@dlr.de Page 9 Step-by-step Approach contd. 5.Installation of EAC systemimpact on sim training system at EAC, system-to-system tests 6.Migration of International Partner Interfacesimpact on ops most critical activity, step-by-step 7.Migration of remote keysetsminimal impact on ops limited 96 shared loops, special conversion equipment 8.Installation of remaining local keysetsno impact on ops control room swaps,… 9.Decoupling of old and new systemno impact on ops End of migration Worked better than expected with much less impact than awaited

10. SpaceOps Stockholm 2012 - Th.mueller@dlr.de Page 10 Problems and Constraints Planning with different parties Delays in shipment, customs, prep work at external sites Operational contraints Replanning of operations Close interface to Mission director(s), FCT, etc. Every step was presented to ops teams in detail ATV#2 flight Migration had to be coordinated with preperation for ATV#2 flight Interface change with ATV-CC system Required ad-hoc verification and re-scheduling to meet ATV#2 schedule Protocol conversion between old and new system Testbed with supllier beforehand Keyset Problems Change of roll-out plan for local keysets Delay of interface migration at MCC-H Temporary solution until now!

11. SpaceOps Stockholm 2012 - Th.mueller@dlr.de Page 11 Testing and Validation The step-by-step approach required to deviate from a classical test and validation approach Factory acceptance Done in a classical way Limitation in validation of external interfaces Testbed with Col-CC was very useful Site Acceptance Campaigns Testing followed the step-by-step migration approach At each migration step was followed by a certain amount of testing Intrusive test only in stand-alone mode No intrusive tests after system was connected to external world and used for ops Simulations used for load test Site Acceptance Review Review of all testing performed during migration Operational Readiness

12. SpaceOps Stockholm 2012 - Th.mueller@dlr.de Page 12 Conclusion A challenging project to replace an intensively and frequently used system during on-going operations. With help of all involved parties and a high amount of flexibility, paitience and understanding this became a success. Thanks to all involved teams! …and thanks for your attention!