01evowerk cloud mrp · manufacturing
One system for the whole plant
MRP, procurement, inventory, quality and shop-floor analytics — running on the sensor data your equipment already speaks (OPC-UA, MQTT).
We reply within one business day. No commitment to see it run.
02The actual cost
The plant is already paying for the system it doesn't have
Every workaround has a price most plants never add up.
- 01
Spreadsheets
MRP math done by hand in a workbook one broken formula away from a stockout.
- 02
Legacy ERP
Six-figure licenses, an eighteen-month rollout, and a module fee for features that should be table stakes.
- 03
Point tools
A forecasting app that doesn't talk to inventory or the quality log — three logins to answer one question.
- 04
Tribal knowledge
The one planner who knows why the BOM is wrong leaves, and the plant finds out the expensive way.
- 05
Hardware lock-in
A dedicated OEE/downtime box that only does OEE/downtime, priced like it's the whole plant.
Most modern lines already speak OPC-UA or MQTT, so ingestion starts on day one instead of after a multi-month PLC integration project. Priced to undercut sensor-hardware-only tools on OEE and downtime alone.
Integrations Hub · day one
- OPC-UA · OPC-DA · MQTTShop-floor telemetry, straight off the PLC
- SAP OData · Oracle · SQL ServerBusiness systems, no export step
- OSIsoft PI · REST · CSV/ExcelHistorians, APIs and the files you already keep
A DAG-based workflow builder schedules the pulls that don't stream.
Time to first reading
- Typical PLC integration~18 months
- EvoWerkDay one
03Twelve modules, two tiers
Eight modules to run the plant. Four to run ahead of it
Core covers what the machines are doing, why they stopped and what the plan needs; Premium adds the models that run ahead of it.
Core
OEE
OEE and SPC control charts, rolled up to a plant summary.
Downtime
Downtime Pareto and MTTR, compared shift against shift.
MRP
Revisioned recipes, netted-vs-gross explosion, build calculator.
Also in CoreBOM & Recipes · Procurement & POs · Inventory & Lots · Quality & RCA · Workflow Automation
Premium
Predictive Maintenance
Machine risk scoring drives the maintenance schedule.
Demand Forecasting
Moving average and exponential smoothing feed the plan directly.
Also in PremiumComputer Vision · AutoML
Industries — one codebase
A per-industry vocabulary layer renames the core — scrap becomes spoilage, shrinkage or return-rate — so no vertical needs a fork.
- Discrete manufacturing≥ 85%OEE target visible per line, per shift
- Food & perishablesFEFOFirst-expiry-first-out enforced on consumption
- Pharma & regulated0Rows that can be updated or deleted, ever
- Automotive & assemblyn-revBOMs tracked across every engineering change
Distribution & retail — Phase 2: the same forecasting layer and report builder, without the MES surface.
Every module reads and writes the same data model — BOM, MRP, POs, lots, OEE and quality in one database with one audit trail, not five integrations. Ask, the built-in copilot, answers in natural language over that data — no SQL, no dashboard hunting, and every answer cites the query it ran.
Running a warehouse instead of a plant? See Inventory Analytics
04No logos yet. Here's the proof instead
Security isn't a feature. It's the foundation
Every claim below is enforced somewhere you can check — a database trigger, a CI gate, a Terraform module — not a paragraph in a security questionnaire.
53 test modules
auth · MRP explosion · procurement · inventory · forecasting · RCA · cross-tenant isolation
0 critical CVEs
bandit · pip-audit · npm audit · Trivy on every push — the build fails otherwise
1 DB-level trigger
2 clouds, one Terraform
- 01
Multi-tenant by design
org_id scoping in every table from day one, not bolted on after the first customer complaint.
- 02
Runs in your infrastructure
The deployment lives in your cloud account, so EvoWerk never holds your production data and never sits in your uptime path.
- 03
Audit log enforced by the database
A Postgres trigger blocks UPDATE and DELETE on audit rows — insert-only holds even if the app layer has a bug.
- 04
MFA that fails safe
TOTP secrets encrypted at rest; re-enrollment requires a password, and the old factor never drops until the new one verifies.
audit_logs · sample trace
05Show, don't dashboard
The shape of the shop floor, not a slide about it
OEE, downtime and machine-risk read off the plant itself, not typed into a report once a week. Figures below are an illustrative sample, not a connected plant.
06Questions we actually get
The four things everyone asks first
If yours isn't here, ask it directly — we reply within one business day.
01Where does EvoWerk run — your cloud or ours?
Yours — your own AWS or Azure account, so EvoWerk never holds your production data and is never in your uptime path. That is the default, not a paid enterprise upgrade.
02What does it take to connect our equipment?
If your equipment speaks OPC-UA or MQTT — most modern lines do out of the box — live ingestion works on day one rather than after a multi-month PLC integration project. A historian feed works too.
03What is the difference between Core and Premium?
Core covers the floor as it runs today: OEE, downtime and MRP. Premium adds predictive maintenance from machine risk scoring, and demand forecasting that feeds the plan without a manual handoff.
04How do you handle security and tenant isolation?
org_id scoping is in every table from day one, the audit log is append-only enforced by a Postgres trigger rather than by application code, and MFA re-enrollment never drops the old factor until the new one verifies. SAST, dependency, secret and container scanning all gate every push.
07Twenty minutes, on your data
See it on your own numbers
Bring one line, one BOM, or one week of downtime — we'll load it and walk through the MRP explosion and the POs it generates. No slides, no forklift migration and no six-figure commitment: your existing finance system stays where it is.
Modelled on the figures above, not a customer: a three-line plant moves OEE 83.4% → 87.3% and MTTR 17.3 → 14.2 min.
We reply within one business day.