Document 62

SEBoK *Information Management*, Distilled

framework

SEBoK Information Management, Distilled

Next-40 distillation, batch 3, item 7. Information Management (IM) is the SEBoK Part 3 page that articulates the technical-management process for planning, executing, and controlling information provision to stakeholders so that information is unambiguous, complete, verifiable, consistent, traceable, and presentable. The data-vs-information distinction is a Doc 372 hypostatic-boundary instance: information is structured-and-interpreted data, the structure is keeper-supplied. The five major IM activities decompose universal-siblings at the information-asset rung. The five-step information-security framework is itself pin-art at the security-rung. Six corpus forms compose. Adds a tenth Cluster A instance.

I. Source

II. Source Read

IM is a technical-management process that "plans, executes, and controls the provision of information to designated stakeholders" ensuring it is unambiguous, complete, verifiable, consistent, traceable, and presentable. Purpose: enable organizations to generate, obtain, confirm, transform, retain, retrieve, disseminate, and dispose of information across the asset's lifecycle while maintaining security, accessibility, compliance. Distinctions: data is raw unstructured values; information is structured-data-in-context that has been analyzed and interpreted; an information asset is any piece or collection requiring independent management. Five major activities: (1) prepare for IM (strategy, scope, plan); (2) perform IM (collection, organization, analysis, distribution, protection, end-of-life); (3) supporting activities across life cycle; (4) integration with configuration, quality, security management; (5) continuous monitoring and adaptation. Information-security framework: define sensitivity levels, establish data classifications, determine controls, implement, monitor. Standards: ISO/IEC/IEEE 15288, ISO/IEC/IEEE 15289, NIST SP 800-160v1r1. Authors: John Metcalf, Philip Hallenbeck, Sandrine Gonthier; contributing Garry Roedler, Andy Pickard. Position: Part 3 Technical Management Processes, between Configuration Management Implementation and Quality Management.

III. Structural Read

Form V — Hypostatic Boundary (Doc 372), at data-vs-information distinction. Data-vs-information is a sharp Doc 372 case. Data is raw unstructured values; information is structured-and-interpreted. The structure is keeper-supplied (analyst's frame, classification scheme, schema). The distinction is operational not ontological: information is what data becomes when a keeper has rung-2 supplied a structuring frame. Doc 372 binds: the page does not claim "information" is a different ontological kind than "data," it names the structured-frame addition. Cluster H gets a fourth sharp case after HSI (603), Roles & Competencies (598), Decision Management (601).

Form III (extension) — Lattice Extension (Doc 572), Appendix D universal-sibling. The five IM activities are universal-sibling lattice at the information-asset rung. Each activity binds every IM engagement; the discriminator is aspect (preparation vs. performance vs. life-cycle support vs. process-integration vs. monitoring). Tenth Appendix D instance.

Form III — Substrate-and-Keeper Composition (Doc 510), with co-production. IM is keeper-side discipline over the engagement's information substrate. Information is co-produced (Doc 573): substrate-side data flows in, keeper-side structure is supplied, output is the information asset. Doc 573's three patterns map: keeper-proposes (analyst designs schema), substrate-proposes (raw-data emergence drives schema revision), on-the-fly (joint elicitation).

Form X — Institutional Ground (Doc 571), with Section X.5 organization-vs-enterprise and authority-evacuation potential. The IM plan and security-classification system live at the organization-component; the day-to-day information-handling practices live at the enterprise-component. §X.5 reads the common pathology: classification policies that remain formally authoritative while working practice has drifted (sensitivity-creep or under-classification both possible). Doc 574 authority-evacuation reads at the boundary case where information-control authority has stopped binding while the formal apparatus persists.

Form IV — Pin-Art Model (Doc 270), at security rung. The five-step information-security framework (define sensitivity levels, establish data classifications, determine controls, implement, monitor) is pin-art at the security rung. Each step is a pin-set the substrate (the engagement's information assets) is pressed through; the shape that emerges is the realized security posture.

Form VI — Pulverization (Doc 445), bidirectional. "Unambiguous, complete, verifiable, consistent, traceable, and presentable" are pulverization criteria for information assets: each candidate asset is tested against six aspect-checks. Verifiable + traceable is the paired-anchor case at the information-asset rung.

IV. Tier-Tags

  • Data-vs-information distinction — π / α as cited; μ / β under corpus as Doc 372 case.
  • Five IM activities — π / α as cited; μ / β under corpus as Doc 572 Appendix D.
  • Five-step security framework — π / α as cited; μ / β under corpus as Doc 270 pin-art.
  • Six quality criteria for information — π / α as cited; μ / β under corpus as Doc 445 pulverization aspects.
  • Standards (15288, 15289, NIST 800-160v1r1) — π / α.

V. Residuals

No structural residuals. The page composes cleanly with Doc 372 (fourth sharp case), Doc 572 Appendix D (tenth instance), Doc 573 (co-production), Doc 571 §X.5.

VI. Provisional Refinements

Cluster H reaches four sharp cases. Cluster H is the discipline-of-reading rather than topical group; four sharp instances strengthen the binding. The data-vs-information case is particularly clean because SEBoK itself articulates the distinction operationally rather than ontologically.

The "verifiable + traceable" aspect-pair as Doc 445 paired-anchor instance at the information-asset rung is a candidate refinement entry.

VII. Cross-Links

Form documents. Doc 372 (Hypostatic Boundary — fourth sharp case), Doc 572 (Lattice Extension, Appendix D — tenth instance), Doc 573 (Co-Production at Sub-Rungs), Doc 510 (Substrate-and-Keeper), Doc 571 (Institutional Ground, §X.5), Doc 574 (Authority Evacuation, boundary), Doc 270 (Pin-Art), Doc 445 (Pulverization).

Part-level reformulation. SE-006 (Part 3 — SE & Management).

Related distillations. SE-058 (Requirements Traceability — adjacent quality criterion). SE-061 (Assessment and Control — measurement adjacency). SE-063 (Measurement — information feeds measurement). SE-028 (Digital Engineering — digital-information adjacency).

Adjacent SEBoK concepts. Configuration Management, Quality Management, Measurement, Digital Engineering.

Methodology refinement candidates. Cluster H fourth-sharp-case promotion. Doc 445 verifiable-plus-traceable paired-anchor at information-asset rung.

Appendix: Originating Prompt

"Let's do the next 40 most likely articles to be most load bearing... my conjecture is that this will inform the next 40."

"It's ok to duplicate entries. It shows where the knowledge base folds back in on itself. Continue fanning out"

(SE-062 is one of the next-40 SEBoK distillations. Batch 3/5.)

Referenced Documents

More in framework