1. The Problem
This Food Manucturer moved their ERP system to Microsoft D365 in the cloud, they faced a critical risk: if the cloud ERP became unavailable (through scheduled maintenance, system updates, or unplanned outages), their highly automated 24/7 production could stop. Even a 2–3 day disruption would result in millions of dollars in lost revenue and disrupt customer orders.
2. The Solution:
Implemented a Survivability Database and web services layer above the MES (GE Plant Applications) to provide local autonomy. This allowed Algood’s MES and production systems to run independently for several days without ERP connectivity.
FrameworX dashboards served as the operator interface, managing production orders, BOMs, formulas, and inventory with lot-level genealogy. Once ERP connectivity was restored, the survivability database synchronized with Microsoft D365, ensuring no loss of order, inventory, or production history.
Simple Architecture Diagram:
Microsoft D365 ERP (Cloud) ↔ Survivability Database (Local) ↔ MES (GE Plant Applications)
↓
Tatsoft FrameworX Dashboards
↓
Rockwell PLCs & Production Lines
Technical Specifications:
ERP: Microsoft D365 (Cloud)
MES: GE Plant Applications
Historian: GE Proficy Historian
Front End: Tatsoft FrameworX dashboards
PLCs: Rockwell Automation
Scope: 2 plants, 100+ clients, redundant servers per plant
3. Key Enablers:
Local database survivability for 2–3 days of autonomy without ERP
Web services synchronization between ERP ↔ MES ↔ Plant floor
Flexible FrameworX GUI for scheduling, order execution, and adjustments
Full genealogy maintained even during disconnection
4. The Results:
Uninterrupted production during ERP outages
Protected millions in potential lost daily revenue
Extended Microsoft D365 capability by enabling true shop-floor continuity
Provided compliance-ready traceability across orders and materials