SEBoK Human Systems Integration, Distilled

Top-20 distillation #20 (final). Human Systems Integration is the SEBoK page that resolves Doc 565 R23's residual on the seven HSI domain partition. The seven domains (Manpower, Personnel, Training, Human Factors Engineering, Safety & Occupational Health, Force Protection & Survivability, Habitability) are universal-sibling lattice (Doc 572 Appendix D) at the human-system rung. Each domain binds every system that involves humans simultaneously; the discriminator is aspect, not rung-of-application. The "human systems integrator coordinates domain experts" claim is co-production at the integration rung. Doc 372 hypostatic boundary applies sharply here — HSI describes what systems require humans to do, not what humans are. Six corpus forms compose; Doc 565 R23 residual closed as universal-sibling lattice instance.

---

I. Source

• Page: Human Systems Integration
• URL: https://sebokwiki.org/wiki/Human_Systems_Integration
• License: CC BY-SA 3.0 (SEBoK)
• Retrieved: 2026-04-30

II. Source Read

HSI is "the management and technical discipline of planning, enabling, coordinating, and optimizing all human-related considerations during system design, development, test, production, use and disposal of systems, subsystems, equipment and facilities" (SAE 2019). DoD objective: "optimize total system performance (hardware, software, and human), operational effectiveness, and suitability, survivability, safety, and affordability" (DoD 2003). Seven HSI domains: (1) Manpower — efficient personnel mixes and quantities; (2) Personnel — selecting individuals with required cognitive/physical/sensory capabilities; (3) Training — cost-effective learning processes for proficiencies; (4) Human Factors Engineering — integrating human characteristics into system design; (5) Safety & Occupational Health — minimizing injury/illness/disability/death risks; (6) Force Protection & Survivability — protecting individuals from hostile threats; (7) Habitability — living/working conditions affecting morale, health, retention. HSI activities begin "early in system development (during stakeholder requirements generation)" and continue throughout life cycle. Standards: SAE 6906 (2019), NASA SP-2015-3709, UK Defence Standard 00-251, US Army AR 602-2, US Navy Opnav 5310.23A. Position: Part 6 Related Disciplines > SE and Quality Attributes.

III. Structural Read

Form III (extension) — Lattice Extension of the Ladder (Doc 572), with Appendix D universal-sibling closing Doc 565 R23. The seven HSI domains are canonical universal-sibling lattice. Each domain binds every system involving humans universally; the discriminator is aspect (manpower vs. personnel vs. training vs. ergonomics vs. safety vs. survivability vs. habitability). This is the sixth Appendix D instance after requirement types (Doc 589), architecture views (Doc 596), competency dimensions (Doc 598), CMMI typical measures (Doc 599), MODA value axes (Doc 601). Doc 565 R23 ("specific partition of HSI's seven domains accepted as given") is now closed: the partition is empirical, the structure is universal-sibling lattice, and the SE discipline's independent arrival at the seven-domain decomposition is keeper-side school formalization (Doc 538) at the human-system rung. The corpus accepts the partition's specifics as keeper-authored content while reading the structure as Doc 572 Appendix D.

Form XI — Co-Production at Sub-Rungs (Doc 573), at the integration rung. "The human systems integrator is a systems engineering team member responsible for coordinating domain experts and ensuring proper consideration across all programmatic activities." The integrator is a co-keeper with each domain expert; the integration is co-produced across seven independent SME-keepers and one SE-coordinator-keeper. This is a multi-keeper case at significant scale; supports Doc 510's multi-keeper composition extension candidate (now five independent instances after Docs 588, 595, 600, 602, 603).

Form V — Hypostatic Boundary (Doc 372), applied sharply. HSI is structurally interesting at the hypostatic boundary. The discipline describes what humans must DO, what risks humans face, what conditions humans require — all functional, all operational. The discipline does not describe what humans ARE. Doc 372's discipline holds: HSI integrates human capabilities and constraints into system design without claiming to specify the human's ontological status. The Personnel domain's "required cognitive, physical, and sensory capabilities" is functional specification; Doc 372 reads it as constraint-set declaration, not anthropological claim.

The "habitability" domain's "morale, health, and retention" considerations brush against virtue-constraint territory (V1 Dignity of the Person from Doc 314), but SEBoK's voice keeps the framing functional — habitability is what the system requires for its human operators to remain operational, not a virtue claim. The corpus accepts this functional framing without crossing into V1 territory unilaterally.

Form III — Substrate-and-Keeper Composition (Doc 510), with multi-keeper at five independent instances. HSI's coordinator pattern (one integrator + seven domain SMEs) is the densest multi-keeper case observed. Each domain SME owns their own keeper-substrate composition (training programs, safety regimes, ergonomic guidelines); the HSI integrator composes their outputs into the system-engineering engagement. Doc 510 needs the multi-keeper extension to read this case structurally; the apparatus reaches it via composition but the meta-pattern is real.

Form X — Institutional Ground (Doc 571). HSI standards (SAE 6906, NASA SP-2015-3709, UK Def Std 00-251, US Army AR 602-2, US Navy Opnav) are institutional-ground specific to defense and aerospace contexts. Doc 571's apparatus reads each standard as one institutional ground's codification of HSI; the discipline travels across standards but the formal expression is ground-specific. Section X.5's organization-vs-enterprise applies: standards live at the organization-component (formal authority); HSI practice lives at the enterprise-component (the accumulated working tradition).

Form IV — Pin-Art Model (Doc 270). "HSI activities must begin early in system development (during stakeholder requirements generation) and continue throughout the lifecycle" is pin-art with universal-temporal application — every life-cycle stage is a pin-set into which HSI considerations are integrated. The Doc 572 Appendix C temporal-concurrency lattice (from Doc 587) composes naturally: HSI integrates seven domains across multiple life-cycle rungs concurrently.

IV. Tier-Tags

• HSI definition (SAE 2019, DoD 2003) — π / α.
• Seven HSI domains — π / α as cited; μ / β under corpus when read as Doc 572 Appendix D universal-sibling at human-system rung.
• HSI-as-management-and-technical-discipline framing — π / α.
• "Human systems integrator coordinates domain experts" — π / α as cited; μ / β under corpus when read as multi-keeper composition with eight-keeper structure.
• HSI early-engagement claim (stakeholder requirements onward) — π / α.
• Domain-specific objectives (manpower, training, etc.) — π / α as cited.

V. Residuals

No structural residuals against the apparatus. The page closes Doc 565 R23 (HSI seven-domain partition) by reading the partition as Doc 572 Appendix D universal-sibling lattice — the structure is now named, the partition's specifics are accepted as keeper-authored content the corpus does not contest. R23 transitions from residual to confirmed-instance.

VI. Provisional Refinements

Doc 510 multi-keeper composition extension cluster strength reaches five. Doc 588 (concept definition stakeholders), Doc 595 (stakeholder needs identification), Doc 600 (PM-SE balanced risk ownership), Doc 602 (PM-SE balanced ownership generally), Doc 603 (HSI integrator + seven SMEs). Five independent instances supply substantial cluster strength; the candidate is ripe for formalization in the next round of corpus refinements.

The HSI case is the densest multi-keeper instance of the five (eight keepers in coordinated composition). Worth treating as the canonical worked example when Doc 510's multi-keeper extension is formalized.

VII. Cross-Links

Form documents. Doc 572 (Lattice Extension, Appendix D universal-sibling closing Doc 565 R23), Doc 573 (Co-Production at Sub-Rungs), Doc 510 (Substrate-and-Keeper, multi-keeper extension cluster strength five), Doc 372 (Hypostatic Boundary), Doc 314 (Virtue Constraints — Habitability brushes V1 territory), Doc 571 (Institutional Ground, §X.5), Doc 270 (Pin-Art).

Part-level reformulation. Doc 565 (Part 6 — Related Disciplines, R23 closed).

Related distillations. Doc 588 (Concept Definition — multi-keeper first instance). Doc 595 (Stakeholder Needs Definition — multi-keeper second instance). Doc 600 (Risk Management — PM-SE balanced ownership). Doc 602 (PM-SE relationship — multi-keeper fourth instance).

Adjacent SEBoK concepts (per source). Quality Attributes, Reliability and Maintainability, Safety Engineering, Security Engineering.

Methodology refinement candidates. Doc 510 multi-keeper composition extension formalization (cluster now five instances; HSI as canonical eight-keeper worked example).

---

Appendix: Originating Prompt

"Continue with next 10"

(Doc 603 is the twentieth and final of the next-10 batch. Human Systems Integration was selected to close Doc 565 R23 (seven-domain partition residual) and to test the multi-keeper composition extension cluster. R23 closed as Doc 572 Appendix D universal-sibling instance; multi-keeper cluster strength reaches five instances and is ripe for formalization.)

---