Connected to your ERP, without ever writing to it

01

What it reads and what it leaves alone

From the ERP, Vexyon reads three things: customers, active orders and planned manufacturing times. They fill the clock-in dropdowns and feed the comparison between actual hours and planned time. Nothing more, nothing less.

Nothing travels the other way. Entries, users, drawings and reports are stored on Vexyon’s side. The ERP stays in charge of customers and orders, and Vexyon makes no writes to it.

02

Four database engines

If your ERP keeps its data in a database, the connection is made straight to that database. The architecture is prepared for the most common engines:

• Firebird
• SQL Server
• MySQL and MariaDB
• PostgreSQL

The way to know how it fits your case is to see it: the demo can run connected to a copy of your ERP’s database, on your own data rather than an example. If you use Odoo, which runs on PostgreSQL, the details are in Vexyon with Odoo.

03

Configurable, without touching anything on your side

The connection is defined in Vexyon. The ERP does not have to be modified:

Engine

Firebird, SQL Server, MySQL, MariaDB or PostgreSQL.

Host and user

Where the database is and which user connects to it. Since Vexyon only reads, a read-only user is all it needs.

Tables and columns

Which tables and columns hold customers, orders and planned times. Every ERP stores them its own way, which is why the mapping is configurable.

Interval

How often the catalogue is refreshed: at the interval you decide, or on demand.

04

Syncing the catalogue

At the interval you choose (every 15 minutes, say) or when you press the button, Vexyon refreshes customers, active orders and planned times in a single pass. That catalogue feeds the clock-in dropdowns and the comparison, and nothing else.

If the ERP does not answer one day, the panel lets you manage customers and orders by hand as a safety net.

05

A history that does not depend on the ERP

Because entries do not live inside the ERP, what was logged stays even when the ERP changes. If an order is gone two years from now, its hours are still in Vexyon’s history, intact.

And reports filter by date, never by status: the spreadsheet for a closed month comes out the same every time it is downloaded. How that history is used for production control.

06

Without an ERP too

The connection is optional. Vexyon runs on its own from day one: you add customers and orders from the panel and the shop floor clocks in that same afternoon. You can start that way and connect the ERP later, without losing a single entry.