Operational data integrity
Your AI project will fail on your data, not your model.
Apex finds what is silently broken underneath, then builds the workflow that runs on top of it.
Ten seconds, in your own file
Two of your accounts may already be the same account.
Account, policy, member or national ID. Nothing leaves your browser.
A spreadsheet keeps only fifteen significant digits and zero-fills the rest. No error. No warning. Nothing on screen to see.
And it is one of eight
Eight ways operational data breaks quietly.
A known, finite set. Tested for in the first week, before anything is built. Most organisations have three.
- 01
Identifiers that lose precision
…0001 → …0000 - 02
Identifiers already destroyed
4.5009E+16 - 03
Dates that read either way
03/04/2026 - 04
Deliveries that change shape
12 → 15 → 16 cols - 05
Columns with no header
[ ] PENDING - 06
Summaries frozen in time
box ≠ list - 07
Rows that are not records
3 counts, 1 batch - 08
Archives that will not open
lists ok · fails
Who runs it
Kudrat Lokman
He helped regulate digital finance in Malaysia. Now he operates inside it.
Bank Negara Malaysia·Wharton·COO, approved takaful operator
He does not learn your operation in order to help you. He runs one.