Browse Topic: Defense industry

Items (1,843)
ABSTRACT The complexity of ground vehicle mission systems has evolved significantly over the last few years resulting in over-taxed platforms with federated mission suites. Department of Defense (DoD) is pursuing platform evolution toward integrated mission suites. Opportunities exist to apply aspects of previously developed methodologies from the aviation sector to ground platforms. This paper describes the parallels of the evolution of aviation platforms with the similarities to ground platforms. Solutions from the military aviation community will be discussed that could reduce development risks, schedules and costs and improve mission capabilities for ground applications. Specific discussion will be on opportunities and techniques to transition performance driven, high cost, low volume technologies into mission suitable and affordable high volume solutions. Discussion of the feedback opportunities into the aviation community will be addressed. This paper is not intended to be a
Hensley, Marion P.
Automated vehicles, in the form we see today, started off-road. Ideas, technologies, and engineers came from agriculture, aerospace, and other off-road domains. While there are cases when only on-road experience will provide the necessary learning to advance automated driving systems, there is much relevant activity in off-road domains that receives less attention. Implications of Off-road Automation for On-road Automated Driving Systems argues that one way to accelerate on-road ADS development is to look at similar experiences off-road. There are plenty of people who see this connection, but there is no formalized system for exchanging knowledge. Click here to access the full SAE EDGETM Research Report portfolio.
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
This document is limited to the aerospace industry, where an approved manufacturer requests a supplier to ship an article against the approved manufacturer’s quality system directly to a customer. The direct ship process is not required or applicable to standard parts or military parts. In this process, the approved manufacturer is responsible for assurance that the article conforms to type design information.
G-14 Americas Aerospace Quality Standards Committee (AAQSC)
This SAE standard establishes the requirement for suppliers to plan a reliability program that satisfies the following three requirements: a The supplier shall ascertain customer requirements b The supplier shall meet customer requirements c The supplier shall assure that customer requirements have been met
G-41 Reliability
This standard is applicable to all items used for manufacturing, maintenance, and repair of aviation, space, and defense products from the raw material to the final product (e.g., aircraft, structural items, constituent assemblies, standard parts, consumables with conformity and/or safety impact). This standard considers items dispositioned as scrap in accordance with 9100-series standards’ supporting nonconformity management, corrective action, or organization decisions (e.g., obsolescence, inventory management, missing traceability documentation). The requirements specified in this standard are complementary (not alternative) to contractual and applicable statutory and regulatory requirements. Should there be a conflict between the requirements of this standard and applicable statutory or regulatory requirements, the applicable statutory or regulatory requirements take precedence. This standard defines requirements and actions to be taken after the disposition decision to control the
G-14 Americas Aerospace Quality Standards Committee (AAQSC)
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
This document establishes test plans/procedures for the AS5643/1 Slash Sheet. The AS5643/1 Slash Sheet establishes guidelines for the use of IEEE Std 1394-2008 as a data bus network in military and aerospace vehicles. It encompasses the data bus cable and its interface electronics for a system utilizing S400β over copper medium over extended lengths.
AS-1A Avionic Networks Committee
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 1843