Field Service Management › Service Dispatch Management
Service Dispatch Management
BC-1050.20
Level 2
Manufacturing & Industrial
2 providers
2 API surfaces
Technician scheduling, routing, dispatch.
Service Dispatch Management (BC-1050.20) is a level-2 business capability under Field Service Management in the Manufacturing & Industrial model. The catalog holds 2 API surface(s) from 2 provider(s) that can perform some part of it. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.
Where this capability definition comes from.
This capability is part of a published business-architecture model that API Evangelist
did not author. It is redistributed here under
CC-BY-4.0.
Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented.
Source repository · NOTICE and third-party framework attributions
Sub-capabilities
Technician Scheduling BC-1050.20.10
Scheduling of technicians by skill and availability.
no catalog coverage
Route Optimisation BC-1050.20.20
Optimisation of routes and travel for service visits.
no catalog coverage
Dispatch Execution BC-1050.20.30
Real-time dispatch and reassignment of service jobs.
no catalog coverage
Providers that reach this capability
Ordered by rating band. Reach means a provider publishes an API surface that can perform
some part of this capability — it is not a claim that any particular
organisation has deployed it.
Emerging
2
Early or largely undocumented
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature.
This page shows
which providers and tags reach Service Dispatch Management. The underlying
tag → capability edges — each with the quoted fragment of the provider's own
OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate
it passed — are available through the API, along with company-level capability maps.
Only edges at confidence ≥ 0.7 with evidence found verbatim in
the source contract are published at all.
See plans →
·
How the edges are graded →