In today’s world where organizations are focused on digitalization and optimizing their operational performance, automation is one of the key drivers to success. The possibilities for automating business processes are virtually unlimited nowadays. This is what Gartner sees as Hyperautomation. Hyperautomation is a business-driven approach to identify and automate as many business and IT processes as possible. It requires the orchestrated use of multiple technologies, tools and platforms, including RPA, low-code platforms and process mining tools.
To stay in control in this fast-growing automation landscape, it is crucial to have a holistic oversight of all the automation initiatives that are being executed in the organization. Hyperautomation is business-driven, so you need something we like to call a ‘digital twin of the organization’ to have control, gain insights and set priorities for what automation is done on what business process.
Mavim is the process backbone to facilitate hyperautomation. We created an API with a connector to the Microsoft Power Platform. This opens up a vast number of possibilities to automate processes from a process perspective, by creating automated integrations where business applications both provide and consume vital ‘process-information’ from your Mavim repository.
The Microsoft Power Platform has thousands of connectors and the Mavim connector is one of them. This means that you can create all sorts of automations where information stored in Mavim is used to feed other business applications or to automatically import or update information stored in Mavim. These three use cases will show a little bit of the possibilities.
Use case 1: Mavim and Azure DevOps integration
Azure DevOps is used in many organizations. It is used largely by teams that work in an Agile approach. Not only IT development teams use it to manage their development tasks, but in all sorts of situations where teams are working together on a set of tasks, Azure DevOps is used to keep track of progress. Take for instance the area of Application Implementation Management. Azure DevOps is used by consultancy firms that implement large applications like CRM and ERP. They have their standard way of working defined in Mavim to describe and visualize the default CRM or ERP processes. When they start a new project, this default set of processes can be duplicated into Azure DevOps to start working on the implementation project.
Use case 2: CMDB / IT Asset management to Mavim import and update
TOPdesk is an application that is used by many organizations for both incident and asset management. Assets, for instance, can be all software applications that are used within the organization. Within TOPdesk, incidents can then be related to applications. From a broader perspective, organizations also want to relate applications to the business processes managed in Mavim. With the Microsoft Power Platform and the Mavim API you can now create workflows that periodically read all the applications managed in TOPdesk and import them in Mavim. You can make this integration smart by updating the TOPdesk application asset with the ID of the created ‘application’ topic in Mavim. By doing this, the workflow can not only import assets once but can run periodically to create newly added TOPdesk assets and update existing TOPdesk assets in Mavim. You can even decide what fields from TOPdesk you want to update in Mavim!
Use case 3: Import all job titles or roles from Active Directory into Mavim
One of the important features of Mavim is that you can create ‘Who’ relationships between processes and job titles or roles in the organization. This makes it possible to create RACI matrices that provide insights in the segregation of duties. The difficulty is often to keep track of the actual job titles and roles in the organization. They tend to chance very often which make your RACI matrices less useful. With the Microsoft Power platform you can connect to your Azure Active Directory or your Office 365 User Profile service to query all active users and get a complete list of their job titles. This list is then imported into the Who relationship category in Mavim. By running this workflow monthly, you always have an up-to-date list in Mavim of the job titles begin used in the organization.
These are just three common use cases you can now achieve by leveraging the Mavim Power Platform connector. Interested to learn what this can do for your organization? Please contact us!
Author: Lennard van Leuven, Value Engineer at Mavim