Technology and interfaces
Whether a workflow can be automated usually comes down to a single question: can the data be reached? The following answers describe the routes that come into consideration — from documented interfaces through file exchange to step-by-step data integration.
- Can you connect our existing industry software? In many cases, yes. What matters is not the name of the program but the route of access: a documented programming interface, a web service, database access with read rights, or a…
- What if our system has no interface at all? Then there are usually several options left. Many older programs can output reports or lists as files, on which an automatic import can be built. Some allow read access to the…
- Do we have to replace our legacy systems? Not necessarily. A system that does its job and can be connected may stay. A change only becomes sensible when running it grows disproportionately expensive, security updates are…
- How often do the automated workflows run? We define that per workflow. Time-critical procedures — the handover of an incoming order, for example — are triggered by events, so the transfer starts immediately after the…
- What happens if a system is temporarily unreachable? Maintenance windows, updates and network faults are part of operations. We therefore design automated workflows so that items are buffered and caught up in the correct order once…
- Can paper records and PDF archives be included? Yes. Incoming documents are captured, made searchable through text recognition and linked to the matching case — delivery note to job, invoice to order, inspection record to…