Universal Process Notation
Universal Process Mapping[1] (UPN) is a graphical representation for specifying business processes.
Developed by Nimbus Partners (later acquired by TIBCO Software) in 2008 as an open standard, UPN is not proprietary to any company and doesn't require any specialized software..[2]
Dating back to the 1970s, UPN shares similarities with IDEF0 but has evolved to be perfect for the current day challenges of rapid business transformation, highly distributed teams and increasing regulatory compliance;[3] modern problems that plague businesses, disrupting and slowing development. This solution to business process mapping creates a more accessible notation that stakeholders at all levels can understand[4][5]
Overview
Universal Process Mapping (UPN) is an open standard for business process modelling that provides a graphical notation for specifying business processes in a business process diagram (BPD), based on a flowcharting technique very similar to activity diagrams from Unified Modelling Language (UML). UPN provides a simplified approach to describing process flows using visual diagrams, focusing on documenting the individual abstracted steps and providing context through directional flow, resource allocation and level architecture. Business process maps enable business analysts to engage end-users and validate business requirements.[3] Driving out waste, identifying improvements and forming the basis of user acceptance testing and training.[3]
By simplifying the modelling system so that any user can quickly understand the process outlined without having to learn a new 'language' comprising numerous symbols and notation standards, UPN has been designed to provide a standard notation immediately understandable by all business stakeholders. Enabling various groups, including business analysts, technical developers and business managers, to effectively collaborate in mapping various processes, functions or business goals amongst other uses.
By creating a hierarchical process map, where every diagram is easier to follow [6] and activities are at the same level of abstraction, resulting in a diagram equally relevant to all business users[7]. Providing usable process information to the executors of business process, while also encapsulating the technical needs of an IT audience. It is a universal and accessible notation for end-to-end process that is accessible and comprehensible to all areas of the business, regardless of background, seniority or discipline.
UPN Architecture
Creating a UPN based, end-to-end cross functional process which clearly communicates business objectives to all users ideally requires a top down approach. Producing not just a horizontal model from end-to-end but also vertical visibility for the purpose of process accountability and management.[8]
Elements of the standard
The UPN drawing notation can be summarised in this image of the activity box. All processes can be captured with just this one building block; these activity boxes answer the Who, What, When, Why and How of the business process.[9]
Here are some critical characteristics of UPN:
- Activity boxes describe what is going on and have a resource rather to denote the involved people/services.
- Annotated lines exist between activity boxes to describe why the process is happening, or show the current state of resources.
- Each activity box can have multiple directional outputs to express decisions and different paths.
- Activity boxes can be drilled down into to display more detail.
- Supporting documentation, used systems and metrics are attached to the relevant activity box.
The other fundamental principle of the UPN process mapping is hierarchy. Process diagrams are not meant to be stand-alone documents nor to be huge and complex; otherwise we risk losing context of how a particular process fits in with other operations or make them too big to understand. Each hierarchy level should describe events at the same level of abstraction.[10]
Process Diagrams
A process diagram is a collection of activity box and connecting flow lines that define a business process at the same level of detail. Enabling each individual user to understand business processes at varying levels of detail.[11]
Process Maps
A process of maps is a hierarchical collection of process diagrams
-
UPN Notation Summary -
UPN Process Diagram -
UPN Drilldown -
UPN Process Map
Diagramming Principles
In order to produce diagrams that can be viewed online and embedded into webpages and apps, process maps need to be small and easily understood.
- No more than 8-10 activity boxes on a screen.
- Activity boxes have 'drill downs' to capture sub processes.
- Activity boxes on the same 'level' of a process diagram should be at the same level of detail.
- An output from an activity box becomes an input trigger for the start of the next activity.
- Activity boxes feature 'resources' to signify who is involved in the execution of the activity.
Comparison with other process modelling notations
Flowcharts and swimlanes were commonly used by most analysts and consultants to capture requirements and business processes. UPN is a simpler and immediately understandable diagramming notation, proven in a range of businesses varying from major highly regulated industries to innovative start-ups and small non-profits[12]. Other notable process modelling notations include:
- Business Process Model and Notation (BMPN)
- Life-Cycle Modelling Language (LML)
- Subject-Oriented business process management (S-BPM)
- Extended Business Modelling Language (xBML)
- Unified Modelling Language (UML)
Alternative standards such as BMPN are often harder to read, due to the volume of different symbols and diagramming standards, despite fulfilling similar purposes. Although the more complex notation offered may enable a more comprehensive modelling of the business process, these alternatives typically have narrower scope; whereas UPN is universal and applicable in more situations. Standards with a larger selection of components and symbols will always be able to display higher degrees of detail more efficiently but typically require specific training to read, much like a new language. Such is the trade off between a complex high-level language and a minimal low-level language like UPN.
- Comparison between flowcharts and UPN
-
Comparison to Flowchart: UPN Process Diagram -
Comparison to flowchart: Flowchart
Jim Boots, who ran the Business Process Mapping program at Chevron, states in his book "Boots on the ground"; "*take any process drawn using flowcharting, swimlanes or BPMN notation and a UPN diagram will be smaller. Fact."[13]
From the images comparing a UPN Process Map to a traditional flowchart it is evident that, in general, UPN Diagrams are more compact, and more easily understood. With a clear left to right flow, and less ambiguity while maintaining a high level of information. Both diagrams describe the same flow.[14]
Further Reading
- Ian Gotts, Richard Parker (June 18, 2007). Common Approach, Uncommon Results: How Adoption Delivers the Results You Deserve. Ideas-Warehouse; 2nd Revised edition. ISBN-13 : 978-0954830915[15]
- The evolution of process diagramming
- Jim Boots (June 22, 2012). BPM Boots on the Ground: How to Implement Strategic Business Process Management: Lessons Learned from one of the World's Largest Organizations. ISBN-13 : 978-0929652160 [13]
- Universal Process Notation Articles, Mike Grammage
References
- ↑ https://www.getskore.com/what-is-upn/
- ↑ elementscloud (2016-06-01). "Universal Process Notation (UPN)". Elements.cloud. Retrieved 2021-05-21.
- ↑ 3.0 3.1 3.2 "Introduction to Universal Process Notation (UPN) for Salesforce Processes Mapping". Salesforce Ben. 2021-06-28. Retrieved 2021-07-23.
- ↑ "At last, a free alternative to BPMN!". www.linkedin.com. Retrieved 2021-08-27.
- ↑ "The 411 on Business Process Modeling | Lucidchart Blog". www.lucidchart.com. 2018-11-15. Retrieved 2021-09-06.
- ↑ "Business Process Modeling Techniques • Checkify". 2019-05-17. Retrieved 2021-05-21.
- ↑ "Business Process Modeling: Definitions, How to Start". Pipefy. Retrieved 2021-09-06.
- ↑ "TIBCO Nimbus UPN -universal-process-notation.pdf | Powered By Box". app.box.com. Retrieved 2021-05-21.
- ↑ "Business Process Modeling: Definitions, How to Start". Pipefy. Retrieved 2021-09-06.
- ↑ elementscloud. "Business process mapping". Elements Academy. Retrieved 2021-05-21.
- ↑ Bolduc, Benjamin; Hodgkins, Suzanne B.; Varner, Ruth K.; Crill, Patrick M.; McCalley, Carmody K.; Chanton, Jeffrey P.; Tyson, Gene W.; Riley, William J.; Palace, Michael; Duhaime, Melissa B.; Hough, Moira A.; Saleska, Scott R.; Sullivan, Matthew B.; Rich, Virginia I. (13 August 2020). "Supplemental Information 3: An excerpt from Data Downloads page, where users can download original datasets". PeerJ. 8: e9467. doi:10.7717/peerj.9467/supp-3. Retrieved 2021-05-21.
- ↑ Gotts @iangotts, Ian (2019-10-22). "The evolution of process diagramming". Medium. Retrieved 2021-05-21.
- ↑ 13.0 13.1 Boots, Jim (2012). Mr. Meghan-Kiffer Press. ISBN 978-0929652160. Search this book on
- ↑ elementscloud (2016-06-01). "Universal Process Notation (UPN)". Elements.cloud. Retrieved 2021-05-21.
- ↑ Gotts, Ian (2007). Mr. Ideas Warehouse. ISBN 978-0954830915. Search this book on
External Links
Elements.Cloud Principles of Universal Process Notation
What is Universal Process Notation (UPN)?
What is UPN? An alternative to BPMN
Whitepaper: TIBCO Universal Process Notation: A simple solution for complex process diagrams
Elements.Cloud Universal Process Notation (UPN)
Salesforce trailhead UPN Course
This article "Universal Process Notation" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Universal Process Notation. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
