“Closed” is often one refusal. The floor is layered: a physical port with no register map; a heartbeat with no event; a cloud API with an annual fee. Can vs. cannot depends on which layer you will stop at.
Sketch: every layer can be “up.” Only events into the business layer make a loop.
Three common paths that still work
One: negotiate rights—official API, read-only store, register map. Two: add an open gateway—devices keep collecting, the exit moves to a topic you control. Three: change the edge or the model; you can still name the brand: Must we supply the hardware, or can you name the brand. If you already bought a closed box, inventory the exit first: When a closed IoT box will not release your data. If the old vendor went dark, ask whether firmware can be re-homed: The old vendor went dark. Can the devices still join a new system.
Do not replace a protocol with a crack
Packet capture, reverse work, bypassed rights: lights go on short-term. They will not pass audit, upgrade or legal risk. Safety wants records they can verify: What device records must prove in a safety audit. DaXi Technology only integrates inside an authorized boundary. If rights cannot be negotiated, we will say you stop at watch-only, or we will recommend a swap.
Accept at the event layer—not “it can ping”
The integration list should include: one real exception that opens a ticket, one rights change that ships, one offline catch-up. Connected is only step one: Why companies should connect devices to business systems. Cycle stretches with protocol: What hardware-software projects cost, and how long they take. To judge whether the protocol you have can reach the business layer, go to the Hardware-software service page with interface notes or a vendor refusal; compare Closed box vs. open access: which one can enter a work order.
No document does not mean no port
RS485 on a panel, DL/T645 on a meter, Wiegand on a gate—the physical layer is often there. The stall is a private application frame, or a cloud that only emits reports. Inventory five columns: wire / port / docs / events / write. That beats one “closed.” Read-without-write cannot kill access in minutes; write-list-without-events leaves an audit with no trail.
An SDK that is only a Windows demo client, with no server API, is half-closed: you can cast a picture to the duty room and still never enter a ticket. The camera-wall problem repeats at protocol: Cameras without work orders are not software. DaXi Technology will write which layer you stop at and what rights the next layer still needs, so the project does not idle on “try a crack.” Offline catch-up also depends on an edge protocol: Sites that drop offline: how collection should be designed.
After you open to the event layer, write ability is a separate assess. Read temp but not reset, read swipe but not revoke—the business is still half missing. Instant access-death depends on write: Access control tied to HR: access dies when employment does. If industrial points can only watch and cannot stop on a rule, the safety loop fails too. On the line: How line energy enters tickets and MES.