developerWorks⑧ ibm. com/developerWorks Implications for business process monitoring. In Business Modeler you can define business measures and key performance indicators(KPIs) that are specific to a particular process. A Web Sphere Business Monitor model may be generated from each Business Modeler process. With many decoupled process models forming part of a larger(parent) process, it is no longer possible to generate a single monitor model for the arent process and all its process components this is by no means a bad thing. In the same way that we now have decoupled business models and, as a by-product, a much more modular approach o or processes, we also end up with corresponding"decoupled " monit monitoring The attentive reader will at this point be thinking that this will work well if the intent is to monitor each process component independently It will not work so well if we wish to monitor the end-to-end process- for example, if we wish to establish metrics that cover the complete life span of an order. The solution is to use an approach that has already been proposed as a best practice for the creation of monitor models. The approach consists of the separation of monitor models into two separate monitoring levels: high-level monitor model and low-level monitor model. Low-level monitor models receive events from the running processes and in turn propagate (appropriate) events to the high-level monitor model. The original intent of this approach was to establish a certain degree of insulation between the running process and the higher-level monitoring artifacts, such as KPIs and business but in this case we have many low-level monitor models contributing events too% measures With decoupled component processes you can use the same approach single high-level monitor model that oversees the whole process(Figure 6) Figure 6. Low-level models contribute to a high-level model for end-to-end monitoring High level monitor mode Event Event Event Low level monitor Low level monitor Low level monitor model 1 model 2 model n Events Events Events Process 1 Process 2 Process n Business Modeler can already generate high-and low-level monitor models, but the Model business processes for flexibility and re-use: A component-oriented approach Page 8 of 11 Copyright IBM Corporation 2009. All rights reserved• Implications for business process monitoring. In Business Modeler you can define business measures and key performance indicators (KPIs) that are specific to a particular process. A WebSphere Business Monitor model may be generated from each Business Modeler process. With many decoupled process models forming part of a larger (parent) process, it is no longer possible to generate a single monitor model for the parent process and all its process components. This is by no means a bad thing. In the same way that we now have decoupled business processes, we also end up with corresponding “decoupled” monitor models and, as a by-product, a much more modular approach to monitoring. The attentive reader will at this point be thinking that this will work well if the intent is to monitor each process component independently. It will not work so well if we wish to monitor the end-to-end process — for example, if we wish to establish metrics that cover the complete life span of an order. The solution is to use an approach that has already been proposed as a best practice for the creation of monitor models. The approach consists of the separation of monitor models into two separate monitoring levels: high-level monitor model and low-level monitor model. Low-level monitor models receive events from the running processes and in turn propagate (appropriate) events to the high-level monitor model. The original intent of this approach was to establish a certain degree of insulation between the running process and the higher-level monitoring artifacts, such as KPIs and business measures. With decoupled component processes you can use the same approach but in this case we have many low-level monitor models contributing events to a single high-level monitor model that oversees the whole process (Figure 6). Figure 6. Low-level models contribute to a high-level model for end-to-end monitoring Business Modeler can already generate high- and low-level monitor models, but the developerWorks® ibm.com/developerWorks Model business processes for flexibility and re-use: A component-oriented approach Page 8 of 11 © Copyright IBM Corporation 2009. All rights reserved