Vol. II, Ch. 2 · Part 1. Enterprise Optimization Foundations · Week 8
The General Enterprise Optimization Problem Revisited
Learning outcomes
After completing this chapter, the reader should be able to:
- Formulate the General Enterprise Optimization Problem in its canonical five-block form, discrete- and continuous-time.
- Distinguish objective functions from enterprise performance measures, and state what promotion from measure to objective adds and obliges.
- Identify enterprise decision variables and state variables, and keep the chosen/induced boundary exact.
- Construct enterprise constraint systems across the five mathematical forms and six architectural provenances.
- Differentiate equality and inequality constraints, and path, boundary, and decision-set constraints, with the multiplier previews each carries.
- Define enterprise feasibility for policies and trajectories, and certify it rather than assume it.
- Interpret enterprise solution spaces: feasible sets, optimal sets, and the value order that ranks only inside feasibility.
- Explain enterprise optimization architectures: the five-layer computational stack from declaration to implementation.
- Recognize the classes of enterprise optimization problems and place classical formulations as GEOP special cases.
- Prepare GEOP formulations for computational solution: standard forms, scaling, sparsity, and export.
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.
Review of GEOP from Volume I
Review of GEOP from Volume IEnterprise Decision Variables
Enterprise Decision VariablesEnterprise State Variables
Enterprise State VariablesObjective Functions
Objective FunctionsConstraint Systems
Constraint SystemsEnterprise Feasible Regions
Enterprise Feasible RegionsEnterprise Optimization Architectures
Enterprise Optimization ArchitecturesClasses of Enterprise Optimization Problems
Classes of Enterprise Optimization ProblemsCanonical GEOP Formulation
Canonical GEOP FormulationComputational Preparation
Computational PreparationTransition to Convex Optimization
Transition to Convex OptimizationWorked Examples
Worked ExamplesChapter Summary
Chapter SummaryExercises
ExercisesNotes and Sources
Notes and Sources
AXIOM
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.
Exercises
12 exercises, grouped A concept checks · B mathematical · C computational · D enterprise applications. Starred (★) exercises are on the advanced track. Full solutions appear in the Instructor's Manual, Chapter 2.
A. Concept checks
- 2.1Name the five constraint blocks of the canonical GEOP and give one Meridian instance of each, citing the block's architectural provenance.
- 2.2Explain why the Bolza/Mayer/Lagrange choice is representational while the -versus- content split is governance, citing Theorem (see book) and the window doctrine.
B. Mathematical exercises
- 2.3Write Example (see book)'s instance fully in the notation of Table (see book): every block, every symbol bound, empty blocks declared empty.
- 2.4Carry out Mayer-to-Lagrange for on linear dynamics: compute the induced running term explicitly and identify the policy-independent constant.
- 2.5Show that exponential discounting is a declared weight inside (define ), and that re-expressing it as an augmented-state multiplicative factor yields the same optimal set; where does Theorem (see book)(iii) enter?
- 2.6Show that rescaling constraint () and variables (diagonal, positive) preserves feasible and optimal sets; identify what the rescaling changes (conditioning, multiplier units) and record the multiplier transformation rule.
C. Computational exercises
- 2.7Prove Proposition (see book)'s open-loop clause in detail: the constant-rule subclass is a declared policy class, its induced problem has the same data as the sequence-decision problem, and feasible/optimal correspondences are bijections.
- 2.8Prove that minimal infeasible subsystems need not be unique: construct an instance with two distinct minimal subsystems and show a repair relaxing a constraint in their intersection fixes both, while one outside some subsystem fixes neither.
D. Enterprise applications
- 2.9(With AXIOM-02 or the Chapter 2 notebook.
- 2.10(With AXIOM-02 or the Chapter 2 notebook.
- 2.11Write one live decision of an enterprise you know in the full five-block template, empty blocks declared empty, every symbol of Table (see book) bound or explicitly unused.
- 2.12 ★Minimal infeasible subsystems can be exponentially numerous.
Downloads
- Lecture deck DCT_V2_Ch02_Slides.pptx · 424 KB
- Python laboratory DCT_V2_Ch02_Lab.ipynb · 9 KB
- Excel workbook DCT_V2_Ch02_Lab.xlsx · 14 KB
- Open the laboratory
All three companions consume the same seeded engine (26202), so their numbers agree by construction — the MFMF convention, carried forward.

