Business Process Management (BPM) tools are hard to define precisely because they do not fit into any particular business silo.

Imagine for a moment, the various operational and support units in your own business, and the myriad processes, manual and automated, that exist within them. Now imagine a BPM tool as being the glue which holds them all together – the reason a BPMS cannot be siloed is precisely because they are so flexible and adaptable to manage and report on whatever the process is, irrespective of what the department it runs across.

Traditional BPM is an exceptionally adaptable and flexible tool set, but they do have some drawbacks. They are expensive to buy and to support – $200 per month per user is a realistic assessment of what a BPM suite from Pegasystems, IBM or Oracle will cost.

Traditional BPM tools will also require a heavy investment of time and resources, notably IT, specialist coders and developers, and it is not unusual to see external partners such as Capgemini, Accenture, PwC, or Deloittes involved too.

Time to deploy is lengthy with anything from 6 months to 2 years being the norm, and implementation can take longer than that.

How Low Code BPM Handles Traditional BPMS Disadvantages

Low Code BPM removes some of the extraneous functionality of traditional BPMS’, such as simulation or data buses. By focusing on core BPM functionality such as workflow automation, enterprise task management, visual workflow design, and automated alerts and notifications plus distributable reporting and compliance logs, low code BPM is able to deliver what you really need, and are most likely to actually use.

The biggest hurdle low code BPM addresses is who will actually be able to create or modify business processes, and push them into the live, operational environment.

An interesting overview of a Low Code BPM solution is included in the following video:

JobTraQ Introduction from Swift Software on Vimeo.

Traditional BPMS’ are used something like this:

Business analysts, operations staff and process owners identify a new process they want to create, or modifications to an existing process which they hope will improve performance.

After they have designed the new process, or know what modifications to the existing process they would like, a statement of requirements is constructed and handed over to the IT department. IT assume responsibility for the deliverables, and typically, they also need external resources and consultants to hit the deliverables.

This is time consuming (6 months or more), expensive and risky – more than this, in an operational environment which is fast-changing, by the time the changes are made, the needs of the operational environment have moved beyond what was thought to be required. In other words, Ops are always behind the 8-ball, trying to keep pace, while IT can never deliver a solution in time for it to be optimally useful.

The Low Code Approach

Low code BPMS’ seek to minimize the time to deploy by using pre-set business rules and processes, this dramatically reduces the amount of coding which is required.
In some rare instances, no coding input is required at all, with BA’s and operational staff able to use a visual workflow designer/UI to make changes, and then have the work platform push the changes live, creating task lists, automated workflows and enforcing business rules and reporting.

Because there is a greatly reduced time to deliver, low code platforms are much more responsive to the demands of customers and the operational environment. They provide a streamlined approach to process management, which is not only faster, but much cheaper too.

An interesting article on the use of low code BPM is found here by Dee Carri

Examples of Low Code Platforms: this is actually a No Code or Zero Code solution combined with advanced BPM functionality (marketed as Lean BPM – it is the only BPMS we are aware of which does not require specialist coding involvement and is for use by business people rather than technical or dev staff).



Leave a Reply

Your email address will not be published. Required fields are marked *