a particular application in this subsystem activities 1660 can be derived directly from events each event 1650 has an occurrence time and an activity 1660 occurs between two events thus an activity 1660 has a start time a stop time and a duration derived from start and stop times the transaction detector 1610 examines sequences of events 1650 to find matches to defined transactions when a match is found the transaction detector 1610 creates a transaction 1670 from the event sequence and stores the transaction 1670 in the adherence database 1630 transaction definitions 1680 are business specific and are created by manager or supervisor through a wfm application not shown transactions 1670 can best be explained by means of an example which follows a particular call center campaign involves taking orders from customers to place a new order an agent interacts with a u201c customer entry u201d screen in the customer relationship manager crm application followed by a u201c product entry u201d screen in the crm other crm screens may be accessed between the u201c customer entry u201d and u201c product entry u201d steps except for the u201c cancel order u201d screen this neworder business transaction can then be defined as in the notation used above the transaction name appears to the left of the equal sign and the event sequence appears to the right of the equal sign in order to match the transaction events must occur in the order they appear in the definition events which are optional appear in brackets in this example the combination of bracket and the not operator means that any event other than the crm_scr_cancelorder event can occur between the crm_scr_custentry event and the crm_scr_prodentry event the transactions 1670 detected by the transaction detector 1610.