Browse Topic: Needs assessment

Items (212)
Find
Design and Development of a Green Mobile Air Conditioning System for Electric Vehicles2024-26-011501/16/2024
Electric Vehicles (EVs) have rapidly grown as a means for clean mobility, as they zero down tail pipe emission of greenhouse gases. Additionally, greenhouse gases such as Hydro-Fluoro-Carbon (HFCs) based refrigerants used in Mobile Air-Conditioning (MAC) are under global scrutiny for their high Global Warming Potential (GWP). To prevent earth environment to pass the climate tipping point that will be irreversible within human capacity, actions such as rapid phase down of HFCs under Kigali Amendment to Montreal Protocol are enacted. India being amongst signatory nations is now working to fast track phase-down use of high GWP refrigerant and transit to low GWP refrigerant options. Nearly half of national HFCs use and emissions are for manufacture and service MAC. Vehicle OEMs supplying to markets in developing countries (e.g. European nation and non-Article 5 Parties) have already phased out HFC-134a (GWP=1400) through alternate refrigerant solutions. The work presented here discusses a
Venu, Santosh, Mehta, Bhavik Haresh, Panchare, Datta, Maurya, Anurag, Kapoor, Sangeet
Assessment of the Effectiveness of Aftermarket Fuel Stabilizers in Preventing Gum Formation and Loss of Oxidation Stability2022-01-058403/29/2022
Plug-in hybrid vehicles are growing in popularity. These vehicles may be driven short distances and recharged several times before engine operation is needed. This situation can cause fuel storage in the vehicle fuel tank for much longer periods of time than have been typical for conventional vehicles. Aftermarket fuel stabilizers have long been marketed to consumers with little if any information availbe to help consumers assess their effectiveness. This study examined the oxidation stability and gum formation tendencies for gasoline samples blended using 3 aftermarket additives plus a top-tier fuel sample and baseline gasoline over a period of one year. Analyses of the fuel oxidation stability and gum formation were conducted at the inception of the study, 1, 2,3, 6, and 12 months of aging. The results demonstrate that while the additives do increase the oxidation stability of the fuel, the baseline sample (without aftermarket additive) remains compliant with gasoline specifications
Sluder, C. Scott, Davis, Stacy C.
Zebra Printer in-line Implementation2021-36-006402/04/2022
The project presents the advantages of using agile methodologies such as Scrum and Extreme Programing, for software development inside big company, showing that is feasible to adopt Agile Methods even in large companies’ culture. Analyzing this methodology being applied in a print management software for a zebra printer, demonstrating the characteristics of agile development such as agility in development time and ease of adapting the necessary changes in a Windows forms application with the C language. The application that was used to demonstrate the advantages of these methodologies has three basic functions, managing communication with an external service to validate and pass printer status, which is done through an RS232 communication, information management in database SQLite in the application itself, and control of the information that will be sent to a zebra printer, through an Ethernet communication passing data in ZPL (Zebra Programming Language). The advantages of applying
Oliveira, Lucas Miranda, dos Santos Nunes, Caio C´esar, da Costa, Roberto Coelho
Standard Practice for HabitabilitySAE1007 (Historical)09/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
G-45 Human Systems Integration
Standard Practice for HabitabilitySAE1007-TEST-REC (Historical)09/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
G-45 Human Systems Integration
Human Engineering - Principles and PracticesHEB1D (Current)04/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 ModelEIA731_1A (Current)03/16/2021
The purpose of this Standard is to support the development and improvement of systems engineering capability.
G-47 Systems Engineering
Systems Engineering Capability Model Appraisal MethodEIA731_2A (Current)03/16/2021
G-47 Systems Engineering
Systems Engineering Capability Model Appraisal MethodEIA731_2A-TEST-REC (Historical)03/16/2021
G-47 Systems Engineering
Systems Engineering Capability ModelEIA731_1A-TEST-REC (Historical)03/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)02/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
G-47 Systems Engineering
Processes for Engineering a SystemEIA632A-TEST-REC (Historical)02/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
G-47 Systems Engineering
1.1.204 - Cost Effective Emergency Intimation System Design for AutomobilesSAE-PP-0021902/02/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
Mutagaana, Festo
SAE project to develop cyber-secure EV charging20AUTP10_1110/01/2020
Electric-vehicle charging is critical to the mainstreaming of EVs. A 2019 study by the International Council on Clean Transportation estimates that to create, by 2025, a charging network for the 100 U.S. metro areas with the highest populations will require 82,000 more EV charging stations at workplaces, 103,000 public stations with Level 2 (240-V) chargers and 10,000 direct current fast charging stations. That network must be cyber-secure, scalable and trusted by industry and the public. For this reason, SAE International and industry partners recently launched a collaborative project to strengthen EV charging system security. The SAE EV Charging Public Key Infrastructure (PKI) project will design and test, over the next 18-24 months, an inclusive, global EV charging PKI platform aimed at ensuring the interface points between EV drivers and EV charging infrastructure is secure and trusted. PKI is a best practice used across industries to ensure a high level of trust between entities
Brooke, Lindsay
Standard Practice for Manpower and PersonnelSAE1010 (Current)09/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
G-45 Human Systems Integration
The Benefits of Embedding Marker Bands vs. SwagingTBMG-3712606/01/2020
In order to identify the location of a catheter tip under fluoroscopy, the use of marker bands is commonplace in medical applications. These bands are typically platinum iridium metals that are easily detectable on the technology used during the surgeries but can also be made of tantalum or gold for certain applications. The marker bands are put on the catheter, either through swaging or embedding, as a shiny indicator to the surgeon of directly where in the body the tip is located as the operation progresses.
Editorial20AVEP05_0105/01/2020
Privately-owned vehicles were never so safe as they are today. Nor have they made so much sense. That thought hit me between the nostrils recently, as I sprayed a pungent disinfectant on the steering wheel of my family's B-segment runabout. Carefully wiping down the car's touch points with antibacterial cleaners has become a new pandemic ritual for us after returning home from food shopping and other essential missions. My little tribe generally keeps the interiors of our two vehicles tidy. Finding the occasional French fry buried in a seat track is, however, preferable to the dangerous microbes deposited every minute in the typical bus, train, or ride-share. The term “clean,” as understood by transit passengers, means a few spritzes by a custodial crew racing to meet uptime targets.
Brooke, Lindsay
Rationale, Considerations, and Framework for Data Interoperability for Health Management within the Aerospace EcosystemAIR6904 (Current)04/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
Your MDR Strategy: Start with a Gap AnalysisTBMG-3640704/01/2020
The 566-page Medical Device Regulation (MDR), which replaces the EU’s Medical Device Directive (93/42/EEC) and the Directive on Active Implantable Medical Devices (90/385/EEC), has caused much discussion, training, debate, and stress in the medical device industry since its publication in May 2017. To say nothing of the changes in device regulation, the aggressive three-year implementation goal of May 26, 2020 has the industry as a whole — manufacturers, laboratories, and regulators — strategizing diligently as we step into 2020. This article briefly examines the current state of the MDR, including deadline extensions announced in the second corrigenda, a strategy to address material information, and what should be included in a gap analysis.
The Navigator19AVEP09_0209/01/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.
On-Road and Chassis Dynamometer Evaluation of a Pre-Transmission Parallel PHEV2019-01-036504/02/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
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-137003/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
McMillan, Craig, Crapo, Andy, Durling, Michael, Li, Meng, Moitra, Abha, Manolios, Panagiotis, Stephens, Mark, Russell, Daniel
Proactive Cybersecurity Saves Healthcare Organizations from Data BreachesTBMG-3399303/01/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)02/08/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)02/07/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
G-33 Configuration Management
Got Your Game Plan? The OEM Playbook to Navigating Preclinical Device Testing Under MDR and ISO 10993-1TBMG-3373502/01/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 Integrated Approach to Model Based Engineering with SysML, AADL and FACE2018-01-194210/30/2018
Multiple model-based engineering (MBE) frameworks have emerged to cover the many requirements for the engineering of avionics systems: from early requirement capture to the final system and embedded software generation, through refinement and V&V activities. In this paper, we consider the SysML, AADL and FACE standards. They are promoted by different standardization bodies, with different objectives. We note they are often seen as competitive, while we argue it is the opposite: there is a potential for a synergistic coupling. To date, no complete open evaluation on the feasibility of such capability has been done. In this paper, we present one workflow that illustrates the joint use of SysML, AADL and FACE. We consider a basic flight control system to exercise the proposed process and gateways between the three notations. We use SCADE Architect by ANSYS that supports the three notations in a unified workbench to illustrate refinement scenarios from one notation to another, then
Zhe, Wang, Hugues, Jerome, Chaudemar, Jean-Charles, LeSergent, Thierry
An Engine Stop Start System with Driver Behavior Learning and Adaption for Improving the User Experience2018-01-060904/03/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
Athani, Gopal, Gavarraju, Srinivasa Raju, Jain, Punit, Addala, Shashank, P, Satishkumar
Implementing IEC 62304 for Safe and Effective Medical Device Software — PART 1TBMG-2772210/01/2017
Monitoring and Control of Hybrid Test Systems2017-01-211909/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
Stockmann, Lars, Himmler, Andreas
Designing Cybersecurity into Connected Medical DevicesTBMG-2731808/01/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.
Arttest – a New Test Environment for Model-Based Software Development *CSP Meta QA Testing*2017-01-000403/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
Wiechowski, Norbert, Rambow, Thomas, Busch, Rainer, Kugler, Alexander, Hansen, Norman, Kowalewski, Stefan
Approaches to Determining Beneficial Use of Simulink and UML in Automotive Embedded Software Systems *CSP Meta QA Testing*2017-01-000803/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-000303/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
Tohdo, Tetsuya
Communication Infrastructure for Hybrid Test Systems - Demands, Options, and Current Discussions2016-01-205109/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
Himmler, Andreas, Stockmann, Lars, Holler, Dominik
A Methodology for Increasing the Efficiency and Coverage of Model Checking and its Application to Aerospace Systems2016-01-205309/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-2540409/01/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.
Industry Implementation of International Standard ISO/IEC 12207:1995 (ISO/IEC 12207) Standard for Information Technology Software Life Cycle ProcessesIEEEEIA12207_0 (Current)06/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 EngineeringEIAIS632 (Current)06/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
G-47 Systems Engineering
Systems Engineering Capability ModelEIAIS731_1 (Current)06/16/2016
The purpose of this Interim Standard is to support the development and improvement of systems engineering capability.
G-47 Systems Engineering
Model for Integrating Metrics into the Procurement ProcessEIA830 (Current)06/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
Software Life Cycle Processes – Implementation ConsiderationsIEEEEIA12207_2 (Current)06/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
Software Life Cycle Processes – Life Cycle DataIEEEEIA12207_1 (Current)06/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
System EngineeringSYSB1 (Current)06/16/2016
G-47 Systems Engineering
Systems Engineering Capability Model Appraisal MethodEIAIS731_2 (Current)06/16/2016
G-47 Systems Engineering
Managing the Development of Artificial Intelligence SoftwareCRB1 (Current)05/31/2016
Systems Management Council
Manufacturing the Next Generation of Connected and Electrified Vehicle2016-01-029604/05/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
Minarcin, Monika
Organic Evolution of Development Organizations - An Experience Report2016-01-002804/05/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
Shahrokni, Ali, Gergely, Peter, Söderberg, Jan, Pelliccione, Patrizio
Conceptual Development of a Multi-Material Composite Structure for an Urban Utility/Activity Vehicle2016-01-133404/05/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
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
Lean Product Development. How to Create Flow? Reflection after a 4 Years Implementation in One Business Unit - Part 12016-01-034604/05/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
Garcia, Patrick, Radous, Jiri, Krol, Artur, Bosek, Jacek, Baeten, Caroline
Items per page:
1 – 50 of 212