A BPM suite bought a decade ago still runs the processes it was bought for, with its own data store, its own forms and a per-user licence.
| Element | What it holds |
|---|---|
| Process models | BPMN or proprietary drawings |
| Forms | the task screens |
| Business rules | decision tables |
| The suite's database | case data copied from the ERP |
| Integrations | adapters to the ERP and the mail system |
| Reports and dashboards | cycle time, work in progress |
| In legacy bpm and workflow suites | In SmartApps |
|---|---|
| A lane | A lane |
| A user task with a form | A box with a screen |
| A gateway | A decision node with an expression |
| A decision table | Criteria in the expression editor, or a global variable table |
| Case data in the suite's store | Data handlers on the systems of record, read in place |
| An ERP adapter | The platform connector, with write-back through the released interface |
| A cycle-time dashboard | The board and the measures of each app |
Lanes, tasks and gateways carry over one to one; the store and the price are what change.
An industrial company ran 31 processes on a BPM suite whose renewal doubled the price. The inventory mapped them to 19 app types; 9 were already in the catalogue. The engineering change process, the largest, was rebuilt in eight days with its 6 lanes and 14 boxes intact, reading the BOM and the open orders live, where the suite had read its nightly copy. The suite was retired at renewal.
It becomes a registered function the app's actions call by name, with its inputs and outputs logged.
The process owner, with the configurator role; the application team keeps the gates and the write-back switches.
The inventory is fixed-scope; the first ten apps carry a fixed price written before the work; the platform is priced by capacity with apps included.
We list the applications, the forms and the workflows you run today, group them by the app type they become, and write a fixed price for the first ten before any work begins.