SLAIn production
Deadlines and SLAs
A deadline that knows nobody works on Sunday.
Promising "three days" without discounting weekends and holidays turns the metric into an argument. Here the clock runs on the company calendar and stops outside working hours.
What it includes
Configured on the diagram, measured on the dashboard.
The SLA is a property of the process element: defined where it is designed, measured where it is operated.
Configuration
- Projected duration in minutes per process element
- Business calendar with a schedule per weekday
- Holiday lists reusable across processes
- Several alerts per task, each with its own trigger point
Alerts
- Notify or reassign when the deadline is reached
- Target: the assignee or their direct manager
- A message template per alert
- Email in the recipient’s language
SLA dashboard
- Active, on-time, at-risk and overdue tasks
- Computed due date for each task
- Available to administrators and managers
- Refreshed against the engine’s live data
Measurement
- Total instance duration
- Operating time spent on the forms
- Workload per user
- Bottlenecks visible per task
Works with
It doesn’t work alone.
These other parts of the product are what make this one work end to end.
Standards and limits
What you can count on.
Maintenance plan recurrence is expressed in UTC when a cron expression is used; every other deadline uses the company calendar.
- Calendar per company
- Each company defines its schedule and holidays; the same process measures differently in each one.
- Continuous checking
- A background service evaluates deadlines, one pass per company.
Let’s measure one of your processes against your real calendar.
We’ll show you one of your own processes modeled and running, with your forms and your deadlines.