## 4 Results
### Some KPIs to Measure Smart Gate Efficiency
\begin{table}
\begin{tabular}{p{113.8 pt} p{113.8 pt}} \hline \hline
**KPI** & **Explanation** \\ \hline
**No. of services not performed (due to inefficiency or unavailability of the terminal operator)** & This KPI refers to the number of services that were scheduled but not performed as planned. This can happen due to various factors, such as vehicle breakdowns, delays, scheduling errors, lack of necessary documentation, lack or mismanagement of resources within the terminal, or other operational problems. This indicator is important because non-performed services can lead to delays in the supply chain, customer dissatisfaction, and operational inefficiencies. \\ \hline
**Average time inside the terminal (time from entering the terminal to leaving)** & This measures the average time vehicles spend inside the terminal from the moment they enter until the moment they leave. This time includes processes such as waiting, loading and unloading goods, documentation, and other administrative procedures. A low average time usually indicates an efficient flow and well-managed operations, while a high average time can indicate congestion, inefficient processes, or problems with loading/unloading operations. This KPI is crucial for understanding how to optimize operations and improve the terminal’s overall productivity. \\ \hline
**No. of appointments vs. No. of no appointments** & This measures the percentage of vehicles that arrive on time according to their appointment versus those that arrive without an appointment. This can help users to understand the effectiveness of training in using the scheduling system. \\ \hline
**Canopy read error rate 1** & This quantifies the failure rate when reading data from the truck/container/galley, which may indicate the need for maintenance or updating of the system. \\ \hline
**Average time between passing checkpoint 1 and gate IN** & This evaluates the average time a truck takes from checkpoint 1 to gate IN, which can help identify bottlenecks and efficiency. \\ \hline
**Percentage of trucks diverted to checkpoint 3** & This calculates the percentage of trucks that are diverted to checkpoint 3, which may indicate problems with pre-validation or the scheduling system. Subsequent identification of the situation that led the vehicle to checkpoint 3 (causes—software, hardware, scheduling, etc.). \\ \hline
**Time to resolve contingencies in checkpoint 3** & This measures the time needed to resolve problems that make it impossible for the driver to enter the terminal. \\ \hline
**Customer/driver satisfaction** & This evaluates the level of satisfaction of drivers with the terminal entry process using surveys or feedback. \\ \hline
**Manual intervention rate** & This accounts for the frequency with which manual intervention is required due to faults in the automated system. \\ \hline
**Peak capacity vs. effective utilization** & This compares the maximum number of trucks the terminal can process in a period with the actual number of trucks processed. \\ \hline
**Intermodal terminal throughput (volume)** & This measures the number of cargo units (containers) that pass through the entry/exit gate per unit of time. \\ \hline
**No. of system response failures (TOS, GOS, GAS, others)** & The aim is to quantify the number of failures in information systems for a year and to categorize these failures based on their specific causes (e.g., hardware failures, software errors, network problems, human failures, security issues, etc). \\ \hline
**Others** & Who went out onto the public highway, what controls they went through, and how long they spent inside from checkpoint 1 to checkpoint 4; trying to identify the cause of their exit (at the limit they were validated and decided to leave...). \\ \hline \hline \end{tabular}
\end{table} 
Table 4: KPI measures. After detailing the processes and improvements expected with the implementation of the smart gate system, Table 5 shows a comparison between the AS-IS (current) and TO-BE (proposed) states.