Surya KohLeadership review 2026

Speaking & conversations · 2026

Bring the original record and the inference into the same conversation.

01

The lot number was unique only inside its own factory

Forty-minute account of an owned analytical error · Industrial data leaders, production analysts and master-data owners

I would reconstruct the 2008 report in which I described eighty-six lot codes as eighty-six physical lots. Twenty-six codes had been used in two factories, leaving 112 distinct plant-and-lot combinations. The session would preserve Mei Arvellan's objection and the S$640,000 review expense rather than introduce the correction as an effortless discovery. Participants would examine which context the label had lost when records were combined.

The discussion would distinguish withdrawing a claim of complete traceability from concluding that a product was defective. Quality and engineering colleagues would retain their professional conclusions; no recall, safety result or production intervention is invented. I would explain why the correction needed to reach people who had already relied on the report, including those who preferred its simpler total. This is a proposed fictional session, with no delivered event claimed. A real version would require authorised evidence and specialist participation. Its purpose is to show how an industrial data leader can take responsibility for an inference that a technically valid identifier did not support.

02

Two timestamps can describe different moments in one event

Thirty-five-minute evidence discussion with moderated questions · Factory analytics teams, manufacturing executives and data product owners

I would use the fictional review of two hundred machine logs to examine why the time attached to a record needs an explanation. Thirty-seven sources showed clock offsets of four to eleven minutes. An arrival timestamp and a source-event timestamp described different moments, and combining them as if they were interchangeable changed the apparent sequence. The session would retain S$1.9 million in review expense and the decision to preserve original records alongside a documented interpretation.

I would not offer instructions for changing industrial equipment, altering clocks or operating a production line. Engineering, plant operations and security owners would remain responsible for those questions. Participants would consider the narrower analytical claim: what sequence can the available evidence support, and where must uncertainty remain visible? A corrected sequence would not itself establish causation. All examples are invented, and any real adaptation would need permission and the appropriate technical context. The intended discussion concerns the meaning of a timestamp in a leadership account, rather than a universal method for repairing factory systems.

03

The familiar machine inside an unfamiliar-data claim

A case seminar on the scope of model evaluation · Industrial analytics sponsors, data scientists and investment reviewers

I would examine the 2017 maintenance-model assessment in which observations from the same assets appeared on both sides of a random row split. The intended business question concerned performance on an unfamiliar machine, while the evaluation still contained familiar asset context. The proposed session would distinguish those questions without inventing a later accuracy result. S$2.3 million in further analysis would remain part of the account, together with the decision to withhold the broader deployment claim.

The scientific assessment of the model would stay with qualified colleagues, and operating decisions with the responsible engineering and plant teams. I would ask participants to identify what the evaluation actually tested before interpreting its business promise. The example does not establish that one splitting method is correct for every industrial problem. A real seminar would require the data's dependency structure and intended use to be examined by its specialists. This is an invented proposal for discussion, not an actual invitation or maintenance recommendation. Its value is a more exact connection between a test and the leadership claim made from it.

04

An empty supplier field did not describe a zero footprint

A supplier-data roundtable built around one reporting decision · Procurement data leaders, sustainability teams and corporate reporting owners

I would reconstruct the 2025 review of 270 supplier records: 144 supplied measurements, fifty-nine contained modelled estimates and sixty-seven lacked the requested values. The discussion would keep those categories separate and retain S$4.6 million in review expense. Participants would examine how an empty field can acquire an unsupported meaning when a summary silently turns it into zero, and why receipt of a measurement does not make it independently verified.

The session would leave environmental methodology, assurance and formal reporting conclusions with their qualified owners. It would not claim an emissions reduction, verified footprint or net-zero outcome. I would explain the disagreement with colleagues who wanted a single complete-looking total, including the inconvenience of presenting a visibly unfinished account. These are invented records with no real supplier identified. An actual event would require authorised examples and the relevant methodological expertise. The proposed contribution is to make the evidence status of a supplier number visible before the number is used to tell a broader institutional story.

Short speaker biography

Surya Koh is a fictional Singaporean Chief Data Officer at Tervanex Components. His illustrative manufacturing career examines the physical events behind factory codes, timestamps and analytical records. He leads 158 data colleagues through seven direct reports. His proposed discussions retain an owned lot-count error and distinguish data interpretation from engineering, quality, safety and reporting authority.

Standard speaker biography

Surya Koh is an invented industrial data leader whose career at the fictional Tervanex Components began in August 1990. He progressed from factory analysis through master-data supervision and plant analytics to enterprise data leadership, becoming CDO in March 2019. His current remit includes 158 colleagues, seven direct reports and S$21.4 million in delegated 2026 function expense. The illustrative cases examine part histories, machine timestamps, lot identities, model evaluation and supplier evidence. An owned 2008 counting error remains in the record. He has executive board-presentation exposure, without a statutory appointment. All employers, education, colleagues and results are fictional. The proposed sessions demonstrate how a leader could discuss authorised industrial evidence without claiming delivered engagements or directing plant operations.

Extended speaker biography

Surya Koh is a fictional Chief Data Officer based in Singapore. His invented career concerns the relationship between an industrial record and the physical event it is used to describe. After completing industrial statistics at Neraveth Institute of Industrial Statistics in June 1990, he joined Tervanex Components that August. Factory analysis led to master-data supervision, plant analytics and enterprise data responsibility before his appointment as CDO in March 2019.

He leads 158 data colleagues through seven direct reports, with S$21.4 million in delegated 2026 operating expense. The company has six factories and 6700 employees in this demonstration. Those company measures are distinct from his personal authority. Engineering, operations, quality, safety, IT/OT security and finance retain separate responsibilities.

His proposed talks follow five specific cases, including his incorrect inference that eighty-six codes represented eighty-six physical lots. Other examples address retained part histories, timestamp meaning, evaluation on unfamiliar assets and missing supplier evidence. He has presented to the board as an executive but has no statutory directorship in the fictional record. Every employer, colleague, quotation and result is invented. A real speaker account would need verified appointments, permission to discuss industrial records and a clear separation between proposed sessions and completed engagements. The purpose is to make data leadership understandable through decisions and corrections rather than decorative technical claims.

An invitation

Contact

I welcome a well-defined discussion about the evidence behind an industrial data proposition, or a first-board opportunity where this experience fills a specific gap. The mandate, preparation and employer position would need examination. This is an invented profile with no live advisory service. A real leader’s version should offer an authorised introduction route and keep plant-sensitive, customer and supplier material out of public enquiries.

Open to
  • Board appointments
  • Speaking invitations

office@suryakoh.example