Install year
The vendor arrived, accounts opened, devices entered their cloud. Contracts often omit data export and a local protocol. Hardware may be a named brand; software can only watch their wall.
What parks fear is not old hardware. It is a cloud that expired, a person who cannot be found, an app that still bills yearly and will not log in. “Replace everything” from the boss usually arrives with no budget and no downtime window. DaXi Technology first draws the dark timeline: when it became read-only, whose phone holds the keys, whether the controller’s local port still opens.
Cloud expired or was subcontracted
Renewal cannot find the original salesperson, the platform reskinned, historic curves will not download. Lamps still blink; the business side is already blind.
The old vendor went dark
Dead phone, company dissolved, implementer left. Keys, certs and Modbus maps may live in one person’s chat history.
Access assess
If you can read locally, side-path in. If only the vendor cloud, negotiate export or walk away. If the protocol is fully closed, replace in batches—do not fantasize that software will wake it.
Can join
Serial/Ethernet docs, or a standard frame you can capture. An edge gateway can translate into the new system.
Serial/Ethernet docs, or a standard frame you can capture. An edge gateway can translate into the new system.
Limited
Read status, cannot write; face gallery will not download. Keep watch first; control on another path.
Read status, cannot write; face gallery will not download. Keep watch first; control on another path.
Replace
No protocol, no account, a chip bound to the cloud. Keeping it only buys another year of an invisible cloud.
No protocol, no account, a chip bound to the cloud. Keeping it only buys another year of an invisible cloud.
DaXi Technology need not supply the hardware. You can name the brand, but the interface must reach the business layer: Must we supply the hardware, or can you name the brand. A closed protocol still leaves side-path, replace, or read-only: If the device protocol is closed, can we still integrate. Whether the whole platform extends or rips is a different question from whether one device can join: Rebuild the old IoT platform, or extend it.
Salvage what you can still read, then talk replace
Bring to site: nameplates, wiring, vendor-cloud shots, contract annexes, whether a debug port exists. If you can reach the controller locally, do not rip first. Many gates and meters speak a standard protocol boxed into a closed app. Closed box vs. open access: Closed box vs. open access: which one can enter a work order. If you cannot salvage a frame, write a replace list by risk: safety interlocks and access first; decorative sensors can wait.
An account on one phone and an OTP only one person can receive is the next dark already scheduled. Move it to the company first. Some “dark” is unpaid cloud; paying to export raw records makes the new system’s reconcile easier. Photograph wiring before you rip; a ten-year terminal strip beats a verbal map. Replace also needs a parallel window: the new system must eat old points before paper or the old app can die. DaXi Technology will not promise every old device can be saved. We will write can-join / limited / replace into a sign-off inventory. Send the dark-device list to Hardware-Software Integration, and say whether you first need to keep access, patrols or energy.
The firmware channel and the parallel window decide how long a side-path lives
Whether a firmware channel still exists decides how long a side-path lives. If private firmware can still be pushed after dark, replace is often wiser than another bet. The inventory needs photos, terminal numbers, and whether it is live-testable. An Excel model list meets a machine already swapped. In parallel, old app read-only, new system writable, so two lists do not scramble rights.