Difference between revisions of "Human Systems Integration"

From SEBoK
Jump to navigation Jump to search
Line 43: Line 43:
No comments were logged for this article in the SEBoK 0.5 wiki.  Because of this, it is especially important for reviewers to provide feedback on this article.  Please see the discussion prompts below.
No comments were logged for this article in the SEBoK 0.5 wiki.  Because of this, it is especially important for reviewers to provide feedback on this article.  Please see the discussion prompts below.
[[Category: Part 6]][[Category:Topic]]
[[Category: Part 6]][[Category:Topic]]
[[Category:Systems Engineering and Specialty Engineering]]
[[Category:Systems Engineering and Specialty Engineering]]

Revision as of 21:34, 12 June 2012

human systems integration (hsi) is an interdisciplinary technical and management process for integrating human considerations with and across all system elements, an essential enabler to systems engineering practice. Human activity considered by HSI includes operating, maintaining, and supporting the system. HSI also considers training and training devices, and the infrastructure used for operations and support. (DAU, 2010). HSI incorporates the following domains as integration considerations: environment, manpower, personnel, human factors, occupational health, habitability, safety, and human survivability.

HSI Domains

Various authors catalog the HSI domains differently. Booher (2003) has one list; the US Air Force (US Air Force, 2010) has a slightly different list, and the Defense Acquisition University (2010) a third list, to name three. According to the Defense Acquisition University, the HSI domains are:

  • Environment (glossary) : Environment includes the physical conditions in and around the system, and the operational context within which the system will be operated and supported. Environmental attributes include temperature, humidity, noise, vibration, radiation, shock, air quality, among many others. This "environment" affects the human's ability to function as a part of the system. (DAU, 2010)
  • manpower : Manpower factors are those job tasks, operation/maintenance rates, associated workload, and operational conditions (e.g., risk of operator injury) that are used to determine the number and mix of personnel necessary to operate, maintain, support, and provide training for the system. (DAU, 2010)
  • personnel : Personnel factors are those human aptitudes (i.e., cognitive, physical, and sensory capabilities), knowledge, skills, abilities, and experience levels that are needed to properly perform job tasks. Personnel factors are used to develop occupational specialties for system operators, maintainers, trainers, and support personnel.(DAU, 2010)
  • training : Training is the learning process by which personnel individually or collectively acquire or enhance pre-determined job-relevant knowledge, skills, and abilities by developing their cognitive, physical, sensory, and team dynamic abilities. The "training/instructional system" integrates training concepts and strategies, as well as elements of logistic support to satisfy personnel performance levels required to operate, maintain, and support the systems. It includes the "tools" used to provide learning experiences, such as computer-based interactive courseware, simulators, actual equipment (including embedded training capabilities on actual equipment), job performance aids, and Interactive Electronic Technical Manuals. (DAU, 2010)
  • human factors : Human factors engineering is primarily concerned with designing human-machine interfaces consistent with the physical, cognitive, and sensory abilities of the user population. Human-machine interfaces include:
    • functional interfaces (functions and tasks, and allocation of functions to human performance or automation);
    • informational interfaces (information and characteristics of information that provide the human with the knowledge, understanding, and awareness of what is happening in the tactical environment and in the system);
    • environmental interfaces (the natural and artificial environments, environmental controls, and facility design);
    • co-operational interfaces (provisions for team performance, cooperation, collaboration, and communication among team members and with other personnel);
    • organizational interfaces (job design, management structure, command authority, and policies and regulations that impact behavior);
    • operational interfaces (aspects of a system that support successful operation of the system such as procedures, documentation, workloads, and job aids);
    • cognitive interfaces (decision rules, decision support systems, provisions for maintaining situational awareness, mental models of the tactical environment, provisions for knowledge generation, cognitive skills and attitudes, and memory aids); and
    • physical interfaces (hardware and software elements designed to enable and facilitate effective and safe human performance such as controls, displays, workstations, worksites, accesses, labels and markings, structures, steps and ladders, handholds, maintenance provisions, etc.). (DAU, 2010)
  • occupational health : Occupational health factors are those system design features that serve to minimize the risk of injury, acute or chronic illness, or disability; and/or reduce job performance of personnel who operate, maintain, or support the system. Prevalent issues include noise, chemical safety, atmospheric hazards (including those associated with confined space entry and oxygen deficiency), vibration, ionizing and non-ionizing radiation, and human factors issues that can create chronic disease and discomfort such as repetitive motion diseases. Many occupational health problems, particularly noise and chemical management, overlap with environmental impacts. Human factors stresses that create risk of chronic disease and discomfort overlap with occupational health considerations. (DAU, 2010)
  • habitability : Habitability factors are those living and working conditions that are necessary to sustain the morale, safety, health, and comfort of the user population. They directly contribute to personnel effectiveness and mission accomplishment, and often preclude recruitment and retention problems. Examples include: lighting, space, ventilation, and sanitation; noise and temperature control (i.e., heating and air conditioning); religious, medical, and food services availability; and berthing, bathing, and personal hygiene. Habitability consists of those characteristics of systems, facilities (temporary and permanent), and services necessary to satisfy personnel needs. Habitability factors are those living and working conditions that result in levels of personnel morale, safety, health, and comfort adequate to sustain maximum personnel effectiveness, support mission performance, and avoid personnel retention problems. (DAU, 2010)
  • safety : The design features and operating characteristics of a system that serve to minimize the potential for human or machine errors or failure that cause injurious accidents. (DAU, 2010)
  • human survivability : Survivability factors consist of those system design features that reduce the risk of fratricide, detection, and the probability of being attacked; and that enable personnel to withstand man-made hostile environments without aborting the mission, objective, or suffering acute chronic illness, disability, or death. Survivability attributes are those that contribute to the survivability of manned systems. (DAU, 2010)


Works Cited

Booher, H.R. (ed.). 2003. Handbook of Human Systems Integration. Hoboken, NJ, USA: Wiley.

DAU. 2010. Defense Acquisition Guidebook (DAG). Ft. Belvoir, VA, USA: Defense Acquisition University (DAU)/U.S. Department of Defense (DoD). February 19, 2010.

US Air Force. 2009. Air Force Human Systems Integration Handbook. Brooks City-Base, TX, USA: Directorate of Human Performance Integration. Available at the Wright Paterson AFB website.

Primary References

DAU. 2010. Defense Acquisition Guidebook (DAG). Ft. Belvoir, VA, USA: Defense Acquisition University (DAU)/U.S. Department of Defense (DoD). February 19, 2010.

Additional References

Pew, R.W. and A.S. Mavor. 2007. Human-System Integration in the System Development Process: A New Look. Washington, DC, USA: National Academies Press.

< Previous Article | Parent Article | Next Article >

Comments from SEBok 0.5 Wiki

No comments were logged for this article in the SEBoK 0.5 wiki. Because of this, it is especially important for reviewers to provide feedback on this article. Please see the discussion prompts below.

SEBoK v. 1.9.1 released 30 September 2018

SEBoK Discussion

Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.

If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.

blog comments powered by Disqus