# Northstar Equipment Services: Connected Service Promise

**Version:** 1.0  
**Published:** 2026-08-19  
**Status:** Fictional teaching case  
**Primary user:** Business architect

## Purpose

This fictional case provides one institutionally realistic enterprise scenario for the Applied Business Architecture work-product collection. Every Phase 2 workbook reuses the same decision, strategy, stakeholders, value stream, capabilities, business objects, initiative, evidence, governance, and open questions. The intent is to show how business architecture work products connect rather than presenting nine isolated templates.

The case is entirely fictional. Names, figures, facts, and decisions do not describe a real employer, client, customer, or supplier.

## Enterprise context

Northstar Equipment Services is a fictional $780 million commercial-equipment maintenance and rental company operating 48 branches in twelve U.S. states. Its 3,200 employees serve construction, utilities, manufacturing, and municipal customers. Branches control daily service execution, while enterprise functions set commercial policy, financial controls, technology standards, and common operating measures.

Customers value rapid restoration of equipment availability, but Northstar's service promises have become unreliable. Branch personnel often commit dates before confirming technician skills, parts availability, or travel capacity. Regions use different terms for the same business objects and different definitions for promise adherence. A scheduling-software vendor has proposed an enterprise platform replacement, but executives do not yet know whether the central problem is technology, policy, capability, information, incentives, or some combination.

## Executive request and architecture decision

The original request is: **“Create a capability map for the Connected Service Promise transformation and validate the scheduling platform.”**

The business architect reframes it as this decision:

> Should Northstar fund a bounded three-branch pilot that establishes a common customer-promise policy, confirms parts and technician availability before commitment, and measures results using existing systems before authorizing an enterprise platform purchase?

The Investment Council owns the funding decision. The EVP of Service Operations sponsors the work. The business architect owns the architecture analysis and recommendation but does not approve the investment, select the vendor, or own operational performance.

## Strategic intent and measures

Northstar's 2027 service strategy contains two relevant objectives:

1. Improve service-promise reliability while preserving appropriate branch operating discretion.
2. Protect service margin while reducing avoidable customer disruption and repeat work.

The initial measures are:

| Measure | Current baseline | Target | Evidence status |
|---|---:|---:|---|
| Promise-date adherence | 82% | 95% | Directionally reliable; regional definitions differ |
| Avoidable repeat visits | 14% | 8% | Sample-based and disputed by two regions |
| Gross service margin | 31% | At least 31% | Governed financial measure |
| Commitments made with confirmed parts and skills | 38% | 90% in pilot | New measure; definition requires approval |

The pilot must not require replacement of the enterprise resource-planning system. A new scheduling platform remains an option only after the pilot tests policy, information, operating practice, and measurement assumptions.

## Stakeholders and decision rights

| Stakeholder | Interest or value | Relevant authority |
|---|---|---|
| Customer operations manager | Equipment restored when promised | Accepts, changes, or cancels the service commitment |
| Branch manager | Reliable service without unusable central rules | Owns branch adoption and local capacity choices |
| Dispatcher | Feasible promise and work sequence | Applies scheduling rules and raises exceptions |
| Field technician | Complete job with correct skills, parts, and information | Confirms execution facts and exception causes |
| EVP, Service Operations | Enterprise service performance | Sponsors the change and owns affected operating capabilities |
| Investment Council | Value, risk, and funding discipline | Approves, conditions, defers, or rejects investment |
| Chief Information Officer | Technology risk and standards | Approves technology standards; does not own service-policy outcomes |
| Business architect | Coherent architecture analysis | Frames, models, traces, challenges, and records; does not take the business decision |

## Value stream

The relevant value stream is **Restore Equipment Availability**. The primary stakeholder is the customer operations manager whose equipment is unavailable or at risk.

| Stage | Stakeholder state entering | Stakeholder state exiting | Illustrative exit criterion |
|---|---|---|---|
| Identify need | Equipment problem is emerging or known | Service need is accepted and classified | Service request has valid asset, urgency, and contact data |
| Define service promise | Need is accepted but timing is uncertain | Feasible service commitment is understood | Promise reflects policy, skills, parts, geography, and capacity |
| Prepare service | Commitment exists but work is not ready | Work is ready to execute | Work order, technician assignment, and part reservation are confirmed |
| Perform service | Work is ready | Equipment condition is restored or dispositioned | Work outcome and exceptions are recorded |
| Confirm outcome | Service occurred but value is unconfirmed | Customer accepts outcome and commitment is closed | Promise and work-order outcomes reconcile; follow-up is owned |

## Capabilities

| ID | Capability | Definition | Accountable owner |
|---|---|---|---|
| C-100 | Customer Need Management | Ability to identify, accept, classify, and maintain a customer service need | VP Customer Operations |
| C-110 | Service Promise Management | Ability to establish, communicate, monitor, change, and close a feasible customer commitment | EVP Service Operations |
| C-120 | Work Planning | Ability to translate an accepted service need into executable work | VP Field Service |
| C-130 | Resource Scheduling | Ability to match demand to qualified people, time, geography, and operating constraints | VP Field Service |
| C-140 | Parts Availability Management | Ability to determine, reserve, position, and release parts needed for service | VP Supply Operations |
| C-150 | Field Service Execution | Ability to perform, record, and disposition equipment service work | VP Field Service |
| C-160 | Service Outcome Management | Ability to confirm customer value, resolve exceptions, and close the service commitment | VP Customer Operations |
| C-170 | Service Performance Management | Ability to define, measure, explain, and govern service performance | EVP Service Operations |
| C-180 | Business Information Governance | Ability to define, own, quality-control, and change shared business information | Chief Data Officer |

## Business objects and lifecycles

| ID | Canonical business object | Common aliases | Relevant lifecycle |
|---|---|---|---|
| BO-01 | Service Request | ticket, service call, case | Draft → Accepted → Classified → Planned → Closed or Cancelled |
| BO-02 | Customer Promise | ETA, commit date, appointment | Draft → Validated → Committed → At Risk → Fulfilled, Broken, or Cancelled |
| BO-03 | Work Order | job, service order | Proposed → Released → Assigned → In Progress → Completed → Closed |
| BO-04 | Equipment Asset | unit, machine, serial | Registered → Active → Unavailable → Restored → Retired |
| BO-05 | Part Reservation | allocation, hold | Requested → Confirmed → Picked → Consumed, Released, or Expired |
| BO-06 | Technician Assignment | dispatch, route assignment | Proposed → Accepted → En Route → Arrived → Completed or Reassigned |

The architecture treats these as business concepts. It does not assume that a current application table, API payload, or local term is authoritative merely because it exists.

## Initiative and release choices

The proposed initiative is **I-01 Connected Service Promise**. Its current release options are:

| Release | Scope | Expected value or learning | Principal boundary |
|---|---|---|---|
| R1: Three-branch pilot | Common promise policy, part and skill confirmation, limited work types, exception log, governed measures, existing systems | Tests whether policy, information, and operating changes can raise adherence before platform purchase | No ERP replacement; manual exception management allowed |
| R2: Twelve-branch expansion | Refined rules, regional adoption pattern, controlled integrations, broader work types | Tests repeatability and operating-model fit | Requires R1 exit criteria and named information owners |
| R3: Enterprise enablement | Enterprise rollout and, if justified, platform procurement | Scales proven practice and automation | Requires a separate investment and architecture decision |

The recommended smallest useful release is R1. It is reversible, can produce measurable results within 90 days, and tests the highest-risk assumptions before a major technology commitment.

## Architecture-backed change packages

| ID | Change package | Outcome | Principal dependencies |
|---|---|---|---|
| CP-01 | Promise definition and policy | One usable rule for creating and changing customer commitments | Object definitions and operations approval |
| CP-02 | Parts availability signal | Dispatcher can distinguish confirmed from assumed part availability | Part Reservation ownership and source agreement |
| CP-03 | Scheduling rules | Promise reflects skills, geography, capacity, and approved exceptions | Policy and technician-skill data |
| CP-04 | Pilot enablement and adoption | Three branches can execute the new practice | CP-01, CP-02, and CP-03 |
| CP-05 | Measurement and scale decision | Investment Council can approve, change, stop, or scale using governed evidence | CP-04 and agreed measure definitions |

## Evidence and contested facts

| ID | Evidence | Current interpretation | Confidence |
|---|---|---|---|
| E-001 | Twelve-month service-performance report | Promise adherence is approximately 82% | High directionally; definition inconsistency limits comparison |
| E-002 | Regional repeat-visit sample | Avoidable repeat visits are approximately 14% | Medium; sampling and cause coding are disputed |
| E-003 | Five branch workshops | Promises often precede parts and skill confirmation | Medium-high; consistent observation but not a controlled measure |
| E-004 | Vendor discovery and demonstration | A platform can automate several desired controls | Medium for product capability; low for realized business value |
| E-005 | Finance margin report | Gross service margin is 31% | High |

Disagreement is not averaged away. The work products preserve the source, observation date, owner, confidence, and unresolved conflict so that governance can decide what is sufficient.

## Initial capability assessment

| Capability | Strategic importance (1–5) | Current performance (1–5) | Evidence strength | Interpretation |
|---|---:|---:|---:|---|
| Service Promise Management | 5 | 2 | 0.90 | Immediate priority |
| Parts Availability Management | 5 | 2 | 0.80 | Immediate priority; source ownership unresolved |
| Resource Scheduling | 4 | 3 | 0.75 | Targeted improvement |
| Field Service Execution | 5 | 4 | 0.85 | Sustain; do not over-scope pilot |
| Service Performance Management | 4 | 2 | 0.70 | Required for credible pilot decision |
| Business Information Governance | 4 | 2 | 0.65 | Foundation, bounded to pilot objects and measures |

## Decisions, conditions, and open items

The fictional architecture review records two initial decisions:

- **DEC-001:** Conditionally approve the R1 three-branch pilot, subject to approved promise and measure definitions, named object owners, and a 90-day scale-or-stop review.
- **DEC-002:** Defer enterprise scheduling-platform procurement until the pilot establishes whether the business change is repeatable and which automation gaps remain.

Open items include:

- approve one promise-adherence definition and owner;
- resolve the authoritative source for Part Reservation status;
- define the approved exception path when confirmed capacity is unavailable;
- verify that the three pilot branches represent distinct operating conditions;
- define stop conditions if margin, customer disruption, or adoption degrades.

## How to use the case

1. Read the case before opening a workbook.
2. Review the completed Northstar example tabs to see how the work product connects to the other artifacts.
3. Duplicate the blank template tabs for local use.
4. Replace fictional facts with sanitized, governed enterprise evidence.
5. Preserve unknowns, conflicts, and assumptions rather than making the workbook look complete.
6. Stop when the work product has improved the named decision; do not fill every reserved row.

## Boundaries

This case and its work products are educational practitioner aids. They do not replace executive accountability, organizational governance, authoritative enterprise models, formal investment approval, legal or regulatory review, project management, solution design, requirements management, data modeling, records-management controls, or the judgment needed to tailor business architecture to a real institution.

Related guidance: https://stephenklahr.com/cookbook/