The purpose of this MOAA standard is to define a set of open architecture standards, concepts & guidelines for Advanced Avionics Architectures (A3).<\/p>\n
The three main goals for the MOAA Standards are:<\/p>\n
Reduced life cycle costs,<\/p>\n<\/li>\n
Improved mission performance,<\/p>\n<\/li>\n
Improved operational performance.<\/p>\n<\/li>\n<\/ul>\n
The MOAA standards are organised as a set of documents including:<\/p>\n
A set of agreed standards that describe, using a top down approach, the Architecture overview to all interfaces required to implement the core within avionics system,<\/p>\n<\/li>\n
The guidelines for system implementation through application of the standards. The document hierarchy is given in Figure 1: (in this figure the document is highlighted)<\/i><\/p>\n<\/li>\n<\/ul>\n
This standard details the functionality and principle interfaces of an EN 4660 compliant network to ensure the interoperability of Common Functional Modules and design guidelines to assist in implementation of such a network.<\/p>\n
The purpose of this standard is to establish by means of well defined interfaces and functionality, a network design that is technology transparent and that is open to a multi-vendor market. Therefore, specific data communication network topology, protocols and technologies are not identified in this document.<\/p>\n
Although the physical organisation and implementation of the network shall remain the System Designers choice, in accordance with the best use of the current technology, it is necessary to define interfaces and parameter sets in order to achieve a logical definition of the network with a defined functionality. This definition includes:<\/p>\n
The generic functionality applicable to all networks.<\/p>\n<\/li>\n
The logical interfaces to the Operating System and Module Support Layers.<\/p>\n<\/li>\n
Optionally the physical interfaces to the Common Functional Modules (CFM).<\/p>\n<\/li>\n<\/ul>\n
This document identifies the principle interfaces for the Network, in Clause 4, and where appropriate, provides requirements on network parameters to be defined.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 6<\/td>\n | 1 Scope <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | 2 Normative references 3 Terms and definitions and Abbreviations 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | 3.2 Abbreviations <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | 4 Network Definition 4.1 Overview 4.2 Specific Network Requirements <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 4.3 Module Physical Interface 4.4 Optional Module Logical Interface <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 4.5 Optional MLI – Network Properties 4.5.1 General 4.5.2 Data Formats 4.5.2.1 General 4.5.2.2 Required Formats 4.5.2.3 Optional Formats <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 4.5.3 Data Link properties 4.5.3.1 General 4.5.3.2 Required Characteristics <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 4.5.3.3 Optional Characteristics 4.5.4 Control Functions 4.5.4.1 Required Functions 4.5.4.2 Optional Functions 4.5.5 Monitoring Functions 4.5.5.1 Required Functions <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 4.5.5.2 Optional Functions 4.5.6 Transfer Protocols 4.5.6.1 General <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 4.5.6.2 Optional Protocols <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | Annex A (informative)Standard Evolution Form <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Aerospace series. Modular and Open Avionics Architectures – Communications\/Network<\/b><\/p>\n |