Customer Solution Point Of View

Purpose: customer-facing position for LumenVision / OneVizion Architecture Commit. This complements the prep pack by turning the meeting analysis into a solution recommendation.

Executive View

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

The solution should not be framed as a single-system replacement. LumenVision should be positioned as the structured workflow, orchestration, planning, and visibility layer that connects existing and future authoritative systems. The architecture should explicitly preserve domain ownership in systems such as Salesforce/NEO, SOM 2.0/BlueSteel, SAP S/4HANA, GLM/3GIS, BluePlanet, BPI, WFM/SFS, Flight Deck, Data Hub, and reporting platforms.

The strongest recommendation is to approve a staged Architecture Commit: commit the target principles, Release 1 scope, system boundaries, integration contracts, migration approach, and value case now; defer broad claims that LumenVision will immediately become the universal source of truth or that AI will autonomously execute operational decisions.

What I Understand From Lumen

Lumen wants a more unified way to manage network implementation work across planning, service delivery, construction, grooms, order management, SiteTracker/Netbuild/Armor exits, field execution, reporting, and future AI-assisted operations.

The current pain is not only tool fragmentation. It is that teams need consistent object definitions, workflow states, milestones, dates, ownership rules, and integration behavior across many systems. Without that foundation, users may still have duplicate tasks, conflicting dates, inconsistent dashboards, and manual follow-up even after a new work surface is introduced.

The workshop action items confirm the immediate priorities:

• 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.
• Decide which follow-up items need owners and near-term closure.

Recommended Solution Position

LumenVision / OneVizion should be the orchestration and work management layer for agreed network implementation workflows. It should coordinate work, expose tasks and milestones, make dependencies visible, manage workflow state where assigned, and provide a consistent operational experience.

It should not automatically own every business object. Product order, service order, inventory, material master, capital/funding, field dispatch, reporting, and network design domains should keep clear authoritative owners. LumenVision can still orchestrate across them through APIs, Kafka/CFKA events, embedded views, context packages, and controlled write-back patterns.

The Architecture Commit should approve a bounded target architecture:

• LumenVision as the Release 1 workflow/orchestration surface.
• Object-level system-of-record decisions.
• Kafka/CFKA as the event, traceability, replay, and exception-handling backbone.
• Integration contracts for the Release 1 systems.
• SiteTracker/Netbuild/Armor migration principles.
• Service Delivery and Network Grooms scope decisions.
• Human-supervised AI/ADO until data lineage, auditability, rollback, replay, and guardrails are proven.

Proposed Target Architecture

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\nHuman-Supervised Recommendations"]
    end

    subgraph DomainSystems["Authoritative Domain Systems"]
        BPI["BPI\nNetwork Order / Design"]
        BP["BluePlanet / VoltRon\nInventory Direction"]
        GIS["GLM / 3GIS\nSite, Route, Survey"]
        SAP["SAP S/4HANA\nBOM, Materials, Capital"]
        WFM["WFM / SFS / Flight Deck\nField Execution"]
    end

    subgraph DataLayer["Integration / Data / Reporting"]
        KAFKA["Kafka / CFKA\nEvents, Headers, Replay, DLQ"]
        HUB["Data Hub\nRead-Side Stitched View"]
        RPT["INID / Dashboards\nOperational 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

This diagram shows the core principle: 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. Data Hub and reporting consume the integrated state. AI/ADO uses trusted workflow and event data but stays human-supervised until governance is mature.

Phased Roadmap

Architecture Commit Artifact Set

For Lumen's Concept and Architecture Commit, I recommend preparing these artifacts:

1. Concept submission: business problem, target outcome, in-scope workflows, out-of-scope items, dependencies, and decision request.
2. Value/business case: reduced manual coordination, fewer duplicate task updates, improved milestone visibility, cleaner exit path for legacy tools, better reporting consistency, and foundation for AI/ADO.
3. Target context diagram: LumenVision, OneVizion, existing Lumen systems, integration layer, reporting, and AI/ADO.
4. Object ownership matrix: project, order, service order, network order, task, milestone, date, site, route, BOM, permit, inventory, status, and document ownership.
5. Integration inventory: source, target, object, trigger, pattern, frequency, owner, error handling, and Release 1 status.
6. Release roadmap: Service Delivery, SiteTracker exit, Network Grooms, SOM/BlueSteel, SAP, BluePlanet, WFM/SFS, and AI/ADO sequencing.
7. Risk and mitigation plan: scope, data quality, ownership ambiguity, migration/cutover, test environments, reporting mismatch, and operational adoption.

Decision Questions For Customer

Ask these questions in the Architecture Commit discussion:

1. Is the approval request for 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?
5. Is SiteTracker exit primarily deadline-driven migration, target-state transformation, or both?
6. What value statements will be accepted as enough for STEPn resource approval?
7. What production-readiness evidence is required: UAT, rollback, replay, observability, support model, or security review?

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. That discipline will let Lumen and OneVizion move faster because each system boundary, migration step, and business value statement will be clear enough for funding, solutioning, and development.”

Bottom Line

The existing documentation is enough for internal understanding and discussion preparation. For a customer presentation, this POV should be the lead document because it converts the analysis into a solution recommendation. Use it together with the prep pack, Q&A diagram, system-of-record matrix, integration inventory, and slide outline.