Definition
Edge computing processes data locally, at or near the equipment generating it (a controller or gateway physically close to the machine) rather than sending raw data to a remote cloud server for processing first. This reduces latency for time-critical decisions and can maintain function even if network connectivity to a remote system is temporarily lost.
Key facts
- Processing happens locally, physically near the equipment, unlike cloud computing's remote processing.
- Reduces latency for time-critical decisions, since data does not need a round trip to a remote server.
- Can maintain local function during network connectivity loss, unlike a system entirely dependent on cloud processing.
- Often used for time-critical filtering or pre-processing before sending a reduced, relevant subset of data onward to the cloud.
How does Edge computing work in maintenance?
Edge computing works by placing processing capability physically close to the equipment (on a local controller, gateway, or dedicated edge device) so time-sensitive decisions can be made immediately using local data, without waiting for a round trip to a remote server, and while still functioning if network connectivity is temporarily unavailable.
What does Edge computing require?
Cloud computing centralizes processing on remote, provider-managed servers, offering scalability but introducing network dependency and latency. Edge computing trades some of that scalability for immediacy and resilience, processing data where it is generated: the two are frequently combined, with edge handling time-critical local decisions and cloud handling broader analytics and long-term storage.
FAQ
Frequently asked questions
What processing happens close to the equipment?
Edge computing: processing data locally, near the equipment that generates it, rather than sending it to a remote cloud server first, reducing latency and maintaining function during connectivity loss.
Last reviewed: