SCADE on-board the UAS P.1HH HammerHead The Use of SCADE to develop the P.1HH Vehicle Control & Management System (Integrated Modular Avionics System) greatly reduced development time and effort. Learn more about ANSYS SCADE Solutions for Aerospace & Defense http://bit.ly/1EdcsOJ

1. © 2015 ANSYS, Inc. August 7, 20151 © Esterel Technologies - An ISO 9001:2008 Certified Company - Confidential & Proprietary
ANSYS SCADE®
User Presentation
PIAGGIO Aerospace

2. Paris
October 17-18, 2013
MPA VCMS Application Software
SCADE Modeling & Testing
SCADE on BOARD

3. An aerospace company operating in the aircraft and engines
business
o Founded in 1884
o First aircraft in 1922
A vertically integrated organization capable to
o design, develop and manufacture aircraft
o manufacture aero engines parts
o maintain, repair and overhaul aircraft and aero engines
Privately held, international & national shareholders
Italy located, with approximately 1,400 employees
o High presence of engineers (# 160)
o Full product lifecycle management capability

4. Over 90 years in the aerospace industry, Piaggio has designed
and produced Engines, Propellers, Seaplanes, Helicopters,
Record and Race Aircrafts, Military & Civil Utility aircrafts
Aircraft
Production
Current products:
- P180 AVANTI II
- P166 DP1 (out of production)
Aircraft
Customer Support
Supported aircraft:
- P.180 AVANTI I & II
- P.166 DL3 & DP1
Engine
Production
Manufacturing:
Honeywell: T55; P&W: PW100
PW200, F-135; Rolls Royce: RRTM
322
Complete Assembly/Test:
PW200
Engine
MRO
Serviced engines:
Honeywell: T53, T55, LTP; P&W:
PW200; Rolls Royce: Allison 250,
Gem, Viper

5. Superior technology and unique design
o Advantage of the propulsion engines: enhanced
aerodynamics and less noise in the cabin
o Jet-like speed: 745 km/hr
o Long range: 2,795 km
o Revolutionary 3 lifting surfaces: unique design
for improved dynamics
o Reduced fuel consumption and reduced
maintenance results in a lower operating cost
P180 boasts technical characteristics and
performance which can only be compared with the
entry level jets
o Superior class of aircraft in terms of
performance, price and operating cost
New state of the art avionics
More cabin space for best-in-class passenger
comfort

6.  New, state-of-the-art Unmanned Aerial System (UAS) designed
for Intelligence, Surveillance and Reconnaissance (ISR) missions
 Performance and operational characteristics is at the very top
end of the UAS MALE category.
 An unmatched combination of range, wide operative speeds, fast
climb gradient, high operative ceiling and variety of payloads,
providing powerful yet flexible Defense System that outperforms
other MALE Systems.
 Suited for a wide range of ISR, Defense and Security missions,
and defines an unsurpassed mission role flexibility and sets a
new frontier of CONcept of OPerationS (CONOPS) for Defense.
 Derived from the successful Piaggio Aero P.180 Avanti II
business aircraft, the fastest twin turboprop aircraft in the world
with a proven, uneventful, service record of more than 20 years
and 800.000 flight hours.

7.  Transform a conventional, manned aircraft in an unmanned air
vehicle with a high degree of autonomy to operate beyond line of
sight
 Design a Vehicle Command & Control architecture that can be
certified against requirements that are not yet completely
defined
 Support a design road map which foresees growing
functionalities to support different operational roles
 Do the job with a strictly controlled number of experts to limit
the management overhead
 Collect the requirements from cabling diagrams, operators’ and
pilots’ experience, flight manuals
 Last but not least the task had to be completed, at least for the
prototype phase, within a very short time frame

8.  Vehicle Control and Management System (VCMS)
◦ The brain, most critical system, of the air vehicle
◦ Implement all the functions required for platform management in a
powered version of the Flight Control System
 Partitioning techniques
◦ Segregated environment where software applications of each function to
run without interfering each other, to avoid propagation of failures
 Model Based methodology
◦ Allow the system engineers to model each function autonomously
◦ Check function behavior on a host computer before using the real
hardware
 Automatically generate source code from the functions’ models
◦ Minimize the effort required to verify that the source code corresponds to
the system model
 Given these assumptions, SCADE looked like the perfect solution

9. Actuation Engines
Remote Interface Units
Flight Control Computer
(IMA Platform)
Sensors

10.  The P1HH VCMS manages:
◦ The Flight Control System
◦ The Propulsion System
◦ The Electrical Power Generation & Distribution System
◦ The Landing Gear System
◦ The Braking System
◦ The Ice detection/Ice protection System
◦ The Navigation System
◦ The Communication System
 Achieved by providing an Integrated Flight Management
System which coordinates all the above systems
 Furthermore the VCMS provides
◦ A Health Management System which monitor all the functions
◦ In case of failure, reconfigure the whole system to limit
performance degradation

11.  VCMS aircraft major functions are:
◦ Flight Management System
◦ Flight Functions
◦ Engine Management
◦ Ground Functions
◦ Navigation
 VCMS is an Integrated Modular Avionics System.
◦ An IMA applicaton is implemented for each aircraft function
◦ Each major function contains more minor functions: e.g.
Engine Management contains Engine Logics, Fire Detection
and Fuel Management
◦ Each minor function is defined using SCADE

12.  All P1HH VCMS functions have to be implemented from
scratch
 P1HH is a huge UAV: Safety Level will be DAL B at least, DAL A
for the most critical functions
 P1HH program schedule is very aggressive, therefore it is
necessary to speed up the information flow from System to
Software engineers. Fast prototyping is required for the
prototype phase.
 Software verification and validation activities take a lot of
time. This time has to be reduced
 System integration and validation activities time on rig and
aircraft has to be reduced using simulation

13.  A new process, had to be put in place. High level requirements were
available in different formats:
◦ As Operational Requirements (Textual), where the system
Engineers were collecting all the informations – functions,
interfaces, redundancy – required for each function
◦ As Operational Manuals (Textual), when instructions to operate
the aircraft were inherited from the P.180 (e.g. Pilot Operational
Handbook)
◦ As Matlab/Simulink models for Control Laws
 The first step was to implement SCADE models based on functional
requirements from the above documentation:
◦ Manually for textual requirements (done directly by system
engineers)
◦ (almost) Automatically via the Simulink Gateway
 The SCADE models were used directly to generate, by KCG, the
source code which runs on the target computer

14. A/C SPECs or Pilot Procedures
VCMS Funct. X
FRD
(Simulink)
Sub System X
Operational
Requirements
Sub System Y
Operational
Requirement
…
…
VCMS Funct. Y
FRD
Spec. Model
(SCADE)
VCMS Funct. X
FRD
Spec. Model
(SCADE)
APPLICATION
VCMS Funct.
X
Src Code
VCMS Funct.
Y
Src Code
…
Glue Code
SCADE KCG SCADE KCG
P1HH Development Process
VCMS Funct. Z
HLR
Natural Language
Sub System Z
Operational
Requirements
VCMS Funct. Z
LLR
Natural Language
DEVELOPER
VCMS Funct.
Z
Src Code
…
…

15.  Test vectors were generated for each model. For
models derived from Simulink models, test
vectors have been translated from Simulink test
vectors.
 Test vectors were run to validate the SCADE
Model by SCADE LifeCycle QTE (Qualified Test
Environment)
 Model coverage has been checked using SCADE
Suite MTC (Model Test Coverage)
 Test vectors have been translated in the target
computer executable code to check each
application on the real hardware

16. Sub System
Operational
Requirement
Simulink
Test
Vectors
Simulink
Model
SCADE
Simulink
Gateway
Translated
SCADE Model
Test Vectors
Translation
SCADE Input
Scenario/
Expected Results
QTE
Model Validation
Test Results
Goal : To be confident that
the Translated SCADE Model
has the same functional
behavior of the input
Simulink Model

17. Sub System
Operational
Requirement &
Simulink Models
VCMS Funct.
FRD
Spec. Model (SCADE) SCADE
Input Scenario
Test Results
DOORS Environment
Links from Test cases to
Operational Reqs
Test Cases
QTE
SCADE RM GATEWAY
SCADE Semantic
Checker
SCADE model validation Process

18.  Verification activities described in the
previous slide exponentially increase
◦ As the number of inputs of each model grows
◦ As when more than one model is involved
 The management of all the test vectors, in
terms of generation, validation and
configuration, was quickly becoming an issue
 The solution was found in the usage SCADE
LifeCycle QTE, still under test, which
automates the verification of test results.

19.  The project schedule did not allow, for the prototype
phase, to perform all required DO-178 verification
 At the same time some steps can be automated due to the
usage of SCADE
 One of the tasks that had to be performed anyway to prove
the robustness of the software implementation was the
structural coverage.
 MTC to analytically verify the structural coverage that the
functional test performed by the test vectors.
 Results gathered from the MTC tool were further analysed
and, when the coverage was not deemed satisfactory,
additional tests were designed and performed to provide
more coverage

20. SCADE
Model
QTE Input
QTE (MTC)
Model Coverage
Report
Goal:
To measure the
Model Coverage
achieved by the
developed set of test
cases in order to
fullfil the DO-178B

21.  Test cases are formalized in DOORS
environment. For each test case are defined
◦ Test steps
◦ Test case expected results
 SCADE LifeCycle QTE input are generated, for
each test case starting from Test steps and
Test cases expected results.

22. IMA Platform
SCADE
Auto-code
SCADE
Input scenario
Test Results
APPLICATION
executable code TEST APPLICATION
SCADE
Expected Results
Integrated
Exp.Res. 1
SCADE model autocode validation
on IMA platform
Integrated
Test Vect. 1
VCMS Funct
Executable
Code
SCADE
Input scenario
translation
SCADE
Expected results
translation
Source Code
integration activities
Glue code

23.  Models of the different functions have been progressively
put together on host; this allowed to build a sort of virtual
VCMS to check the correct integration of the applications
well in advance with respect to System Integration.
 Once System Integration took place, data from the real
world was used and fed into the test vectors to further
verify the models
 These verification activities allowed to identify and solve
the great majority of the design problems even before
performing System Integration. Thus, problems found
during System Integration have been a very limited
number and all of them are due to hardware interfaces
(impedance adaptation, actuation delays etc).

24. System Integration Modeling -Virtual VCMS
BRK
FCS
CL
EL
FML
Interfaces
Models interactions
Ground Functions
Flight Management System
Engine Management
Navigation

25. Application source code produced ~ 125000 SLOC
Percentage of autogenerated SLOC 86%
Development time ~ 5 working months
Size of System Engineering team (peak) 10 engineers
Size of System Engineering team (average) 4 engineers
Size of SW development team 9 engineers
Number of test cases managed by QTE ~ 400
Average decision coverage obtained 95%

26.  P1HH Demo Low Speed Taxi has been performed in February 2013
 P1HH Demo First Flight has been performed on August 8th, 2013
 P1HH prototype first flight is planned by the first quarter of 2014
 P1HH configuration will grow through incremental software releases,
each one adding new functionalities
 Achievement of the P1HH full configuration is planned by 2015

27.  Improve automatization of executable code
validation on the target computer
 Use SCADE System for VCMS system modeling
 Complete the ‘virtual’ model of the VCMS,
including all the computers, to allow extensive
simulation on host
 Introduction of SCADE Display to support Ground
Control Station synoptic pages development and
complete the virtual VCMS by providing the real
user interface
 Nice to have:
◦ Improved traceability interface

28.  FACE Introduction
 FACE Platform Example
 FACE Technical Specification
 SCADE Solutions for FACE

29. © 2015 ANSYS, Inc. August 7, 201529 © Esterel Technologies - An ISO 9001:2008 Certified Company - Confidential & Proprietary
Learn more on
ANSYS Systems & Embedded Software Solutions
Click Here
http://www.ansys.com/Products/Simulation+Technology/Systems+&+Embedded+Software