Browse Topic: Documentation
This SAE Information Report contains definitions for hydrogen fuel cell powered vehicle terminology. It is intended that this document be a resource for those writing other hydrogen fuel cell vehicle documents, specifically, Standards or Recommended Practices.
As part of a human factors research project aimed at optimizing technical documentation used in helicopter maintenance with multimedia elements, we compared different instruction formats to observe their effects on the performance of an assembly task. This task offers us the opportunity to test procedures that call for similar actions as a maintenance task (e.g., localization, action sequencing, assembly). Static (i.e., image and image with text) and dynamic instruction formats (i.e., video, video with text and video with audio) were compared to determine if dynamic formats allowed a better motor performance of the task for assembly reaction time (time needed to complete the assembly) and accuracy. We were also interested in how the use of the text instructions interacted with both visual dynamic and static instructions. Reaction times were recorded and measured with eye tracking data. Subjective data was collected in questionnaires during and after the experiment. Results showed significant differences in the time spent on the instructions and the time spent on the assembly, depending on the format of instructions. Overall, assembly time is shorter with video instruction formats, but videos took longer to be consulted than static formats. Results also showed a difference in the number of actions required to do the assembly. Videos facilitated the right path of action sequence in comparison with static formats. With the analysis of both subjective and objective data, the results give us a better idea of the advantages and drawbacks of using dynamic formats in technical documentation.
This investigation reveals many DoD contractors do not treat integration as a stand-alone activity. Instead, integration is an inherent part of the development process. The contractors did not have a specific documented process for integration beyond calling out integration as an activity in the development process. Integration is an integrator unique step within the development process to meet functional and performance requirements. Identification of the interfaces and engineering to match the interfaces requires substantial individual expertise and heuristics for each integration effort resulting in inconsistent non-repeatable integrations. This increases risk, and limits third party integration effectiveness and utility. This paper identifies steps that can be taken to increase the speed and effectiveness of integration while decreasing the effort and dependency on individual expertise.
This standard establishes supplemental requirements for 9100 and 9145 and applies to any organization receiving it as part of a Purchase Order or other contractual document from a customer. AS13100 also provides details of the Reference Materials (RM13xxx) developed by the SAE G-22 AESQ committee and listed in Section 2 - Applicable Documents, that can also be used by organizations in conjunction with this standard.
Test Scope
ABSTRACT A proof of concept test to measure the unsteady boundary layer transition locations on the lower surface of a Machscaled rotor in forward flight was performed during the Summer of 2017 in the NASA Langley 14- by 22-Foot Subsonic Tunnel. The transition locations were measured using high-speed infrared thermography with a rotating mirror assembly that could be remotely actuated to acquire data at several rotor azimuths. Data were acquired for eight unique rotor flight conditions for a range of advance ratios (μ=0:10 : 0:38), thrust coefficients (CT/α =0:04 : 0:12) and rotor shaft angles (αs = -6 deg : 0 deg). This paper presents the transition locations as a function of azimuth and radius for an advance ratio of, μ, of 0.30, and thrust coefficent, CT/α, of 0.08. At this condition, the lower surface is fully laminar on the retreating side and mostly turbulent on the advancing side except near the tip. The tip airfoils were greater than 60 percent laminar on the lower surface advancing side. Capturing the location of natural transition on a rotating blade in forward flight represents a new advancement toward understanding the boundary layer state and its important contribution to rotor aerodynamics. Documentation of the boundary layer transition location during testing is critical to understanding scaling model to full-scale performance data, validation of newly developed turbulence models, and the design of the next generation of high performance rotor blades.
This SAE Standard applies to cranes which are equipped to adjust the boom angle by hoisting and lowering means through rope reeving.
Illustrations used here are not intended to include all existing industrial or agricultural machines, or to be exactly descriptive of any particular machine. They have been picked to describe the principles to be used in applying this standard.
This research sought to distill and define the fundamentals of system and software architecture analysis and form the basis by which a design can be tested and analyzed prior to its implementation. In short, the question "can a design be measured against the business-level objectives and quality-of-use architectural requirements. The research focuses on building a body of knowledge that supports an analysis, built on fundamentals which scales and can serve as the basis by which we can transform when and how architecture validation can occur. This research supports ongoing work towards developing a strategic comprehensive architecture approach and extends the analysis and documentation of the Key Business Drivers (KBDs) and architectural drivers supporting the efficient development and sustainment of interoperable aviation mission systems. A prototype process that leverages the discovered relationships and weights for use by current Architects and Senior Systems Engineers is shown. Programs implementing this approach are expected to benefit from the planned reuse of architectural artifacts for follow up systems engineering products supporting the development of reusable component product lines avoiding the long-term challenges of unrealized architectural objectives.
Items per page:
50
1 – 50 of 1124