Turn your SLAs and contracts into rules your operation runs on
The service levels you are held to sit in contracts that operations teams rarely have time to read. Certin puts those obligations into the rules that decide which deviations become exceptions, and how serious each one is.
How does Certin turn contracts into operating rules?
Certin turns the obligations in customer SLAs and contracts into rules the operation runs on. The operator uploads a contract, Certin extracts the obligations it is held to, and the team sets the thresholds, tolerances, benchmarks and severities that decide when a deviation becomes an exception.
What belongs in a logistics SLA rule?
A rule tells the operation when a deviation matters. Each rule in Certin is built from the following parts.
| Part of the rule | What it sets |
|---|---|
| Measure | What is watched, such as arrival at a delivery point or a scan at a milestone |
| Threshold | The point at which a deviation counts, such as the end of a delivery window |
| Tolerance | How much deviation is accepted before it becomes an exception |
| Benchmark | The level of service you aim for, which can be stricter than the contract |
| Severity | How serious the exception is, which sets its priority |
Illustrative example: a retail customer requires delivery to its stores between 06:00 and 08:00. The rule watches arrival at each store, sets the threshold at 08:00 with a tolerance of 15 minutes, and gives any risk to the window high severity.
How does Certin read customer contracts?
- Your team uploads the SLA or customer contract.
- Certin extracts the obligations it holds you to, such as delivery windows, service level targets, reporting duties and penalty terms.
- Your team reviews the extracted obligations and confirms them.
- Thresholds, tolerances and severities are set against each confirmed obligation.
- From then on, every exception on that customer's flows is weighed against those obligations.
Who sets the thresholds?
Your team does. Certin extracts what the contract says; your operations team decides how much deviation the operation can absorb and how serious each kind of breach is. Thresholds can be changed at any time as contracts, lanes and partners change.
Why do rules matter?
Without rules, every late scan looks the same, and teams either chase everything or learn to ignore alerts. Rules separate the deviation the operation absorbs from the one that puts a contract at risk, so the team's attention goes to what costs money.
Frequently asked questions
Can each customer have its own rules?
Yes. Each contract you upload carries its own obligations, and thresholds and severities can be set for each one.
What happens when a contract changes?
Your team uploads the new version and reviews the obligations Certin extracts from it, and the thresholds are updated to match.
Do rules trigger actions automatically?
Not today. A rule decides when a deviation becomes an exception and how serious it is. Certin then routes and coordinates the exception, and a person on your team decides and acts. Automatic execution is on the roadmap.
Run your operation against what you promised your customers.