Independent Software Maintenance
An Enterprise License Agreement (ELA) is a contractual agreement outlining the terms and conditions for IBM® software products and services. ELAs allow customers to set up certain programs with a maximum deployment number for a specific timeframe. Basically, they bundle vendor services for a fixed period of time at a set cost. The components of an IBM ELA can vary depending on the organization, but they are typically comprised of the following elements:
- Software licensing
- Terms and renewal
- Scope of use
- Support and maintenance
- Pricing and payment terms
- Compliance and audits
IBM ELAs, in particular, are complex, costly, and typically require a three-year commitment. They have many moving parts and require extensive planning in several areas, including hardware/software upgrades, capacity procedures, and software retirement strategies.
But is it really possible to accurately plan out every single requirement necessary for the entire duration of the ELA?
What if you get it wrong?
A one-year ELA can offer more latitude both in scope planning, as well as the option for more reductions in the future.
Identify your needs
When deciding on what size IBM ELA is best for your organization, it's important to have a clear understanding of your software usage patterns, maintenance needs, and future business strategies. Ask yourself:
- Why do I need this technology?
- What does it do?
- Have we used it in the past two years?
- Will we really need these products for the next three or more years?
Most companies don't use all the software solutions that come bundled together in vendor ELAs, and it's rare that anyone ever realizes the ROI value of their three-year ELA. Developing a realistic plan can help save budget dollars in the long run.
Be aware of the costs
While ELAs can provide cost predictability over the contract term, they often require significant payments upfront or higher overall expenditures compared to shorter-term agreements. Being locked into time-specific terms makes it challenging to switch to alternative solutions that might better suit your current needs.
This lack of flexibility can limit your ability to respond to changing market needs. Before committing, make sure to assess your budget and financial resources to ensure you can meet the financial obligations of a multiyear ELA.
Understand the risks
It's important to understand and plan out all of your IT estate requirements for the duration of the ELA to ensure you have a clear sense of the terms and conditions. Some questions to consider include:
- What happens if the vendor services decline or if there is a major disruption to the vendor organization?
- What is the cost if I want to exit the ELA?
- Will I pay more if I get my estimates wrong?
Reduce the term
It wasn't so long ago that five-year ELAs were the norm. Now three-year contracts seem to be more prominent. When you renew a three-year ELA, you are giving the software vendor a tremendous amount of leverage over your future IT plans. What if those plans change?
A one-year ELA can offer more latitude both in scope planning, as well as the option for more reductions in the future. Remember, it's your roadmap, not IBM's.
5. Get a trusted partner
Having an IBM ELA does not preclude you from working with a third-party software maintenance (TPSM) like Origina. You can keep your ELA and still use a TPSM company for software support and maintenance.
The best TPSM providers don't focus merely on support or just break/fix. They are strategic partners that can help develop your digital strategy and drive your own roadmap.
It's software on your terms.
Origina's independent global IBM experts all have decades of experience on the products they support and are to go-to sources of independent advice for everything in the world of distributed IBM and HCL software.
With the right strategic partner in place, you can avoid vendor lock-in and put a place in place that will benefit both your business plan and your IT estate.