Glosario De Architecture Commit
Glosario practico para la conversacion de LumenVision / OneVizion Architecture Commit. Estas definiciones explican como se usa cada termino en este proyecto para hablar de alcance, ownership, integraciones y riesgos con el mismo vocabulario.
Proceso Y Posicionamiento
Architecture Commit
Checkpoint formal de aprobacion para mover LumenVision de concept hacia solutioning y development con funding.
Como usarlo: Usalo para alinear scope, value, architecture artifacts, decisiones abiertas y riesgo antes de acelerar build.
LumenVision / OneVizion
La capa propuesta de workflow, planning, orchestration y visibility para el trabajo de network implementation de Lumen.
Como usarlo: Posicionalo como work surface y coordination layer, no como dueno de todos los business objects.
Source Of Truth
El sistema o equipo authoritativo que es dueno de un business object y puede actualizarlo.
Como usarlo: Pregunta clave de commit: que sistema es dueno de cada objeto como order, task, site, BOM, inventory, status, date y document?
System Of Record Matrix
Artefacto de decision que mapea cada business object a su owner authoritativo, consumidores, nivel de confianza y preguntas abiertas.
Como usarlo: Usalo para evitar ownership duplicado y comportamiento de write-back poco claro.
POV Cliente
Narrativa de recomendacion para customer: que entendemos, que problema resuelve Lumen y que solution path recomendamos.
Como usarlo: Es el mejor punto de inicio para una conversacion ejecutiva o con customer.
Release 1 Anchor
El primer workflow o use case acotado para probar la target architecture.
Como usarlo: Posibles anchors: Service Delivery, SiteTracker exit, Network Grooms, RNI, Waves o Dark Fiber.
Service Delivery
A major candidate workflow area for Release 1 and architecture commit scope.
Como usarlo: Lumen needs to decide priority and path forward for the Service Delivery module.
SiteTracker Exit
Migration or replacement path away from SiteTracker for selected project/workflow scope.
Como usarlo: Treat it as both a deadline migration problem and a future workflow transformation decision.
Network Grooms
Network grooming workflow area discussed as one of the next scope decisions.
Como usarlo: Clarify owner, release priority, integration points, and whether it belongs in Release 1.
Sistemas Y Dominios
SOM 2.0 / BlueSteel
Service order management flow that sits between product order sources and downstream implementation workflows.
Como usarlo: Important dependency for service-order events, date publishing, Kafka headers, and workflow generation.
Salesforce / NEO
Product order and sales/order-entry source area.
Como usarlo: Do not let LumenVision casually become product-order authority unless Lumen explicitly changes ownership.
BPI
Network order or design execution system area referenced in the target workflow.
Como usarlo: LumenVision may create, request, monitor, or receive status from BPI depending on agreed integration contract.
BluePlanet / VoltRon
Target inventory and network design/inventory direction.
Como usarlo: Likely authoritative for network inventory, but interim ownership and write-back rules need confirmation.
GLM / 3GIS
Location, route, site, and survey-related systems.
Como usarlo: Important for planning requests, route/span objects, and network opportunity data.
SAP S/4HANA
Material master, BOM, procurement, vendor sourcing, capital, and finance-related system.
Como usarlo: Architecture commit must define what LumenVision reads, writes, or references for material and funding workflows.
BOM
Bill of Materials: structured list of required parts/materials for design or build.
Como usarlo: BOM standardization matters because material mismatch creates sourcing and execution risk.
Material Master
Authoritative standardized material and part-number data, likely owned in SAP.
Como usarlo: Needed so LumenVision, engineering, sourcing, and procurement speak the same material language.
Kafka / CFKA
Event backbone for state changes, traceability, replay, dead-letter handling, and integration between systems.
Como usarlo: Treat Kafka headers and contracts as architecture dependencies, not low-level implementation details.
Integracion Y Datos
Kafka 2.0 Headers
Traceability and correlation metadata required for observability across event flows.
Como usarlo: Should be a commit blocker if SOM 2.0 and downstream consumers depend on them.
DLQ
Dead Letter Queue: event handling pattern for failed or invalid messages.
Como usarlo: Needs an operating model: who monitors, retries, resolves, and reports integration failures.
Data Hub
Stitched read view and integration/reporting consumer.
Como usarlo: It can aggregate state, but should not automatically be treated as update authority.
WFM / SFS / Flight Deck
Field execution and task platforms used by different personas or migration states.
Como usarlo: Define which tasks remain there versus which tasks move to or are displayed by LumenVision.
ByFrost
Single-pane/context package concept for field or operational users.
Como usarlo: Clarify whether it is an aggregator only or whether any operational authority lives there.
GCR / ServiceNow
Change notification/ticketing area with possible future ServiceNow direction.
Como usarlo: Define whether LumenVision triggers, monitors, or simply references change notifications.
ADO / AI Agents
AI-assisted decision orchestration and workflow support.
Como usarlo: Keep actions human-supervised until lineage, audit, rollback, replay, and guardrails are proven.
RAG
Retrieval-Augmented Generation: AI pattern that answers using controlled source material.
Como usarlo: Useful for document, rule, permitting, and operational guidance, but needs source governance.
Human-Supervised AI
AI recommends or prepares an action, but a person reviews or approves before execution.
Como usarlo: This is the safer Architecture Commit position for early AI scope.
Integration Contract
Agreed data, event, API, ownership, error, and retry behavior between systems.
Como usarlo: Every high-priority integration should have one before development commitments become firm.
Write-Back
When LumenVision or another consumer updates a source system, not just reads from it.
Como usarlo: Write-back needs owner approval, validation, rollback, replay, and audit rules.
Context Package
A bundle of order, task, site, inventory, document, and status context passed to a user or downstream system.
Como usarlo: Useful for reducing swivel-chair work across LumenVision, ByFrost, and field systems.
Terminos De Programa Y Acronimos
MVP
Minimum viable product or first usable release scope.
Como usarlo: For this program, MVP should prove priority workflow, ownership, integration, and value without overclaiming universal scope.
BAU
Business as usual: current operations that must continue during transformation.
Como usarlo: Architecture must protect BAU while moving target workflows into LumenVision.
FT3
A named Lumen workstream or program term seen in the meeting action items/session notes.
Como usarlo: Needs confirmation from Lumen on scope, owner, and relationship to SiteTracker exit and BAU work.
Project Helix
Transformation/migration program context tied to workflow and legacy exit decisions.
Como usarlo: Use it as a dependency lens when discussing SiteTracker, Netbuild, Armor, and future workflow shape.
NSA
Network Systems Architecture or related Lumen architecture context, based on work item references.
Como usarlo: Confirm the exact internal meaning with Lumen before using the acronym externally.