# A Framework to Model Bursty Electronic Data Interchange Messages for Queueing Systems +
## 3 Results
### Queueing Problems  
From an enterprise dataset, we were able to study the different problems documented in the queue ticketing system. Table 19 shows several categories of issues observed within a period of a queueing system's operation. We observe from the table that 27% of the problems are \"Unclassified\". \"Communication Channel\" related issues are the second biggest hitter at 11% and \"Performance\" is the lowest at 2%. In this context, the \"Communication Channel\" is a link between the client and server systems or between two servers. Interestingly 7% of the problems relate to \"Queue Managers\". To determine the extent to which messages are re-processed, we used two message attributes to investigate this. Using the \"Company ID\" and the \"Message ID\", we determined how many distinct messages were re-processed. A message is re-processed by the system if the message processing time exceeds 20 min. In this case, the message processing is killed, and the message is re-sent into the system. Of just over 1 million (1,237,370) messages, we uncovered that only a small minority of messages were re-processed. Table 20 shows the results of our analysis. We note from the table that one message was re-processed 51 times, and most messages are only re-processed once. When EDI messages traverse through different features of a supply chain network, they go through various transformations. A feature of EDI is a functional acknowledgement (FA). An FA sends back a status message, which serves as an electronic receipt to confirm the delivery of a message. It is sent as a response to other EDI messages received [34]. We sought to investigate which types of status messages are most prevalent. This would allow us to, for example, establish the frequency of malformed messages. Table 21 gives a breakdown of the results. Interestingly, most of these messages do not suffer from malformation during the EDI process, with only 0.12 percent of messages having a return acknowledgement receipt of \"Rejected\" and 0.20 percent of messages being \"Accepted with Errors\". \begin{table}
\begin{tabular}{c c} \hline
**Reprocessed Times** & **Messages** \\ \hline
1 & 281 \\
2 & 6 \\
11 & 1 \\
51 & 1 \\ \hline \end{tabular}
\end{table} 
Table 20: Re-processed messages. \begin{table}
\begin{tabular}{c c c} \hline
**Type** & **Count** & **Percent** \\ \hline Undlassified & 1900 & 27 \\ Communication Channels & 806 & 11 \\ Installation & 620 & 9 \\ Security & 619 & 9 \\ Transport Layer Security & 566 & 8 \\ Queue Managers & 477 & 7 \\ Authorized Program Analysis & 458 & 6 \\ Records (APARs) & Migration & 431 & 6 \\ Product Documentation & 334 & 5 \\ Replicated Data Queue Manager & 256 & 4 \\ (RDQM) & 234 & 3 \\ Logging, Recovery & 177 & 3 \\ Connectivity & 171 & 2 \\ Performance & \multicolumn{1}{c}{} & \\ \end{tabular}
\end{table} 
Table 19: Queueing system problems. Table 22 allows us to investigate the status message and the associated types of EDI transformations. We can use this to ascertain if certain transformations are more susceptible to errors than others. Messages of the type \"Rejected\" and \"Accepted with Errors\" perform the same transformation. The transformation identified is a \"DeEnvelope\" service. The \"DeEnvelope\" service identifies the interchange type contained within a message and extracts them to separate messages handled by the business process. A list of the interchanges can be found here [35]. We observe that only a subset of messages returns an acknowledgement receipt. DevOps informed us that only messages classified as outbound from the \"Direction\" attribute of a message will return an acknowledgement status. We note that most message transformations have a status of accepted whilst applying the DeEnvelope service. Interestingly, no other types of messages transformations have an \"accepted\" status. All other types of message transformation do showcase multiple types of statuses, most of them being either \"Waiting\" or \"None\".