Integration Inventory
Purpose: working inventory of system integrations for the Lumen Architecture Commit. This pairs with system-of-record-matrix.html and should be validated with system owners.
Legend:
- **Confirmed**: explicitly stated or clearly visible in meeting notes/diagrams.
- **Likely**: inferred from roadmap, diagrams, or discussion.
- **Open**: unresolved and needs architecture decision.
Integration Pattern Reference
| Pattern | Meaning |
|---|---|
| Event Publish/Subscribe | Kafka/CFKA event topic with traceability headers, idempotency, replay, and DLQ expectations. |
| Source API Command | System sends a command/update to the authoritative source through an API. |
| Stitched Read View | Data Hub or reporting layer provides a read-only consolidated view. |
| Embedded UI | One system opens another system UI in context to reduce swivel-chair work. |
| Context Package | Aggregator packages relevant notes/order/task/context for execution. |
| External Milestone Gate | External process reports milestone/status back to workflow. |
| Manual Bridge / Flat File | Temporary transfer while target integration is unavailable. |
Integration Inventory Matrix
| ID | Source | Target | Object / Event | Pattern | Status | Dependency / Driver | Open Decision |
|---|---|---|---|---|---|---|---|
| INT-001 | Salesforce / NEO | Data Hub | Product order, product instance | Event Publish/Subscribe or ingestion | Confirmed direction | Salesforce is source of truth; Data Hub stitched view | Exact event/API mechanism and object contract |
| INT-002 | Salesforce / NEO | SOM 2.0 / BlueSteel | Product order to service order | Source API Command / Event | Likely | Northstar order decomposition | Which system performs decomposition and owns failures |
| INT-003 | SOM 2.0 / BlueSteel | Lumen Vision | Service order, service order item, milestones, dates | Event Publish/Subscribe | Likely | SOM 2.0 release for Waves/Dark Fiber | Required Kafka 2.0 headers and date ownership |
| INT-004 | Lumen Vision | SOM 2.0 / BlueSteel | Workflow status, milestone forecast/status | Event Publish/Subscribe / Source API Command | Open | Service Delivery North Star / Waves | Is LV updating SOM or only consuming/publishing status? |
| INT-005 | Lumen Vision | BPI | Network order request/design request | Source API Command | Likely | Session 2 target sketch and BPI network order | Does LV create network orders or request BPI creation? |
| INT-006 | BPI | Lumen Vision | Network order status, design state | Event Publish/Subscribe | Likely | Network implementation workflow visibility | Required status model and error handling |
| INT-007 | Lumen Vision | ByFrost | Project/task/order context | Context Package | Likely | ByFrost single-pane field/network context | Is ByFrost aggregator only or operational state holder? |
| INT-008 | ByFrost | Field users / downstream tools | Field task context, notes, templates | Context Package | Likely | Field execution support | What updates return to LV and by what path? |
| INT-009 | Lumen Vision | Flight Deck | Task assignment/status/context | Source API Command / Embedded UI | Open | Session 2 LV + FD task presentation | Does FD own execution tasks or only selected field workflows? |
| INT-010 | Flight Deck | Lumen Vision | Task completion/status updates | Event Publish/Subscribe / API | Open | No-swivel target and task visibility | Bidirectional status contract |
| INT-011 | Lumen Vision | Itential | Workflow execution / automation steps | Source API Command | Open | Session 2 workflow entity decision point | Which workflows are LV-owned vs Itential-owned? |
| INT-012 | Itential | Lumen Vision | Workflow state/fallout/status | Event Publish/Subscribe | Open | Automation and network workflow execution | Common workflow state model |
| INT-013 | Lumen Vision | WFM / Salesforce SFS | Field task / dispatch request | Source API Command | Likely | Workforce migration to SFS | Field task object and assignment ownership |
| INT-014 | WFM / Salesforce SFS | Lumen Vision | Field status, actuals, completion, technician updates | Event Publish/Subscribe / API | Likely | Bidirectional workforce management | Real-time vs batch updates; conflict handling |
| INT-015 | Lumen Vision | GCR / ServiceNow future | Change notification request | Source API Command | Likely | GCR endpoint in target sketch; ServiceNow transition | Does GCR move to ServiceNow before/after LV integration? |
| INT-016 | GCR / ServiceNow | Lumen Vision | Change status, customer notification state | Event Publish/Subscribe | Open | GCR process visibility | Status taxonomy and owner |
| INT-017 | Lumen Vision | SAP Capital | Funding / capital request | Source API Command / Manual Bridge | Likely | Session 2 target sketch: get funding if needed | API availability and approval workflow |
| INT-018 | SAP S/4HANA | Lumen Vision | Material master, part numbers | Event Publish/Subscribe / Stitched Read View | Confirmed need | Prevent BOM/part mismatch | Read-only master or cached local copy? |
| INT-019 | Lumen Vision | SAP S/4HANA | Preliminary/final BOM, procurement request | Source API Command | Open | BOM/material/procurement roadmap | Which BOM state is LV-owned vs SAP-owned? |
| INT-020 | SAP S/4HANA | Lumen Vision | Procurement, vendor sourcing, logistics, asset status | Event Publish/Subscribe | Likely | SAP roadmap and target ecosystem | Object scope and refresh cadence |
| INT-021 | GLM / 3GIS | Lumen Vision | Site, route, segment, location data | Event Publish/Subscribe / Stitched Read View | Likely | Sites and routes roadmap | Split of ownership across GLM, 3GIS, BluePlanet |
| INT-022 | Lumen Vision | GLM / 3GIS | Site survey / route planning request | Source API Command | Open | Planning/network opportunity and Project Helix | Whether LV can initiate survey/planning workflows |
| INT-023 | BluePlanet / VoltRon | Lumen Vision | Network resource, inventory state | Event Publish/Subscribe / Stitched Read View | Likely | Inventory consolidation and network implementation | Release timing; source object contract |
| INT-024 | Lumen Vision | BluePlanet | Network design/order initiation | Source API Command | Open | Future state mentions LV initiating network orders in BPI/BluePlanet | Deferred until object model is agreed |
| INT-025 | BluePlanet | Data Hub | Inventory/resource domains | Event Publish/Subscribe / ingestion | Likely | Data Hub stitched view | Domain boundaries and latency |
| INT-026 | Data Hub | Lumen Vision / consumers | Stitched order/service/inventory view | Stitched Read View | Confirmed | Session 1 read-side consumer pattern | Ensure LV does not update via Data Hub |
| INT-027 | Source systems | Kafka / CFKA | Order/task/inventory/date/status events | Event Publish/Subscribe | Confirmed direction | Kafka 2.0 / CFKA | Required header standard and producer onboarding |
| INT-028 | Kafka / CFKA | Lumen Vision | Real-time events, CDC, status changes | Event Publish/Subscribe | Likely | Faster integrations and next-best-action AI | Topic subscription model and replay behavior |
| INT-029 | Kafka / CFKA | AI / ADO | Event data for next-best-action and fallout | Event Publish/Subscribe | Likely | ADO and AI Trust Engine | AI-readable event/object model |
| INT-030 | Kafka / CFKA | Ticketing / operations | Dead-letter queue, exception event, automated ticket | Event Publish/Subscribe / Source API Command | Likely | Exception handling via rules/AI agents | DLQ owner, SLA, retry/replay authority |
| INT-031 | Data Cleansing Team / Tool | Lumen Vision | Data cleanse complete/blocked status | External Milestone Gate | Confirmed need | Data cleanse prerequisite for network work | Status format and evidence/audit requirement |
| INT-032 | Lumen Vision | Data Cleansing Team / Tool | Data-cleanse request / prerequisite task | Source API Command / Manual Bridge | Open | Data cleanse gate in workflow | Whether LV initiates or only waits |
| INT-033 | SiteTracker | Lumen Vision | Existing project/workflow migration | Manual Bridge / Migration Load | Likely | SiteTracker exit / Project Helix | New vs in-flight vs historical migration rules |
| INT-034 | Lumen Vision | SiteTracker | Net-new project avoidance / transition state | Manual Bridge / Cutover Policy | Likely | Stop storing new projects in SiteTracker | Effective cutover date and exception policy |
| INT-035 | Armor | Lumen Vision / Project Helix | Legacy work migration | Manual Bridge / Migration Load | Likely | Armor exit | Object mapping and timing |
| INT-036 | Netbuild | Lumen Vision / Project Helix | Network build workplans/orders/status | Manual Bridge / Event/API future | Likely | Netbuild exit / Project Helix | Interim coexistence model |
| INT-037 | INID | Lumen Vision / reporting consumers | KPI, order status, task aging, analytics | Stitched Read View / Reporting | Likely/Open | INID assumed reporting source | Validate whether target or temporary |
| INT-038 | Lumen Vision | INID / reporting platform | Project/task/workflow data | Event Publish/Subscribe / ingestion | Open | Analytics continuity | Reporting ingestion contract |
| INT-039 | Lumen Vision | ADO / AI agents | Workflow state, task data, exceptions | Source API Command / internal event | Likely | Adaptive Decision Orchestrator | Human approval boundary |
| INT-040 | ADO / AI agents | Lumen Vision | Recommendations, next-best actions, generated tasks | Source API Command with human approval | Likely/Open | AI roadmap | What actions can be actualized and audited? |
| INT-041 | Lumen Vision | RAG servers / rule mapping | Workflow context, docs, rules | Source API Command / internal service | Likely | ADO, permitting, smart dossiers | Data access controls and freshness |
| INT-042 | RAG servers / rule mapping | Lumen Vision | Draft package, validation, rules outcome | Source API Command with human approval | Likely | ADO-assisted permitting | Approval and audit trail |
| INT-043 | External jurisdictions / permitting sources | Lumen Vision / ADO | Permit status, requirements, response data | Manual Bridge / API where available | Open | Permitting workflow | External integration availability |
| INT-044 | Lumen Vision | Partner / TXO systems | Partner data sharing | Event Publish/Subscribe / API / Manual Bridge | Open | LTO PMO partner data requests | Security/legal approval and integration strategy |
| INT-045 | NAT Tool | Lumen Vision / LTO PMO | NAT data, financial/build order context | API / Data Feed | Open | LTO PMO NAT data sharing | Data sharing request and owner |
| INT-046 | PathComp | Lumen Vision / planning flow | Product/opportunity/path data | API / Stitched Read View | Open | Planning and order management discussion | Whether PathComp becomes upstream source |
| INT-047 | Intelligent Interval Quoting (IIQ) | Lumen Vision | Interval estimates | Source API Command / Stitched Read View | Open | Roadmap micro-app integration | Forecasting/date-management ownership |
| INT-048 | Order Health Engine (OHE) | Lumen Vision | Order health/risk signals | Event Publish/Subscribe / API | Open | Roadmap micro-app integration | Signal model and action owner |
Priority Integration Decisions
| Priority | Integration | Decision Needed | Why It Matters |
|---|---|---|---|
| P0 | Salesforce/NEO -> SOM/BlueSteel -> Lumen Vision | Product/service order event and ownership model | Defines core order flow and Release 1 scope |
| P0 | SOM/BlueSteel <-> Kafka/CFKA | Required Kafka 2.0 headers and event contracts | Mandatory dependency for SOM 2.0 traceability |
| P0 | Lumen Vision <-> BPI | Network order create/status/update contract | Determines whether LV truly orchestrates network work |
| P0 | Lumen Vision <-> Flight Deck/WFM/ByFrost | Task presentation, task ownership, and status write-back | Determines no-swivel feasibility |
| P0 | Data Cleanse -> Lumen Vision | External gate/milestone contract | Prevents network work starting with bad data |
| P1 | Lumen Vision <-> SAP S/4HANA | BOM/material/funding/procurement scope | Prevents material master and BOM mismatch |
| P1 | GLM/3GIS/BluePlanet <-> Lumen Vision | Site/route/inventory ownership split | Enables planning, build, and inventory automation |
| P1 | SiteTracker/Armor/Netbuild -> Lumen Vision | Migration and cutover mapping | Drives Project Helix and legacy exits |
| P2 | Lumen Vision <-> AI/ADO/RAG | Recommendation/action boundary | Prevents AI overcommitment |
| P2 | Lumen Vision <-> INID/reporting | Reporting and KPI continuity | Prevents conflicting operational metrics |
Release 1 Candidate Integration Set
Recommended Release 1 focus:
- Salesforce/NEO/SOM order events into Lumen Vision.
- Kafka 2.0 traceability headers for SOM 2.0.
- Lumen Vision to/from BPI for network order/design request visibility.
- Lumen Vision to/from Flight Deck or WFM for task/status sync in selected MVP workflows.
- Data cleanse external milestone gate into Lumen Vision.
- Read-only Data Hub stitched view for downstream consumers.
- SiteTracker cutover/migration feed for net-new and selected active projects.
Defer or constrain:
- Full BluePlanet write integration.
- Fully automated forecasting.
- Agentic AI execution without human approval.
- Full universal grooms migration.
- Broad partner live integrations until security/legal/data contracts are settled.
Integration Contract Checklist
For each integration, require:
- Business owner.
- Technical owner.
- Source system and target system.
- Object/event name.
- Create/update/read ownership.
- Integration pattern.
- Trigger condition.
- Payload schema.
- Required correlation ID / traceability header.
- Delivery semantics: sync, async, batch, near-real-time.
- Idempotency/replay behavior.
- Error handling and DLQ behavior.
- Security and access model.
- Audit/logging requirements.
- Cutover and rollback plan.
- Test environment availability.
Open Questions For Architecture Committee
- Which integrations are mandatory for the mid-July architecture commit versus roadmap placeholders?
- Is Kafka/CFKA the default integration pattern for all state changes, or only for selected domains?
- Are source API commands allowed from Lumen Vision into all authoritative systems, or only where workflow ownership is delegated?
- Who owns cross-system correlation IDs and header standards?
- What is the authoritative list of Release 1 topics/events?
- Which temporary manual/flat-file bridges are acceptable, and what is their retirement date?
- What integration failures should block workflow progression versus create fallout tasks?
- Which systems can participate in lower-environment integration testing before production cutover?