Delivery model 05 · Portfolio plan

Six-month delivery and pilot decision plan

A delivery proposal covering investment scope, technical boundaries, accountable teams, material risks and the evidence required before market expansion.

Recommended decision

Fund a controlled technical and care-operations pilot

Build evidence for a narrow set of frequent, diagnosable failures before expanding automation or adding markets.

Duration: 6 months
Initial cohort: 10,000–50,000 managed homes in one launch market
Failure-mode scope: Three failure modes: weak mesh backhaul, poor client association and upload congestion
Scale condition: Proceed only when telemetry, diagnosis, action safety and support outcomes pass their gates

Execution sequence

Each month closes with evidence, not activity

Dependencies move from data contracts to technical control, operational adoption and an explicit investment decision.

Contracts and baselines

Agree the service outcome, target failure modes and CPE signal contract.

Exit evidenceApproved telemetry schema, baseline measures, accountable owners and pilot cohort definition.

CPE integration

Connect router and mesh telemetry to a canonical household state.

Exit evidence≥95% critical-signal completeness across selected CPE profiles.

Diagnosis validation

Validate fault isolation against labeled incidents and counterfactual cases.

Exit evidenceTop failure modes exceed the agreed precision threshold with reviewed false positives.

Controlled action

Expose low-risk commands with independent eligibility, audit and rollback.

Exit evidenceFailure-injection tests show no material customer harm and complete command traceability.

Care workflow

Integrate evidence, next-best action and escalation into support operations.

Exit evidenceCare-agent acceptance, customer wording approval and operational runbook sign-off.

Pilot decision

Assess recovery, repeat contact, safety, economics and country readiness.

Exit evidenceSteering decision to stop, iterate or expand with a named owner for every open risk.

System boundaries

Seven layers with an explicit product purpose

The pilot reuses device-management and data capabilities; it does not create a second broadband operations stack.

Home CPE

Router OS Agent · Mesh Node Agent · Client Device Telemetry · Local Health Check Agent

4 capabilities

Device Management

TR-369 / USP Controller Emulator · OpenSync-style Telemetry Adapter · Remote Command Gateway · Firmware Cohort Controller

4 capabilities

Ingestion

Telemetry Ingestion API · AWS IoT Core / Kinesis Equivalent · Schema Validation Service · Event Normalization Service · Telemetry Contract Registry

5 capabilities

Processing

Stream Processor · Experience Score Engine · Root Cause Rules Engine · Anomaly Detection Service · Remediation Policy Engine · Verification Engine

6 capabilities

Data

Time-Series Store · Postgres Operational Store · Topology Graph Store · Object Storage for Logs · Cache / Session Store

5 capabilities

Experience

Incident Review · Support Agent Console · Customer Message Output · Network Ops View · Delivery Plan

5 capabilities

Business

Care Outcome Join · Customer Outcome Join · Portfolio Performance View

3 capabilities

Decision rights

Accountability by function

ProductOutcome, failure-mode priority, action policy and scale recommendation

Router / MeshSignal quality, topology behavior and safe device control surfaces

Cloud / DataIngestion, diagnosis, verification, audit and service reliability

Care OperationsAgent workflow, escalation policy and customer communication

Security / PrivacyData minimization, identity, command authorization and retention

Country TeamCPE mix, localization, economics and operational launch readiness

Economics

Stage-appropriate cost envelope

Reference implementation€0–€100 / month

Deterministic household fixtures, Vercel app and typed local data.

Technical PoC€500–€3,000 / month

1k–10k synthetic households, cloud ingestion, time-series storage and observability.

Operator Pilot€5k–€30k+ / month

10k–50k real homes, real CPE telemetry, controlled commands and support integration.

Pilot assumption€5k–€30k+ monthly platform run cost, excluding internal delivery capacity

Scale gates

Evidence required before broader rollout

A failed gate produces a stop or remediation decision; it is not converted into a softer success measure.

Telemetry quality validated

≥95% completeness for critical signals across target CPE profiles.

Owner: Platform + Firmware
Evidence: Contract conformance and missing-signal report.

Reference contract defined

RCA confidence above 80%

Top five failure modes exceed 80% precision/confidence on labeled cases.

Owner: Data / RCA
Evidence: Confusion matrix and false-action review.

Reference logic demonstrated

Self-healing above 60%

Low-risk actions resolve >60% of eligible incidents without harm.

Owner: Product + Firmware
Evidence: Controlled action success and rollback rate.

Pilot evidence required

Verification proves improvement

Post-action score and symptom metrics improve beyond minimum delta.

Owner: RCA + Platform
Evidence: Before/after verification contracts.

Reference verification demonstrated

Support workflow accepted

Care operations accept next-best action, escalation and customer wording.

Owner: Support Operations
Evidence: Agent usability and policy sign-off.

Operations review

Pilot architecture approved

Security, cost, SLO, country and operational controls are funded.

Owner: Steering Group
Evidence: Pilot readiness and cost model.

Decision pending

Material risks

Named mitigations and accountable owners

Risk	Consequence	Mitigation	Owner
CPE signal inconsistency	Diagnosis quality varies by vendor and firmware cohort.	Versioned canonical contract, conformance tests and minimum-signal eligibility.	Firmware + Platform
False or unsafe action	Remote intervention can worsen an active customer session.	Separate diagnosis from action authority; use allowlists, guardrails, rollback and audit.	Product + Security
Benefits cannot be attributed	Natural recovery is mistaken for product impact.	Controlled cohorts, pre/post windows and repeat-contact measures with finance review.	Analytics + Finance
Country operating mismatch	Device mix, care process or privacy controls prevent reuse.	Launch-market readiness assessment and explicit localization package.	Country rollout