FAQ

Frequently Asked Questions

The questions we hear most during selection and delivery.

Selection & delivery

If your question is not covered here, get in touch.

Which industrial protocols and devices do you support?

We use the industrial gateway to connect IPCs, PLCs and I/O modules, with support for mainstream protocols such as Modbus, OPC UA and MQTT. Device coverage includes PLCs, CNC machines, industrial robots, instruments and sensors. Existing equipment normally needs no modification — a gateway is simply added.

How long does a project take?

2–4 weeks for standard products and 6–12 weeks for custom projects; on-site work is scoped by point count and site conditions. We recommend a 2–4 week POC before committing to a rollout.

Do you support on-premise deployment? Does data leave the plant?

On-premises, private cloud and hybrid deployments are all supported, including fully offline operation on an isolated network. The middleware runs inside your plant or warehouse, so the data loop can close there and shop-floor work continues even when upstream systems are offline. Only essential diagnostic information is uploaded, and only with your explicit authorisation.

How do you integrate with existing SCADA, MES and ERP?

Standard northbound APIs enable plug-in integration with ERP, WMS and MES through three channels: REST APIs, direct database access, or message queues (Kafka) and MQTT — chosen to match your existing systems. We build and commission the interfaces; you only need to provide a test environment and a point of contact. Existing systems are never modified, so integration is zero-intrusion, with canary release and fast rollback.

What scale can you handle?

The platform scales horizontally across nodes, so plants, workshops or warehouses can be deployed independently and managed centrally. Auto-ID hardware and machine tools can be connected together with multi-machine management. We provide load-test figures against your actual device list in the solution phase.

How are data security and compliance handled?

Data closes the loop inside the on-site middleware by default, and you decide what may leave the plant. Transport is TLS-encrypted, with mutual certificate authentication for devices, fine-grained role-based access and full audit logging.

What are your support response times?

Ticketing and phone support during business hours (Mon–Fri 09:00–18:00, GMT+8): a response window of 2 hours for general issues, remote engagement within 4 hours for critical faults, and on-site attendance within 24 hours where required. Specific SLAs are agreed in the contract. Exact SLAs are agreed in contract.

Can we start with a pilot?

Yes — it is the approach we recommend. Typically 1–2 production lines or 50 points over 2–4 weeks, validating collection stability and business value with real production data before a full contract.

How is pricing structured?

Either a subscription priced by point or device, or fixed-price project delivery. Quotes specify whether edge hardware, on-site implementation, training and first-year support are included. Quotes specify whether edge hardware, on-site implementation, training and first-year support are included; we scope and quote after a requirements discussion.

Still have questions?

Tell us about your site and an engineer will give you an actionable answer.

Contact Us