Appendix 3 to ETSO-C153a – Integrated Modular Avionics (IMA) Module Data Requirements

For an IMA module authorisation, as mentioned in paragraph 2.2 of the ETSO-C153a main body document, additional technical data shall be available or submitted. This data will be documented into a set of documents for the ETSO authorisation (qualification plans, compliance evidences, etc.) and for the IMA module users such as Application developers, Integrators or type certificate applicants (User Guide, Usage domain, etc.):

— Chapter 1 — IMA module ED-124 documentation;

— Chapter 2 — Specific User Guide and Installation Manual contents;

— Chapter 3 — Core software;

— Chapter 4 — Health management and reporting;

— Chapter 5 — Usage domain;

— Chapter 6 — Configuration;

— Chapter 7 — Tools; and

— Chapter 8 — Compatibility & mixability information.

Chapter 1 — IMA module ED-124 documentation

The IMA system approval can be made incremental by introducing some intermediate acceptance steps. An ETSO-C153a authorisation is the first intermediate step dedicated to authorising IMA platforms and/or IMA modules (independently of any specific aircraft installation).

EUROCAE ED-124/RTCA DO-297 contains guidance for Integrated Modular Avionics (IMA) developers, application developers, integrators, certification applicants, and those involved in the approval and continued airworthiness of IMA systems in civil certification projects.

As mentioned in paragraph 3.2.2.1 of the ETSO-C153a main body document, to prepare the integration of the ETSO-C153a IMA module, the development objectives are defined in the EUROCAE ED-124 guidance related to Task 1 (Table A-1 objectives).

For an ETSO-C153a approval, the following data are available (A) or submitted (S) to the competent authority:

Note (1): this Partitioning Analysis shall include the verification results obtained for demonstration of compliance of 0, 0, 0, and 0.

Note (2): only for User Guide content used for ETSO compliance demonstration.

Chapter 2 — Specific User Guide and Installation Manual contents

As per ED-124, the IMA module User guide shall be provided by the IMA module manufacturer to both the module users and the Airworthiness Authority.

This User Guide includes all the information for users, integrators, and certification applicants to successfully interface with or integrate the module, such as:

— guaranteed behaviour and characteristics as per CO.k);

— interfaces (incl. physical mapping of interfaces);

— limitations and Open Problem Reports (OPRs)(1) (including tools);

— the Worst-Case Execution Time (WCET) analysis elements;

— the applicable Failure Mode Effect Analysis/Failure Mode Effect Summary (extracts) necessary for higher level safety analysis;

— the Core Software (see Appendix 3, Chapter 3);

— Fault Management and Health Monitoring (see Appendix 3, Chapter 4);

— the Usage Domain (see Appendix 3, Chapter 5) ;

— configuration aspects (see Appendix 3, Chapter6);

— tools aspects (see Appendix 3, Chapter 7);

— compatibility and mixability information (see Appendix 3, Chapter 8);

— remaining activities to be conducted by the module user to complete the IMA module qualification (environment);

— requirements recommendations for applications (e.g. data for the qualification of the application, service available for applications, etc.); and

— requirements recommendations for System Integration.

(1) An explicit description of the root cause and effects of an IMA module OPR is necessary to support the IMA module user and aircraft manufacturer in their assessment of the effects of the OPR on the aircraft function.

The Installation Manual includes all the data necessary for the proper installation and use of the IMA module (including marking aspects).

Each item of the characterisation and functional requirements is addressed in the User Guide (or possibly in the Installation Manual, if appropriate).

The User Guide defines the Usage Domain for which the module acceptance data is valid.

The information includes recommendations and may also include examples of the correct use of the module. In addition, the guide highlights any warnings or limitations to integrate or to interface with the module to prevent potential incorrect or unintended use.

The User Guide may be completed by the IMA module manufacturer with:

— information on Single Event Upset (SEU) effects;

— a Validation and Integration Kit for application developers and system integrators;

— Development and In-Service support; and

— some training.

The Installation Manual includes information as required in the MPS Appendix or referenced subsequent applicable chapter of the User Guide. In this case, the User Guide chapter will be submitted to the Airworthiness Authority (see Note (*) above).

The User Guide may be included in the Installation Manual of the IMA module (e.g. Annexes) or a separated document referenced by the Installation Manual.

Chapter 3 — Core Software

As defined in Appendix 1 above, the IMA module may be an association of Hardware and Core Software.

Core Software is consists of the operating system and the support software that manage resources to provide an environment in which the intended function is performed. Core software is typically comprised of one or more component(s). Core Software may be resident or a Field-Loadable Software part.

If the IMA module contains Core Software, the Core Software characteristics required by 0 of Appendix 2 are documented in the IMA module User Guide.

Chapter 4 — Health management and reporting

The data requirements related to health management and reporting are listed in 0.

Chapter 5 — IMA module usage domain

An ETSO-C153a authorisation relies on the concept of a Usage Domain (as per Chapter 2 — Definitions of Appendix 1).

The usage domain is defined at the IMA module level and used at the Application level and the IMA system level.

The definition of the usage domain includes consideration of the module functionality, performance and safety requirements, as well as of the required environmental performance of the module.

The IMA module manufactured to comply with this ETSO may be used to support other ETSOs or systems approved under CS-23, CS-25, CS-27, CS-29, CS-E or CS-P. These ETSO authorisations, IMA system approvals and aircraft level approvals, are not covered by this ETSO but will rely on the fact that compliance with the Usage Domain as documented in the User Guide, is correctly implemented.

Chapter 6 — Configuration

The IMA module may need to be configured before installation in the IMA system (EUROCAEED-124, Tasks 2, 3 and 4).

The data requirements related to configurability are listed in 0 of Appendix 2.

Chapter 7 — Tools

Some tolls may need to be used during the installation of the IMA module in the IMA system (EUROCAE ED-124 Tasks 2, 3 and 4). These tools may be used by:

— application developers;

— (an) integrator(s); and

— type certificate (TC) or supplemental type certificate (STC) applicants.

These tools may address:

— software development (hosted applications);

— configuration development;

— network architecture and configuration;

— debug, data loading; and

— WCET analysis and measures.

In that case, the User Guide references each tool in the data listed in Appendix 2 0.

If qualification credit is expected from these tools(such as configuration tools), the qualification process and data requirements are defined in paragraph 2.2 of CS-ETSO Subpart A. Software standards as well as the Airborne Electronic Hardware Qualification data of paragraph 2.3 are considered to be data to be submitted to EASA in the frame of an ETSO-C153a authorisation.

Chapter 8 — Compatibility and mixability information

The IMA module manufacturer provides compatibility and mixability information between hardware, software, tools and the usage domain in the User Guide, as required per 0 of Appendix 2.

[Amdt ETSO/10]

[Amdt ETSO/16]