BlueHour60 | Micro Operating Models for the Modern Enterprise

The enterprise problem

Existing technology is not disappearing. AI is being added to it.

What the enterprise already runsBuilt over decades, and still running the business.

ApplicationsInfrastructureCloudDataERPCRMHCMITSMCybersecurityNetworksWorkflowsPoliciesCapitalPeopleManagement structuresDecision rights

What it is adding nowOn top of everything at left, not instead of it.

AI modelsAI agentsAutonomous workflowsMachine-generated decisions

The result is more intelligence, more components, more decisions and more interactions than the operating model was designed to carry.

Complexity compounds.Each new component adds interactions with every other.
Risk can propagate.A fault in one place can travel through connected systems.
Capital can be misallocated.Spend grows faster than anyone can measure its return.
Local optimization can damage the whole.One function's gain can be another's cost.
Accountability can become unclear.When software decides, who answers for the decision?
Humans can lose visibility.No one sees how the overall system is behaving.

More intelligence requires more architecture, not less.

The agent is not the system.

The Operating Model

How the enterprise turns what it has into what it delivers.

Inputs

Strategy
Capital
Technology
Intelligence
People
Authority
Decisions
Work

Enterprise Operating Modelhow the enterprise actually runs

Business Outcomes

AI is changing several of those inputs at the same time: intelligence, technology, decisions, work and, increasingly, authority.

Adding AI to the existing enterprise is not Operating Model modernization. It puts new capabilities into a model that was never designed to coordinate them.

Operating Architecture

The discipline that connects enterprise intent with how the system actually behaves.

Every enterprise has technology architecture: what systems exist and how they connect. Few have Operating Architecture: how technology, economics, people, authority and decisions work together to produce outcomes.

Technology provides capabilities. Operating Architecture determines how those capabilities operate together.

BlueHour is not another application sitting on top of the enterprise. It works at the level where the enterprise's parts are coordinated.

Operating Architecture coordinates

TechnologyEconomicsPeopleAuthorityOperating ArchitectureWorkflowRiskIntelligenceDecisions

Outcomes

Why MOMs

A Micro Operating Model makes modernization incremental.

A Micro Operating Model (MOM) is a bounded Operating Architecture designed around a specific enterprise problem, opportunity, decision, workflow, risk or outcome.

An operating model is too large to replace in one move, and rebuilding it while the business runs is a rational thing to fear. MOMs remove the need to. A Client activates a MOM around an immediate business requirement. As requirements expand, it activates more. Their collective operation becomes the enterprise's Macro Operating Model.

BlueHour offers a tray of Micro Operating Models. The Client activates the ones its business requires.

A MOM

One bounded Operating Architecture around one requirement. Activated on its own.

Coordinated MOMs

Activated MOMs share data, authority and decisions instead of running in isolation.

Macro Operating Model

The enterprise's operating model, composed of the MOMs it has activated.

The BlueHour60™

A reference architecture for the whole enterprise.

The BlueHour60 is BlueHour's reference architecture for the Micro Operating Models modern enterprises increasingly require: sixty MOMs in six families. All sixty are shown because an architecture for the enterprise has to account for all of it.

The BlueHour60 is our current reference architecture. It will evolve as technologies, industries, regulations and Client requirements evolve.

BlueHour's methods work inside the MOMs rather than as MOMs of their own: FORT operates within Truth Preservation, and Complexity Saturation Testing within Complexity Ceiling Management. Every MOM is delivered through the same lifecycle: design, build, run, guard and value.

Select an objective or an industry to see which MOMs it might involve. Select any MOM for its purpose.

View

Objective

Industry

60 MOMs in the reference architectureConfigurations are illustrative, not prescriptions.

0xxValue & Financial CoreHow capital is committed, measured and redeployed against return.

1xxCustomer & Go-to-MarketHow commitments to customers are made, kept and explained.

2xxProduct & ChangeHow change enters a running enterprise, and how it is taken back.

3xxWork, Authority & ResilienceWho and what does the work, who decides, and how the system holds.

4xxIntelligence, Systems & TruthHow models, agents and systems operate as one estate on preserved truth.

5xxGovernance, Accountability & ValueHow authority is held to account and performance becomes value.

Activated in this viewAvailable in the reference architectureLive demonstration

Select a MOM to see its purpose and, where one exists, its live demonstration.

An important distinction

You probably don't need 60.

The BlueHour60 shows the breadth of the reference architecture. It is not a destination. A Client may begin with one MOM. Another Client's architecture may involve eight, eighteen, thirty-five or some other number. There is no requirement to reach sixty, and sixty is not a ceiling: the architecture will grow as technology, regulation, risk and Client requirements change.

1

Start with one

One immediate requirement, one activated MOM.

8

A focused objective

A defined opportunity that spans several functions.

18

A broader modernization

Several objectives pursued on one architecture.

The architecture adapts to the enterprise. The enterprise does not adapt to our catalog.

BlueHour60 is the reference architecture. Your Operating Model is the answer.

How MOMs compose

MOMs are not isolated selections. They operate together.

MOMs

Each MOM addresses a defined requirement and is valuable on its own.

Activated Client Architecture

The MOMs a Client activates, connected through one Operating Architecture.

Macro Operating Model

How the whole enterprise runs once those MOMs operate as a system.

Enterprise Outcomes

Revenue, cost, risk, operating leverage and enterprise value.

The value comes from two places: what each MOM does, and how activated MOMs interact. When they share data, authority and decisions through one Operating Architecture, their effects reinforce each other. Physicists call this constructive interference. Run separately, the same capabilities can work against each other: one optimizes cost while another raises risk. Whole-System Visibility (MOM-409) is where the difference becomes visible.

That coherence has to hold at every level. The operating intent, authority, economics, policy and decision logic set at the top of the enterprise should arrive intact inside each MOM, and what each MOM learns should travel back up. BlueHour calls this property Fractality™: the same governing logic, consistent at every scale. Strategic Intent Alignment (MOM-506) and Governance & Accountability (MOM-505) carry it through the architecture, and Truth Preservation (MOM-405) keeps it provable.

The agent is not the system. Neither is the MOM. The enterprise outcome is produced by how the whole system operates together.

The business problem decides

Start with the problem, not the catalog.

An example objective

"Increase AI productivity while reducing operating cost."

An objective like this rarely sits in one function. It could involve MOMs spanning:

CapitalCapital DisciplineMOM-001 · Live demonstration

AI economicsAI & Decision Unit EconomicsMOM-002

ApplicationsLegacy & AI CoexistenceMOM-403

WorkflowWork AllocationMOM-302

WorkforceUpboarding & WorkflowMOM-303 · Live demonstration

Decision qualityDecision QualityMOM-204

ComplexityComplexity Ceiling ManagementMOM-304 · Live demonstration RiskOperating RiskMOM-305 · Live demonstration

GovernanceGovernance & AccountabilityMOM-505

Enterprise ValueEnterprise Value & IRMOM-510

The business problem determines the MOMs. The MOM catalog does not determine the project.

Industry configurations

Same reference architecture. Different Operating Models.

Each industry draws on the same sixty MOMs in a different combination. These configurations are illustrative starting points, not prescriptions; every Client's architecture is determined by its own requirements.

14