Can AI connect to an existing ERP without replacing it?+
Yes. We start with the existing process and available interfaces. We determine which logic should stay in ERP and which can run in a separate AI service. Customisation requirements depend on the system version, existing modifications and test-environment availability.
What if the ERP has no suitable API?+
We examine supported exchange mechanisms, middleware and scheduled exports. If only limited data is available, we agree use cases within those limits. We verify the ability to write operations separately from reading and analytics.
How are duplicate orders and requests prevented?+
We assign a business-operation identifier and check previously processed requests and confirmed ERP results. After a timeout, we first establish the actual status, then decide whether to retry or investigate manually.
Can AI change production plans automatically?+
The degree of automation is defined separately for each operation. Changes affecting commitments, budgets or capacity include checks and owner approval. Autonomous actions are permitted only within explicitly defined boundaries.
How is the solution rolled out across several departments?+
We begin with a process and site that have clear data and an owner. After acceptance, we separate shared integration components from local departmental rules. Expansion includes checking each site's reference data, permissions and accounting specifics.
How much does development cost, and how are timelines determined?+
We assess the use cases, data readiness, number of integrations, quality requirements and deployment needs. After discovery, we define stage boundaries, deliverables and acceptance procedures. Infrastructure, model and ongoing support costs are considered separately from development. The precise timeline and budget depend on the agreed scope.
Can the solution run in our company's infrastructure?+
We consider on-premises, cloud and hybrid deployment. The choice depends on data requirements and the availability of models and computing resources. Before implementation, we agree on external requests, access rights, logging and required safeguards with IT and information security teams.
What does the team receive after launch?+
A working solution within the agreed scope, architecture and integration documentation, operating instructions and validation results. Code handover, component rights, access and training are specified in the contract. Ongoing support and SLAs are agreed to meet your company's requirements.