Integration and validation of the ATV Control Center

1
Integration and validation of the ATV Control
Center

• Véronique VALETTE, Carole LARIGAUDERIE,
  Christophe HUGONNET, Patrick CHARLOT
• Centre National dEtudes Spatiales
• Centre Spatial de Toulouse, 18 avenue Edouard
  Belin,
• 31401 Toulouse Cedex 9
• FRANCE

2
Integration and validation of the ATV Control
Center

• ATV Project
• ATV-CC Environment
• ATV-CC Architecture
• AIV Strategy and Presentation of the Tests
• Verification Process
• Assembly, Integration Verification team
• Process Schedule

3
ATV Project

• ATV Automated Transfer Vehicle, Jules Verne,
  will be the first ESA space vehicle to rendezvous
  and dock with the International Space Station
  (ISS).
• Support the logistics maintenance of the ISS
  through dry and wet cargo delivery and disposal,
  and support ISS on-orbit control through its
  re-boost capability.
• Launched on an Ariane 5 and will remain attached
  to the Russian Segment of ISS (ISS-RS), for up to
  6 months, before de-docking and performing a
  destructive re-entry into the Earths Atmosphere.
• The ATV Control Center (ATV-CC) is an ESA
  project developped by CNES as prime contractor
  and is located in CNES facilities in Toulouse.

4
(No Transcript)
5
(No Transcript)
6
ATV Control Center Environment

• The ATV control center is integrated in a
  pre-existant network of manned-space control
  centers and has many interfaces with external
  partners sites
• WS GS White Sand Ground Stations for the TDRSS
  satellites to receive ATV telemetry,
• MCC-H Mission Control Centre of Houston for
  ISS,
• Redu EET and ARTEMIS MCF Mission Control Centre
  of Redu for Artemis satellite to receive ATV
  Telemetry,
• MCC-M Mission Control Centre of Moscow for ISS,
• Col-CC Columbus Control Centre (IGS management
  control facility, Central Dass server for
  processed data),
• ATV EGSE / FSF at Les Mureaux or ESTEC,
• EST (Engineering Support Team, vehicle experts)
  off-site  at Les Mureaux
• Kourou  A5 CVI and ATV EGSE using ICARE (CNES
  operational data network).

7
Icare
8
ATV-CC Architecture

• ATV-CC is split into 9 subsystems
• ATV-CC Infrastructure and Lans,
• Monitoring Control sub-system in charge of all
  the functions related to the monitoring and
  control of the ATV performing the real time
  analysis of the received telemetry and preparing
  and sending the telecommands.
• TTFEE The Telemetry Telecommand Front End
  Equipment, in charge of the real-time data
  exchanges with TDRS or Artemis ground terminals.
  This equipment is split into three parts the
  main equipment within ATV-CC, and a remote
  element within ESA Gateway at MCC-H in Houston
  and at Artemis Ground Station in Redu.
• Flight Dynamics sub-system in charge of all the
  flight dynamics functions during all phases of
  the mission (preparation, execution and mission
  assessment)

9
ATV-CC Architecture

• Data Gateway sub-system, which is in charge of
  all the data exchange between the real-time
  Operations world and the off-line Office
  Automation world, restricted to all non
  real-time external exchanges.
• Office automation sub-system provides office
  tools and also procedures management using MOIS
  tool and Flight Operational Plan tool.
• OCT, Operational Complementary Tools, including
  Memory Image Management, housed by Office
  automation sub-system.
• Voice sub-system.
• Video distribution sub-system.

10
ATV-CC Architecture

• The ATV-CC is composed of
• a nominal center in which all the subsystems are
  redunded
• a backup center
• 40 Unix servers, 40 Unix clients,
• 8 windows application servers, 110 windows
  clients,
• 20 printers dispatched
• 3 networks and 3 DMZs per control center (nominal
  and backup).
• All the interfaces are technically described in
  the ATV-CC External and Internal Interfaces
  Definition Document which represents about 120
  external interfaces and 100 internal interfaces.

11
ATV-CC Architecture
12
AIV Strategy and Presentation of the Tests

• The AIV process includes the following tests
  activities
• Subsystems acceptance tests, which are technical
  and contractual tests between CNES and its
  sub-contractors
• Internal Assembly tests (IAT), which validate the
  internal interfaces between subsystems two by
  two.
• ATV-CC standalone system validation tests ,
  functional tests with all the integrated
  subsystems
• Ground segment interface tests (IT) and End to
  End ground tests to validate all the external
  interfaces of the ATV-CC
• ATV system validation tests (SVT) to test the On
  board/Ground interfaces

13
(No Transcript)
14
Sub-Systems acceptance

• Verify the correct implementation of all
  requirements as described in the subsystem
  requirements document and to accept the
  sub-contractor deliveries
• Splitted into Factory acceptance and On-site
  acceptance
• The acceptance plan and the individual test
  procedures are elaborated by the sub-contractor
  and shall be approved by CNES.

15
Integration Assembly tests

• Verify and test the internal interfaces between
  the subsystems
• The subsystems are integrated two by two, ans all
  the interfaces between the two subsystem are
  verified
• The integration test specifications and
  procedures are written and executed by CNES
  integration team
• Iterative process run at each new version of a
  subsystem leading to ATV-CC versions

16
Standalone verification

• The standalone verification aims to validate the
  entire integrated ATV-CC including the switches
  between nominal and backup centers
• The test procedures are written by CNES
  validation team and approved by ESA. All tests
  are performed by CNES team under ESA supervision.
  
• These tests are the last step before the ESA
  ATV-CC Qualification Acceptance review

17
Interface Tests

• Validation of each external interface of the
  ATV-CC on a technical basis, without taking into
  account operational aspects. The responsibility
  of these tests is shared between partners under
  ESA leadership
• The Interface tests are conducted on a 2 by 2
  basis and defined as follows
• IT1 Connectivity
• IT2 Telemetry exchange
• IT3 Telecommand
• IT4 Voice
• IT5 Video
• IT6 File exchange
• IT7 Archived data retrieval
• IT8 Operation, preparation, planning
• IT9 Security
• IT10 Redundancy

18
Verification Process

• The coverage of the ATV Ground Segment
  requirements will be demonstrated by ensuring
  the traceability between the ATV-CC system
  specification and the ATV-GS SRD which is the ESA
  ground segment specification
• The traceability link is managed using an ACCESS
  database and requests
• The Verification Control Document (VCD) will
  summarise the verification results with regard to
  the GS SRD.
• A coverage matrix of all the internal and
  external interfaces is also constructed as part
  of the Interfaces Validation Reports.

19
AIV Team

• The size and composition of the test team
  ,depends on the type of test.
• For IAT, the AIV team is composed of the core
• AIV manager,
• 2 AIV support,
• 2 integration supports (1 for each subsystem)
• Operating System, OA administrator,
• Software Quality Assurance Manager

20
Process schedule

• The Assembly, Integration and validation process
  of the ATV Control Center has begun Mid 2003 with
  the acceptance of the first subsystem and is
  still going on . We have performed about 45 two
  by two integration tests between sub systems,
  which represents about 2/3 of the identified
  integration tests. Two major versions of each
  Monitoring and Control and Flight dynamics
  subsystems are still to be accepted and
  integrated.
• The Integration Tests have begun end 2004 and are
  at about 90 completed.
• The standalone validation is going to be run
  during the next monthes.