Parent folderOpen Confluence

RWS Architecture article

Micro Edge

Micro Edge is the product-neutral architecture building block for small-footprint edge execution for constrained locations. It states what DC 3.0 needs from this capability before

  1. Typeabb
  2. Statuscandidate
  3. Domaindc30
On this page
  1. ABB Micro Edge
  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 Micro Edge

Summary

Micro Edge is the product-neutral architecture building block for small-footprint edge execution for constrained locations. It states what DC 3.0 needs from this capability before a concrete SBB, product, or operating model is selected.

Capabilities

  • Provides small-footprint edge execution for constrained 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.
  • Micro Edge patterns must define the minimum viable management, security, and observability baseline.
  • Solutions must not assume the same capacity or redundancy profile as central DC 3.0 platforms.

Service Description

This ABB offers a micro-edge service for running a minimal, governed subset of DC 3.0 capabilities in space, connectivity, or support-constrained environments. 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 Micro Edge.
  • 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 and central DC 3.0 landing zone for core infrastructure and platform services.
  • 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

  • Local workload and management interfaces.
  • Intermittent central synchronization and telemetry interfaces.
  • Secure identity and update interfaces.

Dependencies

  • Depends on edge for a supporting capability or integration boundary.
  • Depends on edge-management 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.