Criteria

Text:
Sector:
Content:
Display:

Results

Viewing 1 to 30 of 189
2015-02-26
Standard
J1272_201502
This SAE Standard is intended to describe the basic types of felling heads, including those with bunching capabilities, that are attachments to a self-propelled machine. Only the major components that are necessary to describe the functions to the felling head, and to apply the principles of the recommended practice are included. Illustrations used are not intended to include all existing felling heads or to describe any particular manufacturer's variation.
2015-02-05
Standard
AS13003
This standard defines the minimum requirements for conducting Measurement Systems Analysis (MSA) for variable and attribute assessment on characteristics as defined on the drawing or specification. It does not define the detailed analytical methods for each type of study as these can be found in existing published texts (see Section 2 for guidance).
2015-02-02
Standard
AS13001
The standard applies to aero engine suppliers operating a self-release process as a delegated activity from the delegating organization. While primarily developed around the aero engine supply chain requirements, this standard can also be used in other industry sectors where a self-release process may be of benefit.
2015-01-15
Standard
AS6502
This SAE Aerospace Standard (AS) provides classical propulsion system performance parameter names for aircraft propulsion systems and their derivatives, and describes the logical framework by which new names can be constructed. The contents of this document were, originally, a subset of AS755E. Due to the growing complexity of station numbering schemes described in AS755, and a desire to expand the original document's nomenclature section to include a fuller representation of "classical" (legacy use) names, a decision was made to separate its "station numbering" and "nomenclature" content into two separate documents. This document, then, was created using the "nomenclature" half of AS755E. Both documents will continue to be improved and revised as industry needs dictate. The parameter naming conventions presented herein are for use in all communications concerning propulsion system performance such as computer programs, data reduction, design activities, and published documents.
2015-01-09
Standard
AS4877D
This procurement specification covers bolts and screws made from a corrosion and heat resistant, age hardenable nickel base alloy of the type identified under the Unified Numbering System as UNS N07718.
2014-12-18
Standard
ARP210A
"Hot Day ", "Tropical Day ", "Standard Day ", "Polar Day " and "Cold Day " are part of the lexicon of the aircraft industry. These terms are generally understood to refer to specific, generally accepted characteristics of atmospheric temperature versus pressure altitude. There are also other, less well-known days, defined by their frequency of occurrence, such as "1% Hot Day ", "10% Cold Day ", or "Highest Recorded Day ". These temperature characteristics have their origins in multiple sources, including U.S. military specifications which are no longer in force.
2014-12-15
WIP Standard
GEIASTD0002_1A
This Standard applies to integrated circuits and semiconductors exhibiting the following attributes: a. A minimum set of requirements, or information provided by the part manufacturer, which will allow a standard COTS component to be designated AQEC by the manufacturer. b. As a minimum, each COTS component (designated AQEC) will have been designed, fabricated, assembled, and tested in accordance with the component manufacturer's requirements for standard data book components. c. Qualification of, and quality systems for, the COTS components to be designated as AQEC shall include the manufacturer's standards, operating procedures, and technical specifications. d. Components manufactured before the manufacturer has addressed AQEC requirements, but utilizing the same processes, are also considered AQEC compliant. e. Additional desired attributes of a device designated AQEC (that will support AQEC users) are found in Appendix B of this standard.
2014-12-01
Standard
AIR4243A
This document discusses the work done by the U.S. Army Corps of Engineers and the Waterways Experiment Station (WES) in support of SAE A-5 Committee activity on Aerospace Landing Gear Systems. It is an example of how seemingly unrelated disciplines can be combined effectively for the eventual benefit of the overall aircraft systems, where that system includes the total airfield environment in which the aircraft must operate. In summary, this AIR documents the history of aircraft flotation analysis as it involves WES and the SAE.
2014-12-01
Standard
AS5452B
This SAE Aerospace Standard (AS) will specify what type night vision goggles are required, minimum requirements for compatible crew station lighting, aircraft exterior lighting such as anticollision lights and position/navigation lights that are "NVG compatible." Also, this document is intended to set standards for NVG utilization for aircraft so that special use aircraft such as the Coast Guard, Border Patrol, Air Rescue, Police Department, Medivacs, etc., will be better equipped to chase drug smugglers and catch illegal immigrants, rescue people in distress, reduce high-speed chases through city streets by police, etc. Test programs and pilot operator programs are required. For those people designing or modifying civil aircraft to be NVG compatible, the documents listed in 2.1.3 are essential.
2014-11-20
Standard
EIA649_1
This document is used for placing Configuration Management Requirements on Defense Contracts after being tailored by the Acquirer. When effectively and consistently applied, Configuration Management (CM) provides a positive impact on product quality, cost, and schedule. The planning and execution of Configuration Management (CM) is an essential part of the product development and life cycle management process. It provides control of all configuration documentation, physical parts and software representing or comprising the product. Configuration Management's overarching goal is to establish and maintain consistency of a product's functional and physical attributes with its requirements, design and operational information throughout its life cycle. When effectively and consistently applied, Configuration Management (CM) provides a positive impact on product quality, cost, and schedule.
2014-11-14
Standard
TSB001_201411
ABSTRACT
2014-11-13
Standard
AS6500
This standard is applicable to all phases of the system acquisition life cycle. It is intended for use on all programs with manufacturing content. It requires proven manufacturing management practices with the goal of delivering affordable and capable systems to the extent that it is invoked contractually. The term “organization” as used in this document refers to the company or facility that is implementing this standard, such as when imposed contractually by the customer. NOTE: The term “shall” is used wherever the criterion for conformance with the specific recommendation requires that there be no deviation. The term “should” is used wherever noncompliance with the specific recommendation is permissible.
2014-11-11
WIP Standard
J3083
This Recommended Practice (RP) document will provide guidance on performing a non-handbook reliability prediction for automotive electronic products by utilizing field return data. It will include a description of what kind of data is required, possible sources of data, how to collect it, and the methodology of how to process these data to obtain failure rates. This document will also include the existing failure rate data Delphi Electronics & Safety is currently using for reliability prediction and the Excel-based tool for these types of calculations.
2014-10-30
Standard
AIR1133B
Solid chemical oxygen supplies of interest to aircraft operations are 'chlorate candles' and potassium superoxide (KO 2 ). Chlorate candles are used in passenger oxygen supply units and other emergency oxygen systems, such as submarines and escape devices. Potassium superoxide is not used in aircraft operations but is used in closed-cycle breathing apparatus. Characteristics and applications of both are discussed, with emphasis on chlorate candles.
2014-10-30
Standard
AS9116
The aviation, space, and defense industries rely on the development and manufacture of complex products comprised of multiple systems, subsystems, and components each designed by individual designers (design activities) at various levels within the supply chain. Each design activity controls various aspects of the configuration and specifications related to the product. When a change to design information is requested or required, the change has to be evaluated against the impacts to the higher-level system. Proposed changes to design information that the design activity identifies to be minor and have no effect on their product requirements or specifications have the potential to be concurrently implemented and approved, where authorized to do so. Changes that affect customer mandated requirements or specifications shall be approved prior to implementation.
2014-10-22
WIP Standard
GEIASTD0009A
This standard requires the developers and customer/user's working as a team to plan and implement a reliability program that provides systems/products that satisfy the user's requirements and expectations. The user's requirements and needs are expressed in the form of the following four reliability objectives: The developer shall solicit, investigate, analyze, understand and agree to the user's requirements and product needs. The developer, working with the customer and user, shall include the activities necessary to ensure that the user's requirements and product needs are fully understood and defined, so that a comprehensive design specification and Reliability Program Plan can be generated; The developer shall use well-defined reliability- and systems-engineering processes to develop, design, and verify that the system/product meets the user's documented reliability requirements and needs.
2014-10-01
Standard
CMB6_9
The functional and/or physical characteristics or hardware/software as set forth in technical documentation and achieved in a product. What is Configuration Management? A discipline applying technical and administrative direction and surveillance to (a) identify and document the functional and physical characteristics of a configuration item, (b) control changes to those characteristics, and (c) record and report change processing and implementation status.
2014-10-01
Standard
CMB6_8
Data Management in house training course.
2014-10-01
Standard
CMB6_6
The objective of this course is to provide an in-depth understanding of the concepts and principles involved in the Review and Configuration Audit process. It is intended for an individual who has completed a basic introductory course in CM and who requires the deeper knowledge of a CM practitioner rather than a superficial overview. Technical review and product audit practices described in this text are based on Government requirements. This emphasis is made because the Department of Defense DOD) represents a major customer of goods and services and because the referenced specifications and standards reflect good business practices refined over many years of usage. For commercial companies producing items for other companies or the public, many of these reviews and audits may not be formally implemented. They are, however, an integral and essential part of the systems engineering process.
2014-10-01
Standard
CMB6_5
This text will cover the details of the status accounting function. Identification, audits, and control are covered in other textbooks. It is the intent of the authors that this status accounting text will serve a broad general population of managers engaged in development, manufacturing, and distribution of both commerical and military items. The figures in this text provide illustrations of sample data which might be required and sample formats that might be used by your organization in accomplishing status accounting. You will have to make the decisions about the exact content and format appropriate for your project and/or facility based on the information contained in this text.
2014-10-01
Standard
CMB7_3
the purpose of the Statement of Work is to define the Configuration Management requirements necessary to maintain and control CALS databases and provide transmission, access and receipt of digital data between contractors, subcontractors, vendors and the government. Digital data includes not only traditional configuration management documents such as specifications, drawings, and ECP's but includes all technical data listed in the CDRL. This Model SOW document will provide the government suggested SOW wording that should be included in RFP's and guidance in applying those SOW paragraphs.
2014-10-01
Standard
CMB7_2
This guideline is not intended to provide detailed instructions for implementing an automated CM system. It is intended to provide a framework for planning the automation of CM functions by identifying the issues and potential problems to be considered. We begin with a look at the current problems encountered with the use of manual and semiautomated CM approaches. In order to aid in the cultural acceptance of a fully automated CM system, the benefits of automation are reviewed and the issues of the psychology or change are discussed. Finally, this guideline focuses on automating the CM functions: identification, configuration control, status accounting, and audit. Given current technology and the constraints of available resources, this seciton discusses some of the concerns which must be addressed in order to achieve a successful implementation.
2014-10-01
Standard
CMB7_1
The scope of this bulletin is to provide guidance on the use of current and future technologies for the electronic interchange of CMS data. the purpose of this guide is to ensure requirements of CM (identificaiton, control, status accounting and audit) are used as the basis for transitioning to an automated environment.
2014-10-01
Standard
CMB6_10
In today's high technology environment, a variety of management tools have been developed within government and industry to govern the fast changing technical environment. There is a particular demand in industry for formal education in the disciplines of Configuration Management and Data Management (CM/DM). Briefly, Configuration Management is the disciplined continuous identification of design and control of changes. Data Management ensures that the data (technical, financial, administrative) delivered as part of a contract comply with contractual requirements and are adequate to satisfy the intended use or functions (e.g. logistics, maintenance, reprocurement).
2014-10-01
Standard
CMB4_3
Computer software libraries are an essential element of a software configuration management (CM) system. However, the term, "library" while commonly used in the world of software, has had no significance in the field of CM until recently. Further, even in the software, world, the term has several different meanings. The purpose of this bulletin is to relate the term to the software CM system, e.g., the role of a library in the release of software. It describes the three types of libraries which are involved in the system, it discusses the principles and factors which affect their design and it presents a model, including samples o records and forms. Also included is a "univerals" position description for a librarian.
2014-10-01
Standard
GEIASE0001
The purpose of this panel was to present a set of visions about how Systems Engineering (SE) will transform the engineering of systems in the next decade through development and application of concepts under current Research and Development (R&D). A survey was done of the most significant and innovative systems engineering Initiatives and Technologies covering: Processes Methods, techniques and standards Engineering environments and tools Modeling and simulation Representatives of the most influential Initiatives and Technologies identified were invited to become panelists. Panelists presented an overview of their Initiatives or Technologies and engaged in question and answer periods to elicit further understanding. A final capstone session assessed the effectiveness of the approaches being taken by academia, government and industry.
2014-10-01
Standard
DMG1
To the reader, this publication may appear to have been prepared soley to provide guidance for companies doing business with the Department o Defense (DoD). Such is not the case. The DoD, as the largest procurer of dta, has the greatest number of regulations governing the acquisition of data, and, therefore, presents the most problems to the data provider. However, principles whick apply to all data acquisitions and their implementation can be tailored to satisfy various customers. The present day world of technical advancement sees increasing demands for recorded information. This documentation provides a means for communicating technical ideas, presents plans for developing them, gives instructions to those who will build, operate and service hardware, records the results of technical performance tests and evaluation, and provides visibility for managing technical and business aspects that are necessary to assure program success.
2014-10-01
Standard
DMG2
This document provides guidance in the developing, managing, controlling and transmitting of data in the current electronic environment.
2014-10-01
Standard
CMB5A
The purpose of this Bulleting is to provide a guide for the Buyer in levying tailored CM requirements on his Suppliers; and as a guide for the Suppliers to assist in establishing a management system necessary to satisfy those requirements. through general use of this Bulletin, it is anticipated that: a. Alll buyers, at any level, can impose more consistent CM requirements on the Suppliers. b. Suppliers, because of consistent requirements imposed upon them by the Buyers, will be able to use the same internal systems for all supply activity. c. Because of consistency of requirements and systems, the overall system costs should be reduced.
2014-10-01
Standard
CMB7_4A
This Bulletin provides a comprehensive list of Terms and Definitions used in or related to TechAmerica prepared standards/documents. The information in these listings was extracted from standards and documents prepared by the Systems Engineering (G47), Configuration Management (G33), Life Cycle Logistics Supportability and Enterprise Information Management Interoperability Committees along with other pertinent international, industry and government standards. It is intended that this bulletin be used as a resource to help with harmonization of terms and definitions across standards. One should be cognizant of the release date of this Bulletin and understand that updates to the included standards and handbooks after this Bulletin was released may affect its accuracy.
Viewing 1 to 30 of 189