Static HTML Share Page

LumenVision / OneVizion Architecture Commit

A browser-friendly briefing for colleagues who need the project context, customer-facing recommendation, architecture diagram, and supporting documents without opening Markdown files in a separate app.

Start Reading Open Full POV Visual Evidence Index

Executive View

Lumen is using Architecture Commit to decide whether LumenVision, delivered with OneVizion, can move from concept into funded solutioning and development. The formal path is concept -> architecture commit -> development, with the next major decision window around mid-August.

What Lumen Needs

A more unified way to manage network implementation across planning, service delivery, construction, grooms, order management, legacy-tool exits, field execution, reporting, and future AI-assisted operations.

Recommended Position

Position LumenVision / OneVizion as the structured workflow and orchestration layer, while preserving clear source-of-truth ownership in existing domain systems.

Commit Carefully

Approve target principles, Release 1 scope, system boundaries, integration contracts, migration approach, and value case. Avoid broad claims that one tool owns every object immediately.

Recommended Reading Order

This is the order I recommend for a colleague who is new to the project. It is not just alphabetical and not just raw video order. It starts with the customer story, then explains the architecture, then uses the videos as evidence, and only then goes into appendices.

Start With The Customer Solution POV

Use this to understand the recommendation and how to talk to Lumen.

Open Customer Solution POV

Review The Architecture Diagram And Q&A

Use this to understand the target system shape and likely customer questions.

Open Q&A And Diagram

Read The Architecture Commit Prep Pack

Use this for the decision matrix, risks, talking points, and commit scope.

Open Prep Pack

Use The Videos As Evidence In Meeting Order

After the concept is clear, follow the session sequence below to see where the ideas came from.

Open Video Diagrams

Go To Appendices Only When Needed

Use the system matrix and integration inventory when someone asks about ownership or interfaces.

Open System Matrix   |   Open Integration Inventory

Video Evidence Order

Yes: the evidence section follows the meeting/video sequence. The recommended reading path above comes first because it is easier to understand the solution before reviewing every meeting artifact.

Order Meeting / Video Why It Matters
Video 1 Lumen, June 30, 2026 Introduces target ecosystem, planning request, inventory consolidation, source-of-truth concerns, and construction/project execution patterns.
Video 2 Alignment Lumen 2, June 30, 2026 Shows network-initiated order management, workflow journeys, red/green ecosystem transition, BPI, Flight Deck, ByFrost, and reporting assumptions.
Video 3 Lumen alignment 3, July 1, 2026 Explains OneVizion roadmap, AI/ADO direction, trusted data foundation, Kafka/CFKA requirements, and governance boundaries.
Video 4 Lumen alignment 4, July 1, 2026 Demonstrates OneVizion platform capabilities: tasks, dashboards, comments, documents, roles, templates, and AI/forecasting concepts.
Video 5 Lumen Alignment 5, July 1, 2026 Frames the transformation roadmap, standard terminology, SAP, BluePlanet, GLM/3GIS, WFM, Salesforce/NEO, and two-step transformation.
Video 5.2 Lumen 5.2, July 2, 2026 Details big work areas: Custom Networks, BAU, FT3, LTO PMO, integrations, SiteTracker exit, Kafka 2.0, and project phasing.
Video 6 Lumen alignment vid 6, July 2, 2026 Focuses on delivery governance: testing, UAT, integration expertise, terminology, backlog cleanup, scope control, and readiness.

Immediate Lumen Action Items

  • Decide relative priority and path forward for the Service Delivery module.
  • Decide SiteTracker exit priority, timing, and risk.
  • Finalize roadmap and target execution plan.
  • Prepare content for Concept and Architecture Commit.
  • Define system flow for Network Grooms and next steps.
  • Prioritize follow-up items with clear owners.

Recommended Target Architecture

The diagram below shows the core recommendation: LumenVision becomes the work surface and orchestration layer, while source-of-truth ownership remains distributed by domain. Kafka/CFKA connects state changes and supports traceability, replay, and exception handling. 

flowchart LR
    subgraph Intake["Demand / Order Intake"]
        SF["Salesforce / NEO"]
        SOM["SOM 2.0 / BlueSteel"]
        EXT["Partner / Portal / API"]
    end

    subgraph WorkSurface["LumenVision / OneVizion"]
        LV["Workflow, Planning, Task Visibility"]
        ADO["AI / ADO
Human-Supervised Recommendations"]
    end

    subgraph DomainSystems["Authoritative Domain Systems"]
        BPI["BPI
Network Order / Design"]
        BP["BluePlanet / VoltRon
Inventory Direction"]
        GIS["GLM / 3GIS
Site, Route, Survey"]
        SAP["SAP S/4HANA
BOM, Materials, Capital"]
        WFM["WFM / SFS / Flight Deck
Field Execution"]
    end

    subgraph DataLayer["Integration / Data / Reporting"]
        KAFKA["Kafka / CFKA
Events, Headers, Replay, DLQ"]
        HUB["Data Hub
Read-Side Stitched View"]
        RPT["INID / Dashboards
Operational Reporting"]
    end

    EXT --> SF
    SF --> SOM
    SOM --> KAFKA
    KAFKA --> LV
    LV --> BPI
    LV --> WFM
    LV --> SAP
    BPI --> KAFKA
    BP --> KAFKA
    GIS --> KAFKA
    SAP --> KAFKA
    WFM --> KAFKA
    KAFKA --> HUB
    HUB --> LV
    HUB --> RPT
    LV --> ADO
    KAFKA --> ADO
    ADO --> LV

Phased Roadmap

Phase Focus Recommendation
Phase 0 Commit readiness Finalize value statements, context diagram, object ownership matrix, integration inventory, Release 1 scope, and business case.
Phase 1 Foundation release Implement priority workflows with clear object ownership, Kafka/CFKA traceability, task/status sync, and reporting reconciliation.
Phase 2 Migration and exits Use a hybrid approach for SiteTracker, Netbuild, Armor, and Flight Deck/WFMT: deadline-safe migration first, deeper transformation second.
Phase 3 Domain integration depth Expand SAP, BluePlanet, GLM/3GIS, and WFM/SFS write-back only where ownership and rollback/replay behavior are agreed.
Phase 4 AI-assisted operations Start with recommendations, exception handling, and next-best-action support. Move to automation only after governance is proven.

Customer Questions

  1. Is the approval request a full architecture submission or a partial concept-to-architecture gate?
  2. Which workflow must be the Release 1 anchor: Service Delivery, SiteTracker exit, Network Grooms, RNI, Waves/Dark Fiber, or another priority?
  3. Which systems must remain authoritative for order, inventory, materials, field task, date, and reporting state?
  4. What minimum integration set is required to prove value by the mid-August decision window?
  1. Is SiteTracker exit primarily deadline-driven migration, target-state transformation, or both?
  2. What value statements will be accepted as enough for STEPn resource approval?
  3. What production-readiness evidence is required: UAT, rollback, replay, observability, support model, or security review?

Detailed Documents

These links open directly as browser-friendly HTML pages in the same folder or GitHub repository. The Source notes remain in the repo, but colleagues can stay entirely in HTML from this page.

1. Customer Solution Point Of View Start here. This is the customer-ready recommendation and main story. 2. Q&A And Diagram Read second. This explains the architecture and prepares likely questions. 3. Architecture Commit Prep Pack Read third. This contains the decision matrix, risks, and commit scope. 4. Video Diagrams And Explanations Use fourth as evidence. This shows the actual meeting diagrams with explanations. 6a. Raw Visual Frame Index Use as backup when you need every extracted screenshot by timestamp. 5. System-Of-Record Matrix Appendix for ownership questions: which system owns which object. 6. Integration Inventory Appendix for interface questions: source, target, pattern, and priority. 7. Slide Outline Use last when preparing the actual presentation deck.

Language Packages

Suggested Customer Message

“Our recommendation is to move forward with LumenVision as the structured workflow and orchestration layer, but to make the Architecture Commit precise. We should approve the target architecture principles, Release 1 scope, object ownership, integration contracts, roadmap, and value case. We should not make a blanket source-of-truth claim for every object.”