OpenMES

OpenMES v0.25.0 is out. Two things in this release, and both came from the same question: what happens when you need to prove what a single unit is made of? Unit-level traceability. A unit now gets its own identity on the line, not at packaging. Scan a component into it and the binding is recorded - another sub-assembly, a material lot, a bare identifier you resolve later. Cartons, pallets, shipping. Import the tester's own log and the measurements land on the unit. Search one serial number and you get the whole story back: product, work order, every station it passed, who was there, how long each step took, what was measured. Forward from a material lot to the finished goods, backward from a unit to its source lots, and recall impact across both. Modules that work on a running installation. Until now, a module uploaded to a live system brought routes that answered and pages that rendered nothing - the frontend bundle is compiled before the module exists. A module now ships its own compiled frontend. Modules can also add fields to the user and worker forms, place a tab on the operator bar, and ship their own translations. And one fix worth naming: a module throwing during boot used to take the entire application with it, including the admin screen you needed to disable that module. Recovery meant SSH and deleting a directory. Not anymore. OpenMES is an open-source MES - Work orders, routing, material lots, quality control, OEE, downtime, shop-floor terminals. Release notes and downloads: https://lnkd.in/dNESKvkt #manufacturing #MES #Industry40 #traceability #opensource #lean

OpenMES v0.24.1 is out. Most of what went into this release came from people telling us something was broken. That is worth saying plainly, because it is how the last two weeks actually went. Downloads work again. Two earlier releases were published with no files attached - the build was silently rejected before it ran, and we found out from a user who had been waiting. Fixed, and the release package is now verified by building a container from it before it ships. If you tried to download OpenMES in the past fortnight and got nothing, please try again. Three bugs our users found: → Checklist items and operator parameters were filed against the wrong process step. If you added a check to step 3, it landed on step 1. Worth reviewing your existing templates - the fix stops new mistakes but does not repair old ones. → Completing an inspection with no recorded criteria returned a server error instead of explaining the problem. It now says what is missing, and no longer offers a button it cannot honour. → A work order with no production steps rendered as a blank screen. It now explains why - an order keeps the process configuration it was created with, so steps added to the template later never reach it. New: usage reporting. OpenMES now reports on itself once a day - versions, which features are switched on, rough size bands, and where errors occur. It never sends anything you entered into OpenMES: no material or product codes, no lot numbers, no order data, no recipes, no personal data, and no error message text. That boundary is enforced by a test that seeds a plant's worth of realistic data, builds the real payload, and fails if any value from the database shows up in it. Error messages are excluded entirely rather than filtered, because filtering them reliably is not possible - our own exceptions name materials and their codes. It is on by default and takes one click to switch off, or OPENMES_TELEMETRY=false before you start. The installer says so up front, and the settings page will print the exact payload on request rather than describing it. An installation behind a closed firewall behaves exactly like a connected one. We build it this way because we would rather you read about it here than discover it in a packet capture.

OpenMES v0.23.0 Plant board - a screen for the display above the floor. A flat grid of tiles, each carrying the machine state, the cause of the stop, how long it has been down, the current order and OEE. The clock runs only during downtime and counts from when the stop actually began. Kiosk mode. Downtime reason dictionary - editable at last. There was no screen before, so a plant was stuck with whatever was seeded at installation. Deletes are soft, history is kept. The OEE report's reason ranking gained a cumulative share. Module system - extended administration (ISA-95, workforce, warehousing, packaging, quality) leaves the core and becomes an installable module. The core publishes extension points; enabling and disabling works without a restart. Example companies - four complete plants to choose from instead of one fixed set: print shop, machine shop, bakery, panel furniture. Upgrading - two things, in this order: 1. Migrations together with the code. Without them, a 500 on the dashboard and OEE, not just the new screens. 2. Install the Enterprise module if the plant uses extended administration. Data survives either way; without the module only the menu entries disappear. DEMO: https://lnkd.in/df47XYsr

🚀 OpenMES v0.20.0 — our biggest release since the platform rewrite This release turns OpenMES from a system that records what happened into one that shows what's happening now — and closes the loop from plan, through production, to materials reconciliation. What's new: - Live shift monitoring - two new screens, Shift Monitor and Line Overview: every machine's state minute by minute, output vs. target, OEE and how many stops are still unexplained. Plus a Modbus machine simulator, so you can try it all with no hardware. - Work orders, rebuilt - a redesigned order page (start and complete routing right from it), lists with infinite scroll, bulk actions and deadline countdowns, and Alerts as real, sortable tables. - Controlled production change - pause a running order, change what it builds under review, and resume on the new configuration without ever overwriting what the floor already did. - Materials reconciliation - partial consumption, returns to stock and lot reclassification, every change booked to the stock-movement ledger. - ISA-95 step times - standard setup/run times with planned-vs-actual reporting. - Engineering CAD documents and warehouse management + ERP sync. - Hundreds of new translations (including Vietnamese) and a plant timezone set in the install wizard. Everything is backward-compatible - existing installs upgrade with no data migration. 👉 https://lnkd.in/dbtiB63e Demo: https://lnkd.in/dxQJBJkd

New in OpenMES: pick the MES that fits your shop. Not every factory needs every feature. So starting with v0.18.0, the very first time an admin logs in, they choose how much MES they want: Lightweight - core production tracking + reports. The simplest setup, perfect for small shops. Advanced - full shop-floor operations: materials & tracing, quality, maintenance, machine connectivity, packaging. Custom - tick exactly the modules you need. Turn something on or off anytime in Settings. Disabled areas simply disappear from the menu, so operators see a clean, focused interface instead of a wall of features they'll never use. Less clutter, faster onboarding, and an MES that grows with you. OpenMES is open source and self-hosted. Github: https://lnkd.in/dZwGB4GZ Demo: https://lnkd.in/dRkip8j8 #manufacturing #MES #opensource #industry40 #leanmanufacturing #smartfactory

Thank you for trusting OpenMES! 🙏 We just checked our GitHub stats, and we're amazed. In the last few weeks, OpenMES was cloned over 47,000 times by more than 3,000 people around the world. When we started this project, we simply wanted to build a free, open-source MES system that anyone could use. Seeing so many of you download it, test it, and build with it means a lot to us. Thank you for your trust and support. This is just the beginning — we keep working to make OpenMES better every day. Want to check it out? Find us on GitHub. Repo: https://lnkd.in/dZwGB4GZ Demo: https://lnkd.in/dxQJBJkd #OpenMES #OpenSource #Manufacturing #MES #GitHub

🏭 OpenMES v0.17.0 is out — and this one goes everywhere. Our open-source Manufacturing Execution System just took a big step toward meeting the shop floor wherever it lives: desktop, mobile, and every operator station on the LAN. Here's what's new 👇 🖥️ OpenMES Desktop — Windows, macOS & Linux A native app (built with Tauri) that bundles PHP + the full backend, so you can run OpenMES as a local desktop app or a LAN MES server with zero manual setup — no separate PHP or database install. First launch runs an unattended installer, then it tucks into the tray. Includes a built-in self-updater with atomic swap, SHA-256 verification, and automatic DB snapshot + rollback. 📱 OpenMES Mobile (Android) A brand-new React Native app for shop-floor operations right from a phone or tablet. 🔌 Live workstation registry Shop-floor PCs now self-register by IP and heartbeat — admins get a live online/offline roster of every device on the floor. 📦 Multiple BOMs per work order Orders can now reference more than one bill of materials (variant / alternative BOMs), with overlapping materials merged intelligently and the selection locked once production starts. 👥 Customer intelligence, end to end Full customer master data → automatic priority scoring with configurable rules → auto-tiering (Silver / Gold / VIP) based on revenue & order history → a customer- and priority-aware production planner that flags overdue high-tier orders. ✅ Read-confirmation on critical instructions Flag any process step so the operato they've read the instructions before completing it — with a full who/when audit trail. ⏱️ Live "Age" column on work-order llease pipeline that now ships desktop installers (.exe / .dmg / .deb / .rpevery release. 100% open source. AGPL-3.0. ⭐ Star us on GitHub: https://lnkd.in/dZwGB4GZ TRY DEMO: https://lnkd.in/dxQJBJkd #Manufacturing #MES #OpenSource #IndIndustrialIoT #Laravel #ReactNative#Tauri #LeanManufacturing #ManufacturingTech

OpenMES v0.16 is out - and it's a big one for traceability. OpenMES is our open-source (AGPL) Manufacturing Execution System - Laravel + React, live-syncing production data straight from the shop floor. Here's what shipped in v0.16End-to-end traceability & recall. The genealogy now runs both ways - from a raw supplier lot all the way to the finished pallet and the customer order, and back. Type in a lot or a serial number and get an instant Recall impact view: every affected work order, quantity consumed, and the exact finished units to pull. - Automated quality control. Quality checks now fire on their own - in production, every N units or minutes, after a downtime or a changeover. Blocking checks hard-gate the line until they're done, with a full non-conformance + CAPA workflow behind them. - Outgoing webhooks. OpenMES can now notify Slack, an ERP or a monitor on key events - HMAC-signed, retried with backoff, and SSRF-guarded. - Modular install. Switch off whole feature areas you don't need and keep the deployment lean. - Rich work instructions. Steps can carry images, PDFs, videos and tap-to-tick checklists, delivered live to the operator tablet. - Plus: milestone backflush, a basic MRP shortage report, built-in backup/restore, WO-time lot picking (FEFO/FIFO/LIFO), and Vietnamese joining English, Polish, German and Turkish. Free, self-hostable, no license fees. ⭐ Star it, try it, break it: 👉 https://lnkd.in/dZwGB4GZ #Manufacturing #MES #Industry40 #OpenSource #SmartFactory #Laravel #React #Traceability #LeanManufacturing

Your ERP tells you THAT your margin dropped. It won't tell you WHY machine 3 loses 40 minutes every shift. That's the real difference between ERP and MES — and why so many manufacturers run their shop floor blind, even though they "have a system." In our new article, zero IT jargon: → what actually separates ERP from MES → 5 questions that reveal what your factory really needs → case study: how one manufacturer discovered their OEE was 54%, not the assumed 75% — and what they did about it Link in the comments 👇 #ERP #MES #Industry40 #manufacturing #smartfactory https://lnkd.in/d_rM8Z3p

A plant manager once proudly showed me his big "innovation" - a whiteboard. Every shift, someone walked the line, scribbled downtime reasons in marker, and photographed the board for the morning meeting. It worked. Until the plant doubled output - and that whiteboard quietly became the single biggest blind spot in a nine-figure operation. The question that landed on the board's desk wasn't "should we digitize?" It was: does open source have any business going near a mission-critical factory floor? After years of conversations with manufacturers, I keep coming back to one thing: Open source on the floor isn't a technical question. It's an ownership question. → It's an opportunity when you want control, transparency, and freedom from vendor lock-in. → It's a risk when you mistake "free to license" for "free to run." Plants don't fail because of code quality. They fail when they adopt the software without adopting the accountability - integration, support, and clear ownership. The technology is ready. The real question is different: Are you ready to own it? I broke the whole thing down - the risks, the benefits, and a decision framework for executives. Link in the comments 👇 #manufacturing #MES #opensource #industry40 #smartfactory