Galileo Avionica’s Methodology and Tools for the … Meeting Proceedings/RTO... · Galileo Avionica’s Methodology and Tools for the Design, Development, Integration and Testing

NATO/PFP UNCLASSIFIED

Galileo Avionica’s Methodology and Tools for the Design, Development, Integration and Testing of

Complex, Highly Integrated Avionics Systems

Ing. Vasco De Stefani and Dr. Roberto Primo Galileo Avionica – v.le Europa s.n.c.

20014 Nerviano

ITALY

([email protected] and [email protected])

1.0 INTRODUCTION

Today’s Operational Scenarios are characterized by their geo-political complexity and rapid evolution.

To dominate these scenarios, recent airborne ASW/ASuW systems have been developed to provide the Mission Commander with sufficient support to maintain the real-time awareness of the Tactical Situation, make the correct decisions and assure forces co-ordination, as required to achieve the maximum mission effectiveness.

This goal has been achieved by introducing:

•

•

• •

• •

•

advanced mission sensors, counter-measures and weapons;

extensive use of data links;

a Tactical Control System providing: functions to support the compilation of the Tactical Situation using the huge amount of information collected by both on-board sensors and received from external Agencies via data-links, functions to support the decision making process, advanced HMI aimed to reduce the air-crew workload;

a high level of system integration.

Galileo Avionica has a consolidated experience in the design, development, integration and testing of complex, highly integrated Avionics Systems acquired through its participation to the major Italian and European Programs.

In particular, Galileo Avionica has participated to the development of some of the most recent and advanced ASW / ASuW systems for both fixed and rotary wing (e.g. EH101, NH90, ATR42-MPA, P166-MPA).

Figure 1 shows a simplified block diagram of the Avionics / Mission systems architecture of the NFH (i.e. naval variant of the NH90 helicopter) to highlight the complexity resulting from the full integration of a suite of mission sensors, countermeasures and armaments, which could well equip a corvette, and the basic avionics required to fly an helicopter.

RTO-MP

Paper presented at the RTO SCI Symposium on “Multi-Platform Integration of Sensors and Weapons Systemsfor Maritime Applications”, held in Norfolk, USA, 21-23 October 2002, and published in RTO-MP-097(I).

-097(I) 28 - 1


mailto:[email protected]

mailto:[email protected]

Galileo Avionica’s Methodology and Tools for the Design, Development, Integration and Testing of Complex, Highly Integrated Avionics Systems


However, the real challenge is the design of HMI solutions that will allow a three / four members crew (including the pilots) to fly the helicopter and perform the mission with an acceptable workload (figures 2a and 2b shows the layout of the cockpit and the cabin consolles).

The Avionics / Mission systems architecture for a fixed wing MPA (ref. Figure 3) has the same complexity, but the HMI challenge is mitigated by the larger number of crew member among which the workload can be distributed.

Even smaller MPA, like the ATR-42 MPA, recently developed for the Italian “Guardia di Finanza” (Custom) and “Guardia Costiera” (Coast Guard) are characterized by the significant number of mission sensors to be integrated to fulfill the operational need (ref. figure 4).

The price to be paid for this massive high-tech approach is the need of a cost-effective mean to:

•

•

•

•

•

validate the effectiveness of the design, with respect to the Operational Requirement, before the system development will take place;

validate the achieved integration and performance with an affordable amount number of flight hours.

Moreover, the “traditional” development approach (ref. figure 5) is not adequate to cope with the complexity and level of integration required by these modern Avionics Systems, mainly because error / lacks of either requirement or specification as well as poor HMI design resulting into an excessive crew workload can be detected late in the program, when the cost / time to introduce the corrective actions is high or, sometime, not affordable.

2.0 THE NEED FOR A NEW METHODOLOGY

Only an innovative approach, based on a cost-effective development methodology and supported by adequate tools, allows:

a development time compatible with the urgency of the operational need which justify the entry on service of a new aircraft, or the upgrading of an existing one;

a development cost compatible with reduced budget for military expenses;

a development risk kept to the minimum.

The primary objective of Galileo Avionica’s methodology is reduction of time, cost and risks associated to the development of a complex, highly integrated Avionics System and to its in service maintenance and upgrade, throughout the entire life cycle of the A/C on which it is installed. This primary objective is then broken-down into sub-objectives, applicable to the different Phases of the Program.

During the Design Phase, the objective is to Increase the capability to detect and correct, with the End-User involvement, errors or lacks in the Operational Requirement and/or in the System Design Specifications, as well as a poor HMI design resulting into an excessive crew workload.

This shall be done, before that acquisition/development of real HW and/or SW components takes place, therefore when the time and cost to introduce and validate the appropriate corrective actions are still affordable (ref. figure 6).

During the Integration and Validation Phase, the objective is to increase the realism and functional coverage of the tests which can be executed on the Operational SW (OPSW) Validation Station (SVS) and on the Avionics Integration Rig.

28 - 2 RTO-MP-097(I)




In this way it is possible to convert many expensive flight test activities into cheaper SVS and Rig test activities with the further advantage of deterministic and repeatable test conditions and test environment.

The result is a drastic reduction of time, cost and risk to achieve validation and certification of the Avionics System (ref. figure 6).

Finally, during the Operational In-Service Phase, the objectives are:

•

•

•

•

•

•

•

•

•

•

•

•

•

grant the availability of the integrated development environment and its re-usability to support maintenance and upgrading activities (which can be carried out also by the End-User, without further involvement of Galileo Avionica) and

offer the maximum possible commonality and re-usability of HW and SW modules of the integrated development environment for the development of Mission Planning/Simulation Stations and Procedural/Flight Training Simulators, for either new and/or already existing aircraft.

3.0 GALILEO AVIONICA’S TOOLS, STRATEGIC CHOICES AND THE ATENA ENVIRONMENTS

To support its methodology, Galileo Avionica has developed an integrated environment (ATENA – Advanced Test ENvironment for Avionics) based on the following strategic choices:

make an extensive use of Commercial-Off-The-Shelf (COTS) hardware and software (ref. figure 7):

taking advantage of a market offering a wide choice of state-of-the-art, high performance, general purpose equipment and tools, which are also affordable and well supported; selecting and buying those which “de facto” represent a world-wide standard among the major Avionics / Platform Integrators;

develop the hardware and software components which are specific to the application;

develop the hardware and software tools and services which are necessary to integrate and run the COTS with the application specific components;

follow a modular design approach that assures flexibility during the development and re-usability of the result for maintenance and upgrade and support to operational service.

To support the subsequent phases of the system development, different environments are provided in the ATENA family, all sharing HW and SW modules to reduce the overall time and cost of the Program (ref. figure 8).

The first environment is the System Integration Reference Environment (SIRE – ref. figure 9), which is used to validate the Operational Requirement, the System Design Specifications and the HMI solutions with the direct involvement of the End-User (rapid “virtual prototyping” techniques are used). The Reference Environment includes:

a simulation of reference Operational Scenarios against which reference missions can be played;

a 6-DOF model of the A/C;

a model of the A/C systems relevant for the purpose of the SIRE;

a model of basic avionics systems and equipment;

a model of the mission system.

RTO-MP-097(I) 28 - 3




The second environment is the Software Validation Station (SVS – ref. figure 10), which is used to validate the real Operational SW (OPSW) on real target HW against dynamic test cases based on coherent set of data generated by realistic mission simulations played in the Reference Environment.

With respect to the SIRE, the major change introduced in the SVS is the addition of the Advanced Integration Acquisition and Stimulation System (AIDASS) module, which allows the emulation of the real interfaces of the avionics / mission systems and equipment.

The SVS is intended to complement and not to replace the Software Development Environment (SWDE) used for OPSW development and validation on host/target HW using static / dynamic tests.

The third environment is the System Integration Rig (Rig – ref. figure 11), which is used to validate the integration of the complete Avionics / Mission System against dynamic test cases based on coherent set of data generated by realistic mission simulations played in the Reference Environment. For this purpose, both real equipment and/or their simulation are used.

A “natural evolution” of the System Integration Rig is the System Procedural Trainer (ref. figure 12), where the Supervisor Station will evolve toward an Instructor station. Both visual and motion capability can be easily added as required to upgrade toward a full Flight/Mission Training Simulator.

ATENA environment modules can also be used to build modular, re-configurable low-cost Procedural / Flight Training Simulators (ref. figure 13).

Last but not the least, the modularity and flexibility of ATENA environment components allow their re-configuration as the “core” of a Mission Planning/Simulation system (ref. figure 14).

28 - 4 RTO-MP-097(I)




TCS

2x 2x 1x1x 1x

ICSIFF

XPNDRCOMMS. NAS PMS CDS

DL11 Sonics Radar IFF INT. EWS E/O MAD SMS

STANAG 3838 Core Data Bus

VideoKinematic Data

Audio & Data/Audio5x RTs

BC/BBC

TCS

2x 2x 1x1x 1x2x 2x 1x1x 1x2x2x 2x2x 1x1x1x1x 1x1x

ICSIFF

XPNDRCOMMS. NAS PMS CDSICSIFF

XPNDRCOMMS. NAS PMS CDSICSIFF

XPNDRCOMMS. NAS PMS CDSIFF

XPNDRCOMMS. NAS PMS CDS

DL11 Sonics Radar IFF INT. EWS E/O MAD SMSDL11 Sonics Radar IFF INT. EWS E/O MAD SMSDL11 Sonics Radar IFF INT. EWS E/O MAD SMS

STANAG 3838 Core Data Bus

VideoKinematic Data

Audio & Data/Audio5x RTs

BC/BBC

STANAG 3838 Mission Data Bus

BC/BBC

STANAG 3838 Mission Data Bus

BC/BBC

Figure 1: NH90 NFH Avionics / Mission Systems Simplified Block Diagram.

RTO-MP-097(I) 28 - 5




AFCS

DTDDKU

Spare

Fuel

LandingGear

AFCS

Weapon

Delivery

C/F

Jettison

FCS

IFF B-upIFF M4

DKU

CCU

Aux KB

ICS

Tacan

DL-11Crypto

CCU

Aux KB

ICS

V/UHF

Steering

Harpoon

IFF Int

V/UHFCrypto

V/UHFCrypto

AFCS

DTD

StaticPressure

Units installed in the ceilingof the Cabin-Cockpit corridor

TacticalDisplay

(1)

TacticalDisplay

(2)

TacticalDisplay

(3)DKU

Light CTRL

DomeCTRL

ICS

ICS/RADIO PTT

CCU

TacticalDisplay

(1)

TacticalDisplay

(2)

TacticalDisplay

(3)DKU

AUX Kboard

SENSO OPERATOR CONSOLLE 4th CREW OPERATOR CONSOLLE

(PROVISION FOR ONLY)

ICS

Figure 2a: NFH Cockpit Layout. Figure 2b: NFH Cabin Consolles.

28 - 6 RTO-MP-097(I)




TacticalDisplay

Mission System Equipment: Data Links, Radar, IFF Interrogator, ESM, E/O, Acoustic, MAD

Stores Management System

Self Defense System

Basic Avionics Equipment:

CNI, EFIS, AMS, AFCS

Figure 3: Mission System / Tactical Control System for new MPA Proposals.

RTO-MP-097(I) 28 - 7



28 - 8 RTO-MP-097(I)


MISSION MANAGEMENT SYSTEM

ESM E/O SYSTEM

SENSOR BUS

COMMUNICATIONS BUS

VIDEO LINES

MISSION LAN

TV CAM. FLIR UV

SEARCHRADAR

DF V/UHFRADIO

COLORPRINTER

MISSIONCOMPUTER

FMSIRS

AHRSRADIO ALT.

VORTACAN

ADFGPS

BASIC A/CAVIONICS

VIDEODISTRIBUTION

MANAGER MULTIFUNCTIONOPERATOR CONSOLE (1)

COORD.OFFICERDISPLAY

COCKPITDISPLAY

VIDEO to VDM

MULTIFUNCTIONOPERATOR CONSOLE (2)

COMMUNICATIONCONSOLE

COMMUNICATIONS&

DATA LINK

Figure 4: ATR42 MPA Mission System and Tactical Control System Simplified Block Diagram.




Oper. Req.

SystemSpecification

HW & SWDevelopment

Integration and Teston RIG

Flight Test

time

detected errors

Oper. Req.

SystemSpecification

HW & SWDevelopment


Flight TestOper. Req.

SystemSpecification

HW & SWDevelopment



SystemSpecification

HW & SWDevelopment



SystemSpecification

HW & SWDevelopment


Flight Test

time

detected errors

time

detected errors

Development Errors

Operational Requirement Lacks/Errors, System Specification Errors, Excessive Crew Workload

cost and time for corrective actions

Development Errors


Development Errors


cost and time for corrective actionscost and time for corrective actions

Figure 5: “Traditional” Non-Simulation Based Development Approach.

RTO-MP-097(I) 28 - 9




Oper. Req.

SystemSpecification

HW & SW Developmentwith SVS Support


Flight Test

Op. Req.Validation

HMIValidation

Reference EnvironmentOperational Scenario, A/C and Basic/Mission Avionics Systems, SMS and Weapons/Stores Models

time

detected errors

Oper. Req.

SystemSpecification



Flight Test

Op. Req.Validation

HMIValidation


Oper. Req.

SystemSpecification



Flight Test

Op. Req.Validation

HMIValidation


time

detected errors

time

detected errors

Development Errors


cost and time for corrective actions

Development Errors


Development Errors


cost and time for corrective actionscost and time for corrective actions

Figure 6: “State of the Art” Simulation Based Development Approach.

28 - 10 RTO-MP-097(I)


COTS SW PStatemate I-Logix (USA)

STAGE VPI (Canada)

VAPS VPI (Canada)

FLSIM/HELISIMVPI (Canada)

Vtree/TerraVist(CG2)

Galileo Avionica h• the hardware a• the hardware

components;



ackages Application Galileo Avionica’s Customization Avionics Design and Validation: it is an integrated environment used for: Requirement Traceability; Functional Analysis; Modeling and Simulation of the logic and functional behavior of the

Avionics System components

Traceability of the Requirement specific to the application;

Functional Analysis for the specific application; Modeling and Simulation of the logic and

functional behavior of the specific Avionics System.

Tactical Scenario Simulation: it is a Tactical Scenario simulator capable of simulating: the characteristics and the behavior of friendly and hostile forces

participating to a an operational scenario (including sensors, weapons and countermeasures characteristics and performance);

the characteristics and effects of terrain and environmental conditions.

customization of the Tactical Scenario in accordance with a Reference Operational Environment; specific for the application.

Pilot-Vehicle Interface Design and Simulation: it is an integrated graphic environment used: during the design and concept validation phase for the rapid

prototyping and simulation of the Pilot-Vehicle interface; during the development phase for the generation of the formats to

be integrated in the real displays.

rapid prototyping and simulation of the I/O devices used by the Pilot-Vehicle interface for the specific application;

development of the formats to be downloaded and integrated in the real displays used for the specific application.

A/C Simulation: it is a 6 Degree Of Freedom, general purpose aircraft simulator which can be tailored to simulate the specific dynamic characteristic of any aircraft.

tailoring of the model parameters in accordance with the dynamic characteristic of the specific aircraft.

a “Out of the Window” Scenario Simulation: it is a graphic tool capable of generating a 3D “Out of The Window” (OTW) visualization of the Tactical Scenario generated by STAGE, as seen from the Aircraft cockpit.

as also developed: nd software components which are specific to the application;

and software tools and services which are necessary to integrate and run the above listed COTS SW packages with the application specific

Figure 7: Main COTS Software Packages and Galileo Avionica’s Customization and Integration.

RTO-MP-097(I) 28 - 11




In Service Support

Fast Prototyping (SIRE)Operational Requirement analysis and Design Specifications validation. HMI design and validation supported by a “Fast Prototyping” environment

Avionics Integration RIG

Operational SW (OPSW) SW/SW and HW/SW integration and validation using static and dynamic tests based on a realistic simulation of the Operational Scenario, own A/C and real simulated equipment.

Mission Planning and Simulation Stations

Multi-platform Mission Planning and Simulation station.Possible integration with existing C3I networks.

Procedural and Flight Training Systems

Modular, re-configurable Procedural and Flight training Systems

Realistic models of the Operational Scenario, own A/C, its main on board systems, HMI and OPSW functions.

SW Validation Station (SVS)

Operational SW (OPSW) SW/SW and HW/SW integration and validation using static and dynamic tests based on a realistic simulation of the Operational Scenario, own A/C and Avionics System.

Design, Development, Integration, Test and Validation

Realistic models of the Operational Scenario, own A/C and its main on board systems.

Figure 8: ATENA Integrated Environment Modules.

28 - 12 RTO-MP-097(I)




Mission Sensors and WMSModels

SupervisorI/F

OperationalScenario

Own A/CModel

TCSModel

Basic AvionicsModel

HMI I/F

VisualI/F

VAPSSTAGE

FLSIM

CG2

DevelopmentWork Stations

System SupervisorWork Stations


SupervisorI/F

OperationalScenario

Own A/CModel

TCSModel

Basic AvionicsModel

HMI I/F

VisualI/F


SupervisorI/F

OperationalScenario

Own A/CModel

TCSModel

Basic AvionicsModel

HMI I/F

VisualI/F

VAPSSTAGE

FLSIM

CG2

DevelopmentWork Stations


STATEMATESTATEMATE

Figure 9: System Integration Reference Environment (SIRE).

RTO-MP-097(I) 28 - 13




Figure 10: Software Validation Station (SVS).


SupervisorI/F

Operational Scenario

Own A/C Model

TCSModel

Basic AvionicsModel

HMI I/F

Mission Sensors and WMSI/F (ICD based) Models

Basic Avionics I/F(ICD based) Models

Note: All equipment I/F emulators are developed in accordance with the equipment Interface Control Document (ICD) so that their behavior results identical, from the electrical, logical and functional point of view, to the behavior of the real equipment.

In addition the Operator can manually enter/modify each single data or parameter to force error/anomalous conditions to stress the robustness of the system design.

AIDASS

Real Cockpit Workstation and

Cabin Consolles

28 - 14 RTO-MP-097(I)


TacticalDisplay



Basic Avionics Rig Mission Equipment STTE

Figure 11: Integration RIG.


SupervisorI/F


Own A/C Model

TCSModel

Basic AvionicsModel

HMI I/F

VisualI/F



Mission System Real Equipment

Basic Avionics Real Equipment

RTO-MP-097(I) 28 - 15


TacticalDisplay




InstructorI/F

OperationalScenario

Own A/CModel

TCSModel

Basic AvionicsModel

HMI I/F

VisualI/F



Basic Avionics I/F adapter Out of the Windows Projection

Supervisor InstructorWork Stations

Realistic Cockpit and Cabin Consolles


InstructorI/F

OperationalScenario

Own A/CModel

TCSModel

Basic AvionicsModel

HMI I/F

VisualI/F



Basic Avionics I/F adapter Out of the Windows Projection




InstructorI/F

OperationalScenario

Own A/CModel

TCSModel

Basic AvionicsModel

HMI I/F

VisualI/F




InstructorI/F

OperationalScenario

Own A/CModel

TCSModel

Basic AvionicsModel

HMI I/F

VisualI/F



Basic Avionics I/F adapter Out of the Windows ProjectionBasic Avionics I/F adapter Out of the Windows Projection






InstructorI/F

OperationalScenario

Own A/CModel

TCSModel

Basic Avionics


InstructorI/F

OperationalScenario

Own A/CModel

TCSModel

Basic AvionicsModel

HMI I/F

VisualI/F



Basic Avionics I/F adapter

Model

HMI I/F

VisualI/F



Basic Avionics I/F adapter Out of the Windows ProjectionOut of the Windows Projection



PFDND

CDU CDU

PFD NDTacticalDisplayPFDND

CDU CDU

PFD NDTacticalDisplay

Figure 12: Trainer.

28 - 16 RTO-MP-097(I)





Tactical ObjectsModels Database

System Supervisor InstructorI/F

GalileoTrainingSimulator

Own A/CModel

Own A/C AvionicsModel

Own A/C HMIModel

Out of the WindowsProjection

DomeProjector


ReconfigurableCockpit Mock-Up

andModels





GalileoTrainingSimulator

Own A/CModel

Own A/C AvionicsModel

Own A/C HMIModel

Out of the WindowsProjection

DomeProjector


ReconfigurableCockpit Mock-Up

andModels

Operational ScenarioModel



Customer SimulatorInterface

CustomerTrainingSimulatorVisual+Motion


Customized I/F





Customer SimulatorInterface

CustomerTrainingSimulatorVisual+Motion


Customized I/F

PFDND

CDU CDU

PFD NDTacticalDisplay

Figure 13: Modular Re-Configurable Procedural/Flight Trainers.

RTO-MP-097(I) 28 - 17



28 - 18 RTO-MP-097(I)





External CommunicationsInterface

Cable / RFVoice / DataComm. Links

DataTransferDevice

System SupervisorI/F

Mission PlannersWork Stations

(multi-types multi-units simultaneous slanning)


External Agencies Vehicle Avionics System





DataTransferDevice



DataTransferDevice









External Agencies Vehicle Avionics System

Figure 14: Mission Planning / Mission Simulation Systems.

Documents

Galileo Avionica’s Methodology and Tools for the … Meeting Proceedings/RTO... · Galileo Avionica’s Methodology and Tools for the Design, Development, Integration and Testing