S2C 505 ยท FROM DISCOVERY TO STABILIZATION
How does an S2C implementation unfold?
Join a fictional industrial-service company as it implements one shared service spine for customer-site field work and in-house repair. The project keeps entitlement, technical history, execution evidence, billing, and service economics connected.
PROJECT PHASE
Discover
Define the service promise and operating reality
What the team does
Meet Customer Service, workshop, field operations, planning, inventory, Sales, Finance, Quality, IT, and mobile users. Capture products, installed base, channels, SLAs, warranties, contracts, charging models, locations, volumes, exceptions, and measures.
S2C project moment
Apex Industrial Services repairs major motor failures at its depot while technicians resolve smaller faults at customer sites.
Evidence to leave behind
Approved scope, stakeholder map, service catalog, volumes, pain points, assumptions, measures, and open questions.
PROJECT PHASE
Fit to standard
Classify service cases before designing documents
What the team does
Demonstrate the common request-to-cash spine, then classify real cases into remote support, field visit, or depot repair. Preserve only differences required by value, risk, regulation, or customer promise.
S2C project moment
The first release includes field and depot work; remote diagnostics is captured as a request activity, while subcontracted repair remains later scope.
Evidence to leave behind
Fit decisions, execution-model rules, gaps, owners, acceptance criteria, and decision log.
PROJECT PHASE
Design
Connect common controls to branch-specific evidence
What the team does
Define service organization, customer and technical-object identity, entitlement, dates, statuses, parts, custody, scheduling, mobile evidence, acceptance, billing, accounting, migration, roles, and reporting.
S2C project moment
Both paths share warranty and contract determination; depot design adds customer-equipment custody, while field design adds dispatch and technician stock.
Evidence to leave behind
Signed process design, data model, status model, interface contracts, role concept, billing rules, and end-to-end test conditions.
PROJECT PHASE
Configure
Build the shared spine before the branches
What the team does
Configure the minimum common scenario first, then depot and field dependencies in controlled order. Record decisions beside settings and prepare realistic customers, equipment, contracts, resources, and stock.
S2C project moment
One serial-numbered motor can create either a depot repair order or a field visit while retaining the same customer, equipment, entitlement, cost, and service history.
Evidence to leave behind
Configuration workbook, dependency and transport sequence, master-data readiness, unit evidence, and unresolved defects.
PROJECT PHASE
Test
Prove both golden paths and their exceptions
What the team does
Run unit, string, integration, mobile/offline, authorization, regression, and user-acceptance tests. Reconcile custody or dispatch, parts, confirmations, acceptance, billing, cost, revenue, receivable, and cash.
S2C project moment
Depot testing includes estimate reapproval and a manufactured component. Field testing includes missing technician stock, a follow-up visit, offline confirmation, and customer signature.
Evidence to leave behind
Passed evidence, reconciliations, defect decisions, retest results, business acceptance, and residual risk.
PROJECT PHASE
Cut over
Make workshop and field operations production-ready
What the team does
Sequence transports, roles, customers, sites, equipment, installed base, warranties, contracts, prices, open service cases, workshop custody, technician stock, mobile devices, forms, interfaces, jobs, and reconciliation checkpoints.
S2C project moment
The team validates open depot equipment by serial number, counts technician stock, synchronizes mobile devices, and executes one controlled request-to-confirmation smoke test per branch.
Evidence to leave behind
Approved cutover plan, owners, timings, migrated totals, custody and stock reconciliation, contingency triggers, and go/no-go decision.
PROJECT PHASE
Go live & stabilize
Operate queues, resolve causes, and transfer ownership
What the team does
Monitor request intake, entitlement failures, SLA queues, workshop backlog, dispatch, mobile synchronization, parts differences, confirmations, billing blocks, accounting, and support demand. Preserve evidence before changing configuration.
S2C project moment
Billing blocks rise because field technicians omit acceptance on offline visits; the team corrects the form and operating procedure, retests synchronization, and clears affected orders with retained evidence.
Evidence to leave behind
Daily controls, service KPIs, resolved root causes, accepted backlog, support knowledge, ownership transfer, and stabilization exit.
THE CONNECTING CONTROL
Do not bill what entitlement and delivered-service evidence cannot explain
The rule must survive workshops, branch design, configuration, negative testing, migration, mobile operation, cutover, and production monitoring.
Use S2C 101 for process language, 202 for service capabilities, 303 for the two execution models, and 404 for configuration dependencies and proof.