Criteria

Text:
Content:
Display:

Results

Viewing 61 to 90 of 616
CURRENT
2016-06-16
Standard
EIAIS731_2
This document describes the Appraisal Method (AM ) for the Systems Engineering Capability Model (SECM). An appraisal compares an organization's Systems Engineering capabilities against the Specific Practices of the Focus Areas and the Generic Characteristics defined in EIA/731, Part 1.
CURRENT
2016-06-16
Standard
EQB4
This report on quantification of Essentiality (W) and Utilization (U) terms extends the scope of the basic expression for system effectiveness (Es = ADC) to include the additional "W" and "U" paramenters needed for the quantification of multi-functioned and multi-missioned systems. Methods and procedures for applying these terms to system effectiveness quantification are discussed and simple examples to demonstrate the principles of usage are included. The need to look at the system being quantified in terms of its level in the mission/function hierarchical tree is explained. The relationships between system elements (hardware, software, and personnel) and performance functions are discussed and illustrated with examples. Two methods for applying the "W"'and "U" weight factors, LOGIC AND (weak link model) and LOGIC OR (degraded operational modes model) are described and examples are shown for these cases.
CURRENT
2016-06-16
Standard
EQB1
Scope is unavailable.
CURRENT
2016-06-16
Standard
EQB2
Program Managers have considered the subject of effectiveness quantification from three diverse points of view. The first viewpoint, in conjunction with the system effectiveness analyst, is to quantify everything and to consider everything quantifiable into a figure of merit. The result is a numerical decision aid that usually has some undesirable attributes such as oversimplification, non-sensitivity to critical parameters, hidden calculations, and difficulty in exercise of the model. This technique is characterized by mathematical models, computer programs, and attempted optimizations. The second viewpoint, in conjunction with the controller, is to consider the effectiveness as specified and concentrate on cost reduction, This has a danger of formulating all technical problems in terms of cost or economic considerations. This technique is characterized by closely controlled work packages.
CURRENT
2016-06-16
Standard
EQB3
The Electronic Industries Association (EIA) G-47 Effectiveness QuantificationCommittee has a basic task to quantify system effectiveness. Since the support parameters underly any prime parameter quantification, the topic of support system analysis is a fundamental one to this basic committee task. The charts contained in this bulletin were developed and used for presentations to aircraft support engineering groups, to comunicate the logic and scope of system analysis applied to support system optimization.
CURRENT
2016-06-15
Standard
EIAIS106
This standard will assist the vendors and users of CASE tools in developing mechanisms for interchanging information between CASE tools. This standard specifies an element of a family of related standards. When used together, these standards specify a mechanism for transfemng information between CASE tools. This standard, EIAIIS-IO6 CDIF - CASE Data Interchange Format - Overview, describes the architecture of the CDIF Family of Standards and provides an overview to all the current standards that form the CDIF Family of Standards.
CURRENT
2016-06-15
Standard
EIAIS107
This standard will assist the vendors and users of CASE tools in developing mechanisms for interchanging information between CASE tools. This standard specifies an element of a family of related standards. When used together, these standards specify a mechanism for transferring information between CASE tools.
CURRENT
2016-06-15
Standard
EIAIS108
This standard defines how CDIF supports multiple exchange Syntaxes and Encoding, and describes how CDIF meta-models are concretely represented during a transfer. EIAIZS-IO9 CDIF - Trartsfer- Format - Syntax SYNTAX.1 and EIAIIS-II0 CDIF - Transfer Format - Encoding ENCODING.1 define one specific CDIF Syntax and Encoding.
CURRENT
2016-06-15
Standard
EIAIS109
The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for ImportExport from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories.
CURRENT
2016-06-15
Standard
EIAIS110
This document is intended to be used by anyone wishing to understand and/or use CDIF. This dticument provides a definition of an encoding for CDIF transfers. -those evaluating CDIF -those who wish to understand the principles and concepts of a CDIF transfer -those developing importers and exporters.
CURRENT
2016-06-15
Standard
EIAIS111
This document is intended to be used by anyone wishing to understand and/or use CDIF. This document provides a definition of a single subject area of the CDIF integrated Meta-model. It is suitable for: -those evaluating CDIF -those who wish to understand the principles and concepts of a CDIF transfer -those developing importers and exporters.
2016-06-07
WIP Standard
AIR6908
This document provides informational background, rationale, and data (both physical testing and computer simulations) used in defining the component test methods and acceptance criteria described in SAE Aerospace Recommended Practice (ARP) 6330. ARP 6330 defines multiple test methods uses to assess the effect of seat back mounted IFE monitor changes on head blunt trauma.
CURRENT
2016-06-06
Standard
AS681K
This SAE Aerospace Standard (AS) provides the method for presentation of gas turbine engine steady-state and transient performance calculated using computer programs. It also provides for the presentation of parametric gas turbine data including performance, weight, and dimensions computed by computer programs. This standard is intended to facilitate calculations by the program user without unduly restricting the method of calculation used by the program supplier. This standard is applicable to, but not limited to the following program types: data reduction, steady-state, transient, preliminary design, study, specification, status, and parametric programs.
CURRENT
2016-05-31
Standard
EDIB1B
This userguide contains a description of the Unit Production Cost Tracking Model for use in design tradeoffs and control and reporting tasks of a Design-to-Cost program. This model is designed to compare two Cost Breakdown Structures (CBS) to show elemental and summary cost differences. The two Cost Breakdown Structures may represent design alternatives, or a target allocation and the current design approach for comparison.
CURRENT
2016-05-31
Standard
CRB1
Expert systems are a wave of the information processing future. As time goes on they will become more and more part of the mainstream. However, a necessary prerequisite to moving them into widespread use is to reduce the methodologies for expert system development closer to the more generally accepted software engineering techniques. This report offers a step towards that goal. It describes an alternative software life cycle model for expert system development. Since the field of Artificial Intelligence is so broad, this report limits the software to be considered. Systems that would be of the greatest interest to DoD over the next 5 to 7 years would be expert systems that have the following attributes: - may reason with uncertainty - are not necessarily rule-based - are non-learning systems. For these systems, a developmental cycle is articulated, and each phase of the cycle described.
CURRENT
2016-05-31
Standard
CRB2
This paper originated with a software quality panel workshop at the EIA Computer Resources Workshop. The panel group initially focused on requirements for nondeliverable software. It was felt that the requirements for deliverable software were well covered by Department of Defense standards but non-deliverable software issues were not adequately covered. After much discussion, including attempts to define nondeliverable by examples of software types, a surprising unanimous conclusion was reached by the participants. That is: the states of "deliverable" and "non-deliverable" had no bearing on the quality of the software, and thereby also had no bearing on the quality assurance requirements that should be applied for that software. Rather, the only rational application of quality assurance was primarily dependent on the impact that the software had, or could have, on the end product (¡.e. the ultimate mission).
CURRENT
2016-05-24
Standard
AIR4762A
This Aerospace Information Report (AIR) describes conditions under which freezing (frozen) brakes can occur and describes operating procedures which have been used to prevent or lessen the severity or probability of brake freezing. This document also identifies design features that some manufacturers implement to minimize the occurrence of freezing brakes. This document is not an Aerospace Recommended Practice (ARP) and therefore does not make recommendations based on a consensus of the industry. However, part of this document’s purpose is to describe the design and operational practices that some are using to minimize the risk of frozen brakes. NOTE: The following information is based upon experience gained across a wide-range of aircraft types and operational profiles, and should NOT take precedence over Aircraft Flight Manual or Flight Operations Procedures.
CURRENT
2016-05-24
Standard
J2724_201605
This procedure describes a method for measuring the fraction of underlayer (also referred to as backing layer) existing at any given height above the a disc brake friction materials shoe plate. Measuring underlayer distribution is useful for computing useable lining thickness and for friction material quality management.
2016-05-17
WIP Standard
JA6268
This Aerospace Recommended Practice (ARP) was created to help industry deal with existing barriers to the successful implementation of Integrated Vehicle Health Management (IVHM) technology in the aerospace and automotive sectors. That is,given the common barriers that exist, this ARP can be applied not only to aerospace but also to the automotive, commercial and military vehicle sectors. Original Equipment Manufacturers (OEMs) in all of these sectors are heavily dependant upon a large number of component suppliers in order to design and build their products. The advent of IVHM technology has accentuated the need for improved coordination and communication between the OEM and its suppliers –to ensure that suppliers design health ready capabilities into their particular components.
2016-05-17
WIP Standard
AIR6245
This document is applicable to military aircraft where stakeholders are seeking guidance on the development and approval of Structural Health Monitoring (SHM) technologies and on the integration of these technologies into encompassing maintenance and operational support systems. The document will refer to those guidelines prepared under SAE ARP6461 that are relevant and applicable to military applications.
CURRENT
2016-05-12
Standard
J2923_201605
This Recommended Practice applies to on-road vehicles with a GVWR below 4540 kg equipped with disc brakes.
2016-04-22
WIP Standard
ARP6904
In order to realize the benefits of Integrated Vehicle Health Management (IVHM) within the aerospace and defense industry there is a need to address five critical elements of data interoperability within and across the aircraft maintenance ecosystem, namely • Approach • Trust • Context • Value • Security In Integrated Vehicle Health Management (IVHM) data interoperability is the ability of different authorized components, systems, IT, software, applications and organizations to securely communicate, exchange data, interpret data, use the information and derive consistent insight from the data that has been exchanged to derive value.
CURRENT
2016-04-20
Standard
J3001_201604
This procedure is applicable to modes from 500 and 13,000 Hz. The parameters measured with this procedure are defined as the damping factor, ξ for first nine vibration modes of the beam. The measurement will be done in free-free conditions and with temperature.
2016-04-14
WIP Standard
AIR5925B
The report shows how the methodology of measurement uncertainty can usefully be applied to test programs in order to optimize resources and save money. In doing so, it stresses the importance of integrating the generation of the Defined Measurement Process into more conventional project management techniques to create a Test Plan that allows accurate estimation of resources and trouble-free execution of the actual test. Finally, the report describes the need for post-test review and the importance of recycling lessons learned for the next project.
2016-04-11
WIP Standard
J2816
The Physics-of-Failure (PoF) is a science-based approach to reliability that uses modeling and simulation to design-in reliability. This approach models the root causes of failures such as fatigue, fracture, wear, and corrosion. Computer-Aided Design (CAD) tools have been developed to address various loads, stresses, failure mechanisms and sites. PoF uses knowledge of basic failure processes to prevent failures through robust design and manufacturing practices, and aims to: - Design-in reliability up front; - Eliminate failures prior to testing; - Increase fielded reliability; - Promote rapid, cost effective deployment of Health and Usage Monitoring Systems (HUMS); - Improve diagnostic and prognostic techniques and processes; and, - Decrease operational and support costs. This guide provides a high level overview of the methodology, process and advantages to performing a PoF assessment.
CURRENT
2016-03-16
Standard
AIR5656A
This SAE Aerospace Information Report (AIR) provides a methodology for performing a statistical assessment of gas-turbine-engine stability-margin usage. Consideration is given to vehicle usage, fleet size, and environment to provide insight into the probability of encountering an in-service engine stall event. Current industry practices, such as ARP1420, supplemented by AIR1419, and engine thermodynamic models, are used to determine and quantify the contribution of individual stability threats. The statistical technique adopted by the S-16 committee for performing a statistical stability assessment is the Monte Carlo method (see Applicable References 1 and 2). While other techniques may be suitable, their application is beyond the scope of this document. The intent of the document is to present a methodology and process to construct a statistical-stability-assessment model for use on a specific system and its mission or application.
CURRENT
2016-02-16
Standard
AIR5687A
This document reviews the state of the art for data scaling issues associated with air induction system development for turbine-engine-powered aircraft. In particular, the document addresses issues with obtaining high quality aerodynamic data when testing inlets. These data are used in performance and inlet-engine compatibility analyses. Examples of such data are: inlet recovery, inlet turbulence, and steady-state and dynamic total-pressure inlet distortion indices. Achieving full-scale inlet/engine compatibility requires a deep understanding of three areas: 1) geometric scaling fidelity (referred to here as just “scaling”), 2) impact of Reynolds number, and 3) ground and flight-test techniques (including relevant environment simulation, data acquisition, and data reduction practices).
2016-01-26
WIP Standard
AS8002B
This SAE Aerospace Standard (AS) covers air data computer equipment (hereinafter designated the computer) which when connected to sources of aircraft electrical power, static pressure, total pressure, outside air temperature, and others specified by the manufacturer (singly or in combination) provides some or all of the following computed air data output signals (in analog and/or digital form) which may supply primary flight instruments: pressure altitude; pressure altitude, baro-corrected; vertical speed; calibrated airspeed; mach number; maximum allowable airspeed; overspeed warning; and total air temperature. In addition, the computer may supply one or more of the following signals: pressure altitude, digitized; equivalent airspeed; true airspeed; static air temperature; altitude hold; airspeed hold; mach hold; angle of attack; flight control gain scheduling; and others.
CURRENT
2016-01-14
Standard
J2777_201601
With many corporations and suppliers conducting development and validation tests at different Climatic Wind Tunnel sites, there is an increasing need for a recommended best practice that defines a process by which climatic wind tunnels can be correlated. This document addresses the test methods and metrics used to obtain similar results, independent of location, for Heating Ventilation and Air Conditioning (HVAC) and Powertrain Cooling (PTC) development. This document should be used as a guideline to make sure key aspects of tunnel testing are covered when comparing various climatic wind tunnel facilities. The depth of the correlation program is ultimately influenced by program objectives. Therefore a correlation program, for the intent and purposes of this document, can range from just a few tests to a full analysis that involves multiple vehicle tests identifying limitations and statistical boundaries.
2016-01-03
WIP Standard
AIR6900
This AIR will address the need for a strategy to achieve aircraft operating certificate holder maintenance efficiencies within the existing regulatory environment as well as the need for regulation, policy, and guidance changes in the long-term to accommodate more complex IVHM solutions. This document will analyse which IVHM solutions can be incorporated within existing maintenance procedures and which also comply with regulations, policy, and guidance. One of the AIR’s objectives is to define best practices for aircraft operating certificate holders to engage with regulators to get approval for simpler IVHM applications leading to maintenance efficiencies. Additionally, this document will analyse the barriers that existing regulations, policy, and guidance present to the implementation of more advanced IVHM solutions. The result is a set of recommendations to certify and implement end-to-end IVHM solutions for the purpose of gaining maintenance efficiencies.
Viewing 61 to 90 of 616