Browse Topic: Systems management
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
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
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
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
Harwin Portsmouth, United Kingdom
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
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
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
ARINC 858 Part 1 defines the airborne data communication network infrastructure for aviation safety services using the Internet Protocol Suite (IPS). ARINC 858 builds upon ICAO Doc 9896, Manual on the Aeronautical Telecommunication Network (ATN) using Internet Protocol Suite (IPS) Standards and Protocol. IPS will extend the useful life of data comm services presently used by operators, e.g., VDL, Inmarsat SBB, Iridium NEXT, and others. It represents the evolutionary path from ACARS and ATN/OSI to the end state: ATN/IPS. ARINC 858 includes advanced capabilities such as aviation security and mobility. This product was developed in coordination with ICAO WG-I, RTCA SC-223, and EUROCAE WG-108
This document provides a description of a process for development of fly-by-wire actuation systems. Included are (1) the development of requirements for the servo-actuator hardware and the electronics hardware and software, (2) actuator and servo-electronics interface definitions and, (3) the required communications and interactions between the servo-actuator and the servo-electronics designers
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
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
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
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
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
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
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
Items per page:
50
1 – 50 of 109