BPM.com
  1. Peter Schooff
  2. Sherlock Holmes
  3. BPM Discussions
  4. Tuesday, 27 February 2018
  5.  Subscribe via email
A question Rachel Brennan brought up in a recent discussion about process modeling and low-code BPM. So how would you define low-code/no-code BPM?
Max Young
Blog Writer
Accepted Answer Pending Moderation
β€œThe test of the machine is the satisfaction it gives you. There isn't any other test. If the machine produces tranquility it's right. If it disturbs you it's wrong until either the machine or your mind is changed.”

― Robert M. Pirsig

NoCode BPM enables non-technical resources and build, deploy, and maintain their own BPM solutions. Low-Code BPM is such that shadow IT can do the same. The Test of the machine is it's functional interaction with the humans who use it. There isn't any other test.
References
  1. http://www.capbpm.com\iq
  2. http://www.capbpm.com
Comment
  1. more than a month ago
  2. BPM Discussions
  3. # 1
Accepted Answer Pending Moderation
A very good question. From a definition perspective, one could really simplify and rely 1:1 on the term, stating that "No Code (NC)/Low Code (LC)" means just that, the ability to create processes without or only very little code.
From an end user perspective, however, LC/NC does carry the connotation which implies an intuitive ease of use, allowing that none technical users of BPMS will be enabled to create fully functional, end-to-end business processes. I think, it is these different levels of abstraction in terms of UI's, flow charting and "feature building tools" to create usable business process applications, that in the mind of the end user ultimately determine a given BPMS platform to be LC/NC or not.
That, of course, implies that there is little to no code (and also very innovative concepts that I have seen, where the BPMS contains a natural language based set of scripts a user can read, understand, select, modify and "insert", while the code portion happens behind the scenes) - but also that all the rest that is needed to create a functional process that is easy to grasp, intuitive to use, fast to deploy and simple to be measured & improved upon, later on.
Having said that, I had a chance to see both ends of the spectrum of LC/NC - BPM platforms which, while not relying on the end user to program, are still very cumbersome and hard to use vs. BPMS that indeed are intuitive on all the aforementioned levels.
NSI Soluciones - ABPMP PTY
Comment
  1. more than a month ago
  2. BPM Discussions
  3. # 2
Accepted Answer Pending Moderation
A process-based solution may be implemented without coding in conventual programming languages. In other words,
1) the numerous business artefacts and relationships between them are sufficiently formalised to become digital;
2) they (artefacts and relationships) can be expressed in one or more DSLs and
3) an IDE is used to maintain them (by technical and/or non-technical people) in a BPM-suite tool.

Thanks,
AS
Comment
  1. more than a month ago
  2. BPM Discussions
  3. # 3
Accepted Answer Pending Moderation
Low-code is something I can see as realistic in platforms that need to accommodate a mix of structured and unstructured work.

In order to be able to evolve an inventory of processes that build competitive advantage, you need more than "canned" processes.

Canned processes are perfect for processes that are 'standard' (i.e. filling in an international letter of credit etc). Here, you can have no-code.

For any process that is unique to a particular corporation you need the usual set of capabilities (nodes/arcs/branching decision boxes/loopbacks/data collection forms).

Each node/form/decision box/loopback construct may need rules and unless you consider spreadsheet calculations as "no-code", then you must have a low-code capability at these constructs.

Most BPMs need reachout/reachin (import/export). Here, a generic data exchanger is a wise option and these require low-code. Without a data exchanger, your BPMs becomes an island.

Rules at process steps/forms and import/export facilities typically require help/assistance by IT but nothing wrong, of course, having a tech person embedded in functional departments that are active building and owning their own processes.

At the end of the day, there is not much to debate in the area of low-code/no-code.
Comment
  1. more than a month ago
  2. BPM Discussions
  3. # 4
Accepted Answer Pending Moderation
As the name suggests, Low-Code BPM refers to the capabilities provided by BPM Platforms to be able to develop process applications with minimum hand-coding. The idea is to provide development capabilities to non-developers or citizen developers. The advancement in technology has finally overcome all the limitation. Modern BPM Platforms a.k.a Low-Code BPM Platforms have not only simplified application development but also reduced development efforts manifold.
Kritika Pandey (Software Analyst)
Comment
  1. more than a month ago
  2. BPM Discussions
  3. # 5
Accepted Answer Pending Moderation
Modelling business processes, writing out SOPs and then creating a set of manual change management controls is a very low-code way of performing BPM!
Comment
Less flippantly: low-code/no-code is an approach to building software applications, using domain-specialised (often 'model-driven') tools. Some of these applications can be used to support BPM initiatives. But many of them aren't, at least not on purpose.
  1. more than a month ago
  2. BPM Discussions
  3. # 6
Accepted Answer Pending Moderation
This phrase Low code/ No code a tag that many are using but as ever in the "IT" industry lack of true definition of what it builds. Adding the tag BPM in my mind puts it into the delivery at enterprise software level (not just "apps";) and "citizen developers" should not be allowed near the important delivery of operational digital applications! Whilst we have proven the no code the creation of any enterprise application/case management (what is not a case in business) the build needs a professional business approach working directly with users who may be able to enhance functionality; hence how the tag BPM emerged? This does raise the question is it appropriate for the BPM supporting software to have this tag? If industry analysts did real deep research and could articulate to business exactly how such software delivers in their language then maybe ...........!?

So what does no code need to cover to deliver at enterprise level. Below is the list and should be delivered in an integrated "Platform"
1. Process engine - to ensure all works to plan.
2. Rules engine - reflecting real world of work and compliance.
3. Calculation engine - automating system work.
4. State engine - Real time feed back from any point.
5. Workflow - everything connected in right order.
6. Audit trail, events, escalations - = control with empowerment.
7. Rapid prototyping - user involvement in build no need for a final spec
8. Time recording - supports activity based costing.
9. Real time reporting - becomes predictive.
10. Build mash ups - one screen multiple data sources.
11. Linked intelligent Ajax grids - enter data only once.
12. Roles and performers - people and machines recognised.
13. Management hierarchy - see who does what and when to reallocate work
14. MDM Orchestrating legacy with business processes as required - recognition of valuable legacy data and functional systems
15. Call Web Services - wrapped up in a process.
16. User interface dynamically created linking people, roles, task type and data via forms for specific instances.- supports adaptive capability
17. Content handler and in memory work capability - to ensure high performance.
18. Pre-built templates for custom documents, letters, e-mails, messages etc dynamically populated with instance specific data and edit capability in browser - recognition of external communications documents etc
19. Process and task versioning control – ensures minimal disruption, if any, to implementation of changes

These are the fundamental support requirements to ensure delivery of all functionality for the enterprise and can start the delivery of meaningful automation in delivery of business digital processes. Our build is via a graphical interface which intuitively supports BPM and where custom configuration inserted. See link with summary on how our R&D evolved. The basic underlying principle is the fact business logic never has or will change! Sure IoT, internet, gadgets etc evolve but that supporting logic never changes.....all too simple for IT! Therein lies the real challenge as build time and removal of the layer of coding dramatically reduces costs and that is not welcome by the supply chain.

There will always be an important place for clever coders to build "AI" and "gadgets" which can be used in the operational business process. Indeed new ideas likely to emerge with this new freedom and flexibility at the front end of any business (including government) where real empowerment will encourage users to put forward ideas and deliver improved productivity were all can benefit.
References
  1. https://www.igi-global.com/chapter/object-model-development-engineering/78620
Comment
  1. more than a month ago
  2. BPM Discussions
  3. # 7
Accepted Answer Pending Moderation
I really liked short and concise definition from kritika pandey :)
But I'd add something from the customer perspective. When talking about no-code or low-code BPM, the customer is also thinking about a quick deploy of its processes, without complex installations or configurations, and most important, with the ability to iteratively improve their business process.

They expect to choose the tool and start modeling right now (not waiting a few weeks until it is installed and configured); they expect to model the process, press the "Deploy" button and have it running; they expect to detect bottlenecks using predefined KPI's (without configuring a Datawarehouse or BI tool); they expect to introduce changes in the process and pressing "Deploy" again they will be ready to be used (letting the software solve versioning and complex things).

I think the term #NoCode / #LowCode #BPM has a wider meaning than just avoid manually writing code to run a process in the business community, involving that all the BPM experience is easier and faster.
CEO at Flokzu Cloud BPM Suite
Comment
  1. more than a month ago
  2. BPM Discussions
  3. # 8
Accepted Answer Pending Moderation
I always wondered how appeared strong association between BPM and low-code solutions. As the name suggests, business process management is all about business and its processes. BPM has no direct relation to code.

What is code? In general terms, code is something tedious, cryptic and poorly recognizable. In other words, something insufficiently understood. In IT context, we deal with programming code, which represents our instructions to computer to do what we want.

How appear large amounts of code? Primary source of excessive coding is poor awareness of developers on their subject area of business applications. Better you know your area, less words (code) you need to describe it, simpler and smaller will be your solution.

Why BPM yields low-code solutions and environments? It happens due to aggregation of business knowledge. Systematic and well organized knowledge of business created by BPM serves as a ground for overall code reduction.

Low-code BPM is the code of business.
Comment
Usually, the business architecture is responsible for "code of business".
  1. more than a month ago
  2. BPM Discussions
  3. # 9
Accepted Answer Pending Moderation
If you listen to low-code BPM marketers:
Low-code BPM = the use of combined, pre-packaged, artifacts to quickly deliver generic application functionalities that support business processes.

If you listen to actual low-code BPM developers:

https://preview.ibb.co/kqE2nc/lowcode2.jpg
CEO, Co-founder, Profluo
Comment
Easy remedy. Fire both groups
What, when you've just IPO'd? :-)
Your picture illustrates a bad architecture.....
  1. John Morris
  2. 9 months ago
  3. #5122
LOL @Bogdan's illustration, which is like a Rorschach blot on attitudes to coding. @Walter says "fire 'em!". @Bogdan says #IPO! And Dr. Samarin says #Architecture! I ask "where are the business concepts?"
@Alex: really? what gave it away? ;-)
We're on boarding now someone from a very famous low-code platform (can't say names because IPO and whatnot), he said low-code is an absolute shameless lie - there's horror stories of massively failed projects, feverish endless obscure scripting behind the scenes just to make it stand on its feet, tens of consultants brought from abroad with conflicting approaches and advice, burying the very few ideas that had a slim chance to bring the projects back on track...
  1. more than a month ago
  2. BPM Discussions
  3. # 10
Accepted Answer Pending Moderation
What can be added to the excellent notes already?

Lo- or No-Code BPM is BPM. Real or pure BPM.

Because BPM is the automation software of the repetitive work of business. Only in BPM are the concepts of process and work first-class citizens of that technology, by definition.

One could ask instead, what is code doing in my BPM product?

And the answer is that ideally, code is shouldn't be "in my BPM product".

There's all sorts of categories of code that are necessary for BPM-as-technical-platform (tooling-related and integration especially), but this code is present in any software product. If there is code specifically related to BPM in my BPM product, then my product is not yet mature. The mathematics and engineering of my BPM product are not yet sufficiently powerful that my business analysts can work only using native business process-related concepts (and natively in associated complementary technologies such as rules etc.)

The round-trip issue is the best example of code-in-BPM because the technology is not yet mature. This code-in-BPM describes most BPM-for-sale today, and the vast majority of the BPM process installed base.

One shouldn't consider the fact that BPM still includes code as a failure; BPM science and engineering continues to progress. And however much one appreciates the marvel of code (and even the thrill of coding), code is only an enabler of BPM. But future BPM will be used by future business analysts without code. This is comparable to how today accountants use accounting software without any reference to code. Accounting software just is.

Does this question matter? I say yes. Because asking "why code" enables us to take code off the table, the better to focus on the real power of BPM, the use cases for BPM and the business cases for BPM. No one buys BPM software because it's a great coding tool. BPM software is bought because it can, maybe, please, help me solve a business problem. Faster. Better.

#businesssemantics #softwareexpressiveness #businessanalysis #accounting
Comment
  1. more than a month ago
  2. BPM Discussions
  3. # 11
Accepted Answer Pending Moderation
I see low/no code BPM as basically just another feature of a true BPMS. It's an add-on. A selling point. Yes, you can create enterprise level, complex, fully integrated BPM solutions that span several departments with our software, but you can also have a power user in a single department create a vacation request form and approval flow just for that department. The low/no-code option just adds to the ROI we already know a well rounded BPM solution can provide.

If a platform ONLY has low/no-code, I'd stay away from it; but if they offer medium to high code options in addition to low/no-code ones, then you have something worth looking at.

That is, as long as the low/no-code solutions that are built from the platform are governed properly. One fear you have with low/no-code solutions is the inevitable application sprawl that will happen as users start spewing out solutions like we've seen with Excel, Access, and SharePoint.
Managing Director
ClearCadence, LLC
http://www.clearcadence.com
Comment
  1. more than a month ago
  2. BPM Discussions
  3. # 12
Accepted Answer Pending Moderation
Followed comments with great interest...clearly disbelief exists that no code can deliver. Well it does and in context on some comments a few observations.
Bogdan touches on claims failing to deliver and he is probably right. If an IPO based upon mis information that becomes a serious issue.....this is where independent and deep research by analysts should sit?
John raises the power of BPM and is right but it does need that supporting software where users can have direct just put without need to negotiate with coders! He is right "But future BPM will be used by future business analysts without code." So where are the analysts doing research for end customers...not for vendors...?
Kevin makes a couple of good points. Yes there will be occasions where there is a need to code involving complex situations and any platform should readily enable this. As for application sprawl and spewing out solutions this is just not going to be allowed to happen in enterprise operational software. There must be full accountability for all actions unlike the chaos of spread sheets SharePoint etc. Delivery of adaptive applications with real time feedback on activity will empower users and encourage their ideas to be quickly addressed with good structured BPM discipline. As John indicates the professional business analyst will build. Yes there may be situations where users can effect a change by building in that capability but always tracked with accountability which enables empowerment.
Comment
  1. more than a month ago
  2. BPM Discussions
  3. # 13
Accepted Answer Pending Moderation
To start with the fundamentals, Low-Code/No-Code platforms essentially help a user to speed up the development of any application. By accelerating the application development, the user tends to focus on fast-ramp of the organization, rather than killing the time in weeks or months of coding.

Though the term low-code/no-code is perceived to be something that simply means "minimal or absolutely no coding", the underlying meaning is slightly profound. "Any low-code/no-code platforms must empower the business users to develop complex and functional applications in a simple and intuitive interface i.e. drag-and-drop, that does not demand any technical knowledge from them."

Simply put, "In a low-code/no-code platform, while the business logic of the application is taken care of, by the user, the technicalities are taken care of, by the platform per se."

Now, what if such low-code platforms enable a business user to build fully functional business applications to automate their business processes, without relying on the technical team? Those are the ones that are called as "Low-Code/No-Code BPM".

The most effective low-code solution not only cuts down on coding, but also helps you to get rid of the need of development environment, internal infrastructure and any such complexity.


Check out the article below, to know why BPM software vendors are forced to shift their base to low-code.
References
  1. https://kissflow.com/bpm/low-code-bpm-software-reasons/
Comment
  1. more than a month ago
  2. BPM Discussions
  3. # 14
  • Page :
  • 1


There are no replies made for this post yet.
However, you are not allowed to reply to this post.