# Northstar: the whole value stream and its stages

Fictional teaching model. This explanation makes the existing case structure explicit; it does not change episode evidence, decisions, or achieved results.

## Begin with the whole stream

- **Value stream:** VS-01 Restore Equipment Availability

- **Triggering stakeholder:** ORG-01 Customer operations manager

- **Triggering need:** Equipment is unavailable or at risk, prompting the customer operations manager to request service.

- **Value proposition:** Usable equipment availability restored for the customer operations manager and confirmed against the agreed service commitment.

The stakeholder triggers the stream to obtain that proposition. The stream contains value stream stages. Each stage delivers value items that accrue toward the whole proposition. Capabilities enable the stages; participating stakeholders contribute to or receive value within them.

## Decompose the stream into stages

| Stage | Value item |
|---|---|
| ST-01 Identify need | An accepted, actionable need |
| ST-02 Define service promise | A credible commitment accepted by the customer |
| ST-03 Prepare service | Service ready to execute |
| ST-04 Perform service | Restored equipment condition, or explicit evidence that further recovery is required |
| ST-05 Confirm outcome | Confirmed restored availability on success; a documented outstanding obligation or unfulfilled termination otherwise |

## How value accumulates

An accepted need, a credible commitment, prepared service, and the equipment result contribute to restored availability. Customer confirmation establishes receipt of the agreed value. These contributions combine to fulfill the proposition; accumulation is not an arithmetic sum, a count of completed tasks, or proof that a project delivered benefits.

The stages show a typical progression. Entry and exit criteria govern navigation, including returning to earlier stages. Evidence that further recovery is needed preserves an outstanding obligation. If restoration cannot be achieved, record termination without fulfillment and the remaining obligations. Neither disposition should be counted as the fulfilled value proposition.

## Inspect each stage

### ST-01 Identify need

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

- **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

- **Enabling capabilities:** C-100 Service Request Qualification (primary); C-170 Performance Measure Management (supporting); C-180 Information Definition Governance (supporting)

### ST-02 Define service promise

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

- **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

- **Enabling capabilities:** C-100 Service Request Qualification (supporting); C-110 Customer Promise Management (primary); C-120 Work Order Planning (supporting); C-130 Human Resource Scheduling (supporting); C-140 Part Availability Management (supporting); C-170 Performance Measure Management (supporting); C-180 Information Definition Governance (supporting)

### ST-03 Prepare service

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

- **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

- **Enabling capabilities:** C-110 Customer Promise Management (supporting); C-120 Work Order Planning (primary); C-130 Human Resource Scheduling (primary); C-140 Part Availability Management (primary); C-150 Work Order Execution (supporting); C-170 Performance Measure Management (supporting); C-180 Information Definition Governance (supporting)

### ST-04 Perform service

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

- **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

- **Enabling capabilities:** C-120 Work Order Planning (supporting); C-130 Human Resource Scheduling (supporting); C-140 Part Availability Management (supporting); C-150 Work Order Execution (primary); C-160 Service Request Resolution (supporting); C-170 Performance Measure Management (supporting); C-180 Information Definition Governance (supporting)

### ST-05 Confirm outcome

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

- **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

- **Enabling capabilities:** C-110 Customer Promise Management (supporting); C-150 Work Order Execution (supporting); C-160 Service Request Resolution (primary); C-170 Performance Measure Management (supporting); C-180 Information Definition Governance (supporting)

## Use the blank workbook

The Stage Cards worksheet begins with the whole stream: Value stream, Primary stakeholder, Triggering need, Value proposition, and End outcome. Use Primary stakeholder to identify the triggering stakeholder. Below that header, record each stage’s definition, participating stakeholders, value items, and criteria. Check how the items collectively fulfill the proposition before completing the capability cross-map.

The five stages here belong to this Northstar example. They are not a required stage count or a task-level procedure.

## Sources and modeling status

The stream, stakeholder, stage definitions, and value-item wording come from the historical Northstar structural case and stage workbook. VP-01 and VI-01 through VI-05 are Atlas modeling identifiers for that existing content. The explicit trigger relationship is an authored interpretation of the case’s stakeholder and entry criteria. Partial stakeholder mappings retain generic participants in the stage text rather than inventing new role identities.

- [Northstar structural case, Value stream section](https://stephenklahr.com/downloads/northstar-equipment-services-case-v1.1.md)

- [Historical stage-card source workbook](https://stephenklahr.com/downloads/value-stream-capability-cross-map-v1.1.xlsx)

- [Current blank workbook](https://stephenklahr.com/downloads/value-stream-capability-cross-map-template.xlsx)

- [Business Architecture Guild, Metamodel Guide v3.0, section 5.1](https://cdn.ymaws.com/www.businessarchitectureguild.org/resource/resmgr/whitepapers/business_architecture_metamo.pdf)

- [Explore the value stream in the Atlas](https://stephenklahr.com/cookbook/northstar/atlas/?view=value)
