Founding Partners Wanted: An On-Premise MES That Connects ERP Orders, Operators and Machines

On most shop floors the ERP knows what should be made, the operators know what they actually did, and the machines know how they ran, but those three never meet. The result is paper travellers, end-of-shift re-keying, and a certificate or report that someone assembles by hand from three sources.

simpliMES is our manufacturing execution system for closing that gap: "run the floor, record everything." It takes work orders from your ERP, puts them in front of operators step by step, and attaches equipment telemetry to each run. It is running now, and we are opening a founding-partner program for the first factories that want to deploy it.

This post covers what you get, what is not listed, and how to join.

Who this is for

• Discrete and batch manufacturers replacing paper travellers, spreadsheets or disconnected dashboards.
• Plants that want to keep data on site. simpliMES is on-premise, with the OT and IT networks kept separate.
• Factories with an ERP that creates the work orders, and a mix of machines speaking Modbus, OPC-UA or Siemens S7.
• Teams that want to try it before they talk about it. There is a live demo and a public guide, described below.

What is live today

flowchart TD
    E["ERP - items, BOMs, work orders"] --> C["simpliMES core - UI, API, domain logic"]
    O["Operator terminals"] --> C
    P["PLCs on the OT network"] --> K["Connector - Modbus, OPC-UA, S7 with disk spool"]
    K --> M["MQTT broker over TLS"]
    M --> C
    C --> D[("Postgres and TimescaleDB")]

• Work orders from your ERP. Items, BOMs and work orders sync in from the ERP, or you enter them manually. A work order starts as a draft. Releasing it creates its steps from the routing or process spec, or you add steps by hand. States are draft, released, in progress, completed, closed and cancelled.
• Operator terminals. Bind a terminal to a workstation once. The operator identifies with a badge or PIN, sees the job list and machines for their work centre, picks a step and a machine, starts the run, then reports good and scrap quantities and ends it.
• Telemetry tied to each run. Equipment readings are matched to the run by time window and stored in TimescaleDB, so reports and certificates draw on the combined data instead of three separate sources.
• A connector for your machines. It polls devices over Modbus, OPC-UA and S7, publishes readings through an MQTT broker over TLS, and buffers to disk if the link drops.
• Plant structure. Equipment, areas, work centres, workstations, operators and users are all managed in the system. The interface includes a floor plan and a dashboard.
• Languages. The product pages and guide are offered in English, Thai, Japanese and Chinese.

Try it before you talk to us

There is a live demo with demo accounts listed on the sign-in page, and a public guide that walks through the work order flow, the operator terminal and the telemetry path. The guide also includes an Edge Test page where you can publish test telemetry from your own gateway over MQTT with TLS and see it arrive. The demo data resets periodically, so treat it as a place to look around, not to keep anything.

What is not listed, so you can plan around it

• The simpliMES page does not describe features such as OEE calculation, lot and serial traceability, quality inspection workflows or shift management. We do not claim them here. Tell us which you need and we will say plainly whether they exist today or would be new work.
• ERP sync details are limited in public documentation. Which ERP systems and which fields you need is something we confirm in scoping.
• Roles and permissions are not described in the guide. Ask us what your user model needs.
• There is no published price. Pricing is scoped per factory. If you want a fully custom MES built around your plant, that is a different, project-based engagement with published price bands on our MES development page.
• The demo is not your plant. It shows the flow and the interface, not your machines, routings or ERP.
• Roadmap items are marked as roadmap in your proposal. We do not sell features that do not exist as if they do.

What founding partners get

• A guided session on the live demo, using your own product and routing as the example.
• A gateway connection test with your machines or a representative one, to prove the telemetry path before you commit.
• A scoped proposal that separates what exists today from what would be new work.
• Priority onboarding for your first line.
• A direct line to the engineers who built it, in Bangkok time, by LINE, WhatsApp, phone or email.
• A say in the roadmap. What we build next is shaped by the first plants who run it.

Commercial terms for founding partners are agreed with you in the proposal. We do not publish a fixed founding discount.

How to join

1. Look first: open the live demo and read the guide.
2. Tell us about your plant: what ERP you use, how many machines and what protocols they speak, and how many lines you would start with.
3. Get a scoped proposal, then decide.

Email us to become a founding partner

Prefer chat? LINE: iiitum1984, WhatsApp: +66 83 001 0222, or call +66 97 496 6397.

FAQ

Is simpliMES cloud or on-premise?
On-premise, with the OT and IT networks separated.

Which machines can it talk to?
The connector polls over Modbus, OPC-UA and Siemens S7. Other protocols are scoped separately.

What happens if the network link drops?
The connector buffers readings to disk and resumes.

Can operators log in at the machine?
Yes. Terminals are bound to a workstation, and operators identify with a badge or PIN.

Does it do OEE, traceability or quality workflows?
The simpliMES page does not list them. Ask us and we will answer honestly.

Is there a fixed founding-partner discount?
We do not publish one. Terms are scoped per partner in the proposal.