What is our primary use case?
There are three main reasons that we started working with this product. The first one was to plan projects and report the savings. In this use case, we rely on GEP as a reporting tool for procurement.
The second reason we use it is for online sourcing. In this context, it gives us a platform to run online RFPs, RFIs, and online auctions.
The third reason is to use it for a contract repository.
How has it helped my organization?
In terms of how easy this product is to use, I would say something in the middle. It can be very complex, so it requires some training for the users. Especially for sourcing, it requires some detailed training.
It is possible to simplify things. We can create simple projects and simple sourcing events.
It's user-friendly, in terms of the design of the tool.
GEP SMART is a unified platform that has definitely affected our procurement operations. It is part of our procurement strategy that we increase the usage of online sourcing. The fact that we use project sourcing and contracts means that these three modules support our source-to-contract process, which is one of the key processes of upstream procurement.
The tool helps us, firstly because it provides clear reporting. Second, we gain additional and incremental savings through only sourcing, especially through online auctions. Third, it helps us to be more efficient and transparent within the organization. For example, in procurement, GEP SMART helps facilitate information sharing between teams.
Using this product has significantly improved the efficiency of our procurement process. The more products or sourcing events, RFPs, and auctions that we have in the system, the more efficient it will be with the next project because it can start as a copy of a previous one. Doing so significantly reduces the preparation time of the RFPs and auctions.
GEP enables us to create different templates that we can store in the tool and use. This shortens the time required to prepare the tenders and then publish them to the suppliers.
The platform also allows us to invite more suppliers because supplier management during the sourcing processes is faster and more efficient. We can manage multiple suppliers at the same time.
This product definitely saves us time when setting up an RFP. The first RFP needs to be created from scratch and requires some time but for any future RFPs, where we have things to repeat or do for a second time, it helps us to be faster and more efficient. The amount of time we save depends on the complexity of the RFP but it can be hours.
In summary, using this solution benefits our organization through cost savings, better efficiency, improved transparency, and having information archived.
With respect to the adoption of the platform in the company, for projects, it was pretty easy. It was also very well accepted because our key KPI is related to savings, which is done through the project reporting. This meant that people were highly motivated to use the reporting.
There is slower adoption for sourcing because it requires having quite good knowledge about how to use the product. Furthermore, the suppliers need to agree to participate in online sourcing events. It's not just about our company, but also about the suppliers, because they have to accept it.
It's going a little bit slower than we would like it but our company has a program running to help with this. We have been onboarding procurement teams in different affiliates around the world, and we teach them how to use the GEP solution for sourcing. This program has been live for approximately four years and we have onboarded between 25 and 30 procurement teams from around the world.
For contracts, the adoption is improving. Our aim is to have the top affiliates using all of the modules in three years.
What is most valuable?
The project model is used by most of the people in our company. It is where the official savings reports are generated.
Online sourcing is the most valuable feature for us, although we use all of the features.
We use the source-to-contract (S2C) functionality and our procurement excellence team is helping other procurement teams in different countries to use this platform. It makes them more efficient and more digitized through the source-to-contract process. Essentially, it helps us to digitize certain sub-processes.
What needs improvement?
There is a level of complexity when connecting suppliers to the platform, which is something that could be improved.
In terms of preparing the first RFP, certain documents need to be uploaded. Uploading this content should be easier and more user-friendly.
The support for additional languages should be improved. In particular, for some of the additional languages, or key languages, the tool works well. However, there are others for which it could be better.
The manuals, especially the ones for the suppliers, are currently available only in English. If these can also be translated into different languages, that would be excellent.
For how long have I used the solution?
We have been using GEP SMART for between six and seven years, since 2015.
What do I think about the stability of the solution?
For projects and contracts, this is definitely a stable system. However, for sourcing, we do see bugs from time to time. We need to report these so that they can be corrected.
Examples of bugs that we have seen are that the tool is running slowly, or there is some functionality that is not working the way it should.
From what I have been able to see, the English configuration is more stable than when some of the other languages are being used.
What do I think about the scalability of the solution?
This is quite a developed solution. It enables the users to employ it for really complex processes and projects. As such, the scale is pretty wide.
We have approximately 200 users for projects and these people typically have access to the reporting features. We have approximately 100 users for sourcing and an additional 50 users for contracts.
How are customer service and support?
We are in touch with the GEP team every two weeks to discuss various topics including usage, bugs, and enhancements. If we have any questions about the solution, they advise us. We are able to resolve issues and we can also submit requests.
The support can be split into two groups. The first group is the key account managers that we are in touch with regularly. I would rate them a ten out of ten. The second group is the helpdesk, who are generally the people that help whoever calls. I would rate them an eight out of ten.
Overall, I would rate the technical support an eight out of ten.
Which solution did I use previously and why did I switch?
We used another solution prior to GEP, but we switched because we found that GEP was better. GEP was also an improvement in terms of cost.
How was the initial setup?
The initial setup is of medium complexity.
What is important, or what would be key for any new start or any new implementation is to work closely with the provider. That is what we did at the beginning when we started with GEP.
We had a large training session with a small group of people, and then we disseminated the knowledge throughout the organization. By doing it this way, it made it smoother. It's definitely a good idea to dedicate some time in the beginning to understand all of the features.
The implementation and deployment took place over time. It may have been a month or two, to set it up initially but there was also the training. It was about one week that we sat together with GEP for intensive training sessions that explained how the different features worked. After that, over the years, we have implemented different modules.
The solution is available for those who want to start working with it, and they can learn it quite easily, but the whole implementation with all of the features is a journey that is linked to the internal processes.
What about the implementation team?
We did not use a third-party integrator to assist us with deployment.
We have a team of three people that are taking care of the functionality and deployment within the company. This team is a global sourcing team belonging to Global Procurement Excellence team.
What's my experience with pricing, setup cost, and licensing?
My advice is to think wisely when it comes to estimating the number of licenses that you will require. If you settle on a number too early and you need additional ones, then the extra licenses might be quite expensive. It should be discussed at the very beginning, before signing the contract if possible.
Which other solutions did I evaluate?
Prior to choosing a product, we went through an official RFP. We evaluated a couple of the top solutions in the market, and we were looking mainly into user-friendliness and adoption. We also looked at having different functions available, like the reporting of savings, and the various options for sourcing events.
We also wanted a solution that is available in different languages because our company is worldwide. In particular, when it comes to communication with suppliers, multi-language is a requirement. This includes not only the key ones but also the smaller and less often used languages.
In the end, it was the combination of all of the reasons, including the pricing, that we adopted GEP SMART.
What other advice do I have?
We do not use the procure-to-pay (P2P) functionality, as we have other tools for that.
My advice for anybody who is implementing this solution is definitely to start with training. In particular, the key users, or super users, should be trained at the beginning. I also suggest thinking about how it is going to be implemented throughout the organization. For example, will the power users be responsible for it, or will they have assistance from GEP? GEP can provide training for end-users.
It's best that the power users have knowledge of the system and how it is customized. Having a central team as the primary contact between GEP and the company is important. They can follow the information about the product, including new features, and changes to the tool within the organization.
I would rate this solution a nine out of ten.