NPDL26 transforms production data at source before it leaves the production boundary. RDT26 provides governed, selective reversal when a specific record needs lawful re-identification. Together they cover the everyday case — move data safely — and the exception case — look up one record under control — without softening the boundary between them.
The workflow is designed to be understood at a glance by an auditor and by a database engineer at the same time. NPDL26 uses Oracle GoldenGate to capture change at source, applies deterministic transformation inside the production zone, writes the transformed file inside the production environment, and then delivers it to the target with automatic cleanup at the end of the run.
RDT26 sits alongside as an optional controlled reversal path. When — and only when — a specifically identified record needs follow-up, an authorised operator reverses that single record under key management. Bulk, batch, and stream reversal are blocked by design; there is no path from RDT26 to a re-identified copy of a dataset.
RDT26 unmasks a single element at a time under a specifically identified record. The remaining fields on that record and the rest of the population stay protected. Every reversal is logged.
Deterministic, referentially consistent transformation of production data before it is loaded into development, test, UAT, analytics, or ML environments. Applied inside the production boundary; only transformed data ever leaves.
Governed, selective reversal of individually identified records — one element per pass — for lawful re-identification scenarios such as fraud investigation, incident response, and regulated disclosure.
NPDL26 and RDT26 have native support for the three enterprise database platforms most commonly present in Australian regulated environments — Oracle Database, Microsoft SQL Server, and IBM DB2. Wider platform coverage is achieved via Oracle GoldenGate as the change-data-capture layer, which extends reach without altering the transformation model.
