Why this decision matters
Loss of a remote feature should not be confused with proof that every local function has failed.
Work through the actual task
- Compare outage behaviour before and after migration.
- Test the supported local and remote functions under the agreed procedure.
- Write down the expected behaviour during a connection loss and the way the system reports it.
Worked example
The new system removes an old communications path. This is a hypothetical example, not a completed customer installation.
The useful evidence at the end of this example is: A dependency record showing the effect of the removed path.
Limits and follow-up
A new panel or recorder may change app access and ongoing costs. Include user migration, account ownership and demonstrations in the quotation.
If the relevant check cannot be completed, record what remains uncertain and who will resolve it before work or sign-off proceeds.
Sources and equipment references
Checked for the product, supplier or information details used here. Exact procedures depend on the installed model; these links are not a substitute for its instructions.