[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"scribble-tbm-foundations-synthetic-enterprise-modeling-ug7z8o":3},{"id":4,"title":5,"user_id":6,"is_anonymous":7,"tags":8,"created_at":19,"updated_at":19,"storage_path":20,"is_public":21,"linked_scribbles":22,"previous_scribble":23,"next_scribble":23,"is_draft":7,"related_scribbles":24,"slug":25,"author_name":26,"author_username":27,"body":28,"linked_articles":29,"related_articles":30,"reverse_relation_map":71,"insights":23,"insights_status":72},"2053a578-64f4-431d-8cf6-6e5895f903e5","TBM Foundations & Synthetic Enterprise Modeling","c5599ac1-74e8-4745-b518-653b2f8d39ae",false,[9,10,11,12,13,14,15,16,17,18],"tbm","technology","business","management","finance","cxo","accounts","spends","costs","economics","2026-11-18T17:07:26.935745+00:00","c5599ac1-74e8-4745-b518-653b2f8d39ae\u002F113db51d-9299-4a74-926e-f27427363c20.md",true,[],null,[],"tbm-foundations-synthetic-enterprise-modeling-ug7z8o","Pushkar Patil","patilpushk","# The TBM Problem: Why Traditional IT Management Fails\n\nIf you are new to **Technology Business Management (TBM)**, the central challenge of enterprise IT can be summarized in a single paradox:\n\n> **The Enterprise IT Paradox**: The General Ledger (GL) tracks IT expenditures as accounting lines (e.g., invoices from AWS, payroll for software engineers, Cisco hardware leases), but business executives demand to know the financial return of business capabilities (e.g., \"What does our Customer Loan Origination process cost per transaction?\").\n\n![image](https:\u002F\u002Fzirybgocjulamzssmsuw.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002FMadaatih\u002Fc5599ac1-74e8-4745-b518-653b2f8d39ae\u002Fimages\u002Feefddbca-2a6e-47e8-ac1c-2ef28126fcbc.png)\n\nWithout an intermediary model, IT organizations resort to **\"peanut-butter budgeting\"** - taking the massive pool of IT costs and smearing it evenly across business units based on arbitrary metrics like employee headcount. This distorts decision-making:\n\n1. Low-cost, efficient business units subsidize legacy, bloated departments.\n2. Architects cannot determine whether decommissioning a legacy monolith will save ₹10,00,000 or ₹10 Crore.\n3. FinOps teams optimize server instances without understanding which customer journey relies on them.\n\nTo solve this, TBM introduces a standardized taxonomy (such as the Apptio TBM Unified Model, or ATUM) that maps expenditures across four layers:\n\nCost Pools (Invoices) -&gt; Cost Towers (Infra\u002FApps) -&gt; Applications\u002FServices -&gt; Business Capabilities \u002F UnitsCost Pools (Invoices) -&gt; Cost Towers (Infra\u002FApps) -&gt; Applications\u002FServices -&gt; Business Capabilities \u002F Units\n\n## Why Synthetic Enterprise Data is Mandatory\n\nEnterprise IT cost structures, vendor contracts, and dependency graphs contain strict intellectual property, personally identifiable information (PII), and confidential financial margins. You cannot open-source or benchmark real Fortune 500 General Ledger data.\n\nTo demonstrate production-grade TBM algorithms, we construct an end-to-end **procedural synthetic data generator**. It models a realistic ₹140 Crore+ enterprise IT estate across 25 applications, 6 business units, 10 business capabilities, and 12 months of operations.\n\n# Core Architectural Entities & Relationship Taxonomy\n\nOur enterprise ontology models entities as typed relational tables that subsequently compose a typed property graph:\n\n```mermaid\nerDiagram\n    ORGANIZATION ||--o{ BUSINESS_UNIT : contains\n    BUSINESS_UNIT ||--o{ COST_CENTER : owns\n    COST_CENTER ||--o{ GENERAL_LEDGER_SPEND : incurs\n    BUSINESS_APPLICATION ||--o{ GENERAL_LEDGER_SPEND : attributes\n    BUSINESS_APPLICATION ||--o{ BUSINESS_CAPABILITY : supports\n    BUSINESS_APPLICATION ||--o{ INFRASTRUCTURE_SERVER : hosted_on\n    BUSINESS_APPLICATION ||--o{ BUSINESS_APPLICATION : depends_on\n    BUSINESS_APPLICATION ||--o{ PROJECT : modernized_by\n```\n\n## Entity Specifications\n\n1. **Organization (**`ORG001`**)**: Top-level corporate entity (*Global Financial Enterprises*).\n2. **Business Units (**`BU001` **-** `BU010`**)**: 10 operating divisions (Retail Banking, Corporate Investment, Wealth Management, Digital Payments, Operations & Risk, Core Platform, Treasury & Capital Markets, Consumer Lending, Asset Management, Commercial Banking).\n3. **Business Capabilities (**`CAP001` **-** `CAP025`**)**: 25 high-level business capabilities (e.g., Core Banking, Payment Processing, Loan Origination, Wealth Advisory, Order-to-Cash, Procure-to-Pay, Fraud Detection).\n4. **IT Services (**`SRV001` **-** `SRV018`**)**: 18 technical and shared platform services.\n5. **Applications (**`APP001` **-** `APP050`**)**: 50 systems of record, customer portals, integration middleware, and analytics engines categorized across four criticality tiers.\n6. **Technologies (**`TECH001` **-** `TECH035`**)**: 35 infrastructure, runtime, database, and cloud components.\n7. **Vendors (**`VEN001` **-** `VEN010`**)**: 10 major cloud, software, and hardware providers (e.g., TechNova Cloud, Apex Systems, CloudScale Solutions).\n8. **Transformation Projects (**`PRJ001` **-** `PRJ040`**)**: 40 strategic initiatives tracking budget, actual spend, and realized value.\n\n# Architectural Decisions & Alternatives\n\n| Architectural Choice | Choice in TVI | Alternative 1: Faker \u002F Mockaroo | Alternative 2: SDV (CopulaGAN\u002FCTGAN) | Alternative 3: Anonymized Production Dump |\n| --- | --- | --- | --- | --- |\n| **Generation Engine** | **Deterministic Procedural Python** | Template-driven random generation | Neural generative adversarial network | SQL scrubbing \u002F masking script |\n| **Referential Integrity** | **Strict Relational & Graph GraphML Checks** | Loose foreign keys | Probabilistic joins (often broken) | Native database constraints |\n| **Reproducibility** | **Fixed seed (**`seed=42`**) across NumPy\u002FPython** | Seeded templates | Stochastic random weights | Non-reproducible (schema drifts) |\n| **Compute Overhead** | **&lt; 1.5 seconds on 16 GB laptop** | &lt; 1 second | 10-30 minutes GPU training | Hours of sanitization pipelines |\n| **Why TVI Chose This** | Complete mathematical control over 25 injected edge-case scenarios | Cannot enforce complex graph dependencies or financial balance | Overkill; hallucinates referential graph violations | Legal liability and enterprise NDA breach risk |\n\n# Code Walkthrough: Procedural Entity Synthesis\n\nLet's examine the foundational generator class [EnterpriseDataGenerator](file:\u002F\u002F\u002FUsers\u002Fpushkar\u002FDocuments\u002Fprojects\u002Fvalue\u002Fsrc\u002Ftvi\u002Fdata_generation.py#L30-L75).\n\n```python\n# src\u002Ftvi\u002Fdata_generation.py\nimport random\nimport numpy as np\nimport pandas as pd\nfrom typing import Dict, List, Tuple\nfrom tvi.config import load_config\n\nclass EnterpriseDataGenerator:\n    \\\"\\\"\\\"Generates realistic enterprise IT cost, consumption, and topological data.\\\"\\\"\\\"\n\n    def __init__(self, config: Dict = None, seed: int = 42):\n        self.config = config or load_config()\n        self.seed = seed\n        random.seed(seed)\n        np.random.seed(seed)\n        \n        # Internal state stores\n        self.applications: pd.DataFrame = None\n        self.business_units: pd.DataFrame = None\n        self.cost_centers: pd.DataFrame = None\n        self.capabilities: pd.DataFrame = None\n        self.cost_records: pd.DataFrame = None\n        self.consumption_records: pd.DataFrame = None\n```\n\n## Line-by-Line Code Analysis:\n\n- **Lines 10–14**: Dual random state seeding (`random.seed(seed)` and `np.random.seed(seed)`). This guarantees that every synthetic dataset, variance spike, and dependency graph generated will produce bit-for-bit identical results on macOS, Linux, and Windows.\n- **Lines 17–23**: Data stores are typed as `pd.DataFrame`. DataFrames provide immediate columnar conversion to Apache Parquet and DuckDB memory structures.\n\n## Application Catalog Generation\n\nApplications require realistic tiering, architectural complexity, vendor ownership, and operational lifecycles:\n\n```python\ndef generate_applications(self) -> pd.DataFrame:\n    \\\"\\\"\\\"Generates 25 enterprise applications across tiers and lifecycles.\\\"\\\"\\\"\n    apps_data = [\n        {\"app_id\": \"APP001\", \"app_name\": \"Core Banking Engine\", \"tier\": \"Tier 1\", \n         \"lifecycle\": \"Production\", \"owner_bu\": \"BU001\", \"criticality\": 0.95},\n        {\"app_id\": \"APP002\", \"app_name\": \"Retail Mobile Banking\", \"tier\": \"Tier 1\",\n         \"lifecycle\": \"Production\", \"owner_bu\": \"BU001\", \"criticality\": 0.90},\n        # ... APP003 through APP025\n        {\"app_id\": \"APP021\", \"app_name\": \"Legacy Branch CRM\", \"tier\": \"Tier 3\",\n         \"lifecycle\": \"Legacy\", \"owner_bu\": \"BU005\", \"criticality\": 0.30},\n    ]\n    self.applications = pd.DataFrame(apps_data)\n    return self.applications\n```\n\nNotice the `criticality` score ∈\\[0,1\\]∈\\[0,1\\]. In later notebooks, this score forms a primary weight in Multi-Criteria Decision Analysis (MCDA) for application rationalization and transitive blast-radius simulations.\n\n# Scope of Improvement & Production Roadmap\n\n1. **Hierarchical Capability Taxonomies**: Upgrade from a single-tier capability catalog to a full 3-level BIAN (Banking Industry Architecture Network) capability tree.\n2. **Dynamic Configuration Ingestion**: Allow developers to inject an enterprise's real Application Portfolio Management (APM) taxonomy via YAML schema overrides.\n3. **Distributed Synthesis**: For stress-testing billion-row datasets, parallelize row generation using Ray or Polars.\n\n# Summary & Companion Reading\n\nIn this first technical guide, we established the core rationale for TBM and implemented deterministic procedural generation for corporate entities.\n\n**Next Guide** explores why IT metrics break standard Gaussian distributions.",[],[31,35,39,43,47,51,55,59,63,67],{"id":32,"title":33,"slug":34},"f63275a7-a4fb-463a-8cf5-3cd9589fef63","Category 2: Intermediate Scenarios","category-2-intermediate-scenarios-qxytzx",{"id":36,"title":37,"slug":38},"9796f637-29b9-4035-aa33-b889b856a711","The Valuation Arbitrage","the-valuation-arbitrage-wnz5rv",{"id":40,"title":41,"slug":42},"507a340d-f975-48e5-8761-bedb5a349381","From Strategy to Value","from-strategy-to-value-v959kz",{"id":44,"title":45,"slug":46},"96372a76-4382-4bfc-b85d-9cdfccb54415","Category 3: Advanced Scenarios","category-3-advanced-scenarios-fy3iep",{"id":48,"title":49,"slug":50},"619af8aa-c46e-478d-bfce-3a66b2743794","The 'Massive' Pause","the-massive-pause-619af8aa",{"id":52,"title":53,"slug":54},"8ca1bf3c-2c85-45a9-b6ab-0a2ad72e9682","The $50,000 Moonshot","the-50-000-moonshot-8ca1bf3c",{"id":56,"title":57,"slug":58},"72ef3ab4-a714-41b2-9298-529f4f3c6e39","The Turnaround Hallucination","the-turnaround-hallucination-xc8vi9",{"id":60,"title":61,"slug":62},"4074e215-acb2-414a-9a6d-77329251c9be","Unlocking the value of IT","unlocking-the-value-of-it-oopkxz",{"id":64,"title":65,"slug":66},"37392b05-8672-47dc-9bca-74a1112b2475","The Crisis of Organic Growth","the-crisis-of-organic-growth-37392b05",{"id":68,"title":69,"slug":70},"054aec64-51a3-4c95-b1ed-ce40816f5885","Beyond the Dashboard: Rethinking IT Value Realization in the Age of AI","beyond-the-dashboard-rethinking-it-value-realization-in-the-age-of-ai-04nl9o",{},"pending"]