Browse Topic: Systems management

Items (110)

Digital Twin Simulation and Verification System Design and Implementation for Satellite Production Lines

2026-99-1804

7/17/2026

In this paper, we focus on satellite production lines and design and implement a digital twin simulation and verification system for them. This is to improve manual documentation efficiency and provide sufficient process controllability in the small satellites’ batch production and assembly testing. We built a layered architecture. This allows the system to dynamically interact with AIT data management systems, structured process systems, and equipment data by fusing multi-source data. We also develop functional modules that combine lightweight 3D model visualization, dynamic simulation engines, and hybrid scheduling optimization algorithms. These modules can perform twin simulation, execute processes, intelligently schedule production, manage work reporting, conduct intelligent analysis, trigger anomaly alarms, and perform system management. We also dynamically simulate complex workflows like satellite transfer and automated assembly. These workflows are then verified using 3D virtual scene modeling and physical engines. We use time-series analysis to improve scheduling accuracy and multidimensional dynamic monitoring and hierarchical response to enhance production stability. In practice, the system can provide visualized control over the full process of satellite production. This greatly improves assembly efficiency and process controllability. It can also be an extensible digital way for aerospace manufacturing. The use of hierarchical architecture design and multimodal data fusion can be further applied in the complex equipment intelligent manufacturing.

Zhao, Fenghua

Software Support Concept

JA1006_201205 (Current)

5/26/2026

This SAE Recommended Practice provides a framework for the establishment of a software support concept related to the support and supportability of both custom-developed and Off-the-Shelf (OTS) software. This document complements SAE AIR 5121, JA1004, and JA1005 by providing information needed to understand the support aspects that should be covered by a software supportability program. It should be noted that particular information indicated here should not be considered a complete list of all aspects of the support concept. In particular, the information should not be confused with a list of data elements. This document has general applicability to all sectors of industry and commerce and to all types of equipment that contain software. The target audience for this document includes software acquisition organizations, software logisticians, developers, supporters, and customers. This document is intended to be guidance for business purposes and should be applied when it provides a value-added basis for the business aspects of development, use, and sustainment of support-critical software.

G-41 Reliability

Requirements for a COTS Assembly Management Plan

EIA933D (Current)

4/20/2026

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, disk drives, 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) or by industry standards. An example at this end of the spectrum is a VME circuit card assembly. At the other end of the spectrum are COTS assemblies whose design, internal parts, materials, configuration control, and qualification methods are not controlled, or controllable, in any way by ADHP customers (either individually or collectively) or by industry standards. An example is a disk drive targeted for an industry other than ADHP use. It is critical for the Plan owner to: (1) review and understand the design, internal parts, materials, configuration control, reliability, and qualification methods of all “as-received” COTS assemblies and their capabilities with respect to their application in the intended System and environment; (2) identify risks; and where necessary (3) take additional action to mitigate the risks associated with the performance and reliability of the COTS assembly in the ADHP system.

APMC Avionics Process Management

Spacecraft System Health Management: Current Practices and Emerging Technologies

R-56612/12/2024

Ensuring the safe and reliable operation of spacecraft is a complex task that requires advanced technologies and innovative approaches. This comprehensive guide provides a deep dive into the world of spacecraft system health management. From understanding the intricacies of spacecraft systems to exploring cutting-edge technologies like AI and digital twins, this book offers a valuable resource for anyone interested in the field. Key Features: - Clear and accessible language: The book is written for both technical experts and general readers, making it easy to understand complex concepts. - Real-world examples: Case studies and examples from actual missions bring the theoretical concepts to life. - Future-focused: The book explores emerging technologies that are shaping the future of spacecraft health management, giving readers a glimpse into the future of space exploration. Whether you're a seasoned space engineer or simply curious about the wonders of space exploration, this book offers valuable insights into the critical role of system health management in ensuring mission success. In addition to its technical depth, the book also explores the broader implications of spacecraft health management. It discusses the ethical and societal considerations involved in space exploration and the importance of responsible innovation. By understanding these factors, readers can gain a well-rounded perspective on the field. Spacecraft System Health Management is an essential resource for anyone interested in the future of space exploration. It provides a comprehensive overview of the key concepts and technologies, making it a valuable tool for students, researchers, and professionals alike.

Khan, Samir

The Evolution of Configuration Management (CM) Into an Accelerating Digital World

SAE8579 (Current)

11/20/2023

The purposeful integration of existing and emerging technologies into CM practice will enable collaboration with supporting systems and provide stakeholders access to authoritative and trusted data in a timely fashion at their desktop to help drive educated decision making. This lays to rest the misguided myth that CM and supporting systems operate at cross-purposes. What does it mean to have CM in a world of new initiatives and 2-week sprints (i.e., time-boxed work periods), multiple increments producing Minimum Viable Products (MVP) and synchronized with Model Based Systems Engineering (MBSE) while being digitally transformed? MBSE initiatives drive the jump from “2D” data to “3D” data, thereby becoming a Model-Centric practice. Products now enable technology to push the product lifecycle management process to new levels of efficiency and confidence. This mindset is evidenced by five major functions of CM, as discussed below, and described in EIA-649C.

G-33 Configuration Management

A Review of Digital Twin for Vehicle Predictive Maintenance System

2023-01-1024

3/7/2023

The development of Digital Twin (DT) has become popular. A dominant description of DT is that it is a software representation that mimics a physical object to portray its real-world performance and operating conditions of an asset. It uses near real-time data captured from the asset and enables proactive optimal operation decisions. There are many other definitions of DT, but not many explicit evaluations of DT performance found in literature. The authors have an interest to investigate and evaluate the quality and stability of appropriate DT techniques in real world aircraft Maintenance, Repair, and overhaul (MRO) activities. This paper reviews the origin of DT concept, the evolution and development of recent DT technologies. Examples of DTs in aircraft systems and transferable knowledge in related vehicle industries are collated. The paper contrasts the benefits and bottlenecks of the two categories of DT methods, Data-Driven (DDDT) and Model-Based (MBDT) models. The paper evaluates the applicability of the two models to represent vehicle system management. The authors present their methodological approach on Predictive Maintenance (PM) development basing on reliable DT models for vehicle systems. This paper contributes to design, operation, and support of aircraft/vehicle systems.

Wang, Chengwei, Fan, Ip-Shing, King, Stephen

Easing Industrial-Grade Ethernet Implementation

TBMG-46756

11/3/2022

Ethernet is widely used among consumer and commercial systems throughout the world, and it is well understood by all levels of end-users. Due to economies of scale, coupled with availability of industrial-grade devices, Ethernet has also become suitable, and often dominant, for many types of more rigorous applications. Unfortunately, industrial-grade Ethernet devices are often associated with high costs and complex network management and configuration requirements.

Configuring Spacecraft’s On-Board Computing Systems

TBMG-45655

4/14/2022

Harwin Portsmouth, United Kingdom

The Future of Managing Mission-Critical Systems

22AERP04_044/1/2022

There's no doubt the complexity of aerospace design systems is constantly increasing, driven by new demands on architecture and next-generation technologies. As a result, the costs and time associated with the creation, certification and deployment of mission-critical electronics hugely heighten if the systems are not managed in a new way. The established approach of adopting an RTOS that can be certified in accordance with functional safety standards presents several challenges. The development and maintenance of an RTOS to meet the demanding objectives of (for example) FAA DO-178B/C DAL A is a considerable undertaking, which represents a significant investment for any system developer. The fact they are so complex means they also have substantial (and suboptimal) footprints. Functional safety standards should ideally minimize development overhead by permitting the separation of a software system into software items with the aim of placing as little of the system as possible into the more critical classes.

Industrial Software Integrates With IT

TBMG-39968

10/1/2021

Industrial programmable logic controllers (PLCs) and their associated operations technology (OT) software and communication protocols have traditionally been best suited for localized installations. They lacked the computing performance, connectivity options, and security needed to easily integrate them with higher-level information technology (IT) resources.

Data Formats and Practices for Life Cycle Cost Information

ARP4294A (Current)

9/10/2021

This SAE Aerospace Recommended Practice (ARP)4294 is directed at life cycle cost (LCC) analysis of aerospace propulsion systems and supplements AIR1939. Specific topics addressed by ARP4294 are listed below: a Propulsion system LCC element structure. b Information exchange and relationships with: (1) Aircraft manufacturer (2) Equipment suppliers (3) Customer c The relationship of the LCC element structure to work breakdown structures. d The relationship between LCC analysis and other related disciplines (e.g., technical (performance analysis, weight control, component lives), reliability, availability and maintainability (RAM), integrated logistic support (ILS), production and finance). e Classification of the accuracy and applicability of LCC assessments.

LCLS Life Cycle Logistics Supportability

Migrating Advanced Signal Processing Technology to Rugged SFF Platforms

TBMG-39861

9/1/2021

The latest data acquisition and signal processing devices are critical for capturing and manipulating wideband sensor signals for real-time radar, electronic countermeasures, EW, and SIGINT systems. These include new data converter technology and advanced FPGA designs, including the RFSoC (radio frequency system-on-chip).

Systems Engineering Capability Model

EIA731_1A (Current)

3/16/2021

The purpose of this Standard is to support the development and improvement of systems engineering capability.

G-47 Systems Engineering

Smart Transportation Methods: Optimizing Efficiency in urban commute

SAE-PP-001073/15/2021

The existing traffic junctions operate in a sequential order. The wait time in the signal depends on the existing vehicle queues in all lanes. Also it depends on the signal duration given for each lane. As we have seen, when the waiting time is too long, the solution is to build the underpass or fly overs in such junctions, so that movement of vehicles in one lane is not obstructed by other lanes, in the same plane. However in order to have the smooth vehicle movement in all directions, more such structures are needed. I.e More layers of road infrastructure are built on top of one another. This advantage comes with high expenditure on infrastructure. Often such solutions may not be affordable. In such circumstances, currently there are few alternatives. In this paper we are introducing one such method.

Babu, Jayashree, Devidas, Raghavendra

Processes for Engineering a System

EIA632A (Current)

2/23/2021

The purpose of this Standard is to provide an integrated set of fundamental processes to aid a developer in the engineering or reengineering of a system. Use of this Standard is intended to help developers a) establish and evolve a complete and consistent set of requirements that will enable delivery of feasible and cost-effective system solutions; b) satisfy requirements within cost, schedule, and risk constraints; c) provide a system, or any portion of a system, that satisfies stakeholders over the life of the products that make up the system. NOTE—The term product is used in this standard to mean: a physical item, such as a satellite (end product), or any of its component parts (end products); a software item such as a stand-alone application to run within an existing system (end product); or a document such as a plan, or a service such as test, training, or maintenance support, or equipment such as a simulator (enabling products). d) provide for the safe and/or cost-effective disposal or retirement of a system.

G-47 Systems Engineering

BEST PRACTICES FOR GROUND VEHICLE INTRUSION DETECTION SYSTEMS

2024-01-3866

8/11/2020

ABSTRACT Addressing the well-established need for accurate cyber situational awareness on military vehicles and weapons platforms, we developed a well-tested, robust Intrusion Detection System – Fox Shield™ – currently rated TRL-8. The system is described and the lessons learned during its development are discussed. The basic principles of our anomaly detectors are outlined, and the details of our innovative warning-aggregating Fuser are presented. Many attack detection examples are presented, using a publicly available CANbus dataset. Citation: E.I. Novikova, V. Le, M. Weber, C. Andersen, S.N. Hamilton, “Best Practices For Ground Vehicle Intrusion Detection Systems”, In Proceedings of the Ground Vehicle Systems Engineering and Technology Symposium (GVSETS), NDIA, Novi, MI, Aug. 13-15, 2020.

Novikova, Elena I., Le, Vu, Weber, Michael, Andersen, Cory, Hamilton, Samuel N.

758-4 Communications Management Unit (CMU) Mark 2

ARINC758-4 (Current)11/26/2019

This ARINC Standard specifies the ARINC 758 Mark 2 Communications Management Unit (CMU) as an on-board message router capable of managing various datalink networks and services available to the aircraft. Supplement 4 adds Ethernet interfaces, per ARINC Specification 664 Part 2. This will allow the CMU to communicate with IP based radio transceivers (e.g., L-Band Satellite Communication Systems (Inmarsat SwiftBroadband (SBB) and Iridium Certus), ACARS over IP, AeroMACS, etc.).

Airlines Electronic Engineering Committee

Logistics Product Data

GEIASTD0007C (Current)

11/6/2019

SAE GEIA-STD-0007C defines logistics product data generated during the requirement definition and design of an industry or government system, end item, or product. It makes use of the Extensible Markup Language (XML) through the use of entities and attributes that comprise logistics product data and their definitions. The standard is designed to provide users with a uniform set of data tags for all or portions of logistics product data. The standard can be applied to any industry or government product, system or equipment acquisition program, major modification program, and applicable research and development projects. This standard is for use by both industry and government activities. As used in this standard, the requiring authority is generally the customer and the customer can be a government or industry activity. The performing activity may be either a industry or government activity. The use of the term “contract” in this standard includes any document of agreement between organizations.

LCLS Life Cycle Logistics Supportability

Defining an Open System Architecture Standard for Defense Systems

TBMG-3535510/1/2019

For many years now, there have been efforts within the US defense community to adopt “Open System Architecture” principles (or OSA) for defense computing platforms. Stretching back to the mid-2000’s there have been numerous efforts by all service branches to define sets of OSA principles or requirements on the embedded computing systems they procure and deploy. While these efforts have resulted in widespread adoption of POSIX functions for common tasks and a gradual shift in the use of common form factors and technologies such as VPX and Ethernet, there are still wide disparities between products from different suppliers, which creates difficulties for integrators. Product variations also make technology insertions or system configuration changes expensive, time consuming, and often locked to a particular vendor.

820 Cabin Architecture for Wireless Distribution System

ARINC820 (Current)8/13/2019

This document defines a secure Wi-Fi distribution network installed in the aircraft passenger cabin for passenger and crew use. Carry-on Portable Electronic Devices (PEDs) such as smart phones, tablets, and laptops may use this network to access public internet services provided on the aircraft.

Airlines Electronic Engineering Committee

Standard Practice for Human Systems Integration

SAE6906 (Historical)

2/8/2019

This Human Systems Integration (HSI) Standard Practice identifies the Department of Defense (DoD) approach to conducting HSI programs as part of procurement activities. This Standard covers HSI processes throughout design, development, test, production, use, and disposal. Depending on contract phase and/or complexity of the program, tailoring should be applied. The scope of this standard includes prime and subcontractor HSI activities; it does not include Government HSI activities, which are covered in the DoD HSI Handbook. HSI programs should use the latest version of standards and handbooks listed below, unless a particular revision is specifically cited in the contract.

G-45 Human Systems Integration

Standard Best Practices for System Safety Program Development and Execution

GEIASTD0010A (Current)

10/18/2018

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. This document is intended for use as one of the elements of project solicitation for complex systems requiring a systematic evaluation of hazards and mitigating measures. The Managing Authority may identify, in the solicitation and system specification, specific system safety requirements to be met by the Developer. These may include risk assessment and acceptance criteria, unique classifications and certifications, or mishap reduction needs unique to their program. Additional information in meeting program specific requirements is located in the Appendixes.

G-48 System Safety

GUIDANCE FOR USAGE OF DIGITAL CERTIFICATES

ARINC842-2 (Current)7/11/2018

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

Airlines Electronic Engineering Committee

WCX18 Day 1 Highlights

123474/11/2018

Highlights and interviews from the first day of WCX18

System and Method for Managing Autonomous Entities Through Apoptosis

TBMG-287064/1/2018

This NASA innovation is a biologically inspired system management method designed to make sensor webs as well as other autonomous and autonomic systems more self-directing and self-managing. Based on the mechanisms of cell apoptosis, this method ensures safe and correct operation over time by enabling self-destruct, self-sleep, or standby actions in response to potentially harmful or compromising situations. The capabilities provided by this technology will benefit systems such as sensors, computer systems, and spacecraft.

Security for Plug-In Electric Vehicle Communications

J2931/7_201802 (Current)

2/15/2018

This SAE Information Report J2931/7 establishes the security requirements for digital communication between Plug-In Electric Vehicles (PEV), the Electric Vehicle Supply Equipment (EVSE) and the utility, ESI, Advanced Metering Infrastructure (AMI) and/or Home Area Network (HAN).

Hybrid - EV Committee

Security for Plug-In Electric Vehicle Communications

J2931/7_201710 (Historical)

10/2/2017

Hybrid - EV Committee

Cooling Your Embedded System

17AERP02_022/1/2017

What Can Your Open Standard Architecture Handle? Embedded computing systems for Mil/Aero applications are often conduction-cooled in an ATR or nonstandard chassis. However, there are many designs that require 19″ rackmount systems with forced-air cooling. As more processing performance is packed into tight spaces, enclosures that provide advanced cooling options are increasingly common. The open-standard embedded architectures have different recommended limitations for power. Sometimes these are electrical pinout limitations, and other times they are recommended thermal limitations. There are “tricks of the trade” to extend the power for certain architectures as well as the ability to maximize the thermal limits.

Cooling Your Embedded System: What Can Your Open Standard Architecture Handle?

TBMG-264372/1/2017

Embedded computing systems for Mil/Aero applications are often conduction-cooled in an ATR or nonstandard chassis. However, there are many designs that require 19" rackmount systems with forced-air cooling. As more processing performance is packed into tight spaces, enclosures that provide advanced cooling options are increasingly common.

Handbook of System Data Communications

AIR4271A (Current)

10/21/2016

This Aerospace Information Report (AIR) has been prepared by the Systems Applications and Requirements Subcommittee of SAE Committee AS-2. It is intended to provide guidance primarily, but not exclusively, for specifiers and designers of data communication systems for real time military avionics applications within a platform. The subject of high speed data transmission is addressed from two standpoints: (1) the influence of developments in technology on avionics architectures as a whole and (2) the way in which specific problems, such as video, voice, closed loop control, and security may be handled. While the material has been prepared against a background of experience within SAE AS-2 relating to the development of a family of high speed interconnect standards, reference to specific standards and interconnect systems is minimized. It should be noted, however, that many of the concepts described require interconnect systems with advanced operational and performance characteristics, such as those developed by SAE AS-2.

AS-1A Avionic Networks Committee

Statement on Requirements for Real-Time Communication Protocols (RTCP)

AIR4886A (Current)

10/21/2016

The purpose of this document is to establish the requirements for Real-Time Communication Protocols (RTCP). Systems for real-time applications are characterized by the presence of hard deadlines where failure to meet a deadline must be considered a system fault. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms and commercial aircraft, but are generally applicable to any distributed, real-time, control systems. These requirements are primarily targeted for the Transport and Network Layers of peer to peer protocols, as referenced in the Open System Interconnect Reference Model (2.2.1 and 2.2.2), developed by the International Standards Organization (ISO). These requirements are intended to complement SAE AS4074 (2.1.1) and AS4075 (2.1.2), and future SAE communications standards. Although information transfer objectives herein concentrate primarily on digital data flow attributes, efforts have been made such as not to preclude sensor/video and voice information transfers. This document provides evaluation criteria for selecting viable alternatives for a real-time communications protocol standard.

AS-1A Avionic Networks Committee

Loss-of-Control Mishaps in Revenue Airline Service

AIR6237 (Current)

7/12/2016

The scope of this document is to provide review of recent history of loss-of-control accidents during airline revenue operations.

S-7 Flight Deck Handling Qualities Stds for Trans Aircraft

Systems Engineering

EIAIS632 (Current)

7/1/2015

This standard defines a total system approach for the development of systems. The standard requires: establishing and implementing a structured, disciplined, and documented systems engineering effort incorporating the systems engineering process; multidisciplinary teamwork; and the simultaneous development of the products and processes needed to satisfy user needs. The systems engineering process is defined generically to facilitate broad application. This standard defines the requirements for technical reviews. The tasks in this standard provide a methodology for evaluating progress in achieving system objectives. This standard provides a comprehensive, structured, and disciplined approach for all life-cycle phases, including new system product and process developments, upgrades, modifications, and engineering efforts conducted to resolve problems in fielded systems. This standard is applicable to technical efforts in support of advancement and development of new technologies and their application. It applies to large and small scale systems; to single or multiple procurements; and to the replacement of current products and processes. The standard is applicable to systems irrespective of composition including those that are integrated from diverse elements, hardware dominant, and software dominant. This document should be tailored for effective and efficient program implementation. Systems engineering involves design and management of a total system which includes hardware and software, as well as other system elements. All system elements should be considered in analyses, trade-offs, and engineering methodology.

G-47 Systems Engineering

Integration Engineering for System Effectiveness

EQB2 (Current)

7/1/2015

G-47 Systems Engineering

Systems Engineering Capability Model

EIAIS731_1 (Current)

7/1/2015

The purpose of this Interim Standard is to support the development and improvement of systems engineering capability.

G-47 Systems Engineering

MicroTCA Computing for Mil/Aero Applications

TBMG-218844/1/2015

Small Form Factor (SFF) embedded systems have been gaining popularity due to their small size, weight, and power (SWaP) advantages. The SFF architectures are typically purpose-built, providing just a few specific functions. But, the performance level is often limited and the versatility and re-usability across multiple applications is typically very low. Is a balance available where there is high performance and versatility in an open standard architecture, but a compact size that is optimized for SWaP-C (C stands for cost)?

Mil-Aero Design Embraces Intelligent Application-Ready ATCA Platforms

TBMG-2117412/1/2014

Telecommunications design continues its evolution toward higher bandwidth and performance, fueled by growth in Giga-bit Ethernet, wireless network systems and competitive business models incorporating multi-play network services. Similar data-rich applications characterize military design, with a broad spectrum of image-intensive applications powering modern warfare. With fewer troops on the ground, more use of reconnaissance gathered via autonomous vehicles, and real-time feeds informing command and operations, system developers must deliver more network-centric solutions and applications that offer ideal support to today's warfighter.

The Next Generation of Systems Engineering: A Report by the GEIA G-47 Systems Engineering Panel

GEIASE0001 (Current)

10/1/2014

Systems Management Council

Reviews and Configuration Audits

CMB6_6 (Current)

10/1/2014

G-33 Configuration Management

Education in Configuration and Data Management

CMB6_10 (Current)

10/1/2014

Assist CM and engineering personnel in the implementation and coordination of CM unique procedures and disciplines of Configuration Identification, Change Control, Status Accounting and Audits.

G-33 Configuration Management

Configuration and Data Management References

CMB6_1C (Current)

10/1/2014

G-33 Configuration Management

Configuration Control

CMB6_4 (Current)

10/1/2014

This Interface Control Plan establishes a program for interface control among the major segments/equipments of a DoD program. This could be an airborne weapon system, Medium Launch Vehicle System, Space Launch Complex System, etc. The program is based on formal agreements between participating organizations, and includes (1) documentation to establish, define and control interface requirements and to detail interface design definition between system segments, (2) interface management under the purview of the Interface Management Boards (IMB) and (3) interface control, through Interface Control Working Groups (ICWGs). The plan establishes the IMB and ICWG policy and procedures. Furthermore, it sets forth the Government Agencies Program Offices, associate contractors and participating Government Agency responsibilities in support of the Interface Control Program and the conduct of interface management/control through the IMBs, and ICWGs.

G-33 Configuration Management

Handbook: The Program Managers' Guide to the Integrated Baseline Review Process

GEIAHB748_1 (Current)

10/1/2014

This guide clearly defines the purpose, goals, and objectives of an IBR. It also describes the attributes of an effective IBR and discusses a baseline review process that will lead to a better understanding of program risks. It provides a common definition and framework for the IBR Process. This process harmonizes, and to the extent possible, unifies the management objectives for all PMs. The IBR Process enables managers to effectively utilize the project Performance Measurement Baseline (PMB) to assess performance, and to better understand inherent risks. The IBR Process should continue throughout the life of a project.

G-47 Systems Engineering

830 Aircraft/Ground Information Exchange (AGIE) Using Internet Protocol

ARINC830 (Current)9/15/2014

The purpose of this document is to define a general purpose non-proprietary information exchange framework and protocol for the conduct of Internet Protocol based message traffic between aircraft and airline ground infrastructure. This standard is motivated by the vision to substantially simplify information processing management for airlines by eliminating multiple dissimilar implementations with a single universal system and thereby establishing a more economical environment.

Airlines Electronic Engineering Committee

IMPLEMENTING UNIFIED COMMUNICATIONS VIA A SINGLE SWAP-C DEVICE

2024-01-3448

8/12/2014

ABSTRACT Communications has come a long way from the two dimensional model provided by voice and data. Today complete situational awareness requires bringing a third dimension, video, into the mix. Implementing this unified view into today’s military vehicles calls for a unit with a well thought out design that interfaces thoroughly with other equipment and minimizes SWAP-C impact. This paper addresses the efficient convergence of video with existing voice and data presenting unified communications into a single SWAP-C device.

Elms, Brett, Nair, Unni, D’Agostino, Rosemarie

Technical Architecture for Aircraft, Launcher, and Weapon Interoperability (ALWI TA)

AIR5720A (Current)

8/27/2012

The technical architecture defined in this document outlines mandatory, emerging, and needed standards to provide interoperability at key interfaces in the aircraft/store system (including an associated NATO Network Enabled Capability environment), as required to support a future plug-and-play aircraft/store integration capability. These standards relate to services and protocols associated with the subject interfaces. Modeling standards to facilitate the Model Driven Architecture® (MDA®) approach to system definition and implementation are also included. Note that the status of referenced standards as reflected in this document is as of August 2007, and document users should check to see if there has been a subsequent change of status relative to applicable standards.

AS-1B Aircraft Store Integration Committee