Glosarium Architecture Commit
Glosarium praktis untuk percakapan LumenVision / OneVizion Architecture Commit. Definisi ini menjelaskan arti istilah dalam konteks project ini agar scope, ownership, integrasi, dan risiko dibahas dengan bahasa yang sama.
Proses Dan Posisi
Architecture Commit
Checkpoint approval formal untuk membawa LumenVision dari concept menuju solutioning dan development yang didanai.
Cara menggunakannya: Gunakan untuk menyelaraskan scope, value, architecture artifacts, keputusan terbuka, dan risiko sebelum build dipercepat.
LumenVision / OneVizion
Layer workflow, planning, orchestration, dan visibility yang diusulkan untuk pekerjaan network implementation Lumen.
Cara menggunakannya: Posisikan sebagai work surface dan coordination layer, bukan pemilik semua business object.
Source Of Truth
Sistem atau tim otoritatif yang memiliki business object dan dipercaya untuk memperbaruinya.
Cara menggunakannya: Pertanyaan commit utama: sistem mana yang memiliki setiap object seperti order, task, site, BOM, inventory, status, date, dan document.
System Of Record Matrix
Artefak keputusan yang memetakan setiap business object ke owner otoritatif, consumer, tingkat keyakinan, dan pertanyaan terbuka.
Cara menggunakannya: Gunakan untuk mencegah ownership ganda dan perilaku write-back yang tidak jelas.
POV Customer
Narasi rekomendasi untuk customer: apa yang kita pahami, masalah apa yang Lumen selesaikan, dan jalur solusi apa yang kita sarankan.
Cara menggunakannya: Ini titik awal terbaik untuk diskusi executive atau customer.
Release 1 Anchor
Workflow atau use case pertama yang dibatasi untuk membuktikan target architecture.
Cara menggunakannya: Anchor yang mungkin: Service Delivery, SiteTracker exit, Network Grooms, RNI, Waves, atau Dark Fiber.
Service Delivery
A major candidate workflow area for Release 1 and architecture commit scope.
Cara menggunakannya: 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.
Cara menggunakannya: 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.
Cara menggunakannya: Clarify owner, release priority, integration points, and whether it belongs in Release 1.
Sistem Dan Domain
SOM 2.0 / BlueSteel
Service order management flow that sits between product order sources and downstream implementation workflows.
Cara menggunakannya: Important dependency for service-order events, date publishing, Kafka headers, and workflow generation.
Salesforce / NEO
Product order and sales/order-entry source area.
Cara menggunakannya: 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.
Cara menggunakannya: LumenVision may create, request, monitor, or receive status from BPI depending on agreed integration contract.
BluePlanet / VoltRon
Target inventory and network design/inventory direction.
Cara menggunakannya: Likely authoritative for network inventory, but interim ownership and write-back rules need confirmation.
GLM / 3GIS
Location, route, site, and survey-related systems.
Cara menggunakannya: 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.
Cara menggunakannya: 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.
Cara menggunakannya: BOM standardization matters because material mismatch creates sourcing and execution risk.
Material Master
Authoritative standardized material and part-number data, likely owned in SAP.
Cara menggunakannya: 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.
Cara menggunakannya: Treat Kafka headers and contracts as architecture dependencies, not low-level implementation details.
Integrasi Dan Data
Kafka 2.0 Headers
Traceability and correlation metadata required for observability across event flows.
Cara menggunakannya: 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.
Cara menggunakannya: Needs an operating model: who monitors, retries, resolves, and reports integration failures.
Data Hub
Stitched read view and integration/reporting consumer.
Cara menggunakannya: 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.
Cara menggunakannya: 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.
Cara menggunakannya: 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.
Cara menggunakannya: Define whether LumenVision triggers, monitors, or simply references change notifications.
ADO / AI Agents
AI-assisted decision orchestration and workflow support.
Cara menggunakannya: 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.
Cara menggunakannya: 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.
Cara menggunakannya: This is the safer Architecture Commit position for early AI scope.
Integration Contract
Agreed data, event, API, ownership, error, and retry behavior between systems.
Cara menggunakannya: 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.
Cara menggunakannya: 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.
Cara menggunakannya: Useful for reducing swivel-chair work across LumenVision, ByFrost, and field systems.
Istilah Program Dan Akronim
MVP
Minimum viable product or first usable release scope.
Cara menggunakannya: 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.
Cara menggunakannya: 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.
Cara menggunakannya: 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.
Cara menggunakannya: 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.
Cara menggunakannya: Confirm the exact internal meaning with Lumen before using the acronym externally.