Browse Topic: Integrated modular avionics

Items (85)
Find
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 0 OVERVIEW OF ARINC 653ARINC653P0-3 (Current)11/15/2021
This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Part 0 has been adjusted to reflect technical changes made in Supplements to Parts 1 through 5 in conjunction with the technical changes made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 – Overview of ARINC 653 Part 1 – Required Services Part 2 – Extended Services Part 3A – Conformity Test Specification for ARINC 653 Required Services Part 3B – Conformity Test Specification for ARINC 653 Extended Services Part 4 – Subset Services Part 5 – Core Software Recommended Capabilities The term “this document” refers to Part 0 only, while the term “ARINC 653” or “the Specification” refers to the whole set of ARINC 653 documents, currently Parts 0 to 5. The primary objective of ARINC 653 is to define a general-purpose APplication/EXecutive (APEX) interface (API = Application Program Interface) between the Core Software (CSW) of an Avionics Computer Resource (ACR) and the application software. Included within ARINC 653 are the interface requirements between the application software and the CSW and the list of services which allow the application software to control the scheduling, communication, and status information of its internal processing elements.
Airlines Electronic Engineering Committee
Mathematical Programming for Optimization of Integrated Modular Avionics2021-01-00093/2/2021
Every state-of-art aircraft has a complex distributed systems of avionics Line Replaceable Units/Modules (LRUs/LRMs), networked by several Data buses. These LRUs are becoming more complex because of an increasing number of new functions need to be integrated into avionics architecture. Moreover, the complexity of the overall avionics architecture and its impact on cable length, weight, power consumption, reliability and maintainability of avionics systems encouraged manufacturers to incorporate efficient avionics architectures in their aircraft design process. The evolution of avionics data buses and architectures have moved from distributed analog and federated architecture to digital integrated modular avionics (IMA). IMA architecture allows suppliers to develop their own LRUs/LRMs capable of specific features that can then be offered to Original Equipment Manufacturers (OEMs) as Commercial-Off-The-Shelf (COTS) products. In the meantime, the aerospace industry has been investigating new solutions to develop smaller, lighter, and more capable LRUs/LRMs to be integrated into avionics architecture. However, manual design cannot concurrently fulfil the complexity and interconnectivity of system requirements and optimality. Thus, developing computer-aided design (CAD), Model Based System Engineering (MBSE) tools and mathematical modelling for optimization of IMA architecture has become an active research area in avionics systems integration. In this paper, a general method and tool are developed for optimization of avionics architecture and improving its operational capability. The tool has three main parts including a database of avionics LRUs, mathematical modelling of the architecture and optimization algorithms. Finally, the tool provides a semi-automatic optimization of avionics architecture which helps avionics system architects to investigate and evaluate various architectures in the early stage of design from an LRU perspective. It can also be used to upgrade a legacy avionics architecture.
Radaei, Mohammad
It is Time for Army Aviation to Move to a Development Assurance Approach for Including Open Integrated Modular AvionicsF-0076-2020-1642910/5/2020
In the early days of quality management, prior to 1980s, the focus seemed to be on "Quality Control" or "Quality Assurance". Emphasis was placed on inspection and testing. Quality was about conformance to specification. Non-Conformance Reports were representative of quality control. Our understanding of quality management has evolved, largely based on the Toyota Quality and Concurrent Engineering Approach of moving it off the production line for Integrated Product and Process Development (IPPD) [1]. In the late 1980s industry experienced similar difficulties in understanding and adopting quality management. The ideas behind managing quality are quite abstract. Quality is primarily about understanding and satisfying a customer's expectations. This includes implicit expectations, as well as explicit expectations. The techniques of specification, inspection and testing only make sense in that wider context. Formal risk management was developed in the late 1980s and throughout the 1990s. Risk management principles are now widely understood and applied. Functional Safety Management (FSM) simply applies quality management to systems that are designed to control risk. [2] The standards for FSM and Development Assurance (DA) are relatively new. SAE ARP 4754 and ARP 4761 for complex aircraft systems were introduced in 1996 and DO-178 for software in 1998. In 2010 ARP 4754A [3] was created for movement from federated avionics systems to distributed integrated avionics systems which set the stage for Integrated Modular Avionics (IMA) in DO 297 [4]. The Army identified IMA as a critical technology in its Joint Common Architecture (JCA) Final Report [5] and is seeking to provide a Modular Open Systems Architecture (MOSA) approach to its Future Vertical Lift (FVL) programs. [6] The aim is to build and upgrade FVL mission systems without expensive proprietary interfaces. New capabilities from a choice of developers will adapt to emerging threats. The mission system architecture demonstration (MSAD) Program has awarded six contracts to avionics vendors to develop MOSA tools and rules. A capstone demonstration wraps-up this December 2020 and will generate a final report and provide guidance for Future Attack and Reconnaissance Aircraft (FARA), FLRAA and FUAS architectures. MOSA flexibility and economy come to legacy helicopters with the Aviation Mission Common Server (AMCS), which transitions the legacy fleet from single-purpose/single-vendor architectures to more adaptable modules and components. Nonproprietary, government-controlled, open system standards interface new software applications without going to each platform maker for integration. [6] This paper will review FSM, DA, and Open IMA in these civil aircraft standards, compare them with Army Aviation's current Army Military Airworthiness Certification Criteria (AMACC) [7] and recommend a Civil Military FSM DA Framework for FVL and on how AMACC could be modified for FVL Open Systems Architectures (OSA) Certification using a Modular Open Systems Approach (MOSA). [8]
Daniel, Dr., Lewis, Dr.
An Approach to Verification of Interference Concerns for Multicore Systems (CAST-32A)2020-01-00163/10/2020
The avionics industry is moving towards the use of multicore systems to meet the demands of modern avionics applications. In multicore systems, interference can affect execution timing behavior, including worst case execution time (WCET), as identified in the FAA CAST-32A position paper. Examining and verifying the effects of interference is critical in the production of safety-critical avionics software for multicore architectures. Multicore processor hardware along with aerospace RTOS providers increasingly offers robust partitioning technologies to help developers mitigate the effects of interference. These technologies enable the partitioning of cores for different applications at different criticalities and make it possible to run multiple applications on one specific core. When incorporated into system-design considerations, these partitioning mechanisms can be used to reduce the effects of interference on software performance. In this paper we describe a novel approach to verifying the effectiveness of RTOS interference mitigation on the final hosted software. We showcase the use of the proposed approach on the NXP T2080 multicore board. The approach follows a V-model based methodology in which high- and low-level requirements for the analysis are defined before designing and implementing tests and producing verification results using the Rapita Verification Suite. Tests are supported by multicore interference generators called RapiDaemons that create a configurable degree of contention on shared resources. This provides an assessment of the robustness of the system by identifying and quantifying any remaining interference on the partitioned system, thus demonstrating that interference is bounded and thereby providing evidence of WCET to certification authorities. The presented results confirm the effectiveness of our proposed approach to independent verification of multicore interference mitigation.
VanderLeest, Steven H., Evripidou, Christos
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 2 EXTENDED SERVICESARINC653P2-4 (Current)12/23/2019
As avionics software continues to evolve, so does ARINC Specification 653. ARINC 653 Part 2 specifies extensions (i.e., optional services) to the required Application Program Interfaces (APIs) described in ARINC 653 Part 1. Supplement 4 adds optional multicore services capabilities.
Airlines Electronic Engineering Committee
The Research on Validation and Verification Method of Configuration Data for IMA Resources Allocation2019-01-18509/16/2019
Integrated Modular Avionics (IMA) system comprises IMA platform and hosted applications. The IMA platform provides the hosted applications with shared resources, e.g. computing, memory, communication, health monitoring resources. As a bridge between them, the IMA configuration data specifies how these shared resources are allocated to each hosted application. The IMA configuration data, which is different from real hardware and software code, should be validated and verified as an important portion of IMA system. After a brief introduction of IMA system, development processes, and general means of compliance for certification, this paper proposed an Architecture Analysis and Design Language (AADL) model of IMA configuration based on a case study of airborne datalink system. Based on the model, the IMA configuration data is abstracted and categorized into several types, with the correspondent means of compliance identified for each type. Furthermore, the associated roles and responsibilities are discussed for IMA configuration data validation and verification. The IMA configuration data specific means of compliance, the validation and verification processes, the roles and responsibilities, together form a method for validating and verifying the IMA configuration data for shared resources allocation, which can be applied to all partitioning systems beyond avionics.
Wang, Yunsheng, Li, Yan-xiao
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 0 OVERVIEW OF ARINC 653ARINC653P0-2 (Current)8/7/2019
This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Supplements to Part 0 will be made more consistent with Parts 1 through 5 in conjunction with the technical changes expected to be made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 - Overview of ARINC 653, Part 1 - Required Services, Part 2 - Extended Services, Part 3 - Conformity Test Specification, Part 4 - Subset Services, and Part 5 - Core Software Required Capabilities. Supplement 1 reflects the introduction of multicore processor support in Parts 1 and 2.
Airlines Electronic Engineering Committee
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 5 CORE SOFTWARE RECOMMENDED CAPABILITIESARINC653P5-1 (Current)8/7/2019
Part 5 defines additional ARINC 653 core software capabilities to ease integration on a variety of Integrated Modular Avionics (IMA) hardware platforms by allowing platform suppliers to extend and customize it for use with their unique hardware platform. Supplement 1 expands the guidance provided on resource profiling and execution profiling pertinent to the use of mulicore processors in avionics.
Airlines Electronic Engineering Committee
FACE™ - Future Airborne Capability Environment19AERP06_056/1/2019
The FACE™ of Military Modernization Diminishing U.S. Combat Superiority Drives New Software Development Requirements U.S. rival countries have been rapidly modernizing their militaries, with publicized advances that pose credible challenges to U.S. supremacy in all aspects of warfare: air, land, sea, space and cyberspace. On January 19, 2018 Secretary Mattis discussed the National Defense Strategy and emphasized the need to modernize key capabilities to address these threats. He stated: “To keep pace with our times, the department will transition to a culture of performance and affordability that operates at the speed of relevance. Success does not go to the country that develops a new technology first, but rather, to the one that better integrates it and more swiftly adapts its way of fighting. Our current bureaucratic processes are insufficiently responsive to the department's needs for new equipment. We will prioritize speed of delivery, continuous adaptation and frequent modular upgrades.” Avionic systems are a case in point. They have been on an unaffordable trend due to complexity and cost, particularly in the evolution from hardwaredefined systems to modern software-defined systems, where the costs to develop, integrate, and maintain software continues to grow at an unsustainable rate. In response, The Open Group Future Airborne Capability Environment (FACE) Consortium has established an open procurement environment that facilitates reuse to meet four core goals: improve affordability, speed, agility, and excellence. The FACE™ Consortium is a government and industry partnership dedicated to accomplish this using open industry standards, advanced integration, and maintenance technologies.
The FACE™ of Military ModernizationTBMG-345286/1/2019
U.S. rival countries have been rapidly modernizing their militaries, with publicized advances that pose credible challenges to U.S. supremacy in all aspects of warfare: air, land, sea, space and cyberspace. On January 19, 2018 Secretary Mattis discussed the National Defense Strategy and emphasized the need to modernize key capabilities to address these threats. He stated: “To keep pace with our times, the department will transition to a culture of performance and affordability that operates at the speed of relevance. Success does not go to the country that develops a new technology first, but rather, to the one that better integrates it and more swiftly adapts its way of fighting. Our current bureaucratic processes are insufficiently responsive to the department's needs for new equipment. We will prioritize speed of delivery, continuous adaptation and frequent modular upgrades.”
Analyze This! Sound Static Analysis for Integration Verification of Large-Scale Automotive Software2019-01-12464/2/2019
Safety-critical embedded software has to satisfy stringent quality requirements. One such requirement, imposed by all contemporary safety standards, is that no critical run-time errors must occur. Runtime errors can be caused by undefined or unspecified behavior of the programming language; examples are buffer overflows or data races. They may cause erroneous or erratic behavior, induce system failures, and constitute security vulnerabilities. A sound static analyzer reports all such defects in the code, or proves their absence. Sound static program analysis is a verification technique recommended by ISO/FDIS 26262 for software unit verification and for the verification of software integration. In this article we propose an analysis methodology that has been implemented with the static analyzer Astrée. It supports quick turn-around times and gives highly precise whole-program results. We give an overview of the key concepts of Astrée that enable it to efficiently handle large-scale code, and describe a pre-analysis which transforms the source code to make it better amenable to static analysis. The experimental results confirm that sound static analysis can be successfully applied for integration verification of large-scale automotive software.
Kaestner, Daniel, Schmidt, Bernard, Schlund, Maximilian, Mauborgne, Laurent, Wilhelm, Stephan, Ferdinand, Christian
An Open Source Domain-Specific Avionics System Architecture Model for the Design Phase and Self-Organizing Avionics2019-01-13833/19/2019
State-of-the-art avionics systems are standardized, e.g. the computing system of the flying vehicle is composed of pre-defined and pre-qualified modules of a standardized avionics platform. Integrated Modular Avionics (IMA) is the most popular representative, but not the only one. Two challenges of standardized avionics platform are system design and configuration. Since the high numbers of functions, modules, and constraints for modern air vehicles, bringing up the optimal system architecture is a difficult job if carried out manually. The subsequent process of creating millions of configuration parameters is time consuming and error prone. Both issues are similar and are, in general, processable by algorithms. Algorithms proved to provide significant support for current system design issues and might be mandatory in future, when avionics become self-organizing and the design and configuration are derived by the platform itself. Automated design already proved its advantages and self-organizing platforms started to be in development. Having the right and rigid data format for this purpose is mandatory. A suitable data format must hold all requirements necessary to proof the validity of the avionics architecture and take reliable organization decisions. It must be independent of technologies, in terms of hardware, software, and configuration. It must have a structure simple enough to be used in qualified embedded systems. Existing modeling approaches, e.g. AADL, have different purposes as detailed system design, dynamic simulations, virtual qualification, and lack especially rigidity and simplicity. The Open Avionics Architecture Model (OAAM) is a domain-specific model representing avionics system’s architectures designed to be used offline or online in the automated organization of avionics systems. It was implemented using the EMOF modeling standard and the Eclipse Modeling Framework (EMF). It is available as open source. This article explains the structure and the purpose of OAAM.
Annighoefer, Bjoern
Experiences of Civil Certification of Multi-Core Processing Systems in Commercial and Military Avionics, Integration Activities, and Analysis2019-01-13823/19/2019
Avionics systems are currently undergoing a transition from single core processor architectures to multi-core processor architectures. This transition enables significant advantages in reduction in size, weight, power (SWaP) and cost. However, avionics hardware and software certification policies and guidance are evolving as research and experience is gained with multi-core processor architectures. The unique challenges of using multi-core processors in certified avionics will be discussed. The requirements for a virtualization platform supporting multiple real-time operating system (RTOS) partitions on a multi-core processor used in safety-critical avionics systems are defined, including the ability to support multiple design assurance levels (DAL) on multiple cores, fault isolation and containment, static configuration as per ARINC 653, role-based development as per DO-297, and robust partitioning to reduce cost of incremental certification. The paper will present a collaborative approach undertaken by a leading avionics system supplier and a leading safety-critical commercial-off-the-shelf (COTS) RTOS supplier in the development of a multi-core real-time system with DO-178C DAL A software and DO-254 DAL A hardware safety certification on an FAA Program of Record (PoR). The approach taken to comply with FAA CAST-32A objectives will be presented. Particular focus is provided for integration activities and program specific analysis performed by the IMA application developer and integrator to guarantee determinism in the deployed system. Using the approach defined under the PoR, the application developer performs activities including foot-printing under worst-case execution time (WCET) loads and application of numerical methods to predict interference effects. The IMA integrator uses this data to define a performance restricted environment (PRE) and uses WCET verification in the PRE. Tools, analysis methods, and sample results will be presented. The method to capture results is discussed. Finally the paper includes lessons learned during the program.
Tiedeman, Harold Glenn, Parkinson, Paul
SAE Architecture Analysis and Design Language (AADL) Annex Volume 2:Annex B: Data Modeling AnnexAnnex D: Behavior Model AnnexAnnex F: ARINC653 AnnexAS5506/2 (Current)2/18/2019
AS-2C Architecture Analysis and Design Language
Model-Based Systems Engineering Methodology for Implementing Networked Aircraft Control System on Integrated Modular Avionics – Environmental Control System Case Study2018-01-194310/30/2018
Integrated modular avionics (IMA) architectures host multiple federated avionics applications on a single platform and provide benefits in terms of size, weight, and power, which, however, leads to increased complexity, especially during the development process. To cope efficiently with the high level of complexity, a novel, structured development methodology is required. This paper presents a model-based systems engineering (MBSE) development approach for the so-called “distributed integrated modular architecture” (DIMA). The proposed methodology adapts the open-source Capella tool, based on the Architecture Analysis & Design Integrated Approach (ARCADIA) methodology, to implement a complete design cycle, starting with requirements captured from the aircraft level to streamline the development, culminating in the integration of an avionics application into an ARINC 653 platform. This paper shows how to address the variability of technology implementations at the aircraft and system levels and how the specification artifacts are efficiently managed and traced from the aircraft to the system to the item level to implement the SAE ARP4754A guidelines. The effectiveness of the methodology is presented via a case study of the integration of an environmental control system (ECS) into aircraft control architecture, illustrated for the cabin pressure control system (CPCS). The guidelines derived are applicable to other aircraft systems. In addition, the presented paper provides important insights into the challenges and advantages of the MBSE process over the traditional paper-based specification process.
George Mathew, Prince, Liscouet-Hanke, Susan, Le Masson, Yann
Anomaly Based Intrusion Detection for an Avionic Embedded System2018-01-194110/30/2018
This paper firstly describes the challenges raised by the introduction of Intrusion Detection Systems (IDS) in avionic systems. In particular, we discuss some specific characteristics of such systems and the advantages and limitations of signature-based and anomaly-based techniques in an avionics context. Based on this analysis, a framework is proposed to integrate a Host-based Intrusion Detection System (HIDS) in the general Integrated Modular Avionics (IMA) development process, which fits avionic systems constraints. The proposed HIDS architecture is composed of three modules: anomaly detection, attack confirmation, and alert sending. To demonstrate the efficiency of this HIDS, an attack injection module has also been developed. The overall approach is implemented on an IMA platform running a cockpit display function, to be representative of embedded avionic systems.
Damien, Alienor, Fumey, Marc, Alata, Eric, Kaâniche, Mohamed, Nicomette, Vincent
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 3A CONFORMITY TEST SPECIFICATIONS FOR ARINC 653 REQUIRED SERVICESARINC653P3A-1 (Current)9/7/2018
ARINC 653, Part 3A is the Compliance Test Specification for ARINC 653 Required Services presently defined in ARINC 653 Part 1. The document specifies a set of stimuli and the expected responses. Future work on the ARINC 653 document set includes an effort to define Operating System services for multi-core processor environments. The Compliance Test Specification is expected to be updated in step with ARINC 653, Part 1.
Airlines Electronic Engineering Committee
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 3B CONFORMITY TEST SPECIFICATIONS FOR ARINC 653 EXTENDED SERVICESARINC653P3B (Current)9/7/2018
ARINC 653, Part 3B is the Compliance Test Specification for ARINC 653 Extended Services presently defined in ARINC 653 Part 2. The document specifies a set of stimuli and the expected responses. Future work on the ARINC 653 document set includes an effort to define Operating System services for multi-core processor environments. The Compliance Test Specification is expected to be updated in step with ARINC 653, Part 2.
Airlines Electronic Engineering Committee
ADVANCED FLIGHT MANAGEMENT COMPUTER SYSTEMARINC702A-5 (Current)8/28/2018
The Advanced FMCS provides expanded functions beyond that defined in ARINC 702 to support the anticipated requirements for operation in the CNS/ATM operating environment. GNSS and RNP based navigation, air-to-ground data link for communications and surveillance, and the associated crew interface control/display definitions are included. The NextGen/SESAR concepts and their relative effects on the FMS are addressed in this document. The functional requirements also apply to a Flight Management Function (FMF) in an Integrated Modular Avionics (IMA) architecture with software partitions.
Airlines Electronic Engineering Committee
In-Flight Real-Time Avionics AdaptationTBMG-327348/1/2018
Avionics is a very restricting domain for obvious safety reasons. Along with miniaturization comes the idea of integration. More functionality on one spot requires a good management of privacy and congestion on shared platforms. This is why determinism is one of the keywords of avionics works. This led to protocols like ARINC653[1] assuring that multitask embedded programs respect a predictable policy applied by the operating system (OS). Another key protocol is ARINC664, which guarantees that multiple communicating systems efficiently share the network. These two protocols are pillars of the Integrated Modular Architecture (IMA) concept[2].
Affordable Vehicle Avionics (AVA)TBMG-290386/1/2018
NASA Ames Research Center has developed a novel, low-cost, self-contained guidance system for small payload operators. Small satellites are becoming ever more capable of performing valuable missions for both government and commercial customers; however, currently these satellites can only be launched affordably as secondary payloads, which makes it difficult for the small satellite mission to launch when needed, to the desired orbit, and with acceptable risk.
General Requirements for WDM Backbone NetworksAIR6005 (Current)1/23/2018
This document (AIR6005) provides the framework for the specifications of a WDM OBN within the SAE AS5659 WDM LAN Specification document family, in particular, the Transparent Optical Backbone Network Specification. This framework includes potential requirements, technical background, investigation and context to support the writing of SAE’s WDM LAN specifications documents. The SAE’s AS6005 WDM OBN document describes a transparent optical network which contains optical components and optical interfaces to perform optical transport, optical add/drop, optical amplification, optical routing, and optical switching functions. The conforming optical signal interfaces for the data plane of the WDM OBN are defined. The conforming signal interfaces for the control and management planes of this network are also defined. The control and management plane signals may be either electrical or optical. If successful, a WDM LAN standard is anticipated to include multiple variants that may get created either as separate documents (e.g. a multimode and single-mode specification) and additional documents may be needed to specify the components from which a WDM LAN and OBN will be built. The WDM OBN specification is to be established in a future document, SAE AS5659. This AIR document is a requirements document that provides input regarding the WDM OBN to the AS5659 Aerospace Standard. Additional documents are anticipated to specify aggregation of access for multiple systems that interface to the OBN. The transition from electrical communications links to optically multiplexed networks, is anticipated to involve aggregation of slower speed signals as necessary part of a cost effective transition.
AS-3 Fiber Optics and Applied Photonics Committee
Guide to Civil Aircraft Electromagnetic Compatibility (EMC)ARP60493 (Current)10/25/2017
This guide provides detailed information, guidance, and methods for demonstrating electromagnetic compatibility (EMC) on civil aircraft. This guide addresses aircraft EMC compliance for safety and functional performance of installed electrical and electronic systems. The EMC guidance considers conducted and radiated electromagnetic emissions and transients generated by the installed electrical and electronic systems which may affect other installed electrical and electronic systems on the aircraft. Application of appropriate electrical and electronic equipment EMC requirements are discussed. Methods for aircraft EMC tests and analysis are described. This guide does not address aircraft compatibility with the internal electromagnetic environments of portable electronic devices (PED) or with the external electromagnetic environments, such as high-intensity radiated fields (HIRF), lightning, and precipitation static.
AE-4 Electromagnetic Compatibility (EMC) Committee
In Flight Real-Time Adaptation2017-01-21699/19/2017
Avionics is one kind of domain where prevention prevails. Nonetheless fails occur. Sometimes due to pilot misreacting, flooded in information. Sometimes information itself would be better verified than trusted. To avoid some kind of failure, it has been thought to add an new kind of embedded monitoring that enable adaptation.
Granado, Bertrand, Gatti, Marc, Denoulet PhD, Julien, Rayrole, Martin
A Proposed Byzantine Fault-Tolerant Voting Architecture using Time-Triggered Ethernet2017-01-21119/19/2017
Over the last couple decades, there has been a growing interest in incorporating commercial off-the-shelf (COTS) technologies and open standards in the design of human-rated spacecraft. This approach is intended to reduce development and upgrade costs, lower the need for new design work, eliminate reliance on individual suppliers, and minimize schedule risk. However, it has not traditionally been possible for COTS solutions to meet the high reliability and fault tolerance requirements of systems implementing critical spacecraft functions. Byzantine faults are considered particularly dangerous to such systems because of their ability to escape traditional means of fault containment and disrupt consensus between system components. In this paper, we discuss the design of a voting protocol using Time-Triggered Ethernet capable of achieving data integrity in the presence of a single Byzantine fault. Moreover, we explore how this capability can be combined with an exact-match voting strategy to realize a fault-tolerant computer system that can be used with different COTS processor boards, operating systems, and software frameworks.
Loveless, Andrew, Fidi, Christian, Wernitznigg, Stefan
Optimizing the Benefit of Virtual Testing with a Process-Oriented Approach2017-01-21149/19/2017
In the aerospace industry, methods for virtual testing cover an increasing range of test executions carried out during the development and test process of avionics systems. Over the last years, most companies have focused on questions regarding the evaluation and implementation of methods for virtual testing. However, it has become more and more important to seamlessly integrate virtual testing into the overall development process. For instance, a company’s test strategy might stipulate a combination of different methods, such as SIL and HIL simulation, in order to benefit from the advantages of both in the same test process. In this case, efforts concentrate on the optimization of the overall process, from test specification to test execution, as well as the test result evaluation and its alignment with methods for virtual testing. Furthermore, software tools have to be suitable for virtual testing and the entire tool chain has to be adaptable so it can be used for different test methods for various applications that have different users. This paper introduces an exemplary validation and verification process according to ARP4754A and describes how virtual testing contributes to a more efficient overall development process. The ARINC 653 software architecture serves as an example for demonstrating the benefits of using different virtual test environments. In order to coordinate and manage the design, implementation and test process, all test and simulation data is stored centrally using a data and test management tool that reduces complexity for an improved overview. Examples from real projects will illustrate this process-oriented approach.
Stavesand, Jann-Eve, Reglitz, Sören, Himmler, Andreas
Open Ethernet-Based Embedded Platforms for Integrated Modular Architectures and Autonomous SystemsF-0073-2017-120345/9/2017
ABSTRACT By adopting the latest developments from other critical (e.g. integrated modular avionics) and high-volume automotive industries with safety requirements (ADAS and autonomous driving), the rotorcraft industry could reduce system lifecycle costs and gain new integrated platform capabilities which support incremental modernization, simplify upgrades and modifications for different missions or rotorcraft platforms. A specific set of architecture design patterns and computational models, used in integrated modular architectures, enables the design of less complex integrated systems which can collect and process all system sensor data in (hard) real-time, supports seamless sensor data fusion for IVHM, and enables the integration of critical and non-critical functions. Accompanied with robust system engineering, RTCA DO-254 / DO-178C DAL A/B design assurance and extended use of ASIL-D-compliant (automotive) components, novel integrated architectures for rotorcraft can be designed to fit with robust modular form factors such as VPX. Such integrated architectures can be extended with COTS computing and sensor fusion LRUs/ECUs used for automotive ADAS/ADS (advanced driver assistance systems/autonomous driver systems) and rapidly progressing autonomous driving applications.
Jakovljevic, Mirko, Soares, Alvaro
Model Based Engineering for Advanced Integrated Modular Avionics - Focus and ChallengesF-0073-2017-120315/9/2017
ABSTRACT Advanced Integrated Modular Avionics (A-IMA) will drive new focus and challenges for Model Based Engineering (MBE). First, there is the need to bridge MBE to legacy system elements that were developed without MBE along with the need to handle hybrid Open System Architecture / Integrated Modular Avionics (OSA/IMA) based architectures. Second, there is the need for MBE to be reusable and interoperable across product development cycles as technology insertions occur. Third, there is the need for integration of MBE into synthesizable descriptions that can also be effectively validated for mixed general purpose, safety, and secure computing and networking environments. Fourth is the need for effective application of MBE in hybrid waterfall and agile development environments where target infrastructure is scalable in capability and cost. Fifth is the need for MBE to support partitioned roles across companies, government, and universities where one entity does requirements, one does architecture, one develops components, one provides formal test, and another provides system sustainment. There are a number of industry and university efforts underway to address these focus items and challenges spread across these adjacent MBE complex system domains. This paper is focused on the current state of each of these areas relative to use in A-IMA systems based on industry initiatives and academic research. It uses the driverless car for comparison as an emerging "Advanced Integrated Modular Architecture" and identifies its parallel approaches to address these focused items and challenges. This work is being built on the authors' work exploring dual use technologies being developed for the driverless car domain that will lead to a market of 10 Million autonomous cars operating in 2020. Previous papers have addressed identification of potential advanced automotive dual use transformational hardware and software technologies including many core processing, advanced software autonomy and data fusion components, unified mixed criticality networking, and integrated cyber security for A-IMA. A testbed has also been recently proposed as a mechanism to evaluate these dual use technologies in an A-IMA context. This paper extends the dual use view to include understanding of the best-of-breed avionics MBE environment and how it can be complementary to leveraging a testbed environment in addressing affordable, scalable, and open solutions.
Gaska, Thomas, Summerville, Doug, Gaska, Marilyn, Chen, Yu
Evaluating Key Certification Aspects of Multicore Platforms for Safety Critical Avionics ApplicationsTBMG-264382/1/2017
High performance, low power consumption and small footprint requirements imposed by the embedded market on the processor industry is causing a definite move away from single-core processors to multicore processors. Multicore processors have been deemed as the future of Size, Weight, and Power (SWaP) constrained applications like military and avionics. They provide higher performance (MHz/W) at lower power. They also allow consolidation of multiple functions/ applications onto a single platform.
Evaluating Key Certification Aspects of Multicore Platforms for Safety Critical Avionics Applications17AERP02_032/1/2017
High performance, low power consumption and small footprint requirements imposed by the embedded market on the processor industry is causing a definite move away from single-core processors to multicore processors. Multicore processors have been deemed as the future of Size, Weight, and Power (SWaP) constrained applications like military and avionics. They provide higher performance (MHz/W) at lower power. They also allow consolidation of multiple functions/applications onto a single platform.
Embedded Real-Time Monitoring Using SystemC in IMA Network2016-01-20699/20/2016
Avionics is one kind of domain where prevention prevails. Nonetheless failures occur, sometimes due to pilot misreacting, flooded in information. Sometimes information itself would be better verified than trusted. To avoid some kind of failure, it has been thought to add,in midst of the ARINC664 aircraft data network, a new kind of monitoring.
Aloui, Zied, Ahamada, Nawfal, Denoulet, Julien, Rayrole, Martin, Pierre, Francine, Gatti, Marc
Integration and Performances Analysis of a Data Distribution Service Middleware in Avionics2015-01-25549/15/2015
The amount of functionalities in modern aircrafts is increasing to satisfy performance, safety and economic benefits. Therefore, the communication needs of avionic systems are growing. Furthermore, the portability and reusability of applications are current challenges of the aerospace industry. The use of the Data Distribution Service (DDS) middleware technology would reduce the complexity of communications and ease the portability and reusability of applications with its standardised interface. Few previous works used a DDS middleware within the aerospace industry and those didn't take into account the impact of this technology on the applications performances. Therefore, this paper presents an impact evaluation of using a DDS middleware on the performances of avionic applications. To do so, a design methodology was proposed to design an automatic flight control system (AFCS) from a high abstraction level representation of a control loop to a low-level implementation on a development board. The AFCS was modeled with Simulink® to control a Boeing 747-400 simulated within the X-Plane flight simulator. The AFCS code was then ported on a Freescale 8572 embedded platform running VxWorks operating system to allow hardware-in-the-loop (HIL) testing. The performances of the AFCS were evaluated through the stabilisation of the aircraft's altitude, speed and roll angle. To measure the impact of using a DDS middleware, the performances of the AFCS with and without a DDS middleware were compared. The results shows that using a DDS middleware allows the aircraft to stabilise at the desired altitude, speed and roll angle without having any significant impact on the performances of the AFCS. However, due to the limitations of this paper's works, there is still much to do before using a DDS middleware in an actual aircraft becomes a common practice.
Landry, Kevin, Boland, Jean-François, Bois, Guy
Deterministic Ethernet VPX 3U/6U Switches for Open Integrated Architectures2015-01-25229/15/2015
VPX, as a switched fabric, supports the design of advanced integrated systems using technologies such as deterministic Ethernet. Deterministic Ethernet can be used in backplane and backbone applications. In cases where functional interrelationships and Ethernet network bandwidth sharing is deterministic and all logical links among critical function have configurable quality of service with guaranteed timing, the complexity challenges in design of advanced integrated architectures can be much simpler to handle and mitigate. VPX switches in 3/6U format with ARINC664 and SAE AS6802 services enable deterministic integration of many critical functions hosted on common embedded computing and networking resources. Both ARINC664 (asynchronous real-time) and SAE AS6802 (synchronous hard real-time), as Layer 2 enhancements, do not affect existing Ethernet services. They are compliant with all standard Ethernet physical layers for backbone and backplane networks, including those described in VPX (VITA 46) and VITA 48. They are also compliant with higher OSI Layers 3-6, and can be easily used in design of open and generic integrated architectures using VPX standards. This enables the design of truly open and flexible modular embedded systems, which can host hard real-time, real-time, and soft-time functions. Incremental modernization is fully supported, and new functions can be added without influencing already integrated capabilities.
Jakovljevic, Mirko, Radke, Jan, Rucker, Perry
Evaluation of Key Certification Aspects of Multi Core Platforms for Safety Critical Applications in Avionics Industry2015-01-25249/15/2015
Multi core platforms offer high performance at low power and have been deemed as future of size, weight and power constrained applications like avionics safety critical applications. Multi core platforms are widely used in non-real time systems where the average case performance is desired like in consumer electronics, telecom domains. Despite these advantages, multi core platforms (hardware and software) pose significant certification challenges for safety critical applications and hence there has been limited usage in avionics and other safety critical applications. Many multicore platform solutions which can be certified to DO-254 & DO 178B Level A are commercially available. There is a need to evaluate these platforms w.r.t certification requirements before deploying them in the safety critical systems thereby reducing the program risks. This paper discusses the advantages of multi core platforms in terms of performance, power consumption and weight/size. Certification challenges in providing the evidence for robust partitioning in space and time, inter-partition/ inter-core communication, Worst Case Execution Time (WCET) estimation, Fault containment, Error detection and handling are discussed. This paper aims to identify key aspects (e.g. interconnect architecture, scheduling policy) and measures of performance (e.g. ratio of ACET to WCET), which needs to be analyzed for a given platform and strategies to evaluate the same are presented. Process of evaluation could provide required insights which will aid system architects and platform designers to identify potential safety challenges and develop mitigation techniques and incorporate safety mechanisms into systems architecture and platform design. Evaluation results could be used as guidance for selection of multi-core platform for use in safety critical applications.
Gampa, Srikanth
An Adaptive Software Architecture for Future CMS2015-01-25459/15/2015
Aircraft cabin systems, especially cabin management systems (CMS) have to cope with frequent cabin changes during their lifecycle. This includes not only layout rearrangements and technological upgrades during the service, but also extensive CMS customizations and product variations before aircraft delivery. Therefore it is inevitable for the CMS to be highly changeable and offer an easy and agile change process. Today's CMS solutions face this challenge with configurable system architectures. Although such architectures offer a vast change domain, they usually come with time consuming and error prone change processes. This paper introduces an adaptive avionics software architecture that enables the CMS to cope with cabin changes highly automatically and with minimal human interactions. The adaptation is performed during an on ground organization phase, in which system changes are detected and evaluated by the CMS itself. Consequently the CMS instantiates and adapts the software within hardware modules and establishes the system overall communication. The concept of adaptive CMS is based on an open service oriented software architecture with built in services, which abstract the communication, redundancy, fault-tolerance and the supervision of the system operation modes during the life-cycle. The software architecture contains also organization services, which enable the CMS to detect the system changes and adapt itself accordingly.
Ahmadi, Reza, Marquardt, Oliver, Riedlinger, Marc, Reichel, Reinhard
Model-based Method to Automate the Design of IMA Avionics System Based on Cosimulation2015-01-25319/15/2015
In the aerospace industry, as the modern avionics systems became more and more complex, the Integrated Modular Avionics (IMA) architecture has been proposed as a replacement of the federated architecture, in order to offer better solutions on SWaP constraints (Size, Weigh and Power). However, the development process of IMA avionics systems is much more difficult. This paper aims to propose to the aerospace industry a set of time-effective and cost-effective solutions for the integration and functional validation of IMA systems. Based on MBE methodology, which is considered as an interesting solution for the IMA systems development [8], this paper proposes a design flow, that integrates three steps of refinement, for the configuration and the validation of IMA platforms. In the first step of the design flow, the modeling language AADL is used to describe the IMA architecture. The AADL modeling environment OCARINA, a code generator initially designed for the real-time operating system POK, has been modified to generate software integration code and system configuration files for the IMA simulator named SIMA. This solution is a cost effective alternative to expensive commercial development environments to validate ARINC653 software applications. In the second step of the design flow, a cosimulation platform composed of two simulators is proposed: Simulink for the simulation of peripherals and SIMA for the simulation of IMA modules. In the third step, the validated avionics applications and system configuration can be ported with minimum effort from the cosimulation environment to an implementation platform. A case study, which consists in integrating several avionics applications to SIMA and then porting them to PikeOS development environment, was brought in the purpose of demonstrating the proposed design flows and co-simulation platform. The research work realized in this paper is a part of collaboration between industrials and academics through the CRIAQ AVIO509 project.
Bao, Lin, Bois, Guy, Boland, Jean-François, Savard, Julien
AVIONCS APPLICATION SOFTWARE STANDARD INTERFACE PART 2 EXTENDED SERVICESARINC653P2-3 (Current)8/21/2015
As avionics software continues to evolve, so does ARINC Specification 653. ARINC 653 Part 2 specifies extensions (i.e., optional services) to the required Application Program Interfaces (APIs) described in ARINC 653 Part 1. Supplement 3 adds optional multicore services capabilities.
Airlines Electronic Engineering Committee
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 0 OVERVIEW OF ARINC 653ARINC653P0-1 (Current)8/3/2015
This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Supplements to Parts 1 through 5 will be made more consistent with Part 0 in conjunction with the technical changes expected to be made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 - Overview of ARINC 653, Part 1 - Required Services, Part 2 - Extended Services, Part 3 - Conformity Test Specification, Part 4 - Subset Services, and Part 5 - Core Software Required Capabilities. Supplement 1 reflects the introduction of multicore processor support in Parts 1 and 2.
Airlines Electronic Engineering Committee
Core Flight System (cFS) Software Bus Network Application Version 1.0TBMG-220265/1/2015
The Software Bus Network (SBN) is a plug-in component developed for the Core Flight System (cFS) framework that extends the core Flight Executive (cFE) Software Bus (SB) publish/subscribe messaging service across partitions, processes, processors, and networks. This extension is done transparently for cFS software components, such that cFS software components remain unchanged and are unaware of source or destination(s) location.
Habitat Demonstration Unit Core Avionics SoftwareTBMG-214202/1/2015
The Habitat Demonstration Unit Core Avionics Software (HDU-CAS) is designed to provide the required functionality for an engineering prototype of a highly autonomous space habitat element, and to provide an opportunity for new software technologies to be tested in an environment that provides that functionality. The HDU itself must provide basic environmental and infrastructure services, while also supporting a variety of integrated subsystems that aid in the fulfillment of space mission operations. The HDU-CAS must then provide complete command and data handling, and intelligent autonomous operations functions of these needed subsystems in all appropriate circumstances (nominal and off-nominal).
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 5 CORE SOFTWARE RECOMMENDED CAPABILITIESARINC653P5 (Current)12/1/2014
The objective of this part is to define additional ARINC 653 core software capabilities to ease integration on a variety of Integrated Modular Avionics (IMA) hardware platforms by allowing platform suppliers to extend and customize it for use with their unique hardware platform. The objective of Part 5 is to define additional recommended capabilities when implementing ARINC 653 core software using a Commercial off the Shelf (COTS) ARINC 653 Operating System (O/S).
Airlines Electronic Engineering Committee
ECOA - A New Architecture Concept for Complex Military Software Systems2014-01-22279/16/2014
ECOA is an active software architecture research programme conducted by the French Republic and United Kingdom. It is one product of the recent Defence and Security Co-operation Treaty signed between the two nations. This paper provides an overview of the programme goals and progress as well as an introduction to the technology being developed and comparison to related initiatives. The goal of the ECOA programme is to define an open software architecture that enables collaborative development of mission system software. The ECOA programme is needed to reduce development and lifecycle costs of future military air programmes. For this reason the programme has a specific focus on combat-air mission systems but the underlying technology is general purpose, applying to multiple military and civil domains. At present, the programme has defined a concept, delivered a set of initial technical standards and produced a joint demonstrator to validate the technology developed.
Cornilleau, Thierry, Linard, Pierre, Moxon, Paul, Nicholas, Christopher
Technological Changes and Competitive Advantage: The New Deal for Avionics Firms2014-01-21739/16/2014
Since 2000, avionics is facing several changes, mostly driven by technological improvements in the electronics industry and innovation requirements from aircraft manufacturers. First, it has progressively lost its technological leadership over innovation processes. Second, the explosion of the electronics consumer industry has contributed to shorten even more its technology life cycles, and promoted the use of COTS. Third, the increasing complexity of avionics systems, which integrate more and more functions, have encouraged new players to enter the market. The aim of this article is to analyze how technological changes can affect the competitiveness of avionics firms. We refer to criticality levels as a determinant of the market competitiveness. Certification processes and costs could stop new comers to bring innovations from the consumer electronics industry and protects traditional players. The study will compare three avionics systems regarding their patent dynamics since 1980: flight controls, Integrated Modular avionics and Head-Up Displays. We assume that differences in the market competitiveness may appear due to their differences in their related criticality level. Systems belonging to Design Assurance Level A or B required wide-range of capabilities and long-term experience. The opportunity for new comers to introduce a certified-version of their product could be constrained by certification requirements.
Beaugency, Aurelie, Gatti, Marc, Regis, Didier
Method for Authorizing Critical Effector Commands in a Space-Based Integrated Modular Avionics SystemTBMG-205579/1/2014
An Integrated Modular Avionics (IMA) architecture provides a common platform for software partitions with shared processing and input/output (I/O) resources. A key feature of the IMA architecture is I/O partitioning. An IMA system will prevent one software partition from changing an I/O resource that is owned by another software partition. This prevents one software partition from controlling the outputs of another due to hardware fault or software error. The IMA system must have protection mechanisms in place to enforce the I/O partitioning.
Fully Configurable Interrupt ControllerTBMG-205589/1/2014
An interrupt is a signal in an interrupt controller (IC) that pulses to indicate an event or error. The IC is responsible for processing multiple internal interrupts and making these interrupts available to a host computer via a data bus or external output pins. Since there exist numerous interrupts, a method must be developed for routing the interrupts to the external output pins.
Collaborative Search and Pursuit for Autonomous HelicoptersF-0070-2014-96795/20/2014
This paper describes recent results from the Georgia Institute of Technology to develop, improve, and flight test a multi-aircraft collaborative architecture, focused on decentralized autonomous decision-making. The architecture includes a search coverage algorithm, behavior estimation, and a pursuit algorithm designed to solve a scenario-driven challenge problem. The architecture was implemented on a pair of Yamaha RMAX helicopters outfitted with modular avionics, as well as an associated set of simulation tools. Simulation and flight test results for single- and multiple-aircraft scenarios are presented. Further work suggested includes identification and development of more sophisticated methods that can replace the simpler elements in modular fashion.
Mooney, John, Johnson, Eric
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE, PART 3A, CONFORMITY TEST SPECIFICATION FOR ARINC 653 REQUIRED SERVICESARINC653P3A (Current)1/13/2014
The scope of this Compliance Test Specification is to define test procedures to demonstrate compliance of the API behavior only. This does not include performance tests (e.g., benchmark tests), nor demonstration of capability of the operating systems to manage combinations of configuration parameters.
Airlines Electronic Engineering Committee
Model-Based Design Flow Driven by Integrated Modular Avionic Simulations2013-01-22119/17/2013
The Integrated Modular Avionics (IMA) architecture has been a crucial concern for the aerospace industry in developing more complex systems, while seeking to reduce space, weight and power (SWaP), as well as development, certification and production time. From a software perspective, that objective pushes developers to migrate toward safety critical space and time partitioning environment. However, mainstream commercial real-time operating systems (RTOS) offering such partitioning can be restrictive in early development due to very high licensing costs. That situation is even more striking when considering that low-cost alternatives could instead be used for system modeling and early simulation before acquisition of a target platform. This paper reviews existing low-cost and open-source development environments to propose a novel design flow. The proposed methodology starts with model-based analysis in the AADL modeling language. Then, configuration files and software integration code are generated and executed using the Simulated IMA (SIMA) software from GMV. A case study experiment was created using a Multi-purpose Control and Display Unit (MCDU) communicating with an external Flight Management System (FMS) simulation provided by our industrial partner CMC Electronics. Results show reduction of time for system and partition configurations from hours to seconds, notably by reducing human error. It also proves useful in identifying design flaws in early development as well as facilitating software architectural exploration for integrated modular avionics.
Savard, Julien, Bao, Lin, Bois, Guy, Boland, Jean-François
A Multi-disciplinary and Multi-scale Simulation-Based Approach for the Design of Control Systems2013-01-22129/17/2013
This paper introduces a model-based systems and embedded software engineering, workflow for the design of control systems. The interdisciplinary approach that is presented relies on an integrated set of tools that addresses the needs of various engineering groups, including system architecture, design, and validation. For each of these groups, a set of best practices has been established and targeted tools are proposed and integrated in a unique platform, thus allowing efficient communication between the various groups. In the initial stages of system design, including functional and architectural design, a SysML-based approach is proposed. This solution is the basis to develop systems that have to obey both functional and certification standards such as ARINC 653 (IMA) and ARP 4754A. Detailed system design typically requires modeling and simulation of each individual physical component of the system by various engineering groups (mechanical, electrical, etc.). It also includes overall system design, assembling all physical components together, and designing the required control laws. In order to achieve the objectives for physical simulation, the paper proposes a multi-scale approach based on a combination of detailed “3D” and simplified “0D” system simulation tools, including Reduced Order Models created from “3D” simulation. For this purpose, simulation languages that implement the fundamental laws of physics are used (VHDL-AMS and Modelica). The Scade language is then used to design control laws that can be co-simulated together with the above physical models and, finally, the SCADE® qualified automatic code generator implements the control laws as embedded software behaving exactly as the model-based simulation that was previously achieved. The complete workflow described in this paper will be presented at the conference with an interactive flight controls demonstration.
Macauley, John, Delafosse, Vincent, LeSergent, Thierry
Secured Hybridization Algorithms of Critical Sensors Applied to Inertial Reference System for Civil Air Transport2013-01-21399/17/2013
By developing TopFlight ADIRU (Air Data Inertial Reference Unit) for civil aircraft avionics, THALES is establishing a new standard to comply with most demanding RNP-AR navigation procedures. Indeed, this new generation of inertial reference product goes a step further in the management of positioning integrity, continuity and availability, to simplify crew operations in demanding conditions. This is done through dedicated GPS/inertial hybridization algorithms, and their extensions to supplemental failure detection and exclusion.
Portal, Didier, Coatantiec, Jacques, Clemenceau, Pierre-Jerome
Items per page:
1 – 50 of 85