Connecting a carpet loom to 1C: an integration story

In a carpet factory the most valuable data lives inside the loom: metres woven, which design, how long it stood idle. It usually reaches accounting by hand, late and with errors. At Urgaz we automated it; the approach fits other equipment too.

Step 1: what the machine "speaks"

• Find the protocol in the manual: usually Modbus, OPC UA, or a plain CSV/log in a network folder.
• Nothing there? The vendor's software has an export format — use that as the source.

Step 2: a service in the middle

• Never wire the machine straight into 1C. A small service sits between: reads, validates, normalises and writes to a database.
• It keeps running when the loom is off and when 1C is being updated — the two sides are not tightly coupled.

Step 3: the 1C side

• In 1C you write a receiver for external data on the production document (an HTTP service or scheduled exchange).
• Every record carries machine id, shift and time — the "which loom worked how much" report then builds itself.

Handling failures

• Network down — the service queues and sends later; nothing is lost.
• A suspicious value (10× the metres in one shift) goes to review, not straight in.

Accounting now sees production in the same shift, not the next day. And the project does not end at 1C: the same middle service later connects to SAP and to the warehouse system.