So let me introduce to you Dave Favereau. Dave is responsible for global enterprise architecture at Adecco. For those of you who don't know who Adecco is, Adecco is the second largest HR provider around the globe.
And I've had the opportunity to spend time with Dave and the Adecco team through their evaluation of our solution over the past year and a half, and I think what you're going to see in how they're utilizing Evolve today is going to give you some ideas in how you might like to do things and see how Evolve can be scaled. So with that, Dave, I'll hand it off to you.
OK. Thanks, Wendy. So hello everybody. It's a pleasure for me to be here and to present what we did with Evolve in Adecco context. Just before getting into a really big usage of Evolve, maybe I can present you a bit what is our company doing. Can you present the slide, Victoria, please? OK.
So our company also, we are HR service leader since 1996. So we are competing mainly with actors as consultant and mentor. We are implemented across 60 countries, so which means that we have, as any international company who are facing a cultural, I would say, challenges. The key challenge also we have is that the maturity of the market is not the same. And the kind of HR service we are providing across countries are differing from a country to another.
Just to be clear on what are HR services, it's going from temp staffing to a permanent staffing. It's also include all the training part of that outsourcing of HR activities as a recruitment, even payroll in some countries. And help in restructuring companies when they are in difficulties.
One of the key challenge for this or coming from this is that Adecco is still structured as Region. So this means that each Region is responsible for its own results, which is sometimes quite challenging at local level to get consistent enterprise architecture practices.
And the maturity is really differing from a country to another. As a result, we [INAUDIBLE] with a catalog of solutions, so really a portfolio of application across Adecco, which is more than 1,000. Now we have [INAUDIBLE] about 1,200, which is quite complex. And provide us a strong challenge to getting the future business model which will be more digital and which will require to have data structural harmonization and even application harmonization.
So what would we do? Next slide, please. What we did so far, in 2017, we went forward in enterprise architecture team and we started to build a simple framework on architecture based on the standard, I would say, of enterprise architecture. But we [INAUDIBLE] as TOGAF or other standard. In order to notify the countries, we were most of the time pushing back complex standard also.
But we are relying on key principle as business on that architectural solution, architectural infrastructure and security. And we embed all of our framework. We have a project management framework. In order to be able to get the more information we can, in order to gather information about new solution, solution which were already in place, and we use Evolve in order to store it in our Catalogue of Solution.
So our Catalogue of Solution is really a central repository which is key in order to enable enterprise architecture activity. How did we move or how did we land with erwin Evolve solution? Next slide, please. So just to be-- Victoria? All right, thanks. So just to be clear, the structure in erwin where IT-- the way IT was structured in Adecco has evolved along these years.
Before 2012, we were really country-focused. We started or we tried to build a catalogue or portfolio of application, so Catalogue of Solutions, using SharePoint. But as we global team wasn't so influencing the countries and countries were perceiving this as a redoing or doing providing kind of reporting to corporate. It was not working.
In 2012, we start a big, big program in order to try to harmonize both solutions and business processes across Adecco, which was called Everest. Here all the IT team went or become global. Here we used this opportunity to gather the maximum of information around overall application which was implemented across Adecco.
And we store it in Excel spreadsheet. And we just try to use Mega as a tool but Mega was quite complex and quite expensive. And we received a big pushback from people in order to update the data directly into it. So we were really using a lot Excel.
When starting 2017, we changed a bit, our organization, by balancing better the power of countries versus the power of corporate. And so be more close to our business requirement. By doing this, we were [INAUDIBLE] was continued and we enhance our Excel spreadsheet. However, it was quite limited so we started to assess a solution in order to be able to post all the information we have gathered so far in a central repository which was accessible to everybody.
And here came erwin solution. Next slide, please, Victoria. So our key principles was, the first one, really to be able to fit the maturity of the various countries. Because some countries was really small and there were no dedicated architect able to understand what was the various dimension of a solution we need together, so we need to keep it simple as much as possible. And to capture the minimum of information from them.
But for the more mature countries and as a target where we want to go, we needed to do to provide some capabilities which were more powerful in terms of storing information. It was really one of the first quarter. Yeah, the second one was really maybe most of people were working and on top, as Adecco took care of honoring that.
But at the end, as the
13:28