It was Monday morning and there was a cheerful atmosphere among the company's IT staff. They had worked on a new project release for over one year, the acceptation testing had resulted in a convincing GO, and the deployment to the production environment had taken place during the past weekend without a single hitch. Everybody was optimistic and ready to see the results of their hard work. But it wasn't how they had expected it would be. Users called in with complaints. Their Excel sheets, which contained some custom scripting, didn't work anymore. The report they relied on gave errors. The small piece of crucial software, of which IT never knew its existence, hung on them. What had happened?
As the saying goes "Failing to plan is planning to fail", we started a quest for a planning tool. Requirements? Well, we had plenty of them. The planning tool should be flexible, should provide reports, should be accessible for everyone and should be configurable to our needs. Along the way, we tried out the Office 365 Planner, a member of the Office 365 suite. For our goals, it is a promising tool. And so, we would like to share our vision on it and explain you how you can set up your own Planner.
There was a time when integrating two typical applications required experienced integration specialists. Applications were often very dissimilar and hard to access and the tools used to create integration solutions were equally complex and only really usable by highly skilled and experienced specialists.
Although these cases very much still exist today, we can now also see cases in which people with a lot less technical expertise also integrate applications. This is possible because the applications they integrate are different from the ones we described before, and because the tools which are available to them are also very different from the ones traditionally used by integration specialists.
Building APIs is not without challenges. While APIs can be considered strictly technical assets, the best APIs are often built by multidisciplinary teams because there are just so many things to think about. In this blog, I’ll share some simple rules to get you started.
With the introduction of new generation privacy and data protection laws, including our GDPR, the need for personal data classification towards compliancy is an absolute must. The requirement to be proactive is not only a feature of the GDPR, it can also be found in other privacy frameworks around the world like CPBR for all APEC countries. Thus, we have our newly introduced information classification policy, privacy classification policy, but how do we put those into practice?
Recently we started a project where the customer asked us to set up and manage a software selection process. The new software would replace the existing, outdated and lacking solution. One of the challenges involved in the assignment was that we needed to be open to both commercial off-the-shelf products and custom-made solutions. Since the solution was part of their business-critical systems, simply browsing the internet and trying a few demos would not suffice.
In this blog post I will explain how we managed the selection process.
End of last year, we thought it would be a good time for all our consultants in the integration unit to get some more insights in the key concepts of API management and to get some really hands-on experience with a variety of software from different vendors, and have some fun while we’re at it. What better way to do that than to organize our own API management hackathon!
When modelling information, it is important to balance easy to understand high level overviews with accurate and detailed models. In the beginning of a project, all there is are high-level overviews. Often they are not yet complete, and they are not very useful once you get into the details.