VEXPLOR
VEXPLOR OPEN SOURCE · APACHE-2.0 · GITHUB.COM/WACEINC

WACE open sourcetwo programs that build equipment AAS and collect factory machine values

VEXPLOR AAS Studio and VEXPLOR Edge are published under Apache-2.0. Machine and factory IT engineers download and install them themselves, change them, and ship them in commercial products.

The two connect through the contract vexplor.edge/1. With the server inside the factory, AAS Studio alone is enough; with the server outside, add Edge on a factory PC.
01PROJECTSTWO REPOSITORIES

Two programs
are published

PROJECT 01 · v2.7.0 · APACHE-2.0

VEXPLOR AAS Studio

Author equipment AAS (Asset Administration Shell) in a web app and check it against 43 rules. It collects OPC UA, Modbus TCP and MQTT values as the collection links (AID) in the AAS describe, and serves them through the IDTA Part 2 REST API and MES, ERP and CMMS integration.

Versionv2.7.0
Runs onDocker Compose · Node.js 22+ — Linux, Windows, macOS
LicenseApache License 2.0
PROJECT 02 · v1.0.0 · APACHE-2.0

VEXPLOR Edge

The remote collector you put on one factory PC. It reads only the machine values on a list a person approved and sends them out over HTTPS — outbound only. It connects from the AAS Studio screen with one button and one pasted line.

Versionv1.0.0
Runs onLinux x64 · arm64 (systemd) — Windows in preparation
LicenseApache License 2.0
02HOW THEY CONNECTAASX → READ LIST → FACTORY PC

AAS Studio decides what to read
and Edge reads it inside the factory

STEP 01 · AAS STUDIO

Add collection links to the AASX

The AID in an AASX says which tags of which machine to read, at which address and interval. The server turns them into a read list.

STEP 02 · APPROVAL

A person approves the read list

Making the command in Settings → Remote collectors approves the list. The collector reads only an approved list; a changed list is not read until it is approved again.

STEP 03 · EDGE

The factory PC reads and sends out

VEXPLOR Edge, installed by one command line, only reads the PLCs and sends signed batches to the server over HTTPS 443. The values appear in the equipment file's Collect pane.

Where the server isWhat you install
On the machine network — a server in the factoryVEXPLOR AAS Studio only. The collector inside the server reads the machines
Outside the factory — cloud · head officeVEXPLOR AAS Studio + VEXPLOR Edge on one factory PC
03PRINCIPLESHOW WE PUBLISH

How WACE publishes
its open source

ItemDetails
LicenseApache License 2.0 — change it and ship it in commercial products. The VEXPLOR and WACE names and logos are not part of that license (NOTICE in each repository)
ReleasesEvery version is a GitHub release with the files and SHA256SUMS. The installers install only when the checksum matches
DocumentationEach repository has a README, a user guide and an install guide in Korean and English. When a version goes up, the docs, the README and this site change the same day
TestsCI runs the tests on every change. VEXPLOR Edge must also pass interop tests against a real AAS Studio server
Security reportsAs described in each repository's SECURITY.md
ContributingIssues and pull requests are welcome; the steps are in each repository's CONTRIBUTING.md
04FAQQUESTIONS

WACE open source
— frequent questions

Q1. Is WACE open source free?
VEXPLOR AAS Studio and VEXPLOR Edge are both open source under the Apache License 2.0: download them, change them and ship them in commercial products. The VEXPLOR and WACE names and logos are not part of that license.
Q2. How do AAS Studio and Edge differ?
VEXPLOR AAS Studio is a web application on a server that authors and checks equipment AASX and collects and serves values. VEXPLOR Edge is a collector on a factory PC that reads approved machine values and sends them to the server when the server is outside the factory.
Q3. Do I need both?
With the server on the machine network, VEXPLOR AAS Studio alone is enough. Only when the server is outside the factory (cloud, head office) do you add VEXPLOR Edge on one factory PC.
Q4. Which machine protocols do they read?
OPC UA, Modbus TCP and MQTT. Both use the same reading code, so values are read the same way inside the server or on the factory PC.
Q5. Where are the user guides?
In each GitHub repository: docs/usage.md (Korean docs/사용법.md), from the first install to troubleshooting, with screen captures. The project cards above link straight to them.
Q6. Can WACE review our machine integration with us?
Request an adoption review and we look at the scope of machine and system integration with you.

From equipment AAS to factory machine values, in open source

Download from the public repositories and install it yourself. To review machine integration together, request an adoption review.

github.com/waceincRequest a review