Labnaf Part 3: Business Capabilities and Heat Maps

Identify enterprise functions as the high-level activities that describe what the organization does, forming a functional taxonomy and heat maps to reveal risks.

Learn why enterprise functions serve as stable architecture assets and why we avoid the term 'business capability' to prevent confusion with evolving target capabilities and roadmaps.

Identify how information entities are owned, controlled, and exchanged across enterprise functions, illustrated by birth planning and product price flows between traffic management and pricing management.

Explore how enterprise functions support architecture elements and classifications, enabling catalog packages and explicit ownership for applications, processes, roles, and information entities in the information and process portfolios.

Discover enterprise functions and build a taxonomy by organizing them into a hierarchy, using value streams as inspiration while incorporating resource entities and exchange entities to reveal missing parent functions.

Explore how enterprise functions differentiate or not, marked by a diagonal line on the icon. See externalisation patterns from outsourced bus maintenance to internal security and partially outsourced services.

Explore the enterprise functions catalog as a taxonomy and hierarchy with level-specific types and layouts. Learn how the meta model enforces consistent mappings to functional blocks at level three.

Explore catalog of access points, which define the vehicles for communicating with enterprise functions, qualify functional flows, and enable exchanges between customers and enterprise systems via email and mobile UI.

Explore viewpoints used to feed enterprise function catalogs, including three-level viewpoints and diagram types that define the elements and connectors for the enterprise functions and access points catalogs.

Explore the functional landscape diagram, illustrating top-level enterprise functions and how each level shows its parent’s content, such as the catalog and traffic management.

Explore the functional interactions viewpoint, drilling from top-level enterprise functions to deeper levels to map information exchanges, access points, and information entities across domains and blocks.

Visualize which applications realize which enterprise functions with a functional application landscape diagram. Generate complete diagrams with consistent layout, show realizations, and use color outlines to reflect property values.

Create a hierarchy of enterprise functions within marketing and sales, outlining order management, pricing management, and B2C self-service, and evaluate differentiator and externalisation in a functional catalog.

Create functional flows between enterprise functions by defining entities, access points, and information in a functional interaction diagram, linking marketing and sales with external exchanges.

Use holistic or selective heat maps to show what is going well or wrong in the enterprise, emphasizing total cost of ownership and other criteria.

Create an automatic coloring legend for the base map by selecting a prototype element, choosing a target value, and applying colors to differentiate elements.

Lenhoff automatically generates diagrams at three levels: functional domain, functional area, and functional block, showing which applications realize each function and can be regenerated from templates.

Navigate heat maps in the prolaborate portal via a web interface for non-modelers, view and edit properties with credentials, and perform impact analyses across application and enterprise dashboards.

Generate enterprise function portfolio reports in Excel or CSFI using the lab NAV folder, Doubler templates, and three detail levels to map elements to enterprise functions.

Explore a typical chart and heat map publication scenario where live data feeds an enterprise portal, is enriched through processing from multiple sources, and generates diagrams using templates.

Conclude by showing why enterprise functions and architecture assets matter, describe structure and interactions, map to applications, people, and equipment, and use heat maps to highlight oddities, problems, and risks.