50 harness editors at HQ. 50,000 workshop technicians in the global service network. One pipeline between them. Every edit at the editor end propagates VIN-specific to every dealership diagnosing an electrical fault, a roughly 1,000× leverage ratio between authoring and consumption. The deployment has held at both ends across every procurement-review checkpoint since 2020.
SPREAD touches both ends of that pipeline: a harness-editor platform at HQ where the 50 editors author the wiring data, and a workshop wiring application at the dealership where the 50,000 technicians query it. Same data, two surfaces.
Why the editor layer matters
At a 1,000× leverage ratio, every blocking second at the editor's keyboard compounds against the downstream service network. A productivity quibble at HQ is a structural drag at the dealership.
The editor's bottleneck
A typical editor session involves table-based filter operations across thousands of harness signals, diagram redraws when a new variant is opened, and field-by-field edits on individual components. Two integration surfaces matter: the editor platform at HQ that authors the wiring data, and the workshop wiring application that delivers it VIN-specific into the dealership diagnostic system. Same data, two surfaces, one pipeline. The customer-side ask, in the editor's own words: "save seconds and clicks ... we want the table and filters to work like Excel."
The arithmetic at the leverage point
Illustrative: 5 seconds saved per edit × 30 edits per editor per shift × 50 editors × 220 shifts/year ≈ 1,650,000 editor-seconds saved annually, propagating to ~1.65 billion workshop-second equivalents downstream. The arithmetic is the structural reason a multi-year framework agreement is the contracting shape that fits this engagement at the editor end.
The other end of the pipeline
At the workshop end, the workshop wiring application (wiring schematics) delivers what the editor platform authors. For the workshop technician diagnosing an E/E (electrical/electronic) fault, the platform delivers:
- VIN-specific wiring schematics queryable directly within the dealership diagnostic system at the point of E/E fault diagnosis (configuration filtering happens upstream, before the technician sees the schematic)
- Cross-component dependencies surfaced in context, not via separate document lookup
- Only the components actually installed on this vehicle, only the wiring topology this configuration produces
The structural shift is one that recurs across the SPREAD aftersales portfolio: documentation moves from configuration-agnostic (technician filters mentally) to VIN-specific (configuration filtering happens before the technician sees it). The workshop wiring application is the infrastructure layer of that shift, the platform that makes VIN-specific wiring delivery possible at the global service-network scale the customer operates at.
Every procurement checkpoint cleared since 2020
The workshop-wiring deployment renews on a recurring procurement cycle, with an annual platform-tier renewal layered in. Since 2020, the customer's procurement organization has cleared every checkpoint without a non-renewal.
The cadence is what makes this durability legible. Most B2B platform engagements churn at 5–15% net annually depending on category. A recurring procurement structure converts each cycle into a checkpoint where the customer can walk away. Every time, across both contracting structures (multi-year framework at the editor end, recurring + annual at the workshop end), they have chosen not to.
Where the workshop surface extends next
Under active scoping with the customer: extending the workshop-wiring surface from 2D schematic delivery to 3D harness visualisation. For a workshop technician, this pairs the wiring diagram and the 3D twin in a single VIN-scoped view, restricted to the vehicle's actual configuration.
If that extension lands, the workshop end's contracting structure moves from recurring renewals toward a multi-year framework like the editor side's, turning a recurring procurement checkpoint into one structural commitment.
What the two ends tell you together
The editor end and the workshop end share one pipeline and one leverage ratio. The editor end shows what 1,000× looks like as a productivity multiplier; the workshop end shows what it looks like as procurement durability, every checkpoint since 2020 where the customer could have walked and chose not to.
Same data, two surfaces, one structural fact: the pipeline has held at both ends.
Program shape
| Pipeline | Aftersales wiring data, HQ editor end → global service-network workshop end |
|---|---|
| Harness editors at HQ | ~50 |
| Workshop technicians downstream | ~50,000 |
| Leverage at editor layer | ~1,000× (50 editors → 50,000 technicians) |
| Procurement durability | Every procurement-review checkpoint cleared since 2020 |
| Contracting structure | Multi-year framework (editor end); quarterly + annual (workshop end) |
| Workflow shift at workshop | Configuration-agnostic documentation → VIN-specific delivery |
| Active extension | 2D schematic → 3D harness visualisation, VIN-scoped |
| Customer-side roles | HQ GM (commercial); ~50 harness editors (workflow); ~50,000 workshop technicians (consumption) |