Browse Topic: Supplier assessment

Items (225)
This document covers the requirements for SAE implementations based on ISO 17987:2016. Requirements stated in this document will provide a minimum standard level of performance to which all compatible ECUs and media shall be designed. This will assure full serial data communication among all connected devices regardless of supplier.The goal of SAE J2602-1 is to improve the interoperability and interchangeability of LIN devices within a network by adding additional requirements that are not present in ISO 17987:2016 (e.g., fault tolerant operation, network topology, etc.).The intended audience includes, but is not limited to, ECU suppliers, LIN controller suppliers, LIN transceiver suppliers, component release engineers, and vehicle system engineers.The term “master” has been replaced by “commander” and term “slave” with “responder” in the following sections.
Vehicle Architecture For Data Communications Standards
This SAE Aerospace Recommended Practice (ARP)4294 is directed at life cycle cost (LCC) analysis of aerospace propulsion systems and supplements AIR1939. Specific topics addressed by ARP4294 are listed below: a Propulsion system LCC element structure. b Information exchange and relationships with: (1) Aircraft manufacturer (2) Equipment suppliers (3) Customer c The relationship of the LCC element structure to work breakdown structures. d The relationship between LCC analysis and other related disciplines (e.g., technical (performance analysis, weight control, component lives), reliability, availability and maintainability (RAM), integrated logistic support (ILS), production and finance). e Classification of the accuracy and applicability of LCC assessments.
LCLS Life Cycle Logistics Supportability
The purpose of this Standard is to support the development and improvement of systems engineering capability.
G-47 Systems Engineering
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
Items per page:
1 – 50 of 225