We do not replace the systems you use today. ERP, MES, PDM and even Excel — the systems and data your company already has are connected through an ontology, and an AI work team is built on top of them. Five agents that read data, forecast supply, propose orders, communicate with suppliers and write reports work together as one workflow.
When an order comes in, people search through ERP, PDM and Excel to check materials, set order quantities from experience, and chase suppliers by phone and email. The system only keeps the records; decision and execution are left entirely to people. These are four structural problems we have seen repeatedly on manufacturing sites.
Item codes differ between ERP, PDM and outsourcing systems, so people match the same material by eye.
The more items there are and the higher the share of outsourcing, the more complex supply decisions become, and the more they depend on one person's experience.
It is hard to say with confidence when materials will arrive and when production can start.
Orders, reminders and replies for dozens of suppliers are scattered across phone calls and emails, and managing them becomes a job in itself.
FIG — FIVE ROLES, ONE RELAYAdding one agent per task soon turns into dozens of maintenance liabilities. How we handle that maintenance is set out in After the build. What is needed is not a number of agents but an environment in which agents can work. The point is the team structure, not the number five — five agents with roles divided from perception to generation pick up one another's results on a single ontology environment and carry the work through to the end. Purchasing and materials is the first pack — with the environment left as it is, the same approach extends to other areas such as production, quality and equipment.
In the dark factory journey, this service is the third step, intelligence. Agents begin to make decisions on the data standard set up in the foundation and integration steps. The environment in which agents work starts with a diagnosis — the VEXPLOR diagnosis first checks the data standard and readiness for integration.
FIG — ADD WITHOUT BREAKINGReplacing a system is a decision that takes years. AI agents do not ask for that decision — the existing ERP, MES and PDM servers are left untouched, an edge server pre-processes the data securely and passes it to the VEXPLOR AI server, and the ontology maps each system's data structure automatically.
| AS-IS — people search the systems | TO-BE — agents report to people | |
|---|---|---|
| Sales · orders | After an order, material availability is checked department by department before a delivery date is given | The supply forecast agent presents material and delivery scenarios as soon as the order arrives |
| BOM · material matching | Item codes in ERP, PDM and Excel are matched by eye | Automatic ontology mapping absorbs the code mismatches; people only check the matching result |
| Outsourcing orders | Order quantities are set from experience and managed by phone and email | The order optimisation and communication agents handle proposals, dispatch and replies; people approve |
An answer comes with evidence found in the company's records by following definitions and relationships. When there is no evidence it does not answer, so a plausible guess is not reported to people.
BASERelationship graph derived from table definitions · Evidence search — no answer when there is no evidenceWhat an agent is allowed to do is controlled through the AAF permission framework. Proposal only, or execution after approval — the company sets the scope.
CONTROLAAF L0~L4 · Approval gate · Audit log of every decisionThis foundation is not only for our own agents. Whichever AI agents you come to use, working safely in a factory requires a foundation of data standards, permissions and verification to be in place first. That foundation is what VEXPLOR builds — agents will keep changing, but the foundation stays with the company.
How this technology works — technology map →Five purchasing and materials AI agents across multiple plants for a manufacturer of semiconductor parts (N2 Purge). The existing K-System ERP (Younglimwon) is not replaced; it is connected through an ontology.
STACKAI AGENT ×5 · K-SYSTEM ERP (YOUNGLIMWON) + PDM ontology mapping · 2026.07–2027.03A project supplying POP to the Younglimwon ERP ecosystem is delivered, and we also build under a cooperation model with ERP partners — the partner takes the customer relationship and the ERP domain, and WACE takes the AI build and operation.
MODELERP partner channel cooperation · Government manufacturing-AI specialised track can be used · Phased adoption (proposal only → execution on approval)There are three. You want a fully unmanned factory right now — we commit only to step-by-step autonomy. You want office automation only, with no manufacturing — our expertise is in manufacturing. You are looking for a hardware vendor for robots or equipment — hardware is supplied by verified partners, and we take integration and operation.
We diagnose the systems and data structures you use, and decide together which task's agent to start with.