VEXPLOR
FACTORY DX BUILD

Not an SI project that vanishes once the build is done.A build that leaves standards behind.

This is not the SI approach of developing the same requirement from scratch every time. We build on the VEXPLOR platform, so the standard tables, ontology and screen assets stay with your company after the project ends. From MES to ERP, QMS, WMS and FEMS, it works in any of the 21 areas.

PROJECTS 20+ — MES 8+ · PLM 8+ · AI autonomous factory 1 · Manufacturing-AI specialised 6 · Inter-ministry collaboration 1
01SCOPE21 SOLUTIONS · ONE STANDARD · ANY RANGE

Start in whichever area you need.
All twenty-one areas sit on the same standard.

VEXPLOR has 21 industrial solutions on the same standard tables. Whether it is production, quality, design, materials, energy or safety, we build what you need first, and if you already run an ERP or MES we connect it without replacing it and bring it under the same standard. Expansion happens on the same standard too, and the data integrated this way becomes the base for AI in the next stage. That is the difference from SI, which develops everything anew each time.

ERPMESAPSPLMSCMWMSTMSQMSSPCLIMSHACCPCGMPEAMMROFEMSCRMHRESGSECURITYGROUPWAREDIGITAL TWIN
FULL CATALOG — 21 INDUSTRIAL SOLUTIONS · Teal = areas with the most builds
Solution modules docking onto a single standard foundationFIG — ONE FOUNDATION · TWENTY-ONE MODULES
01-APROVEN RANGESWHERE WE BUILT MOST
RANGE-A

MES·POP

Production execution, output collection, quality control and equipment monitoring. Delivered many times, including the large–SME win-win type (Samsung Electronics) and the general government type.

SCOPEProduction execution · Output collection · Quality control · Equipment monitoring · Shop-floor POP · POP add-on for Younglimwon ERP
RANGE-B

PLM·ERP

Drawing, technical-document and engineering-change management, and order-based PLM. Up to a company-wide build that replaced the existing ERP with VEXPLOR.

SCOPEORDER-BASED PLM · Engineering change (ECO) · Integrated equipment-manufacturing management · ERP replacement build (precision machine-parts company — ICUBE → VEXPLOR)
RANGE-C

Manufacturing AI

Predictive-maintenance, quality-prediction and process-optimisation AI and AI agents connected to business systems. Six manufacturing-AI specialised projects delivered.

SCOPEPredictive maintenance · Quality prediction · Process optimisation · AI AGENT connection
These three are simply the areas where we have built the most. All 21 areas are built the same way
02HOW WE WORK3 STEPS · STANDARDS REMAIN

We work in three steps.

STEP 1

Diagnosis

Site and data diagnosis and a build strategy — the VEXPLOR diagnosis sets the build scope.

OUTSite and data diagnosis report · Standardisation level checked · Build scope fixed
STEP 2

Implementation

System build on the platform, with shop-floor integration such as PLC and IoT

OUTSystem on standard tables · PLC, IOT and existing ERP/MES integration
STEP 3

Operation

Support for settling into operation, and AI model updates — how requests are handled after acceptance is set out in After the build.

OUTOperation settled · AI model updates · Standard assets handed over
DIAGNOSE → BUILD ON PLATFORM [ TABLES 1,539 · UI 1,766 · POP 144 ] → OPERATE [ AI MODEL UPDATES ]FIG — A build that leaves standards · tables, ontology and screen assets stay with the company after the project ends
Where it sits · THE JOURNEY

The first two steps of the dark-factory journey — foundation and integration

This service carries out the first two steps of the journey — foundation (equipment and data standards) and integration (a factory connected as one). The diagnosis before the start fixes the roadmap and the acceptance criteria.

03AFTER GO-LIVEREQUEST TO OPERATION

After the build is finished,
this is how your change requests are handled.

In smart-factory projects, what we hear about most is what comes after the build. The person in charge changes, and a new quotation is needed to alter a single screen. We take requests through one channel that keeps a record. The system handles intake, analysis, the fix, deployment to the development server and the functional check, and nothing goes to production until your person in charge has approved it.

01

Request intake

A request you post on the board, or one raised in a meeting, is registered as one item.

WHOYour person in charge
02

Intake decision

We determine whether it is a defect fix, operations or additional development, and set how it will be handled.

OUTType classified · Handling direction
03

Fix

We make the fix in line with the standard development guide.

OUTChange details · Reason recorded
04

Development server

We deploy first to a development environment separate from production and notify your person in charge.

OUTDeployed to development · Notice sent
05

Functional check

After checking that it works correctly, we send you a request to confirm.

OUTFunctional check · Confirmation request
06

Production after approval

Only what your person in charge has approved goes to production, and we let you know when it is done.

WHOYour approval → assigned developer
Request → Decision · Fix · Development server → Your approval → ProductionFIG — The automated part ends at the development server · a person decides what goes to production

First we separate what counts
as maintenance, and how far it goes.

If they are mixed, "Isn't this a defect fix?" comes up every month. We separate three things at contract time.

Defect fix

Not working as specified

A function you accepted does not run as written in the specification.

COSTFree of charge — for the agreed period from the acceptance date
Operations maintenance

Work needed to keep operations running

Incident response, changes in regulation, data query support and user enquiries.

COSTAnnual rate
Additional development

Not in the acceptance specification

New screens, new rules and new integrations.

COSTWithin the limit: included in the rate · beyond it: per item
The record stays · WHAT REMAINS

It does not break when the person in charge changes

You see the current status of your request yourself — received, under review, in development, deployed, complete. There is no need to phone and ask "What happened to that?" One request stays as one fix, kept together with what was changed and why, so the record continues even when the people in charge on either side are replaced.

04GOV PROGRAMS8 TYPES EXPERIENCED

You can start alongside a government support programme.

We have delivered across the main types of the smart-factory support programme — AI autonomous factory, manufacturing-AI specialised, large–SME win-win type (Samsung Electronics), general government type, expert type, inter-ministry collaboration type (food GMP), local-government type and Smart AS. Standards capability from leading the consortium that developed the national manufacturing-data standardisation reference model (AAS/IEC 63278) is the base for this project work. The conditions and schedule for next year are set out in the guide to the 2027 smart-factory support programme.

20+Builds delivered — MES 8+ · PLM 8+ · Autonomous factory 1 · Manufacturing AI 6 · Inter-ministry collaboration 1
8 typesGovernment programme types delivered
CASE100%LOT tracking automated — glass-processing company (MES+PLM)
6–15 monthsDuration of actual factory DX cases — depending on scope
05WHEN NOT TO3 CASES

Cases where we are not the right fit.

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 supplier for robots or equipment — hardware is supplied by proven partners, and we take on integration and operation.

Quotation basis → Equipment · integration scope · Scope of AI use · Build · integration depthFIG — An exact quotation follows the diagnosis

The diagnosis decides which scope fits.

We look at your data, equipment and system structure and propose a build scope.

See the casesRequest a Diagnosis