One data set
Planning, BDE, MES and quality work on the same database. Whatever one module creates, all the others use too – there are no separate data worlds anyone has to reconcile.
Architecture
Your production data belongs to you.
POM runs on your server: clients in your network, one shared database, roles and permissions enforced server-side. WEKAS does not sit in the operational data path.
Your infrastructure
- POM Desktop
- Shop floor terminal
- MES workstation
POM Server roles, permissions, logic
Database one data set for every module
Access on your terms
POM runs on the local network. Remote access goes through your infrastructure – your company VPN, for instance. No WEKAS cloud is required for operation.
Operated in-house
Installed by your IT or IT provider, backup in the admin area, security log included. We support optionally – never mandatorily.
Licence & sessions
The licence counts sessions – verified locally.
POM verifies its licence entirely locally against a digital signature – no internet access, no licence server. Only concurrently open sessions are counted; a seat without a heartbeat frees itself after 15 minutes.
Roadmap
Where the architecture is heading.
Future architecture, clearly labelled – none of it is available today.
-
01 Roadmap · not available
POM Mobile
iOS and Android on the same backend: orders, BDE, photos, approvals on the shop floor.
-
02 Roadmap · not available
POM Customer
A portal where your customers follow their own orders – internal steps mapped to a few clean external states. Data stays on your server.
-
03 Roadmap · not available
Machine Connectivity
The machine client at the line already exists in POM MES. Automatic machine data is in progress – orders down, feedback up, without retyping.
-
04 Roadmap · not available
License Gateway
One-time activation, then a signed local licence – production never depends on a permanent WEKAS connection.
On-premise, without giving up comfort.
Every module, no contract. We set up the server together with you – and you talk to the people who write the software.