Refine Your Search

Topic

Search Results

Viewing 1 to 19 of 19
Standard

DATALINK SECURITY PART 1 - ACARS MESSAGE SECURITY

2007-12-10
CURRENT
ARINC823P1
The purpose of this document is to provide an industry standard for ACARS Message Security (AMS), which permits ACARS datalink messages to be exchanged between aircraft and ground systems in a secure, authenticated manner using a uniform security framework. The security framework described herein is based on open international standards that are adapted to the ACARS datalink communications environment.
Standard

Survey of practices for securing the interface through the Data Link Connector (DLC)

2017-07-05
WIP
J3146
This document has been issued to provide a reference or overview of some current practices which could be utilized for securing the vehicle’s interface with the Data Link Connector (DLC) from cybersecurity risks associated with external test equipment connections (e.g. diagnostics scan tools) or remotely connected applications (e.g. telematics devices).
Standard

GUIDANCE FOR USAGE OF DIGITAL CERTIFICATES

2018-07-11
CURRENT
ARINC842-2
This document sets forth guidance for life-cycle management of public/private (i.e., asymmetric) keys that are used to secure interactions among systems.
Standard

GUIDANCE FOR SECURITY EVENT LOGGING IN AN IP ENVIRONMENT

2017-06-21
CURRENT
ARINC852
This report sets forth guidance for IP-based onboard networks and systems residing in the Airline Information Services (AIS) and Passenger Information and Entertainment Services (PIES) Domains by establishing a common set of security related data elements and format(s) that are produced by aircraft systems, suitable for use by airline IT and/or avionic supplier analytical ground tools.
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: Architecture Technical Governance

2020-08-12
CURRENT
AS6522A
This Technical Governance is part of the SAE UCS Architecture Library and is primarily concerned with the UCS Architecture Model (AS6518) starting at Revision A and its user extensions. Users of the Model may extend it in accordance with AS6513 to meet the needs of their UCS Products. UCS Products include software components, software configurations and systems that provide or consume UCS services. For further information, refer to AS6513 Revision A or later. Technical Governance is part of the UCS Architecture Framework. This framework governs the UCS views expressed as Packages and Diagrams in the UCS Architecture Model.
Standard

Configuration Management Requirements for Defense Contracts

2020-08-10
CURRENT
EIA649_1A
This document applies to hardware and software and provides CM requirements to be placed on contracts after being tailored by the Acquirer. The requirements have been organized by the following five CM functions: a Configuration Planning and Management b Configuration Identification c Configuration Change Management d Configuration Status Accounting e Configuration Verification and Audit
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: Architecture Description

2020-07-14
CURRENT
AS6512A
This document is the Architecture Description (AD) for the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture Library Revision A or, simply, the UCS Architecture. The architecture is expressed by a library of SAE publications as referenced herein. The other publications in the UCS Architecture Library Revision A are: AS6513A, AS6518A, AS6522A, and AS6969A.
Standard

Electron Beam Powder Bed Fusion Process

2020-07-01
CURRENT
AMS7007
This specification establishes process controls for the repeatable production of aerospace parts by Electron Beam Powder Bed Fusion (EB-PBF). It is intended to be used for aerospace parts manufactured using additive manufacturing (AM) metal alloys, but usage is not limited to such applications.
Standard

Requirements for a COTS Assembly Management Plan

2020-08-03
CURRENT
EIA933C
This document applies to the development of Plans for integrating and managing COTS assemblies in electronic equipment and Systems for the commercial, military, and space markets; as well as other ADHP markets that wish to use this document. For purposes of this document, COTS assemblies are viewed as electronic assemblies such as printed wiring assemblies, relays, disk drives, LCD matrices, VME circuit cards, servers, printers, laptop computers, etc. There are many ways to categorize COTS assemblies1, including the following spectrum: At one end of the spectrum are COTS assemblies whose design, internal parts2, materials, configuration control, traceability, reliability, and qualification methods are at least partially controlled, or influenced, by ADHP customers (either individually or collectively). An example at this end of the spectrum is a VME circuit card assembly.
Standard

Airworthiness Assurance for Airborne Electronic Hardware (AEH) Containing Commercial-off-the-shelf (COTS) Electronic Components

2018-12-19
WIP
ARP7495
This document addresses issues related to assurance that COTS electronic hardware components will perform their intended function in the AEH equipment or system in which they are installed. Those issues may impact system design, reliability assessment, quality, testing, production or support; but this document is not intended to be specific to any of those disciplines. This document is focused on the hardware issues raised in DOT/FAA/TC-16/57; it does not include issues related to software, firmware, etc. This document is intended to fit within the development process for civil aircraft and systems. This document can be used to support design and analysis activities in RTCA DO-254/EUROCAE ED-80 and RTCA DO-297/EUROCAE ED-124, as well as SAE ARP4754. This document addresses twelve (12) of the twenty-six (26) specific issues described in DOT/FAA/TC-16/57.
Standard

Glossary of System Safety Engineering and Management

2018-05-08
WIP
SAE1003
This SAE Aerospace Information Report will be a compilation of system safety engineering and management terms and definitions covering concepts used across multiple products and disciplines
Standard

Standard for Preparing a DMSMS Management Plan

2017-04-14
WIP
STD0016A
This document defines the requirements for developing a DMSMS Management Plan, hereinafter also called the Plan, to assure customers that the Plan owner is using a proactive DMSMS process for minimizing the cost and impact that part and material obsolescence will have on equipment delivered by the Plan owner. The technical requirements detailed in clause 5 ensure that the Plan owner can meet the requirement of having a process to address obsolescence as required by Industry Standards such as EIA-4899 "Standard for Preparing an Electronic Components Management Plan" and DoD Programs as required by MIL-STD-3018 "Parts Management". Owners of DMSMS Management Plans include System Integrators, Original Equipment Manufacturers (OEM), and logistics support providers.
Standard

Implementation Guide for Data Management

2014-07-01
WIP
GEIAHB859A
The federal government and industry have moved to concurrent acquisition and development processes using integrated process teams (IPTs). These processes are supported by timely, accurate, cross functional access to data within an integrated data environment (IDE) enabled by advances in information technology (IT). Since the advent of acquisition reform in 1994, Data Management (DM) practices have evolved from being directed by a prescriptive set of standards and procedures to use of the guidance in a principles-based standard -- ANSI/EIA 859.

GEIA Handbook 859 provides implementation guidance for ANSI/EIA 859, with discussions of applications of the standard's principles, tools, examples, and case studies. Handbook 859 is organized according to the lifecycle of data management and covers activities from the pre-RFP stage through records disposition.

Standard

Standard Best Practices for System Safety Program Development and Execution

2018-11-19
WIP
GEIASTD0010B
This document outlines a standard practice for conducting system safety. In some cases, these principles may be captured in other standards that apply to specific commodities such as commercial aircraft and automobiles. For example, those manufacturers that produce commercial aircraft should use SAE ARP4754 or SAE ARP4761 (see Section 2 below) to meet FAA or other regulatory agency system safety-related requirements. The system safety practice as defined herein provides a consistent means of evaluating identified risks. Mishap risk should be identified, evaluated, and mitigated to a level as low as reasonably practicable. The mishap risk should be accepted by the appropriate authority and comply with federal (and state, where applicable) laws and regulations, executive orders, treaties, and agreements. Program trade studies associated with mitigating mishap risk should consider total life cycle cost in any decision.
Standard

FLIGHT SIMULATION TRAINING DEVICE (FSTD) – LIFE CYCLE SUPPORT

2019-10-16
CURRENT
ARINC434-2
This document will address measures pertaining to and directly associated with the maintainability and reliability of FSTDs throughout their entire life cycle, from initial specification and design to de-commissioning. Although the primary emphasis of this document is on full flight simulators (with motion and visual systems), it should be applicable in part or total to all FSTDs.
X