Bsi bs en 04660 002 2011

BS EN 4660-002:2011 BSI Standards Publication Aerospace series — Modular and Open Avionics Architectures Part 002: Common Functional Modules NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW raising standards worldwide™ BS EN 4660-002:2011 BRITISH STANDARD National foreword This British Standard is the UK implementation of EN 4660-002:2011 The UK participation in its preparation was entrusted to Technical Committee ACE/6, Aerospace avionic electrical and fibre optic technology A list of organizations represented on this committee can be obtained on request to its secretary This publication does not purport to include all the necessary provisions of a contract Users are responsible for its correct application © BSI 2011 ISBN 978 580 62442 ICS 49.090 Compliance with a British Standard cannot confer immunity from legal obligations This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 March 2011 Amendments issued since publication Date Text affected BS EN 4660-002:2011 EN 4660-002 EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM February 2011 ICS 49.090 English Version Aerospace series - Modular and Open Avionics Architectures Part 002: Common Functional Modules Série aérospatiale - Architectures Avioniques Modulaires et Ouvertes - Partie 002: CFM Luft- und Raumfahrt - Modulare und offene Avionikarchitekturen - Teil 002: CFM This European Standard was approved by CEN on 26 June 2010 CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN member This European Standard exists in three official versions (English, French, German) A version in any other language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom EUROPEAN COMMITTEE FOR STANDARDIZATION COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG Management Centre: Avenue Marnix 17, B-1000 Brussels © 2011 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members Ref No EN 4660-002:2011: E BS EN 4660-002:2011 EN 4660-002:2011 (E) Contents Page Foreword 4 0 0.1 0.2 Introduction 5 Purpose 5 Document structure .6 1 1.1 Scope 6 Relationship with other ASAAC Standards 6 2 Normative references 7 3 3.1 3.2 3.3 Terms, definitions and abbreviations 7 Terms and definitions 7 Abbreviations 8 Conventions used in this Standard 10 4 4.1 4.2 4.3 4.4 4.5 4.6 CFM Definition 10 Generic CFM 11 Module Support Unit 13 Module Processing Capability 20 Network Interface Unit (NIU) and Routing Unit (RU) 29 Module Power Supply Element 29 Module Physical Interface (MPI 31 5 5.1 5.2 5.3 Common Functional Module Interfaces 31 Module Logical Interface (MLI) 31 Module Physical Interface (MPI) 31 MOS Interface 32 6 6.1 6.2 6.3 6.4 6.5 CFM System Support and Guidelines 32 Fault Management 33 Fault Detection 33 Fault Masking 33 Fault Confinement 33 Safety and Security 34 Annex A.1 A.2 A.3 A.4 A.5 A.6 A (informative) Performance Sheet for all Common Functional Modules 36 Data Processor Module 36 Signal Processing Module 37 Graphic Processing Module 38 Mass Memory Module 38 Network Support Module 39 Power Conversion Module 39 Figures Page Figure — ASAAC Standard Documentation Hierarchy Figure — Functional representation of a generic CFM 11 Figure — IMA Common Functional Modules – Graphical Composition 21 Figure — The Power Supply Distribution functions of the PCM 26 Figure — Power Supply Element functions 30 Figure — Software Architecture Model - Three Layer Stack 32 BS EN 4660-002:2011 EN 4660-002:2011 (E) Tables Page Table — CFM Embedded Information – Read Only 14 Table — CFM Embedded Information – Read / Write 15 Table — PCM output characteristics 27 Table — PSE input voltage characteristics 30 Table A-1 — Performance sheet for a DPM 36 Table A-2 — Performance sheet for a SPM 37 Table A-3 — Performance sheet for a GPM 38 Table A-4 — Performance sheet for a MMM 38 Table A-5 — Performance sheet for a NSM 39 Table A-6 — Performance sheet for a PCM 39 BS EN 4660-002:2011 EN 4660-002:2011 (E) Foreword This document (EN 4660-002:2011) has been prepared by the Aerospace and Defence Industries Association of Europe - Standardization (ASD-STAN) After enquiries and votes carried out in accordance with the rules of this Association, this Standard has received the approval of the National Associations and the Official Services of the member countries of ASD, prior to its presentation to CEN This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by August 2011, and conflicting national standards shall be withdrawn at the latest by August 2011 Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom BS EN 4660-002:2011 EN 4660-002:2011 (E) Introduction 0.1 Purpose This document was produced under the ASAAC Phase II Contract The purpose of the ASAAC Programme is to define and validate a set of open architecture standards, concepts and guidelines for Advanced Avionics Architectures (A3) in order to meet the three main ASAAC drivers The standards, concepts and guidelines produced by the Programme are to be applicable to both new aircraft and update programmes The three main drivers for the ASAAC Programme are: Reduced life cycle costs Improved mission performance Improved operational performance The Standards are organised as a set of documents including:  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 systems,  The guidelines for system implementation through application of the standards The document hierarchy is given hereafter: (in this figure, the current document is highlighted) Standards for Architecture Standards for Software Standards for Packaging Guidelines for System Issues − − − − − − − System Management Fault Management Initialisation / Shutdown Configuration / Reconfiguration Time Management Security Safety Standards for Communications and Network Standards for Common Functional Modules Figure — ASAAC Standard Documentation Hierarchy BS EN 4660-002:2011 EN 4660-002:2011 (E) 0.2 Document structure The document contains the following clauses: Clause 1, scope of the document Clause 2, normative references Clause 3, the terms, definitions and abbreviations Clauses and provide CFM concept definition, requirements and standards Clause provides guidelines for implementation of standards Performance sheets for each of the CFMs are attached to the end of the document These sheets contain a list of attributes to be defined by the system designer and used by the CFM provider Scope This standard defines the functionality and principle interfaces for the Common Functional Module (CFM) to ensure the interoperability of Common Functional Modules and provides design guidelines to assist in implementation of such a CFM It is one of a set of standards that define an ASAAC (Allied Standard Avionics Architecture Council) Integrated Modular Avionics System This definition of interfaces and functionality allows a CFM design that is interoperable with all other CFM to this standard, that is technology transparent, that is open to a multi-vendor market and that can make the best use of COTS technologies Although the physical organisation and implementation of a CFM should remain the manufacturer’s choice, in accordance with the best use of the current technology, it is necessary to define a structure for each CFM in order to achieve a logical definition of the CFM with a defined functionality This definition includes:  The Generic CFM, which defines the generic functionality applicable to the complete set of CFMs The generic functionality is defined in 4.1  The processing capability, which defines the unique functionality associated with each CFM type within the set This functionality is defined in 4.3  The logical and physical interfaces that enable CFMs to be interoperable and interchangeable, these are defined in Clause  The functionality required by a CFM to support the operation of the System is defined in Clause 1.1 Relationship with other ASAAC Standards The definition of the complete CFM is partitioned and is covered by the following ASAAC standards:  CFM Mechanical properties and physical Interfaces – ASAAC Standards for Packaging  CFM Communication functions – ASAAC Standards for Software  CFM Network interface – ASAAC Standards for Communications and Network  CFM Software architecture – ASAAC Standards for Software  CFM Functional requirements – This document BS EN 4660-002:2011 EN 4660-002:2011 (E) Normative references The following referenced documents are indispensable for the application of this document For dated references, only the edition cited applies For undated references, the latest edition of the referenced document (including any amendments) applies ISO 1540, Aerospace — Characteristics of aircraft electrical systems EN 4660-001, Aerospace series — Modular and Open Avionics Architectures — Part 001: Architecture EN 4660-003, Aerospace Communications/Network series — Modular and Open Avionics Architectures — Part 003: EN 4660-004, Aerospace series — Modular and Open Avionics Architectures — Part 004: Packaging EN 4660-005, Aerospace series — Modular and Open Avionics Architectures — Part 005: Software ASAAC2-GUI-32450-001-CPG Issue 01, Final Draft of Guidelines for System Issues 1) — Volume — System Management — Volume — Fault Management — Volume — Initialisation and Shutdown — Volume — Configuration / Reconfiguration — Volume — Time Management — Volume — Security — Volume — Safety 3.1 Terms, definitions and abbreviations Terms and definitions Use of “shall”, “should” and “may” within the standards observe the following rules:  The word SHALL in the text express a mandatory requirement of the standard  The word SHOULD in the text expresses a recommendation or advice on implementing such a requirement of the standard It is expected that such recommendations or advice will be followed unless good reasons are stated for not doing so 1) Published by: Allied Standard Avionics Architecture Council BS EN 4660-002:2011 EN 4660-002:2011 (E)  The word MAY in the text expresses a permissible practice or action It does not express a requirement of the standard Open System: 3.2 A system with characteristics that comply with specified, publicly maintained, readily available standards and that therefore can be connected to other systems that comply with these same standards Abbreviations 2D : Two Dimensional 3D : Three Dimensional A3 : Advanced Avionics Architecture AGT : Absolute Global Time ALT : Absolute Local Time APOS : Application to Operating System Interface ASAAC : Allied Standard Avionics Architecture Council BIT : Built-in Test CBIT : Continuous BIT CFM : Common Functional Module CORBA : Common Object Request Broker Architecture COTS : Commercial Off The Shelf CRC : Cyclic Redundancy Check dc : Direct Current DPM : Data Processing Module DSP : Digital Signal Processor EDAC : Error Detection And Correction FFT : Fast Fouriert Transformation FIR : Finite Impulse response Filter FMECA : Fault Mode Effect and Criticality Analysis GPM : Graphic Processing Module GSM : Generic System Management HW : Hardware HDD : Head-Down Display HMD : Helmet Mounted Display HUD : Head-Up Display IBIT : Initiated BIT ID : Identification BS EN 4660-002:2011 EN 4660-002:2011 (E) The NSM will perform two main functions:  Connection to the network or networks and when necessary the configuration of network paths and switching capabilities for switched networks  The maintenance of a Master Reference Clock to support the distribution of time throughout the system The NSM is currently considered to be a suitable location for the Master Reference Clock as most systems are expected to include one or more NSMs Nevertheless, the Master Reference Clock may be provided by other means (e.g by MMM) The internal logical structure of the NSM, in compliance with the selected network baseline, will consist of the following building blocks as illustrated in Figure 3e  The Module Physical Interface (MPI) as defined in 4.6  The Power Supply Element as defined in 4.5  The Communication Control Unit shall perform controlling and management tasks for the communication unit and for the distribution of ALT A Master Reference Clock shall support the distribution of time throughout the system It will monitor the functions on the NSM and report any faults to the system management software It will be responsible for establishing the connections required for a default communications network on power-up and will also alter the switch configuration when commanded  Each Communication Unit will provide reconfigurable interconnection for its network interfaces  The Communication Network Interface Unit will provide an interface to the network connections in the rack backplane 4.3.6.2 Network Support Module – Requirements The NSM is not required to adhere completely to the generic CFM concept but shall implement the following subset of the generic functionality:  CFM Embedded Information (see 4.2.2.1)  BIT (see 4.2.2.2)  Fault Logging (see 4.2.2.3)  Absolute Local Time (see 4.2.2.4)  Boot Strap Loader (see 4.2.4)  Hours of Operation (see 4.2.2.5)  Time distribution  Maintenance Test Port (see 4.2.2.6) In addition the NSM shall provide the following capabilities:  Support functions, including switching and routing capabilities as required by EN 4660-003  Maintain a default communication configuration that can be adopted on power-up  Provide non-blocking facilities for the routing and reconfiguration of the ASAAC network 28 BS EN 4660-002:2011 EN 4660-002:2011 (E) 4.4 Network Interface Unit (NIU) and Routing Unit (RU) 4.4.1 NIU and RU Description The ´NIU and RU provide all the communications within the CFM and connection to the external network under the control of the MSU They allow all PEs of a modular system to be capable of intercommunicating with each other The NIU and RU within each CFM module provide the capability for the following communication types:  Intra-Module Communication: Allowing communication between PEs inside the module  Between-Module Communication: Allowing communication between modules  Intra-PE Communication: Allowing communication between processors inside a PE To enable interoperability between CFMs of a different type or between different implementations of the same CFM type, the Module Logical Interface (MLI) is defined, see Clause 4.4.2 NIU and RU Requirements The NIU and RU functions shall support the required number of ASAAC Network interfaces as defined for each module type in 4.3 The NIU and RU shall support Intra-Module, Between-Modules and Intra-PE communications The NIU and RU shall provide an interface to the Operating System (at the MOS level) compliant with the MOS Communication Services defined in EN 4660-005 4.5 4.5.1 Module Power Supply Element Module Power Supply Element Description In order to power the hardware of a CFM, the CFM shall be able to accept a standardised DC voltage from the backplane and convert it to the technology-specific power levels required within the module This capability shall exist as a physical Power Supply Element The functions of the Power Supply Element (PSE) are described in Figure 29 BS EN 4660-002:2011 EN 4660-002:2011 (E) CFM dc to dc conversion down to component voltages Power Supply Element Module Physical Interface Figure — Power Supply Element functions The PSE functionalities are:  The dc to dc conversion of the CFM supplied voltages down to the required component voltage(s): there is no limitation on the number of the PSE outputs  The consolidation of supplied voltages coming from different PCMs during normal operation For fault tolerance reasons, at least two PCMs are supplying each CFM 4.5.2 Module Power Supply Requirements The Power Supply Element within a CFM shall accept the following input voltage characteristics: Table — PSE input voltage characteristics 30 Parameter Value Input Voltage 48 Vdc Input Voltage characteristics 36 to 75 Vdc Input Voltage 48 Vdc Input Voltage characteristics 36 to 75 Vdc Input voltage consolidation Load sharing between input voltages and BS EN 4660-002:2011 EN 4660-002:2011 (E) 4.6 Module Physical Interface (MPI 4.6.1 MPI Description The MPI is those parts of the module that provide the common physical interfaces for the module and that adhere to the Module Physical Interface definition, see 4.6.2 4.6.2 MPI Requirements All ASAAC Common Functional Modules shall adhere to the MPI, which is specified in EN 4660-004 Common Functional Module Interfaces This clause provides a top-level description of the interfaces, both logical and physical, that define the interoperability requirements for the Common Functional Module The detailed definition of these interfaces can be found in the ASAAC Standards identified below 5.1 Module Logical Interface (MLI) 5.1.1 MLI Description To enable interoperability between CFMs of a different type or between different implementations of the same CFM type, the Module Logical Interface (MLI) is defined This comprises two parts:  The Module Logical Interface for Network Properties This specifies the network medium, format, protocol, control and characteristics of the communication, across the Network, between NIU on different CFMs This MLI for Network Properties is specified in EN 4660-003  The Module Logical Interface for Communications This defines the data presentation and Virtual Channel communications format between instances of the Communication Manager and the MOS communication services, both of these residing above the NIU These logical communications support:  Module and System Initialisation  Module Resource Management  Time Management  Network Management This is defined in EN 4660-005 5.1.2 MLI Requirements All CFM shall comply with the MLI specification for the communication services as defined in EN 4660-005 All CFM shall comply with the MLI specification for the network properties as defined in EN 4660-003 5.2 5.2.1 Module Physical Interface (MPI) MPI Description The MPI defines the principle interfaces: Cooling, connector and insertion extraction device, for more details refer to EN 4660-004 31 BS EN 4660-002:2011 EN 4660-002:2011 (E) 5.2.2 MPI Requirements All ASAAC Common Functional modules shall adhere to the MPI, which is specified in EN 4660-004 5.3 MOS Interface 5.3.1 MOS Interface Description The Module Support Layer to Operating System Layer (MOS) interface defines a set of services that provides hardware independence for the operating system and allows the operating system software to access the resources, which reside on a CFM and are implemented by the Module Support Layer (MSL) software The MOS interface is an essential element of the three layer architectural model, as specified in EN 4660-005 as illustrated in Figure Apps & App Manager APOS OSL MOS MSL CFM Hardware Figure — Software Architecture Model - Three Layer Stack 5.3.2 MOS Interface – Requirement The Data Processing Module (DPM), Signal Processing Module (SPM), Graphics Processing Module (GPM), Mass Memory Module (MMM) and the Power Conversion Module (PCM) shall provide a MOS interface compliant with the Operating System requirements defined in EN 4660-005 Note, that the NSM is exempted from having a MOS interface, refer to 4.1.2 CFM System Support and Guidelines This clause provides guidelines when implementing system functionality in a CFM To support the implementation of CFMs compliant with the Standards and Systems Issues These will cover:  Support for Fault Management  Safety and Security 32 BS EN 4660-002:2011 EN 4660-002:2011 (E) 6.1 Fault Management Details of the System and Fault Management of an ASAAC system are specified in Fault Management section of the Final Draft of Guidelines for System and Fault Management ASAAC2-GUI-32450-001-CPG Issue 01 (Volume 2) 6.2 Fault Detection The module should have techniques (PBIT) designed to detect faults that exist at module power up Any detected fault by PBIT should be logged in the Fault Log for subsequent interrogation and ITM purposes; refer to 4.2.2.3 NOTE During operational mode CBIT and IBIT faults may be logged by the fault manager, which runs above the MOS There are many techniques that exist for the detection of faults and it is not the purpose of this guideline to exhaustively list them Details on Fault Management are given in ASAAC2-GUI-32450-001-CPG Issue 01 (Volume 2) However, the general requirements for fault detection are given below:  To maintain a high availability of the on-module resources, separate hardware elements such as processing elements, the network interface, the module controller etc should be able to perform BIT in a modular fashion without affecting the rest of the module  It is necessary that data checks be implemented on all communication channels on and off the module It is highly recommended that the scheme have in-built-in error correction capabilities  To aid the system in determining the efficiency of the system, the module should be able to monitor the performance of aspects such as processing and communication Processors could maintain a performance task that monitors the task usage Communication channel interfaces could maintain a packet throughput register Accurate time data should be used to enable performance measurement 6.3 Fault Masking To increase the availability of the system and to guard against a series of small failures rendering a system non-operational, the module should - whenever possible - attempt to mask detected faults The technique used for masking is completely dependent upon the technology and should be considered in conjunction with fault analysis For example:  Code checks such as CRC and EDAC on communication channels provide a simple fault masking method as they possess inherent error correction capabilities  Memory, whatever technology, is subject to storage location faults and address mapping mechanisms A technique to remove the faulty location from the memory map is recommended while the access characteristics to the memory keeps unaltered with the change in address mapping  If critical paths or paths subject to a high fault occurrence probability exist, then multiple identical paths should be implemented similarly 6.4 Fault Confinement Fault masking is not able to mask all the possible faults from the system and it is therefore essential that in the event of one of these faults occurring the fault is confined to a specified boundary In terms of CFMs there are two approaches:  Isolate the module hardware by disabling the network interface except for a dedicated link to the module controller The module then localises the fault, using BIT and determine its impact on the operation of the module Then the module could be made available again to the system if the fault is deemed non-repeatable, although this is the responsibility of the system implementor 33 BS EN 4660-002:2011 EN 4660-002:2011 (E)  Isolate the complete module by turning it off by the PCM This approach is most certainly the safest, poses the least danger to the system and simplifies the design and construction 6.5 Safety and Security 6.5.1 Safety The following three main requirements should be maintained through all the elements of the ASAAC IMA system architecture to allow the proof of Safety They are data integrity, availability of data and resources, and predictability 6.5.1.1 Data Integrity The data integrity requirement applied to computing process resources impacts directly the design of the module processing capabilities of the DPM, GPM and MMM Therefore the design should be such that a high level of confidence to data integrity is achieved The data integrity requirement applied to communications (i.e no corruption or misrouting) impacts directly the design of the NSM as a whole and also the internal communications elements of all the CFMs concerned with Safety applications mainly DPMs, GPMs and MMMs This implies that on all these parts:  At design stage adequate information on the internal organisation and operation should be made available to enable comprehensive risk analysis and FMECA to be performed and to obtain the risk estimates for critical failure occurrences  At run time their operation and associated resources (e.g configuration tables and mapping tables) should be maintained safe from hazards or faults occurring in adjacent areas  At run time, sufficient fault detection and localisation should be performed to achieve the fault tolerance objectives 6.5.1.2 Availability of Data and Resources It should be shown with a high degree of confidence that, at run time, the memory management actually provides the processes with the amount of data and program memory space specified in the Blueprints, refer to EN 4660-005 This implies providing very efficient monitoring and built-in tests 6.5.1.3 Predictability The architecture of a CFM should ensure that internal communications operation is predictable in terms of time and is guaranteed to be free from lock-up situation 6.5.2 6.5.2.1 Security Memory Management support Memory management utilities may be used to prevent access to invalid memory addresses according to blueprint information by errant or illicit computing processes 6.5.2.2 Module Tempest Modules should be designed such that electromagnetic coupling effects between data communication and power supply not result in unintentional transmission of data off modules 34 BS EN 4660-002:2011 EN 4660-002:2011 (E) This impacts the mechanical and electrical design of all processing and networking modules that should provide sufficient electromagnetic decoupling between internal areas to ensure that no unintentional transmission can be observed on the module electrical interfaces It is assumed that the Network optical physical layer is immune against electromagnetic coupling 6.5.2.3 Electromagnetic Separation It is required that electromagnetic coupling effects should not result in leakage of data between CFM modules of any type, such that no classified information is written to non-volatile memory locations 6.5.2.4 Memory Erase All processing modules (DPM, GPM, SPM and MMM) may be designed such that all classified data is deleted when power is removed A memory erase can be required to be initiated by the MMM autonomously if a non authorised removal is detected This may require some specific memory technologies for the storage of sensitive information 35 BS EN 4660-002:2011 EN 4660-002:2011 (E) Annex A (informative) Performance Sheet for all Common Functional Modules A.1 Data Processor Module This sheet provides a performance parameter framework that may be used to indicate the capability of an implemented CFM Table A.1 — Performance sheet for a DPM Parameter Number of Processors Integer Integer Processing Power per Processor SPECint95 Floating Point Processing Power per Processor SPECfp95 Total Non-Volatile Memory Size Mbyte Total Volatile Memory Size Mbyte Total Number of Timers Integer Timer Rollover Period ms Timer Accuracy µs Timer Resolution ns Rate per Network Link – for each type 36 Units Gbytes/s Number of Input Network Links – for each type Integer Number of Output Network Links – for each type Integer Power Consumption W Weight kg BS EN 4660-002:2011 EN 4660-002:2011 (E) A.2 Signal Processing Module This sheet provides a performance parameter framework that may be used to indicate the capability of an implemented CFM Table A.2 — Performance sheet for a SPM Parameter Number of Digital Signal Processors Units Integer Integer Processing Power per Processor SPECint95 Floating Point Processing Power per Processor SPECfp95 Total Non-Volatile Memory Capacity Mbyte Total Volatile Memory Capacity Mbyte Total Number of Timers Integer Timer Rollover Period ms Timer Accuracy µs Timer Resolution ns Rate per Network Link – for each type Gbytes/s Number of Input Network Links – for each type Integer Number of Output Network Links – for each type Integer Power Consumption W Weight kg 37 BS EN 4660-002:2011 EN 4660-002:2011 (E) A.3 Graphic Processing Module This sheet provides a performance parameter framework that may be used to indicate the capability of an implemented CFM Table A.3 — Performance sheet for a GPM Parameter Number of Graphics Processors Image resolution Units Integer pixels x pixels x bits Refresh rate Hz Line/Polygon drawing rate vectors/sec Gouraud/Phong Shading rate triangles/sec Total Non-Volatile Memory Capacity Mbyte Total Volatile Memory Capacity Mbyte Total Number of Timers Integer Timer Rollover Period ms Timer Accuracy µs Timer Resolution ns Rate per Network Link – for each type Gbytes/s Number of Input Network Links – for each type Integer Number of Output Network Links – for each type Integer Power Consumption W Weight kg A.4 Mass Memory Module This sheet provides a performance parameter framework that may be used to indicate the capability of an implemented CFM Table A.4 — Performance sheet for a MMM Parameter Total Non-Volatile Memory Capacity Mbyte Total Volatile Memory Capacity Mbyte Rate per Network Link – for each type 38 Units Gbytes/s Number of Input Network Links – for each type Integer Number of Output Network Links – for each type Integer Power Consumption W Weight kg BS EN 4660-002:2011 EN 4660-002:2011 (E) A.5 Network Support Module This sheet provides a performance parameter framework that may be used to indicate the capability of an implemented CFM Table A.5 — Performance sheet for a NSM Parameter Rate per Network Link – for each type Units Gbytes/s Number of Input Network Links – for each type Integer Number of Output Network Links – for each type Integer Power Consumption W Weight kg A.6 Power Conversion Module This sheet provides a performance parameter framework that may be used to indicate the capability of an implemented CFM Table A.6 — Performance sheet for a PCM Parameter Units Maximum Input Current A Minimum Input Current A Maximum Output Current per Output Power Link A Number of Output Power Links Power Integration Electrical Efficiency Rate per Network Link – Type Integer kW/I % Gbytes/s Number of Input Network Links – Type Integer Number of Output Network Links – Type Integer Rate per Network Link – Type Gbytes/s Number of Input Network Links – Type Integer Number of Output Network Links – Type Integer Power Consumption W Weight kg 39 This page deliberately left blank This page deliberately left blank British Standards Institution (BSI) BSI is the independent national body responsible for preparing British Standards and other standards-related publications, information and services It presents the UK view on standards in Europe and at the international level It is incorporated by Royal Charter Revisions Information on standards British Standards are updated by amendment or revision Users of British Standards should make sure that they possess the latest amendments or editions It is the constant aim of BSI to improve the quality of our products and services We would be grateful if anyone finding an inaccuracy or ambiguity while using this British Standard would inform the Secretary of the technical committee responsible, the identity of which can be found on the inside front cover Tel: +44 (0)20 8996 9001 Fax: +44 (0)20 8996 7001 BSI provides a wide range of information on national, European and international standards through its Knowledge Centre BSI offers Members an individual updating service called PLUS which ensures that subscribers automatically receive the latest editions of standards Tel: +44 (0)20 8996 7669 Fax: +44 (0)20 8996 7001 Email: plus@bsigroup.com Buying standards You may buy PDF and hard copy versions of standards directly using a credit card from the BSI Shop on the website www.bsigroup.com/shop In addition all orders for BSI, international and foreign standards publications can be addressed to BSI Customer Services Tel: +44 (0)20 8996 9001 Fax: +44 (0)20 8996 7001 Email: orders@bsigroup.com In response to orders for international standards, it is BSI policy to supply the BSI implementation of those that have been published as British Standards, unless otherwise requested Tel: +44 (0)20 8996 7004 Fax: +44 (0)20 8996 7005 Email: knowledgecentre@bsigroup.com Various BSI electronic information services are also available which give details on all its products and services Tel: +44 (0)20 8996 7111 Fax: +44 (0)20 8996 7048 Email: info@bsigroup.com BSI Subscribing Members are kept up to date with standards developments and receive substantial discounts on the purchase price of standards For details of these and other benefits contact Membership Administration Tel: +44 (0)20 8996 7002 Fax: +44 (0)20 8996 7001 Email: membership@bsigroup.com Information regarding online access to British Standards via British Standards Online can be found at www.bsigroup.com/BSOL Further information about BSI is available on the BSI website at www.bsigroup.com/standards Copyright Copyright subsists in all BSI publications BSI also holds the copyright, in the UK, of the publications of the international standardization bodies Except as permitted under the Copyright, Designs and Patents Act 1988 no extract may be reproduced, stored in a retrieval system or transmitted in any form or by any means – electronic, photocopying, recording or otherwise – without prior written permission from BSI This does not preclude the free use, in the course of implementing the standard of necessary details such as symbols, and size, type or grade designations If these details are to be used for any other purpose than implementation then the prior written permission of BSI must be obtained Details and advice can be obtained from the Copyright & Licensing Manager Tel: +44 (0)20 8996 7070 Email: copyright@bsigroup.com BSI Group Headquarters 389 Chiswick High Road London W4 4AL UK Tel +44 (0)20 8996 9001 Fax +44 (0)20 8996 7001 www.bsigroup.com/standards raising standards worldwide™