Browse Topic: Standardization

Items (474)
SAE J4001 provides instruction for evaluating levels of compliance to SAE J4000. Component text (Sections 4 to 9) from SAE J4000 is included for convenience during the evaluation process. Applicable definitions and references are contained in SAE J4000. SAE J4000 tests lean implementation within a manufacturing organization and includes those areas of direct overlap with the organization’s suppliers and customers. If applied to each consecutive organizational link, an enterprise level evaluation can be made. SAE J4001 relates the following approximate topic percentages to the implementation process as a whole: SAE J4001 is to be applied on a specific component basis. Each of the 52 components tests part of, one, or multiples of the specific requirements of lean implementation. Implementation throughout an organization may be measured by evaluating all of the components. The level of compliance for each component relative to best practice may be used as a reference by an organization to compare itself to current best practice in establishing lean operation. Examples of current best practice are available in SAE publication RR003. An organization may evaluate only selected components without affecting validity of results.
Automotive Quality and Process Improvement Committee
SAE J4000 is a tool to identify and measure best practice in the implementation of lean operation in a manufacturing organization. Implementation of lean operation is defined as the process of eliminating waste exhibited in an organization’s value stream. Best practice in this process is Level 3 conduct as described in the standard’s component statements. A description of the levels of implementation is: A procedure for evaluation and scoring of each component will be included in the SAE J4001 Implementation of Lean Operation User Manual.
Automotive Quality and Process Improvement Committee
Under the Rotorcraft Structural Integrity Program (RSIP) Pilot Demonstration effort, the requirements defined in MILSTD-3063 were applied to a Future Vertical Lift (FVL) representative, model performance specification objective aircraft to demonstrate a standardized RSIP process. This paper covers application of the MIL-STD-3063 approach on SB>1 DEFIANTTM airframe structural components and presents the evolution of the resulting RSIP Master Plan. Elements of the resulting Master Plan are discussed in detail. The Master Plan is the basis for collaborative establishment of structural integrity with an efficient and effective airworthiness substantiation footprint. The discussion includes case studies of the application of logic flow to requirements in MIL-STD-3063 for the determination of specific, relevant action items to airframe structural demonstration components. Execution of this pilot effort led to lessons learned and highlighted feedback to inform the ongoing development of the MIL-STD-3063 process, through ongoing collaboration between the SB>1 DEFIANTTM team and the U.S. Army.
Chiu, LisaKrastel, MatthiasLorthridge, DerrellMcCarthy, Dennis
AVSC Best Practice for Describing an Operational Design Domain: Conceptual Framework and LexiconAVSC000022020044/15/2020
An ADS-operated vehicle’s operational design domain (ODD) is defined by the manufacturer based on numerous factors. Research is underway at other organizations to define and organize ODD elements into taxonomies and other relational constructs. In order to enhance collaboration and communication between manufacturers and developers and transportation authorities, common terms and consistent frameworks are needed. The conceptual framework presented by Automated Vehicle Safety Consortium establishes a lexicon that can be used consistently by ADS developers and manufacturers responsible for defining their ADS ODD. A common framework and lexicon will reduce confusion, align expectations, and therefore build public trust, acceptance, and confidence. The guidance in this document is intended for: The technical community (e.g. manufacturers and developers) Public agencies (e.g. regulatory authorities) Infrastructure owner-operators The public This document, Best Practice for Describing an Operational Design Domain: Conceptual Framework and Lexicon is a critical first step. It offers a conceptual framework for manufacturers and developers to use when communicating with public agencies and the general public about their ADS’s ODD. It also details a list of potential variables with definitions that manufacturers and developers might use to describe certain aspects of the ODDs of their ADS-operated vehicles. It was developed with fleet-managed, SAE Level 4 vehicles in mind — i.e. vehicles requiring no human intervention to operate within their ODD. These vehicles are NOT privately owned.
Automated Vehicle Safety Consortium
A Study on the Development of Aerostructures Design for Assembly Guidelines and Their Effective Use to Proactively Identify Opportunities for Improvement in Mitigating Common Defects of the Aerostructures Assembly2020-01-00093/10/2020
An Aircraft’s assembly process plays a vital part in its design, development and production phases and contributes to about half of the Total cost spent in its entire product lifecycle. Design For Assembly (DFA®) principles have been one of the proven effective methodologies in Automotive and Process industries. Use of DFA® principles have resulted in proactively simplifying and optimizing engineering designs with reduced product costs, and improved efficiencies in product design and performance. Standardization of Assembly guidelines is vital for “Design and Build” and “Build-To-Print” manufacturing supplier organizations. However, Standardizing design methodologies, through use of proven tools like Advanced Product Quality Planning, (APQP) are still in the initial stages in Aerospace part and process design processes. Thus, there is a tremendous opportunity for research on the application of the existing DFA® guidelines to optimize Engineering Aerospace Assembly processes aiming to simplify, standardize design methodologies by building on existing industry practices which have a common platform for design communication and are easy to adopt within the existing process/systems. This technical paper is to discuss the framework for application of DFA® principles and design guidelines specifically aimed for engineering optimization of Aerospace Assembly Process Designs. The Aerospace DFA® implementation framework proposed in this paper is based on the study on the application of the existing DFA® guidelines proven and used in other Process industries to Aerospace Part and Process Design and development. This paper collates the findings, experiences and learnings gained during the study collated from a research point of view using Six Sigma methodology DMAIC and DMADV. This paper also focuses on the use and publication of this research outputs on Aerospace industry applicable DFA® guidelines, which can be used as a reference for emerging Aerospace designers in their future and current designs.
Rajamani, Mani RathinamPunna, Eshwaraiah
A “STEP” Forward for Product Lifecycle Management19AERP10_0210/1/2019
The existence of countless proprietary file formats and the exchange of 3D CAD data has been a significant problem since the beginning of 3D CAD modeling. CAD applications and methods using digital data are constantly changing, which predicates the need for a solution to share validated and accurately translated data. Thus the birth of STEP242. Companies who are adopting model-based processes and tools within their organizations are using ISO 10303 STEP Application Protocols AP242 and AP239 for both exchanging data as well as maintaining data for archival and retrieval. Long Term Data Archival and Retrieval (LOTAR) (http://www.lotar-international.org) is an International project sponsored by multiple consortiums for the standardization of the archival and retrieval of digital product and technical data. This project is ISO compliant and works across multi-CAD environments enabling stake holders to share 3D data within a Model-Based Environment (MBE) or a digital enterprise. To ensure the preservation of design intent, validation properties that include geometric shape representation, assembly features, saved views, user-defined attributes, color, visibility, and Product & Manufacturing Information (PMI) 3D data need to be verified and validated for compliance. The culmination of these standards is allowing companies around the globe to manage interoperability with fewer challenges.
The process detailed within this document is generic and can be applied to commercial and military applications. It applies to the entire end-to-end health management system throughout its lifecycle, covering on-board and on-ground elements. The practical application of this standardized process is detailed in the form of a checklist. The on-board element described here are the source of the data acquisition used for off-board analysis. The on-board aspects relating to safety of flight, pilot notification, etc., are addressed by the other SAE Committees standards and documents. This document does not prescribe hardware or software assurance levels, nor does it answer the question “how much mitigation and evidence are enough”. The criticality level and mitigation method will be determined between the ‘Applicant’ and the regulator. In order to provide some detailed guidance utilizing the process and checklist, some high-level examples of previous successful cases of Maintenance Credit applications are included. At this point, it is incumbent on the ‘Applicant’ to explain any differences in terminology between the health management system they are seeking a credit for and the appropriate regulatory references. For example, the system name often uses interchangeable terms such as Engine Health Monitoring, Equipment Health Management, Prognostic Health Management, Powerplant Health Management, etc.
E-32 Aerospace Propulsion Systems Health Management
Definition equations for the steering wheel location2018-36-02569/3/2018
The environment of vehicle occupants and the arrangement of controls around the driver are critical factors for determining a good vehicle concept. The location of the steering wheel is perhaps one of the most important factors to be considered. Engineering organizations such as SAE and GCIE have struggled to provide guidelines which standardize the variables important during the development of vehicles, and, thus far do not provide a reference for steering wheel positioning. Realizing this deficiency, researchers have devoted considerable effort studying this relationship. Based on the investigations of M. Reed [2013], it was noted that there was an opportunity to develop equations which could serve as references for positioning the steering wheel based upon the seat height (H30), then, find a correlation directly to the driver's seating position. For the development of this work, data from the M. Reed [2013] model was used. The correlation between different seat heights and how these relate to the steering wheel position were investigated and measured in Reed's laboratory. The data was taken from a considerable range of vehicles available in the US market. This data was plotted and the equations obtained by linear interpolation of the points are presented here as references for application in advanced vehicle development, where fast and less precise definitions of the variables are sufficient to determine the main concepts of the vehicle, called Vehicle Advance Packaging. These steering wheel positioning equations were also correlated with a minimum safety distance to the chest of a 50th percentile female Dummy to ensure sufficient time for the Air Bag deployment between the driver and the steering wheel.
Almeida, A. R.Magalhães, A. P.Evangelista, L. W.Marçal, G.V.Ferreira, S. T.
This SAE Standard provides a definition of a rainflow file format. This type of simple text file would contain all relevant information about the rainflow cycle content of a time history. Included information are Comments, Signal Range, Signal Mean, Number of Cycles, Signal Maximum, Signal Minimum. Rainflow cycle counting has become the most accepted procedure for identifying material fatigue relevant cycles in complex variable amplitude load time histories. The cycle counting methods account for the effects of material plasticity and material memory of prior deformation, and the resulting compressed history information is used by durability analysts to estimate the effects of a given service or test history. Standardization of the rainflow counting methods output files, which is the format addressed by the present standard, is important for reliable information transfer between test and design groups, or different calculation software packages, and thus forms a critical step in the evaluation of components and vehicles. Further background information can be found in the SAE publication AE-10 cited in 2.1.1.
Materials, Processes and Parts Council
Autonomous Vehicle Engineering: November 201717AVEP1111/2/2017
Introduction: Welcome to the Revolution Autonomy: the New Age of Automobility The self-driving future brings profound implications for the auto industry-and unprecedented mobility to a lot more people. The Building Blocks of Autonomous Tech Sensors, processors, architecture and communications trends for the self-driving future. Artificial Intelligence Becomes a Reality Automakers could be among the leaders in deploying AI in free-standing, high-reliability environments. But developers must determine how to mitigate undesirable side-effects. Standards Play a Vital Role Developing safe, reliable AVs and their infrastructure requires a robust foundation of standards. SAE's expert explains. A Revolution for Testing The new American Center for Mobility is the ultimate proving ground for real-world testing and validation of autonomous vehicles. Integration, Communication Hurdles to Truck Automation Combining sensors, inter-vehicle communications and controllers poses major challenges in the effort to bring autonomy to commercial trucking. Suppliers Take the Tech Lead Tier 1s and their partners are driving autonomy's technology bus. Six execs talk about their roles. Embracing the Challenge of Smart Cities "Smarter" cities will be better, more-productive places. But development challenges abound. Why America Needs a National Autonomous-Vehicle Development Policy A set of standardized autonomous-vehicle regulations, applicable nationwide, is the best policy structure to encourage AV-specific innovation. Automated Driving: Who Should Regulate What? Traditional state and federal roles in transportation regulation are being tested by autonomy's new vistas. Special Advertising Section: Leaders in Autonomy
Items per page:
1 – 50 of 474