System Of Record Matrix
Purpose: working architecture artifact for the Lumen Architecture Commit. This matrix captures likely ownership, open questions, and integration implications based on the meeting notes and video diagrams.
Companion artifact: integration-inventory.html.
Legend:
- **Confirmed**: explicitly stated or strongly visible in meeting notes/diagrams.
- **Likely**: inferred from diagrams/discussion, should be validated.
- **Open**: unresolved or needs architecture decision.
Object Ownership Matrix
| Object / Data Domain | Create Owner | Update Owner | Read / Consumer View | Lifecycle / State Owner | Confidence | Architecture Notes |
|---|---|---|---|---|---|---|
| Product Order | Salesforce / NEO | Salesforce / NEO | Data Hub, Lumen Vision, SOM/BlueSteel consumers | Salesforce / NEO with SOM involvement | Confirmed | Session 1 states Salesforce is source of truth for product orders. Data Hub is stitched read view, not update authority. |
| Product Instance | Salesforce / product stack | Salesforce / product stack | Data Hub | Product stack / Salesforce | Likely | Session 1 references product order and product instance as Data Hub domains. Needs lifecycle definition. |
| Service Order | SOM 2.0 / BlueSteel | SOM 2.0 / BlueSteel | Lumen Vision, Data Hub, Order Management, Service Delivery | SOM 2.0 / BlueSteel | Likely | Roadmap shows BlueSteel order management unlocking service order workflow, work plan generation, and date publishing. |
| Service Instance | SOM / service platforms | Service platforms / activation systems | Data Hub, diagnostics, Lumen Vision | Service platform | Open | Mentioned in Northstar decomposition. Need exact owner by service type. |
| Network Order | BPI / BluePlanet-related network order flow | BPI / network implementation systems | Lumen Vision, ByFrost, analytics | BPI / Network Implementation | Likely | Session 2 target sketch shows BPI Network Order in design. Future-state says LV may initiate network orders in BPI/BluePlanet. |
| Planning Request / Network Opportunity | Lumen Vision | Lumen Vision with Planning teams | Lumen Vision, downstream design/integration systems | Lumen Vision / Planning | Likely | Session 1 diagram shows LumenVision planning request. Session 5.2 renames planning request to network opportunity. |
| Project | Lumen Vision | Lumen Vision / project teams | Lumen Vision, dashboards, analytics | Lumen Vision | Likely | Session 4 demo shows project metadata and project/task views. SiteTracker migration may move net-new projects into LV. |
| Program / Portfolio | Lumen Vision / PMO | PMO / Lumen Vision | Dashboards, leadership reports | PMO / Lumen Vision | Open | Session 2 discusses program-level dependencies and rollups. Need reporting/portfolio authority decision. |
| Work Plan | Lumen Vision | Lumen Vision / workflow engine | Lumen Vision, ByFrost, field/work systems | Lumen Vision or workflow engine | Likely | Session 5 says work plan definitions must be standardized. Session 2 shows LV workflow across execution. |
| Service Delivery Work Plan | BlueSteel/SOM + Lumen Vision | Service Delivery / Lumen Vision | Lumen Vision, Service Delivery, reporting | Open | Open | Session 5 distinguishes service delivery work plan vs network build work plan. Ownership not settled. |
| Network Build Work Plan | BPI / Netbuild / Project Helix transition | Network Implementation / Lumen Vision | Lumen Vision, ByFrost, INID/reporting | Open | Open | Project Helix will change this boundary. Need Release 1 versus target state. |
| Task | Lumen Vision and/or Flight Deck / WFM by task type | Assigned task system / user | Lumen Vision, Flight Deck, ByFrost, WFM | Open | Open | Session 2 decision point says task presentation platforms are LV + FD. Session 4 shows LV task fields. Need task lifecycle owner. |
| Task Status | Executing task system | Executing task system or LV if native | Lumen Vision dashboards / Data Hub / reporting | Open | Open | Must decide whether status write-back is bidirectional or LV-authoritative for some tasks. |
| Work Group / Role Assignment | Template / Lumen Vision | Lumen Vision with manual override | Lumen Vision, work queues | Lumen Vision | Likely | Session 4 demo shows work group and role fields. Need governance for overrides. |
| Site | GLM / 3GIS / location systems | GLM / 3GIS / source location owner | Lumen Vision, planning, network implementation | GLM / 3GIS or location master | Likely | Session 5 roadmap: sites/routes via GLM/3GIS. Session 1 planning request begins with locations. |
| Route / Segment / Span | GLM / 3GIS / BluePlanet | GLM / 3GIS / BluePlanet | Lumen Vision, planning, inventory | BluePlanet / GLM / 3GIS | Open | Roadmap shows GLM/3GIS for sites/routes and BluePlanet for network design/inventory. Need object split. |
| Network Resource / Inventory | BluePlanet / VoltRon | BluePlanet / inventory systems | Data Hub, Lumen Vision, BPI, analytics | BluePlanet | Confirmed/Likely | Inventory consolidation into BluePlanet/VoltRon is a major program. Exact interim ownership may vary. |
| Equipment Inventory | BluePlanet / inventory source | Inventory systems after install/update | Lumen Vision, Data Hub, analytics | BluePlanet / inventory source | Likely | Session 2 workflow shows equipment install/add equipment to inventory before implementation request. |
| BOM / Bill of Materials | Planning / engineering discipline | SAP / Lumen Vision / sourcing flow | Lumen Vision, SAP, sourcing, vendors | Open | Open | Session 1 says SAP Material Master standardization is required. Session 5 says BOM object definition must be standardized. |
| Material Master | SAP S/4HANA | SAP S/4HANA | Lumen Vision, procurement, BOM consumers | SAP S/4HANA | Confirmed | Session 1 explicitly calls for SAP material master standardization to prevent part-number mismatch. |
| Procurement / Vendor Sourcing | SAP S/4HANA | SAP S/4HANA / procurement | Lumen Vision, PMO, finance | SAP S/4HANA | Likely | Session 1 target ecosystem shows SAP S/4HANA for vendor sourcing, logistics, assets, capital management. |
| Capital / Funding Request | SAP Capital / finance systems | SAP / finance | Lumen Vision / project planning | SAP / finance | Likely | Session 2 target sketch routes “get funding if needed” to SAP Capital. |
| Permit | Lumen Vision / ADO permitting workflow | Lumen Vision / permitting team / external jurisdictions | Lumen Vision, dashboards, ADO/RAG | Lumen Vision + external jurisdiction status | Likely | Session 3 ADO permitting frames show AI-assisted permitting lifecycle. Need external authority boundaries. |
| Site Survey | Lumen Vision / GLM / field workflow | Survey/field team | Lumen Vision, planning, Project Helix | Open | Open | Site survey appears in planning request and Project Helix. Need tool owner and status contract. |
| Forecast Date | Lumen Vision / SOM / source workflow by date type | Owning workflow/source system | Dashboards, reports, downstream systems | Open | Open | Date management repeatedly called out as holistic unresolved capability. Needs canonical model. |
| Baseline Date | Planning / project management | Controlled change process | Lumen Vision/reporting | Lumen Vision or PMO | Open | Session 5 transformation model names baseline plan. Ownership not settled. |
| Projected / Forecast Date | Lumen Vision / workflow engine | Lumen Vision / task owners / automated forecasting | Dashboards, Service Delivery, OM | Open | Open | Forecasting desired but deferred in some contexts. Needs field-level ownership. |
| Actual Completion Date | Executing system / user | Executing system / user | Lumen Vision, reporting | Executing system or LV | Open | Actuals are shown in LV task UI, but authoritative write source may vary. |
| GCR / Change Notification | GCR / ServiceNow future | GCR / ServiceNow | Lumen Vision, WFM, customer notification flows | GCR / ServiceNow | Likely | Session 1 says GCR may move to ServiceNow. Session 2 target sketch has GCR endpoint from LV workflow. |
| Field Work / Dispatch Task | WFM / Salesforce SFS / Flight Deck | Field system / field tech | Lumen Vision, ByFrost | WFM / field system | Likely | Workforce migration to SFS is multi-year. LV likely needs bidirectional task/status contract. |
| ByFrost Context Package | ByFrost | ByFrost / integration feeds | Field users / single pane | ByFrost | Likely | Session 2 target sketch positions ByFrost as single pane. Need clarify if aggregator only or operational authority. |
| Analytics / KPI / Performance Metrics | INID / reporting platforms / Data Hub | Reporting pipelines | Leadership, PMO, operations | INID/reporting platform | Likely/Open | Session 2 assumes INID for network-initiated reporting; needs validation. |
| Data Hub Stitched View | Data Hub | Data Hub ingestion pipelines | Downstream consumers | Data Hub | Confirmed | Session 1: consumers use Data Hub for stitched view; updates go to source system APIs. |
| Kafka Event / Topic | Source system / integration team | Source system / integration platform | Subscribers, Lumen Vision, analytics, AI | Kafka/CFKA platform + source owners | Likely | Session 3 positions Kafka as scaled fast data utility with replay, idempotency, traceability, validation. |
| Correlation / Traceability Header | Kafka/CFKA integration standard | Producing systems | All subscribers | Integration architecture | Likely | Kafka 2.0 headers are mandatory dependency for SOM 2.0. Should be commit blocker. |
| Dead Letter / Exception Event | Kafka/CFKA platform | Integration operations | Support, dashboards, workflow exception handling | Integration operations | Likely | Session 3 mentions dead-letter queues and automated ticketing/actions. Need operating model. |
| AI Recommendation / Next Best Action | ADO / AI services | AI service with human validation | Lumen Vision user/workflow | Human-supervised workflow | Likely | Session 3 says ADO recommends next actions; human-in-loop governance needed. |
| AI-Authorized Action | Human-approved workflow step | Lumen Vision / target system API | Audit log, dashboards | Target source system + audit | Open | Should not be autonomous until governance and auditability are approved. |
Release 1 Ownership Focus
These ownership questions are most urgent for the architecture commit:
| Priority | Object / Domain | Why It Matters | Proposed Next Action |
|---|---|---|---|
| P0 | Product Order / Service Order / Network Order | Defines order flow from Salesforce/SOM to network execution | Confirm create/update/read/lifecycle owner per order type |
| P0 | Task / Task Status | Determines whether users still swivel-chair between LV, FD, WFM, ByFrost | Define task lifecycle and bidirectional sync contract |
| P0 | Kafka Traceability Header | Mandatory dependency for SOM 2.0 and cross-system observability | Define required header fields and owning standard |
| P0 | Date Fields | Forecasting, milestones, and reporting depend on consistent dates | Define canonical baseline/forecast/actual/need-by ownership |
| P1 | Data Cleanse Gate | Network work cannot safely start with bad inventory/network data | Define external milestone/status contract |
| P1 | SiteTracker / Project Helix Project | Migration/cutover depends on ownership for net-new and in-flight projects | Define cutover rules by project state |
| P1 | BOM / Material Master | Procurement, cost, and build planning depend on SAP alignment | Define BOM owner and SAP material master integration |
| P1 | Site / Route / Segment | Planning, GLM/3GIS, BluePlanet, and network build all depend on this split | Define object boundary across GLM/3GIS and BluePlanet |
| P2 | AI Recommendation / Action | AI roadmap depends on governance and auditability | Define recommendation/action boundary |
| P2 | Reporting / Analytics | INID/Data Hub/LV dashboards may conflict | Define reporting source and reconciliation model |
Integration Pattern Matrix
Use this as the first draft of integration patterns.
| Pattern | Description | Candidate Uses | Commit Guidance |
|---|---|---|---|
| Source API Command | Lumen Vision or workflow sends an action to the authoritative system | Create/update order, task, network order, GCR, field dispatch | Use only where target system supports stable API and authorization |
| Event Publish/Subscribe | Source publishes Kafka/CFKA event; consumers react | SOM updates, status changes, inventory changes, date updates | Require traceability header, idempotency, replay, DLQ |
| Stitched Read View | Consumers read consolidated view without write authority | Data Hub product/service/order views | Use for visibility; never update through read model |
| Embedded UI | Lumen Vision opens another tool experience in context | Interim no-swivel support for modern apps | Use as transitional pattern, not source-of-truth substitute |
| Context Package | Aggregator packages notes/order/task/context for execution | ByFrost field context | Clarify ownership and update path |
| External Milestone Gate | External process reports completion/blocked status | Data cleansing, site survey, jurisdiction permit status | Must be auditable and visible in workflow |
| Manual Bridge / Flat File | Temporary handoff while target integration is unavailable | Partner data, early migration, blocked integrations | Time-box and track retirement plan |
Architecture Commit Validation Checklist
Before approval, verify:
- Every Release 1 object has a create/update/read/lifecycle owner.
- Every cross-system update has an integration pattern.
- Kafka/CFKA event headers include correlation, source, object identity, event type, timestamp, version, and replay/idempotency support.
- Data-cleansing gate is represented in workflow even if execution remains external.
- SiteTracker/Armor/Netbuild migration rules distinguish new, in-flight, historical, and duplicated records.
- LV, FD, ByFrost, WFM, BPI, and Itential task responsibilities are explicitly separated.
- AI/ADO action boundaries are human-supervised unless separately approved.
- Environments and rollback/replay controls exist for multi-system testing.
Open Items For Stakeholder Review
- Validate whether INID remains the network-initiated reporting source of truth.
- Confirm whether ByFrost is UI aggregation only or also owns operational task/context data.
- Confirm whether Lumen Vision initiates all network orders or only selected MVP workflows.
- Confirm authoritative ownership for site/route/span across GLM, 3GIS, and BluePlanet.
- Confirm whether BOM lives primarily in Lumen Vision, SAP, or split by preliminary/final state.
- Confirm if Project Helix owns only legacy exits or also planning/grooms/site survey workflow harmonization.
- Confirm minimum Kafka 2.0 header set and delivery date relative to SOM 2.0.