Vol. I, Ch. 2 · Part 1. Foundations · Week 1
Enterprise Systems and Transformation

Jump to any chapter
Volume I: Foundations and Mathematical Framework
- Ch. 1Introduction to Dynamic Corporate Transformation
- Ch. 2Enterprise Systems and Transformation
- Ch. 3Mathematical Foundations
- Ch. 4Enterprise Modeling Principles
- Ch. 5Enterprise State Representation
- Ch. 6Enterprise Transformation Operators
- Ch. 7Dynamic Enterprise Systems
- Ch. 8Stochastic Enterprise Dynamics
- Ch. 9Enterprise State Architecture
- Ch. 10Enterprise Capital Architecture
- Ch. 11Enterprise Performance Architecture
- Ch. 12Enterprise Risk, Resilience, and Robustness Architecture
- Ch. 13Unified Enterprise Transformation Architecture
- Ch. 14Mathematical Analysis of the Unified Enterprise Transformation Architecture
- Ch. 15Mathematical Formulation of Enterprise Optimization
- Ch. 16Synthesis, Future Directions, and Transition to Volume II
Volume II: Enterprise Optimization & Applications
- Ch. 1Introduction to Enterprise Optimization
- Ch. 2The General Enterprise Optimization Problem Revisited
- Ch. 3Convex Enterprise Optimization
- Ch. 4Nonlinear and Mixed-Integer Enterprise Optimization
- Ch. 5Dynamic Enterprise Optimization
- Ch. 6Optimal Control of Enterprise Systems
- Ch. 7Dynamic Programming for Enterprise Systems
- Ch. 8Hamilton–Jacobi–Bellman Enterprise Framework
- Ch. 9Stochastic Enterprise Optimization
- Ch. 10Neuro-Fuzzy Robust Enterprise Optimization
- Ch. 11Distributionally Robust Enterprise Optimization
- Ch. 12Multi-Objective Enterprise Optimization
- Ch. 13Machine Learning for Enterprise Transformation
- Ch. 14Artificial Intelligence for Enterprise Optimization
- Ch. 15Enterprise Digital Twins and Autonomous Enterprise Transformation
- Ch. 16Enterprise Applications and Integrated Transformation Case Studies
Lecture
Watch the chapter summary
Watch the chapter summary
Vol. I, Ch. 2Enterprise Systems and Transformation

Learning outcomes
After completing this chapter, the reader should be able to:
- Explain what it means to treat a company as an open system—state, decisions, environment, and outputs—and why planning models that project the future from the present alone cannot represent a real company.
- Describe a company's boundary as a declared modeling choice, and use Meridian's dealer network to show what moving the boundary changes and what it cannot change.
- Distinguish the levels of a company—group, division, and unit—and explain why each level's environment includes its sibling units.
- Distinguish feedback (changing decisions under a fixed rule) from adaptation (changing the rule itself), and explain why a company's rules are a form of capital.
- Interpret transformation as designed system change—of state, rules, structure, or boundary—and apply the four-stage lifecycle to one of Meridian's options.
Reading guide
Work through the chapter in section order; the full development, proofs, and worked examples are in the book — this page indexes them and does not replace them.
2.1 Systems Thinking and Enterprise Analysis
Table 2.12.2 The Enterprise as an Open System
Definition 2.1 (Enterprise System) · Proposition 2.1 (Open-System Representation) · Theorem 2.1 (Enterprise System Representation Theorem) · Table 2.22.3 Enterprise Boundaries and Environment
Definition 2.2 (Enterprise Environment) · Definition 2.3 (Enterprise Boundary) · Theorem 2.2 (Enterprise Boundary Consistency Theorem) · Figure 2.1 · Figure 2.22.4 Hierarchy and Subsystems
Definition 2.4 (Enterprise Subsystem) · Figure 2.3 · Table 2.32.5 Feedback, Adaptation, and Control
Definition 2.5 (Enterprise Feedback) · Proposition 2.2 (Feedback Consistency) · Definition 2.6 (Enterprise Adaptation) · Proposition 2.3 (Enterprise Adaptation Principle) · Table 2.4 · Figure 2.42.6 Enterprise Transformation
Definition 2.7 (Enterprise Transformation Process) · Table 2.5 · Figure 2.5Worked Example 2.1: Where Does Meridian End?
Table 2.6AXIOM Lab 1.2: Drawing Meridian's Boundary
Appendix 2.A: Formal Statements and Proofs
Theorem 2.1, formal statement and proof · Theorem 2.2, formal statement and proof · Proposition 2.3, formal statement and proof
Concepts in this chapter
AXIOM Lab
AXIOM Lab 1.2: Drawing Meridian's Boundary
The business situation. Meridian's CFO has asked for a single definition of “the enterprise” to be used in all board materials on the three options. You are on the finance team. Before recommending a definition, you want to see what each candidate boundary does to the numbers, which parts of the company are coupled to which, and how Meridian's own management rules behave under pressure.
Your objective. Use AXIOM to test boundary choices on Meridian's map of entities and flows, see how environments change from level to level, and compare a fixed management rule with an adaptive one.
What you will do. Open AXIOM, choose Lab 1.2 (module AXIOM-02), and load the Meridian entity–flow world.
- Draw boundary A. In the boundary designer, place only Meridian inside the perimeter. Record which flows the tool labels inputs, outputs, interior, and environmental.
- Move the dealers inside. Drag the dealer network across the boundary and record the new labels. Check the conservation panel: is the total set of flows unchanged? Repeat with another entity of your choice and note which moves change nothing.
- Change levels. In the hierarchy inspector, zoom from group to division to unit. For Digital Solutions, note which parts of Meridian now appear as its environment.
- Close the loop. On the feedback bench, run the efficiency example with feedback switched off and then on, and vary the feedback gain. Then switch on the adaptation law and shift the environment. Which rule copes better, and which behaves less predictably?
- Map a loop. In the loop mapper, build Industrial Systems' migration loop—volume, unit cost, customer migration—and label each link as reinforcing or balancing.
What to look for. Moving the boundary relabels flows but never changes the total (Theorem 2.2); each division's environment includes its siblings (Definition 2.4); feedback holds a target against the environment's pull, while adaptation trades predictability for flexibility (Proposition 2.3).
Discussion questions. (1) Which boundary makes the digital option look best, and is that a reason to choose it or to distrust it? (2) Which of Meridian's management rules—capital allocation, pricing, hiring—is most in need of adaptation, and what would the second-order loop look like? (3) Is Industrial Systems' migration loop structural or cyclical, and what evidence would settle the question?
Deliverable. A one-page memo to the CFO recommending a boundary for the board materials, stating which analyses it supports, which it makes harder, and what it cannot affect.
Time and outcomes. About 45–60 minutes; supports LOS 2.2, 2.3, and 2.4. The Chapter 2 Excel workbook and Python notebook on this page reproduce the lab's calculations.
This chapter is instrumented by:
Launch the module, load the chapter model, modify inputs, run the optimization, and compare against the worked examples in the book.
Downloads
All three companions come from the chapter's seeded engine: the notebook and workbook reproduce the book's Worked Example and AXIOM Lab and check every number against it — the MFMF convention, carried forward.




