# A Data-Driven Approach to Discovering Process Choreography
## 5 Experimentation  
### Inter-Organizational Event Logs  
The proposed approach was evaluated using the event logs of 4 real-life scenarios and 2 artificial scenarios of IOBPs. Table 2 summarizes the characteristics of each event log corresponding to the scenarios used in our experimentation. 1. **Air quality system**. This scenario was derived from an autonomous air quality monitoring system based on IoT technology. The collaborative process includes the interaction between 3 participants; consult the description at [46] for more details. The first participant, the _IoT Air quality monitor_, includes activities regarding the validation of the monitoring system's sensors, requests for access to the system, and assigning a valid network address for the monitoring system. Furthermore, it manages all activities for data census through sensors, validation, and sending of air pollution data and meteorological factors through a web service and system shutdown information. The second participant, the _System Access Service_, manages system access requests (accepted and rejected), assigns network addresses for the operation to the IoT air quality monitoring system, and registers active clients. This participant establishes communication with each instance of the _IoT Air quality monitor_ participant. The third participant's _Repository Management Service_ manages each request for data storage in a database located in a cloud service. It also manages the validation activities of the data sent by the participant _IoT Air quality monitor_ (with acceptance or rejection options) and inserts these data into the database. 2. **Healthcare**. This scenario is made up of the activities of 4 participants (_Patient_, _Gyneologist_, _Laboratory_, and _Hospital_) involved in an IOBP within a healthcare scenario (e-healthcare) [31]. The process begins when the _Patient_ participant provides information regarding her health status and waits for a response about her treatment or, if applicable, a request for hospitalization. The participant _Gyneologist_ coordinates laboratory blood studies and hospitalization activities with the participant _Laboratoryand the participant _Hospital_. The collaboration begins when a _Patient_ sends information about her illness to the _Synecologist_. The _Synecologist_ examines the _Patient_ and, in parallel, takes blood samples from the _Patient_ and sends them to the _Laboratory_ for analysis. The _Laboratory_ studies the blood samples, generating a report with the study results for the participant _Synecologist_. Subsequently, the _Gynecologist_ decides whether the _Patient_ should be prescribed medicine or needs hospitalization, informing the _Patient_. When hospitalization is required, the _Synecologist_ communicates with the hospital to request the patient's admission and sends the clinical analysis results. When the _Hospital_ begins its process, the patient's clinical history is created. Then, it decides whether to consider the blood test results sent by the _Synecologist_ or request a new analysis; in either case, the login information is sent to the _Patient_. 3. **Travel Agency**. This collaborative process involves the participants _Customer_ and _Travel Agency_[31]. The process begins with the _Travel Agency_ proposing a travel offer to the _Customer_. The _Customer_ reviews the offer and can request a reservation for the trip. Next, the negotiation is executed to confirm the reservation, the payment of the services, and the generation of a reservation confirmation by the _Travel Agency_. Finally, the _Travel Agency_ confirms the reservation number to the _Customer_ and sends the electronic tickets. 4. **Purchase order**. The event log contains instances of the execution of the purchase order management process from 2017 to 2018 involving two organizations in the telecommunications industry [47]. The organization _M-Repair_ plays the role of customer, and the organization _M-Parts_ plays the role of the supplier of electronic components.