Integration debt belongs on the executive agenda
Most CIOs know the feeling. A change that should take days takes weeks because nobody is sure which interfaces touch the data. A support team keeps a private list of fragile flows. A project plan quietly includes a line that says "check PI dependencies". None of this appears as a budget item, yet all of it is paid for, every month.
That is integration debt. It is not a technical curiosity. It is a liability that shapes how fast the business can change, how safely it can operate and how much of the IT budget is left for anything new. This paper argues three points:
- Integration debt can be sized, in your own units, without borrowed statistics.
- A fixed maintenance date makes the sizing urgent.
- Retiring the debt is a sequence of managed waves, and the work only pays off if governance is built in at the same time.
What integration debt actually is
Integration debt is the gap between the integration estate you have and the one you can safely and cheaply change. It builds up when interfaces are created for a project and then left alone. It shows up in four recognisable ways.
Interfaces nobody owns
The original developer has moved on. The business owner is unclear. Documentation, if it exists, describes an earlier version. When something breaks, the first hour is spent finding out who knows how it works.
Logic hidden in the middleware
Mappings, routing rules and custom code carry business decisions that no one has written down. Replacing the platform means rediscovering those decisions, usually under time pressure.
Monitoring that depends on people
Failures are found because a user complains, or because one experienced administrator checks the same screens every morning. There are no consistent correlation IDs, so tracing a document across systems means searching several logs by hand.
A platform with a deadline
Some debt is inherited from the platform itself. SAP Process Orchestration 7.5 (and PI 7.5) follows the SAP NetWeaver 7.5 maintenance strategy: mainstream maintenance until 31 December 2027, optional extended maintenance until 31 December 2030. Releases below 7.5 are already out of maintenance. A platform with a known end date turns diffuse debt into a dated obligation.
