Basic Architecture

AMoCoS is motivated by the idea of assembling information from distributed sources for analysis purposes. In a business-to-business process scenario, for example, the trading partner do not have control over the processes of the other party, and the information shared between the parties may be limited. Nevertheless, business activity monitoring (BAM) applications should provide a holistic view of the entire process. Therefore, the external process structure needs to be mirrored inside the BAM application. In the AMoCoS architecture, an Observer listens to events that a data source publishes on a bus (publish/subscribe mechanism). The observer stores this information in a persistent audit trail. A BAM user can then query the observer about the current status of the source, without having to query information sources outside his or her own domain.

Figure 1: Basic Architecture

In case contact with the source is lost (for example, due to a breakdown of the communication infrastructure), the observer is able to use a replication of the source's plan (e. g. the workflow model) to reason about the current state of the source (i. e., what is happening at the remote site), or the extrapolated state after a given period of time (i. e., the most likely next step).

Figure 2: Architecture in the event of disrupted communication

[Back to the Project Description]