Browse Topic: Needs assessment

Items (197)
Find
Enabling Novel Collaborative Control Paradigms between Humans and Machines in Electric Vertical Takeoff and Landing (eVTOL) AircraftF-0081-2025-03595/20/2025
Electric Vertical Takeoff and Landing (eVTOL) vehicles undergoing advanced air mobility (AAM) operations feature increasingly autonomous systems (IAS) with non-traditional role allocations. Ensuring the safety of these operations and their novel human–machine teaming (HMT) paradigms requires an appropriate body of knowledge created through relevant, reproducible research. In this paper, we briefly examine the meaning of teaming; current regulation, standards, and guidance; and the knowledge required to build resilient HMTs before turning our attention to how this knowledge is being created by recent research and what conclusions or recommendations can be made. We identify the need for further research into the holistic performance of HMTs, the effect of novel allocations of roles between humans and machines, the ability of humans to provide resilience to unforeseen dangers when acting as a part of these teams; and the characteristics required for clear, timely, and accurate communication between the humans and machines. This work is done in the context of eVTOL aircraft with an indirect flight control system (IFCS) undergoing urban air mobility operations.
Neogi, Natasha, Graydon, Mallory, Holbrook, Jon, Maddalon, Jeffrey, McCormick, Frank
Standard Practice for HabitabilitySAE1007 (Historical)9/14/2021
This Standard specifies the Habitability processes throughout planning, design, development, test, production, use and disposal of a system. Depending on contract phase and/or complexity of the program, tailoring of this standard may be applied. The primary goals of a contractor Habitability program include: Ensuring that the system design complies with the customer Habitability requirements and that discrepancies are reported to management and the customer. Identifying, coordinating, tracking, prioritizing, and resolving Habitability risks and issues and ensuring that they are: ○ Reflected in the contractor proposal, budgets, and plans ○ Raised at design, management, and program reviews ○ Debated in Working Group meetings ○ Coordinated with Training, Logistics, and the other HSI disciplines ○ Included appropriately in documentation and deliverable data items Ensuring that Habitability requirements are applied to all personnel environments, including operators, maintainers, trainers, and support personnnel. Identifying and pursuing opportunities to reduce Habitability costs. Ensuring that Habitability considerations are addressed in analyses, design decisions, trade-offs, and design changes (e.g., Engineering Change Proposals (ECP)). Conducting Habitability analysis activities and supporting human factors analyses (e.g., workload analysis) and other HSI domain analyses to provide evidence to support design decisions and trade-offs and to coordinate shared data. Ensuring that Habitability analyses, results and recommendations are timely, technically competent/complete, and included in design decisions, tradeoffs, and changes. Ensuring that environments experienced by subjects in experiments, simulations, tests, evaluations, and demonstrations are consistent with the customer’s Habitability requirements and meet the U.S. Government and DoD policies for protecton of human subjects. Ensuring that Habitability issues discovered in test, evaluation, demonstration, Operational Test and Evaluation (OT&E), and operations are resolved in a technically competent/complete and timely manner.
G-45 Human Systems Integration
Human Engineering - Principles and PracticesHEB1D (Current)4/14/2021
This Engineering Bulletin and its annexes provide guidance on the application of Human Engineering principles and practices to the analysis, design, development, testing, fielding, support, accident investigation, and training for military and commercial products throughout their intended life cycles.
G-45 Human Systems Integration
Systems Engineering Capability Model Appraisal MethodEIA731_2A (Current)3/16/2021
G-47 Systems Engineering
Systems Engineering Capability ModelEIA731_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
Processes for Engineering a SystemEIA632A (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
1.1.204 - Cost Effective Emergency Intimation System Design for AutomobilesSAE-PP-002192/2/2021
The death toll due to traffic accidents in India is on a rise, according to the latest Road Transport ministry report, a total of 4.97 lakh road accident was reported in 2011. Though compared to 2010, the accidents have gone down by 1,945, the number of deaths at 1,42,485 has increased by over 7,000.[1] This paper proposes a design of an Emergency Intimation System (EIS) tailored to fit for Indian consumer needs and available infrastructure. EIS is an emergency alert technology devised to assist drivers and passenger in an event of vehicle crash. Majority of deaths are caused by slow accident response time. EIS is aimed to lower this response time and ensure that the required rescue and medical services are made available in time. This device employed to make this emergency alerts will be fitted into the vehicle Electrical and Electronics (E/E) architecture and will have interfaces with crash sensor network, CAN network and GSM etc. In an event of crash, this device shall send an SMS to In Case of Emergency contacts identified by the vehicle owner. The SMS shall comprise of information like location (Vehicle co-ordinates), airbag deployment status and time stamp (Minimum Set of Data).
Mutagaana, Festo
Standard Practice for Manpower and PersonnelSAE1010 (Historical)9/18/2020
This Standard covers Manpower and Personnel (M&P) processes throughout planning, design, development, test, production, use, and disposal of a system. Depending on contract phase and/or complexity of the program, tailoring can be applied. The scope of this standard includes Prime and Sub-contractor M&P activities; it does not include Government M&P activities. The primary goals of a contractor M&P program typically include: Ensuring that the system design complies with the latest customer manpower estimates (numbers and mix of personnel, plus availability) and that discrepancies are reported to management and the customer. Ensuring that the system design is regularly compared to the latest customer Personnel estimates (capabilities and limitations) and that discrepancies are reported to management and the customer. Identifying, coordinating, tracking, and resolving M&P risks and issues and ensuring that they are: ○ Reflected in the contractor proposal, budgets, and plans. ○ Raised at design, management, and program reviews. ○ Debated in Working Group meetings. ○ Coordinated with Training, Logistics, and the other HSI disciplines. ○ Included appropriately in documentation and deliverable data items. Identifying and pursuing opportunities to reduce Manpower and Personnel demands and costs. Ensuring that M&P considerations are addressed in analyses, design decisions, trade-offs, and design changes (e.g., ECPs). Conducting Manpower and Personnel analysis activities and supporting human factors analyses (e.g., workload analysis) and other HSI domain analyses to provide evidence to support design decisions and trade-offs and to coordinate shared data (e.g., task analyses). Ensuring that M&P analyses and results are timely, technically competent/complete, and in a format that enables them to be included in design decisions, tradeoffs, and changes. Ensuring that M&P issues discovered in test, evaluation, demonstration, Operational Test and Evaluation (OT&E), and operations are tracked and resolved in a technically competent/complete and timely manner. Ensuring that the subjects used in experiments, simulations, tests, evaluations, and demonstrations are consistent with the customer’s latest projected target audiences.
G-45 Human Systems Integration
Rationale, Considerations, and Framework for Data Interoperability for Health Management within the Aerospace EcosystemAIR6904 (Current)4/21/2020
This SAE Aerospace Information Report (AIR) offers an overview of the aspects of intellectual property (IP) protection, legislative compliance, business model, and technologies which need to be considered and addressed to implement a data interoperability, secure business model and technology platform to enable prognostics and health management (PHM) in the digital age. While this information report is restricted to the aerospace domain and also to commercial aviation, the concepts are applicable to any other domain that employs data for supporting health management functionality.
G-31 Electronic Transactions for Aerospace Committee
The Navigator19AVEP09_029/1/2019
No trust in AI systems without data protection When people surround themselves with microphones and cameras, others will be listening and watching. This reality shouldn't come as a surprise, but remarkably it does. The advent of automated driving will dramatically expand this activity. In fact, it is already creating controversy. At its core is the challenge of training so-called artificial intelligence systems. As human children, we learn in large part through the guidance we get from parents, teachers and other caregivers. AI systems are no different. They ingest data and “learn” from it. But just as children must be shown the difference between red and green, a circle and a square, or A and Z, machine learning systems need data that has been labeled.
Effects of Transition Modeling on the Simulation of Helicopter Rotor HubsF-0075-2019-145225/13/2019
No abstract. Part of Introduction: Helicopter rotor hubs are geometrically complex components that experience a wide rage of aerodynamic behaviors and flow physics. This includes strong unsteadiness, large amounts of separation, laminar-turbulent transition, and interactional aerodynamic behaviors (Ref. 1). At high forward flight speeds (high advance ratios), the parasitic drag of the hub accounts for O(30 percent) of the total power required to fly (Ref. 1). A common method for characterizing this contribution is the hub drag factor, Kf e, which correlates the flat-plate area of the hub with the helicopter gross weight and functions as a technology factor (Ref. 2). In a recent assessment of needs for future vertical lift systems, Ormiston suggested that the hub drag factor needs to be reduced from the current state of the art of Kf e = 0:5 down to a value 0.2 (Ref. 3).
Coder, James
On-Road and Chassis Dynamometer Evaluation of a Pre-Transmission Parallel PHEV2019-01-03654/2/2019
This paper details the vehicle testing activities performed during the Year 4 of the EcoCAR 3 competition by the Wayne State University team on a Pre-Transmission Parallel PHEV. The paper focuses on two main testing platforms: the chassis dynamometer and the closed-course track (on-road). The focus of the former is to evaluate the emissions and energy consumption associated with different driving scenarios, while the latter has been used to assess the vehicle performance and their impact on the consumer appeal. The paper presents the objectives of each test, the setup accomplished for the different vehicle testing platforms, the results obtained and the comparison with the values expected from simulations. In addition, the impact of the results on the refinement of the control strategies and on the validation of the simulation models are discussed. The EcoCAR 3 competition challenges sixteen North American universities to re-engineer a 2016 Chevrolet Camaro to reduce its environmental impact without compromising performance and consumer acceptability. Over the course of Year 4 the Control and Modeling and Simulation team used various simulation platforms to test the control algorithms designed for each operational mode of the vehicle. While Model-in-the-Loop (MIL) and Hardware-in-the-Loop (HIL) environments have been the main focus of Year 2 and Year 3, during this last competition year a considerable amount of time has been spent on chassis dynamometer and closed-course vehicle testing. The control strategies have been tested over a variety of drive cycles to identify the need for refinements and improve the robustness of the algorithms. In addition, the results obtained have been used to validate the components plant model and to support further development of the operational strategies within the non-vehicle platforms.
Di Russo, Miriam, Arora, Vaibhav, Lyu, Ronghui, Ku, Jerry C.
Increasing Development Assurance for System and Software Development with Validation and Verification Using ASSERT™2019-01-13703/19/2019
System design continues to trend toward increasing complexity as more functionality is added to aviation systems and the level of automation is increased. Since exhaustive validation and verification of this functionality becomes increasingly difficult, reliance on development assurance is needed to provide confidence that errors in requirements, design and implementation have been identified and corrected. To address this need for increased development assurance, GE is introducing a tool called ASSERT™ (Analysis of Semantic Specifications and Efficient generation of Requirements-based Tests). The system developer uses this tool to capture requirements in an unambiguous way with built-in semantic error checking. The requirements analysis engine is then used to assist in requirements validation to identify common problems which may include requirements that conflict with one another, requirements that do not fully specify the behavior of a function, requirements that are not independent of one another, and requirements that are either always true or false. Having unambiguous and complete requirements also enables the tool to consistently generate a complete set of requirements-based test cases and procedures to ensure the implemented product performs its intended functions and only the intended functions. This paper will detail how the ASSERT™ tool assists the system developer in performing validation and verification to increase development assurance on an example representative aerospace product beyond what a system developer could traditionally do on their own.
McMillan, Craig, Crapo, Andy, Durling, Michael, Li, Meng, Moitra, Abha, Manolios, Panagiotis, Stephens, Mark, Russell, Daniel
Proactive Cybersecurity Saves Healthcare Organizations from Data BreachesTBMG-339933/1/2019
Over the past few years, healthcare organizations have increasingly become one of the leading targets for cyber criminals with data breaches exposing personal patient data, medical records, and financial information, resulting in millions of dollars of added cost to these institutions. As the healthcare organizations become savvier with their cybersecurity, the criminals just get more creative.
Standard Practice for Human Systems IntegrationSAE6906 (Current)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
Configuration Management StandardEIA649C (Current)2/7/2019
This standard defines five CM functions and their underlying principles. The functions are detailed in Section 5. The principles, highlighted in text boxes, are designed to individually identify the essence of the related CM function and can be used to collectively create a checklist of “best practice” criteria to evaluate a CM program. The CM principles defined in this standard apply equally to internally focused enterprise information, processes, and supporting systems (i.e., Enterprise CM - policy driven, supporting the internal goals needed to achieve an efficient, effective and lean enterprise), as well as to the working relationships supported by the enterprise (i.e., Acquirer/Supplier CM - contracted relationship to support external trusted interaction with suppliers). In an Enterprise CM context there are several methodologies for principle use by the enterprise: The principles of this standard provide direction for developing enterprise or functional CM plans focused on identifying, defining, authorizing, and managing CM activities. These plans identify the participants involved in activities, their responsibilities, their authority, and how accountability is administered to serve enterprise/activity objectives. The Enterprise uses CM’s integrity-based traceability and management capabilities as a foundation to support the “best practice” initiatives of data/information management, quality assurance, program/project management, systems engineering and life cycle logistics, by providing principle-guided functions to achieve a more efficient, effective and lean enterprise. In the Acquirer/Supplier CM context there are several methodologies for conformance by a supplier: Acquirer requires a CM plan consistent with the principles of this standard from the supplier. Acquirer uses this standard to develop a checklist with which to evaluate supplier CM plans. Acquirer reviews and approves the supplier CM plan and makes it a requirement of the contract. This method requires both parties to the acquisition to understand both the concepts and the tailoring. Acquirer uses the principles of this standard as the basis for developing either or both an enterprise CM requirements document or a specific project CM requirements document to impose on suppliers. The requirements documents may state this standard’s principles as requirements and reference this standard’s paragraphs. Compliance with the contractual requirements constitutes conformance with this standard. In describing each CM function and its principles, this standard utilizes neutral Configuration Management terminology, while also providing equivalent terms, that have historically been used in various product environments (see Table 2). There is no intent to express a preference for any particular set of terminology. Similarly, this standard uses a neutral set of names for the phases of a product’s life cycle, which are generic enough to be easily mapped to the myriad of different life cycle models in use. Table 1 illustrates some of the aliases for each phase name and identifies characteristics that apply to each one. Regardless of the titles chosen for these phases, or what the product is (i.e., a facility, software, an airplane or a machine screw), at some point in its history a product will go through all or most of these phases. The phases can have considerable overlap, or the sequence of the phases might change or be repeated, e.g., for product improvements and enhancements. Approved configurations of a product can be in the build, distribution, operation, and disposal phases simultaneously, and changes to those configurations may occur during all life cycle phases. Appropriate application of CM functions enables a user of this standard to plan and implement a CM program for a product, project, or enterprise. All functions apply during every phase of the product’s life cycle but the degree to which each of the CM principles applies may vary. A scalable CM process should be defined, measured, continuously improved, and adhered to, that is commensurate with the product’s complexity, its intended use, and its value over the product life cycle. An organization that has the responsibility for performing Configuration Management for a product during any period of its life cycle could be a commercial enterprise, e.g., contractor, subcontractor, supplier, or government agency. References in this standard to the acquirer (i.e., customer) should be interpreted as the entity that specifies requirements (functional and performance attributes) for the product or that acquires and uses the product. An acquirer may be external to the developing and producing organization or may be internal such as marketing, management, or the using department. Configuration Management functions related to a product may be the responsibility of several organizations during its life cycle. For example, an organization with the responsibility to design and build a product will perform Configuration Management during the definition and build phases; other organizations or government activities with responsibility for upgrading the product and servicing units will perform Configuration Management during the operation phase. GEIA-HB-649 “Configuration Management Standard Implementation Guide,” provides additional “how to” guidance for planning, managing, and implementing CM functions and principles.
G-33 Configuration Management
Got Your Game Plan? The OEM Playbook to Navigating Preclinical Device Testing Under MDR and ISO 10993-1TBMG-337352/1/2019
When the Medical Device Regulation (MDR) replaces the Medical Device Directive (MDD) in 2020, requirements for medical devices in Europe will present greater regulatory hurdles. In addition, ISO 10993-1, created by the International Organization for Standardization (ISO) Committee and mandated by both the FDA and MDR also introduce new requirements for pre-clinical safety device testing. Medical device manufacturers are feverishly working to navigate the changes and develop their preclinical device testing strategies to overcome what's not just a regulatory hurdle, but a business challenge.
An Engine Stop Start System with Driver Behavior Learning and Adaption for Improving the User Experience2018-01-06094/3/2018
Engine Stop/Start System (ESS) promises to reduce greenhouse emissions and improve fuel economy of vehicles. Previous work of the Authors was concentrated on bridging the gap of improvement in fuel economy promised by ESS under standard laboratory conditions and actual driving conditions. Findings from the practical studies lead to a conclusion that ESS is not so popular among the customers, due to the complexities of the system operation and poor integration of the system design with the driver behavior. In addition, due to various functional safety requirements, and traffic conditions, actual benefits of ESS are reduced. A modified control algorithm was proposed and proven for the local driving conditions in India. The ways in which a given driver behaves on the controls of the vehicles like Clutch and Brake Pedals, Gear Shift Lever were not uniform across the demography of study and varied significantly. In addition, Authors also discovered that some drivers also deployed the parking brake during an idle stop. Thus, a concept of autonomous learning algorithm was envisaged, which would learn the driver behavior on the controls which influence the functions of ESS and then adapt the same conditions to trigger the auto engine stop and restart. This was aimed at improving the user experience and yet ensure the benefits of the ESS. In this paper, the findings from previous works are analyzed to make grounds for the new submission and to identify the need for User Experience of ESS. The solution implemented to detect the driver behavior from the set of possible ways is discussed in detail and simulation case studies are discussed to ascertain the functions and benefits of the new algorithm.
Athani, Gopal, Gavarraju, Srinivasa Raju, Jain, Punit, Addala, Shashank, P, Satishkumar
Implementing IEC 62304 for Safe and Effective Medical Device Software — PART 1TBMG-2772210/1/2017
Monitoring and Control of Hybrid Test Systems2017-01-21199/19/2017
Hybrid test systems are gaining more and more significance in the aerospace industry. At the heart of these systems is a standardized communication infrastructure. There are many challenges when designing the communication infrastructure. For example, it requires very specific knowledge to boot a hybrid system, manage its configuration process, and start and stop the execution of applications, such as simulations, panels or recorders. Likewise, when testers use a heterogeneous test environment, they cannot commit themselves too much to every single test means and its special characteristics. Nevertheless, testers must always be able to monitor and control every test system. This means, they must be able to determine the current overall system status and the current status of its components and parts. Examples for this are hardware components, such as real-time processors and I/O boards, as well as software applications, such as real-time simulations models on the test system. Based on this, the user needs to be able to efficiently control the test bench and appropriately react to error situations. For the hybrid test system, this means that each of its modules must follow a common concept for status monitoring and control. Naturally, this is not the case as every supplier has their own specific methods and concepts for these tasks. The aim of this paper is to present concepts for hybrid test benches incorporating systems from different suppliers. These concepts are based on the idea of a communication infrastructure that supplies the standardized transport mechanism required for interoperability. As a first step, the requirements for cross-vendor status monitoring and control are analyzed with a particular emphasis on developing a common basis. Subsequently, a basic concept is presented for both status monitoring and control. The goal is to find mechanisms that can be used to establish a standard.
Stockmann, Lars, Himmler, Andreas
Designing Cybersecurity into Connected Medical DevicesTBMG-273188/1/2017
Cyber threats to health delivery organizations (HDOs) and the medical device industry as a whole have hit a new level of maturity in the last year. A decade ago, the attack scene was dominated by academic papers about theoretical attacks on connected medical devices.1 Then we started seeing data breaches on connected medical devices primarily as a means to access personal healthcare information.2 In the last year, however, at least two major events occurred where attackers directly monetized attacks on medical devices. In August 2016, a short stock seller openly published video and details about cybersecurity attacks on a medical device maker’s implantable cardiac devices. Predictably, the device manufacturer’s stock fell.3 In May 2017, the WannaCry ransomware compromised both hospital systems and medical devices. While there are multiple reasons each attack succeeded, it is clear that attackers are becoming bolder, and medical devices are not immune.
Joint Military and Commercial Rotorcraft Mechanical Diagnostics Gap AnalysisF-0073-2017-120775/9/2017
ABSTRACT A group of rotorcraft original equipment manufacturers (OEMs) and military and commercial operators have come together to review the current state of mechanical diagnostics (MD) for on board rotorcraft Health and Usage Monitoring Systems (HUMS). HUMS has become an integral part of the modern rotorcraft both in commercial and military operations to enhance safety and enable Condition-Based Maintenance (CBM). Commercial oil and gas operators depend on the HUMS vibration monitoring and MD to comply with regulations and customer requirements for ensured safety of off-shore transportation. Under the auspices of the HUMS Technical Committee within the American Helicopter Society (AHS), the authors have assessed the performance of HUMS MD through both quantitative and qualitative means. First, results from the U.S. Army fleet, which comprises thousands of deployed HUMS on multiple aircraft models, were examined. Second, qualitative surveys of both commercial/military operators and rotorcraft/HUMS original equipment manufacturers (OEMs) were completed. Finally, a literature survey focused on HUMS research and development (R&D) and operational analysis was conducted. Based on this assessment, gaps in the performance of current HUMS MD, needs for future R&D, and challenges to closing those gaps are identified. Collaborative, pre-competitive efforts are also recommended to help close the gaps and generally raise the performance of HUMS MD to enable further enhancements to safety and to support expanded CBM initiatives.
Wade, Daniel, Tucker, Brian, Davis, Mark, Knapp, Doug, Hasbroucq, Sophie, Saporiti, Moreno, Garrington, Malcom, Rudy, Alexander
Approaches to Determining Beneficial Use of Simulink and UML in Automotive Embedded Software Systems *CSP Meta QA Testing*2017-01-00083/28/2017
Simulink is a very successful and popular method for modelling and auto-coding embedded automotive features, functions and algorithms. Due to its history of success, university feeder programs, and large third party tool support, it has, in some cases, been applied to areas of the software system where other methods, principles and strategies may provide better options for the software and systems engineers and architects. This paper provides approaches to determine when best to apply UML and when best to apply Simulink to a typical automotive feature. Object oriented software design patterns as well as general guidelines are provided to help in this effort. This paper's intent is not to suggest a replacement for Simulink but to provide the software architects and designers additional options when decomposing high level requirements into reusable software components.
Miloser, James Andrew
Criteria-Driven Approach in Automotive Software Development – Integrating Concepts of Formal Methods with Testing *CSP Meta QA Testing* *CSP Meta QA Testing II* *CSP Meta QA Testing DEMO* *CSP Meta QA Testing - SM*2017-01-00033/28/2017
We propose a verification method in the field of automotive control systems integrating the concepts of Formal Methods with testing, aiming at efficient and reliable software development. Although Formal Methods are believed to provide the benefits of their rigorous nature and their inherent capability of automation, only limited cases are known where Formal Methods were applied in system and software development, in practice, due to two major difficulties: appropriate abstraction in modeling and scalability in automated reasoning. Focusing on testing on the other hand, there is the difficulty of selecting reasonable set of tests for given verification objectives. In order to overcome these difficulties, our approach is to present verification criteria for testing to appropriately cover the property with the help of the Formal Method concepts. From the consistency with respect to the abstraction level of models between generic property (such as controllability) and underlying assumptions, we derive test coverage that covers the models and the assumptions. Based on a case study using a set of the artifact of a product system, we propose a criteria-driven approach with potential benefits in that we expect to gain the practical efficiency of testing the automotive control systems with the concept of model-checking.
Tohdo, Tetsuya
Arttest – a New Test Environment for Model-Based Software Development *CSP Meta QA Testing*2017-01-00043/28/2017
Modern vehicles become increasingly software intensive. Software development therefore is critical to the success of the manufacturer to develop state of the art technology. Standards like ISO 26262 recommend requirement-based verification and test cases that are derived from requirements analysis. Agile development uses continuous integration tests which rely on test automation and evaluation. All these drove the development of a new model-based software verification environment. Various aspects had to be taken into account: the test case specification needs to be easily comprehensible and flexible in order to allow testing of different functional variants. The test environment should support different use cases like open-loop or closed-loop testing and has to provide corresponding evaluation methods for continuously changing as well as for discrete signals. In a joint project of RWTH Aachen University and Ford, a new tool, Arttest, has been developed for testing model-based software. The tool uses a domain specific language to specify the tests. It offers different test evaluation methods for automated open- and closed-loop testing and reactive testing. It automatically executes the tests, evaluates the outputs and generates summary reports indicating passed tests and errors found. The paper presents the tool and its various unique propositions such as domain specific test language, the evaluation properties and other features like open-loop and closed-loop capabilities.
Wiechowski, Norbert, Rambow, Thomas, Busch, Rainer, Kugler, Alexander, Hansen, Norman, Kowalewski, Stefan
Communication Infrastructure for Hybrid Test Systems - Demands, Options, and Current Discussions2016-01-20519/20/2016
The application of a communication infrastructure for hybrid test systems is currently a topic in the aerospace industry, as also in other industries. One main reason is flexibility. Future laboratory tests means (LTMs) need to be easier to exchange and reuse than they are today. They may originate from different suppliers and parts of them may need to fulfill special requirements and thus be based on dedicated technologies. The desired exchangeability needs to be achieved although suppliers employ different technologies with regard to specific needs. To achieve interoperability, a standardized transport mechanism between test systems is required. Designing such a mechanism poses a challenge as there are several different types of data that have to be exchanged. Simulation data is a prominent example. It has to be handled differently than control data, for example. No one technique or technology fits perfectly for all types of data. There are certain requirements that have to be fulfilled. For example, the mechanism for data exchange needs to have adequate performance to satisfy the demands of the industry. Another requirement is that it must rely on well-established standards to ensure stability and be future-proof. This paper describes the architecture of hybrid test systems, with special emphasis on the communication infrastructure. On the basis of this, it then analyzes the requirements for realizing a suitable communication infrastructure of hybrid test systems. Finally, it presents a proposal of how to devise a standardized interface to this communication infrastructure.
Himmler, Andreas, Stockmann, Lars, Holler, Dominik
A Methodology for Increasing the Efficiency and Coverage of Model Checking and its Application to Aerospace Systems2016-01-20539/20/2016
Formal Methods, and in particular Model Checking, are seeing an increasing use in the Aerospace domain. In recent years, Formal Methods are now commonly used to verify systems and software and its correctness as a way to augment traditional methods relying on simulation and testing. Recent updates to the relevant Aerospace regulations (e.g. DO178C, DO331 and DO333) now have explicit provisions for utilization of models and formal methods. At the system level, Model Checking has seen more limited uses due to the complexity and abstractions needed. In this paper we propose several methods to increase the capability of applying Model Checking to complex Aerospace Systems. An aircraft electrical power system is used to highlight the methodology. Automated model-based methods such as Cone of Influence and Timer Abstractions are described. Results of those simplifications, in combination with traditional Assume-Guarantee approaches will be shown for the Electric Power System application.
Ferrante, Orlando, Scholte, Eelco, Pinello, Claudio, Ferrari, Alberto, Mangeruca, Leonardo, Liu, Cong, Sofronis, Christos
Achieving Quality and Economy with Cold FormingTBMG-254049/1/2016
As medical devices become smaller, the need for precision microminiature components increases. This provides several challenges for the medical device manufacturer as they seek cost-effective parts meeting the exacting quality specifications that play a critical role in the overall performance of the medical device.
Systems Engineering Capability Model Appraisal MethodEIAIS731_2 (Current)6/16/2016
G-47 Systems Engineering
System EngineeringSYSB1 (Current)6/16/2016
G-47 Systems Engineering
Software Life Cycle Processes – Implementation ConsiderationsIEEEEIA12207_2 (Current)6/16/2016
This guide provides implementation consideration guidance for the normative clauses of IEEE/EIA 12207.0. The guidance is based on software industry experience with the life cycle processes presented in IEEE/EIA 12207.0.
Systems Management Council
Model for Integrating Metrics into the Procurement ProcessEIA830 (Current)6/16/2016
This model is designed to enhance insight into the application of meaningful metrics. The emphasis is on business processes which may best provide indication of the level of risk to the customer when contemplating or continuing business with the supplier base. (E.g., the RFP/RFQ, proposal, supplier selection, and performance).
Systems Management Council
Systems EngineeringEIAIS632 (Current)6/16/2016
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
Industry Implementation of International Standard ISO/IEC 12207:1995 (ISO/IEC 12207) Standard for Information Technology Software Life Cycle ProcessesIEEEEIA12207_0 (Current)6/16/2016
This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation, and maintenance of software products. Software includes the software portion of firmware. This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.
Systems Management Council
Systems Engineering Capability ModelEIAIS731_1 (Current)6/16/2016
The purpose of this Interim Standard is to support the development and improvement of systems engineering capability.
G-47 Systems Engineering
Software Life Cycle Processes – Life Cycle DataIEEEEIA12207_1 (Current)6/16/2016
This guide provides guidance for recording life cycle data resulting from the life cycle processes of IEEE/EIA 12207.0. NOTE—For informative references, see annex A.
Systems Management Council
Managing the Development of Artificial Intelligence SoftwareCRB1 (Current)5/31/2016
Systems Management Council
Organic Evolution of Development Organizations - An Experience Report2016-01-00284/5/2016
In areas such as Active Safety, new technologies, designs (e.g. AUTOSAR) and methods are introduced at a rapid pace. To address the new demands, and also requirements on Functional Safety imposed by ISO 26262, the support for engineering methods, including tools and data management, needs to evolve as well. Generic and file-based data management tools, like spreadsheet tools, are popular in the industry due to their flexibility and legacy in the industry but provide poor control and traceability, while rigid and special-purpose tools provide structure and control of data but with limited evolvability. As organizations become agile, the need for flexible data management increases. Since products become more complex and developed in larger and distributed teams, the need for more unified, controlled, and consistent data increases. In this paper we report the successful experience of Volvo Car Corporation (VCC) to achieve these challenges and we present a new paradigm called organic evolution of development organization. VCC has for more than ten years used an integrated model-based platform for developing their active safety systems. The platform supports distributed real-time collaboration, fine-grained versioning, and integration with specialized tools. VCC uses the platform for requirements, design, test and verification, failure mode avoidance and change management. Specifications to suppliers, ISO 26262 safety documentation and AUTOSAR templates are generated from models. The agile and lean development processes have met the increased rate of evolution in projects like the new XC90. High quality is attested by both the products and the endorsement of the development organization.
Shahrokni, Ali, Gergely, Peter, Söderberg, Jan, Pelliccione, Patrizio
Manufacturing the Next Generation of Connected and Electrified Vehicle2016-01-02964/5/2016
Increasing electrification of the vehicle as well as the demands of increased connectivity presents automotive manufacturers with formidable challenges. Automakers and suppliers likely will encounter three practices that will influence how they develop and manufacture highly connected vehicles and future e-mobility platforms: 1) hierarchical production processes in fixed footprints that do not share data freely; 2) lack of real-time, in-line quality inspection and correction processes for complex miniaturized electronic components; and 3) floor to enterprise resource and execution systems that can collect, analyze and respond to rapidly changing production needs. While the automotive manufacturing industry has implemented sensors, robotics and computerized automation for decades, these systems largely are organized in a hierarchical fashion within individual data silos, and often in a closed, hard-wired network environment largely disconnected from IT and enterprise service-based networks. To complicate matters, automotive and industrial standard manufacturing equipment is still largely constrained by a large installed base of legacy workflow, equipment and standards. This paper explores some possible directions how automakers and suppliers will need to change and what considerations they will need to account for with respect to data into order to manufacture the next generation of connected and electrified vehicles.
Minarcin, Monika
Lean Product Development. How to Create Flow? Reflection after a 4 Years Implementation in One Business Unit - Part 12016-01-03464/5/2016
During the 4 last years, Lean has been successfully implemented in one of the Tenneco’s Business Units: Ride Performance. This paper reflects on the results and more specifically on the third principle of Lean [1] “How to make flow” and on the fifth principle “To strive for perfection” obtained in the fields of “Product Development” related to Processes, Tools and People. Processes and Hard Tools. How to improve the flow in the engineering processes? It will be shown that In general standardized processes supported by some integrated tools and, more specifically Some workload leveling in testing, CAD Departments, Standardization in design processes, testing procedures and prototypes development processes and Standardization and availability of components and parts for prototype building are key enablers to enhance flow in the Product Development. Additionally the application of some Poka Yoke principles improves the Product Development quality and front loading of the development process ensures the efficient realization of an optimized product solution. The hard tools are defined as tools supporting the processes and the people in their daily business. A couple of examples illustrate how the tools are bolstering the engineering flow. An example shows how to speed up some processes such as testing, the CAD design or the building of prototypes by sharing resources globally, i.e. efficiently making parts or components available from one engineering center to other locations. The integration of several local databases into one global standardized database helps the end user to both identify the location where resources are available and use it. Another example illustrates the process and the tools to analyze and benchmark the competitor products and technology trends. This tool employs standardized test procedures and report templates. People. To increase the competences of the Product Development group the skills are properly identified and reviewed on a regular basis by the manager. Coaching, Mentoring, Knowledge Sharing and Lessons Learned are supported by the function leaders whose roles and responsibilities include continuously improving the standards of their specialty and sharing of it within the organization. The Change Agents, who propagate the continuous improvement spirit, work closely with the functional leaders to help to identify opportunities for improving and supporting the execution of work by using structured problem solving methods. Soft Tools. The Soft tools [2] are defined as tools supporting Communication to drive alignment and commitment including the use of Visual Management. Problem Solving technics including PDCA and Continuous Improvement. Knowledge collection, Lessons Learned and Sharing Visual Management is a powerful tool to share information, to create transparency, to align and finally gain clear commitment of the stakeholders. Some examples as Obeya room and Cockpit will be presented. PDCA and problem solving are disciplined methods to identify, define, solve problems, driving a systematic behavior and thinking to continuously improve the current business. Lessons learned and Knowledge Sharing processes are supported by some tools to select, approve and finally share the information to the right audience. An efficient way to capture the lessons learned and the experience is to integrate design guidelines, generic DFMEA,DVP, BOM and Drawings into a tool which provides guidance and support the product design process. This tool is particularly efficient knowledge transfer method when bringing new engineers on board.
Garcia, Patrick, Radous, Jiri, Krol, Artur, Bosek, Jacek, Baeten, Caroline
Conceptual Development of a Multi-Material Composite Structure for an Urban Utility/Activity Vehicle2016-01-13344/5/2016
The Deep Orange framework is an integral part of the graduate automotive engineering education at Clemson University International Center for Automotive Research (CU-ICAR). The initiative was developed to immerse students into the world of an OEM. For the 6th generation of Deep Orange, the goal was to develop an urban utility/activity vehicle for the year 2020. The objective of this paper is to describe the development of a multimaterial lightweight Body-in-White (BiW) structure to support an all-electric powertrain combined with an interior package that maximizes volume to enable a variety of interior configurations and activities for Generation Z users. AutoPacific data were first examined to define personas on the basis of their demographics and psychographics. The resulting market research, benchmarking, and brand essence studies were then converted to consumer needs and wants, to establish vehicle target and subsystem requirement, which formed the foundation of the Unique Selling Points (USPs) of the concept. The various sub-systems within the vehicle were then developed; a systems integration approach was used to balance design, engineering, and project (cost, weight, and timing) compromises. The paper discusses the BiW as an enabler of the vehicle USPs, including an very low, flat floor, a utility-oriented asymmetric door concept, and an integrated hatch and rear bumper which create a low lift-over height for loading and unloading. The development of the topology, geometry, and properties of the BiW structure in relation to the chassis, powertrain, and occupant packaging elements required balancing design space, functionality, cost, and weight. Novel manufacturing processes, materials, and joining techniques are described in addition to elaborations on the final realization of the BiW concept.
Flegel, Christopher, Bhivate, Parth, Li, Liang, Mathur, Yash, Phalgaonkar, Sanket, Benton, Mark, Muralidharan, Prasanth, Brooks, Johnell, Pilla, Srikanth, Venhovens, Paul, Lewis, David, DeBry, Garrett, Payne, Craig
Configuration Management Standard Implementation GuideGEIAHB649A (Current)3/1/2016
This handbook is intended to assist the user to understand the ANSI/EIA-649B standard principles and functions for Configuration Management (CM) and how to plan and implement effective CM. It provides CM implementation guidance for all users (CM professionals and practitioners within the commercial and industry communities, DoD, military service commands, and government activities (e.g., National Aeronautics and Space Administration (NASA), North Atlantic Treaty Organization (NATO)) with a variety of techniques and examples. Information about interfacing with other management systems and processes are included to ensure the principles and functions are applied in each phase of the life cycle for all product categories.
G-33 Configuration Management
Best Practices and Recommendations for the Model-Based Development Process2015-01-25299/15/2015
The Aerospace and Defense industry is currently challenged in multiple ways - cost cutting and sequestration on the defense side, and spurt of growth on the commercial aviation side of business. While these are opposing trends, both will impose severe challenges to the management of product development process for both the Air framers and the suppliers. The challenge becomes severe as the innovation expectations become rapid with increases in embedded software content in avionics and the advent of a new category of autonomous ground, marine, and air systems. Clearly, the industry need is to have a product development process that allows for reducing costs, while increasing embedded software quality and thereby product quality even in an iterative development process. This paper looks at the lessons learnt by industries like automotive and commercial vehicles in overcoming similar economic and technical challenges by leveraging model-based design to establish a continuous product development process that stretches from OEMs to suppliers. Commercially available tool-chains, standards and practices across the industries hold similar promise for aerospace and defense industries. Authors of this paper will share their insights from decades of experience in supporting OEMs and suppliers across the broad spectrum of industries to recommend best practices that will help with the aforesaid challenges in avionics development.
Muli, Mahendra, Moudgal, Vivek, Allen, Jace
Verification of Robustness for FPGAs and CEH to Meet Compliance to Objectives (DO-254 and FAA Order 8110.105)2015-01-25259/15/2015
The verification of Robustness is conceptually simple, once the reasonable set of “abnormal operating conditions” has been established. During testing those conditions are created and the FPGA/CEH response is noted. Depending upon system requirements, sometimes the FPGA/CEH response need not be “to work normally” but should at a minimum return to normal operation once normal conditions are reestablished. Part of the analysis is to establish acceptable FPGA/CEH responses to the “abnormal operating conditions”. Some of the acceptable responses may actually affect the LRU/CCA hardware performance or software functions hosted on the system, an early identification of such interdependence is essential for the planning of robustness testing. The test cases implementing robustness testing conform to the same constraints and pedigree as any requirements based test case. The key here is to know the scope of the tests and plan accordingly. The understanding that the test environment will need to be capable of generating these “abnormal operating conditions” is key to properly planning for and establishing the infrastructure needed. Attempting to modify or adapt a Test Infrastructure later in the life cycle is never beneficial as there is limited success with regard to effectiveness, time and costs.
Duncan, Dave
Modeling Space Operations Systems Using SysML as to Enable Anomaly Detection2015-01-23889/15/2015
Although a multitude of anomaly detection and fault isolation programs can be found in the research, there does not appear to be any work published on architectural templates that could take advantage of multiple programs and integrate them into the desired systems. More specifically, there is an absence of a methodological process for generating anomaly detection and fault isolation designs to either embed within new system concepts, or supplement existing schemes. This paper introduces a new approach based on systems engineering and the System Modeling Language (SysML). Preliminary concepts of the proposed approach are explained. In addition, a case study is also mentioned.
Rabelo, Luis, Clark, Tom
Electric Power Assist Steering System Parameterization and Optimisation Employing Computer-Aided Engineering2015-01-15004/14/2015
The automotive industry strives to develop high quality vehicles in a short period of time that satisfy the consumer needs and stand out in the competition. Full exploitation of simulation and Computer-Aided Engineering (CAE) tools can enable quick evaluation of different vehicle concepts and setups without the need of building physical prototypes. Addressing the aforementioned statements this paper presents a method for optimising the Electric Power-Assisted Steering (EPAS) ECU parameters employing solely CAE. The objective of the optimisation is to achieve a desired steering response. The developed process is tested on three specific steering metrics (friction feel, torque build-up and torque deadband) for two function parameters (basic steering torque and active return) of the EPAS. The optimisation method enabled all metrics to fall successfully within the target range.
Ljungberg, Marcus, Nybacka, Mikael, Gil Gómez, Gaspar, Katzourakis, Diomidis
Configuration and Data Management In-House Training PlanCMB6_2 (Current)10/1/2014
G-33 Configuration Management
Configuration ControlCMB6_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
Dynamic Lighting Control Saves Energy, Reinforces Energetic AtmosphereTBMG-201738/1/2014
AWeber Communications in Chalfont, PA thrives on creative energy. From free-form office space, to tube slide transports, to a dynamic lighting control system that automatically responds to the outdoor environment, AWeber offices combine playfulness with productivity and energy efficiency. These values are built into the office design, and evaluated regularly.
Logistics Product Data HandbookGEIAHB0007B (Current)2/10/2014
LCLS Life Cycle Logistics Supportability
Items per page:
1 – 50 of 197