PlatformMachine connectivity & API

Connect — capture, gateway & API

Every machine connected. Every reading yours.

Machine connectivity comes down to two questions: which protocol reaches each of your machines, and what your network has to allow. The answers are OPC UA, Modbus TCP, a relay contact or a power clamp on the way in, one outbound connection on the port your browser already uses, and an open API on the way back out.

Connect any machine

Machine connectivity by protocol: OPC UA, Modbus TCP, relay and power clamp.

If it runs on power, SmartFactory can measure it; the question is which route. Every route lands in one system, in the same dashboards, charts and alerts.

  • OPC UA. Where a machine has a PLC, production data is read straight from the controller: read-only, no extra hardware, alongside existing SCADA.
  • Relay or volt-free contact. Where a machine has a spare relay or contact, a simple sensor counts every cycle, with debouncing tuned per machine so contact bounce never inflates your counts.
  • Power signature. Where a machine has nothing to connect to, a clip-on power clamp is enough: SmartFactory learns the machine’s electrical signature and counts cycles without touching the machine at all.
  • SmartFactory Node. Where a machine must never lose a count, our own DIN-rail edge device counts in hardware, survives power cuts, buffers through network outages and replays every missed reading on reconnect.
  • Modbus TCP metering. Heavy three-phase plant is metered to MID-certified, billing-grade accuracy with split-core CTs: clamped on, no rewiring, no downtime to install.
  • JSON over HTTPS. Every cycle records how it was captured, mixed estates run side by side, and an open JSON contract brings in anything else that can send data, including machines that arrived with software of their own.

What each route asks of an operator, and how a bench with no machine gets counted, is on shop floor data capture. The power-signature method is written up with the working shown in the signed field note Instrumenting a press with no OPC UA.

Site gateway

One box, one outbound connection, nothing inbound.

For whoever owns the firewall: no inbound rule, no VPN, no static IP, no exception on the plant network.

  • The gateway makes a single outbound connection on TCP 443 — the same port your browser uses. Nothing listens for the internet, and no port is forwarded to anything on your plant network.
  • Unplug the internet and the factory keeps producing: the gateway buffers locally and forwards when the link returns. You can watch the backlog drain, which is the demo worth asking for.
  • One installer with an enrolment code. Run it, paste the code, and the site is on — Windows service or Linux container, your choice.
  • A per-site health page shows what is really working: broker, meters, OPC UA sessions, printers and door events, each as its own chip with a count and a last-seen time.
  • On-premises devices are configured from the cloud through the same tunnel, so adding a meter does not mean a site visit or a laptop in a switch cupboard.
  • A gateway is optional, not a toll booth: where SmartFactory reaches your devices directly, everything works the same way without one.

API & webhooks

An open API on every plan — and webhooks that behave like a payments provider’s.

Production data that cannot get back out of the software that captured it becomes somebody’s reporting problem eighteen months later. The API is on every plan rather than the top one, because a system you cannot read from is not really yours.

  • A documented OpenAPI surface covering machines, works orders, jobs, OEE, downtime, energy and quality, with cursor pagination and ISO-8601 timestamps throughout.
  • Scoped API keys: a reporting integration gets read access to production data and nothing else. Keys are shown once, stored hashed, and revocable.
  • Rate limits are published in the response headers rather than discovered in production, and a 429 tells you when to come back.
  • Webhooks are HMAC-signed with a timestamped signature header — the same construction Stripe uses — so your receiver can verify what it is being sent.
  • Deliveries retry to a published schedule across eight attempts spanning several hours, then dead-letter. Nothing is silently dropped.
  • The delivery log shows every attempt and its response, and any dead-lettered delivery can be replayed in one click once your endpoint is back.
  • It is demonstrable: kill your receiver during the demo, watch the retries arrive on schedule, then replay the backlog from the log.
  • You choose which system is the master for stock: SmartFactory, your existing ERP fed by these webhooks, or the value landed in QuickBooks Online as period journals. Three authority modes, and the product behaves differently in each rather than pretending.

SmartFactory Intelligence

Ask your factory anything.

Add-on
  • “Why was OEE down on cell 3 last week?” — answered in seconds from your live production data, with citations you can open and check.
  • “Which downtime reason cost us the most this month?” “Show the scrap trend for part X since the tool change.” Plain questions, evidenced answers.
  • Powered by OneBrain, OneTek’s production AI layer, already running live in production.
  • Available as an add-on tier, so you only pay for it when you want it.

The platform underneath

Modern SaaS — not a twenty-year-old codebase hosted in the cloud.

“Cloud” gets claimed by a lot of manufacturing software that is really a desktop system with a browser in front of it. What it means here is specific, and it is the half of the product you never see.

  • A true multi-tenant cloud platform with strict tenant isolation, monthly releases, and unlimited users on every plan.
  • Multiple locations within your company roll up into one view while each site keeps its own boards, shifts, tariffs and users.
  • Role-based access from operators to quality managers to directors, with invite flows, PIN logins for the shop floor and Microsoft 365 single sign-on.
  • Runs on off-the-shelf hardware — standard smart meters, relays and Zebra printers — plus our own edge node where you need one. Nothing proprietary to buy back.
  • Devices connect outbound and provision themselves with per-device credentials, so there are no inbound holes in your plant network.
  • Try it before any hardware arrives: a built-in simulated factory generates a realistic production floor — live states, cycles, energy and quality data — so a trial starts on day one.

Ask us to unplug the internet.

In the demo we pull the link and you watch the backlog drain, then kill a webhook receiver and replay the deliveries from the log. Bring whoever owns the network.