Approaches

Identify significant IDs

In order to detect each visitor’s communication situation, I calculated the number of messages which each ID received or sent a day. Then built a bar chart to show those numbers. As the following figures shown, there are three significant IDs which had extreme large volumes: 839736, 1278894. Compare the above graph with the below graph, I noticed that nearly 85% visitors received messages from 839736. In addition, ID 839736 and 1278894 both sent messages only from the entry corridor. On basis of these findings, I can identify these two IDs are service ID and belongs to the theme park.

ID 839736

I filtered ID 839736 to observe its time series in three days. I noticed that at 9 a.m. to 10 p.m. ID 839736 continued to connect with visitors and the number of messages was slightly different in Friday and Saturday. However, the number become very weird which was significant increased at around 1400 at 12 p.m. and around 250-350 at 3 p.m. to 4 p.m. Why service ID sent and recieved such large amount of messages? I assumed there may was a terrible accident happened at Sunday afternoon.

ID 1278894

Like the method of observation of ID 839736, I built three bar charts of the number of messages by ID 1278894 in three days. We can find an interesting thing that ID 1278894 sent a large number of messages to visitors every 5-minutes interval in an hour and rested next one hour but then it would continue to send messages with 5-minutes interval. This ID did the loop from 12 p.m. to 9 p.m. each day. In addition, ID 1278894 didn’t like ID 839736 that had a significant peak in Sunday. So in my opinion, though both ID 839736 and 1278894 are park service IDs, they have different functions and send different messages. ID 839736 is more like a help ID, and ID 1278894 is more like a real-time information update service ID.