Fednot supports the notary's offices with legal advice, office management, IT solutions, training and information for the general public. Given a complete transformation process to better meet the needs of all stakeholders and to attract new partnerships, Fednot opted for an integrated and API first approach. Due to the strong expertise within Archers and Integration Designers in the field of API management, Fednot put both companies in charge of the project. Fednot forms the centre of a large ecosystem, ranging from notaries and their IT-providers, as well as the government, banks and citizens. For all these parties, Fednot provides an answer to different needs. In the background, however, the solutions and answers to these needs are strongly connected. This shows how important it is for these parties to exchange information with each other in an efficient way.
With a view to the goal of letting stakeholders exchange information efficiently, Fednot decided to build a partner platform. A platform with the right API’s so data can be exchanged efficiently among the stakeholders but is also able to offer better services to citizens. For example, when a citizen buys a house, the notary invests the ground and the IT-provider puts the information in its system. Due to focused disclosure to the Fednot platform, the information can be easily communicated to all other stakeholders.
To put this into effect, the challenge was to question both the existing architecture framework and to re-evaluate it in the context of these new objectives.
Step 1: Choosing the right API management solution
First, a selection procedure was organized to look for the right API management solution for Fednot. To do so, a general architecture of how these API’s needed to interfere with each other was conducted.
A first requirement was the shift from SOAP to rest APIs. A shift that had to be made both to support the new API management solution and to integrate future APIs, allowing Fednot to offer more services around the platform like KPI monitoring, insight into partner relationships, etc.
Step 2: Embedding the platform on organizational level and internal evangelization
After the entire architecture had been drawn, it was time to move on to the second step: dive deeper into how they could embed this platform on an organizational level. For this, the foundations have risen from the 8 pillars below. (insert pic)
These pillars were the starting point to set priorities and to work out a roadmap
Step 3: Internal evangelization
After the embedding stage, the next step was internal evangelization. For the platform to be a success, it was of undeniable importance to get everybody at Fednot on board and give them a frame of reference. "Integration never stands on its own," Jolien says, "to make this a success, we needed the involvement of all teams."
Together with Archers and Integration Designers, internal groups and strategies on how to inform them, were defined. The first group consisted of the architects: they were informed on how to get involved in the new project and follow up on new integration projects. Then, it was up to the developers: they were shown the added value of the new platform and how they could ask questions.
To make this work, Fednot chose to work with Archers and their colleagues from Integration Designers. "Archers is well known in the world of integration, especially for their knowledge of API’s and Microservices. Integration Designers, on the other hand, for its enormous integration expertise," Jolien says, API Platform Manager at Fednot. “Besides, there is a huge community of experts behind both companies. Our consultants can always turn to their colleagues with cases and problems, which makes their network extremely strong. That’s why we’ve chosen to take on this integration challenge with them.”