SAE HEB 1-B-2014 Human Engineering - Principles and Practices (Formerly TechAmerica HEB1-B).pdf

1、_SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising theref

2、rom, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and suggestions.Copyright 2014 SAE International All rights reserved. No part of this pub

3、lication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: +1 724-776-4970

4、(outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.orgSAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/HEB1BTECHNICAL REPORTHEB1 REV. BIssued 2002-06 Revised 2014-02 Human Engineering - P

5、rinciples and Practices NOTICEThis document has been taken directly from the original TechAmerica document and contains only minor editorial and format changes required to bring it into conformance with the publishing requirements of SAE Technical Standards. The release of this document is intended

6、to replace the original with the SAE International document. Any numbers established by the original document remain unchanged.The original document was adopted as an SAE publication under the provisions of the SAE Technical Standards Board (TSB) Rules and Regulations (TSB 001) pertaining to acceler

7、ated adoption of specifications and standards. TSB rules provide for (a) the publication of portions of unrevised specifications and standards without consensus voting at the SAE committee level, and (b) the use of the existing specification or standard format.TechAmericaEngineeringBulletinHuman Eng

8、ineering Principles and PracticesHEB1-BFebruary 2014 HEB1-BNOTICE TechAmerica Engineering Standards and Publications are designed to serve the public interest by eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assis

9、ting the purchasers in selecting and obtaining with minimum delay the proper product for their particular needs. Existence of such Standards and Publications shall not in any respect preclude any member or nonmember of TechAmerica from manufacturing or selling products not conforming to such Standar

10、ds and Publications, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TechAmerica members, whether the standard is to be used either domestically or internationally. Standards and Publications are adopted by TechAmerica in accordance with th

11、e American National Standards Institute (ANSI) patent policy. By such action, TechAmerica does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication.Technical Publications are distinguished from TechAmerica Standards

12、in that they contain a compilation of engineering data or information useful to the technical community and represent approaches to good engineering practices that are suggested by the formulating committee. This Bulletin is not intended to preclude or discourage other approaches that similarly repr

13、esent good engineering practice, or that may be acceptable to, or have been accepted by, appropriate bodies. Parties who wish to bring other approaches to the attention of the formulating committee to be considered for inclusion in future revisions of this publication are encouraged to do so. It is

14、the intention of the formulating committee to revise and update this publication from time to time as may be occasioned by changes in technology, industry practice, or government regulations, or for other appropriate reasons.(From Project Number TA-HEB1-B, formulated under the cognizance of the G-45

15、 Human Systems Integration Committee.)Published by 2013 TechAmerica Standards * achieve required effectiveness of human performance during system operation, maintenance, support, control, and transport; * make economical demands upon personnel resources, skills, training, and costs; and * improve hu

16、man performance to maximize system performance. * effect safe, efficient life support, escape, search and recovery of personnel.Figure 2.1-1. Human Engineering in the System Acquisition Process HEB1-B2The HE effort should include, but not necessarily be limited to, active participation in the follow

17、ing three major interrelated areas of system development. 2.1.1 Analysis Starting with a mission analysis developed from a baseline concept of operations and operational scenario, the functions that must be performed by the system in achieving its mission objectives should be identified and describe

18、d. These functions should be analyzed to determine their best allocation to personnel, hardware, software, or combinations thereof. Allocated functions should be further dissected to define the specific tasks that must be performed to accomplish the functions. Each task should be analyzed to determi

19、ne the human performance parameters; the system, equipment, and software capabilities; and the tactical/environmental conditions under which the tasks will be conducted. Task parameters should be quantified where possible, and should be expressed in a form that permits effectiveness studies of the h

20、uman-system interfaces in relation to the total system operation. HE high-risk areas should be identified as part of the analysis. Analyses should be updated as required to remain current with the design effort. HEB1-B32.1.2 Design and development HE should be applied to the design and development o

21、f the system hardware, software, procedures, work environments, and facilities associated with the system functions that require personnel interaction. This HE effort should convert the mission, system, and task analysis data into (a) detailed design and (b) development plans to create a human-syste

22、m interface that will operate within human performance capabilities, meet system functional requirements, and accomplish mission objectives. The HE design of a system should also take into account any requirements to interoperate with other systems and untrained personnel. Human interface design is

23、a multi-disciplinary task requiring the participation and coordination of experts from both sides of the interface. In order to develop a good human interface the people or organization involved should have demonstrated expertise in Human Engineering and the technical operating principles and proced

24、ures of systems for which the interface is being designed. Full design authority should reside within the team responsible for the user interface. 2.1.3 Test and evaluation (T * quantify such risks and their impacts on cost, schedule, and performance; * evaluate and define the sensitivity of such ri

25、sks to HE design; * identify alternative solutions to moderate- and high-risk HE problems and define the associated risks of each alternative; HEB1-B4* take actions to avoid, minimize, control, or accept each HE risk. * document the identified risks, their impact, and the actions taken; and * ensure

26、 that human performance/design risk is an element of management awareness/control specification requirements. 2.4 Reviews 2.4.1 Major technical reviews HE practitioners should participate in the major technical reviews, as applicable to the acquisition phases indicated, which include: * Analysis of

27、Alternatives * System Requirements Review * System Design Review * Preliminary Design Review (PDR) * Critical Design Review (CDR) * System Verification Review HE practitioners should also participate in other important technical activities that further HE efforts (e.g., mission analysis, and test an

28、d evaluation planning). 2.4.2 Subsystem reviews HE practitioners should also participate in subsystem reviews, including, where applicable, software specification, test readiness, and functional reviews (e.g., support, training, systems engineering, test, and manufacturing reviews). 2.5 Cognizance a

29、nd coordination The HE program should be integrated into the total system program. In particular, HE should be coordinated with systems engineering, software engineering, RAM (reliability, availability, and maintainability), system safety, survivability/vulnerability, facilities engineering, Integra

30、ted Logistic Support (ILS) and Logistics Support Analysis (LSA), and other HE-related functions, including biomedical, life support, personnel survivability, habitability, personnel, and training functions. (See International Standards Organization (ISO) 13407 5 for information on a human-centered d

31、esign process for interactive systems). HE data should be provided for incorporation into Logistic Management Information (LMI). The HE effort should utilize the LMI reports as source data where possible. The HE portion of any analysis, design, or T equipment procedures; and skill, training, and com

32、munication requirements; and as inputs to Logistics Support Analysis, as applicable. All analyses of tasks should use the task taxonomy expressed in MIL-HDBK-1908 6. 3.1.3.1 Analysis of tasks Analyses of tasks should be conducted and should provide one of the bases for making conceptual design decis

33、ions. For example, task analyses should be considered in determining, before hardware fabrication, whether system performance and maintenance requirements can be met by the combination of anticipated hardware, software, and personnel, and in ensuring that human performance requirements do not exceed

34、 human capabilities. Time requirements for tasks should be evaluated for task duration versus time availability, task sequencing, and task simultaneity. Task requirements should be evaluated, as applicable, for accuracy, precision, completeness, and the effects of task feedback and error tolerance/e

35、rror recovery on performance. These analyses should also consider effects of sustained/continuous operations on human performance. Tasks identified during HE analyses that require performance of critical tasks, reflect possible unsafe practices, or show the potential for improvements in operating ef

36、ficiency should be further analyzed for redesign. 3.1.3.2 Analysis of critical tasks Further analysis of critical tasks should identify the: * information required by the operator/maintainer, including cues for task initiation, * information available to operator/maintainer, * evaluation process, *

37、decision reached after evaluation, * action taken, * body movements required by the action taken, * workspace envelope required by the action taken, * workspace available, * location and condition of the work environment, HEB1-B8* frequency and tolerances of action, * time base, * feedback informing

38、 the operator/maintainer of the adequacy of the action taken or the failure to take an action, * tools and equipment required, and their timely availability, * number of personnel required, their specialties, and their experience, * job aids, training, or references required, and their timely availa

39、bility, * communications required, including type of communication, channel clarity, and available channel capacity, * special hazards involved, * required or typical operator interactions when more than one crewmember is involved, * performance limits of personnel, and * operational limits of hardw

40、are and software. The analysis should be performed for all affected missions and phases, including degraded modes of operation. Each critical task should be analyzed to a level sufficient to identify operator/maintainer problem areas that can adversely affect mission accomplishment and to evaluate p

41、roposed corrective action.3.1.3.3 Workload analysis Operator and maintainer (individual and team) workload analyses should be performed and compared with performance criteria. To avoid overloading or underloading, the degree to which demands of any task or group of tasks tax the attention, capacitie

42、s, and capabilities of system personnel (individually and as a team) and thus affect performance should be evaluated. Sensory, cognitive, and physiological limitations should be considered, as applicable. The workload analyses should define operational sequences and task times. Preliminary workload

43、estimates should correlate mission segments with crew tasks for each task component (visual, auditory, motor, and cognitive) specified in terms of time, workload, mental effort, and psychological stress. A workload estimate for each crewmember should be defined in a fashion permitting individual and

44、 team workload to be related to mission segment(s). 3.1.3.4 Corrective action Human-system interface design incompatibilities and excessive skill/physical requirements identified by analysis of tasks, analysis of critical tasks, or workload analysis should be corrected by changing the design or rest

45、ructuring the tasks to ensure that degraded human performance does not result in degraded system performance. 3.1.3.5 Timeliness and availability Analyses of tasks should be modified as required to remain current with the design effort and should be available to the customer. HEB1-B93.1.4 Preliminar

46、y system and subsystem design HE principles and criteria should be applied to system and subsystem designs and should be reflected in design criteria documents, specifications, functional flow diagrams, system and subsystem schematics and block diagrams, interface control drawings, overall layout dr

47、awings, and related applicable drawings provided in compliance with contract data requirements. The preliminary system and subsystem configuration and arrangements should satisfy human-system performance requirements and comply with applicable HE design criteria, such as MIL-STD-1472 7.3.2 HE in des

48、ign and development During design and development, the HE inputs made by implementing the results of analyses described in 3.1 through 3.1.4, as well as other appropriate HE inputs, should be converted into detailed engineering design features. Design of the equipment should satisfy human-system per

49、formance requirements and meet applicable HE design criteria such as, MIL-STD-1472. HE testing of the system or equipment should be considered during design and should include such factors as verifying proper operation, defining need for maintenance, and allocating adequate space for test personnel to perform their tasks. HE provisions in the equipment should be evaluated for adequacy during design reviews. HE practitioners assigned