The fourth BIZBOK blueprint answers “what does the business need to know about?” — the stable information concepts an enterprise runs on, independent of the systems that store them. It is where business architecture meets the ledger: each concept has a home in a real capability, moves through a value stream, and lands as a row in an SAP object. Click any concept to light the concepts it relates to — with cardinality — and read its full mapping.
A capability map says what the business does; the information map says what it does it to. The two are a pair — every capability acts on information concepts, and every concept is owned by a capability. Getting this model right is what keeps a data-migration honest (you can only load a Customer once you agree what a customer is), what makes an integration contract precise (which system masters the GL Account?), and what lets a close reconcile (does every Billing Document post exactly one balanced Journal Entry?). It is the same discipline as an SAP migration object catalogue and an integration map, lifted to the conceptual level and cross-mapped to the capability model.