Northstar Equipment Services

See the enterprise.
Understand the decision.

Four core domains: Capabilities, Value Streams, Organization, and Information. Explore how they connect to deliver customer value and inform strategy and change.

New to the case?The guided lessons introduce the connections one step at a time.Start the short learning path →

Choose an Atlas tour or explore the map below.

Fictional teaching case · Includes all three decision outcomes through May 6, 2026. Try the independent exercise first. About the sources and earlier assessments.

Guided learning

Choose a question.
Follow the evidence.

Four short journeys through the same enterprise.

Loading interactive controls. The enterprise map and complete text reference are available below.

Enterprise

An enterprise is a set of connected promises.

Capabilities, Value Streams, Organization, and Information: four core domains connected around Northstar’s service-reliability challenge.

How to use this view
Business question
What has to work together for a dependable customer promise?
Reasonable inference
The layers reveal where strategy relies on customer value, business abilities, shared meaning, and accountable decisions.
Evidence boundary
This is a decision-focused slice of Northstar, not a complete enterprise model. A connection is not causal proof.
In practice
Select an element, inspect its evidence, then follow the relationship that could change the next decision.
01

Strategic intent

The direction and guardrails

02

Intended outcomes

What needs to become different

03

Capabilities

Enterprise abilities; open the full hierarchy

04

Value Streams

Whole streams, decomposed into stages that deliver stakeholder value

05

Organization

Organizational contribution and accountability

06

Information

Shared business meaning, not database tables

07

Enterprise change

Choices and dependencies

08

Supporting records

Implementation context with bounded acceptance

A map with a paper trail

Inspect the evidence. Keep the boundaries.

A fictional $780 million equipment-maintenance and rental company with 48 branches in twelve states and 3,200 employees. Its central question: can it make dependable service promises while protecting customer value and margin?

Complete text reference · 109 elements

Seven selected enterprise branches with explicit object boundaries. This is an authored hierarchy for the fictional case, not a complete enterprise map or a BIZBOK reference model. Original C-100–C-180 IDs remain stable; original decision labels are retained as aliases. The added parents, siblings, names, and levels are modeling additions, not evidence of approval in Decisions 1–3.

Dependable customer commitments OUT-01 · Intended outcome

Customers receive commitments that can be kept, changed transparently, or escalated through a usable exception route

Intended outcome extracted from the existing objective table. The Atlas identifier is a modeling extension; this is not a new outcome claim.

Boundary: A common policy must not prevent branches from responding to legitimate local conditions

Protect service margin O-02 · Strategic objective

Protect service margin

Reliability improves without transferring hidden cost or capacity burden to branches, technicians, or adjacent work

Boundary: Margin, technician productivity, implementation cost, and capacity remain visible

Margin without hidden burden OUT-02 · Intended outcome

Reliability improves without transferring hidden cost or capacity burden to branches, technicians, or adjacent work

Intended outcome extracted from the existing objective table. The Atlas identifier is a modeling extension; this is not a new outcome claim.

Boundary: Margin, technician productivity, implementation cost, and capacity remain visible

Less disruption and repeat work OUT-03 · Intended outcome

Fewer customers experience preventable return visits, missed commitments, and recoverable escalations

Intended outcome extracted from the existing objective table. The Atlas identifier is a modeling extension; this is not a new outcome claim.

Boundary: Cause coding, customer escalation, and branch-level variation remain visible

Restore Equipment Availability VS-01 · Value stream

Restore usable equipment availability for the customer operations manager.

The whole stream begins when the customer operations manager requests help for equipment that is unavailable or at risk. Its five stages contribute value toward restored usable availability confirmed by that customer.

Triggering need
Equipment is unavailable or at risk, prompting the customer operations manager to request service.
Fulfillment
Restored availability and customer acceptance are evidenced and reconciled to the agreed service commitment.

Boundary: A value stream is not a departmental process or a project plan.

Customer-confirmed restored equipment availability VP-01 · Value proposition

Usable equipment availability restored for the customer operations manager and confirmed against the agreed service commitment.

The desired value of VS-01, expressed from the triggering stakeholder’s perspective. The stage value items collectively contribute to it; recovery or termination without fulfillment does not deliver it.

Boundary: A value proposition states desired value. A map, completed task, or improved measure does not establish that it has been fulfilled.

Identify need ST-01 · Value stream stage

Recognize and qualify the customer’s equipment-service need so it can receive an accountable response.

An accepted, actionable need

Entering
Equipment problem is emerging or known
Exiting
A valid service need is accepted and classified
Entry criterion
Equipment problem or risk is known
Exit criterion
Asset, urgency, requester authority, location, and contact data are valid
Participating stakeholders
ORG-01 Customer operations manager; ORG-03 Dispatcher

Boundary: A stage has participating stakeholders and entry and exit criteria. Its value items contribute to the whole stream’s value proposition; completing a task alone does not establish value.

An accepted, actionable need VI-01 · Value item

An accepted, actionable need

The value-item entry from Identify need. It accrues toward the stream’s value proposition when the applicable fulfillment conditions hold. Recovery evidence keeps the remaining obligation visible.

Boundary: A value item is distinct from its stage, a task, an information record, and a KPI. Recovery evidence does not substitute for fulfilled customer value.

Define service promise ST-02 · Value stream stage

Establish and communicate a feasible commitment using the service need, resource signals, and applicable policy.

A credible commitment accepted by the customer

Entering
Need is accepted but timing is uncertain
Exiting
A feasible commitment is understood and accepted
Entry criterion
A valid service need is accepted and classified
Exit criterion
Promise reflects POL-01, skill, part, geography, capacity, and any approved exception
Participating stakeholders
ORG-01 Customer operations manager; ORG-03 Dispatcher; parts and scheduling contributors; ORG-02 / ORG-05 for exceptions

Boundary: A stage has participating stakeholders and entry and exit criteria. Its value items contribute to the whole stream’s value proposition; completing a task alone does not establish value.

A credible commitment accepted by the customer VI-02 · Value item

A credible commitment accepted by the customer

The value-item entry from Define service promise. It accrues toward the stream’s value proposition when the applicable fulfillment conditions hold. Recovery evidence keeps the remaining obligation visible.

Boundary: A value item is distinct from its stage, a task, an information record, and a KPI. Recovery evidence does not substitute for fulfilled customer value.

Prepare service ST-03 · Value stream stage

Coordinate prerequisites and resource confirmations so the promised service can proceed.

Service ready to execute

Entering
Commitment exists but work is not ready
Exiting
Work is ready to execute
Entry criterion
A governed customer promise exists
Exit criterion
Work order, technician assignment, required reservation, and access conditions are confirmed
Participating stakeholders
ORG-03 Dispatcher; ORG-04 Field technician; parts contributors; ORG-01 for site access

Boundary: A stage has participating stakeholders and entry and exit criteria. Its value items contribute to the whole stream’s value proposition; completing a task alone does not establish value.

Service ready to execute VI-03 · Value item

Service ready to execute

The value-item entry from Prepare service. It accrues toward the stream’s value proposition when the applicable fulfillment conditions hold. Recovery evidence keeps the remaining obligation visible.

Boundary: A value item is distinct from its stage, a task, an information record, and a KPI. Recovery evidence does not substitute for fulfilled customer value.

Perform service ST-04 · Value stream stage

Carry out the authorized intervention and establish its equipment-condition result and any remaining exceptions.

Restored equipment condition, or explicit evidence that further recovery is required

Entering
Work is ready
Exiting
Equipment condition is restored or otherwise dispositioned
Entry criterion
Work package is ready
Exit criterion
Work outcome, consumption, and exceptions are recorded
Participating stakeholders
ORG-04 Field technician; ORG-01 Customer operations manager

Boundary: A stage has participating stakeholders and entry and exit criteria. Its value items contribute to the whole stream’s value proposition; completing a task alone does not establish value.

Restored equipment condition, or explicit evidence that further recovery is required VI-04 · Value item

Restored equipment condition, or explicit evidence that further recovery is required

The value-item entry from Perform service. It accrues toward the stream’s value proposition when the applicable fulfillment conditions hold. Recovery evidence keeps the remaining obligation visible.

Boundary: A value item is distinct from its stage, a task, an information record, and a KPI. Recovery evidence does not substitute for fulfilled customer value.

Confirm outcome ST-05 · Value stream stage

Verify the customer’s receipt of restored availability, reconcile it to the commitment, and determine success, further recovery, or termination without fulfillment.

Confirmed restored availability on success; a documented outstanding obligation or unfulfilled termination otherwise

Entering
Service occurred but value is unconfirmed
Exiting
Equipment availability is restored and the customer confirms the agreed outcome
Entry criterion
A recorded work outcome exists
Exit criterion
Success: restored availability and customer acceptance are evidenced and reconciled to the promise. Recovery: reenter the relevant stages with an open value obligation. If restoration cannot be achieved, record termination without fulfillment and resulting obligations
Participating stakeholders
ORG-01 Customer operations manager; customer-recovery contributors; ORG-04 for work-outcome evidence

Boundary: A stage has participating stakeholders and entry and exit criteria. Its value items contribute to the whole stream’s value proposition; completing a task alone does not establish value.

Confirmed restored availability on success; a documented outstanding obligation or unfulfilled termination otherwise VI-05 · Value item

Confirmed restored availability on success; a documented outstanding obligation or unfulfilled termination otherwise

The value-item entry from Confirm outcome. It accrues toward the stream’s value proposition when the applicable fulfillment conditions hold. Recovery evidence keeps the remaining obligation visible.

Boundary: A value item is distinct from its stage, a task, an information record, and a KPI. Recovery evidence does not substitute for fulfilled customer value.

Service Request Management C-010 · Business capability

Establish and maintain a recognized equipment-service need, then govern its disposition against the requested customer outcome.

Establish and maintain a recognized equipment-service need, then govern its disposition against the requested customer outcome.

Focal object
Service Request (BO-01)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Service Request Qualification C-100 · Business capability

Identify, accept, qualify, and maintain a service need; exclude the customer commitment and authorization of work.

Identify, accept, qualify, and maintain a service need; exclude the customer commitment and authorization of work.

Focal object
Service Request (BO-01)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Service Request Resolution C-160 · Business capability

Reconcile the request, promise, and work result; confirm restored availability and customer acceptance, retain open recovery obligations, or record termination without fulfillment.

Northstar must establish that the equipment is usable and the customer confirms the outcome. A recovery handoff leaves the value obligation open.

Focal object
Service Request (BO-01)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Success can be overstated if revised commitments replace the original customer need.

Customer Promise Management C-110 · Business capability

Establish, validate, communicate, monitor, and revise a governed customer commitment; use resource evidence without planning work or owning resource allocations or final customer-value acceptance.

The customer commitment is the center of this case. Dispatchers need dependable part, skill, geography, and capacity signals before confirming a date, or a usable approved exception.

Focal object
Customer Promise (BO-02)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Premature commitments, incompatible regional definitions, and difficult exception routes. Later promises may improve adherence while delaying restoration.

Customer Promise Definition C-111 · Business capability

Specify the proposed commitment, its scope, timing, and terms.

Specify the proposed commitment, its scope, timing, and terms.

Focal object
Customer Promise (BO-02)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Customer Promise Validation C-112 · Business capability

Assess the proposed commitment against policy and the available feasibility evidence.

Assess the proposed commitment against policy and the available feasibility evidence.

Focal object
Customer Promise (BO-02)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Customer Promise Communication C-113 · Business capability

Communicate the commitment and its status to the parties who rely on it.

Communicate the commitment and its status to the parties who rely on it.

Focal object
Customer Promise (BO-02)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Customer Promise Monitoring C-114 · Business capability

Determine the commitment’s current standing and whether its terms are being met.

Determine the commitment’s current standing and whether its terms are being met.

Focal object
Customer Promise (BO-02)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Customer Promise Change C-115 · Business capability

Revise, cancel, or supersede the commitment while retaining its history and obligations.

Revise, cancel, or supersede the commitment while retaining its history and obligations.

Focal object
Customer Promise (BO-02)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Work Order Management C-030 · Business capability

Specify and authorize a unit of service work, perform and record it, then reconcile and close its work record; exclude customer-value acceptance and resource ownership.

Specify and authorize a unit of service work, perform and record it, then reconcile and close its work record; exclude customer-value acceptance and resource ownership.

Focal object
Work Order (BO-03)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Work Order Planning C-120 · Business capability

Translate an accepted need into authorized work scope, method, and prerequisites; exclude capacity assignment and execution.

Translate an accepted need into authorized work scope, method, and prerequisites; exclude capacity assignment and execution.

Focal object
Work Order (BO-03)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Work Order Execution C-150 · Business capability

Perform and record the authorized equipment intervention and its exceptions; exclude customer acceptance and promise policy.

Perform and record the authorized equipment intervention and its exceptions; exclude customer acceptance and promise policy.

Focal object
Work Order (BO-03)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Work Order Closure C-151 · Business capability

Reconcile recorded work, consumption, and exceptions and determine administrative closure or cancellation; closure alone does not prove delivered customer value.

Reconcile recorded work, consumption, and exceptions and determine administrative closure or cancellation; closure alone does not prove delivered customer value.

Focal object
Work Order (BO-03)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Human Resource Management C-040 · Business capability

Govern the identity and engagement of people whose work the enterprise uses, their qualifications and availability, and their assignment to demand; cross-map agreements, payments, and organizational units.

Govern the identity and engagement of people whose work the enterprise uses, their qualifications and availability, and their assignment to demand; cross-map agreements, payments, and organizational units.

Focal object
Human Resource
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Human Resource Engagement C-131 · Business capability

Establish and maintain a person’s working relationship with the enterprise, including entry, changes, and exit.

Establish and maintain a person’s working relationship with the enterprise, including entry, changes, and exit.

Focal object
Human Resource
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Human Resource Qualification C-132 · Business capability

Establish and maintain the evidence of a person’s skills and qualifications.

Establish and maintain the evidence of a person’s skills and qualifications.

Focal object
Human Resource
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Human Resource Availability C-133 · Business capability

Determine the person’s available time, location, and capacity constraints.

Determine the person’s available time, location, and capacity constraints.

Focal object
Human Resource
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Human Resource Scheduling C-130 · Business capability

Match authorized demand to qualified people, time, geography, and capacity; govern the resulting assignments without owning parts or customer commitments.

Qualified people, time, geography, and capacity must line up. The rural branch has limited skill substitution and long travel.

Focal object
Human Resource
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: The compact SCALE workspace assigns a coordination owner to ORG-05. The detailed capability register assigns performance accountability to ORG-07. This Atlas keeps ORG-07 accountable and maps ORG-05 as a regional contributor.

Part Management C-050 · Business capability

Define and acquire physical components used in equipment service, govern their availability and use, and retire unusable or obsolete components; cross-map suppliers, payments, and equipment assets.

Define and acquire physical components used in equipment service, govern their availability and use, and retire unusable or obsolete components; cross-map suppliers, payments, and equipment assets.

Focal object
Part
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Part Definition C-141 · Business capability

Establish and maintain the identity, specification, and permitted use of a physical service component.

Establish and maintain the identity, specification, and permitted use of a physical service component.

Focal object
Part
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Part Acquisition C-142 · Business capability

Obtain and accept components that satisfy the defined service need.

Obtain and accept components that satisfy the defined service need.

Focal object
Part
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Part Availability Management C-140 · Business capability

Determine, reserve, position, consume, release, and expire availability of service components; exclude technician assignments and customer commitments.

“Allocated” did not consistently mean a confirmed reservation. ORG-08 owns BO-05; its inventory source is only provisional for R1.

Focal object
Part
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Enterprise source authority remains open under OI-06; manual controls require recurring capacity.

Part Retirement C-143 · Business capability

Determine and govern withdrawal or disposal of unusable or obsolete components.

Determine and govern withdrawal or disposal of unusable or obsolete components.

Focal object
Part
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Performance Measure Management C-170 · Business capability

Define business measures and guardrail thresholds, determine their observed values, and interpret and govern their use; exclude source transactions and operational remediation.

Measures preserve the version of the promise, population, period, scope changes, and financial guardrails.

Focal object
Performance Measure (M-* register)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Later-period confirmation and policy compliance are not cumulative measures; they are not nested sets.

Performance Measure Definition C-171 · Business capability

Specify a measure’s meaning, calculation, population, period, and guardrail thresholds.

Specify a measure’s meaning, calculation, population, period, and guardrail thresholds.

Focal object
Performance Measure (M-* register)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Performance Measure Determination C-172 · Business capability

Calculate and substantiate the measure’s value from governed evidence.

Calculate and substantiate the measure’s value from governed evidence.

Focal object
Performance Measure (M-* register)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Performance Measure Review C-173 · Business capability

Interpret, explain, review, and govern use of the measure and any decision implications.

Interpret, explain, review, and govern use of the measure and any decision implications.

Focal object
Performance Measure (M-* register)
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Information Definition Governance C-180 · Business capability

Establish shared business meaning, semantic accountability, quality requirements, and controlled changes to information definitions; exclude the operational decisions represented by that information.

Shared meaning and source authority must survive handoffs among Dispatch, Supply, Operations, and Technology.

Focal object
Business Information Definition
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Do not transfer operating accountability to information stewards.

Information Definition Structuring C-181 · Business capability

Specify a concept’s meaning, category, types, states, and typed relationships.

Specify a concept’s meaning, category, types, states, and typed relationships.

Focal object
Business Information Definition
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Information Definition Stewardship C-182 · Business capability

Assign and maintain accountable owners and stewards for the definition.

Assign and maintain accountable owners and stewards for the definition.

Focal object
Business Information Definition
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Information Quality Rule Definition C-183 · Business capability

Specify the quality rules and thresholds associated with the definition.

Specify the quality rules and thresholds associated with the definition.

Focal object
Business Information Definition
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Information Definition Change Control C-184 · Business capability

Evaluate, authorize, version, and communicate changes in shared business meaning.

Evaluate, authorize, version, and communicate changes in shared business meaning.

Focal object
Business Information Definition
Hierarchy provenance
Authored October 6, 2026 correction; added context does not imply an approved case decision.

Boundary: Capability structure alone cannot establish maturity, causation, ROI, or investment priority.

Service Request BO-01 · Information concept

A customer-recognized need for equipment service that Northstar has accepted for evaluation or action.

ticket; service call; case

Concept category
Primary (authored modeling judgment)
Source status
Current service record accepted for R1
Nonterminal states
Draft; Submitted; Accepted; Qualified; Planned
Terminal states
Resolved; Declined; Cancelled
Concept types
Not established by case; do not infer types from states.

Boundary: A concept is distinct from a report, database field, or application record.

Customer Promise BO-02 · Information concept

A governed commitment to provide a defined service outcome within stated conditions and timing.

Preserve the original commitment, linked revisions, cancellation reasons, and recovery obligation.

Concept category
Primary (authored modeling judgment)
Source status
Current promise record accepted for R1 under E-008 version/linkage audit; not declared the enterprise future-state source
Nonterminal states
Proposed; Validated; Committed
Terminal states
Fulfilled; Broken; Cancelled; or superseded by a linked Revised promise
Concept types
Not established by case; do not infer types from states.

Boundary: ETA is an estimate; a commit date is an attribute. Neither is automatically the business commitment.

Work Order BO-03 · Information concept

An authorized unit of service work with scope, asset, status, and completion evidence.

job; service order

Concept category
Primary (authored modeling judgment)
Source status
Current work-order record accepted for R1
Nonterminal states
Proposed; Authorized; Scheduled; In Progress; Completed; Suspended
Terminal states
Closed; Cancelled
Concept types
Not established by case; do not infer types from states.

Boundary: A concept is distinct from a report, database field, or application record.

Equipment Asset BO-04 · Information concept

A uniquely recognized item of customer equipment whose condition and service history matter.

unit; machine: contextual shorthand. serial: identifier, not an object synonym.

Concept category
Primary (authored modeling judgment)
Source status
Enterprise asset register accepted
Nonterminal states
Registered; Available; Unavailable; Under Service
Terminal states
Retired
Concept types
Not established by case; do not infer types from states.

Boundary: A concept is distinct from a report, database field, or application record.

Part Reservation BO-05 · Information concept

A time-bounded allocation of a specific part quantity to planned service work.

Ownership was proposed in Decision 1 and confirmed for ORG-08 in Decision 2. The inventory record remains a provisional R1 source with twice-daily reconciliation.

Concept category
Secondary (authored modeling judgment)
Source status
Inventory reservation record accepted only as provisional R1 source with twice-daily reconciliation; enterprise authority remains OI-06
Nonterminal states
Requested; Confirmed; Picked
Terminal states
Consumed; Released; Expired
Concept types
Not established by case; do not infer types from states.

Boundary: Seven of 24 inspected sequences had delayed updates; four uses of “allocated” did not mean confirmed. This purposive diagnostic is not an enterprise defect rate.

Technician Assignment BO-06 · Information concept

A governed allocation of a qualified technician and time window to service work.

An accepted assignment and verified skill qualification are separate checks.

Concept category
Secondary (authored modeling judgment)
Source status
Scheduling record accepted for R1 subject to skill-data validation
Nonterminal states
Proposed; Accepted; Dispatched; Arrived; In Progress
Terminal states
Completed; Rejected; Reassigned; Cancelled
Concept types
Not established by case; do not infer types from states.

Boundary: The detailed object register assigns ORG-07 ownership; ORG-05 coordinates regional capacity. The compact workspace uses ORG-05 as owner, so the different scopes remain explicit.

Customer operations manager ORG-01 · Stakeholder / authority

Needs equipment restored when promised

Accepts, changes, or cancels the customer commitment on behalf of the customer

Decision rights
Accepts, changes, or cancels the customer commitment on behalf of the customer

Boundary: Architecture stewardship does not confer investment or operating authority.

Branch manager ORG-02 · Stakeholder / authority

Balances customer commitments, capacity, margin, and local conditions

Owns branch adoption, local capacity choices, and use of the approved exception route

Decision rights
Owns branch adoption, local capacity choices, and use of the approved exception route

Boundary: Architecture stewardship does not confer investment or operating authority.

Dispatcher ORG-03 · Stakeholder / authority

Creates feasible promises and sequences work

Applies policy and raises exceptions; cannot waive enterprise guardrails

Decision rights
Applies policy and raises exceptions; cannot waive enterprise guardrails

Boundary: Architecture stewardship does not confer investment or operating authority.

Field technician ORG-04 · Stakeholder / authority

Executes work and records actual conditions

Confirms execution facts and exception causes

Decision rights
Confirms execution facts and exception causes

Boundary: Architecture stewardship does not confer investment or operating authority.

Regional VP Operations ORG-05 · Stakeholder / authority

Coordinates capacity and resolves cross-branch operating conflicts

Approves defined regional exceptions and is accountable for readiness across participating branches

Decision rights
Approves defined regional exceptions and is accountable for readiness across participating branches

Boundary: Architecture stewardship does not confer investment or operating authority.

VP Customer Operations ORG-06 · Stakeholder / authority

Represents customer outcome and service recovery

Owns customer-disruption definition and service-recovery practice

Decision rights
Owns customer-disruption definition and service-recovery practice

Boundary: Architecture stewardship does not confer investment or operating authority.

VP Field Service ORG-07 · Stakeholder / authority

Owns field work planning, scheduling, execution, and workforce capacity

Approves operating practices within delegated authority

Decision rights
Approves operating practices within delegated authority

Boundary: Architecture stewardship does not confer investment or operating authority.

VP Supply Operations ORG-08 · Stakeholder / authority

Owns part-availability operating performance

Approves part-reservation rules and operating remediation

Decision rights
Approves part-reservation rules and operating remediation

Boundary: Architecture stewardship does not confer investment or operating authority.

EVP Service Operations ORG-09 · Stakeholder / authority

Sponsors I-01 and owns the service outcome

Accountable for C-110 and C-170 performance and approves POL-01 with required contributors

Decision rights
Accountable for C-110 and C-170 performance and approves POL-01 with required contributors

Boundary: Architecture stewardship does not confer investment or operating authority.

Chief Data Officer ORG-10 · Stakeholder / authority

Owns enterprise information-governance policy

Confirms business-object ownership and stewardship; does not own service performance

Decision rights
Confirms business-object ownership and stewardship; does not own service performance

Boundary: Architecture stewardship does not confer investment or operating authority.

Chief Information Officer ORG-11 · Stakeholder / authority

Owns technology standards and service risk

Approves technology standards; does not own service-policy outcomes or vendor value claims

Decision rights
Approves technology standards; does not own service-policy outcomes or vendor value claims

Boundary: Architecture stewardship does not confer investment or operating authority.

Investment Council ORG-13 · Stakeholder / authority

Balances value, capacity, risk, and opportunity cost

Approves, conditions, defers, or rejects funding and later scale/procurement gates

Decision rights
Approves, conditions, defers, or rejects funding and later scale/procurement gates

Boundary: Architecture stewardship does not confer investment or operating authority.

Business architect ORG-14 · Stakeholder / authority

Maintains the decision frame and architecture trace

Frames, models, tests, recommends, and records; does not take the business decision

Decision rights
Frames, models, tests, recommends, and records; does not take the business decision

Boundary: Architecture stewardship does not confer investment or operating authority.

R1 Readiness Forum ORG-15 · Stakeholder / authority

Brings Operations, Customer, Field, Supply, Information, Technology, Finance, and Delivery evidence together for the authorized release

Under authority delegated by ORG-13, may activate, stagger, adapt, pause, or stop R1 within the approved scope and cost/capacity band. Only where a governed guardrail explicitly permits, it may authorize one contained remediation interval to the next formal review after the named owner validates the breach; it may not waive or renew the exception, expand to R2, exceed an investment boundary, or reopen procurement.

Decision rights
Under authority delegated by ORG-13, may activate, stagger, adapt, pause, or stop R1 within the approved scope and cost/capacity band. Only where a governed guardrail explicitly permits, it may authorize one contained remediation interval to the next formal review after the named owner validates the breach; it may not waive or renew the exception, expand to R2, exceed an investment boundary, or reopen procurement.

Boundary: Architecture stewardship does not confer investment or operating authority.

Supply Operations OU-03 · Organizational unit

Part availability and reservation operations

Part availability and reservation operations

Boundary: Organizational contribution does not transfer decision rights or create a capability parent.

Service Operations OU-04 · Organizational unit

Enterprise service performance and promise policy

Enterprise service performance and promise policy

Boundary: Organizational contribution does not transfer decision rights or create a capability parent.

R1 Readiness Forum OU-06 · Organizational unit

Collaborative governance team for the authorized R1 release

Collaborative governance team for the authorized R1 release

Boundary: Organizational contribution does not transfer decision rights or create a capability parent.

Connected Service Promise I-01 · Initiative / option

Proposed bounded business change, not approved technology.

The case’s change boundary connects policy, confirmation, exception practice, adoption, and measurement.

Boundary: No recorded decision authorizes enterprise procurement or twelve-branch activation.

Promise adherence M-01 · Business measure

Cumulative latest-accepted-promise adherence;92%R1 gate versus95%strategic target. Original promise and restoration outcomes remain balancing measures.

Latest accepted promise adherence is only one lens on the customer’s experience.

Boundary: The 82% enterprise dashboard is not a comparable pilot baseline. The 92% R1 gate does not replace the 95% strategic target.

Part/skill confirmation M-04 · Business measure

Recorded part/skill confirmation;90%later-period gate; not identical to full policy compliance.

Recorded part/skill confirmation;90%later-period gate; not identical to full policy compliance.

Boundary: Different populations and promise versions cannot be compared as if they were interchangeable.

Policy adoption M-07 · Business measure

Complete workflow or valid approved exception;85%day30 and95%later-period gates. Not nested within M-04.

Complete workflow or valid approved exception;85%day30 and95%later-period gates. Not nested within M-04.

Boundary: Different populations and promise versions cannot be compared as if they were interchangeable.

Cost and capacity M-08 · Business measure

At most$300k fully loaded change cost and6peak temporary FTE; forecast excess requires prior scope/funding action; recurring burden separate.

At most$300k fully loaded change cost and6peak temporary FTE; forecast excess requires prior scope/funding action; recurring burden separate.

Boundary: Different populations and promise versions cannot be compared as if they were interchangeable.

Service Promise Policy POL-01 · Business policy

Approved R1 policy: confirmation or a complete approved exception; preserve original/revised promise lineage,communication and recovery.

Approved R1 policy: confirmation or a complete approved exception; preserve original/revised promise lineage,communication and recovery.

Boundary: Policy approval does not establish adoption or sufficient operating capacity.

Customer escalations M-05 · Business measure

Escalations attributable to a missed or changed promise per 100 eligible commitments.

Escalations attributable to a missed or changed promise per 100 eligible commitments.

Boundary: Different populations and promise versions cannot be compared as if they were interchangeable.

Three-branch feasibility release R1 · Release

Can the defined policy, information, exception, and operating practices work under three intentionally different conditions and produce decision-grade measures using existing systems?

A three-branch experiment using existing systems and controlled manual work. The v1.2 reference path releases $15k for diagnosis, up to $75k cumulatively for preparation, and at most $300k after a separate operating-entry decision.

Boundary: Operational feasibility at day 90 does not establish improved customer value or enterprise repeatability.

Enterprise enablement R3 · Release

What enterprise operating model and automation are justified by repeatable evidence?

Enterprise rollout and only the technology required for confirmed residual gaps

Boundary: Platform procurement requires its own business case and decision after repeatability evidence; R2 success does not automatically select a vendor.

Promise definition and policy CP-01 · Change package

One usable rule for creating, changing, cancelling, and recovering customer commitments

O-01/O-02/O-03, BO-02, Operations and Customer approval

Boundary: Original Decision 1 status: Proposed; not approved merely because R1 is funded. Later readiness and results require the evidence for those decisions.

Parts and skills confirmation CP-02 · Change package

Dispatcher can distinguish confirmed, provisional, and unavailable prerequisites

BO-05 owner/source decision; skill-data validation

Boundary: Original Decision 1 status: Proposed. Later readiness and results require the evidence for those decisions.

Scheduling and branch-exception practice CP-03 · Change package

Promise reflects geography and capacity while legitimate local discretion remains usable

POL-01, M-07, the one-shift exception criterion, and named escalation authority

Boundary: Original Decision 1 status: Proposed. Later readiness and results require the evidence for those decisions.

Targeted integration A4 · Initiative / option

A reservation/skill-status feed and dispatcher exception queue using existing systems.

A credible alternative or complement to the operating experiment. The planning range is $60–120k and one to two temporary FTE, conditional on usable source semantics.

Boundary: It cannot fix technician scarcity, travel, or disputed promise policy. No approval or benefit is implied.

Reconcile measures first A0 · Initiative / option

Clarify definitions and improve reporting without changing the promise practice.

$25–75k and 0.5–1 temporary FTE are planning ranges in E-007.

Boundary: It does not directly test or change operating practice.

Inventory reservation record SYS-RESERVATION · Enabling record / technology

The existing inventory record used as the provisional R1 reservation-status source.

E-008 accepts it for R1 only, with twice-daily reconciliation. This Atlas ID identifies an already documented record; no product or database design is invented.

Boundary: A named record does not establish an enterprise system of record.

Current service-promise record SYS-PROMISE · Enabling record / technology

The existing record accepted for R1 under versioning, original/revised linkage, and audit rules.

An Atlas identifier for the supporting record in E-008, not a new application.

Boundary: R1 acceptance does not select enterprise future-state technology.

Fund a bounded diagnostic DEC-001 · Governed decision

Only the first $15k is released initially within a conditional $150–300k A1/R1 envelope. Preparation and activation each require subsequent decisions.

Recorded fictional reference disposition. Conditions remain attached to the decision.

Boundary: A later result does not rewrite what was knowable at the original decision.

Defer platform procurement DEC-002 · Governed decision

Keep procurement deferred pending repeatability-quality evidence, residual-gap analysis, and a separate comparison and authorization.

Recorded fictional reference disposition. Conditions remain attached to the decision.

Boundary: A later result does not rewrite what was knowable at the original decision.

Begin R1 only when ready DEC-003 · Governed decision

Authorize a staggered start after remaining training and baseline reconciliation. Temporary source and backup-approver conditions expire at day 30 unless explicitly reviewed.

Recorded fictional reference disposition. Conditions remain attached to the decision.

Boundary: A later result does not rewrite what was knowable at the original decision.

Continue one remediation interval DEC-004 · Governed decision

Continue only to day 90 under the delegated margin exception. Narrow admissions, repair controls, review workload, and prohibit expansion.

Recorded fictional reference disposition. Conditions remain attached to the decision.

Boundary: A later result does not rewrite what was knowable at the original decision.

Investigate before expansion DEC-005 · Governed decision

Authorize R2 design/readiness investigation only. Require customer-value investigation; prohibit twelve-branch activation and retain procurement deferral.

Recorded fictional reference disposition. Conditions remain attached to the decision.

Boundary: A later result does not rewrite what was knowable at the original decision.

Sources, versions, and what this Atlas can establish

The current case is the learning edition (v1.2). The original workbook examples (v1.1) provide structural reference material and earlier illustrative assessments. They do not establish current performance. Guide to the materials.

Northstar is wholly fictional. “Established” means stated in the teaching case, not observed in a real enterprise. Existing hierarchy additions are authored modeling context. New impact paths are labeled as inferences or illustrative extensions. Archived capability ratings are judgments; they are not measured maturity, investment priorities, or probabilities of success.

The current learning evidence takes precedence for measurement periods and reference decisions. Capability boundaries and normalized names come from the corrected hierarchy. Detailed workbook accountability is retained where the compact SCALE workspace uses a regional coordination owner; the affected detail panels explain that discrepancy.