In the demo the box always works: scan to join, a curve in three minutes, a phone push. The contract often says “data may be viewed only on this platform.” After warranty the vendor goes dark. The curve still lives on someone else’s cloud. Your board is empty. That is not an operations problem. The exit was welded shut at purchase.
- Ticket system asks for device status: no API / annual fee required
- HR wants access events: screenshot export only
- MES wants crew kWh: manual Excel download, field names change weekly
- Offline catch-up: no local cache, or the cache is unreadable
Closed versus open is whether it can enter your ticket
A box can collect reliably. The question is who owns the result. Closed plans usually open only their app, their wall skin and their annual plan. You need over-threshold to open a maintenance ticket, badge events into attendance, kWh into crew accounting. Those actions live in the business system, not in the vendor demo account. Compare Closed box vs. open access: which one can enter a work order. A pretty IoT wall that still cannot release numbers is almost as bad as none: A pretty IoT video wall is almost as bad as none.
If you already bought it, is there a path
Inventory first: official API, MQTT, Modbus, a read-only database account, or only CSV. Protocol without open docs is not automatically impossible. It means authorization and capture boundaries first: If the device protocol is closed, can we still integrate. When the old vendor goes dark, devices need not be scrap, but firmware and gateways must be assessed for a new system: The old vendor went dark. Can the devices still join a new system. Software need not supply hardware. Named brands are fine if the interface reaches the business layer: Must we supply the hardware, or can you name the brand.
How to buy the next box
Write into the purchase: raw-data ownership, interface list, offline cache, accounts that do not follow a salesperson. Acceptance is not a green light. Run a real ticket through event → dispatch → write-back. Why devices and the business must connect: Why companies should connect devices to business systems. DaXi Technology can add an access layer outside an existing box, or recommend a gateway change. The test is whether data enters the back office you already run—not another cloud you cannot see into. Bring platform screenshots and interface notes to the Hardware-software service page.
Annual fees and accounts are another lock
Some platforms allow export, but the right is tied to a salesperson’s demo account. When that person leaves, the password dies. The curve is still there. You cannot open it. Make the tenant the company, two people able to receive codes, API keys with operations—not on a sales laptop. That is the same asset discipline as a domain filing. Rebuild or extend the old IoT platform: Rebuild the old IoT platform, or extend it.
If paper patrols still run in parallel, a locked box and backfilled checkmarks become a double blind: a curve on screen, a tick on paper, and after an incident neither proves handling. Patrol risk: Why paper patrol checklists fail at scale. Unboxing cost should sit in the integration budget at kickoff: What hardware-software projects cost, and how long they take.
Sales may say “we open MQTT.” Open it and the topic is an encrypted payload, keys renewed yearly. Open in name, leased in fact. At acceptance, pull one over-threshold event into a ticket with your own account. If it will not come, the picture is still locked. Online devices with people still staring often stop at this layer: Devices are online. Why the floor still stares at screens.