Mercantil Bank: Adopting and Adapting Itil® Rosal Urdaneta
Mercantil Bank: Adopting and Adapting Itil® Rosal Urdaneta
Mercantil Bank: Adopting and Adapting Itil® Rosal Urdaneta
Rosal Urdaneta
Case study
August 2018
Contents
1 Who are Mercantil Bank? 03
5 About AXELOS 08
As a bank, business interruption is unacceptable, as that means ‘money loss’ as well as possible regulatory
violations. We work together with the business to implement and maintain services for our internal and
external customers.
IT service management (ITSM) has become the solution to many historical issues, including discontent
with IT. One contention was that IT had no statistics or fact-based information that could help us identify
the weaknesses that affected the delivery of services.
The adoption of ITIL was a learning and sharing experience which helped us understand how we could do
better as a department. ITIL allowed us to see that we needed to set an expectation for users with regards
to our response time, etc.
Previously, everything that came into IT entered through one funnel. There was no distinction between
requests and incidents, which made it difficult to identify how to prioritize our response. At the same time,
we were limited with our ticketing system because our ITSM tool was not ITIL-compliant.
User tickets ended up in a ‘black hole’ once they made it to IT. Consequently, users had no visibility
regarding the status of their ticket.
In addition, we were restricted to just two service level agreements (SLAs): three days for failures and 30
days for requests. This was a problem because, for example, not every request takes 30 days. There was
no prioritization and we ultimately learned the definition of the word ‘backlog’.
With the acquisition of an ITIL-compliant CMDB tool that works with our other ITIL processes, we are now
able to maintain an updated CMDB which is available to both IT and Info Security. This means we have
full ownership of the information.
This lack of control over changes made troubleshooting more difficult and less efficient; identifying the root
cause of a problem was based solely on trial and error.
We introduced a Change Advisory Board (CAB) which meets every week to agree on the implementation of
changes. The stakeholders talk to each other before a decision is made and, if users will be affected in any
way, we send out a communication to let them know how they will be affected. Also, certain changes are
now postponed if they conflict with a systems update or on-going maintenance.
We have moved from an approach of ‘what happened?’ to ‘how did it occur?’ We find the root cause and
work out how to do better next time.
While the IT teams embraced ITIL, it took us years to get everyone else on board. However, as it became
more widely adopted and people began to see positive results, they joined the culture. It has taken time
and education to bring our staff along the ITIL journey.
ITIL exposed many of our previous deficiencies in IT, to the point where today we often bring an ITIL book
to meetings to support our discussions, (for example, with the Information Security team) because we
know it works.
The business now understands that each business process needs an owner, (otherwise known as a
business relationship manager), who works with IT to improve how they work. As we grow and mature,
different roles have become relevant. Each needs defining along with the services they relate to.
Additionally, the bank has implemented project management methods, which are supported by ITIL.
The plan is to create knowledge articles at the conclusion of every project implementation. Similarly, an
article will be created each time we find a common solution to an IT-related issue. Users don’t always
realize they can do certain tasks themselves; we need to improve the knowledge base so they can source
this information. This is our goal for the next six months; we need to communicate how users can benefit
from the changes we are making.
zz Don’t introduce KPIs or CSFs that are too difficult to calculate or measure
zz Don’t create an ITIL role unless it is necessary.
Rosal is certified in ITIL Service Strategy, ITIL Service Operations, and Six Sigma Green Belt.
She has been married for 17 years and is a mother of two boys. Rosal considers managing the three men
in her life as another full-time job!
The methodologies, including ITIL®, PRINCE2®, MSP® and the new collection of cyber
resilience best practice products, RESILIA®, are adopted in more than 150 countries to
improve employees’ skills, knowledge and competence in order to make both individuals and
organizations work more effectively.
In addition to globally recognized qualifications, AXELOS equips professionals with a wide range
of content, templates and toolkits through the CPD aligned AXELOS Membership and our online
community of practitioners and experts.
Visit www.AXELOS.com for the latest news about how AXELOS is ‘Making organizations
more effective’ and registration details to join AXELOS’ online community. If you have
specific queries, requests or would like to be added to the AXELOS mailing list please contact
[email protected].
Reuse of any content in this Case Study is permitted solely in accordance with the permission
terms at https://www.axelos.com/policies/legal/permitted-use-of-white-papers-and-case-studies
Our Case Study series should not be taken as constituting advice of any sort and no liability is
accepted for any loss resulting from or use of or reliance on its content. While every effort is
made to ensure the accuracy and reliability of information, AXELOS cannot accept responsibility
for errors, omissions or inaccuracies. Content, diagrams, logos, and jackets are correct at time
of going to press but may be subject to change without notice.