Your automation programme, from first idea to measured saving.
Automation programmes lose the thread between the workshop and the running system. The Portal carries the programme through all four phases of the 3Di+ method: potentials are found and valued, each one is worked out until it can be built, it becomes a running automation, and what it actually saved is measured and fed back as the next potential. Every phase leaves its record in the platform instead of in somebody’s spreadsheet.
Available today alongside Agent ManagerThe problem it removes
Four phases, four different places to keep them.
The potential was found in a workshop in March. The design lives in a document somebody mailed. The automation is running, and nobody can say what it actually saved. Each phase hands over to the next as an attachment, so when somebody finally asks for a view of the whole programme, it has to be rebuilt from memory.
You automate what is expensive, not what is loud
Potentials are captured with what they cost today and what removing them is worth, in one register rather than one list per department. The sequence follows the numbers instead of whoever asked most recently.
A design that can be built without another meeting
Each potential is worked through until there are no open questions left: what happens, in what order, with which data, and who is accountable for it. Effort and benefit are assessed side by side, so the go-ahead is a decision rather than a preference.
The running automation still knows why it exists
When a design goes live, the link back to the potential that justified it stays intact. Two years later, the automation nobody remembers commissioning can still be traced to the case that paid for it.
What it saved, not what it promised
The platform measures the automation against the benefit that was claimed for it, and watches its own runs for the ones that quietly stop behaving. A programme is judged on results that were measured, not on a business case written before it existed.
Everything in one record, not one mailbox
Notes, documents, assessments and decisions sit against the potential and the automation they belong to, versioned and searchable. The programme can be read end to end by somebody who was not in the room.
One login, one directory, two languages
The Portal and Agent Manager share a sign-in and a user directory, so joiners and leavers are handled once. The whole surface is available in German and English.
The four phases
Discover, Design, Develop, Improve. All four in one place.
This is the 3Di+ method we run engagements with, made into a system rather than a slide. If you want the method itself rather than the product, read how 3Di+ works.
Discover
Potentials captured and valued
Every candidate for automation is recorded with what it costs the business today and what removing it is worth. The register is shared, so two departments proposing the same thing find each other rather than funding it twice.
- One register, not one list per department
- Cost today and value of removing it, on every entry
- Ranked by what it is worth, not by who asked
Design
Worked out until it can be built
The potential is developed until nothing is left open: the steps, the data, the exceptions, the person accountable. Effort and benefit are assessed together, so what gets built next is an argued choice.
- Open questions closed before anything is built
- Effort assessed against benefit
- The agreed design kept as a record, not an attachment
Develop
It becomes a running automation
The design goes live on the platform with its own schedule, its own access boundary and its own run record, and the Portal keeps the thread back to the potential it came from.
- Live with a schedule and an owner
- Its own access boundary from day one
- Traceable back to the case that justified it
Improve
Measured, watched, and fed back
What the automation actually saves is measured against what was claimed, and the platform watches its own runs for the ones that start failing quietly. What is learned returns to Discover as the next potential.
- Actual saving measured, not assumed
- The platform watches its own runs
- New potential flows back into Discover
How much the automation decides
Three levels of autonomy, and you choose per case.
Not every job should be handed to an agent, and the ones that should are not all the same. Each automation sits at one of three levels, chosen deliberately and recorded with the design.
Fixed rules
The automation follows rules you have written down. The same input produces the same result every time, and it can be checked by reading it. Most of a programme belongs here, and so does most of the saving.
The agent proposes, a person approves
The agent does the preparation and puts a recommendation in front of somebody, who accepts it or overrules it. The judgement stays with a person while the two hours of gathering and comparing stop being their job.
The agent decides inside guardrails
Where the boundaries can be stated clearly, the agent acts on its own within them. Anything that falls outside those limits still comes to a person, and every decision it made is in the run record.
What the Portal keeps
The programme, written down as it happens.
Register
Potentials with their numbers attached
One entry per candidate: what it is, what it costs today, what it is worth, where it stands and who owns it.
Assessment
Effort and benefit side by side
The two figures that decide sequence, recorded on the potential rather than argued from memory in the next steering meeting.
Documents
Filed against the work, not in a folder habit
Notes, evaluations and delivery documents attached to the potential or the automation they describe, versioned so the current one is obvious.
Decisions
What was agreed, and when it changed
The agreed scope is an object in the system. A change is a concrete difference against the last agreed version, visible to both sides.
People
Access handled once
Add somebody once and they have what their role implies in the Portal and in Agent Manager. Remove them once and it is gone from both.
Languages
German and English throughout
The whole surface, including the documents area and the administration screens, not a translated menu bar over an English product.
How it runs
It installs alongside Agent Manager, in your own data centre, on the cluster you already operate, or hosted by us, and signs people in through the identity provider they already use. Documents are held in your own storage, so your retention rules apply to them exactly as they apply to everything else.
Works with the rest of the range
The Portal and Agent Manager are two views of one programme: the case and the agreement on one side, the running automations and their results on the other, with one sign-in and one set of rights across both.
How to start
Start at Discover, with a room and half a day.
The first phase needs your people and their real work, not a system integration. We run the discovery session, the potentials land in the register with numbers on them, and you decide from there what is worth designing.