Operations consultancy / Process mapping and integrations
Process mapping and integrations
Your systems do not talk, so people are the integration.
What does the work involve?
- Current workflows documented as they are run, not as the manual describes them.
- Every manual handover of data between systems identified and costed in hours.
- Proposed workflows with the integration requirements written in a form a developer can build from.
What do you get?
- Current and proposed workflow documentation.
- Integration requirements and data handovers specified.
- A testing and implementation scope.
Who does it suit?
Businesses where staff rekey data between systems, or where a new system is about to be bought without the process being understood.
Who is it not for?
Buying a system before the process is mapped; 360 is not a software vendor and does not sell the system it recommends.
How long does it take?
Measured in weeks, set by the number of systems and handovers; the proposal fixes the dates.
What do we need from you?
Missing some of this is normal and is not a reason to wait. Send what exists and we will tell you what the work can and cannot conclude before anyone commits.
- A list of the systems in use and what each one is the master of.
- Time with the people who do the rekeying, because they know where it breaks.
- Any integration or vendor documentation you already hold.
What does it cost?
Scoped project. Scope is set by the number of systems and handovers, not by headcount.
How does 360 work?
A consultant delivers the work and is accountable for the content. Findings come from the data you supply and what we observe inside the agreed scope, and estimated benefits are opportunities to test rather than guaranteed savings. Where a recommendation could lead to 360 earning from supply, we say so in the report so you can compare it against the market. Full terms are on the purchase terms page.
Not sure this is the right one? The operations health check takes ten minutes, costs nothing and tells you where to look first.
Questions
Do you build the integrations?
We specify and coordinate them. The build is done by your developer or the vendor, against a scope that is clear enough to quote.
We are about to buy a new system. Should we map the process first?
Yes. A system bought before the process is mapped tends to automate the rekeying rather than remove it. The map shows which system is the master of each piece of data and where the handovers are, which is the brief the vendor should be quoting against.
Which systems do you work with?
Whatever you run: ERP, WMS, TMS, accounting, ecommerce and the spreadsheets between them. The work is the process and the data ownership, not a particular product, and 360 does not sell or resell any of them.
What comes out of it?
A process map as the work really runs, a list of every manual handover with the hours and the errors it carries, and the integration options for the ones worth removing, costed so you can put them to the vendor or your own developer.
Do you travel outside Sydney?
Site days run in person. Travel is included for Greater Sydney, the Illawarra, the Central Coast and Newcastle; anywhere else in Australia or New Zealand the travel is quoted at cost before you commit, and the desk work is done remotely either way.
Related work
All sixteen consultancy services.
On site across Australia, with the deepest coverage in Sydney and Melbourne. Travel outside those areas is quoted as its own line rather than folded into the fee.
Benchmarking yourself? We published what a good DIFOT actually is. Want the price before you ask? See what a review costs. Not sure where to start? Take the ten minute health check.