Order Fulfillment and Procurement
Extracted from BPMN 2.0 by Example (non-normative OMG document)
This order fulfillment process starts after receiving an order message and continues to check whether the ordered article is available or not. An available article is shipped to the customer followed by a financial settlement, which is a collapsed sub-process in this diagram. In case that an article is not available, it has to be procured by calling the procurement sub-process. Please note that the shape of this collapsed sub-process is thickly bordered which means that it is a call activity. It is like a wrapper for a globally defined task or, like in this case, sub-process.
Comments (9)
Leave a Comment
You must be logged in to post a comment.
Very good template. It’s a good point to start my journey into BPM. Thanks to the contributor, I hope to be useful to the community.
Ked
Hello Ked,
Thank you, glad you found it useful!
Best regards.
I am new using BPMN as well. I don´t understand how does the sequence flow after ¨procurement¨ sub-process make the article ship-able.
Hi Denada,
Procurement is a sub-process, and at this point we don’t know the detail of it. However, it will be a process to refill inventory when an article is no longer available within the store. There is 2 intermediate events attached to the sub-process :
– an error intermediate event when the procurement sub-process get that this article is undeliverable. The process will then inform customer and remove the article from the catalogue.
– A escalation intermediate event will let the customer know that it will take longer than anticipated to get his article, but without cancelling the procurement.
After procurement sub-process is done, the is a link in the top-right corner of “Procurement” to get to “Ship Article”, when the article will then be shipped.
Regards,
JP
Good day. Question about naming: I suppose that tasks “Inform customer” and “Remove article from Catalogue” are independent. So, they can be either paralleled or go in reverse order. So, does that mean that the End Event “Article removed” can be renamed as “Customer Informed and Article Removed” ? Or it goes against recommended naming convention?
Hi Maxim,
Usually, we try to keep the End Event name as short and descriptive as possible. But to be complete, your suggestion of “Customer Informed and Article Removed” would do the trick!
Coun you confirm that I read the following case correctly:
If the article is not available and it will have a late delivery the customer is informed and then the flow ends. E.g. the customer will not get the article in this flow.
I just checked the documentation https://www.omg.org/cgi-bin/doc?dtc/10-06-02.pdf where the same example is explained. There the sub process ‘late delivery’ is a non-interrupting event. That makes more sense imo.
Anybody have a Process Requirement Gathering Document for BPMN purpose?