VEXPLOR
VEXPLOR ADOPTION DIAGNOSIS — STEP 1 OF 4

Adopting VEXPLORstarts with a diagnosis.

The adoption diagnosis is the first step: deciding where in your company VEXPLOR goes, and how far. VEXPLOR runs the software; WACE engineers work the floor with you.

TWO TRACKS — FACTORY · OFFICE WORK · FIELD EXPERIENCE 16 YRS / 200+ SITES
01TWO TRACKSFACTORY · OFFICE WORK

First, choose what to diagnose:
the factory or the office work.

There are two adoption diagnoses. The Factory diagnosis looks at your equipment, process and quality data and your existing systems, and sets the scope of the VEXPLOR build. The Office Work diagnosis looks at sales, purchasing, accounting and document work, and sets the scope of VEXPLOR WORK. Manufacturers can take both.

VEXPLOR Adoption Diagnosis — FactoryVEXPLOR Adoption Diagnosis — Office Work
Who it's forManufacturers with a smart factory or MES whose data is scattered across equipment, MES, ERP and spreadsheets, and has not turned into AI resultsCompanies whose sales, purchasing, accounting and document work is spread across teams and files and handled by hand — including the back office of manufacturers
What we look atEquipment, process and quality data; which existing systems (MES, ERP) to connect; where you stand today on the five levels of agent authority (L0–L4)Workflows and approvals, where documents and data live, role- and rank-based permissions, and the repetitive work AI can take off people's hands
Duration8 weeks as standard — fixed in week 1 to fit the plant
45-minute weekly review · interim report in week 4
3–4 weeks of diagnosis plus one pilot demonstrated on your real data
the full schedule follows the diagnosis
PriceOur estimation criteria are public on the pricing page · See pricing →A fixed price, public on the pricing page · See pricing →
Next stepSmart Factory Build → AI Agent PacksAdopting VEXPLOR WORK
We also help you design how to use Korean government support programs — the same engineers stay from the call for proposals through the business plan
02WHAT YOU GETDELIVERABLES AT THE END

When the diagnosis ends,
this is what you receive.

Every number in the report carries its source. For figures such as uptime and defect rate we hand over the calculation scripts, so you can reproduce the same value from the same data.

OUT-1

Diagnosis report

Where your data is today and what keeps it from being used by AI — every figure with its source and calculation script.

OUT-2

Adoption design

Which VEXPLOR modules go where — an integration design for the factory, a data and permission design for office work.

OUT-3

Execution roadmap

What to build first, the schedule, and a clear split between what can start now and what comes after an extension.

OUT-4

One-page executive summary

Only what the decision needs, on one page. The Office Work diagnosis also shows one pilot built on your real data.

03INTO THE MAIN CONTRACTNOTHING IS REDONE

The diagnosis carries over
into the main contract as is.

SCOPE

Scope and schedule

The scope and schedule set in the diagnosis become the build scope of the main contract. Once you sign, the Office Work diagnosis is not repeated.

PRICE

Price ceiling

The price confirmed after the diagnosis does not exceed the ceiling published on the pricing page. If your conditions sit on the boundary between two ranges, we judge to the larger one up front.

STOP

When we stop

If the diagnosis shows no stage worth starting, we end there. We don't push a build.

04ADOPTION PATHSTEP 1 → 4

Adopting VEXPLOR
is four steps, in one order.

You move on only as far as the diagnosis sets the scope. You don't have to take every step.

1 · Adoption Diagnosis → 2 · Smart Factory Build → 3 · AI Agent Packs → 4 · Autonomous FactoryFIG — ADOPTION PATH · THE DARK FACTORY IS WHERE THIS ORDER IS HEADED · SEE THE DARK FACTORY TECHNOLOGY

Where VEXPLOR goes first
is decided together, at the diagnosis.

Just tell us whether it's the factory or the office work, and we'll point you to the right diagnosis.

See pricingRequest a Diagnosis