Application Portfolio Management (APM) Best Practices - Connect APM to the Vendors and Suppliers Inventories to assess vendor health, concentration risk, and strategic alignment
Application Portfolio Management (APM) Best Practices
Connect APM to the Vendors and Suppliers Inventories to assess vendor health, concentration risk, and strategic alignment
Overview
The vendors that supply enterprise applications are themselves a source of portfolio risk that is entirely independent of the applications they provide. A financially unstable vendor creates continuity risk for every application it supplies, regardless of how well those applications are currently performing. A vendor acquired by a competitor may immediately create strategic conflicts around data, pricing, or roadmap direction that affect the long-term viability of the applications it supplies. Overreliance on a single vendor creates concentration risk that amplifies the organizational impact of any disruption that vendor experiences. Without visibility into the vendor landscape behind the application portfolio, these risks are invisible until they materialize.
Best Practice
Establish and maintain a direct connection between every application in the portfolio and the vendor entries in the Vendors and Suppliers Inventories that supply and support it. For each vendor connection, ensure APM has visibility into the total applications supplied by that vendor, the total annual spend across all products, the vendor’s financial health and stability indicators, the strategic importance of the relationship, and any identified concentration risk. Review the vendor landscape at least annually as part of the portfolio risk assessment. Identify vendors that supply a disproportionate number of critical applications and develop contingency plans for scenarios in which those vendor relationships are disrupted.
Benefit(s)
Connecting APM to the vendors inventory makes the vendor risk embedded in the application portfolio visible and governable. Concentration risks are identified before they become crises. Vendor financial instability is monitored proactively rather than discovered through service disruption or product discontinuation. Strategic misalignment between vendor roadmaps and organizational priorities is surfaced in time to evaluate alternatives and develop transition plans rather than being discovered when the misalignment has already become a constraint.
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers