TheLayerTheyCannotBuild

The first two articles in this series argued what the layer cannot be. It cannot be built inside SAP or IBM. It cannot be delivered by the SI services equilibrium. So what does the layer that replaces both actually look like? It is owned, not engaged. Continuous, not project-based. Architectural, not methodological. Federated across master domains. Multi-platform native. Governed at the schema layer. The architecture is not theoretical. It is being built.

The first MRO master data remediation projects were sold around 2003. Twenty-three years later, the same firms are selling the same projects to the same customers. The methodology has matured. The drift back to baseline is the same. This is not a story about bad system integrators. It is a story about an arrangement none of the participants can exit alone.

A manufacturing CIO showed me a remediation proposal two years ago. His successor — three CIOs later — showed me a near-identical one. Same SI. Same scope. Same eight figures. The records had drifted back. The MRO data quality problem on SAP and IBM Maximo will not be solved by SAP or IBM. Not because they have not tried. Because they architecturally cannot.