VEXPLOR
KO/ ENLog inRequest a Diagnosis
M-04 · VEXPLOR CONNECT

A different signal from every machine,turned into one standard dataset.

Connect is the equipment and system integration module. Using the international standard AAS (IEC 63278) and industrial protocols, it converts floor data into a standard format so any machine connects to the OS.

AAS IEC 63278 · OPC-UA · MQTT → KAFKA · EDGE GATEWAY
VEXPLOR CONNECT · AAS MODELER
Connect AAS modeler — product screen
FIG — DEFINE THE SUBMODEL, AND THE INTEGRATION IS DONE · PRODUCT SCREENScreen data is illustrative
DEVICE [ OPC-UA · MQTT ] → EDGE GATEWAY → KAFKA → AAS SUBMODEL [ IEC 63278 ] → ONTOLOGYFIG — FIELD-TO-STANDARD PATH · Meaning comes up, not just tags
01PROBLEMEVERY INTEGRATION STARTS FROM ZERO

Every integration project
starts over from scratch.

A different protocol per machine, a different format per vendor. Connected, but meaningless — the tags pile up, and no one knows which value came from which machine.

  • International standard AAS (IEC 63278)Model equipment as standard asset administration shells, so what you collect is meaningful data, not just tags.SUBMODELSIDENTIFICATION · TECHNICAL SPEC · OPERATIONAL DATA · AI SUBMODEL — LEADING THE NATIONAL REFERENCE-MODEL CONSORTIUM
  • WACE-AAS ModelerOne AAS modeling task in 3 days — 57% faster than before (AAS modeling only).SPEED1 MODEL IN 3 DAYS · 57% FASTER (AAS MODELING ONLY)
  • Industrial protocol stackOPC-UA and MQTT ingestion through a Kafka pipeline. Edge gateway supported.PIPEOPC-UA · MQTT → KAFKA STREAM · EDGE GATEWAY
IEC 63278International standard AAS — leading the national manufacturing-data standardization reference-model consortium
3 daysOne AAS model · 57% faster (AAS modeling only)
OPC-UA · MQTTOpen-protocol ingestion → Kafka
EDGEGateway supported

Existing ERP and MES integrate at this layer too.

A project integrating an existing ERP such as K-System ERP into the ontology is in progress.

Cases (KR)Request a Diagnosis
← M-03 INSIGHTNext — M-05 VISION →