spaceops stockholm 2012- [email protected] page 1 spaceops 2012 stockholm col-cc voice system...

SpaceOps Stockholm 2012- [email protected]

SpaceOps 2012 Stockholm

Col-CC Voice System Migration During On-Going Operations

Thomas Mueller, DLR, GSOC/Col-CC, Germany

SpaceOps Stockholm 2012 - [email protected]

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


The Col-CC Voice System connects

The International Partner Control Centers

MCC-H, MCC-M, HOSC

ATV-CCDedicated system for ATV

operations

EACDedicated system for training

Local Keyset60 keyset at Col-CC

Remote Keysets80 keysets at 21 ESA facilities


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


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!


Day X Concept

Complete built up of the new system in parallel and then switch-over to new system at day X.


Day X Concept – Draw backs

• Parallel installation of System at Col-CCrack space, cabling,… -> real no issue

• Parallel installation of local keysetsconsole space, redundancy,…

• Parallel installation of remote keysetsconsole space, double bandwidth, logistics (two travels)…

• Double interfaces to external systemsdouble bandwidth, capability of interfaces (technical and sizing), logistics

…

• Clear NoGo(s) for this approach!


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-CC no impact on ops

rack space, cabling (including control rooms),…

2. Installation of main matrix at Col-CC no impact on opsstand alone testing

3. Coupling of old and new system no impact on opslimited 96 shared loops, special conversion equipment

4. Installation of first set of local keysets impact on simdedicated control rooms for simulation, training, testing


Step-by-step Approach contd.

5. Installation of EAC system impact on simtraining system at EAC, system-to-system tests

6. Migration of International Partner Interfaces impact on opsmost critical activity, step-by-step

7. Migration of remote keysets minimal impact on opslimited 96 shared loops, special conversion equipment

8. Installation of remaining local keysets no impact on opscontrol room swaps,…

9. Decoupling of old and new system no impact on opsEnd of migration

• Worked better than expected with much less impact than awaited


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!


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


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!

spaceops stockholm 2012- [email protected] page 1 spaceops 2012 stockholm col-cc voice system...

Documents