Back-up control room helps ESOC balance the load

Although launches are normally conducted one at a time, ESOC's Main Control Room (MCR) could, in a pinch, handle two simultaneously. Three at once, however, would be a unique challenge, but that is precisely the situation facing ESOC facility planners as CryoSat, Venus Express and MSG-2 ramp up for launch on 8 October, 26 October and late December, respectively.

And it isn't just launch day itself that demands intensive use of the MCR.

Specialised LEOP expertise

Flight Control Team (FCT) activity in the big room continues throughout the launch and early orbit phase (LEOP), a focal point of ESOC's expertise, which starts immediately after a satellite separates from its launcher and can continue for several critical days or weeks while onboard instruments are verified and calibrated.

And if any problems occur, the MCR can be the scene of intense activity for many days, as it was for the famous post-launch recoveries of GEOS and Hipparcos. And that's just for a single mission.

Consider also that launch dates are notoriously fickle and depend on a complex set of factors coming together at the right time, including a suitable launch window, successful satellite check-out, booster readiness, flight certification and -- not least -- the weather. Thus having even two launches scheduled in the same month creates the risk that MCR needs will conflict.

Triple launches trigger active planning

Accordingly, in spring 2005, as it became apparent that the three launch dates would fall within the same tight period, it was decided to create a functional copy of the MCR in a then-empty science investigation room, known as a PISA (Principal Investigators Support Area), in ESOC's Building D.

The project involved not only replicating a fully operational copy of the MCR, with the minimum number of workstations and communication links necessary, but also replicating the Project Support Room and Software Support Room, used by industry engineers and software developers, which are crucial to supporting any mission.

"The project to build a back-up MCR and related rooms started in April 2005 and was complete by July. That's a rather short time for a complex project like this," says Beck.

He cites the excellent support received from suppliers and contractor companies, who responded quickly with "lots of goodwill" in view of the importance of the project.

Also, the budget was fixed in view of the time-limited need for the extra rooms, thus adding more limitations to an already hectic timeline.

Reuse of computing assets

As a result, maximum use was made of existing and in-stock mission control workstations, based on Sun Ultra 60 computers.

The back-up MCR was refurbished with new consoles, furniture, power and air conditioning, and provided with PCs and communication, data, video and other infrastructure links. "The biggest challenge was time," says Mark Thompson, a facilities engineer who helped oversee the project.

Thompson worked as part of a team that included as many as 60 people, drawn at various stages from ESOC's computer, communications, ground station and site infrastructure sections, among others.

"The first usage came in early August, just a week after we finished, for simulation runs by the CryoSat flight team," he says with much satisfaction.

Overall, ESA benefited from the quick implementation, adding a useful and potentially critical new capability at a time when launch activity is at a high tempo, and ESOC personnel demonstrated again that teamwork and careful use of resources are regular job requirements.

The new back-up facilities are being used for additional simulation and training sessions through August and September and will be available during the Cryosat and Venus Express launches.