evowerk cloud mrp · multi-tenant manufacturing system

One system for
the whole plant.

MRP, procurement, inventory, quality, and shop-floor analytics — running as one platform instead of a patchwork you're duct-taping together with spreadsheets and point tools.

the actual cost

The plant is already paying for the system it doesn't have.

Every workaround has a price. Most plants just never add it up.

  • SpreadsheetsMRP math done by hand in a workbook one broken formula away from a stockout, held together by whoever built it.
  • Legacy ERPSix-figure licenses, an eighteen-month rollout, and a module fee for features that should be table stakes.
  • Point toolsA forecasting app that doesn't talk to inventory, that doesn't talk to the quality log — three logins to answer one question.
  • Tribal knowledgeThe one planner who knows why the BOM is wrong leaves, and the plant finds out the expensive way.

one platform

Not eleven tools stitched together. One system, eight disciplines.

Choose a module to inspect

MRP & BOMs

Revisioned recipes, netted-vs-gross explosion, build calculator.

  • BOMs and recipes with full revision history
  • Netted-vs-gross MRP explosion across the plan horizon
  • Build calculator with unit conversion on every BOM line

Procurement

Suppliers, MOQ rounding, POs generated straight off the plan.

  • Purchase orders and preferred-supplier selection
  • MOQ rounding applied automatically
  • POs auto-generated off the live MRP plan

Inventory & Lots

On-hand tracking with FEFO consumption and a full audit trail.

  • Lot/FEFO consumption across multiple locations
  • Concurrency-safe stock adjustments
  • Every movement written to an append-only audit trail

Demand Forecasting

Moving average and exponential smoothing feed the plan directly.

  • Moving average / exponential smoothing models
  • Forecast feeds the MRP plan without a manual handoff
  • Same numbers drive automatic PO generation

Shop-Floor Analytics

OEE, SPC, downtime and scrap, rolled up to a plant summary.

  • OEE and SPC control charts
  • Downtime Pareto / MTTR and scrap tracking
  • Shift comparison and a rolled-up plant summary

Quality & RCA

Defect-rate analysis with fishbone cause trees and CAPA.

  • Defect-rate and DPU analysis
  • Root-cause cases with fishbone-style cause trees
  • CAPA actions tracked to closure

Predictive Maintenance

Machine risk scoring drives the maintenance schedule.

  • Machine risk scoring from real operating data
  • Maintenance scheduling driven by that score
  • Feeds the same shop-floor analytics, not a separate silo

BI & Integrations

Dashboards, an Ask-your-data chat, and the connectors to feed both.

  • Pivot/SQL query, custom dashboards, saved reports
  • Natural-language "Ask" chat over your own data
  • OPC-UA, MQTT, SAP OData, and OSIsoft PI connectors, plus a DAG workflow builder

no logos yet — here's the proof instead

Security isn't a feature request here. It's the foundation.

  • Multi-tenant by designorg_id scoping is baked into every table from day one, not bolted on after the first customer complaint.
  • Audit log, enforced by the databaseA Postgres trigger blocks UPDATE and DELETE on audit rows — insert-only holds even if the app layer has a bug.
  • MFA that fails safeTOTP secrets encrypted at rest; re-enrollment requires a password, and the old factor never drops until the new one verifies.
  • Gated on every pushSAST, dependency scanning, secret scanning, and container scanning all run in CI before code ships — not on a quarterly schedule.

show, don't dashboard

The shape of the shop floor, not a slide about it.

Real OEE, scrap, and downtime data — read live off the plant, not typed into a report once a week.

Line 3 · Plant Summarylive
OEE
83.4%+2.1
Scrap rate
1.8%-0.4
Downtime
3h 12m-38m
Throughput · last 12h
Downtime · Pareto
Changeover
92h
Material wait
68h
Unplanned stop
51h
Minor stop
33h
Quality hold
21h

worth twenty minutes

Switching isn't the eighteen-month project you're picturing.

No forklift migration, no six-figure commitment before you've seen it run. Bring one line, one BOM, or one week of downtime data — we'll show you the plan explosion on your own numbers.