E7. ENCLOSURE 7

HUMAN SYSTEMS INTEGRATION (HSI)

E7.1. General. The PM shall have a comprehensive plan for HSI in place early in the acquisition process to optimize total system performance, minimize total ownership costs, and ensure that the system is built to accommodate the characteristics of the user population that will operate, maintain, and support the system. HSI planning shall be summarized in the acquisition strategy and address the following:

E7.2. Human Factors Engineering. The PM shall take steps (e.g., contract deliverables and Government/contractor IPT teams) to ensure human factors engineering/cognitive engineering is employed during systems engineering over the life of the program to provide for effective human-machine interfaces and to meet HSI requirements. Where practicable and cost effective, system designs shall minimize or eliminate system characteristics that require excessive cognitive, physical, or sensory skills; entail extensive training or workload-intensive tasks; result in mission-critical errors; or produce safety or health hazards.

E7.3. Personnel. The PM shall work with the personnel community to define the human performance characteristics of the user population based on the system description, projected characteristics of target occupational specialties, and recruitment and retention trends. To the extent possible, systems shall not require special cognitive, physical, or sensory skills beyond that found in the specified user population. For those programs that require skill requirements that exceed the knowledge, skills, and abilities of current military occupational specialties or that require additional skill indicators or hard-to-fill military occupational specialties, the PM shall consult with personnel communities to identify readiness, personnel tempo (PERSTEMPO), and funding issues that impact program execution.

E7.4. Habitability. The PM shall work with habitability representatives to establish requirements for the physical environment (e.g., adequate space and temperature control) and, if appropriate, requirements for personnel services (e.g., medical and mess) and living conditions (e.g., berthing and personal hygiene) for conditions that have a direct impact on meeting or sustaining system performance or that have such an adverse impact on quality of life and morale that recruitment or retention is degraded.

E7.5. Manpower. In advance of contracting for operational support services, the PM shall work with the manpower community to determine the most efficient and cost-effective mix of DoD manpower and contract support. Once the Manpower Estimate is approved by the DoD Component manpower authority, it shall serve as the authoritative source for reporting manpower in other program documentation.

E7.6. Training. The PM shall work with the training community to develop options for individual, collective, and joint training for operators, maintainers and support personnel and, where appropriate, base training decisions on training effectiveness evaluations. The PM shall address major elements of the training system described in DoD Directive 1430.13, reference (bd), and place special emphasis on options that enhance user capabilities, maintain skill proficiencies, and reduce individual and collective training costs. The PM shall develop training system plans to maximize the use of new learning techniques, simulation technology, embedded training, and instrumentation systems that provide anytime, anyplace training and reduce the demand on the training establishment. Where possible, the PM shall maximize the use of simulation-supported embedded training, and the training systems shall fully support and mirror the interoperability of the operational system. For training programs that require training infrastructure modifications, the PM shall identify technology, schedule, and funding issues that impact program execution.

E7.7. Environment, Safety and Occupational Health (ESOH). As part of risk reduction, the PM shall prevent ESOH hazards where possible, and shall manage ESOH hazards where they cannot be avoided. The acquisition strategy shall incorporate a summary of the Programmatic ESOH Evaluation (PESHE), including ESOH risks, a strategy for integrating ESOH considerations into the systems engineering process, identification of ESOH responsibilities, a method for tracking progress, and a compliance schedule for NEPA (42 U.S.C. 4321-4370d and Executive Order 12114, references (x) and (az)). During system design, the PM shall document hazardous materials used in the system and plan for the system.s demilitarization and disposal. The CAE (or for joint programs, the CAE of the Lead Executive Component) or designee, is the approval authority for system-related NEPA and E.O. 12114 documentation. For acceptance of ESOH mishap risks identified by the program, the CAE is the acceptance authority for high risks, PEO-level for serious risks, and the PM for medium and low risks as defined in the industry standard for system safety.

E7.8. Survivability. For systems with missions that might require exposure to combat threats, the PM shall address personnel survivability issues including protection against fratricide, detection, and instantaneous, cumulative, and residual nuclear, biological, and chemical effects; the integrity of the crew compartment; and provisions for rapid egress when the system is severely damaged or destroyed. The PM shall address special equipment or gear needed to sustain crew operations in the operational environment.