Pemetaan Slide Accenture dengan Kajian Teknis

Perbandingan slide Accenture untuk Pertamina Patra Niaga — “03.2 To-be technology landscape” — “Microservice Decomposition” (“From Monolith to 14 Bounded Contexts — Domain-Driven Service Decomposition”) — dengan kajian teknis kita (Overview Kajian Scorecard).

Pemetaan 14 service Accenture ↔ service kita

Core Business Services (6)

#	Service Accenture	Isi (per slide)	Status kajian teknis
1	Registration & Onboarding	Customer registration (Direct B2B/Agent/E-Voucher), AM/SBM mapping, approval workflows, SAP Customer ID creation	✅ SV-09 (Registrasi & OTP) + SV-12 (Terima mapping SAP) — ⚠️ AM/SBM mapping (hierarki internal sales) belum pernah ditelusuri
2	Identity & Access Management (IAM)	RBAC, entity hierarchy (HQ→Sold-To→Ship-To), super-admin delegation, dual-role buyer/seller identity, audit logs	✅ SV-09 — Accenture pisahkan dari Registration (#1), kajian teknis sekarang juga terpisah sejak D29 (`SV-09` Account vs `SV-12` Customer) — persis konvergen dengan Accenture. ⚠️ “dual-role buyer/seller” — konsep baru, 0 evidence di kode
3	Contract Management	Contract lifecycle, pricing & quota agreements, volume monitoring, renewal alerts, i-Customer/SAP integration	⚠️ Tipis — cuma `tblT_Booking_Group_Kontrak_Jaminan` (SV-03) & “Get Contract ZOR” (SV-02 F02). Quota agreements/volume monitoring/renewal alerts — 0 evidence, dicek langsung ke kode
4	Ordering	End-to-end order lifecycle (LOCO/FRANCO/VHS/FMS), bulk upload, recurring orders, templates, demand planning & consolidation	✅ SV-01+SV-02+SV-03 (Cart→Simulate→SO), Bulk Buying ada. ⚠️ Recurring orders, demand planning — 0 evidence
5	Delivery & Fulfillment	Scheduling, live tracking, DO/LO generation, BAST digitization, MS2/ODI/DGO/PADMA/WebVHS integration	❌ Nyaris tidak ada — cuma “Monitoring DO” (SV-11 F08, baca-saja dari SAP) & “Proof of Order” (SV-03 F03). Live tracking/BAST/istilah sistem lapangan kemungkinan besar sistem lain di luar portal ini sepenuhnya
6	Payment & Invoicing	Payment processing, invoicing, debit/credit notes, billing reconciliation, deposit balance management	✅ SV-02(Payment) + SV-08(Billing/DCN) — tercover, tersebar 2 service

Commerce & Intelligence Services (4)

#	Service Accenture	Isi (per slide)	Status kajian teknis
7	Pricing Engine	Real-time price calculation, SAP baseline sync, customer-specific pricing, price change alerts	⚠️ Tensi dengan DDD — DDD (tervalidasi domain expert): “tidak ada harga terpublikasi non-aviasi”. SV-07 cuma cover pricing aviasi. Accenture usul pricing engine semua produk — kemungkinan to-be aspirasional, bukan cerminan bisnis saat ini
8	Recommendation & Personalization	Customer 360, behavioral analysis, product bundling, rebate-driven upsell, AI/ML engine	❌ Aspirasional murni — 0 evidence AI/ML/behavioral/bundling/rebate di kode (wajar, kapabilitas baru)
9	E-Voucher Management	Issuance→distribution→redemption, RFID management, recipient directory, anomaly detection, B2C telemetry	✅ SV-04 — tapi RFID/anomaly detection/B2C telemetry jauh lebih kaya dari 4 fitur yang ada saat ini (Simulate, Create Booking, Get Token LinkAja, Cancel Transaction)
10	Reporting & Analytics	Dashboards (purchases, balance, credit, payments), volume monitoring vs commitment, purchase forecasting, D-1 data aggregation	✅ SV-11 — paling cocok dari semua 14. “D-1 data aggregation” match persis pola scheduler yang sudah didesain

Platform / Cross-Cutting Services (4)

#	Service Accenture	Isi (per slide)	Status kajian teknis
11	Notification & Alerting	Push, email, in-app inbox, SMS — price alerts, approval requests, delivery updates, renewal reminders, SLA breaches	⚠️ Tensi — kajian teknis sengaja gabung ke SV-05 karena “notifikasi sekarang cuma 1 kanal (email)”. Accenture usul multi-channel jadi service sendiri
12	Customer Support & Ticketing	Chatbot/live agent routing, ticket lifecycle, FAQ knowledge base, SLA tracking, conversation history	❌ Tidak ada — dikonfirmasi DDD juga (“informasi kontak saja… tidak ada ticketing”) dan grep kode (0 sistem ticketing). Aspirasional murni
13	Workflow Orchestration	Camunda BPMN approval routing, Temporal durable execution (bulk orders, recurring schedules, delivery retry)	❌ Bukan domain service, ini pilihan platform. 0 abstraksi workflow engine di kode — approval masih ad-hoc per stored-procedure
14	Integration Gateway	SAP connector (CDC via Kafka), surrounding system adapters (UMR/DCS/UBP/ISL/ICS), API translation layer	⚠️ Beda pola arsitektur, paling penting — lihat catatan khusus di bawah

Catatan khusus #14 — Integration Gateway terpusat vs pola kajian teknis saat ini

Kajian teknis mendesain tiap service panggil SAP WSDL langsung/sendiri-sendiri (SV-02, SV-06, SV-07, SV-08, SV-12, SV-11 semua punya hop WSDL masing-masing ke SAP). Accenture mengusulkan satu Integration Gateway Service terpusat (SAP connector via CDC/Kafka, bukan WSDL request-response berulang).

Ini bukan sekadar preferensi Accenture sendirian — Pemetaan DDD juga mencatat DDD bilang “Investasi arsitektur terbesar: Gerbang SAP (ACL)… kualitas ACL menentukan kualitas seluruh portal”. Dua sumber independen (DDD + Accenture) sama-sama mengarah ke sentralisasi integrasi SAP, sementara kajian teknis belum pernah mengusulkan pola gateway terpusat secara eksplisit — desain saat ini masih “ACL tersebar” (tiap service urus sendiri).

Ringkasan lintas 3 sumber (kode kita · DDD · Accenture)

Kategori	Service
✅ Match kuat, 3 sumber saling menguatkan	E-Voucher (SV-04), Identity (SV-09/SV-12, split D29 konvergen dgn Accenture #1/#2 terpisah), Reporting/Dashboard (SV-11)
⚠️ Gap nyata, layak di-scan ulang ke kode	Contract Management (quota/renewal), AM/SBM mapping
❌ Kemungkinan di luar portal ini sepenuhnya	Delivery & Fulfillment, Workflow Orchestration (pilihan engine), sebagian besar Platform services
⚠️ Tensi arsitektur	Notification sentralisasi · Integration Gateway terpusat (didukung DDD dan Accenture) · Pricing Engine semua-produk (vs DDD “tidak ada harga non-aviasi”)
❌ Aspirasional murni, tidak diharapkan ada di kode	Recommendation/Personalization (AI/ML), Customer Support & Ticketing

Lihat juga

Pemetaan DDD — pemetaan sumber kedua (DDD Strategic Design, System Analyst).