Parent folderOpen Confluence

RWS Architecture article

Edge Management

Edge Management is the product-neutral architecture building block for management and lifecycle control for distributed edge locations. It states what DC 3.0 needs from this capabi

  1. Typeabb
  2. Statuscandidate
  3. Domaindc30
On this page
  1. ABB Edge Management
  2. Summary
  3. Capabilities
  4. Constraints
  5. Service Description
  6. Roadmaps
  7. Landing Zones
  8. Interfaces
  9. Dependencies
  10. EIRA Alignment
  11. Available SBB's

ABB Edge Management

Summary

Edge Management is the product-neutral architecture building block for management and lifecycle control for distributed edge locations. It states what DC 3.0 needs from this capability before a concrete SBB, product, or operating model is selected.

Capabilities

  • Provides management and lifecycle control for distributed edge locations.
  • Defines the functional, technical, security, and quality expectations that SBBs must satisfy.
  • Keeps service ownership, interfaces, and consumption boundaries visible before product selection.
  • Enables traceability from architecture intent to implementation, operational evidence, and consuming services.

Constraints

  • The resulting SBB must fit the datacenters ownership model and document the support, lifecycle, and service-management boundary.
  • Security, privacy, logging, evidence, and compliance controls must be explicit enough to assess BIO2-aligned implementation where applicable.
  • Management flows must tolerate constrained links and disconnected operation where required.
  • SBBs must provide clear ownership for remote hands, lifecycle, and incident response.

Service Description

This ABB offers an edge-management service that keeps distributed edge nodes inventoried, configured, patched, monitored, and governed. It is consumed by solution architects, platform teams, and service owners as the capability contract for selecting and shaping SBBs.

The service description remains implementation-neutral: product selection, hosting pattern, detailed runbooks, and service levels belong in the mapped SBB and related ADRs.

Roadmaps

  • Baseline: confirm scope, service ownership, constraints, and acceptance criteria for Edge Management.
  • MVP: identify candidate SBBs and connect them to the service, support, and lifecycle model.
  • Next: add measurable service levels, evidence requirements, and roadmap dependencies once the SBB is selected.

Landing Zones

  • Private cloud landing zone in ODC-Amsterdam, following the RWS ICT Strategy 2025-2030 private-cloud direction.
  • Edge or Micro Edge landing zones for distributed operation close to the operational location.
  • Government cloud or external cloud landing zones only when the SBB documents the required control set, connectivity model, and data classification fit.

Interfaces

  • Fleet and device management APIs.
  • Telemetry, policy, and update-distribution interfaces.
  • Secure remote access interfaces.

Dependencies

  • Depends on edge for a supporting capability or integration boundary.
  • Depends on automation for a supporting capability or integration boundary.
  • Depends on fleet-management for a supporting capability or integration boundary.
  • No implementing SBB is mapped yet; candidate SBB selection is a dependency for further elaboration.
  • Consuming ABB and SBB dependencies must be recorded as links when solution design identifies concrete upstream or downstream use.

EIRA Alignment

Available SBB's

  • No SBB is available yet. Candidate selection must be completed before this ABB can be promoted beyond capability intent.