2.3.14 - Human Factors Engineering

2.3.14-1 Level 2 Tasks

Tasks Applicable Mission Phases Description SFWC Artifacts References
2.3.14-1-1 Ensure the HSI domains are addressed in the acquisition documents Phase A | Phase B | Phase C | Ensure the acquisition domains include: Manpower; Personnel; Training (sometimes combined into MPT); Human Factors Engineering; Environment; Safety; and Occupational Health (the previous three are commonly grouped as ESOH); Survivability; and Habitability where appropriate. Applies to HW, SW, and SE across Ground, Space, User and Factory. NA NA SMC Human Systems Integration (HSI) Policy, 12 Feb 2006 or equivalent; United States Air Force (2009) Human Systems Integration Requirements Pocket Guide, U.S. Air Force Human Systems Integration Office, September 2009; United States Air Force (2010) Air Force Instruction 10-601, Operational Capability Requirements Development, 12 July 2010; Defense Acquisition Guidebook, Chapter 6, 10 January 2012; Air Force Human Systems Integration Handbook (AFHSI) Handbook, Planning and Execution of Human Systems Integration, 21 Jan 2009
2.3.14-1-2 Ensure that an human system integration acquisition management plan is developed and approved by all stakeholders Phase A | Phase B | Phase C | Ensure the ground segment/system in particular has documented human system integration acquisition management documented. Ensure appropriate user interface design standards are applied for a consistent HSI in look, feel, behavior and navigation for all HCI displays. Applies to HW, SW, and SE across Ground, Space, User and Factory. NA NA MIL-STD-1472F; ANSI HFES 2007 (100)
2.3.14-1-3 Ensure contractor products are complete Phase A | Phase B | Phase C | Ensure contractor products include a Human Engineering Program Plan (HEPP), Human Engineering System Analysis Report (HESAR), Human Engineering Design Approach Document - Operator (HEDAD-O), Human Engineering Design Approach Document - Maintainer (HEDAD-M), Human Engineering Test Plan (HETP) and Human Engineering Test Report (HETR). Applies to HW, SW, and SE across Ground, Space, User and Factory. NA NA SMC Human Systems Integration (HSI) Policy, 12 Feb 2006 or equivalent; United States Air Force (2009) Human Systems Integration Requirements Pocket Guide, U.S. Air Force Human Systems Integration Office, September 2009; United States Air Force (2010) Air Force Instruction 10-601, Operational Capability Requirements Development, 12 July 2010; Defense Acquisition Guidebook, Chapter 6, 10 January 2012; Air Force Human Systems Integration Handbook (AFHSI) Handbook, Planning and Execution of Human Systems Integration, 21 Jan 2009
2.3.14-1-4 Ensure that a complete and traceable set of requirements is contained within the appropriate contractual documents for human systems integration Phase A | Phase B | Phase C | Ensure requirements should address requirements for each HSI domain as required. These domains include; Manpower; Personnel; Training (sometimes combined into MPT); Human Factors Engineering; Environment; Safety; and Occupational Health (the previous three are commonly grouped as ESOH); Survivability; and Habitability). This includes the number of personnel required to operate the system as well as the personnel skill level of the designated operators/maintainers, adequate timeline allocation for operator review, decision making, crew coordination for mission critical tasks, and measurement of human performance (cognitive workload, human error rates, situation awareness). Applies to HW, SW, and SE across Ground, Space, User and Factory. NA NA SMC Human Systems Integration (HSI) Policy, 12 Feb 2006 or equivalent; United States Air Force (2009) Human Systems Integration Requirements Pocket Guide, U.S. Air Force Human Systems Integration Office, September 2009; United States Air Force (2010) Air Force Instruction 10-601, Operational Capability Requirements Development, 12 July 2010; Defense Acquisition Guidebook, Chapter 6, 10 January 2012; Air Force Human Systems Integration Handbook (AFHSI) Handbook, Planning and Execution of Human Systems Integration, 21 Jan 2009