Practical process patterns: DIP

Decompose Into Patterns (DIP)

A friend of mine asked me to have a look at his first try of business process modelling in BPMN. The modelled process is well-known – “gestion de sinistres” or “claim processing”.

An apartment owner/leaseholder, who got an accident, inform the property managing company (régie), they call a repair service and validate the repair cost with the insurance company. Then the managing company control the work by the repair service and ask the insurance company about to reimburse the cost. The latter transfer the money to the former to pay the invoice.

The following picture is an attempt to model this process.

This diagram does not show the structure of the process thus not easy to understand. Actually, there are four big steps in this process:

1. Submission a claim to the managing company
2. Selection of the acceptable repair service by the managing company
3. Repair and control of repair
4. Submission the invoice from the managing company to insurance company and further payment

For all of those steps there is a proper practical process pattern to follow on.

1. Submission interface (SI) – http://www.slideshare.net/samarin/process-practical-patterns-si
2. Proposal, Action, Reaction (PAR) – see my book
3. Initial Process Skeleton (IPS) – see my book
4. Submission interface (SI) – http://www.slideshare.net/samarin/process-practical-patterns-si

So, decompose your process and try to apply practical process patterns. Maybe not exactly – slightly modified to a particular use.

Thanks,
AS