- Partnership Projects
- Core Competitiveness
- How to Apply
- Our Projects
The Spacecraft Computer Unit (SCU MK1) is the central computer of the ASTRIUM Eurostar E3000 platform. This externally redounded unit (operating in hot redundancy) has demonstrated that it is well dimensioned in terms of interfaces, processing capability and level of configurability to suit various types of Telecom missions. Nevertheless, the constant market pressure forced us to revisit the SCU architecture in order to improve the overall competitiveness. This was also the opportunity to invest in a “durability” of the EEE parts of the SCU.
In order to avoid the issue of parts obsolescence, the development of a new version (SCU MK2) became crucial. It was proposed to take benefit from this mandatory evolution to introduce upgrades consistent with the overall Eurostar evolutions driven by competitiveness and customer needs.
click for larger image
click for larger image
The ability to offer an E3000 Spacecraft Computer Mk2 which incorporates these developments had an important impact on the overall competitiveness of the Eurostar E3000 communication satellite. Benefits are identified here after:
The SCU is the computer unit of the Service Module of the Eurostar E3000 platform for telecommunication satellites. It is in charge of carrying out both TM/TC/Data Handling and Altitude and Orbit Control activities.
The Spacecraft Computer Unit (SCU) presently used in the Eurostar E3000 platform had to evolve to better cope with the customer requirements and the evolution of the Eurostar E3000 platform definition.
TC security option:
The SCU improvement consisted in the design, the definition and the validation of the SCU Mk2. It was the opportunity to reduce the number of boards by gathering the processing boards (VPM) and Transponder Interface Board (TIF). This integration was made possible by using a single core ASIC embedding the main functions of previous design (use of IP products).
The design and development plan of the SCU Mk2 has covered the following activities:
To run these activities, the development plan was a standard development logic separated in several phases (Kick Off, BDR, MTR, QRR, Final review).
The validation of each phases and the passage to the next phase was made through formal reviews, and consolidated through a risk mitigation action plan. Building and successful testing of an Engineering Qualification Model (EQM) was mandatory to demonstrate the compliance to the unit technical requirements, but also for the functional chain validation and notably the compatibility with E3000 Flight Software