1397 lines
76 KiB
Python
1397 lines
76 KiB
Python
#!/usr/bin/env python3
|
||
"""
|
||
Generate PowerPoint slides for all 18 chapters of:
|
||
"Sistem Informasi Manajemen di Era AI: Perspektif Strategis dan Pengambilan Keputusan"
|
||
by Helmi Bahar Alim, S.Kom., M.Kom.
|
||
"""
|
||
|
||
import os
|
||
from pptx import Presentation
|
||
from pptx.util import Inches, Pt, Emu
|
||
from pptx.dml.color import RGBColor
|
||
from pptx.enum.text import PP_ALIGN, MSO_ANCHOR
|
||
from pptx.enum.shapes import MSO_SHAPE
|
||
|
||
# === CONFIGURATION ===
|
||
OUTPUT_DIR = os.path.join(os.path.dirname(os.path.dirname(__file__)), "slides")
|
||
os.makedirs(OUTPUT_DIR, exist_ok=True)
|
||
|
||
# Color scheme
|
||
PRIMARY = RGBColor(0x1B, 0x3A, 0x5C) # Dark navy
|
||
SECONDARY = RGBColor(0x2E, 0x86, 0xAB) # Teal blue
|
||
ACCENT = RGBColor(0xE8, 0x5D, 0x26) # Orange accent
|
||
WHITE = RGBColor(0xFF, 0xFF, 0xFF)
|
||
LIGHT_BG = RGBColor(0xF0, 0xF4, 0xF8) # Light blue-gray
|
||
DARK_TEXT = RGBColor(0x2D, 0x3A, 0x4A) # Dark gray
|
||
MEDIUM_TEXT = RGBColor(0x5A, 0x6A, 0x7A) # Medium gray
|
||
|
||
BOOK_TITLE = "Sistem Informasi Manajemen di Era AI"
|
||
BOOK_SUBTITLE = "Perspektif Strategis dan Pengambilan Keputusan"
|
||
AUTHOR = "Helmi Bahar Alim, S.Kom., M.Kom."
|
||
INSTITUTION = "Fakultas Sains dan Teknologi — Universitas Putra Bangsa"
|
||
|
||
|
||
def set_slide_bg(slide, color):
|
||
"""Set solid background color for a slide."""
|
||
background = slide.background
|
||
fill = background.fill
|
||
fill.solid()
|
||
fill.fore_color.rgb = color
|
||
|
||
|
||
def add_shape_bg(slide, left, top, width, height, color):
|
||
"""Add a colored rectangle shape."""
|
||
shape = slide.shapes.add_shape(MSO_SHAPE.RECTANGLE, left, top, width, height)
|
||
shape.fill.solid()
|
||
shape.fill.fore_color.rgb = color
|
||
shape.line.fill.background()
|
||
return shape
|
||
|
||
|
||
def add_textbox(slide, left, top, width, height, text, font_size=18,
|
||
bold=False, color=DARK_TEXT, alignment=PP_ALIGN.LEFT, font_name="Calibri"):
|
||
"""Add a text box with specified formatting."""
|
||
txBox = slide.shapes.add_textbox(left, top, width, height)
|
||
tf = txBox.text_frame
|
||
tf.word_wrap = True
|
||
p = tf.paragraphs[0]
|
||
p.text = text
|
||
p.font.size = Pt(font_size)
|
||
p.font.bold = bold
|
||
p.font.color.rgb = color
|
||
p.font.name = font_name
|
||
p.alignment = alignment
|
||
return txBox
|
||
|
||
|
||
def add_bullet_slide(slide, items, left, top, width, height,
|
||
font_size=16, color=DARK_TEXT, bullet_char="▸"):
|
||
"""Add bullet points to a slide."""
|
||
txBox = slide.shapes.add_textbox(left, top, width, height)
|
||
tf = txBox.text_frame
|
||
tf.word_wrap = True
|
||
|
||
for i, item in enumerate(items):
|
||
if i == 0:
|
||
p = tf.paragraphs[0]
|
||
else:
|
||
p = tf.add_paragraph()
|
||
p.text = f"{bullet_char} {item}"
|
||
p.font.size = Pt(font_size)
|
||
p.font.color.rgb = color
|
||
p.font.name = "Calibri"
|
||
p.space_after = Pt(6)
|
||
return txBox
|
||
|
||
|
||
def create_title_slide(prs, bab_num, bab_title, bagian_label):
|
||
"""Create the chapter title slide with styled layout."""
|
||
slide = prs.slides.add_slide(prs.slide_layouts[6]) # Blank layout
|
||
set_slide_bg(slide, PRIMARY)
|
||
|
||
# Top accent bar
|
||
add_shape_bg(slide, Inches(0), Inches(0), Inches(13.33), Inches(0.08), ACCENT)
|
||
|
||
# Bagian label
|
||
add_textbox(slide, Inches(0.8), Inches(1.2), Inches(11), Inches(0.5),
|
||
bagian_label, font_size=14, color=SECONDARY, bold=False)
|
||
|
||
# Chapter number
|
||
add_textbox(slide, Inches(0.8), Inches(1.8), Inches(11), Inches(0.8),
|
||
f"BAB {bab_num}", font_size=44, bold=True, color=WHITE)
|
||
|
||
# Chapter title
|
||
add_textbox(slide, Inches(0.8), Inches(2.8), Inches(11), Inches(1.5),
|
||
bab_title, font_size=32, bold=True, color=RGBColor(0xA0, 0xD2, 0xEB))
|
||
|
||
# Bottom accent line
|
||
add_shape_bg(slide, Inches(0.8), Inches(4.5), Inches(3), Inches(0.05), ACCENT)
|
||
|
||
# Book info
|
||
add_textbox(slide, Inches(0.8), Inches(5.5), Inches(11), Inches(0.4),
|
||
BOOK_TITLE, font_size=12, color=MEDIUM_TEXT)
|
||
add_textbox(slide, Inches(0.8), Inches(5.9), Inches(11), Inches(0.4),
|
||
AUTHOR, font_size=11, color=MEDIUM_TEXT)
|
||
|
||
|
||
def create_outcome_slide(prs, bab_num, outcome_text):
|
||
"""Create a Reader Outcome slide."""
|
||
slide = prs.slides.add_slide(prs.slide_layouts[6])
|
||
set_slide_bg(slide, WHITE)
|
||
|
||
# Header bar
|
||
add_shape_bg(slide, Inches(0), Inches(0), Inches(13.33), Inches(1.0), PRIMARY)
|
||
add_textbox(slide, Inches(0.8), Inches(0.2), Inches(11), Inches(0.6),
|
||
f"BAB {bab_num} — Capaian Pembelajaran", font_size=24, bold=True, color=WHITE)
|
||
|
||
# Outcome box
|
||
box = add_shape_bg(slide, Inches(1.0), Inches(1.8), Inches(11.33), Inches(3.5), LIGHT_BG)
|
||
|
||
# Icon-like label
|
||
add_textbox(slide, Inches(1.5), Inches(2.0), Inches(2), Inches(0.5),
|
||
"🎯 READER OUTCOME", font_size=14, bold=True, color=ACCENT)
|
||
|
||
# Outcome text
|
||
add_textbox(slide, Inches(1.5), Inches(2.7), Inches(10), Inches(2.5),
|
||
outcome_text, font_size=20, color=DARK_TEXT)
|
||
|
||
|
||
def create_content_slide(prs, bab_num, section_title, bullets, slide_subtitle=""):
|
||
"""Create a content slide with bullet points."""
|
||
slide = prs.slides.add_slide(prs.slide_layouts[6])
|
||
set_slide_bg(slide, WHITE)
|
||
|
||
# Header bar
|
||
add_shape_bg(slide, Inches(0), Inches(0), Inches(13.33), Inches(1.0), PRIMARY)
|
||
add_textbox(slide, Inches(0.8), Inches(0.15), Inches(11), Inches(0.7),
|
||
section_title, font_size=24, bold=True, color=WHITE)
|
||
|
||
if slide_subtitle:
|
||
add_textbox(slide, Inches(0.8), Inches(1.2), Inches(11), Inches(0.5),
|
||
slide_subtitle, font_size=14, bold=True, color=SECONDARY)
|
||
bullet_top = 1.8
|
||
else:
|
||
bullet_top = 1.3
|
||
|
||
add_bullet_slide(slide, bullets, Inches(1.0), Inches(bullet_top),
|
||
Inches(11), Inches(5.0), font_size=18, color=DARK_TEXT)
|
||
|
||
# Footer
|
||
add_textbox(slide, Inches(10.5), Inches(7.0), Inches(2.5), Inches(0.4),
|
||
f"Bab {bab_num}", font_size=10, color=MEDIUM_TEXT, alignment=PP_ALIGN.RIGHT)
|
||
|
||
|
||
def create_model_slide(prs, bab_num, model_title, description, components):
|
||
"""Create a model/framework slide."""
|
||
slide = prs.slides.add_slide(prs.slide_layouts[6])
|
||
set_slide_bg(slide, WHITE)
|
||
|
||
# Header bar
|
||
add_shape_bg(slide, Inches(0), Inches(0), Inches(13.33), Inches(1.0), PRIMARY)
|
||
add_textbox(slide, Inches(0.8), Inches(0.15), Inches(11), Inches(0.7),
|
||
f"📊 {model_title}", font_size=24, bold=True, color=WHITE)
|
||
|
||
# Description
|
||
add_textbox(slide, Inches(0.8), Inches(1.3), Inches(11), Inches(0.7),
|
||
description, font_size=16, color=MEDIUM_TEXT)
|
||
|
||
# Components in boxes
|
||
num_cols = min(len(components), 4)
|
||
box_width = (11.0 - 0.3 * (num_cols - 1)) / num_cols
|
||
start_left = 1.0
|
||
|
||
for i, (label, desc) in enumerate(components):
|
||
col = i % num_cols
|
||
row = i // num_cols
|
||
left = start_left + col * (box_width + 0.3)
|
||
top = 2.3 + row * 2.2
|
||
|
||
box = add_shape_bg(slide, Inches(left), Inches(top),
|
||
Inches(box_width), Inches(1.8), LIGHT_BG)
|
||
add_textbox(slide, Inches(left + 0.2), Inches(top + 0.15),
|
||
Inches(box_width - 0.4), Inches(0.5),
|
||
label, font_size=15, bold=True, color=PRIMARY)
|
||
add_textbox(slide, Inches(left + 0.2), Inches(top + 0.65),
|
||
Inches(box_width - 0.4), Inches(1.0),
|
||
desc, font_size=12, color=DARK_TEXT)
|
||
|
||
# Footer
|
||
add_textbox(slide, Inches(10.5), Inches(7.0), Inches(2.5), Inches(0.4),
|
||
f"Bab {bab_num}", font_size=10, color=MEDIUM_TEXT, alignment=PP_ALIGN.RIGHT)
|
||
|
||
|
||
def create_case_slide(prs, bab_num, case_title, points):
|
||
"""Create a case study slide."""
|
||
slide = prs.slides.add_slide(prs.slide_layouts[6])
|
||
set_slide_bg(slide, WHITE)
|
||
|
||
# Header bar with accent
|
||
add_shape_bg(slide, Inches(0), Inches(0), Inches(13.33), Inches(1.0), ACCENT)
|
||
add_textbox(slide, Inches(0.8), Inches(0.15), Inches(11), Inches(0.7),
|
||
f"📌 Studi Kasus: {case_title}", font_size=24, bold=True, color=WHITE)
|
||
|
||
add_bullet_slide(slide, points, Inches(1.0), Inches(1.3),
|
||
Inches(11), Inches(5.5), font_size=18, color=DARK_TEXT, bullet_char="●")
|
||
|
||
# Footer
|
||
add_textbox(slide, Inches(10.5), Inches(7.0), Inches(2.5), Inches(0.4),
|
||
f"Bab {bab_num}", font_size=10, color=MEDIUM_TEXT, alignment=PP_ALIGN.RIGHT)
|
||
|
||
|
||
def create_callout_slide(prs, bab_num, callouts):
|
||
"""Create a key takeaways / callout slide."""
|
||
slide = prs.slides.add_slide(prs.slide_layouts[6])
|
||
set_slide_bg(slide, LIGHT_BG)
|
||
|
||
# Header
|
||
add_shape_bg(slide, Inches(0), Inches(0), Inches(13.33), Inches(1.0), PRIMARY)
|
||
add_textbox(slide, Inches(0.8), Inches(0.15), Inches(11), Inches(0.7),
|
||
"⚠️ Poin Penting & Jebakan Kognitif", font_size=24, bold=True, color=WHITE)
|
||
|
||
add_bullet_slide(slide, callouts, Inches(1.0), Inches(1.4),
|
||
Inches(11), Inches(5.5), font_size=17, color=DARK_TEXT, bullet_char="⚡")
|
||
|
||
# Footer
|
||
add_textbox(slide, Inches(10.5), Inches(7.0), Inches(2.5), Inches(0.4),
|
||
f"Bab {bab_num}", font_size=10, color=MEDIUM_TEXT, alignment=PP_ALIGN.RIGHT)
|
||
|
||
|
||
def create_summary_slide(prs, bab_num, summary_points):
|
||
"""Create a chapter summary slide."""
|
||
slide = prs.slides.add_slide(prs.slide_layouts[6])
|
||
set_slide_bg(slide, PRIMARY)
|
||
|
||
# Accent bar top
|
||
add_shape_bg(slide, Inches(0), Inches(0), Inches(13.33), Inches(0.05), ACCENT)
|
||
|
||
add_textbox(slide, Inches(0.8), Inches(0.5), Inches(11), Inches(0.7),
|
||
f"Ringkasan Bab {bab_num}", font_size=28, bold=True, color=WHITE)
|
||
|
||
add_bullet_slide(slide, summary_points, Inches(1.0), Inches(1.5),
|
||
Inches(11), Inches(5.5), font_size=18, color=RGBColor(0xD0, 0xE8, 0xF0),
|
||
bullet_char="✓")
|
||
|
||
|
||
def create_discussion_slide(prs, bab_num, questions):
|
||
"""Create a discussion questions slide."""
|
||
slide = prs.slides.add_slide(prs.slide_layouts[6])
|
||
set_slide_bg(slide, WHITE)
|
||
|
||
add_shape_bg(slide, Inches(0), Inches(0), Inches(13.33), Inches(1.0), SECONDARY)
|
||
add_textbox(slide, Inches(0.8), Inches(0.15), Inches(11), Inches(0.7),
|
||
"💬 Pertanyaan Diskusi", font_size=28, bold=True, color=WHITE)
|
||
|
||
add_bullet_slide(slide, questions, Inches(1.0), Inches(1.4),
|
||
Inches(11), Inches(5.5), font_size=18, color=DARK_TEXT, bullet_char="❓")
|
||
|
||
|
||
# === ALL 18 CHAPTERS DATA ===
|
||
chapters = [
|
||
{
|
||
"num": 1,
|
||
"title": "Peran Sistem Informasi dalam Organisasi Modern",
|
||
"bagian": "BAGIAN I — Fondasi Sistem Informasi",
|
||
"outcome": "Memahami SI sebagai aset strategis organisasi, bukan sekadar alat teknis. Menjelaskan mengapa organisasi kehilangan keunggulan kompetitif tanpa SI yang efektif.",
|
||
"sections": [
|
||
("SI dalam Organisasi: Definisi dan Evolusi", [
|
||
"Sistem Informasi = kombinasi manusia, proses, teknologi, dan data",
|
||
"SI bukan hanya software — mencakup ekosistem pengambilan keputusan",
|
||
"Empat tipe SI: TPS, MIS, DSS, ESS",
|
||
"Konsep digital firm: organisasi yang sepenuhnya terintegrasi digital",
|
||
]),
|
||
("Piramida Nilai Informasi Organisasi (PVIO)", [
|
||
"Lima lapisan: Data → Informasi → Pengetahuan → Keputusan → Nilai Bisnis",
|
||
"Setiap lapisan membutuhkan proses transformasi yang berbeda",
|
||
"Tanpa transformasi, data mentah tidak menghasilkan nilai bisnis",
|
||
"SI berperan di setiap lapisan transisi piramida",
|
||
]),
|
||
("Evolusi Generasional SI (1960–2020an)", [
|
||
"Generasi 1 (1960an): Otomasi dasar, batch processing",
|
||
"Generasi 2–3: Database, real-time processing, MIS",
|
||
"Generasi 4–5: Client-server, internet, e-business",
|
||
"Generasi 6 (2020an): AI, cloud, IoT, platform economy",
|
||
]),
|
||
("SI sebagai Competitive Advantage", [
|
||
"Mekanisme: efisiensi, diferensiasi, inovasi, lock-in pelanggan",
|
||
"55% kegagalan proyek SI disebabkan tidak ada keselarasan strategis",
|
||
"Transformasi digital: SI bukan hanya mengoptimasi proses, tetapi menciptakan model bisnis baru",
|
||
]),
|
||
],
|
||
"model": ("Piramida PVIO", "Model 5 lapisan transformasi nilai informasi organisasi", [
|
||
("Data", "Fakta mentah tanpa konteks — angka, teks, gambar"),
|
||
("Informasi", "Data yang diproses, diorganisir, dan bermakna"),
|
||
("Pengetahuan", "Informasi + pengalaman + interpretasi kontekstual"),
|
||
("Keputusan", "Pemilihan tindakan berdasarkan pengetahuan"),
|
||
]),
|
||
"case": ("Telkom Indonesia: Transformasi Digital", [
|
||
"Dari perusahaan telekomunikasi tradisional ke digital ecosystem",
|
||
"Revenue stream baru: IndiHome, MyTelkomsel, Telkomsel Orbit",
|
||
"SI sebagai enabler transformasi bisnis, bukan hanya pendukung operasional",
|
||
"Bukti: SI strategis meningkatkan diversifikasi pendapatan",
|
||
]),
|
||
"callouts": [
|
||
"Miskonsepsi: 'SI hanya urusan IT' → SI adalah kapabilitas strategis manajerial",
|
||
"Miskonsepsi: 'SI = Software' → SI = Manusia + Proses + Teknologi + Data",
|
||
"Tingkat kegagalan SI tanpa keselarasan strategis: ~55%",
|
||
"Tantangan: Berpindah dari mindset 'SI sebagai beban biaya' ke 'SI sebagai investasi strategis'",
|
||
],
|
||
"summary": [
|
||
"SI telah berevolusi dari pendukung back-office menjadi kapabilitas strategis",
|
||
"Piramida PVIO menjelaskan bagaimana data ditransformasi menjadi nilai bisnis",
|
||
"SI yang efektif membutuhkan integrasi manusia, proses, teknologi, dan data",
|
||
"Era AI menjadikan SI semakin kritis bagi keunggulan kompetitif",
|
||
"Organisasi harus melihat SI sebagai investasi strategis, bukan beban teknis",
|
||
],
|
||
"questions": [
|
||
"Mengapa banyak organisasi masih melihat SI sebagai 'urusan IT'?",
|
||
"Berikan contoh nyata bagaimana SI menciptakan competitive advantage di industri Anda",
|
||
"Di level mana piramida PVIO organisasi Anda sering 'macet'?",
|
||
],
|
||
},
|
||
{
|
||
"num": 2,
|
||
"title": "Keselarasan Strategi Bisnis dan SI",
|
||
"bagian": "BAGIAN I — Fondasi Sistem Informasi",
|
||
"outcome": "Menganalisis keselarasan strategi bisnis-SI menggunakan model Henderson-Venkatraman. Memahami mengapa 55% proyek SI gagal akibat ketidakselarasan.",
|
||
"sections": [
|
||
("Keselarasan Strategis (Strategic Alignment)", [
|
||
"Alignment = keselarasan antara strategi bisnis dan strategi SI",
|
||
"Bukan one-time event, melainkan proses iteratif berkelanjutan",
|
||
"Organisasi dengan alignment formal: 2× tingkat keberhasilan proyek",
|
||
"55% kegagalan proyek SI berakar dari misalignment, bukan teknologi",
|
||
]),
|
||
("Model Henderson-Venkatraman", [
|
||
"4 domain: Business Strategy, IT Strategy, Organizational Infrastructure, IT Infrastructure",
|
||
"4 perspektif alignment: Strategy Execution, Technology Transformation, Competitive Potential, Service Level",
|
||
"Cross-domain linkage menghasilkan strategic fit dan functional integration",
|
||
]),
|
||
("Matriks McFarlan — Portfolio SI", [
|
||
"4 kuadran: Strategic, High Potential, Key Operational, Support",
|
||
"Membantu organisasi memprioritaskan investasi SI",
|
||
"Tidak semua SI bernilai strategis — klasifikasi menentukan alokasi sumber daya",
|
||
]),
|
||
("Tata Kelola SI: COBIT & ISO", [
|
||
"COBIT 2019: framework governance SI — memastikan SI mendukung tujuan bisnis",
|
||
"ISO 38500: standar tata kelola TI oleh Board",
|
||
"Governance ≠ Management: Board mengatur arah, IT mengelola operasi",
|
||
]),
|
||
],
|
||
"model": ("Henderson-Venkatraman Model", "Strategic alignment 4 domain × 4 perspektif", [
|
||
("Strategy Execution", "Strategi bisnis mengarahkan struktur organisasi dan SI"),
|
||
("Technology Transformation", "Strategi bisnis mengarahkan strategi TI langsung"),
|
||
("Competitive Potential", "IT Strategy membuka peluang bisnis baru"),
|
||
("Service Level", "Strategi TI menentukan infrastruktur organisasi"),
|
||
]),
|
||
"case": ("BRI: Alignment dalam Transformasi Digital", [
|
||
"BRI menerapkan questioning alignment di setiap tahap proyek",
|
||
"Integrasi strategi bisnis (inklusi keuangan) → strategi SI (BRImo, satellite banking)",
|
||
"Hasil: 30+ juta pengguna digital, penetrasi wilayah terpencil",
|
||
"Alignment kontinu menghasilkan konsistensi arah transformasi",
|
||
]),
|
||
"callouts": [
|
||
"55% kegagalan proyek SI bukan karena teknologi, tapi misalignment strategis",
|
||
"Alignment bukan one-time event — harus iteratif dan berkelanjutan",
|
||
"Organisasi tanpa governance formal SI: 2× lebih rentan kegagalan proyek",
|
||
"SIPD: studi kasus alignment pemerintah — standardisasi melalui SI nasional",
|
||
],
|
||
"summary": [
|
||
"Keselarasan strategi bisnis-SI adalah prediktor utama keberhasilan proyek SI",
|
||
"Model Henderson-Venkatraman menyediakan framework analisis alignment komprehensif",
|
||
"Matriks McFarlan membantu prioritisasi portfolio investasi SI",
|
||
"COBIT dan ISO 38500 menyediakan framework tata kelola SI terstruktur",
|
||
"Alignment harus dijaga secara iteratif, bukan dicapai sekali saja",
|
||
],
|
||
"questions": [
|
||
"Identifikasi satu proyek SI yang gagal — apakah penyebabnya misalignment?",
|
||
"Di perspektif mana (H-V Model) organisasi Anda paling lemah?",
|
||
"Bagaimana Anda akan meyakinkan Board untuk berinvestasi dalam SI governance?",
|
||
],
|
||
},
|
||
{
|
||
"num": 3,
|
||
"title": "Sistem Informasi dalam Fungsi Bisnis",
|
||
"bagian": "BAGIAN II — SI dalam Konteks Bisnis",
|
||
"outcome": "Menganalisis kontribusi SI pada 4 fungsi bisnis utama. Mengidentifikasi information silos dan dampaknya terhadap efisiensi organisasi.",
|
||
"sections": [
|
||
("Ekosistem SI Lintas Fungsi", [
|
||
"4 fungsi utama: Marketing, Keuangan, SDM, Operasi",
|
||
"Masing-masing memiliki SI spesifik dengan kapabilitas unik",
|
||
"Integrasi lintas fungsi adalah pengali nilai (value multiplier)",
|
||
]),
|
||
("SI per Fungsi Bisnis", [
|
||
"Marketing: CRM, digital marketing analytics, customer segmentation",
|
||
"Keuangan: Financial systems, treasury management, compliance reporting",
|
||
"SDM: HRIS, talent analytics, payroll, performance management",
|
||
"Operasi: SCM, procurement, inventory management, quality control",
|
||
]),
|
||
("Information Silos: Fenomena Nyata", [
|
||
"86% masalah proses disebabkan information silos, bukan kekurangan SI",
|
||
"64% perusahaan menengah Indonesia punya gap digitisasi lintas fungsi signifikan",
|
||
"73% data organisasi adalah dark data (dikumpulkan tapi tidak digunakan)",
|
||
"Silos menciptakan asimetri informasi yang merusak pengambilan keputusan",
|
||
]),
|
||
],
|
||
"model": ("Cross-Functional SI Ecosystem", "Integrasi SI 4 fungsi bisnis utama", [
|
||
("Marketing SI", "CRM, Analytics, Segmentasi — Revenue & Customer Value"),
|
||
("Finance SI", "Treasury, Reporting, Compliance — Cost & Risk Control"),
|
||
("HR SI", "HRIS, Talent Analytics — Productivity & Retention"),
|
||
("Operations SI", "SCM, Procurement, QC — Efficiency & Delivery"),
|
||
]),
|
||
"case": ("BCA: Integrasi Sistem Lintas Fungsi", [
|
||
"BCA mengintegrasikan CRM, core banking, dan operations dalam satu platform",
|
||
"Data pelanggan tersedia real-time di semua touchpoint (cabang, mobile, ATM)",
|
||
"Eliminasi silos menghasilkan customer experience konsisten",
|
||
"Produktivitas meningkat 30%+ melalui single source of truth",
|
||
]),
|
||
"callouts": [
|
||
"86% masalah proses = information silos, bukan kekurangan teknologi",
|
||
"73% data organisasi adalah dark data — dikumpulkan tapi tidak pernah dianalisis",
|
||
"Miskonsepsi: 'Setiap departemen bisa optimasi SI secara independen' → Salah",
|
||
"Integrasi lintas fungsi adalah value multiplier, bukan cost center",
|
||
],
|
||
"summary": [
|
||
"SI beroperasi di 4 fungsi bisnis utama dengan kapabilitas spesifik",
|
||
"Information silos adalah masalah #1 — lebih besar dari kekurangan SI",
|
||
"73% data organisasi adalah dark data yang tidak dimanfaatkan",
|
||
"Integrasi lintas fungsi menghasilkan efek pengali nilai",
|
||
"KPI informasi per fungsi mengukur efektivitas SI",
|
||
],
|
||
"questions": [
|
||
"Identifikasi silo informasi di organisasi Anda — apa dampaknya?",
|
||
"Fungsi bisnis mana yang paling underserved oleh SI di Indonesia?",
|
||
"Bagaimana Anda mengukur ROI integrasi SI lintas fungsi?",
|
||
],
|
||
},
|
||
{
|
||
"num": 4,
|
||
"title": "Sistem Perusahaan dan Integrasi Lintas Fungsi",
|
||
"bagian": "BAGIAN II — SI dalam Konteks Bisnis",
|
||
"outcome": "Menjelaskan arsitektur enterprise systems (ERP/CRM/SCM). Membedakan pendekatan integrasi dan memahami faktor keberhasilan implementasi.",
|
||
"sections": [
|
||
("Enterprise Systems Overview", [
|
||
"Tiga platform: ERP (inti), CRM (pelanggan), SCM (pemasok/rantai pasok)",
|
||
"ERP sebagai backbone integrasi proses bisnis",
|
||
"Data warehouse sebagai lapisan integrasi analitis",
|
||
]),
|
||
("Arsitektur Integrasi Enterprise", [
|
||
"ETL (Extract-Transform-Load) sebagai jembatan data antar sistem",
|
||
"Data warehouse menyatukan data dari ERP, CRM, SCM",
|
||
"BI layer menganalisis data terintegrasi untuk decision-making",
|
||
"Integrasi real-time vs batch: trade-off kecepatan dan kompleksitas",
|
||
]),
|
||
("Tantangan Implementasi Enterprise System", [
|
||
"55-75% tingkat kegagalan implementasi ERP global",
|
||
"67% melebihi anggaran dan timeline",
|
||
"67% masalah change management",
|
||
"5 mode kegagalan utama: scope creep, data quality, resistance, training, governance",
|
||
]),
|
||
],
|
||
"model": ("Enterprise Integration Model", "ERP core + CRM/SCM + Data Warehouse + BI", [
|
||
("ERP (Core)", "Integrasi proses bisnis: Finance, HR, Manufacturing, Procurement"),
|
||
("CRM", "Customer lifecycle: Marketing, Sales, Service, Analytics"),
|
||
("SCM", "Supply chain: Planning, Sourcing, Manufacturing, Delivery"),
|
||
("DW + BI", "Analytics layer: ETL, Reporting, Dashboard, Insights"),
|
||
]),
|
||
"case": ("Hershey vs P&G: Teknologi Sama, Hasil Berbeda", [
|
||
"Hershey: Big Bang SAP → kerugian $150M, kehilangan 12% penjualan musim Halloween",
|
||
"P&G: Implementasi bertahap → sukses, integrasi global 80+ negara",
|
||
"Teknologi identik — perbedaan 100% di pendekatan implementasi",
|
||
"Lesson: Change management dan phased approach menentukan keberhasilan",
|
||
]),
|
||
"callouts": [
|
||
"55-75% implementasi ERP gagal secara global — bukan masalah kecil",
|
||
"Hershey vs P&G: bukti bahwa teknologi ≠ keberhasilan; pendekatan = segalanya",
|
||
"Change management adalah faktor keberhasilan kritis, bukan teknologi",
|
||
"67% proyek ERP melebihi anggaran dan timeline yang direncanakan",
|
||
],
|
||
"summary": [
|
||
"Enterprise systems (ERP/CRM/SCM) adalah backbone integrasi organisasi modern",
|
||
"Data warehouse + BI menyediakan lapisan analitis di atas sistem transaksional",
|
||
"55-75% implementasi gagal — sebagian besar karena faktor manusia dan organisasi",
|
||
"Phased approach + change management = resep keberhasilan implementasi",
|
||
"Kasus Hershey vs P&G membuktikan teknologi yang sama bisa menghasilkan outcome berlawanan",
|
||
],
|
||
"questions": [
|
||
"Mengapa Big Bang approach lebih berisiko daripada phased approach?",
|
||
"Apa peran change champion dalam implementasi ERP?",
|
||
"Identifikasi 3 hidden costs implementasi enterprise system yang sering diabaikan",
|
||
],
|
||
},
|
||
{
|
||
"num": 5,
|
||
"title": "Data dan Informasi sebagai Aset Organisasi",
|
||
"bagian": "BAGIAN III — Data, Informasi, dan Keputusan",
|
||
"outcome": "Menjelaskan hierarki DIKW; mengevaluasi dimensi kualitas data; memahami data governance lifecycle dan implikasi UU PDP.",
|
||
"sections": [
|
||
("Hierarki DIKW", [
|
||
"Data → Informasi → Pengetahuan → Kebijaksanaan",
|
||
"Setiap lapisan memiliki risiko: Garbage In → Bias → Knowledge Decay",
|
||
"Transformasi antar lapisan membutuhkan proses dan konteks",
|
||
]),
|
||
("Dimensi Kualitas Data", [
|
||
"Accuracy: data sesuai realitas",
|
||
"Completeness: data lengkap tanpa missing values kritis",
|
||
"Consistency: data konsisten di semua sistem",
|
||
"Timeliness: data tersedia tepat waktu untuk keputusan",
|
||
]),
|
||
("Data Lifecycle Management (6 Tahap)", [
|
||
"Collection → Storage → Processing → Sharing → Archiving → Destruction",
|
||
"Setiap tahap memiliki kebijakan, kontrol, dan tanggung jawab",
|
||
"UU PDP (2022) mengatur aspek legal di setiap tahap lifecycle",
|
||
]),
|
||
("Data sebagai Aset Neraca", [
|
||
"73% data organisasi = dark data (dikumpulkan tapi tidak digunakan)",
|
||
"Data governance: kemampuan organisasi mengelola data sebagai aset",
|
||
"UU PDP mengubah data dari 'sumber daya' menjadi 'tanggung jawab hukum'",
|
||
"Pendekatan valuasi data: data sebagai intangible asset di neraca",
|
||
]),
|
||
],
|
||
"model": ("DIKW Hierarchy + Risk Layer", "5 lapisan transformasi dengan risiko di setiap level", [
|
||
("Data", "Fakta mentah — Risiko: GIGO (Garbage In, Garbage Out)"),
|
||
("Informasi", "Data + konteks — Risiko: Misinterpretasi"),
|
||
("Pengetahuan", "Info + pengalaman — Risiko: Knowledge Decay"),
|
||
("Kebijaksanaan", "Judgment + values — Risiko: Bias kognitif"),
|
||
]),
|
||
"case": ("Satu Data Indonesia: Integrasi Data Publik", [
|
||
"Inisiatif nasional mengintegrasikan data antar kementerian/lembaga",
|
||
"Problem: silos data pemerintah menghambat evidence-based policy",
|
||
"Solusi: standar data nasional, portal data terbuka, interoperabilitas",
|
||
"Tantangan: kualitas data, kapasitas SDM, resistensi birokrasi",
|
||
]),
|
||
"callouts": [
|
||
"73% data organisasi = dark data — harta karun yang tidak digali",
|
||
"UU PDP (2022): transformasi hukum — data bukan lagi free resource",
|
||
"Kualitas data buruk → keputusan buruk → kerugian organisasi",
|
||
"Miskonsepsi: 'Semakin banyak data = semakin baik' → Data harus berkualitas",
|
||
],
|
||
"summary": [
|
||
"DIKW hierarchy menjelaskan transformasi data mentah menjadi kebijaksanaan",
|
||
"4 dimensi kualitas data: accuracy, completeness, consistency, timeliness",
|
||
"Data lifecycle management memastikan pengelolaan data di setiap fase",
|
||
"Data governance adalah kapabilitas organisasi, bukan hanya kebijakan IT",
|
||
"UU PDP mengubah paradigma data menjadi tanggung jawab hukum",
|
||
],
|
||
"questions": [
|
||
"Bagaimana Anda mengukur kualitas data di organisasi Anda?",
|
||
"Apa implikasi UU PDP terhadap praktik pengumpulan data saat ini?",
|
||
"Seberapa besar proporsi dark data di organisasi Anda?",
|
||
],
|
||
},
|
||
{
|
||
"num": 6,
|
||
"title": "Pengambilan Keputusan Berbasis Data",
|
||
"bagian": "BAGIAN III — Data, Informasi, dan Keputusan",
|
||
"outcome": "Menerapkan model keputusan Simon; membedakan tipe keputusan terstruktur hingga tidak terstruktur; memahami bounded rationality dan efek HiPPO.",
|
||
"sections": [
|
||
("Model Keputusan Simon (4 Fase)", [
|
||
"Intelligence: identifikasi masalah dan peluang",
|
||
"Design: eksplorasi dan desain alternatif solusi",
|
||
"Choice: pemilihan alternatif terbaik",
|
||
"Implementation: eksekusi dan monitoring hasil",
|
||
"Setiap fase membutuhkan dukungan SI yang berbeda",
|
||
]),
|
||
("Tipologi Keputusan", [
|
||
"Structured: terdefinisi, rutin, bisa diotomasi (contoh: reorder point)",
|
||
"Semi-structured: sebagian terstruktur (contoh: alokasi anggaran)",
|
||
"Unstructured: novel, ambigu, sarat nilai (contoh: akuisisi perusahaan)",
|
||
]),
|
||
("Data-Driven Decision Making (DDDM)", [
|
||
"McKinsey: DDDM → 23% profitabilitas lebih tinggi",
|
||
"Hanya 20% perusahaan menggunakan data secara sistematis",
|
||
"49% keputusan masih menggunakan HiPPO Effect (Highest Paid Person's Opinion)",
|
||
"Bounded rationality: manusia tidak memaksimalkan, melainkan satisficing",
|
||
]),
|
||
("Bias Kognitif dalam Keputusan", [
|
||
"Confirmation bias: mencari data yang mengonfirmasi keyakinan — berkurang 45% dengan data support",
|
||
"Anchoring bias: terlalu terpaku pada informasi awal",
|
||
"Availability bias: mengandalkan informasi yang mudah diingat",
|
||
"SI berperan mengurangi bias melalui data objektif dan terstruktur",
|
||
]),
|
||
],
|
||
"model": ("Simon's Four-Phase Decision Model", "4 fase pengambilan keputusan dengan dukungan SI", [
|
||
("Intelligence", "Identifikasi masalah — SI: monitoring, alerting, dashboard"),
|
||
("Design", "Eksplorasi alternatif — SI: modeling, simulation, what-if analysis"),
|
||
("Choice", "Pilih tindakan — SI: scoring, ranking, decision support"),
|
||
("Implementation", "Eksekusi & monitor — SI: tracking, feedback, reporting"),
|
||
]),
|
||
"case": ("SIPD: Dari Political ke Data-Driven Budgeting", [
|
||
"SIPD pemerintah daerah: transisi dari penganggaran politis ke berbasis data",
|
||
"Dashboard terintegrasi: realisasi anggaran real-time per OPD",
|
||
"Hasil: transparansi meningkat, inefisiensi anggaran terdeteksi lebih cepat",
|
||
"Tantangan: resistensi dari pihak yang diuntungkan sistem lama",
|
||
]),
|
||
"callouts": [
|
||
"McKinsey: DDDM → profitabilitas 23% lebih tinggi",
|
||
"49% keputusan masih pakai HiPPO — opini orang terbayar tertinggi",
|
||
"Miskonsepsi: 'Lebih banyak data = keputusan lebih baik' → Data harus relevan & tepat waktu",
|
||
"Confirmation bias berkurang 45% dengan dukungan data terstruktur",
|
||
],
|
||
"summary": [
|
||
"Model Simon menyediakan framework 4 fase pengambilan keputusan",
|
||
"Keputusan terstruktur bisa diotomasi; unstructured membutuhkan judgment manusia",
|
||
"DDDM menghasilkan 23% profitabilitas lebih tinggi (McKinsey)",
|
||
"Bias kognitif merusak kualitas keputusan — SI membantu menguranginya",
|
||
"Transisi dari HiPPO ke data-driven membutuhkan perubahan budaya organisasi",
|
||
],
|
||
"questions": [
|
||
"Di organisasi Anda, seberapa besar pengaruh HiPPO Effect?",
|
||
"Keputusan mana yang paling cocok diotomasi vs tetap butuh judgment manusia?",
|
||
"Bagaimana Anda mendeteksi confirmation bias dalam proses keputusan tim?",
|
||
],
|
||
},
|
||
{
|
||
"num": 7,
|
||
"title": "Business Intelligence dan Analitik Bisnis",
|
||
"bagian": "BAGIAN IV — Analisis dan Pemodelan",
|
||
"outcome": "Memahami spektrum maturitas analitik; memanfaatkan analytics untuk competitive advantage dari descriptive hingga prescriptive.",
|
||
"sections": [
|
||
("Spektrum Maturitas Analitik", [
|
||
"Descriptive: Apa yang terjadi? (laporan, dashboard)",
|
||
"Diagnostic: Mengapa terjadi? (drill-down, root cause analysis)",
|
||
"Predictive: Apa yang akan terjadi? (forecasting, ML models)",
|
||
"Prescriptive: Apa yang harus dilakukan? (optimization, simulation)",
|
||
"Keunggulan kompetitif meningkat seiring level maturitas",
|
||
]),
|
||
("Arsitektur Data Warehouse & ETL", [
|
||
"Source systems → ETL process → Data Warehouse → BI tools",
|
||
"ETL: Extract (ambil data), Transform (bersihkan & format), Load (simpan di DW)",
|
||
"DW menyimpan data historis terintegrasi untuk analisis",
|
||
]),
|
||
("Reporting vs Self-Service Analytics", [
|
||
"Reporting: backward-looking, terjadwal, standar format",
|
||
"Self-Service: eksploratif, on-demand, user-driven",
|
||
"Tren: demokratisasi analytics ke business users (bukan hanya IT)",
|
||
]),
|
||
("Real-Time Analytics", [
|
||
"Memungkinkan keputusan operasional instan (pricing, inventory, routing)",
|
||
"Event-driven architecture untuk data streaming",
|
||
"Kompleksitas infrastruktur vs value of speed",
|
||
]),
|
||
],
|
||
"model": ("Analytics Maturity Spectrum", "4 level maturitas analitik dan business impact", [
|
||
("Descriptive", "What happened? — Dashboard, KPI reports, standard metrics"),
|
||
("Diagnostic", "Why? — Drill-down, correlation analysis, root cause"),
|
||
("Predictive", "What will happen? — ML models, forecasting, propensity scoring"),
|
||
("Prescriptive", "What to do? — Optimization, simulation, recommendation engine"),
|
||
]),
|
||
"case": ("Netflix: $1B Recommendation Engine", [
|
||
"Recommendation engine menghasilkan $1B+ nilai per tahun",
|
||
"75% konten yang ditonton berasal dari rekomendasi AI",
|
||
"Predictive analytics menentukan keputusan investasi konten $17B",
|
||
"Analytics mengubah Netflix dari distributor menjadi studio berbasis data",
|
||
]),
|
||
"callouts": [
|
||
"Netflix: $1B+ nilai dari recommendation engine — predictive analytics at scale",
|
||
"Mayoritas organisasi masih di level descriptive (dashboard & reporting)",
|
||
"Competitive advantage terbesar di level predictive dan prescriptive",
|
||
"Gap skill dan data quality menghalangi transisi ke advanced analytics",
|
||
],
|
||
"summary": [
|
||
"4 level maturitas analitik: descriptive → diagnostic → predictive → prescriptive",
|
||
"Data warehouse + ETL adalah fondasi arsitektur BI",
|
||
"Self-service analytics mendemokratisasi data untuk business users",
|
||
"Real-time analytics memungkinkan keputusan operasional instan",
|
||
"Netflix membuktikan ROI analytics at scale ($1B+ dari recommendation engine)",
|
||
],
|
||
"questions": [
|
||
"Di level mana maturitas analytics organisasi Anda saat ini?",
|
||
"Apa hambatan terbesar untuk memajukan level analytics?",
|
||
"Proses bisnis mana yang paling diuntungkan dari predictive analytics?",
|
||
],
|
||
},
|
||
{
|
||
"num": 8,
|
||
"title": "Analisis Permasalahan Organisasi",
|
||
"bagian": "BAGIAN IV — Analisis dan Pemodelan",
|
||
"outcome": "Menerapkan framework problem framing; menghindari premature solutionism; membedakan akar masalah dari gejala.",
|
||
"sections": [
|
||
("Problem Framing vs Symptom Addressing", [
|
||
"45% kegagalan SI karena salah mendefinisikan masalah",
|
||
"Organisasi sering langsung ke solusi tanpa memahami masalah",
|
||
"Problem framing: investasi waktu yang menghemat kelipatan di solusi",
|
||
]),
|
||
("Analisis Fishbone (Ishikawa)", [
|
||
"6 kategori penyebab: Manusia, Proses, Teknologi, Lingkungan, Material, Metode",
|
||
"Visual mapping dari efek ke penyebab",
|
||
"Membantu tim melihat masalah dari perspektif multidimensional",
|
||
]),
|
||
("Five-Why (5W) Root Cause Analysis", [
|
||
"Teknik iterative questioning: 'Mengapa?' berulang sampai akar masalah",
|
||
"Sederhana namun efektif untuk masalah non-trivial",
|
||
"Hindari berhenti di gejala — terus gali hingga akar penyebab",
|
||
]),
|
||
("Gap Analysis & Systems Thinking", [
|
||
"Gap Analysis: kondisi saat ini vs kondisi yang diinginkan",
|
||
"Systems Thinking: memahami interkoneksi dan feedback loops",
|
||
"Masalah sering interdependen — solusi parsial bisa memperburuk",
|
||
]),
|
||
],
|
||
"model": ("Framework Analisis Masalah", "3 tool utama untuk root cause analysis", [
|
||
("Fishbone", "Pemetaan visual penyebab di 6 kategori → Identifikasi akar"),
|
||
("Five-Why", "Questioning iteratif → Temukan root cause, bukan gejala"),
|
||
("Gap Analysis", "Current state vs Desired state → Prioritisasi intervensi"),
|
||
("Systems Thinking", "Interkoneksi & feedback loops → Solusi holistik"),
|
||
]),
|
||
"case": ("Rumah Sakit: Bottleneck Analysis", [
|
||
"Analisis proses rumah sakit mengungkap 86% waktu = non-value-adding",
|
||
"Problem awal: 'antrian terlalu panjang' → Root cause: proses registrasi berlapis",
|
||
"Fishbone analysis menemukan 4 penyebab utama yang saling berkaitan",
|
||
"Solusi: redesain proses sebelum otomasi → pengurangan waktu tunggu 60%",
|
||
]),
|
||
"callouts": [
|
||
"45% kegagalan SI karena salah mendefinisikan masalah — premature solutionism",
|
||
"86% waktu proses rumah sakit = non-value-adding activities",
|
||
"Miskonsepsi: 'Kita sudah tahu masalahnya' → Organisasi jarang menggali cukup dalam",
|
||
"Rule: Investasi 20% waktu di problem framing menghemat 80% waktu di solusi",
|
||
],
|
||
"summary": [
|
||
"45% kegagalan SI berasal dari definisi masalah yang salah",
|
||
"Fishbone, Five-Why, dan Gap Analysis adalah 3 tool utama problem framing",
|
||
"Systems Thinking membantu memahami interkoneksi masalah",
|
||
"Gejala ≠ akar masalah — proses RS membuktikan pentingnya analisis mendalam",
|
||
"Problem framing yang benar menghemat biaya dan waktu implementasi",
|
||
],
|
||
"questions": [
|
||
"Kapan terakhir kali organisasi Anda melakukan Five-Why analysis?",
|
||
"Identifikasi satu gejala yang selama ini dianggap sebagai masalah utama",
|
||
"Bagaimana Anda membedakan root cause dari gejala dalam konteks SI?",
|
||
],
|
||
},
|
||
{
|
||
"num": 9,
|
||
"title": "Kebutuhan Informasi Manajerial",
|
||
"bagian": "BAGIAN IV — Analisis dan Pemodelan",
|
||
"outcome": "Memetakan kebutuhan informasi per level manajemen; mendesain SI yang menyampaikan informasi tepat ke peran yang tepat.",
|
||
"sections": [
|
||
("Piramida Kebutuhan Informasi", [
|
||
"3 level: Operasional (bawah), Taktikal (tengah), Strategis (atas)",
|
||
"Setiap level memiliki karakteristik informasi yang berbeda",
|
||
"Mismatch = SI underutilization — informasi salah ke orang salah",
|
||
]),
|
||
("Karakteristik Informasi per Level", [
|
||
"Strategis: jarang, agregat, sumber eksternal, berorientasi masa depan",
|
||
"Taktikal: periodik, departmental, campuran internal/eksternal, menengah",
|
||
"Operasional: real-time/harian, transaksional, internal, segera",
|
||
]),
|
||
("Pemetaan Kapabilitas SI ke Kebutuhan", [
|
||
"ESS & BI untuk level strategis — dashboard agregat, tren, benchmarking",
|
||
"MIS & DSS untuk level taktikal — laporan periodik, analisis departmental",
|
||
"TPS untuk level operasional — input transaksi, tracking, alerting",
|
||
"Desain SI harus dimulai dari kebutuhan informasi, bukan dari teknologi",
|
||
]),
|
||
],
|
||
"model": ("Piramida Kebutuhan Informasi", "3 level manajemen × karakteristik informasi", [
|
||
("Strategis (Top)", "Frekuensi rendah, agregat, eksternal, masa depan — ESS & BI"),
|
||
("Taktikal (Mid)", "Periodik, departmental, mixed, menengah — MIS & DSS"),
|
||
("Operasional (Low)", "Real-time, transaksional, internal, segera — TPS"),
|
||
]),
|
||
"case": ("SI HR Pemerintah: Data Salah ke Level Salah", [
|
||
"Sistem HR memberikan data transaksional ke level eksekutif",
|
||
"Eksekutif membutuhkan summary analytics, bukan detail absensi",
|
||
"Akibat: SI dianggap 'tidak berguna' → underutilization & resistance",
|
||
"Solusi: redesain dashboard per level — adoption meningkat 3×",
|
||
]),
|
||
"callouts": [
|
||
"SI underutilization sering karena informasi salah dikirim ke level salah",
|
||
"Eksekutif tidak butuh detail transaksi — butuh insight strategis",
|
||
"Staff operasional tidak butuh summary quarterly — butuh data real-time",
|
||
"Desain SI harus demand-driven (dari kebutuhan), bukan supply-driven (dari teknologi)",
|
||
],
|
||
"summary": [
|
||
"3 level manajemen memiliki kebutuhan informasi fundamentally berbeda",
|
||
"Mismatch informasi-level adalah penyebab utama SI underutilization",
|
||
"ESS/BI untuk strategis, MIS/DSS untuk taktikal, TPS untuk operasional",
|
||
"Desain SI harus dimulai dari mapping kebutuhan informasi per role",
|
||
"Right information to right role = realisasi nilai SI",
|
||
],
|
||
"questions": [
|
||
"Identifikasi mismatch informasi-level di organisasi Anda",
|
||
"Apakah dashboard SI Anda menampilkan informasi yang tepat per level?",
|
||
"Bagaimana Anda memetakan kebutuhan informasi tanpa bias teknologi?",
|
||
],
|
||
},
|
||
{
|
||
"num": 10,
|
||
"title": "Pemodelan Proses Bisnis",
|
||
"bagian": "BAGIAN V — Perancangan dan Solusi",
|
||
"outcome": "Menerapkan pemodelan proses AS-IS ke TO-BE; mengidentifikasi bottleneck dan peluang optimasi.",
|
||
"sections": [
|
||
("Fundamentals Pemodelan Proses", [
|
||
"Proses bisnis = serangkaian aktivitas yang menghasilkan output bernilai",
|
||
"AS-IS: kondisi aktual saat ini (bukan SOP ideal)",
|
||
"TO-BE: kondisi target setelah perbaikan/otomasi",
|
||
"AS-IS ≠ SOP — banyak organisasi tidak tahu proses aktualnya",
|
||
]),
|
||
("Teknik Pemodelan", [
|
||
"Swimlane diagram: menunjukkan cross-function dependencies",
|
||
"BPMN (Basic): events, activities, gateways, flow",
|
||
"Value analysis: aktivitas value-adding vs non-value-adding",
|
||
]),
|
||
("Bottleneck & Value Analysis", [
|
||
"Bottleneck = titik penyempitan yang menahan seluruh proses",
|
||
"Value-adding vs non-value-adding: identifikasi waste",
|
||
"Biasanya 30-40% aktivitas proses transaksi adalah non-value-adding",
|
||
"BPR (Business Process Reengineering) bisa mencapai efisiensi 60-90%",
|
||
]),
|
||
],
|
||
"model": ("AS-IS → TO-BE Process Modeling", "Metodologi optimasi proses bisnis", [
|
||
("AS-IS Mapping", "Dokumentasi proses aktual — bukan SOP, bukan ideal"),
|
||
("Bottleneck ID", "Identifikasi penyempitan dan waste dalam proses"),
|
||
("TO-BE Design", "Proses target yang dioptimasi — eliminasi waste"),
|
||
("Automation Layer", "Otomasi proses yang sudah dioptimasi — bukan yang lama"),
|
||
]),
|
||
"case": ("RS: 86% Non-Value-Adding Activities", [
|
||
"Swimlane modeling mengungkap 86% waktu proses = non-value-adding",
|
||
"Registrasi berulang, antrian manual, transfer dokumen fisik",
|
||
"TO-BE design: digitalisasi first-contact registration + electronic referral",
|
||
"Hasil: waktu tunggu berkurang 60%, kepuasan pasien meningkat signifikan",
|
||
]),
|
||
"callouts": [
|
||
"30-40% aktivitas proses transaksi biasanya non-value-adding (waste)",
|
||
"Miskonsepsi: 'Otomasi proses saat ini' → Reality: redesain dulu, baru otomasi",
|
||
"Otomasi proses buruk = waste amplifier yang mahal",
|
||
"BPR: 60-90% efisiensi bisa dicapai dengan pemahaman proses yang benar",
|
||
],
|
||
"summary": [
|
||
"AS-IS modeling mengungkap realitas proses aktual (bukan SOP ideal)",
|
||
"30-40% aktivitas proses biasanya adalah waste non-value-adding",
|
||
"Swimlane dan BPMN adalah tool utama pemodelan proses",
|
||
"TO-BE design harus mengoptimasi dulu, baru otomasi",
|
||
"Otomasi proses buruk = expensive waste amplifier",
|
||
],
|
||
"questions": [
|
||
"Apakah organisasi Anda pernah melakukan AS-IS mapping (bukan review SOP)?",
|
||
"Proses bisnis mana yang paling banyak waste-nya?",
|
||
"Bagaimana Anda meyakinkan manajemen untuk investasi di process redesign?",
|
||
],
|
||
},
|
||
{
|
||
"num": 11,
|
||
"title": "Perancangan Konseptual Sistem Informasi",
|
||
"bagian": "BAGIAN V — Perancangan dan Solusi",
|
||
"outcome": "Menerjemahkan kebutuhan bisnis menjadi spesifikasi teknis; menjembatani bahasa bisnis dan IT.",
|
||
"sections": [
|
||
("Perancangan Konseptual SI", [
|
||
"Bridge antara kebutuhan bisnis (Bab 10) dan implementasi teknis",
|
||
"Menerjemahkan 'apa yang bisnis butuhkan' ke 'apa yang harus dibangun'",
|
||
"Designer brief: dokumen handoff kritis dari bisnis ke IT",
|
||
]),
|
||
("Model IPO (Input → Process → Output)", [
|
||
"Pattern desain SI fundamental: semua SI mengikuti pola IPO",
|
||
"Input: data apa yang masuk? Dari mana? Siapa memasukkan?",
|
||
"Process: apa transformasi/business rules yang diterapkan?",
|
||
"Output: informasi apa yang dihasilkan? Untuk siapa?",
|
||
]),
|
||
("Three-Tier Architecture", [
|
||
"Presentation tier: user interface — apa yang dilihat pengguna",
|
||
"Business Logic tier: aturan bisnis — bagaimana data diproses",
|
||
"Data tier: database — di mana data disimpan",
|
||
"Separation of concerns mencegah tight coupling dan memudahkan maintenance",
|
||
]),
|
||
("Business Rules sebagai Intelligence Layer", [
|
||
"Business rules = aturan yang menentukan bagaimana organisasi beroperasi",
|
||
"Contoh: 'Jika pesanan > 100 juta, butuh persetujuan direktur'",
|
||
"Rules harus didokumentasikan terpisah dari code",
|
||
"ERD (Entity-Relationship Diagram) untuk pemodelan data",
|
||
]),
|
||
],
|
||
"model": ("Three-Tier Architecture", "Separasi concerns dalam desain SI", [
|
||
("Presentation", "UI/UX — apa yang pengguna lihat dan interaksi"),
|
||
("Business Logic", "Aturan & proses — bagaimana data ditransformasi"),
|
||
("Data Tier", "Database & storage — di mana data disimpan aman"),
|
||
]),
|
||
"case": ("Gap Bisnis-IT: Lost in Translation", [
|
||
"Bisnis minta 'sistem yang mudah digunakan' → IT bangun fitur kompleks",
|
||
"Tanpa designer brief: 60% fitur tidak sesuai kebutuhan aktual",
|
||
"Solusi: structured requirements document dengan IPO mapping per fitur",
|
||
"Lesson: translation layer antara bisnis dan IT mencegah costly misinterpretation",
|
||
]),
|
||
"callouts": [
|
||
"Miskonsepsi: 'Requirements = Design' → Salah: butuh translation layer",
|
||
"Three-tier architecture mencegah tight coupling dan memudahkan maintenance",
|
||
"Designer brief: dokumen paling kritis dalam transisi bisnis → IT",
|
||
"IPO model: semua SI mengikuti pattern Input → Process → Output",
|
||
],
|
||
"summary": [
|
||
"Perancangan konseptual menjembatani kebutuhan bisnis dan implementasi teknis",
|
||
"IPO model: pattern fundamental desain semua SI",
|
||
"Three-tier architecture memisahkan presentation, logic, dan data",
|
||
"Business rules harus didokumentasikan terpisah dari implementasi",
|
||
"Designer brief mencegah costly misinterpretation bisnis → IT",
|
||
],
|
||
"questions": [
|
||
"Siapa yang membuat designer brief di organisasi Anda?",
|
||
"Bagaimana Anda memastikan bisnis dan IT 'berbicara bahasa yang sama'?",
|
||
"Identifikasi satu proyek SI yang gagal karena translation gap bisnis-IT",
|
||
],
|
||
},
|
||
{
|
||
"num": 12,
|
||
"title": "Alternatif Solusi: Custom, Komersial, dan Cloud",
|
||
"bagian": "BAGIAN V — Perancangan dan Solusi",
|
||
"outcome": "Membandingkan Make vs Buy vs SaaS; menerapkan framework TCO untuk seleksi solusi.",
|
||
"sections": [
|
||
("Make: Custom Development", [
|
||
"Kontrol penuh, fleksibilitas maksimal",
|
||
"Biaya tertinggi, risiko tertinggi, timeline terpanjang",
|
||
"Cocok untuk proses bisnis unik yang tidak ada di pasar",
|
||
]),
|
||
("Buy: COTS (Commercial Off-The-Shelf)", [
|
||
"Standardisasi, deployment lebih cepat, less flexibility",
|
||
"Best practices industri sudah embedded dalam produk",
|
||
"Cocok untuk proses standar (accounting, HR, email)",
|
||
]),
|
||
("Cloud/SaaS Solutions", [
|
||
"Upfront cost rendah, fleksibilitas operasional, subscription model",
|
||
"Risiko: vendor dependency, data sovereignty, exit costs",
|
||
"Memungkinkan UMKM akses tools enterprise-grade dengan biaya terjangkau",
|
||
]),
|
||
("Total Cost of Ownership (TCO) 5 Tahun", [
|
||
"TCO = biaya akuisisi + operasional + tersembunyi",
|
||
"TCO 5 tahun biasanya 2.5-3× biaya akuisisi awal",
|
||
"Hidden costs: training, migrasi data, productivity loss, exit costs",
|
||
"Hidden costs sering 60-70% dari total TCO — sering diabaikan",
|
||
]),
|
||
],
|
||
"model": ("Make vs Buy vs Cloud Decision", "Framework keputusan solusi SI", [
|
||
("Make (Custom)", "Full control | Highest cost & risk | Unique processes only"),
|
||
("Buy (COTS)", "Standardized | Faster deploy | Industry best practices"),
|
||
("Cloud (SaaS)", "Low upfront | Flexible | Vendor dependency risk"),
|
||
("TCO Analysis", "5-year view: Acquisition + Operation + Hidden = True Cost"),
|
||
]),
|
||
"case": ("SIPD: Transisi dari Custom ke COTS Nasional", [
|
||
"Pemerintah daerah dahulu: custom SI beragam per daerah → silos, inkonsistensi",
|
||
"SIPD nasional: standardisasi via COTS → interoperabilitas antar-daerah",
|
||
"Trade-off: lost customization vs gained standardization & data comparability",
|
||
"Cloud enabler: UMKM bisa akses Jurnal.id, Google Workspace tanpa investasi besar",
|
||
]),
|
||
"callouts": [
|
||
"TCO 5 tahun = 2.5-3× biaya akuisisi awal — selalu hitung TCO, bukan harga beli",
|
||
"Hidden costs = 60-70% total TCO — training, migrasi, productivity loss",
|
||
"Cloud memungkinkan UMKM akses enterprise-grade tools dengan biaya terjangkau",
|
||
"Keputusan Make/Buy/Cloud adalah keputusan strategis, bukan hanya cost comparison",
|
||
],
|
||
"summary": [
|
||
"3 alternatif solusi: Make (custom), Buy (COTS), Cloud (SaaS)",
|
||
"TCO 5 tahun = 2.5-3× biaya akuisisi — hidden costs dominan",
|
||
"Tidak ada solusi universal — tergantung kebutuhan, kapabilitas, dan skala",
|
||
"Cloud SaaS mendemokratisasi akses SI enterprise untuk UMKM",
|
||
"Keputusan solusi harus strategis, bukan hanya perbandingan harga",
|
||
],
|
||
"questions": [
|
||
"Bagaimana organisasi Anda menghitung TCO saat memilih solusi SI?",
|
||
"Apa hidden costs yang paling sering diabaikan?",
|
||
"Kapan custom development justified vs membeli solusi jadi?",
|
||
],
|
||
},
|
||
{
|
||
"num": 13,
|
||
"title": "Implementasi Sistem Informasi",
|
||
"bagian": "BAGIAN VI — Implementasi dan Evaluasi",
|
||
"outcome": "Menganalisis faktor keberhasilan/kegagalan implementasi; mendesain strategi change management yang efektif.",
|
||
"sections": [
|
||
("Model Implementasi: Change Management-Centric", [
|
||
"Implementasi SI = proyek perubahan organisasi, bukan proyek teknis",
|
||
"31% proyek SI succeed (Standish Group) — on time, on budget, meeting requirements",
|
||
"70% kegagalan karena faktor manusia/organisasi, BUKAN teknologi",
|
||
]),
|
||
("5 Fase Implementasi", [
|
||
"Perencanaan → Kesiapan → UAT → Go-Live → Stabilisasi",
|
||
"Change management berjalan paralel di setiap fase, bukan afterthought",
|
||
"Hypercare (2-4 minggu pasca go-live) = periode paling kritis",
|
||
]),
|
||
("ADKAR Model", [
|
||
"Awareness: paham mengapa perlu berubah",
|
||
"Desire: motivasi untuk berpartisipasi",
|
||
"Knowledge: tahu cara menggunakan sistem baru",
|
||
"Ability: mampu mengaplikasikan secara konsisten",
|
||
"Reinforcement: penguatan agar perubahan bertahan",
|
||
]),
|
||
("Strategi Deployment", [
|
||
"Phased: risiko rendah, timeline panjang — safest option",
|
||
"Big Bang: risiko tinggi, timeline pendek — dangerous",
|
||
"Pilot: validasi dulu di area terbatas, lalu skala",
|
||
"User adoption = ultimate success metric",
|
||
]),
|
||
],
|
||
"model": ("ADKAR Change Management", "5 elemen perubahan yang harus tercapai berurutan", [
|
||
("Awareness", "Mengapa perlu berubah? — Komunikasi, data dampak"),
|
||
("Desire", "Mau berpartisipasi? — Motivasi, insentif, buy-in"),
|
||
("Knowledge", "Tahu caranya? — Training, dokumentasi, mentoring"),
|
||
("Ability", "Mampu melakukan? — Practice, support, coaching"),
|
||
]),
|
||
"case": ("Hershey vs P&G: Big Bang vs Phased", [
|
||
"Hershey: Big Bang SAP implementation → $150M kerugian",
|
||
"Kehilangan 12% penjualan musim Halloween karena sistem gagal",
|
||
"P&G: phased implementation SAP yang sama → sukses global 80+ negara",
|
||
"e-KTP Indonesia: investasi triliunan gagal — training, data migration, governance",
|
||
]),
|
||
"callouts": [
|
||
"31% proyek SI succeed (Standish Group) — 69% gagal atau bermasalah",
|
||
"70% kegagalan = faktor manusia & organisasi, BUKAN teknologi",
|
||
"Miskonsepsi: 'Bangun yang benar, pengguna pasti adopt' → Salah: butuh change management",
|
||
"Hypercare (2-4 minggu pasca go-live) = periode paling kritis",
|
||
],
|
||
"summary": [
|
||
"31% SI projects succeed — 70% kegagalan dari faktor manusia",
|
||
"Implementasi SI = proyek perubahan organisasi, bukan proyek teknis",
|
||
"ADKAR: 5 elemen perubahan yang harus dicapai berurutan",
|
||
"Phased > Big Bang > Pilot — sesuaikan dengan risiko dan kapabilitas",
|
||
"Hypercare pasca go-live menentukan sustainability adopsi",
|
||
],
|
||
"questions": [
|
||
"Apa strategi deployment yang paling cocok untuk organisasi Anda?",
|
||
"Bagaimana Anda mengukur user adoption (bukan hanya user login)?",
|
||
"Identifikasi resistensi perubahan terbesar dalam implementasi SI",
|
||
],
|
||
},
|
||
{
|
||
"num": 14,
|
||
"title": "Evaluasi Kelayakan dan ROI Sistem Informasi",
|
||
"bagian": "BAGIAN VI — Implementasi dan Evaluasi",
|
||
"outcome": "Melakukan cost-benefit analysis; mengevaluasi nilai SI melampaui metrik finansial.",
|
||
"sections": [
|
||
("Business Case: Struktur & Komponen", [
|
||
"Business case menjustifikasi investasi SI dan mendokumentasikan baseline",
|
||
"Hanya 35% proyek SI di Indonesia punya formal business case",
|
||
"Tanpa business case: tidak bisa evaluasi pasca implementasi",
|
||
]),
|
||
("Komponen Biaya: Akuisisi, Operasional, Tersembunyi", [
|
||
"Akuisisi: lisensi, hardware, konsultan, customization",
|
||
"Operasional: maintenance, hosting, support, upgrade",
|
||
"Tersembunyi: training, migrasi data, productivity loss, exit costs",
|
||
"TCO 5 tahun = 2.5-3× biaya akuisisi awal",
|
||
]),
|
||
("Manfaat Tangible vs Intangible", [
|
||
"Tangible: terukur dalam Rupiah (cost savings, revenue increase)",
|
||
"Intangible: nyata tapi sulit dimonetisasi (kepuasan pelanggan, agility, kecepatan keputusan)",
|
||
"Intangible benefits = 40-60% total value SI — sering diabaikan",
|
||
]),
|
||
("Metode Evaluasi Finansial", [
|
||
"NPV (Net Present Value): akurat tapi kompleks — mengikutkan time value of money",
|
||
"ROI: sederhana tapi mengabaikan timing — (Benefits - Costs) / Costs",
|
||
"Payback Period: kapan BEP? — mengabaikan nilai pasca-payback",
|
||
"Balanced Scorecard (4 perspektif): holistik tapi subjektif",
|
||
]),
|
||
],
|
||
"model": ("Framework Evaluasi SI Multidimensional", "4 metode evaluasi dengan kekuatan/kelemahan", [
|
||
("NPV", "Accurate + time value | Complex | Strategic projects"),
|
||
("ROI", "Simple formula | Ignores timing | Quick comparison"),
|
||
("Payback Period", "Easy to understand | Ignores post-payback | Risk assessment"),
|
||
("BSC", "Holistic 4-perspective | Subjective | Strategic alignment"),
|
||
]),
|
||
"case": ("SIMRS Rp 3 Miliar: No Business Case", [
|
||
"RS investasi Rp 3 miliar untuk SIMRS tanpa formal business case",
|
||
"Tidak ada baseline metrics → tidak bisa ukur ROI pasca implementasi",
|
||
"Hasil: SIMRS berjalan tapi nilai aktual tidak pernah tervalidasi",
|
||
"AWS ROI study: inflated karena vendor-sponsored + Fortune 500 sample bias",
|
||
]),
|
||
"callouts": [
|
||
"Hanya 35% proyek SI Indonesia punya formal business case — sisanya 'atas perintah atasan'",
|
||
"Intangible benefits = 40-60% total value SI — sering diabaikan karena sulit dihitung",
|
||
"TCO 5 tahun = 2.5-3× biaya akuisisi — organisasi sering underestimate 40-60%",
|
||
"ROI saja tidak cukup untuk keputusan strategis — harus multidimensional",
|
||
],
|
||
"summary": [
|
||
"Business case adalah prerequisite evalusi SI — hanya 35% proyek Indonesia memilikinya",
|
||
"TCO = akuisisi + operasional + tersembunyi — biasanya 2.5-3× akuisisi",
|
||
"Intangible benefits = 40-60% total value — jangan diabaikan",
|
||
"Evaluasi multidimensional: NPV + ROI + Payback Period + BSC",
|
||
"Tanpa baseline metrics, ROI pasca-implementasi tidak bisa diukur",
|
||
],
|
||
"questions": [
|
||
"Apakah proyek SI terakhir organisasi Anda memiliki formal business case?",
|
||
"Bagaimana Anda mengukur intangible benefits seperti kecepatan keputusan?",
|
||
"Kapan ROI saja cukup vs kapan perlu evaluasi multidimensional?",
|
||
],
|
||
},
|
||
{
|
||
"num": 15,
|
||
"title": "Risiko, Keamanan, dan Tata Kelola SI",
|
||
"bagian": "BAGIAN VI — Implementasi dan Evaluasi",
|
||
"outcome": "Mengidentifikasi tipologi risiko SI; mengevaluasi maturitas IT governance; mendesain risk response.",
|
||
"sections": [
|
||
("Tipologi Risiko SI (5 Dimensi)", [
|
||
"Teknis: server crash, software bugs, infrastructure failure",
|
||
"Operasional: human error, process breakdown, data corruption",
|
||
"Keamanan: ransomware, data breach, phishing",
|
||
"Strategis: misalignment, obsolescence, vendor lock-in",
|
||
"Reputasional: data breach publicity, trust erosion",
|
||
]),
|
||
("Model CIA (Confidentiality, Integrity, Availability)", [
|
||
"Confidentiality: hanya pihak berwenang yang akses",
|
||
"Integrity: data akurat dan tidak dimodifikasi tanpa izin",
|
||
"Availability: sistem tersedia saat dibutuhkan",
|
||
"80% breaches bisa dicegah dengan basic hygiene (patching, password kuat, backup)",
|
||
]),
|
||
("Siklus Manajemen Risiko", [
|
||
"Identifikasi → Penilaian → Mitigasi → Monitor → Review",
|
||
"Risk register: dokumentasi 8+ skenario risiko umum",
|
||
"Response strategies: avoid, mitigate, transfer (asuransi), accept",
|
||
]),
|
||
("IT Governance Frameworks", [
|
||
"COBIT 2019: governance SI — aligning SI with business objectives",
|
||
"ISO 27001: standar keamanan informasi internasional",
|
||
"NIST CSF: cybersecurity framework terstruktur",
|
||
"Governance memiliki 40% fewer incidents & 25% higher IT efficiency (ISACA)",
|
||
]),
|
||
],
|
||
"model": ("CIA + Risk Management Framework", "Model keamanan + siklus risiko", [
|
||
("Confidentiality", "Akses hanya oleh pihak berwenang — enkripsi, access control"),
|
||
("Integrity", "Data akurat & utuh — hashing, audit trail, validation"),
|
||
("Availability", "Sistem selalu tersedia — backup, DR, redundancy"),
|
||
("Risk Cycle", "Identify → Assess → Mitigate → Monitor → Review"),
|
||
]),
|
||
"case": ("RS Dharmais WannaCry & Equifax Breach", [
|
||
"RS Dharmais: satu Windows unpatched → seluruh SIMRS lumpuh (WannaCry 2017)",
|
||
"Equifax: PCI-DSS certified tapi tetap breach 148 juta data",
|
||
"Compliance ≠ Security — compliance adalah baseline, security butuh lebih",
|
||
"Basic hygiene bisa mencegah 80% serangan: patching, password, backup",
|
||
]),
|
||
"callouts": [
|
||
"80% breaches bisa dicegah dengan basic hygiene — bukan solusi mahal",
|
||
"Compliance ≠ Security: Equifax PCI-DSS certified tapi tetap breach 148M data",
|
||
"Governance → 40% fewer incidents + 25% higher IT efficiency (ISACA)",
|
||
"UU PDP: notifikasi breach wajib dalam 72 jam — konsekuensi hukum nyata",
|
||
],
|
||
"summary": [
|
||
"Risiko SI mencakup 5 dimensi: teknis, operasional, keamanan, strategis, reputasional",
|
||
"CIA (Confidentiality, Integrity, Availability) = fondasi keamanan informasi",
|
||
"80% breaches bisa dicegah dengan basic security hygiene",
|
||
"IT governance menghasilkan 40% fewer incidents dan 25% efisiensi lebih tinggi",
|
||
"UU PDP mengubah proteksi data dari best practice menjadi kewajiban hukum",
|
||
],
|
||
"questions": [
|
||
"Apa 3 risiko SI terbesar yang dihadapi organisasi Anda saat ini?",
|
||
"Apakah organisasi Anda memiliki risk register yang aktif diupdate?",
|
||
"Bagaimana Anda membedakan compliance (checklist) dari security (substance)?",
|
||
],
|
||
},
|
||
{
|
||
"num": 16,
|
||
"title": "Transformasi Digital dan E-Business",
|
||
"bagian": "BAGIAN VII — Transformasi dan Masa Depan",
|
||
"outcome": "Membedakan digitisasi/digitalisasi/transformasi digital; mengevaluasi maturitas digital; mendesain roadmap transformasi.",
|
||
"sections": [
|
||
("3 Level Transformasi", [
|
||
"Digitisasi: Analog → Digital (format berubah, proses tetap) — scan dokumen",
|
||
"Digitalisasi: Manual → Digital process (proses berubah) — e-procurement",
|
||
"Transformasi Digital: Model bisnis berubah, value proposition baru — GoTo",
|
||
"Hanya 16% organisasi global mencapai full DT; 70% masih di digitalisasi atau bawah",
|
||
]),
|
||
("Digital Maturity Model (5 Level)", [
|
||
"Ad-hoc → Managed → Defined → Measured → Optimized",
|
||
"6 dimensi: Strategy, Culture, Technology, Process, Data, Customer",
|
||
"Assessment membantu identifikasi gap dan prioritas transformasi",
|
||
]),
|
||
("Strategi Transformasi", [
|
||
"Top-Down: eksekutif mengarahkan — risk: disconnected from reality",
|
||
"Bottom-Up: inovasi dari bawah — risk: lack of strategic alignment",
|
||
"Ambidextrous: exploit existing + explore digital simultaneously — BCA model",
|
||
]),
|
||
("Platform Economy & Network Effects", [
|
||
"Platform economy: network effects menciptakan winner-takes-most dynamics",
|
||
"Direct network effects: lebih banyak user = lebih bernilai (WhatsApp)",
|
||
"Indirect: seller attraction attracts buyers (Tokopedia)",
|
||
"85% executives menyebut budaya sebagai hambatan DT terbesar",
|
||
]),
|
||
],
|
||
"model": ("3 Level Transformasi Digital", "Dari format change ke business model innovation", [
|
||
("Digitisasi", "Format: Analog → Digital — Tidak mengubah proses"),
|
||
("Digitalisasi", "Proses: Manual → Digital — Proses berubah, model tetap"),
|
||
("Transformasi Digital", "Model: Bisnis lama → Bisnis baru — Value proposition baru"),
|
||
]),
|
||
"case": ("BCA Ambidextrous & GoTo Platform Economy", [
|
||
"BCA: exploit legacy banking + explore digital (myBCA, QRIS, API banking)",
|
||
"Strategi ambidextrous: tidak meninggalkan legacy, tapi menambah channel digital",
|
||
"GoTo: dari 20 ojek → 190M+ users ecosystem melalui platform economy logic",
|
||
"67% UMKM Indonesia masih offline — gap digital semakin melebar (3× growth differential)",
|
||
]),
|
||
"callouts": [
|
||
"Hanya 16% organisasi globally capai full digital transformation",
|
||
"Miskonsepsi: 'Website = sudah transform' → Itu hanya digitisasi!",
|
||
"85% executives: budaya adalah hambatan DT terbesar — bukan teknologi",
|
||
"Shadow IT (62% pekerja Indonesia pakai app unauthorized) = sinyal SI resmi buruk",
|
||
],
|
||
"summary": [
|
||
"3 level: digitisasi (format), digitalisasi (proses), transformasi (model bisnis)",
|
||
"Hanya 16% organisasi mencapai full DT — mayoritas masih di digitalisasi",
|
||
"Digital Maturity Model: 5 level × 6 dimensi assessment",
|
||
"Strategi ambidextrous (exploit + explore) terbukti untuk incumbents (BCA)",
|
||
"Platform economy menciptakan winner-takes-most dynamics",
|
||
],
|
||
"questions": [
|
||
"Di level mana organisasi Anda: digitisasi, digitalisasi, atau transformasi?",
|
||
"Apakah ada Shadow IT di organisasi Anda? Apa penyebabnya?",
|
||
"Bagaimana Anda mendesain roadmap dari current state ke digital transformation?",
|
||
],
|
||
},
|
||
{
|
||
"num": 17,
|
||
"title": "Kecerdasan Buatan dalam Pengambilan Keputusan Manajerial",
|
||
"bagian": "BAGIAN VII — Transformasi dan Masa Depan",
|
||
"outcome": "Mengevaluasi potensi & limitasi AI; mendesain human-in-the-loop AI adoption; mengelola implikasi etis.",
|
||
"sections": [
|
||
("AI untuk Manajer: 3 Prinsip Inti", [
|
||
"AI belajar dari data (bukan diprogram eksplisit)",
|
||
"AI mengenali pola (pattern recognition)",
|
||
"Output AI bersifat probabilistik (bukan deterministik)",
|
||
"Manajer tidak perlu coding — perlu memahami kapabilitas & limitasi",
|
||
]),
|
||
("ML, Deep Learning, Generative AI", [
|
||
"Machine Learning: algoritma belajar dari data terstruktur",
|
||
"Deep Learning: neural networks untuk data kompleks (image, voice, text)",
|
||
"Generative AI: menghasilkan konten baru (ChatGPT, DALL-E, Copilot)",
|
||
"70% organisasi akan adopt AI workspace assistants by 2027",
|
||
]),
|
||
("AI dalam Spektrum Keputusan", [
|
||
"Otomasi Penuh: fraud detection, credit scoring — volume tinggi, data kaya",
|
||
"Augmentasi (HITL): AI recommends, human decides — keputusan consequential",
|
||
"Manusia Saja: M&A strategy, ethical dilemmas — judgment & values dominan",
|
||
"Human-in-the-loop (HITL) = model teraman untuk keputusan berdampak besar",
|
||
]),
|
||
("Limitasi & Etika AI", [
|
||
"GIGO: data buruk → AI buruk — 87% AI projects gagal di data preparation",
|
||
"Bias algoritmik: Amazon AI reject resume wanita karena data historis male-dominated",
|
||
"Hallucination: Generative AI menghasilkan informasi salah dengan percaya diri",
|
||
"Governance: transparansi, akuntabilitas, fairness harus diatur organisasi",
|
||
]),
|
||
],
|
||
"model": ("AI Appropriateness Matrix", "Kapan AI tepat vs kapan manusia harus memutuskan", [
|
||
("Otomasi Penuh", "Volume tinggi + data kaya + pattern-based — Fraud, credit scoring"),
|
||
("Augmentasi (HITL)", "AI recommends + human decides — Diagnosis, investment"),
|
||
("Manusia Saja", "Value-laden + novel + ambiguous — M&A, ethical decisions"),
|
||
]),
|
||
"case": ("Bank Mandiri AI Credit Scoring & Amazon Bias", [
|
||
"Bank Mandiri: AI memproses 90% aplikasi kredit (30 detik) — manusia 10% kompleks (2 hari)",
|
||
"ROI: Rp 24B/tahun savings + 10× speed + 15% penurunan NPL",
|
||
"Netflix: 2-3× industry hit rate (30-40% vs 10-15%) pakai AI-informed decisions",
|
||
"Amazon: AI recruiting menolak kandidat wanita — bias dari data historis male-dominated",
|
||
]),
|
||
"callouts": [
|
||
"87% proyek AI gagal di fase data preparation — bukan algoritma",
|
||
"Amazon AI tolak kandidat wanita: AI mewarisi bias dari data training",
|
||
"Miskonsepsi: 'AI itu objektif' → Salah: AI mewarisi bias data training",
|
||
"Bank Mandiri: ROI Rp 24B/tahun + 10× speed — bukti nyata AI value",
|
||
],
|
||
"summary": [
|
||
"AI tepat untuk keputusan volume tinggi, data kaya, pattern-based",
|
||
"HITL (Human-in-the-loop) = model teraman untuk keputusan consequential",
|
||
"87% proyek AI gagal di data preparation, bukan di algoritma",
|
||
"Bias algoritmik nyata — Amazon AI menolak wanita dari data historis",
|
||
"Manajer masa depan: bukan coding, tapi memahami kapabilitas & limitasi AI",
|
||
],
|
||
"questions": [
|
||
"Proses bisnis mana di organisasi Anda yang paling cocok untuk AI?",
|
||
"Bagaimana Anda mendeteksi dan mengurangi bias algoritmik?",
|
||
"Apakah HITL model cocok untuk semua keputusan consequential?",
|
||
],
|
||
},
|
||
{
|
||
"num": 18,
|
||
"title": "Tren SI dan Masa Depan Organisasi",
|
||
"bagian": "BAGIAN VII — Transformasi dan Masa Depan",
|
||
"outcome": "Menganalisis tren SI; memproyeksikan implikasi terhadap peran manajerial; mempersiapkan masa depan organisasi digital.",
|
||
"sections": [
|
||
("3 Tren Konvergen", [
|
||
"AI & Otomasi: 50% aktivitas kerja secara teknis bisa diotomasi by 2030 (McKinsey)",
|
||
"Cloud-Native: demokratisasi SI enterprise untuk UMKM (SaaS, pay-as-you-go)",
|
||
"IoT & Real-Time Data: 55.7B perangkat IoT by 2025 (IDC)",
|
||
"Konvergensi ketiganya = Data-Driven Organization",
|
||
]),
|
||
("Evolusi Peran Manajer", [
|
||
"Dari operator (mengarahkan proses) ke orchestrator (mengorkestrasi ekosistem)",
|
||
"8 dimensi perubahan peran: decision-making, leadership style, skill requirements dll.",
|
||
"AI menggantikan tasks, bukan roles — manajer tanpa AI literacy akan tertinggal",
|
||
"Future skill: data literacy, AI literacy, ecosystem thinking, ethical judgment",
|
||
]),
|
||
("Indonesia: Peluang & Tantangan", [
|
||
"Peluang: 270 juta populasi, 79% internet penetration, ekosistem digital matang",
|
||
"Tantangan: infrastruktur tidak merata (Jawa vs Papua), talent shortage",
|
||
"67% UMKM masih offline — peluang digitalisasi masif",
|
||
"GoTo ecosystem: bukti Indonesia bisa membangun platform digital skala besar",
|
||
]),
|
||
("Etika & Governance di Era AI", [
|
||
"Transparansi: keputusan AI harus bisa dijelaskan",
|
||
"Akuntabilitas: siapa bertanggung jawab atas keputusan AI?",
|
||
"Fairness: mencegah diskriminasi algoritmik",
|
||
"Organizational AI governance = competitive advantage baru",
|
||
]),
|
||
],
|
||
"model": ("Convergence → Digital Organization → Orchestrator", "3 tren → Data-Driven Org → New Manager Role", [
|
||
("AI & Automation", "50% tasks automatable by 2030 — Augments, not replaces"),
|
||
("Cloud-Native", "Enterprise-grade SI accessible to all — Democratization"),
|
||
("IoT + Real-Time", "55.7B devices → continuous intelligence stream"),
|
||
("Orchestrator Role", "Manager: data × AI × people × ecosystem integration"),
|
||
]),
|
||
"case": ("GoTo, Toyota, Microsoft Copilot", [
|
||
"GoTo: dari 20 ojek → 190M+ users — platform economy Indonesian scale",
|
||
"Toyota: IoT sensors prediksi kerusakan mesin 72 jam sebelum terjadi",
|
||
"Microsoft Copilot: 50K+ enterprises adopsi AI workspace assistant",
|
||
"ChatGPT: 100 juta users dalam 2 bulan — kecepatan adopsi belum pernah ada",
|
||
]),
|
||
"callouts": [
|
||
"Miskonsepsi: 'AI menggantikan manajer' → AI menggantikan tasks, bukan roles",
|
||
"50% aktivitas kerja technically automatable — bukan berarti actually automated",
|
||
"Manajer masa depan = orchestrator ekosistem digital, bukan direct controller",
|
||
"Indonesia: 67% UMKM masih offline — peluang, bukan kelemahan",
|
||
],
|
||
"summary": [
|
||
"3 tren konvergen (AI, Cloud, IoT) membentuk Data-Driven Organization",
|
||
"Manajer berevolusi dari operator ke orchestrator ekosistem digital",
|
||
"AI menggantikan tasks, bukan roles — AI literacy menjadi keharusan",
|
||
"Indonesia memiliki peluang unik: skala populasi + digital maturity",
|
||
"Organizasi masa depan: data-driven, AI-augmented, human-governed",
|
||
],
|
||
"questions": [
|
||
"Skill apa yang paling perlu dikembangkan manajer dalam 5 tahun ke depan?",
|
||
"Bagaimana organisasi Anda mempersiapkan diri untuk konvergensi AI-Cloud-IoT?",
|
||
"Apa pesan utama yang Anda bawa dari seluruh buku ini?",
|
||
],
|
||
},
|
||
]
|
||
|
||
|
||
def generate_chapter_pptx(chapter_data):
|
||
"""Generate a complete PowerPoint for one chapter."""
|
||
prs = Presentation()
|
||
prs.slide_width = Inches(13.33)
|
||
prs.slide_height = Inches(7.5)
|
||
|
||
num = chapter_data["num"]
|
||
|
||
# 1. Title slide
|
||
create_title_slide(prs, num, chapter_data["title"], chapter_data["bagian"])
|
||
|
||
# 2. Outcome slide
|
||
create_outcome_slide(prs, num, chapter_data["outcome"])
|
||
|
||
# 3. Content slides (one per section)
|
||
for section_title, bullets in chapter_data["sections"]:
|
||
create_content_slide(prs, num, section_title, bullets)
|
||
|
||
# 4. Model/Framework slide
|
||
if "model" in chapter_data and chapter_data["model"]:
|
||
m = chapter_data["model"]
|
||
create_model_slide(prs, num, m[0], m[1], m[2])
|
||
|
||
# 5. Case study slide
|
||
if "case" in chapter_data and chapter_data["case"]:
|
||
c = chapter_data["case"]
|
||
create_case_slide(prs, num, c[0], c[1])
|
||
|
||
# 6. Callout/traps slide
|
||
if "callouts" in chapter_data and chapter_data["callouts"]:
|
||
create_callout_slide(prs, num, chapter_data["callouts"])
|
||
|
||
# 7. Summary slide
|
||
if "summary" in chapter_data and chapter_data["summary"]:
|
||
create_summary_slide(prs, num, chapter_data["summary"])
|
||
|
||
# 8. Discussion slide
|
||
if "questions" in chapter_data and chapter_data["questions"]:
|
||
create_discussion_slide(prs, num, chapter_data["questions"])
|
||
|
||
# Save
|
||
filename = f"slide-bab-{num:02d}.pptx"
|
||
filepath = os.path.join(OUTPUT_DIR, filename)
|
||
prs.save(filepath)
|
||
return filepath
|
||
|
||
|
||
def main():
|
||
print(f"Generating slides for {len(chapters)} chapters...")
|
||
print(f"Output directory: {OUTPUT_DIR}")
|
||
print("=" * 60)
|
||
|
||
for ch in chapters:
|
||
filepath = generate_chapter_pptx(ch)
|
||
slide_count = len(Presentation(filepath).slides)
|
||
print(f" ✓ Bab {ch['num']:02d}: {ch['title'][:50]}... ({slide_count} slides) → {os.path.basename(filepath)}")
|
||
|
||
print("=" * 60)
|
||
print(f"Done! {len(chapters)} presentations generated in: {OUTPUT_DIR}")
|
||
|
||
|
||
if __name__ == "__main__":
|
||
main()
|