Why Manufacturing Needs a Data Bus
In a manufacturing company, plan, actuals, and stock data live in different systems: the plan comes from 1C:ERP, production actuals come from MES and OT controllers, movement of materials and finished goods comes from the warehouse system (WMS), and analysts need the consolidated view in BI. As long as these systems are connected point to point or reconciled manually in Excel, the company pays twice: with plan-vs-actual mismatches that are noticed too late, and with people who compare exports every morning.
A service bus (ESB, Enterprise Service Bus) removes manual reconciliation: each system sends the event once, and the bus reliably delivers it to all consumers along the defined route. This article is an overview based on public sources of what is done in manufacturing with Datareon ESB. It is not a KT.Team project description, but an industry example with references.
What Datareon ESB can do
Datareon ESB is a CIS enterprise service bus for building an enterprise integration landscape: it connects manufacturing systems, warehouses, and analytics tools, translating data from one format to another. According to the vendor, more than 700 customers use the Datareon platform, over 5,000 systems have been integrated, and more than 1,000 implementation projects have been delivered, including in large industry (datareon.ru).
The key property for manufacturing is guaranteed message delivery. It is implemented through acknowledgments, queues, and retry mechanisms: the bus itself monitors channel availability and delivery to the receiving system (sofros.ru). Thanks to routing, the source system sends the message to the bus once and does not need to know who will receive it or whether the recipient is ready; the bus delivers the event to all subscribers on the current route. For manufacturing, this means a fact export from MES will not be lost if BI is under maintenance at that moment: the message will wait in the queue until delivery.
Typical setup: 1C + MES/OT + warehouse + BI
The integration is built as a set of data flows, each responsible for one type of event:
- Production Plan goes from 1C:ERP to MES - shift assignments, routes, standards.
- Production output returns from MES and OT control systems to 1C - operation completion marks, defects, downtime.
- Stock and material movement are synchronized between the warehouse system and accounting - receipt, issue to production, and finished goods output.
- Summary data goes to BI for OEE, plan-vs-actual, and cost calculation.
Based on similar implementations, dozens of such flows are deployed in manufacturing - in one project on Datareon ESB, the target integration design was created and 48 data flows were launched. Datareon is also used to connect 1C:ERP with custom production management systems, including at an electronics manufacturing company (decosystems.ru).
What this delivers in practice
The vendor's published cases present results in business terms, not feature terms:
- PTPA Group (pipeline valves) integrated 7 systems through Datareon ESB - T-FLEX.DOCs, 1C:Enterprise, 1C:Document Management, 1C:Payroll and HR, 1C:Holding Management, BFG-MRP, and CRM - and achieved reliable information exchange between all applications (decosystems.ru).
- "Phoenix Contact RUS" via the bus connected the AXELOT WMS system to warehouse logistics and enabled stable data exchange and real-time warehouse management (decosystems.ru).
All flows are managed through a single monitoring dashboard, turning an "integration zoo" into an observable landscape: you can see which flow has stopped and where the queue has built up.
Architectural Point: Connectivity, Not a Monolith
The key point is that the bus does not turn 1C, MES, and the warehouse into a single monolith. Each system remains independent and exchanges events through the bus rather than through rigid direct links. This provides loose coupling: replacing WMS locally or updating MES does not break neighboring systems as long as the message contract remains intact. It also provides transferability: the integration landscape is described through explicit flows and routes, so it can be handed over to another team or contractor without untangling a web of point exports.
This is how KT.Team believes manufacturing integrations should be built: do not stitch systems into a monolith for the sake of speed, but keep them loosely coupled through a bus with guaranteed delivery. Then dozens of data flows work as an observable, maintainable mechanism rather than a set of fragile overnight exports.
Conclusion
Datareon ESB in manufacturing solves a specific task: end-to-end exchange of plan-vs-actual data and inventory balances between the shop floor (MES/APCS), accounting (1C), and analytics (BI) without manual reconciliation. The business result is that discrepancies are visible immediately, not at the end of the month, and people do not spend a shift reconciling exports.
