Implementierung der Systemkon- trolle und Systemsteuerung gemäß ASAAC Informationstag zur Informatik, TU Chemnitz 8.11.2005 Burkhard Balser, Michael Förster,

Implementierung der Systemkon-trolle und Systemsteuerung gemäß ASAAC

Informationstag zur Informatik, TU Chemnitz8.11.2005

Burkhard Balser, Michael Förster, EADS, MT321

Informationstag zur Informatik, TU Chemnitz, 8.10.2005Seite 2

Implementierung des Systemmanagement nach ASAACGSM

Inhalt

ASAAC Overview ASAAC Software and System Concept Blueprints Generic System Management Design and Implementation Details



ASAAC: involved Nations and Companies

DEM 110,000,000

FranceDassault AviationThomson CSF - Radar & ContremesuresThomson CSF - CommunicationsDassault ElectroniqueSextant Avionique

Budget:

U.K.GEC - Marconi AvionicsBritish Aerospace

Military Aircraft & AerostructuresSmith Industries Aerospace

GermanyDasa Military AircraftDasa Defence and Civil SystemsESG Elektroniksystem- und

Logistik GmbHLITEF GmbH



ASAAC: State of Work

T0

Stage 2 (45 Months)Stage 1 (15 Months)

Time

Demo Specs

1st draft Stan-dards

104 Documents

Demonstrations + Standards Validation

Core Arch

Con-cepts

Core + Applications

Concept 1Concept 2

Concept nStd. Arch

Std. NET

Std. S/W

StdH/W

2004

The ASAAC Program

2000

The three national ASAAC Program was finished in time



Inhalt




ASAAC Software Model

Application Layer

Operating System Layer

Module Support Layer

OperatingSystem

Generic System

Management

FunctionalApplications

ApplicationManagement

Run TimeBlueprint

System Management

MOS

APOS

SMOSSMBP

Aircraft Dependent,Hardware Independent

Aircraft Independent,Hardware Independent

Aircraft Independent,Hardware Dependent



ASAAC System Concept: Management Operations

Pilot/Application

Power

Ground Crew

Fault

Valid Avionic System State

Blueprints

System Design

System Manager

Mission Mode Management

Initialisation + Shutdown

ITM

Fault Tolerance

Reconfiguration



Inhalt




Blueprints

Blueprints are used at all Development Steps:– Designtime: Designtime Blueprints

• Resource Blueprints

• Application Blueprints

– Runtime: Runtime Blueprints Blueprints provide a formal context free

Description of the related Elements The Content of the Blueprints is defined by a

Grammar– for Runtime Blueprints the Grammar is expressed in

eBNF in the Standards for Software



Inhalt




GSM embedded in ASAAC Standards and Guidelines

Standards– APOS

– SMOS

– SMBP

– MOS/NII Guidelines: Definition of the

component’s behaviour– GSM with HM, FM, CM and BPM

APOS (incl. Communication)

SMOS

RTBP

MOS/NII

Hardware

SMBPFM CM

HM BPM

GSM



GSM embedded in the Generic ASAAC Design

ASAAC Components

RTOS Components

ASAAC Standards

Legend:

Application Code

APOS Adaptation Layer

RTOS VirtualChannel

Management

BSP

MSL

Process Management

RTOS-API

APOS

SMOS RTBP

MOS/NII

FM CM

HM BPM

GSMSMBP

APOS

Application

APOS-Lib



GSM Task: Configuration of Communication

Configure Interfaces Create TC Create VC Attach VC to TC Attach VC to Process Destroy TC Destroy VC Detach VC from TC Detach VC from Process

Virtual Channel Managementimplements Configuration Services

GSM

NII

SMOS

SMOS-Lib

VCM

VCDrv

MSL

VCMgt

RTBP

APOSLibAPOS

Application

APOSLibAPOS

Application



GSM Task: Configuration of Processes

Create Process Setup Scheduling Run Process Stop Process Destroy Process

Process Managementimplements Configuration Services

GSM

MOS

RTOS-API

SMOS-Lib

ProcessManager

MSL

ProcMgt

SMOS

RTBP

APOSLibAPOS

Application



GSM Task: Health Monitoring and Fault Management

Log Error Raise Application Error Get Error Information Destroy Process Get Fault Get Thread State

Process Management implementsServices for Fault Management

GSM

MOS

RTOS-API

SMOS-Lib

ProcessManager

MSL

ProcMgt

SMOS

RTBP

APOSLibAPOS

Application



ASAAC System Concept: Hierarchy of the GSM’s

Exchange of Messages between GSM’s

Delegation of Responsability:– Notification (of State or Error) is sent to

the next higher Level

– Command is sent to the next lower Level

– for each Level the Blueprints define the Generation and Handling of Notifications and Command

All Messages between the Levels are routed over VC's

GSM

Aircraft Level

Integration Area Level




ResourceElement Level





Inhalt




The GSM Project

System Requirement– Implementation to be used in future EADS M Projects

– Minimalisation of Dependencies of O/S Interfaces

– Design flexible to be incorporated in existing Environments with ASAAC or none ASAAC Behaviour

– Design flexible to incorporate existing Components of HM/FM/CM

Implementation Requirements– Using UML for Design and Code Generation

– Using Design Pattern for better Understanding

– Using ADA as the Target Language



Elements of the GSM

HM BPM

GSM

FM CM

The GSM consists of– Health Monitor

– Fault Manager

– Configuration Manager and 1 Interface

– SMBP and its Implementation

– Blueprint Manager



Generic GSM Component Design

Communication

Conversion

Threads of Control

SMOS

SMBP

APOS Generic Design of all

GSM Components– SMOS at RE Level only:

• Configuration of the RE,

including GSM Elements

• Controling of Processes,

Communication and Hardware

• Receiving Faults of Hardware

and Software

Using Interfaces of the Standard only

Instantiation of the real Component via a Factory



Inter GSM Component Communication

GSM Broker

Communication

Conversion

Threads of Control

SMOS

SMBP

APOS

Communication

Conversion

Threads of Control

SMOS

SMBP

APOS

Configurationvia CM-RE

Simplifies Implementation of Components– only one Channel for receiving

ore sending messages

– Routing wil be done by an external Component

Configuration of the GSM Broker is defined in the Blueprints

GSM Broker can translate Messages to communicate with GSM implemented differently



Comprehension (1) Implementation gives a full ASAAC System

Hierarchy for other Projects with– Resource Element Level

– Integration Area Level

– Aircraft Level

as described in the ASAAC Standards and Guidelines



Comprehension (2) Inheritance and Design Pattern allow a flexible

Implementation and Reuse of Elements– GSM Broker: Adaptor to external System Managers

– Converter: Adaptor to existing System Management Components for Health Monitoring, Fault Management or Configuration Services



Comprehension (3) O/S Dependencies are dedicated to explicite

Elements:– Process Management for O/S specific Process

Instantiation and Control

– Virtual Channel Management for O/S specific Communication Instantiation and Control

– ADA hides O/S specific Tasking and Synchronisation to the GSM Implementation