Integration with industrial systems
NDDev connects equipment and shop-floor software with your business systems: data from machines and sensors flows into ERP, 1C and reports on its own, and jobs from the business system reach production. We build the exchange with queues, retries and a log, so a failure in one system leaves the others running. NDDev has worked since 2019.
Who it is for
Manufacturers whose equipment data lives apart from their accounting, with staff copying figures by hand between the shop floor, the warehouse and finance.
- Machines and sensors linked to ERP and 1C
- Queues, retries and an exchange log
- Gaps visible to the people responsible
- Runs on your infrastructure
How shop-floor data reaches your accounts
We start with an exchange map: what data the equipment produces, which systems wait for it, who owns each field. Then we write an intermediary program that reads the equipment through its protocols and APIs, converts the data to the business system's format and passes it through that system's interfaces.
- a data map between the shop floor and accounting
- an intermediary program for equipment communication
- transfer to ERP, 1C and other business systems
- queues, retries and double-write protection
- an exchange log and failure notifications
- a gaps screen for the staff responsible
We build the exchange on rules proven in our integrations: queues and retries with growing delays, signature checks on incoming requests, protection against double writes and a log of every call. An unknown value is recorded as a gap and shown to a member of staff, and an outage in one system leaves the others running.
The order of connection
A trial exchange on one operation comes first, and everything else follows its pattern.
Exchange map
We describe the sources, the recipients and the rules for each field, and agree them with your process engineers and finance team.
Trial exchange
We connect one machine and one accounting operation and check the data against manual records.
Full connection
We extend the exchange to the remaining equipment and operations and switch on the log and notifications.
Handover to IT
We deliver the code, the exchange description and an administrator guide to your IT team.
Questions about linking the shop floor and accounting
Which business systems do you work with?
Most often 1C and ERP systems, SAP among them. We connect through the interfaces the system already provides, and first check which operations they allow.
What happens if the business system is down?
The intermediary program queues the data and sends it once the system is back. Production keeps running, and the log shows what was transferred and when.
Do we need to change our equipment?
The protocols and data outputs the equipment already has are usually enough, and we confirm this in the trial exchange. If the data falls short, we tell you which measurements are worth adding.
How much does the integration cost?
The price depends on the number of systems and machines, the volume of the exchange and the reconciliation rules. You will find the starting price in the price block on this page. The total goes into the specification, which we write as part of the project price.
Why does RnD handle this integration?
One side of this exchange sits on the shop floor, with its own protocols, data rates and access limits. That is the work of our RnD practice, which writes software for equipment. Web service and API integrations are done by NDDev.Dev.
from $2,300
- Free warranty
- 20 days
Prices are starting prices for information only and are not a public offer. The final price is fixed in the specification.
RnD consulting and integration
Related
Tell us where figures are copied by hand
Name the equipment and the business system. We will suggest which exchange to start with.
We reply within 24 hours