Keep working when the network does not.
ArcHorizon is built around locally retained incident data. The desktop client can work with its local store and connect to a LAN server or cloud service when either is reachable.
Local first, with routes to shared data.
The client checks available connection paths and keeps local incident records available when it cannot reach a server.
At a connected command post, a local server gives clients a nearby shared path for incident data.
When the local server is unavailable and internet connectivity exists, the client can use the cloud connection.
If neither path is available, the client continues with data retained on the device. The LAN server can also synchronize with the cloud.
Design for intermittent connectivity.
An incident may move between a command post network, a remote connection, and no connection at all. The application treats that as a normal operating condition.
- Data on the clientThe desktop client retains a local incident database in its data directory, including records needed for work away from a server.
- Shared paths when availableA LAN server provides a local shared path at the command post; a cloud endpoint provides a remote path when internet access is available.
- SynchronizationLocally recorded work can be reconciled with shared data after a connection returns; a LAN server can synchronize onward to the cloud.
- External servicesLive weather, external map layers, and other remote feeds require a connection unless the relevant material has been stored locally.
See the workspace.
Return to the full incident picture.
Connection status and synchronization matter because teams need to know which information is local and what has reached the shared record.
Explore all features →