GBA study materials
GBA study resources

GBA: Digital Transformation and Information Systems

GBA · Work through your exam, one topic at a time.

All guide sections

Digital Transformation and Information Systems

What this domain tests

Digital Transformation and Information Systems tests the business case for platform change, data governance, and the controls that must survive a move to cloud and AI.

Core rules and concepts

  • Digitisation versus transformation - digitisation converts an artefact; transformation changes the operating model, decision rights and process ownership.
  • ERP logic - a single source of truth requires process harmonisation. Local statutory, fiscal and language requirements are handled through a localisation layer, not by forking the template.
  • Cloud models - IaaS, PaaS, SaaS; shared responsibility means the provider secures the infrastructure while you still own identity, configuration and data classification.
  • Data governance - ownership, master data management, data quality rules, lineage and retention.
  • Architecture - TOGAF ADM for enterprise architecture; APIs and event-driven integration instead of point-to-point sprawl; RPA for narrow, rules-based tasks, not as a fix for broken processes.
  • Security - CIA triad, NIST CSF functions (govern, identify, protect, detect, respond, recover), zero trust, least privilege.
  • Value - total cost of ownership includes licences, implementation, integration, change management, run costs and technical debt; benefits materialise only with adoption.

Worked example

A manufacturer weighs a single global ERP template against regional instances. Licence $2m, implementation $6m, run $1.5m per year. Benefits: inventory reduction $1.2m and headcount $0.8m per year, so $2.0m per year. Five-year cost = 2 + 6 + (1.5 x 5) = $15.5m. Five-year benefits = $10m. Net = -$5.5m, with payback at 8 / 2 = 4 years, so the case only closes beyond year four or with further benefits such as reduced audit and compliance effort. Regional instances cut localisation risk but add integration and master-data reconciliation cost. A defensible recommendation: one template plus a controlled localisation layer for tax and statutory reporting, because benefits come from harmonised processes while statutory compliance is non-negotiable.

Traps that cost marks

  • Counting licence cost as the project cost and ignoring change management.
  • Assuming cloud migration transfers GDPR or sector compliance obligations to the vendor.
  • Claiming benefits before adoption is measured.
  • Choosing bespoke build where a configurable standard process would serve.
  • Underestimating data migration quality and record-retention constraints.