OIM Verify

An independent check that your key numbers survived the move.

The migration vendor confirmed your data loaded successfully. That is true, and it is not the same thing as your most-watched metrics still calculating the way they did before. Verify is the narrow, independent spot-check that tells you whether a handful of the numbers you run on held.

What it is

OIM Verify is a focused engagement. You name up to three of your most-watched operational metrics, the ones a leader would ask about by name. I independently establish how each one is actually defined, to a recognized standard (ISO 22400 / SMRP), and check whether it still computes the same way after an Epicor on-prem → Kinetic move.

You do not get an absolute verdict. You get a clear, written account of what each metric means, whether it held, and where it drifted, so you can make the call from the evidence rather than from someone’s assurance.

OIM Verify is the narrow entry point to the fuller OIM Validate engagement. It checks a defined set of metrics; Validate checks the whole move. What you spend on Verify carries forward if you go on to Validate.

Why it matters

A metric is a definition computed over data, and that computation lives inside the system. Move the system and you have quietly moved the computation. The single-number measures usually survive. The fragile ones are the ratios: OEE, on-time %, scrap rate, utilization. Each depends on how both halves are derived, and that derivation is exactly what changes underneath.

The drift hides behind numbers that still look plausible, so nobody catches it until it is wrong in front of leadership. And the person who built a number cannot certify their own work. Independence is the structural thing an in-house analyst cannot provide about their own migration, and it is the whole point of bringing in an outside check.

How I’d approach it
  1. Pin the definition. Establish exactly how each chosen metric is defined, every term in the numerator and denominator, mapped to the recognized standard rather than to whatever the software happened to compute.
  2. Compute on both sides. Run the same definition against the on-prem source and the Kinetic target while both are still available to compare, so the result is a real comparison and not a reconstruction.
  3. Document the difference. Where a number held, say so. Where it drifted, show by how much and why: which table, which logic, which assumption moved.
  4. Hand you something defensible. A written record, established to standard and certified by someone outside your team, that you can put in front of leadership and stand behind.
The thinking behind it
No. 017 OPS TRUTH

I Built Both Systems. The Numbers Still Didn’t Match.

I architected both ends of a migration myself, same person, same definitions, and the numbers still didn’t reconcile. Why that’s the rule, not the exception, and why an outside check is the only honest all-clear.

Read the Dispatch →