The Leonardo Blog

An organisation should be looking for ways to continually add value.At it's core Customer Experience Management understands what is of value for a customer, and how we create/deliver value, that will lead to actions that result in a good customer experience.

Integration efforts are frequently suppressed by the high cost of latent resources, slow delivery models, expensive licensing alongside the battle of retaining the capability of staff year on year. The maturity of open source combined with advancements in cloud technologies presents great opportunities to realise the potential of a scalable, subscription based integration to meet business challenges & drive business transformation. Below is a transcription from the presentation by Adam Mutton at the Red Hat Forum in Sydney, October 2017. -- The maturity of open source, combined with advancements in cloud technologies has presented a great opportunity to realise the potential of a scalable subscription-based integration model that meets business challenges and drives business transformation. I'm here today to talk to you about the direction Leonardo was seeing integration heading in, and how we see it driving towards a replicable, repeatable, and robust model of integration, and what kinds of tools and services that are required to make that a reality.

Since the first release of ARIS Connect, the concepts of publishing in ARIS have changed and lightweight workflows were introduced to provide basic support for the governance of process models. These new features have brought new and interesting experiences. However, feedback from ARIS customers with unique needs for rigorous process model governance indicated that more is needed than the lightweight workflows—like, for example, a workflow for publishing models in isolated repositories to ensure consistency for reporting and analysis. Although the gap left by the lightweight workflows can be filled by a fully-fledged ARIS Process Governance engine, budgets are often a barrier. On the other hand, manual administration (e.g. the handling of models across several repositories without the support of automation) requires a fair bit of maintenance.

Is process modelling difficult? It sounds quite straightforward: processes are to be modelled—arrows and boxes—this happens, and then that happens. Let’s just get on with it!

It's just getting too hard to support the business that wants more flexibility, cheaper service provision, faster implementation, connectivity worldwide and the supply of information to multiple user access devices. All must be delivered on a reduced budget.