Practical process pattern: SAAP

Servicing As A Process (SAAP) pattern was observed in “implied” business processes (http://improving-bpm-systems.blogspot.com/2012/07/practical-process-pattern-mimo.html). It is implied that an organisation-unit-oriented (or functional) process is invoked from a bigger (almost end-to-end) process. Actually, the former is invoked to serve client’s requests and servicing of different request may overlap in time. Thus, each service invocation should be a separate instance (see the diagram below).
So, there are elements of a mass service system – an input flow of requests for service has to be served in accordance with a potential SLA and by a limited number of servicing slots. (Like a barber shop.)

In the diagram above, the several coordination techniques (http://improving-bpm-systems.blogspot.com/2012/07/coordination-techniques-in-bpm-social.html) were used, namely: template-based, event-based, instance-based, and information-based (to manage the number of available slots – in an implicit way).


No comments: