Too many system integration providers promise a simple journey to success, but in reality, this is far from what ends up happening.
At ONEiO we've seen through countless successful system integrations, and we have observed some clear mistakes. A common pitfall is saying... "I just need to integrate these systems with each other – what does it cost?"
Here are 9 important questions to ask when starting a system integration project:
1. Why are you integrating?
2. Do you have a Project Manager?
3. What other resources do you need?
4. What systems are you looking to integrate?
5. Are your systems running in the cloud, on-premise or hybrid?
6. Do you have enough knowledge of the systems you are integrating with?
7. Have you defined the use case you are looking to integrate?
8. Have you defined the field and value mappings?
9. Have you defined a test scenario that you are looking to run?
So how do we stop this from happening?
There are many things to take into consideration when thinking about the whole integration project and we want to help you identify and address these.
The real question is: "How do we do it and how much does it cost?".
To answer that, there are 9 vital questions to be answered first.
1: What are you integrating?
This is a multiple-choice question, and here are your options:
- Customers
- Service Providers
- Internal systems
Why are we asking this?
Integrations always have (at least) two ends. It's important for you to understand that the complexity of the project might vary between these parties. Are you able to control both ends, does the customer or service provider have somebody from their end to work with you?
2: Do you have a Project Manager?
- We have someone in-house who runs the show
- The service provider or customer is providing the Project Management
- We are using an external provider / consultant on the project management
Why are we asking this?
Like in any project the manager plays a crucial role in the success of the end result and keeping the elements together.
3. What other integration resources will you need?
- Tool admin?
- Integration architect?
- Process owner?
After you have sorted out questions 1-3, we can move forward. And now the project will be divided into two tracks. Technical and process tracks.
Let's start with the technical track.
4: What systems are you looking to integrate?
- Application 1: __________________
- Application 2: __________________
- Application 3:___________________
- Application n:___________________
Why are we asking this?
The complexity of the system and depending on how sophisticated it is might have an effect on the total time and effort needed to execute the project. We have seen all kinds of interesting systems and API's in our life.
5: Are your systems running in the cloud, on-premise or hybrid?
- Cloud
- On-premise
- Both
Why are we asking this?
This might not have a direct cost related to the project, but it might slow things down. When opening firewalls and allowing IP addresses there are usually certain policies in place and those might take some time. So take this into consideration when planning the system integration project and thinking of the timeline.
6: Do you have enough knowledge of the systems you are integrating with?
- I know my own tool
- I know both tools
- I have no knowledge over these
Why are we asking this?
It's more of a fact than a myth that all tools and their characteristics are individual and designed in a unique way. Even if we avoid having to make changes in the corresponding systems. Sometimes you need to be able to create some triggers or web-hooks from your own system. Especially if you have something custom build.
7. Have you defined the use case you are looking to integrate?
- Yes
- No
- Sort of... (maybe you get the process, but it hasn't translated into a genuine use case yet)
Why are we asking this?
First of all, let's address the question: "What is a use case, really?"
Our experience shows us that the most important thing to understand is what are you looking to achieve. Meaning what is it that you are looking to do on a process and logical level? This is the most important part of a successful integration project and will define a lot on the length and success of the project.
8: Have you defined the field and value mappings?
- Yes, the fields and values to be mapped are clear
- Our side is done, waiting for the other side
- Nope..
Why are we asking this?
Mapping the fields and values that will be exchanged in the integration and the use case will ease the actual configuration work when setting up the integration.
9: Have you defined a test scenario that you are looking to run?
- Yes
- No
Why are we asking this?
When the configurations have been made to accommodate the use case, there should be testing involved. The test scenario and acceptance criteria's should be agreed with the parties prior to know if the project was successful!
Now, what is the expected cost of system integration?
Unfortunately, we can't answer without seeing your systems up close (boo!).
But it is very quick and easy to do, and 'just looking' won't cost you a dime. However, we are 100% certain that we can help you reduce the total cost of delivery with your next integration project.
This is great news for you because it means more profit, better value for your customer and a faster time to value.
At ONEiO, we have over 20 years experience in integrations. We've been there, and done that. We've seen all the pitfalls and successful projects.
Based on our vast experience we've created a tool to assess your integration needs and help with Request For Proposals for integrations and integration platforms. We call it Integration Landscape Assessment.
Download our Roadmap and Landscape Assessment and sample report to your integration success PDF by clicking the button below (no registration needed).
