Application · Enterprise Data, AI & Digital leadership · Sasol

Data→Intelligence→Action→Value

A practical blueprint for turning enterprise data and AI into measurable operational performance, productivity and growth.

Harshan PillayTechnology • Architecture • Data • AI • Digital Transformation

Everything below runs in your browser on synthetic data. No Sasol confidential or proprietary data is used, and the AI never writes to a control system.

The 60-second version

Short on time? Start here.

Proven experience
Who I am

Former Software Developer at Securities Trading Technology (STT). 3+ years building mission-critical clearing, trading and client-analytics platforms in regulated financial services. Based in Johannesburg.

Demonstration · synthetic data
What I built for you

A working industrial AI lab: three machine-learning models that detect, explain and optimise, a second use case on the same platform, and a knowledge assistant that cites its sources.

Proposed Sasol approach
How I would lead

Value first, trusted data, one reusable platform, responsible AI and real adoption. Understand in 90 days, prove value by 180, scale by 365.

Safety first

The AI never writes to a control system. It advises and an accountable person decides. When the data or the model can't be trusted, it steps back and escalates.

I haven't yet led an enterprise AI function. This page is labelled throughout so you can see what I have done, what transfers, and what I propose.

I don't just propose AI.I show how it becomes an enterprise capability.

Proven experience
Build
Mission-critical technology.

Clearing and trading platforms: microservices, secure APIs, messaging and cloud delivery in regulated financial services.

Transferable capability
Connect
Technology + data + business priorities.

Start from the decision and the KPI, then choose the data and the model. Value first, technology second.

Proposed Sasol approach
Scale
Reusable enterprise capabilities.

Turn one working use case into shared pipelines, lifecycle, governance and measurement that every team reuses.

Try it yourselfDemonstration · synthetic data

Sasol AI Operations Lab

Watch three real machine-learning models spot a problem on a simulated process unit, explain it and suggest what to do. A person always decides.

  • Synthetic data only, no Sasol data
  • Never writes to a control system
  • Runs entirely in your browser
Connecting to synthetic telemetry…
Same platform, more use cases

One platform, reused.

Scale comes from reuse. Two more working examples built on the same building blocks as the Lab.

Reuse the platform · use case 2Demonstration · synthetic data

Same platform. A second use case.

Loading the asset-health models…
How I would lead it at Sasol

From one demo to an enterprise capability.

My proposed approach, one topic at a time. Pick the one you care about most.

How it would work at SasolProposed Sasol approach

A prototype is not a production system. Here is the difference.

The Lab collapses the whole chain into a browser. In an enterprise, every arrow becomes a governed, owned and monitored capability.

  1. 01Industrial systemsDCS · historian · LIMS · CMMS
    →
  2. 02Governed data platformingestion · quality · lineage · data products
    →
  3. 03Enterprise AI platformfeature store · training · registry · serving · monitoring
    →
  4. 04AI models / agentsversioned · validated · approved
    →
  5. 05Operational applicationscontrol-room UI · work management · mobile
    →
  6. 06Human decisionsoperator · engineer · manager
    →
  7. 07Measured outcomesbaselined KPIs · value ledger
Same logic, different guarantees

Detection, explanation, policy gating and human approval carry over unchanged. What changes is who owns each step and how it is secured, monitored and supported.

The model is the smallest part

Most of the effort in production sits in data pipelines, integration with operational systems, change management and value measurement.

Never write to control systems

Recommendations flow to people through operational applications. The AI platform has no write path to the DCS.

My 90 / 180 / 365-day planProposed Sasol approach

Understand. Prove. Scale.

0 – 90 days
Understand
Map
  • Business priorities
  • Data landscape
  • AI portfolio
  • Architecture
  • Governance
  • Capability maturity
  • Value opportunities
Deliverable
Enterprise Data & AI Value Map
90 – 180 days
Prioritise + prove
Establish
  • AI portfolio governance
  • Value measurement
  • Responsible AI framework
  • Data quality priorities
  • Reusable architecture
  • Targeted pilots launched
Deliverable
Measured AI Value Portfolio
180 – 365 days
Scale
Industrialise
  • Reusable AI services
  • Governed data products
  • AI lifecycle management
  • Communities of practice
  • Business-unit adoption model
Deliverable
Enterprise AI Engine

Three low-risk quick wins for the first 90 days

Illustrative

Chosen to build trust fast without touching operations: each is read-only or advisory, has a named owner and a baseline, and can be stopped at any time. To be validated with the business in the first weeks.

Quick win 1Data & AI value register

Inventory every data and AI initiative already in flight: owner, KPI, stage, risk, spend and expected value. The start of the portfolio dashboard.

Why it is low risk
Touches no systems; it is a governance and visibility exercise.
Measured at day 90
Every in-flight initiative listed with a named owner and a KPI.
Quick win 2Advisory energy-intensity alerts on one unit

The Operations Lab pattern on real historian data for a single unit, sending advisory alerts to its engineers.

Why it is low risk
Read-only data, advisory output, a person decides, no write path to control systems.
Measured at day 90
Baseline set, alerts reviewed by engineers, share of confirmed deviations.
Quick win 3Engineering knowledge assistant pilot

The knowledge-assistant pattern over approved procedures and standards for one engineering team, answering only with citations.

Why it is low risk
Read-only, access-controlled, answers must cite approved documents.
Measured at day 90
Time to find information and weekly active users in the pilot group.
Why me

What I have done, and how it maps to the role.

Every claim is tied to my CV, and labelled honestly where it is transferable rather than proven.

My engineering evidence

What I have built, and why it matters here.

Former Software Developer at Securities Trading Technology (STT), Johannesburg. Software Developer 2023 – Aug 2026 · Software Engineering Intern / Scholarship Recipient 2021 – 2022. BSc Computer Science, University of the Witwatersrand.

Proven experience→Transferable capability→Proposed Sasol approach
Proven experience
Microservices

MICS: modernised a mission-critical clearing platform from a monolith to microservices, improving scalability, fault tolerance and maintainability.

Transferable capability
Scalable enterprise architecture

Decomposing a large system into services with clear contracts, independent deployment and owned data.

Proposed Sasol approach
At Sasol

Treat AI use cases as products on a shared platform, not one-off builds.

MICSC# / ASP.NET CorePlatform modernisation
StackC#PythonASP.NET CoreAngularFlutter (Dart)REST APIsFIX protocolRabbitMQDockerKubernetes (AKS)Azure DevOps CI/CDInfrastructure-as-code (ARM)SAML

The goal is not more AI.The goal is more value from data.

  1. Trusted data
  2. →
  3. Intelligent systems
  4. →
  5. Better decisions
  6. →
  7. Operational action
  8. →
  9. Measured value
  10. →
  11. Enterprise-scale capability

My aim would be to make Data and AI a repeatable enterprise capability — not a collection of disconnected experiments.

Harshan PillayTechnology • Architecture • Data • AI • Digital Transformation · Johannesburg, South Africapillayharshan@gmail.com
Take away a one-page brief written from what you just did in the Lab.