This week I got a quick update on Kofax’s TotalAgility product and business (acquired when it bought UK-based BPM technology supplier Singularity in December 2011). A few days previously the company had formally announced TotalAgility 6.0, with the key headline being availability of the technology on Microsoft’s Azure cloud platform (and feature parity across cloud-based and on-premise delivery for customers).
To get to this point, the former Singularity developers have had to do a lot of work, although this project was already underway before the Kofax acquisition – and supporting Azure is a logical move for a BPM technology player with a deep commitment to Microsoft’s platform, applications and ecosystem. To be clear, Singularity already had a hosted offering (LiveAgility) – but previously, this was offered to customers on a case-by-case basis and because the Designer environment was a Windows-based application, it relied on a number of assistive technologies to work in a hosted configuration. Version 6.0 of this development transitions all elements of the technology to web-based front ends, along the way implementing a much more intuitive design experience.
The runtime system has been redesigned around Azure’s platform architecture to enable multi-tenancy easily: something that Kofax wants to promote to its BPO and multinational enterprise customers as well as offering to customers itself. This extends TotalAgility’s proposition for these communities beyond another method it already offers for managing variation in large implementations: “process skins”.
It’s already clear that, as well as supporting the Kofax headline position of “Capture enabled BPM”, the company intends to continue developing broader opportunities around structured process as well as case management scenarios. In the Microsoft-centric part of the BPM technology supplier community, Kofax is undoubtedly serious about capturing (ho ho) a leadership position.
I’m going to be getting a deeper dive on this new release as it nears its general availability date (currently September 2012), and we’ll be publishing a new analysis of the offering soon after that.