Operate & Automate
Operate & Automate is stage three: after the build, we run, monitor and support the software and the agents for a monthly fee, and move each workflow up the autonomy ladder as it earns it. This page covers what we run, how support works, when promotion reviews happen, the quarterly on-site week and how new workflows are added.
What we run and monitor
Section titled “What we run and monitor”| What | What we watch |
|---|---|
| The operations layer: the screens, queues and rules your people work in | That it is up and that work is moving. Nothing should sit in a queue longer than its workflow owner allows. |
| The connections to your ERP | That every read and every write-back succeeded, that each scheduled file or EDI exchange arrived, and that what was written matches what the ERP now holds. |
| The agents | What each one did, how often people correct or reject what it prepared, how many exceptions it sends to people and whether it is running into its limits. |
Audit trail and monitoring describes the alerts and the sampling behind this.
Your ERP, your network and your devices stay with your IT team and your ERP partner. We ask for one thing: tell us before an ERP upgrade, or before anyone changes a field, a price list structure or an EDI map that a workflow reads. We test the connection against the change before it reaches production.
How support works
Section titled “How support works”- Someone reports a problem. Anyone who uses the software can report it, directly or through the workflow owner, to the forward-deployed engineers on your engagement. They stay on call.
- If an agent is doing something wrong, stop it first. The stop switch halts the agent at once. If the agent should keep working with less autonomy, the workflow owner moves the workflow down a level, for example back to a person approving every transaction. The work goes back to people while we look. Nobody has to wait for us to do either.
- Your engineers find the cause and fix it. A fix is released the same way as any other change: tested, then signed off by the workflow owner.
- The problem and the fix are written down. If an agent was involved, the record points to the entries in its audit trail.
Response times are agreed in your contract, so this page states none. Stages and terms lists what your contract records.
Support covers what is already in use: faults, and the adjustments that keep a workflow working when the documents around it change, such as a customer’s new purchase order layout or a supplier’s new invoice format. A new workflow is not support. The last section covers how one is added.
When promotion reviews happen
Section titled “When promotion reviews happen”A promotion review is held as soon as a workflow is ready, remotely if need be. It does not wait for a calendar date, and a ready workflow does not wait for the quarterly on-site week. Ready means two things. The workflow has done enough real work at its current level to be measured against the threshold that was written down before that level started. And its workflow owner wants to take the next step. Sales order entry builds that record quickly, because orders arrive all day. Returns take longer.
The review checks four things: measured accuracy on real work against the threshold set in advance, the cost of a wrong action, that every action is logged and reversible, and sign-off by the workflow owner. Promotion reviews covers who attends and what is recorded.
Three rules hold throughout:
- A workflow moves up one level at a time.
- Moving a workflow down needs no review. The workflow owner decides, without waiting for us.
- Not every workflow should reach Level 4 (Autonomous). Some stay at Level 2 (Prepared) or Level 3 (Supervised) for good, and that is a fine result.
The quarterly on-site week
Section titled “The quarterly on-site week”Our engineers come back on site for one week each quarter. The dates are set in advance with the sponsor. The week is used to:
- Sit with the people who use the software and see how the work has changed since the last visit.
- Go through recent exceptions with each workflow owner and pick out the ones that keep repeating.
- Hold in person the promotion reviews that fall near the week. A workflow that is ready at another time is reviewed then, remotely if need be.
- Review the Automation Backlog with the sponsor.
Travel for the week is billed at cost. Stages and terms lists the terms.
How new workflows are added
Section titled “How new workflows are added”New workflows come from the Automation Backlog and are added by scheduling more Embedded Build time.
- The sponsor picks the next workflow from the backlog. Anything new that was found on site is ranked into the backlog first.
- A workflow owner is named.
- Build time is scheduled. It runs to the same weekly rhythm as the Embedded Build.
- Once the workflow is in daily use, it joins what we run and monitor.
The monthly fee for Operate & Automate is on the pricing page. If you end the stage, we hand over as described in Handover and exit.