Human Systems Integration (HSI)

Overview

Systems engineering (SE) addresses the three major elements of each system: hardware, software and human. SE integrates human capability considerations with the other specialty engineering disciplines to achieve total system performance requirements by factoring into the system design the capabilities and limitations of the human operators, maintainers and users. Within the SE process, HSI involves both the technical and program management efforts that provide integrated and comprehensive analysis, design, and assessment of human performance requirements, concepts, and resources for the seven HSI domains. HSI supports enhanced operational effectiveness, optimal system design, and reduction in Total Ownership Cost (TOC).

DoDI 5000.95, Human Systems Integration in Defense Acquisition, describes planning considerations for seven HSI domains. It further states: ???The PM will plan for and implement HSI beginning early in the acquisition process and throughout the product life cycle. The goal will be to optimize total system performance and TOC, while ensuring that the system is designed, operated, and maintained to effectively provide the user with the ability to complete their mission. PMs will ensure that the DoD Component HSI staff is aware of and engaged with Working-level IPTs (WIPTs) tasked with the development and review of program planning documents that reflect HSI and that they inform program decisions.??? The HSI Guidebook covers HSI activities throughout concept development, design, test, production, deployment, operational use, and disposal and addresses HSI domain activities, trade-offs, and the integration of HSI with systems engineering and logistics. Execution of HSI activities should be tailored to the unique acquisition program.

Throughout the acquisition life cycle, the Systems Engineer should apply Human Systems Integration (HSI) design criteria, principles and practices described in MIL-STD-1472 (Human Engineering) and MIL-STD-46855 (Human Engineering Requirements for Military Systems, Equipment and Facilities).

The HSI effort assists the Systems Engineer to minimize ownership costs and ensure the system is built to accommodate the human performance characteristics of users who operate, maintain and support the total system. The total system includes not only the mission equipment but also the users, training and training devices and operational and support infrastructure.

Role of the PM and SE

The PM is responsible for integrating the HSI effort into the program (see HSI Guidebook).

The Systems Engineer supports the PM by leading HSI efforts aligned to the SE process. The Systems Engineer should work with the manpower, personnel, training, safety, health, habitability, personnel survivability and Human Factors Engineering (HFE) stakeholders to develop the HSI effort. The Systems Engineer translates and integrates those human capability considerations, as contained in the capabilities documents, into quantifiable system requirements. Requirements for conducting HSI efforts should be specified for inclusion in the Statement of Work and contract. HSI should also be addressed in the Systems Engineering Plan (SEP), specifications, Test and Evaluation Master Plan (TEMP), Software Development Plan (SDP), Life-Cycle Sustainment Plan (LCSP) and other appropriate program documentation. The SEP Outline requires that HSI be addressed as a design consideration.

Outcomes of Effective HSI

Elements of an effective HSI should (see HSI Guidebook):

Provide an optimized operational solution to the warfighters.

In the conduct of systems engineering technical reviews, emphasis is placed on assessing the following HSI attributes:

HSI domain experts should review the elements of the Analysis of Alternatives (AoA) devoted to HSI considerations (i.e., manpower, personnel, and training). In addition, HSI domain experts should ensure that the preferred solution considers the end user besides just the hardware and software components in the system. Defining the intended end user population through a Target Audience Description (TAD) provides boundary conditions for defining the required human performance parameters.

The Systems Engineer should review HSI requirements and determine if they have been implemented in the system design. HSI requirements should be specified in both the ICD and draft Capability Development Document (CDD).

System Integration (SI) practitioners and domain-level SMEs (e.g., HFEs) involvement should ensure that the functional baseline is compliant with human factors design guidance, and standards. Human performance and end user requirements should be sufficiently detailed and understood to enable system design to proceed. System requirements should be allocated among hardware, software, and human functions. The HSI Plan (HSIP) and other related acquisition documents are updated as required.

Some design decisions leading up to PDR may precipitate discussions with the operational requirements community and consultation with HSI practitioner because they could have an impact on the CDD, contributing to trade-off analyses. Critical Design Review (CDR) determines whether the hardware, human, and software final detail designs are complete. HSI should ensure that the detailed design satisfied known HFE and other HSI requirements.

The HSI practitioner has access to many tools to support the PM and SE, including HSI simulation tools (e.g., for task network modeling or digital human modeling), guidelines and standards, checklists, subjective assessments, and other resources. Models and simulations provide a mechanism to define, visualize, and adjust parameters for human contribution to implementing a Digital Engineering (DE) enterprise. Digital Human Modeling (DHM) provides a digital representation of a human (or set of humans) and a virtual environment that represents the system within which the user needs to fit, see, reach, or otherwise physically interact. Any HSI tool can be used to aid in the application of SE methods and complement the use of SE tools that ensure systems consider human limitations and capabilities across the spectrum of HSI domains, such as:

For access to the HSI body of knowledge online repository, see HSI Guidebook.

Products and Tasks

Product Tasks
10-10-1: Document human systems integration (HSI) activities incorporated into the SEP
  1. Obtain the Concept of Operations/Operational Mode Summary/Mission Profile (CONOPS/OMS/MP), as well as requirements documents, the system specification (if available) and related acquisition documentation for the system.
  2. Determine how the program will address human factors engineering, manpower, personnel, training, habitability, and personnel survivability requirements and constraints.
  3. Document the human systems integration (HSI) requirements and constraint handling procedures, along with known HSI issues, and incorporate them into the overall design and design trade-offs in accordance with current guidance.
  4. Verify incorporation of the HSI activities into the program???s systems engineering plan.

Source: AWQI eWorkbook


Resources

Key Terms

Policy and Guidance

DAU Training Courses

DAU Communities of Practice

DAU Media

On this page

  1. Overview
  2. Role of the PM and SE
  3. Outcomes of Effective HSI
  4. Resources
Back to top