Service Contract and SLA Management

Overview#

The Service Contract and SLA Management capability turns the commitments written into a vendor or customer contract into enforceable, automatically monitored targets that the platform measures against real field work. It manages the full lifecycle of field service contracts, from draft through approval, activation, suspension, renewal, and termination, so that operations teams stop reconciling obligations in spreadsheets and instead work from one authoritative record.

Service and maintenance organisations such as police fleet maintenance units, fire equipment servicing teams, utility field crews, and emergency management contractors can define the exact response, resolution, and on-site targets they owe, then let the platform watch open jobs against those targets in real time. When a job misses a target, the breach is recorded with the overage in minutes and any agreed penalty amount, removing the disputes that come from manual calculation. Operations managers also gain a live burn-rate view of hours consumed against a contract budget and early warning when a contract is approaching its expiry date.

Key Features#

• Full Contract Lifecycle: Move every agreement through draft, pending approval, active, suspended, expired, terminated, and renewed states, with dual approval, effective and expiry dates, notice periods, and optional auto-renewal.

• Seven Contract Types: Model service contracts, maintenance agreements, parts supply, mutual aid, managed service engagements, projects, and warranties under one consistent structure.

• Configurable SLA Rules: Attach response-time, resolution-time, and on-site-time targets to each contract, with priority bands, business-hours awareness, escalation configuration, and per-breach and monthly penalty caps.

• Automatic Breach Detection: Scan open work orders against every applicable SLA rule, record new breaches with target, actual, and overage minutes, and skip jobs already accounted for so nothing is double-counted.

• Breach Acknowledgement and Waivers: Let operators acknowledge a recorded breach or waive it with a reason and an audit of who waived it, keeping penalty reporting honest.

• Hour and Balance Ledger: Track every hour against a contract through a transaction ledger covering work, adjustments, credits, initial allocation, renewal, and penalty entries, each tied back to the originating job.

• Live Burn-Rate Visibility: Show total, consumed, and remaining hours in real time so managers see how much of a contract budget is left before it runs out.

• Geographic and Operational Scoping: Define coverage areas as geographic shapes, link a service territory, and bind a dispatch agreement so the contract aligns with where and how work is delivered.

Use Cases#

Police and Public Fleet Maintenance#

A fleet maintenance unit holds a maintenance agreement with a workshop vendor that promises a four-hour response on critical vehicle faults. The platform watches every open repair job, flags the ones that pass the four-hour mark, and attaches the contractually agreed penalty so the unit can recover it without arguing over timings.

Fire and Safety Equipment Servicing#

A servicing contractor manages warranty and maintenance agreements across breathing apparatus, pumps, and detection equipment. Line items capture the covered services and parts, while the hour ledger shows how much of the annual service allocation each station has consumed.

Utility Field Crews#

A utility runs managed-service and mutual-aid contracts with neighbouring operators. Coverage areas and service territory links keep each contract scoped to the right geography, and the expiry look-ahead surfaces agreements that need renewing before a storm season starts.

Emergency Management Contractors#

A contractor delivering project-based and parts-supply work to an emergency management agency needs a defensible record of consumed hours and any missed targets. The balance ledger and breach history give both sides a shared, auditable account.

Audiences#

• Operations and dispatch managers monitoring contract burn rate and exposure.
• Contract and procurement teams enforcing SLA commitments and penalties.
• Field service supervisors reconciling logged hours against an allocation.
• Finance teams reconciling penalties and overage charges.

Integration#

The capability is exposed as a structured data service over HTTP, so external systems read and write contracts, SLA rules, line items, ledger entries, and breaches through a single typed interface secured by OAuth2 bearer tokens carrying signed JWT claims. Requests are authenticated and scoped to the calling organisation automatically, so a customer integration only ever sees its own records.

• Typed Data Service: A strongly typed schema lets partner systems create contracts, attach SLA rules, record ledger transactions, and list breaches with predictable inputs and outputs.

• Real-Time Event Stream: Contract and breach events are pushed to subscribers over WebSocket, so dashboards and downstream systems react the moment a breach is detected or a contract changes state, rather than polling.

• Work Order Linkage: Each ledger entry and each breach references the originating job, giving customers an exact line of evidence from a charged hour back to the work that consumed it.

• Dispatch and Territory Connectors: A contract can bind to a dispatch agreement and a service territory, so the same record that defines the commitment also defines where and how the work is dispatched.

• Geographic Coverage Payloads: Coverage areas are exchanged as standard geographic feature objects, which any compliant mapping or geospatial system can render and validate without custom parsing.

The benefit for a customer plugging in is that contractual commitments, the work that fulfils them, and the financial consequences of missing them all live in one connected model, reachable from existing dispatch, mapping, finance, and reporting tools.

Open Standards#

• GraphQL: the capability is published through a GraphQL gateway, giving consumers a typed, self-describing interface with predictable reads and writes over standard HTTP.

• GeoJSON (RFC 7946): contract coverage areas are stored and exchanged as GeoJSON geometry, so any compliant geospatial tool can render and validate a coverage boundary directly.

• WGS 84 / EPSG:4326: coverage geometry uses the common latitude and longitude reference model expected by modern mapping systems.

• OAuth2 with JWT (RFC 7519): every operation is authorised with an OAuth2 bearer token carrying signed JSON Web Token claims, the standard pattern for delegated, organisation-scoped access.

• ISO 8601: effective dates, expiry dates, breach detection timestamps, and ledger entry times all use the ISO 8601 date and time representation for unambiguous, timezone-aware records.

• ISO 4217: monetary values on contracts and balances carry an ISO 4217 currency code, so financial figures are exchanged without ambiguity across borders.

• WebSocket (RFC 6455): contract and breach events are broadcast over the RFC 6455 WebSocket protocol for low-latency, push-based delivery to dashboards and subscribers.

• JSON Schema: structured configuration such as escalation rules, penalty clauses, and coverage scope is exchanged as JSON objects validated against well-defined shapes.

Security & Compliance#

• Organisation Isolation: Every contract, SLA rule, line item, ledger entry, and breach is bound to an organisation identifier, and all reads and writes are filtered to the caller's organisation so tenants never see one another's data.

• Authenticated Operations: All operations require an authenticated, authorised caller, with access carried by signed tokens rather than shared secrets.

• Auditable Breach Handling: Breaches record when they were detected, who acknowledged them, and who waived them along with the stated reason, producing a defensible trail for penalty disputes and compliance review.

• Authoritative Record of Truth: A relational database holds the source of truth for all contract data, giving a consistent, transactional record suitable for financial reconciliation and audit.

• Traceable Financials: Each charged hour and each penalty links back to a specific work order, supporting transparent billing and dispute resolution.

Last Reviewed: 2026-05-26 / Last Updated: 2026-05-26