Plant floor workloads need cloud connectivity that does not blink

TOGAF-style gap framing — what we typically see today, and what the proposed end state looks like. The gap between them is the engagement.

Each decision is offered as explicit options with trade-offs — Hohpe's “selling options” principle. A safe default is noted where one exists.

1. Decision 1.ExpressRoute Premium add-on for Microsoft 365 connectivity — yes or no

   Premium add-on

   When it fitsHeavy M365 usage from connected plants; latency SLA on Teams or SharePoint matters.

   Trade-offsSignificant additional cost.

   Standard (default)

   When it fitsM365 routed via public internet break-out; latency tolerated.

   Trade-offsNo accelerated path for M365.

   Default recommendationStandard. Premium is the exception, not the default.

2. Decision 2.Arc scope — all plant servers vs critical workloads only

   All plant servers

   When it fitsCentralised governance is the goal; operational team prepared.

   Trade-offsInitial onboarding workload; agent management at scale.

   Critical workloads only

   When it fitsPilot phase or limited platform team capacity.

   Trade-offsTwo governance planes during transition.

   Default recommendationStart with critical workloads in pilot; expand to all plant servers within 6 months.

3. Decision 3.Carrier circuit — existing telco or new procurement

   Existing telco

   When it fitsExisting WAN contract has good terms; existing relationship.

   Trade-offsTied to existing terms; less competitive pricing.

   New procurement

   When it fitsWAN contract due for renewal; better terms achievable.

   Trade-offsProcurement timeline often dominates project schedule.

   Default recommendationExisting telco if relationship is functional; new only at natural renewal point.

Recommended cards

The SKUs and capabilities most likely to be part of the solution, with the editorial rationale for each in the context of this story. Add the ones that fit your situation.