Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:e:edge_environment [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:e:edge_environment [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Edge Environment ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | An Edge Environment is an [[public: | ||
| + | |||
| + | An Edge Environment may operate near: | ||
| + | |||
| + | * Sensors | ||
| + | * Industrial equipment | ||
| + | * Vehicles | ||
| + | * Communication infrastructure | ||
| + | * Users | ||
| + | * Facilities | ||
| + | * Data sources | ||
| + | * Operational processes | ||
| + | * Remote locations | ||
| + | |||
| + | An Edge Environment may have: | ||
| + | |||
| + | * Limited computing capacity | ||
| + | * Limited storage capacity | ||
| + | * Limited network bandwidth | ||
| + | * Intermittent connectivity | ||
| + | * Restricted external connectivity | ||
| + | * Location-specific security controls | ||
| + | * Local operational authority | ||
| + | * Low-latency processing requirements | ||
| + | * Environmental or physical constraints | ||
| + | |||
| + | An Edge Environment differs from a central Infrastructure Environment: | ||
| + | |||
| + | * An Edge Environment places computing capability near a relevant data source, consumer, process, or physical location | ||
| + | * A central Infrastructure Environment consolidates computing capability within a centralized facility or service | ||
| + | |||
| + | An Edge Environment differs from an [[public: | ||
| + | |||
| + | * An Edge Environment is distinguished by its location and operational relationship to another subject | ||
| + | * An Air-Gapped Environment is distinguished by controlled network isolation | ||
| + | |||
| + | An Edge Environment may be connected, disconnected, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | An Edge Environment does not by itself establish: | ||
| + | |||
| + | * Disconnected operation | ||
| + | * Network isolation | ||
| + | * Limited resource capacity | ||
| + | * A particular physical distance | ||
| + | * A particular device class | ||
| + | * A particular provider | ||
| + | * A particular deployment technology | ||
| + | * A particular security classification | ||
| + | |||
| + | The applicable architecture identifies the reason the environment qualifies as an Edge Environment. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | An Infrastructure Environment located within a manufacturing facility processes equipment telemetry locally to reduce latency and continued dependence on a remote cloud service. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||