Document 107

SEBoK *Organizational Structures for Systems Engineering*, Distilled

framework

SEBoK Organizational Structures for Systems Engineering, Distilled

Third-batch SEBoK distillation, batch 4/5. Read on the canonical Organizing Business and Enterprises to Perform Systems Engineering page (Part 5 > Enabling Businesses and Enterprises, lead authors Beasley, Pyster, Sillitto). The five enterprise structure types (Project / Functional / Matrix / Integrated / Product-Centered) form a clean Cluster A universal-sibling lattice at the organization-design rung, with the Rechtin "product and process must match" principle naming the lattice's discriminator-by-aspect explicitly. The page is a Cluster E institutional-ground anchor at unusual density: knowledge management, infostructure, people, process, and tools are all read as the organization-component carrier of the enterprise's accumulated SE practice. Cluster G SIPE touches at "knowledge transfer is also a psychological, cultural, and managerial issue"; Cluster D co-production at the IPT framing; Cluster K not surfaced. The page complements SE-104 (assessment rung) by supplying the design-rung counterpart.

I. Source

II. Source Read

Lead authors Richard Beasley, Art Pyster, Hillary Sillitto; Part 5 > Enabling Businesses and Enterprises. Scope: "In order for a business or enterprise to perform systems engineering well, the team must decide which specific SE capabilities the business or enterprise needs in order to be successful and then organizing to deliver those capabilities." "SE capabilities and organizational approach should support the Systems Engineering Organizational Strategy and reflect the nature of the business, its products and services, various stakeholders, business leadership focus, etc." "Knowledge and Information are key assets in a business, and their management is critical." "Knowledge transfer is just an information technology issue, but in actuality, it is also a psychological, cultural, and managerial issue, in short a human issue" (Fasser and Brettner 2002). "SE is a knowledge activity. Systems engineers need appropriate facilities for accessing, sharing and capturing knowledge, as well as for interacting effectively with the whole set of stakeholders." "The product and the process must match" (Rechtin 1991). Five enterprise structure types: Project, Functional, Matrix, Integrated, Product-Centered. Frameworks: ISO/IEC 15288 (Infrastructure Management), CMMI, ISO/IEC 9000, System Breakdown Structure, Integrated Product Teams. Six framework components: Organization Issues, Knowledge and Information Management, Enabling Infrastructure, People, Process, Tools and Methods.

III. Structural Read

Cluster A — Universal-sibling lattice (Doc 572 Appendix D), at the organization-design rung with explicit discriminator naming. The five enterprise structure types are universal-sibling lattice: each binds every SE-performing enterprise universally as a candidate organizational form, the discriminator is aspect (project-axis, function-axis, matrix-axis, integration-axis, product-axis). Rechtin's "the product and the process must match" principle names the discriminator-by-aspect logic explicitly: the organization-design choice is governed by which aspect of the enterprise's product-process pair carries the dominant structural load. This is the cleanest keeper-side articulation of the universal-sibling discriminator-by-aspect logic the corpus has read in any SEBoK page. Pairs with SE-046 Development Approaches (which SE-039 §VII.5 named as the cleanest empirical-partition-vs-universal-structure acknowledgment).

The six-component framework (Organization Issues, KIM, Infrastructure, People, Process, Tools/Methods) is a second universal-sibling lattice at the enabling-component rung — six axes binding every SE-performing enterprise. Two co-present lattices at different rungs of the same article.

Cluster E — Institutional Ground (Doc 571), §X.5 organization-vs-enterprise distinction with extreme density. This article is a Cluster E anchor candidate. Every framework component is read by Doc 571's apparatus. The explicit organization-vs-enterprise asymmetry is exactly Doc 571 §X.5: the organization-component carries formal structure (Project / Functional / Matrix / etc.), the enterprise-component carries the accumulated practice (knowledge culture, communication norms, tooling habits). Beasley et al. write the page from inside the apparatus: the formal organizational form is necessary but not sufficient; the enterprise-component must also be cultivated. Doc 571 §X.5 may want this article as the canonical anchor.

Cluster G — SIPE with Threshold (Doc 541), at the enterprise-knowledge substrate. "Knowledge transfer is also a psychological, cultural, and managerial issue, in short a human issue" reads as SIPE at the enterprise-knowledge substrate. The substrate is individual knowledge plus the documents and tools that hold it; the constraint is the organization's culture, process, and infrastructure; the threshold-crossing is when the enterprise has knowledge as a property — not "individuals know things" but "the enterprise knows." This is the third Cluster G worked example surfaced in this batch (after SE-104 maturity-assessment rung, SE-105 team-rung), supplying the enterprise-rung counterpart. Cluster G strength rises from no-movement (post SE-039) to three-instance worked-example saturation in batch 4/5 alone.

Cluster D — Co-production at sub-rungs (Doc 573), at the IPT framing. Integrated Product Teams are explicit co-production: cross-functional members co-keep the product across discipline-substrate slices. The IPT is the named co-production discipline at the enterprise-design rung. Convergent with the SE-022 (Synthesis) and SE-038 (HSI) co-production readings.

Cluster B — Multi-keeper composition (Doc 604). The Matrix structure is the canonical organizational form for multi-keeper composition: every member has two keepers (functional-line and project-line). The Matrix is the keeper-substrate composition's two-keeper case at the organization-design rung. Adds a non-engagement-scoped instance to Doc 604's cluster.

Cluster F — Pulverization (Doc 445). The System Breakdown Structure is backward-pulverization at the design-allocation rung — the system is decomposed for organizational assignment so that organizational structure mirrors product structure (Conway's Law named procedurally). This is structurally distinct from the forward-pulverization cluster.

IV. Tier-Tags

  • Organizing-for-SE scope (Beasley, Pyster, Sillitto) — π / α.
  • "Product and process must match" (Rechtin 1991) — π / α.
  • Five enterprise structure types — π / α as cited; μ / β under corpus when read as Doc 572 Appendix D universal-sibling at organization-design rung with explicit discriminator-naming.
  • Six framework components — π / α as cited; μ / β under corpus when read as second universal-sibling lattice at enabling-component rung.
  • "Knowledge transfer is also a psychological, cultural, and managerial issue" (Fasser and Brettner) — π / α as cited; μ / β under corpus when read as SIPE at enterprise-knowledge substrate.
  • IPT framing — π / α as cited; μ / β under corpus when read as Cluster D co-production at enterprise-design rung.

V. Residuals

No structural residuals. The page reads cleanly across six clusters with two co-present universal-sibling lattices at different rungs.

VI. Provisional Refinements

Cluster E anchor-article candidate (alignment with SE-039 §VII.5). SE-044 (Process Concepts) was named the canonical SEBoK-side anchor for Cluster I. SE-107 is a candidate canonical SEBoK-side anchor for Cluster E (institutional ground, §X.5 organization-vs-enterprise). The page operates inside the §X.5 apparatus explicitly, articulating the asymmetric distribution as a design principle. Worth proposing as the Cluster E anchor when SE-039 is next revised.

Cluster G SIPE saturation (third instance in batch 4/5). SE-104 (assessment rung), SE-105 (team rung), SE-107 (enterprise-knowledge rung). Cluster G moves from no-movement-in-Doc-605-§VII.5 to three-instance saturation in this batch alone. The cluster is now well past the worked-example threshold; a Doc 541 cluster-strength update is warranted in the next refinement pass.

Universal-sibling discriminator-by-aspect explicit-naming refinement. Rechtin's "product and process must match" is the cleanest keeper-side articulation of the discriminator-by-aspect logic the corpus has seen. May warrant Doc 572 Appendix D update with Rechtin as the named-principle citation.

No alignment with longitudinal-pulverization, handoff-mode evacuation, chronic-but-stable, emergent-only, universal-sibling-with-ordinal-axis, V3-as-procedure-binding, three-carrier robustness.

VII. Cross-Links

Form documents. Doc 572 (Lattice Extension, Appendix D, two co-present lattices and explicit-discriminator-naming candidate), Doc 571 (Institutional Ground, §X.5 anchor candidate), Doc 541 (SIPE, third batch instance), Doc 604 (Multi-keeper composition, Matrix as canonical two-keeper at organization rung), Doc 573 (Co-Production, IPT instance), Doc 445 (Pulverization, SBS as Conway's-Law procedural form).

Part-level reformulation. SE-008 (Part 5 — Enabling SE).

Related distillations. SE-023 (Concept Definition). SE-027 (Enterprise Systems Engineering, SIPE first instance). SE-034 (Assessing SE Performance). SE-046 (Development Approaches, empirical-partition-vs-structure acknowledgment). SE-104 (SE Maturity Assessment, batch SIPE first). SE-105 (Team Communication, batch SIPE second).

Adjacent SEBoK concepts (per source). Capability Maturity Model Integration, Systems Engineering Organizational Strategy, Roles and Competencies, Knowledge Management.

Appendix: Originating Prompt

"Apply refinements; report back for next 40" / "Continue"

(SE-107 is the fourth of eight in batch 4/5. The target Organizational Structures for SE is read as the canonical Organizing Business and Enterprises to Perform SE page. Surfaces a Cluster E anchor-article candidate and saturates Cluster G SIPE in this batch; supplies the cleanest keeper-side articulation of universal-sibling discriminator-by-aspect via Rechtin. Batch 4/5.)

Referenced Documents

More in framework