Processes we can scope and automate.
These three demonstration examples show how we think about start, end, systems, exceptions and human control. They are not customer cases and not the full catalogue.
These three demonstration examples show how we think about start, end, systems, exceptions and human control. They are not customer cases and not the full catalogue.
Automation type
Domain
3 of 3 demonstration examples. The full process catalogue will be imported from the source register when available.
Incoming order emails and PDFs are interpreted, customer and item are matched against master data, and an order draft is created. A person reviews and approves before anything becomes a binding order.
Review and approval before the order becomes binding.
Read the exampleA work or service report is structured, reconciled against the agreement and price list, and becomes an invoice-ready basis. An authorised person attests it before it reaches finance.
Attestation by an authorised person before it becomes invoice basis.
Read the exampleAccounts, contacts, relationships and history are inventoried, mapped and test-loaded. Reconciliation against source and target happens before a controlled cutover with a write stop and a rollback plan.
Business reconciliation and acceptance before cutover; cutover is a separate decision.
Read the exampleThis is three curated demonstrations, not the full process catalogue. The original catalogue with 298 candidates, domains and overlap groups will be imported from the source register when available – we do not fill it with invented processes or maturity levels.
A process in the catalogue is not automatically orderable. A delivery requires a scoped process owner, volume, data, systems and acceptance criteria.
Describe your variant in one sentence. We use it to propose the next step – a process analysis on site or a defined automation.
Describe your process