Introduction and Status of SAVOIR · 2013. 10. 22. · procurement and development, while preparing...

ESA UNCLASSIFIED – For Official Use

Introduction and Status of SAVOIR

On behalf of the SAVOIR Advisory Group Kjeld Hjortnaes – ESTEC/TEC-SW

Head of Software Systems Division


K. Hjortnaes | SAVOIR Status | ADCSS-2013 | 22-Oct-2013 | Page. 2

SAVOIR.

SAVOIR means Space Avionics Open Interface aRchitecture.

It is an initiative to federate the space avionics community and to work together in order to improve the way that the European Space community builds avionics subsystems.

SAVOIR is coordinated by the Savoir Advisory Group including representative of ESA, CNES, DLR, Astrium, Thales, OHB, RUAG, Selex Galileo, Terma.



What is it all about.

Improve the way we deliver space systems.

Support industrial competitiveness.

Enhance product orientation.



Product orientation

Improve the way we deliver Space Systems (cost & schedule) by

Pre-developed Products / Building Blocks based on

well defined Specification & Interfaces based on

an agreed Reference Architecture



SAVOIR objectives

– to reduce the schedule and risk and thus cost of the avionics procurement and development, while preparing for the future,

– to improve competitiveness of avionics suppliers,

– to influence standardization processes by standardizing at the right level in order to get equipment interchangeability (the topology remains specific to a project).

– to define the governance model to be used for the products, generic specifications, interface definition of the elements being produced under the SAVOIR initiative.

The process is intended to be applied as part of the Agencies ITTs, and throughout the subsequent procurements and development process. A particular goal is to have SAVOIR outputs exploited in future projects and relevant products as part of European supplier’s portfolios.



SAVOIR Output

The primary outputs of Savoir are:

– reference avionics architecture for spacecraft platform hardware and software,

– a set of avionics external and internal interface specifications,

– the definition of building blocks composing the architecture,

– the functional specification of selected building blocks comprising the architecture,

– Demonstrate maturity of the functional & Interface specification by performing prototyping activities

– Facilitating the implementation of selected building blocks.



SAVOIR expected benefits

SAVOIR supports:

– space avionics customers and system architects,

– system integrators,

– avionics and technology suppliers,

– standardization bodies.

It is a tool for the industrial policy and R&D planning makers.

The expected benefits of SAVOIR are:

– for customers, streamline the procurement process of spacecraft avionics,

– for system integrators, facilitate the procurement and integration of the spacecraft avionics,

– for suppliers, prepare the technical conditions for an efficient product line organization.



Organisation

Software reference

architecture

Electrical interface

(Data & Power)

Sensor/Actuator Functional Interface

Advisory Group

TSP based Software reference

architecture



SAVOIR perimeter

SAVOIR focus on the Platform Avionics including Payload Interfacing

Build on the pillars

Data Handling Hardware

Control Sensors & Actuators

On-board Communication

Flight Software

Related topics

The operations view

Development and Verification Process.

Model Based Development

Functional Verification strategy.

Links the system data repository.



Agree on which functions

compose the perimeter of

avionics and how to allocate them to BB if needed.

Measure the effectiveness

of SAVOIR recommendations and approach, in

terms of costs and effectiveness.

Agree on variability and modularity of the specifications for the selected BB or for groups of BB.

Agree on the most important BB to standardize and develop. Propose a roadmap to implement them.

SAVOIR is an initiative to federate

the space avionics community to work together in order to:

• Improve the way to deliver

space programs. • Set a « product philosophy »

approach. • Deliver elements usable by the

customers, the system integrators and the

suppliers.

System

Reference Architecture

1

Product

Use Assesment

4

Generic

Functional Specification

3

Building Blocks

Selection 2 Define

Interface (IRD)

Refine Interface

(ICD)

The SAVOIR wheel

Domain of reuse

Key Performance

Indicators

Domain design

Reusable spec & I/F standards



SW Func. spec’s SW Func.

spec’s i/F spec’s i/F spec’s

SAVOIR process

Avionics Ref. Architecture

Hardware Functional. Architecture

Com’s I/F & protocols

Software Ref. Architecture

I/F spec’s

HW physical topology

Com’s protocols

SW Architecture

Products

Software Factory

Hw Func Spec’s Hw Func Spec’s Hw Func Spec’s Com’s

protocols Com’s

protocols

Manufac-turing

Project specific SW req.

Project specific HW req.

Pre-dev. HW components

Executionplatform Spec’s

SW Func. spec’s

Pre-dev. SW components



The Avionics Reference Architecture

OBT Mgmt P/L Manager

System mode mgmt Power

Plan/ Autonomy Framework Thermal

AOCS Applications

SSMM Mgmt

Satellite Conf and Eqpt Mgmt

System FDIR

Component services

On-board time =SOIS TAS

Abstract component

services

Container services

RTOS

Connector services

Communication services

addressing physical

distribution across nodes = SOIS MTS

PUS specific

PUS

Context Mgmt

Avionics Equipment

virtual devices =SOIS DVS

PUS monitoring

OBCP interpreter

SOIS Subnetwork layer (1553, CAN, SpW) (including HDSW)

CPU

EEPROM Boot PROM

RAM SGM

UART SpW

CAN MIL-1553 OBTimer

HW watchdog

Software bus

CPU

SOIS Layers

File/ Compress/

Encrypt

Solid State Mass Memory

Security Unit

Telemetry Telecommand

Payload Computer

Space Linux

Application

Payloads & Instruments

CPU

Sensors & actuators

Computation

microcontroller Digital Sensorbus

ADCs / DACs

Remote Terminal Unit Remote Interface Unit

Libraries: mathematical,

etc.

Standardized devices

Legacy devices

SOIS Layers

SOIS Layers

Onboard Communications H/W (e.g. MIL-STD-1553B, SpaceWire, CAN RS422)

Application software

Execution platform

On board computer Hardware

Intelligent devices

Buses

Hardware functions

BSP



SAVOIR HW Reference Architecture Functional View.

Telecommand

PlatformTelemetry

Time reference

Security

Reconfiguration

Processing

On-Board Time

PlatformData Storage

Safe-GuardMemory

EssentialTC

Cmd & Ctrl Links

MissionData Links

TCCLTUs

Authentication/Decryption

Encryption

TMCADUs

Context data,Boot report

CLCW

TC Segments

TCSegments

EssentialTM

TM packets

X

Enable/Disable

Alarms

Discretesignals

System alarms

Time andtime tick

Trig

Time tick

TMpackets

TM packets

TC Segments

Platform sensors and

actuators

Platform commanding

Payload commanding

Data Concentrator

Sensor and actuator I/F

Sensor and actuator I/F

Synchronisation

PayloadData

Storage

Instruments incl. ICUs,

Payload I/F Unit

PayloadData Routing

X

Platform Payload

TC Segments

TM packets,files

Time tick

Time

TMframesync

Payload synchronisation

Payload control

Inter-PM

Platform synchronisation

Hot redundant operation

Cold redundant operation

Hot or cold redundant operation

PayloadTelemetry TM

CADUs

Security

Encryption

Payload direct monitoring

PIO

PIO

Time & Tick

Context Data



Communication Network & Protocols



Software Reference Architecture



Software Reference Architecture Execution platform – ‘Classic’



Software Reference Architecture Execution Platform – ‘Time & Space Partitioning’



i/F spec’s i/F spec’s

SAVOIR process

Avionics Ref. Architecture

Hardware Functional. Architecture

Com’s I/F & protocols

Software Ref. Architecture

I/F spec’s

HW physical topology

Com’s protocols

SW Architecture

Products

Software Factory

Hw Func Spec’s Hw Func Spec’s Hw Func Spec’s Com’s

protocols Com’s

protocols

Manufac-turing

Project specific SW req.

Project specific HW req.

Pre-dev. HW components

Executionplatform Spec’s

Func. Chain spec’s



Pre-dev. SW components

Examples: - OBC gen Spec - RTU gen Spec (draft) - Payload gen I/F Spec (draft)

Examples: - Boot software - Execution platform’s (TSP or

Classic) - TSP kernels - Space component model.



Specification production scheme.

Under SAG agreement;

1. A draft version is produced;

By a SAG working group

Output of an R&D activity

Proposed by Industry

ESA internal

2. Submitted for restricted review and updated as needed

Check compliance to SAVOIR architecture and principle

Completeness / consistency / etc

3. Submitted for public review and updated (same objective as 2)

4. Verified by prototyping – to demonstrate maturity of the spec., consistency with the ref architecture (as far as possible on a case by case basis)

5. Publication

Functional / interface spec.

Public review

Proto-typing

Restricted review

publication



Public review of SAVOIR documents will be restricted member states only.

Objectives will be to verify

Completeness, consistency, coherence

Reusability, domain of reuse

Compliance to SAVOIR reference architecture

Dissemination aspects (e.g. proprietary information, IPR infringements)

Discussion with ECSS TA on-going

The role of the Savoir within ECSS still to be agreed

Public review of SAVOIR spec.



Visit the SAVOIR website

http://savoir.estec.esa.int/



Contact

Feedback: [email protected]

SAVOIR Advisory Group:

- Kjeld Hjortnaes – ESTEC/TEC-SW

- Philippe Armbruster – ESTEC/TEC-ED

- Alain Benoit – ESTEC/TEC-EC

- Jean-Loup Terraillon – ESTEC/TEC/SWE

- Juan Miro – ESOC/OPS-G

- Paul Arberet – CNES

- Fabian Greif– DLR

- Thierry Duhamel – Astrium

- Jacques Busseuil – ThalesAleniaSpace

- Bernard Bruenjes- OHB

- Carsten Jørgensen – Terma

- Torbjörn Hult – RUAG

- Franco Boldrini – Selex Galileo

mailto:[email protected]

Date post:	15-Oct-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times

Introduction and Status of SAVOIR · 2013. 10. 22. · procurement and development, while preparing...

Documents