Aircraft Systems Integration from EMBRAER Perspective. João Paulo Marques Reginato Systems Integration Manager

Transcription

1 Aircraft Systems Integration from EMBRAER Perspective João Paulo Marques Reginato Systems Integration Manager 31/August/2015

2 Main Topics - Introduction - Systems Integration evolution on EMBRAER programs - Next Steps

3 Introduction

4 Introduction 80 s 90 s 2000 s State-of-the-Art Airbus Defense Market Twin Aisle Boeing Functional Integration Glass Cockpit Growth Shared Resources Federated with Glass A/C Systems O / I O / I IMA Systems Integration Bus & Automation Growth, Weight & Volume Processes & Management No STDs Synergy Yet O / I O / I Bus Networked IMA OEM Integration (Open STD) Single Aisle Large Jets Federated Functional Integration Glass Cockpit Weight & Volume Integration Effort Growth A/C Systems Integration & Automation Lead Time & Effort for A/C Sys. Integration O / I O / I Bus Networked IMA Avionics Suite (Proprietary) Systems & Processes Evolved With Lessons Flexibility for A/C Systems Integration O / I O / I Bus Networked IMA Avionics Suite (Open STD) Medium Jets Small Jets / TPs General Aviation Architecture Customization Proprietary Tech. Poor Scalability for Lower-End Avionic Suite Scalability Affordability Functional Integration HMI Customization Proprietary Tech. Non-IMA Networked Avionics Suite (Proprietary) This chart is notional and does not refer to any industry milestones such as aircraft launch, certification or entry into service dates. It s only intended to provide a big picture of the avionics evolution.

5 Introduction Intended Aircraft Function Safety AssessmentProcess Guidelines& Methods (ARP 4761 / ED-135) Function, Failure & Safety Information System Design Information Safety Assessmentof Aircraft in CommercialService (ARP 5150 / 5151) System Development Processes ( ARP 4754A / ED - 79A Guidelinesfor Integrated Modular Avionics (DO-297/ED-124) Functional System Operation Certification Authorities focus: Safety Hardware Development Life-Cycle (DO-254 / ED-80) Software Development Life-Cycle (DO-178C/ED-12C) Development Phase In-Service/Operational Phase

6 Introduction - According to SAE ARP-4754A: The current trend in system design is an increasing level of integration between aircraft functions and the systems that implement them. While there can be considerable value gained when integrating systems with other systems, the increased complexity yields increased possibilities for errors, particularly with functions that are performed jointly across multiple systems. Aircraft/System integration is the task of ensuring all the aircraft systems operate correctly individually and together as installed on the aircraft. This provides the means to show that intersystem requirements, taken as a group, have been satisfied. It also provides an opportunity to discover and eliminate undesired unintended functions.

7 Introduction Systems Engineering Process FUNCTIONAL ANALYSIS REQUIREMENTS ANALYSIS DESIGN AIRCRAFT LEVEL AIRCRAFT LEVEL AIRCRAFT LEVEL Customer Requirements AIRCRAFT FUNCTIONS AIRCRAFT REQUIREMENTS DESIGN (BASIC ARCHITECTURE) AIRCRAFT LEVEL SUB-SYSTEM FUNCTIONS SUB-SYSTEM REQUIREMENTS SUB-SYSTEM DESIGN SUB-SYSTEM LEVEL Source: Jackson 1997

8 Systems Integration evolution on EMBRAER programs

9 Evolution EMBRAER Civilian Programs Number of embedded systems that uses software EMB 120 EMB 145 EMB 170/190 EMB-500 EMB-505 EMB-550

10 Evolution The information presented during ICAS Workshop is confidential and cannot be reproduced.

11 Next Steps

12 Next Steps CyberSecurity

13 Next Steps CyberSecurity QAR CSD EFB File Server Cockpi t EFB Ethernet switch Wireles s Bridge Airline Network A664 switch Pres sctrl Tem p Ctrl Maintenanc e GSE Manufactur er Network

14 Next Steps Model-based systems engineering (MBSE) is the formalized application of modelling to support system requirements, design, analysis, verification and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases (INCOSE-TP , Version 2.03, September 2007).

15 Next Steps STAMP - Systems-Theoretic Accident Model and Processes STAMP is a new accident causality model based on systems theory and systems thinking described in Nancy Leveson s new book Engineering a Safer World. STAMP accounts for the new causal factors associated with software, human-decision making, new technology, social and organizational design, and increasing complexity. (

16 Summary - Introduction - Systems Integration evolution on EMBRAER programs - Next Steps

17

18 João Paulo Marques Reginato Questions? ESTAS INFORMAÇÕES SÃO PROPRIEDADE DA EMBRAER E NÃO PODEM SER USADAS OU REPRODUZIDAS SEM AUTORIZAÇÃO POR ESCRITO.