Do you provide an ERP or MES product?
No. We build custom business applications and integrations around the systems you already use. We do not sell an ERP or MES product, and we do not claim to have built one. If standard ERP or MES software already covers a process well, we will say so.
Can you connect our existing ERP, plant or shop-floor systems?
Often this can be considered, depending on the interfaces those systems expose and their vendors' terms. Options range from supported APIs and database access to file exchange. We confirm what is feasible during discovery and cannot promise compatibility with every product or version.
When does a manufacturer need a custom application instead of packaged software?
When a process is central to how you operate, depends on rules or data that packaged software cannot hold, and is currently run through spreadsheets, paper or manual workarounds. If configured software already covers the need, that is usually the better and cheaper choice, and we would rather tell you than build something unnecessary.
Can you replace a production, inventory or quality spreadsheet?
It can be considered. We start by looking at how the spreadsheet is used, who depends on it and where it breaks down. The right outcome may be a focused web application, an automation between existing systems, or a better-controlled spreadsheet process. Replacing it is not always the right answer.
Which manufacturing processes are suitable to start with?
A good first process is one with a clear owner, a manageable number of systems and a visible cost from the current approach. Examples include production or work-order tracking, inventory and stock reconciliation, quality records, maintenance requests, and exception handling between office and plant systems. These are illustrative; we assess each process on its own facts.
Do you have manufacturing case studies?
No, and we prefer to say so plainly. Our documented experience is on the Experience pages, where it is labelled as current Avasarant work, prior team experience or illustrative. We do not present examples as delivered manufacturing projects.
How would you avoid disrupting production?
By planning the change in stages, working on one process at a time and, where it helps, running the new system alongside current practice until it has proved reliable. The exact approach depends on your shifts, systems and tolerance for downtime, and we agree it during discovery.
How do you handle data from our current systems?
We identify what data exists, where it lives and how reliable it is, then agree what to move, what to link and what to leave. Migrations are checked against the source records before anything relies on them. Data quality problems are common and are usually better found early.
Who owns the application and the data?
You should know exactly what you are getting before work begins. Ownership of the code, hosting and data, and any ongoing support arrangement, are agreed in writing as part of the engagement.
How do you scope a manufacturing engagement?
We start with one process, map the systems and exceptions involved, and agree a small first increment. Timelines and cost depend on the number of systems and the quality of their interfaces, so we do not quote them before reviewing the situation.