<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.3 20210610//EN" "JATS-journalpublishing1-3-mathml3.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ali="http://www.niso.org/schemas/ali/1.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" article-type="research-article" dtd-version="1.3" xml:lang="EN">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">Front. Future Transp.</journal-id>
<journal-title-group>
<journal-title>Frontiers in Future Transportation</journal-title>
<abbrev-journal-title abbrev-type="pubmed">Front. Future Transp.</abbrev-journal-title>
</journal-title-group>
<issn pub-type="epub">2673-5210</issn>
<publisher>
<publisher-name>Frontiers Media S.A.</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">1735788</article-id>
<article-id pub-id-type="doi">10.3389/ffutr.2025.1735788</article-id>
<article-version article-version-type="Version of Record" vocab="NISO-RP-8-2008"/>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Original Research</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Times of ships in container ports: automatic identification system data for analyzing traffic conditions at a maritime terminal</article-title>
<alt-title alt-title-type="left-running-head">Belcore and Polimeni</alt-title>
<alt-title alt-title-type="right-running-head">
<ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3389/ffutr.2025.1735788">10.3389/ffutr.2025.1735788</ext-link>
</alt-title>
</title-group>
<contrib-group>
<contrib contrib-type="author" corresp="yes">
<name>
<surname>Belcore</surname>
<given-names>Orlando Marco</given-names>
</name>
<xref ref-type="aff" rid="aff1"/>
<xref ref-type="corresp" rid="c001">&#x2a;</xref>
<uri xlink:href="https://loop.frontiersin.org/people/2839769"/>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Methodology" vocab-term-identifier="https://credit.niso.org/contributor-roles/methodology/">Methodology</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Investigation" vocab-term-identifier="https://credit.niso.org/contributor-roles/investigation/">Investigation</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Software" vocab-term-identifier="https://credit.niso.org/contributor-roles/software/">Software</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Data curation" vocab-term-identifier="https://credit.niso.org/contributor-roles/data-curation/">Data curation</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Conceptualization" vocab-term-identifier="https://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Writing &#x2013; original draft" vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-original-draft/">Writing - original draft</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Formal analysis" vocab-term-identifier="https://credit.niso.org/contributor-roles/formal-analysis/">Formal Analysis</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Writing &#x2013; review &#x26; editing" vocab-term-identifier="https://credit.niso.org/contributor-roles/Writing - review &#x26; editing/">Writing - review and editing</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Visualization" vocab-term-identifier="https://credit.niso.org/contributor-roles/visualization/">Visualization</role>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Polimeni</surname>
<given-names>Antonio</given-names>
</name>
<xref ref-type="aff" rid="aff1"/>
<uri xlink:href="https://loop.frontiersin.org/people/1571255"/>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Visualization" vocab-term-identifier="https://credit.niso.org/contributor-roles/visualization/">Visualization</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Conceptualization" vocab-term-identifier="https://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Validation" vocab-term-identifier="https://credit.niso.org/contributor-roles/validation/">Validation</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Project administration" vocab-term-identifier="https://credit.niso.org/contributor-roles/project-administration/">Project administration</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Funding acquisition" vocab-term-identifier="https://credit.niso.org/contributor-roles/funding-acquisition/">Funding acquisition</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Methodology" vocab-term-identifier="https://credit.niso.org/contributor-roles/methodology/">Methodology</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Supervision" vocab-term-identifier="https://credit.niso.org/contributor-roles/supervision/">Supervision</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Writing &#x2013; review &#x26; editing" vocab-term-identifier="https://credit.niso.org/contributor-roles/Writing - review &#x26; editing/">Writing - review and editing</role>
</contrib>
</contrib-group>
<aff id="aff1">
<institution>Department of Engineering, University of Messina</institution>, <city>Messina</city>, <country country="IT">Italy</country>
</aff>
<author-notes>
<corresp id="c001">
<label>&#x2a;</label>Correspondence: Orlando Marco Belcore, <email xlink:href="mailto:obelcore@unime.it">obelcore@unime.it</email>
</corresp>
</author-notes>
<pub-date publication-format="electronic" date-type="pub" iso-8601-date="2026-01-05">
<day>05</day>
<month>01</month>
<year>2026</year>
</pub-date>
<pub-date publication-format="electronic" date-type="collection">
<year>2025</year>
</pub-date>
<volume>6</volume>
<elocation-id>1735788</elocation-id>
<history>
<date date-type="received">
<day>30</day>
<month>10</month>
<year>2025</year>
</date>
<date date-type="rev-recd">
<day>04</day>
<month>12</month>
<year>2025</year>
</date>
<date date-type="accepted">
<day>08</day>
<month>12</month>
<year>2025</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright &#xa9; 2026 Belcore and Polimeni.</copyright-statement>
<copyright-year>2026</copyright-year>
<copyright-holder>Belcore and Polimeni</copyright-holder>
<license>
<ali:license_ref start_date="2026-01-05">https://creativecommons.org/licenses/by/4.0/</ali:license_ref>
<license-p>This is an open-access article distributed under the terms of the <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution License (CC BY)</ext-link>. The use, distribution or reproduction in other forums is permitted, provided the original author(s) and the copyright owner(s) are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.</license-p>
</license>
</permissions>
<abstract>
<p>Maritime shipping is the primary means connecting countries and global economies, with ports serving as critical logistics hubs in the supply chain. In recent decades, international conflicts and economic disruptions have increasingly stressed maritime transport, highlighting the need to focus more on terminal performance. This paper presents a methodology to evaluate port traffic conditions using data from open Automatic Identification System (AIS) repositories. A rule-based approach is applied to segment the vessel trajectories into underway, anchoring, and berth operations, allowing the assessment of all stages that characterize a port call and the calculation of the vessel turnaround time. The methodology is demonstrated in the Port of Los Angeles, the busiest container hub on the United States West Coast. Historical AIS data are analyzed to obtain traffic conditions, and a set of key performance indicators is computed to quantify terminal operations and docks utilization during the observation period. The proposed framework provides a scalable tool for maritime traffic monitoring and decision support in port management.</p>
</abstract>
<kwd-group>
<kwd>AIS data</kwd>
<kwd>container shipping</kwd>
<kwd>maritime transport</kwd>
<kwd>port congestion measures</kwd>
<kwd>port efficiency</kwd>
<kwd>rule-based approach</kwd>
<kwd>spatial-temporal analysis</kwd>
<kwd>vessel turnaround time</kwd>
</kwd-group>
<funding-group>
<funding-statement>The author(s) declared that financial support was received for this work and/or its publication. This study is carried out within the research project &#x201c;National and local factors affecting times of ships in container ports&#x201d;, Piano Nazionale di Ripresa e Resilienza (PNRR), Next Generation EU. Progetti di Rilevante Interesse Nazionale PRIN_2022_PNRR_P202292YFW. CUP: C53D2300878001. This piece of work reflects only the authors&#x2019; views and opinions, neither the European Union nor the European Commission can be considered responsible for them.</funding-statement>
</funding-group>
<counts>
<fig-count count="13"/>
<table-count count="4"/>
<equation-count count="5"/>
<ref-count count="63"/>
<page-count count="16"/>
</counts>
<custom-meta-group>
<custom-meta>
<meta-name>section-at-acceptance</meta-name>
<meta-value>Freight Transport and Logistics</meta-value>
</custom-meta>
</custom-meta-group>
</article-meta>
</front>
<body>
<sec sec-type="intro" id="s1">
<label>1</label>
<title>Introduction</title>
<p>Maritime transport is crucial in global trade, and the number of vessels at sea is growing. The United Nations Conference on Trade and Development (UNCATD) reports that more than 80% of global trade is provided by maritime shipping (<xref ref-type="bibr" rid="B53">United Nations Conference on Trade and Development, 2024</xref>). Therefore, ports represent critical nodes in the supply chain. Container shipping activities are sensitive to external stress, and in recent years there have been many unexpected disruptions, such as the COVID-19 and war frictions that affected global trade. Given its crucial role, the maritime transport network is required to improve reliability, thus increasing the efficiency of the supply chain. In the context of the container shipping network, as evidenced by <xref ref-type="bibr" rid="B60">Yue and Mangan (2023)</xref>, at least three cornerstones such as infrastructure, network configuration, and connectivity may be taken into account when developing a more resilient and reliable container shipping network. In this field, new generation ICT and five generation ports play a decisive role in increasing terminal performance (<xref ref-type="bibr" rid="B44">Russo and Musolino, 2021</xref>; <xref ref-type="bibr" rid="B45">Russo and Musolino, 2022</xref>). As stated by <xref ref-type="bibr" rid="B22">Kishore et al. (2024)</xref> the most recent developments demonstrate a growing interest in AIS application, with the topic shifting from a niche theme to one of relevance. The use of AIS data plays a central role in analyzing port performance, thus representing a valuable instrument to compare results achieved at port level (<xref ref-type="bibr" rid="B31">Musolino et al., 2026a</xref>). Specifically, the possibility to directly extract maritime routes from AIS increases the knowledge of the shipping network and changes related to emerging crisis or new trends (<xref ref-type="bibr" rid="B35">Notteboom et al., 2024</xref>; <xref ref-type="bibr" rid="B43">Rindone, 2024</xref>). To this end, in a global market where liberalization and technologies are driving factors for economic development, undertaking a digitalization process with align to the 4.0 industry is becoming a driving strategy (<xref ref-type="bibr" rid="B5">Belmoukari et al., 2023</xref>). Several port authorities are investing in renewing their infrastructures under the paradigm of the communication technology (<xref ref-type="bibr" rid="B16">Heilig and Vo&#xdf;, 2017</xref>), in the view of a &#x201c;smart port&#x201d; (<xref ref-type="bibr" rid="B30">Molavi et al., 2020</xref>; <xref ref-type="bibr" rid="B41">Rajabi et al., 2018</xref>; <xref ref-type="bibr" rid="B49">Shuo et al., 2016</xref>), whose targets may consist of sustainability, stakeholders collaboration, effective management and operation efficiency (<xref ref-type="bibr" rid="B36">Odeck and Sch&#xf8;yen, 2020</xref>; <xref ref-type="bibr" rid="B51">Song et al., 2024</xref>).</p>
<p>The process towards digitalization also requires the ability to monitor and assess terminal conditions to achieve sustainable goals when managing the infrastructure (<xref ref-type="bibr" rid="B37">Peng et al., 2018</xref>). By this way, vessel route information represents a valuable source when performing analyses. Shipping traceability and reconstruction of vessel operations represent a challenging task. Since 2005, the International Maritime Organization (IMO) has been established to introduce devices on board for all passengers and cargo vessels as prescribed within the Safety of Life as Sea (SOLAS) agreement. AIS data include both static information on vessels (MMSI, Vessel Name, Ship type, cargo, length, width, GT, DWT), and kinematic information (latitude, longitude, SOG, COG, heading) and come from the family of spatial-temporal information set. AIS have become a well-recognized instruments when conducting analyses that range from safety and security, to environmental issues as well as on port operation and terminals development (<xref ref-type="bibr" rid="B47">Russo et al., 2024</xref>). For such a reason, AIS data processing became a valuable source in enhancing provisional models and management operations at the maritime terminal (<xref ref-type="bibr" rid="B8">Chen et al., 2023</xref>; <xref ref-type="bibr" rid="B63">Ziran, 2024</xref>). However, extracting information from AIS signals require handling a large amount of noisy data, whose quality may be affected by human errors and lack of coverage (<xref ref-type="bibr" rid="B13">Eljabu and Etemad, 2023</xref>; <xref ref-type="bibr" rid="B42">Ribeiro et al., 2023</xref>). In fact, raw data usually needs to be preprocessed and cleaned before undertaking traffic analysis and several authors approached the problem of developing an affordable structure to manage AIS (<xref ref-type="bibr" rid="B52">Spadon et al., 2024</xref>). For such reasons, this paper focused i) on proposing a generalized operation tool capable of extracting events from raw AIS database, and ii) on the possibility of using open data for analyzing the phases that characterize a port call, also pointing out the contribution of each operation within the vessel turnaround time. The output consists of the identification of traffic conditions for both docks and anchorage areas, outlining the most critical phases of a generic port call (anchorage and mooring). A set of key statistical performance indicators is derived as a discriminator against terminal performance.</p>
<p>Thus, the paper addresses the valuable opportunities offered by the widespread presence of AIS data that can assist both analysts and planners in.<list list-type="bullet">
<list-item>
<p>Proposing a generalized procedure to extract vessel operations (<xref ref-type="sec" rid="s3-2">Section 3.2</xref>);</p>
</list-item>
<list-item>
<p>Introducing a set of indicators to represent the berth occupation and assessing dwell time operations directly from open data (<xref ref-type="sec" rid="s3-3">Section 3.3</xref>);</p>
</list-item>
<list-item>
<p>Quantifying annual traffic and port calls distributions utilizing AIS data (<xref ref-type="sec" rid="s4-3">Sections 4.3</xref> and <xref ref-type="sec" rid="s4-4">4.4</xref>);</p>
</list-item>
<list-item>
<p>Exploring the potential connected with AIS data in analyzing terminal activities (<xref ref-type="sec" rid="s4-5">Section 4.5</xref> and <xref ref-type="sec" rid="s4-6">4.6</xref>);</p>
</list-item>
<list-item>
<p>Describing the main stages that characterize a generic port call, thus achieving an evaluation of the vessel turnaround time (<xref ref-type="sec" rid="s4-6">Section 4.6</xref>).</p>
</list-item>
</list>
</p>
<p>The structure of the paper resumed as follows. After the introduction (<xref ref-type="sec" rid="s1">Section 1</xref>), Section two focuses on the emerging evidence from literature and the role of AIS data. Section three reports on the methodology as a basis of the proposed analysis tool. Section four resumes the output, and the key performance indicators developed. Following (Section five) discussion on results, and conclusion characterize the closing paragraphs.</p>
</sec>
<sec id="s2">
<label>2</label>
<title>Literature review</title>
<p>Data from AIS are used to identify and analyze various elements related to maritime transport, from risk analysis and emission assessment to route estimation and port performance (just to cite a few). Several authors approached the use of AIS by merging the signals from onboard devices with another source to test the devices&#x2019; accuracy. As stated by <xref ref-type="bibr" rid="B55">Wolsing et al. (2022)</xref>, who reviewed the most relevant approaches, the anomaly detection was among the first task underpinned mainly focusing on tracking deviation and missing data anomalies. As an example, <xref ref-type="bibr" rid="B33">Nguyen et al. (2015)</xref> and <xref ref-type="bibr" rid="B19">Jankowski et al. (2021)</xref> compared the accuracy of AIS signals with radar tracks from ground instruments to assess data quality and evaluate how to fix the information. In contrast, <xref ref-type="bibr" rid="B20">Jones et al. (2023)</xref> proposed a data mining process to merge information from AIS data and satellite imagery (synthetic aperture radar, SAR) to detect vessel behavior and navigation stages.</p>
<p>Over the years, as data became more widely available, several scholars have focused on route extraction as the primary approach to investigating maritime traffic. Trajectory-based methods consist of extracting information over travel and let the opportunity to observe vessel routes as spatial-temporal curves whose sub-trajectories qualify specific ship behaviors (<xref ref-type="bibr" rid="B15">Gao et al., 2021</xref>; <xref ref-type="bibr" rid="B58">Yan et al., 2020</xref>). Trajectory segmentation, in general, represents a valuable technique when dealing with AIS data, and feature extraction may assist analysts in detecting meaningful indicators of port congestion and performance (<xref ref-type="bibr" rid="B18">Huang et al., 2024</xref>; <xref ref-type="bibr" rid="B54">Wijaya and Nakamura, 2024</xref>). Data management and analysis of AIS signals require a great effort (<xref ref-type="bibr" rid="B61">Zhang et al., 2018</xref>) for this reason, several approaches have been developed to focus on specific problems that range from safety and security in navigation to traffic evolution in an area. For example, <xref ref-type="bibr" rid="B62">Zhang et al. (2019)</xref> employed AIS data to analyze ship traffic demand and utilized an analytical approach to analyze spatial temporal dynamics at the Singapore port. Vessel traffic analyzes are conducted starting from origin-destination trajectories. Port management strategies, centered on traffic safety, are evaluated by linking traffic conditions with a historical dataset of collisions. On the contrary, <xref ref-type="bibr" rid="B59">Yan et al. (2022)</xref> analyzed historical AIS data extracted from several vessels along the South Sea Silk Road to identify their destination. The paper proposes a random forest approach to classify the vessel stops, to identify the trajectories and to analyze spatial-temporal distribution of AIS signals. Similarly, <xref ref-type="bibr" rid="B27">Lee et al. (2022)</xref> analyzed the most crowded channels and main routes for different classes of vessels and mapped the trajectory through a statistical analysis. It proposed a workflow that relies on data cleaning and clustering, then trajectories are processed, and waypoints are aggregated through a density-based clustering approach. Finally, the shipping network is completed by connecting the waypoints.</p>
<p>AIS data also emerged as a valuable source when interpreting phenomena that occurred in the terminal area: <xref ref-type="bibr" rid="B14">Feng et al. (2020)</xref> employed AIS signals in analyzing the vessel turnaround time for different classes of vessels and informing over the navigation status. <xref ref-type="bibr" rid="B1">AbuAlhaol et al. (2018)</xref> used AIS data to predict congestion indexes in both anchorage and berth areas. <xref ref-type="bibr" rid="B21">Kim et al. (2023)</xref> analyzed traffic conditions in coastal waters of Korea to verify vessel navigation security. Therefore, traffic conditions and seasonality for different Korean sea areas were analyzed to assess a vessel traffic index (VTI) as a descriptive measure. <xref ref-type="bibr" rid="B26">Kweon et al. (2022)</xref> analyzed operations in the Port of Ulsan between 2016 and 2019 by collecting data on vessel traffic, berth allocation and weather conditions, focusing on the development of strategies for managing demurrage rate and on the definition of policies aimed at reducing terminal congestion. Port performance analysis represents a prolific field of study, and several scholars addressed the research using information from AIS (<xref ref-type="bibr" rid="B29">Meng et al., 2023</xref>). Several procedures formulated in the literature can be framed within the perspective of transportation system models, often simulating terminal status through an equilibrium approach (<xref ref-type="bibr" rid="B46">Russo and Musolino, 2024</xref>). As stated by <xref ref-type="bibr" rid="B48">Sahoo and Song (2022)</xref>, big data in the maritime field could be integrated into policy making, thus uncovering the most appropriate strategies for port operators. Conversely, <xref ref-type="bibr" rid="B57">Xu et al. (2024)</xref> starting from AIS data route analysis, tackled the problem from the perspective of shipping companies, highlighting the contribution of each actor to the global container shipping network. Similarly, in <xref ref-type="bibr" rid="B11">Di Gangi et al. (2026)</xref> the shipping network was explored by identifying how operational time may affect container routes. The focus is on the trip of a container moved from the origin to the destination, and the performance is simulated to measure and compare the magnitude of travel time, transshipment operations, and handling. Ship arrivals, loading and unloading operations, and port transitions are elements considered relevant in the simulation. <xref ref-type="bibr" rid="B12">Ducruet and Itoh (2022)</xref> utilized historical AIS to investigate route delays and the evolution of vessel turnaround time through the years, by linking it to external factors such as the financial crisis of 2007 and digitalization. The outputs were then analyzed at national and regional level. AIS data were used by <xref ref-type="bibr" rid="B25">Kruse et al. (2018)</xref> to evaluate a freight fluidity index and to assess port congestion conditions, thus estimating the vessel turnaround time. The total port system time and the port cycle time, as well as the channel navigation time (travel time inbound, were used as discriminants for the operation within the port area. As stated by <xref ref-type="bibr" rid="B9">Chu et al. (2024)</xref>, uncertainty over vessel turnaround time and delays on arrival time can affect handling operation and berths efficiency. This recalls a great emphasis on dwell times, and the analyses of AIS data over berth calls may improve the management experience (<xref ref-type="bibr" rid="B50">Smith, 2021</xref>). Several maritime infrastructures were observed by evaluating performance in terms of handled TEUs, and the analyses demonstrated that vessel scheduling may represent a determinant over dwell time and berth efficiency.</p>
<p>
<xref ref-type="bibr" rid="B23">Kolley et al. (2022)</xref> used different machine learning methods to predict vessel arrival time. The accuracy of the forecasts is then analyzed to improve the robustness of the berth scheduling. <xref ref-type="bibr" rid="B38">Peng et al. (2023)</xref> used AIS data to identify anchorage areas through the clustering technique and convex hull method to define the involved operations areas, thus forecasting the traffic congestion using a neural network model. Finally, <xref ref-type="bibr" rid="B56">Xin et al. (2024)</xref> developed a model to reconstruct common vessels patterns using machine learning techniques, to assess navigation status (underway, anchorage, and berth). The messages delivered by onboard devices were at the basis of their work, and both SOG (speed over ground) and COG (course over ground) were used as critical features to interpret the status of the vessel.</p>
<p>The review analysis highlighted the wide variety of approaches used in the interpretation of AIS signals. Clustering approaches, spatio-temporal analysis, and trajectory features extraction are among the most used methods in analyzing AIS data. Similarly, port performance and competition among actors, analyzed using data and route information from AIS, represent a novel field of application, remarking the growing interest in the use of information technologies within the transportation field.</p>
<p>In the following, the paper will focus on maritime terminal berth utilization and vessel turnaround time dimension analyses. Two specific aspects will be highlighted: the feature extractions from AIS signals, and the interpretation of the events detected to assess terminal operations. In this way, the proposed approach addresses some critical issues related to data utilization by defining a generalized methodology able of identifying terminal traffic conditions, leveraging AIS data and publicly available resources.</p>
<p>This study aims to answer the following research questions.<list list-type="bullet">
<list-item>
<p>To what extent can the extraction of features from AIS signals facilitate the identification of events characterizing a port call?</p>
</list-item>
<list-item>
<p>How can these events be interpreted to assess terminal operations and traffic phenomena within the port area?</p>
</list-item>
<list-item>
<p>To what degree does AIS-based feature extraction allow for reliable estimation of vessel turnaround times and the identification of critical phases of a port call?</p>
</list-item>
</list>
</p>
</sec>
<sec sec-type="materials|methods" id="s3">
<label>3</label>
<title>Materials and methods</title>
<p>This section outlines the workflow and its main components. The outline of the methodological framework is discussed. The theoretical model that guides the analysis is then introduced, followed by a detailed overview of the analysis tool to provide context for the forthcoming results. The section concludes with the presentation of performance indicators used to describe the activities of the vessel during a port call.</p>
<sec id="s3-1">
<label>3.1</label>
<title>Vessel turnaround time</title>
<p>The time spent in port for each vessel, <inline-formula id="inf1">
<mml:math id="m1">
<mml:mrow>
<mml:msub>
<mml:mi>T</mml:mi>
<mml:mi>v</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula> can be considered as a function of multiple operational factors and can be summarized as follows:<disp-formula id="e1">
<mml:math id="m2">
<mml:mrow>
<mml:msub>
<mml:mi>T</mml:mi>
<mml:mi>v</mml:mi>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mi>f</mml:mi>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:msub>
<mml:mi>T</mml:mi>
<mml:mi>w</mml:mi>
</mml:msub>
<mml:mtext>&#x2009;</mml:mtext>
<mml:mo>;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mtext>&#x2009;</mml:mtext>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mtext mathvariant="italic">ber</mml:mtext>
</mml:msub>
<mml:mtext>&#x2009;</mml:mtext>
<mml:mo>;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mtext>&#x2009;</mml:mtext>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mtext mathvariant="italic">op</mml:mtext>
</mml:msub>
<mml:mtext>&#x2009;</mml:mtext>
<mml:mo>;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mtext>&#x2009;</mml:mtext>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mtext mathvariant="italic">un</mml:mtext>
</mml:msub>
<mml:mtext>&#x2009;</mml:mtext>
<mml:mo>;</mml:mo>
<mml:msub>
<mml:mi>T</mml:mi>
<mml:mi>l</mml:mi>
</mml:msub>
<mml:mtext>&#x2009;</mml:mtext>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:math>
<label>(1)</label>
</disp-formula>
</p>
<p>In the previous equation, the vessel turnaround time <italic>T</italic>
<sub>
<italic>v</italic>
</sub> is a function of several components.<list list-type="bullet">
<list-item>
<p>
<italic>T</italic>
<sub>
<italic>w</italic>
</sub> is the time spent by a vessel within the anchorage area;</p>
</list-item>
<list-item>
<p>
<italic>T</italic>
<sub>
<italic>ber</italic>
</sub> and <italic>T</italic>
<sub>
<italic>un</italic>
</sub> represent the operative time needed to access the berth (<italic>T</italic>
<sub>
<italic>ber</italic>
</sub>) and the time spent by the vessel to leave the area (<italic>T</italic>
<sub>
<italic>un</italic>
</sub>);</p>
</list-item>
<list-item>
<p>
<italic>T</italic>
<sub>
<italic>op</italic>
</sub> is the dwell time, it includes loading/unloading operations;</p>
</list-item>
<list-item>
<p>
<italic>T</italic>
<sub>
<italic>l</italic>
</sub> is the time to leave the port.</p>
</list-item>
</list>
</p>
<p>
<xref ref-type="fig" rid="F1">Figure 1</xref> reports a qualitative diagram of the components of the turnaround time. During the anchorage, the vessel remains within a fixed area around the anchor point. Berthing implies the travel of the vessel from the anchorage area to the berth, and both the variables time and space change in value. During operations, the vessel is at the berth (changes in time, but not in space). Finally, unberthing and port departure imply a variation in both space and time.</p>
<fig id="F1" position="float">
<label>FIGURE 1</label>
<caption>
<p>Schematic representation of the vessel turnaround time.</p>
</caption>
<graphic xlink:href="ffutr-06-1735788-g001.tif">
<alt-text content-type="machine-generated">Graph illustrating stages of a maritime operation over time: Tw for anchorage, Tber for berthing, Top for operations, Tun for unberthing Tl for leaving. Lines vary in color and slope, indicating space usage at each stage.</alt-text>
</graphic>
</fig>
<p>
<xref ref-type="fig" rid="F1">Figure 1</xref> reports the phases that may characterize a port call, whose events are detected by analyzing AIS signals. The key features of the procedure, introduced in the following paragraphs, are further detailed in <xref ref-type="bibr" rid="B2">Belcore and Polimeni (2025)</xref> where the workflow for the detection and classification of the main stages of a port call was tested. Considering the seaside, the vessel arrives and, in general, waits at anchor (<italic>T</italic>
<sub>
<italic>w</italic>
</sub>) before entering the port (<italic>T</italic>
<sub>
<italic>ber</italic>
</sub>). When a berth is available, the loading/unloading operations start (<italic>T</italic>
<sub>
<italic>op</italic>
</sub>), then the vessel leaves the berth (<italic>T</italic>
<sub>
<italic>un</italic>
</sub>) and the port (<italic>T</italic>
<sub>
<italic>l</italic>
</sub>). Note that there may be situations where the vessel stops at anchor again. Thus, addressing the above-mentioned stages, allows the analyst to evaluate performance indexes and congestion measures for the maritime terminal. In the following sections, the generalized procedure used for processing information related to vessel navigation phases (specifically, for container vessels) within port areas and its boundaries are presented. Unlike the approach adopted in <xref ref-type="bibr" rid="B3">Belcore et al. (2025a)</xref>, which analyzed terminal traffic by considering spatial density and average service time at the berth, this approach advances further by providing a detailed quantification of the phases that characterize the port call. Moreover, the analysis of the identified phenomena enables reconstruction of berth utilization and the quantification of anchoring and maneuvering operations within a port call, providing a set of statistical indicators based on the detected events.</p>
</sec>
<sec id="s3-2">
<label>3.2</label>
<title>AIS toolkit</title>
<p>A flexible and modular framework is designed to process and analyze AIS data for the detection and classification of the main stages of a port call. The architecture is organized into interconnected components that span from raw data acquisition and cleaning, through navigation status segmentation and event classification, to final visualization and reporting over traffic conditions at the terminal area.</p>
<sec id="s3-2-1">
<label>3.2.1</label>
<title>Overview</title>
<p>
<xref ref-type="fig" rid="F2">Figure 2</xref> resumes the architecture of the proposed tool, it comprises five modules.<list list-type="order">
<list-item>
<p>A <italic>data layer</italic> capable of managing data from different repositories;</p>
</list-item>
<list-item>
<p>A <italic>model system</italic> whose pipelines operate on raw data to segment trajectories by differentiating sub-events for a generic vessel route;</p>
</list-item>
<list-item>
<p>A user <italic>interface</italic> helps the analyst in analyzing the process through maps and data sheets;</p>
</list-item>
<list-item>
<p>An <italic>events dataframe</italic> stores the data on the extracted events that are ready to be analyzed;</p>
</list-item>
<list-item>
<p>A <italic>dashboard</italic> summarizes aggregated results, enabling flexible data export and comparative analyses across docks, time frames, or vessel classes.</p>
</list-item>
</list>
</p>
<fig id="F2" position="float">
<label>FIGURE 2</label>
<caption>
<p>A scalable framework for AIS data processing and event detection in port areas.</p>
</caption>
<graphic xlink:href="ffutr-06-1735788-g002.tif">
<alt-text content-type="machine-generated">Flowchart illustrating a data processing system for terminal and vessel data. The data layer involves preprocessing through zoning and cleaning. The model system conducts trajectory analysis with segmentation, classification, and segment mining. The user interface displays analysis results with graphs and maps. The dashboard monitors dock performances and vessel turnaround times. Data management involves organizing events into a dataframe. Arrows indicate data flow between each step.</alt-text>
</graphic>
</fig>
</sec>
<sec id="s3-2-2">
<label>3.2.2</label>
<title>Functional modules</title>
<p>Open AIS data are characterized by a high sampling frequency and may contain anomalies or missing signals. Therefore, preprocessing is crucial to ensure consistency and reliability of the dataset.</p>
<sec id="s3-2-2-1">
<label>3.2.2.1</label>
<title>Data layer (Terminal and vessel data and preprocessing)</title>
<p>This stage includes spatial and temporal filtering, data cleaning, and trajectory validation, providing a robust basis for subsequent analysis. The tool extracts historical AIS records from authoritative online sources; it applies spatial and temporal filters based on a predefined Zone of Interest (ZoI) and cleans the resulting dataset. The filters allow us to optimize data input, speed up computation, and restrict analyses to those signals that fall within the ZoI and the temporal scope. Subsequently, the filtering stage ensures that only significant vessel routes and reliable trajectories are stored, while incomplete or fragmented data are discarded to reduce noise and bias. Pre-processing includes a down-sampling procedure used to purge inconsistent values, thus were confirmed as valid those records where (1) the MMSI string consists of nine characters; (2) headings values ranged between [0&#x2013;360] degrees; (3) 1-min interval sampling was applied to reduce redundancy and mitigate the impact of duplicate or noisy signals. Finally, distance checks are applied between consecutive points, and unrealistic speeds are flagged as noise. This cleaned dataset serves as the foundation for subsequent analyses, including vessel status extraction, operational state classification, and visual reporting.</p>
</sec>
<sec id="s3-2-2-2">
<label>3.2.2.2</label>
<title>Model system (segmentation)</title>
<p>Rule-based methods detect shifts along vessel tracks, distinguishing underway, maneuvering, and stationary phases. Therefore, the kinematic attributes SOG (speed over ground), COG (course over ground) and heading are analyzed to detect changes along the trajectories and perform the classification. The underway phases are typically characterized by higher and stable speeds with limited heading variation, whereas stationary phases present low speeds and irregular heading changes. Therefore, the rule-based segmentation algorithm captures these transitions without requiring supervised learning or clustering, isolating operational blocks within vessel tracks and facilitating downstream classification. As also stated by <xref ref-type="bibr" rid="B54">Wijaya and Nakamura (2024)</xref> and <xref ref-type="bibr" rid="B13">Eljabu and Etemad (2023)</xref>, the rule-based approach represents a robust alternative to the most advanced data-driven methods. This technique ensures rapid convergence and generalizability across different vessel types, although parameter tuning, especially speed thresholds, may impact accuracy (<xref ref-type="bibr" rid="B1">AbuAlhaol et al., 2018</xref>; <xref ref-type="bibr" rid="B58">Yan et al., 2020</xref>).</p>
</sec>
<sec id="s3-2-2-3">
<label>3.2.2.3</label>
<title>Model system (Classification and segment mining)</title>
<p>Each identified event is analyzed to determine its spatial extent and duration. The system aggregates signals over time and matches geospatial information achieved from event segmentation to reveal anchorage stages and mooring operations, enabling both point-in-time analysis and trend tracking over longer periods. Some synthetic geometrical features are used to distinguish anchoring from berthing. Key features include.<list list-type="order">
<list-item>
<p>
<italic>Convex hull area</italic>, as the area occupied by the signals falling within the same event;</p>
</list-item>
<list-item>
<p>
<italic>Mean event radius,</italic> as the ideal radius marked by the signals that fall within the same event;</p>
</list-item>
<list-item>
<p>
<italic>Geohash coverage</italic>, as the number of occupied cells of the geohash grid during an event;</p>
</list-item>
<list-item>
<p>
<italic>Point density per square meter</italic>, that refers to how signals are distributed during an event.</p>
</list-item>
</list>
</p>
<p>To further improve accuracy, the framework integrates external geospatial sources: (i) reverse geocoding of event centroids (it lets verify the position of a vessel within an area, and it highlights unexpected behaviors by crossing navigation status with the geographic area); (ii) the overlap with official berth and anchorage boundaries. These enrichments improve classification reliability.</p>
</sec>
<sec id="s3-2-2-4">
<label>3.2.2.4</label>
<title>User interface and data management</title>
<p>Classified events can be visualized <italic>via</italic> interactive maps and exported. The tool enables individual vessel analysis as well as system-level summaries over docks, vessel classes, and time frames, thus allowing the possibility of inspecting both routes and events. The information achieved from the set of port calls highlights activities and trends over different time frames.</p>
</sec>
</sec>
</sec>
<sec id="s3-3">
<label>3.3</label>
<title>Port statistics indicators</title>
<p>The output of the events classification is used to obtain aggregate port statistics, and some key performance indicators are evaluated to assess terminal performance over the observation window.</p>
<p>By default, an overview of berth activity at dock level, is achieved through assessing the total number of vessel calls. Thus, berthing operations may be resumed through a synthetic estimator as the dwell time, evaluating the <italic>total dwell time</italic> (<italic>T</italic>
<sub>
<italic>dt</italic>
</sub>), that represents the cumulative time all the vessels occupy the berth during the observation period, and the <italic>average dwell time</italic> that captures the average time spent by a vessel at the dock. Even if aggregate measures offer a valuable portrait on the berth use (<xref ref-type="sec" rid="s4-4">Section 4.4</xref>), these statistics may be lacking in describing the effective use of the infrastructures and as far as performance may be defined from different perspectives, a further set of performance indicators will be introduced involving both spatial and temporal dimensions.</p>
<sec id="s3-3-1">
<label>3.3.1</label>
<title>Congestion indicators</title>
<p>Congestion in a maritime terminal occurs when the capacity of the berth cannot meet demand, either due to a lack of available berths or insufficient length to accommodate incoming vessels. Under such conditions, vessel turnaround time is expected to increase with a significant amount of time spent at the anchorage. A simplified way to evaluate the berth occupation status is through the congestion index <italic>CI</italic>, defined as the ratio between the number of occupied berths at interval <italic>t</italic> (<inline-formula id="inf2">
<mml:math id="m3">
<mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>o</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:math>
</inline-formula>) and the number of available berths (<italic>N</italic>
<sub>
<italic>bert</italic>
</sub>):<disp-formula id="e2">
<mml:math id="m4">
<mml:mrow>
<mml:mi>C</mml:mi>
<mml:mi>I</mml:mi>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x3d;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>o</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>b</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mfrac>
</mml:mrow>
</mml:math>
<label>(2)</label>
</disp-formula>
</p>
<p>The index <italic>CI</italic> ranges from 0 to 1 and represents a measure of berth occupation rate but, although it can be calculated at different instants of the day, it does not consider ships waiting at anchor. For such reasons another measure is introduced to capture port performance analyzing the balance between vessels waiting at the anchorage and those engaged in berth activities. Its purpose is to assess whether the port system is accumulating vessels at the anchorage or efficiently serving the incoming traffic. The basic assumption cores on the variation of vessel counts in discrete time steps, based on net inflows and outflows as:<disp-formula id="e3">
<mml:math id="m5">
<mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mi>w</mml:mi>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x3d;</mml:mo>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>w</mml:mi>
<mml:mo>_</mml:mo>
<mml:mi>i</mml:mi>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>w</mml:mi>
<mml:mo>_</mml:mo>
<mml:mi>o</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:math>
<label>(3)</label>
</disp-formula>
<disp-formula id="e4">
<mml:math id="m6">
<mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>o</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x3d;</mml:mo>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>o</mml:mi>
<mml:mi>b</mml:mi>
<mml:mtext>&#x2009;</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x2b;</mml:mo>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>o</mml:mi>
<mml:mi>b</mml:mi>
<mml:mo>_</mml:mo>
<mml:mi>i</mml:mi>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>o</mml:mi>
<mml:mi>b</mml:mi>
<mml:mo>_</mml:mo>
<mml:mi>o</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:math>
<label>(4)</label>
</disp-formula>where.<list list-type="bullet">
<list-item>
<p>
<inline-formula id="inf3">
<mml:math id="m7">
<mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mi>w</mml:mi>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:math>
</inline-formula> is the number of vessels at anchor interval <italic>t</italic>;</p>
</list-item>
<list-item>
<p>
<inline-formula id="inf4">
<mml:math id="m8">
<mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>w</mml:mi>
<mml:mo>_</mml:mo>
<mml:mi>i</mml:mi>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>w</mml:mi>
<mml:mo>_</mml:mo>
<mml:mi>o</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:math>
</inline-formula> is the variation between the entries and the exits of vessels from the anchorage area;</p>
</list-item>
<list-item>
<p>
<inline-formula id="inf5">
<mml:math id="m9">
<mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>o</mml:mi>
<mml:mi>b</mml:mi>
<mml:mo>_</mml:mo>
<mml:mi>i</mml:mi>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>o</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>b</mml:mi>
<mml:mo>_</mml:mo>
</mml:mrow>
<mml:mrow>
<mml:mi>o</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:math>
</inline-formula> is the variation between the entries and the exits of vessels at docks.</p>
</list-item>
</list>
</p>
<p>Thus, considering the variation for these two sets of vessels that occupy the berth, and the anchoring area let the analysis visualize if the number of waiting vessels increases or not. Therefore, the so-called Cumulative Congestion Index <italic>CCI</italic> highlights whether queues at anchorage are accumulating or being reduced, offering a system-level view of port balance, and can be expressed as in <xref ref-type="disp-formula" rid="e5">Equation 5</xref>.<disp-formula id="e5">
<mml:math id="m10">
<mml:mrow>
<mml:mi>C</mml:mi>
<mml:mi>C</mml:mi>
<mml:mi>I</mml:mi>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x3d;</mml:mo>
<mml:mi>C</mml:mi>
<mml:mi>C</mml:mi>
<mml:mi>I</mml:mi>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x2b;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>w</mml:mi>
<mml:mo>_</mml:mo>
<mml:mi>i</mml:mi>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi>w</mml:mi>
<mml:mo>_</mml:mo>
<mml:mi>o</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
<mml:mrow>
<mml:mi>max</mml:mi>
<mml:mtext>&#x2009;</mml:mtext>
<mml:mrow>
<mml:mfenced open="{" close="}" separators="|">
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mtext>&#x2009;</mml:mtext>
<mml:mi>N</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>o</mml:mi>
<mml:mi>b</mml:mi>
<mml:mtext>&#x2009;</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mtext>&#x2009;</mml:mtext>
</mml:mrow>
</mml:mfrac>
</mml:mrow>
</mml:math>
<label>(5)</label>
</disp-formula>
</p>
<p>
<xref ref-type="disp-formula" rid="e5">Equation 5</xref> represents a proxy of the balanced demand/supply, where the structure of the denominator ensures avoiding singularity. Interpretating the equation, an increase in <italic>CCI</italic> implies an accumulation process in the anchorage area, a constant value over the time reports about a balanced system.</p>
<p>Since vessels cannot always be accommodated at the first available berth (due to draft, length, or terminal assignment constraints), it should be of interest to analyze terminal conditions at the dock level, and for this reason, additional indicators will be introduced in the following.</p>
</sec>
<sec id="s3-3-2">
<label>3.3.2</label>
<title>Berths performance indicators</title>
<p>In the following, the use of the berth will be analyzed by highlighting both the rate of berth length and the current usage time. The proposed variables highlight berth vacancy, full operational capacity, partial operations, or temporary overcapacity that may restrict access to a vessel waiting at anchor. From this perspective, dock activity may be analyzed using a set of indicators that address the spatial and temporal dimensions. A first indicator, the yearly total empty time <italic>T</italic>
<sub>
<italic>eb</italic>
</sub>, considers the amount of time, in a year, when the infrastructure is empty. Conversely, when a set of vessels at the dock occupies all the available berths, no further operations can be hosted, the full capacity time indicator <italic>T</italic>
<sub>
<italic>fu</italic>
</sub> can be considered (it defines, for a year, the amount of time the port is working at full capacity).</p>
<p>In the case when the available berth length is sufficient to operate on the incoming vessel, but there are no other vessels at the dock, it is possible to quantify the elapsed time <italic>T</italic>
<sub>
<italic>us</italic>
</sub> when the docks is underused; in contrast when the incoming vessel length is over the available space resources, the incoming berth call is rejected, the elapsing time under this scenario is <italic>T</italic>
<sub>
<italic>b</italic>
</sub>.</p>
<p>Therefore, it is possible to define.<list list-type="bullet">
<list-item>
<p>The <italic>operational time</italic> (<italic>T</italic>
<sub>
<italic>ot</italic>
</sub>) is evaluated as the time intercurrent between the first and the last served vessel;</p>
</list-item>
<list-item>
<p>The <italic>vacancy ratio</italic> (<italic>V</italic>
<sub>
<italic>r</italic>
</sub> <italic>&#x3d; T</italic>
<sub>
<italic>eb</italic>
</sub>
<italic>/T</italic>
<sub>
<italic>ot</italic>
</sub>) accounts for the share of hours when no vessel activity occurred.</p>
</list-item>
<list-item>
<p>The <italic>berth utilization</italic> (<italic>B</italic>
<sub>
<italic>use,t</italic>
</sub> &#x3d; <italic>T</italic>
<sub>
<italic>dt</italic>
</sub>
<italic>/T</italic>
<sub>
<italic>ot</italic>
</sub>) measures the proportion of time when a berth is occupied; such an indicator can also be measured considering the space dimension (<italic>B</italic>
<sub>
<italic>use,l</italic>
</sub> &#x3d; <italic>O</italic>
<sub>
<italic>lenght</italic>
</sub>
<italic>/B</italic>
<sub>
<italic>length</italic>
</sub>) as the ratio between the portion of the berth occupied vessels and the maximum available length;</p>
</list-item>
<list-item>
<p>The <italic>full utilization ratio</italic> (<italic>F</italic>
<sub>
<italic>ur</italic>
</sub> <italic>&#x3d; T</italic>
<sub>
<italic>fu</italic>
</sub>/<italic>T</italic>
<sub>
<italic>ot</italic>
</sub>) identifies the share of time when all berths are occupied, the dock is working at its maximum capacity;</p>
</list-item>
<list-item>
<p>The <italic>residual utilization ratio</italic> (<italic>R</italic>
<sub>
<italic>ur</italic>
</sub> &#x3d; <italic>T</italic>
<sub>
<italic>us</italic>
</sub>/<italic>T</italic>
<sub>
<italic>ot</italic>
</sub>) identify the time when at the dock a residual length is available, and the incoming vessel may be moored;</p>
</list-item>
<list-item>
<p>The <italic>blocked utilization ratio</italic> (<italic>B</italic>
<sub>
<italic>ur</italic>
</sub> &#x3d; <italic>T</italic>
<sub>
<italic>b</italic>
</sub>
<italic>/T</italic>
<sub>
<italic>ot</italic>
</sub>) resumes all those events where the available berth length is not enough to host the incoming vessel.</p>
</list-item>
</list>
</p>
</sec>
</sec>
</sec>
<sec sec-type="results" id="s4">
<label>4</label>
<title>Results</title>
<p>This section summarizes the output obtained. It is structured in multiple subparagraphs that highlight tool outputs, berths operation and traffic conditions at the dock, finally the vessel turnaround time is resumed to highlight the capability enabled using AIS data when analyzing a generic port call. First an overview of the annual traffic and its distribution is offered. Then it focuses on two main aspects: berths activities though the evaluation of two crucial synthetic statistics at berth level, the average and the total dwell time, then it focuses on docks operations thus resuming their degree of utilization and occupancy. Finally, it reports an overview about traffic conditions at the maritime terminal by focusing on the main stages that characterize a generic port call. To ensure the capability of the tool, a previous study was conducted on a small case test (<xref ref-type="bibr" rid="B4">Belcore et al., 2025b</xref>). In it the trajectory analysis was applied to test the effectiveness of clustering methods in distinguishing between anchorage and berthing. The dwelling time was compared with official statics delivered by the Bureau of Transportation Statistics (2025). In addition, segmentation and classification results were also compared with other case study (<xref ref-type="bibr" rid="B28">Liang et al., 2021</xref>; <xref ref-type="bibr" rid="B59">Yan et al., 2022</xref>) whose finding was in accordance with the output of the developed procedure.</p>
<sec id="s4-1">
<label>4.1</label>
<title>Study area</title>
<p>The study area is the ports of Los Angeles-Long Beach (LALB), California (CA), United States of America, a maritime infrastructure that represents a critical container hub that links the USA and Asia, as well as a critical node for the marine traffic along the West Coast. <xref ref-type="fig" rid="F3">Figure 3</xref> shows the container dock layout of LALB port, resuming some synthetic characteristics of the docks represented in the layout. The port throughput, in the last 15&#xa0;years, ranged between eight and ten million TEUs (<xref ref-type="bibr" rid="B40">Port of Los Angeles, 2025</xref>).</p>
<fig id="F3" position="float">
<label>FIGURE 3</label>
<caption>
<p>Port of Los Angeles Long Beach - Container docks layout (source: own elaboration on OpenStreetMap).</p>
</caption>
<graphic xlink:href="ffutr-06-1735788-g003.tif">
<alt-text content-type="machine-generated">Map showing the ports of Los Angeles and Long Beach with labeled container terminals in red and green outlines. A table lists details of container terminals: layout ID, berth number, and berth length in meters for both ports.</alt-text>
</graphic>
</fig>
<p>The infrastructure has several docks, and among them, ten are directly connected to both road and rail services. Official statistics also report on the availability of approximately ninety super post panamax cranes (able to operate on more than 20 parallel rows of containers). Yearly, container docks host approximately one thousand and five hundred port calls (<xref ref-type="bibr" rid="B6">Bureau of Transportation Statistics, 2025</xref>).</p>
</sec>
<sec id="s4-2">
<label>4.2</label>
<title>Dataset</title>
<p>AIS data used in the experiment were sourced from an online repository provided by the National Oceanic and Atmospheric Administration (NOOA) and the U.S. Coast Guard Navigation Centre (<xref ref-type="bibr" rid="B34">NOOA, 2025</xref>). The open service delivers vessel traffic signals organized by day, and up now the agencies provide AIS data collected continuously since the beginning of 2009 covering the coastal areas of the United States.</p>
<p>The dataset relies on historical data spanning from January to December 2023 related to the area of the container ports of Los Angeles-Long Beach (LALB). <xref ref-type="table" rid="T1">Table 1</xref> reports on the structures of data; each record includes both kinematic and static data. Specifically, the archive stores timestamp such as <italic>BaseDateTime</italic>, longitude (<italic>LON</italic>), latitude (<italic>LAT</italic>), speed (speed over ground, <italic>SOG</italic>), course (course over ground, <italic>COG</italic>), heading, and ship information (<italic>MMSI</italic>, <italic>name</italic>, <italic>type</italic>, <italic>length</italic>, <italic>width</italic>, <italic>draft</italic>).</p>
<table-wrap id="T1" position="float">
<label>TABLE 1</label>
<caption>
<p>Feature class of information delivered from AIS devices.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Information</th>
<th align="center">Variables</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">Static</td>
<td align="center">MMSI, IMO, call sign vessel name, vessel type, length, width, draft, cargo</td>
</tr>
<tr>
<td align="left">Kinematic</td>
<td align="center">BaseDateTime, LON, LAT, speed over ground (SOG) course over ground (COG) heading</td>
</tr>
<tr>
<td align="left">Route related</td>
<td align="center">Navigation status</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>The <italic>Vessel Type</italic> attribute, as previously stated by <xref ref-type="bibr" rid="B17">Huang et al. (2023)</xref> and <xref ref-type="bibr" rid="B24">Kraus et al. (2018)</xref>, does not define specific types of vessel, but only their category, for such a reason a more comprehensive view on vessel distribution required to match the information contained in the open data with external repositories using the MMSI as pivotal variable. So far, a further set of additional static information upon vessels was achieved; thus adding (i) the capacity (TEU) of a vessel, (ii) the gross tonnage (GT) as a volume measure of the vessel, (iii) the dead weight tonnage (DWT) as maximum mass in metric tons that a vessel can carry in safe conditions.</p>
<p>The original data set contained more than seven million records. Therefore, a down-sampling strategy was applied as a preprocessing step, complemented by a control to verify the distances between consecutive positions and to exclude speeds beyond acceptable limits.</p>
<p>After removing incomplete or inconsistent entries, more than five million valid records fall within the ZoI, and through segmentation and classification analyses, a valid number of 5,127 events were classified, including stopping, underway, and piloting operations. So, the refined dataset is ready for visualization and to support statistical analyses on port operations. Since the quality of observations directly affects the reliability of the results, by following the evidence emerging from the literature (<xref ref-type="bibr" rid="B7">Chen et al., 2016</xref>; <xref ref-type="bibr" rid="B62">Zhang et al., 2019</xref>), and focus only on statistically significant operations, just those events whose berths operation lasts a minimum of 5&#xa0;hours were included in the analyzes.</p>
<p>Finally, detailed information on port configuration (docks, berths, terminal operators) was integrated into the database to support the case study.</p>
</sec>
<sec id="s4-3">
<label>4.3</label>
<title>Annual traffic</title>
<p>The port call distribution offers a solid overview of the activities that take place at the terminals. Therefore, considering just container vessels, <xref ref-type="fig" rid="F4">Figure 4</xref> reports the week-based trend of arrivals.</p>
<fig id="F4" position="float">
<label>FIGURE 4</label>
<caption>
<p>Port calls per week at LALB in the year 2023 (source: own elaboration).</p>
</caption>
<graphic xlink:href="ffutr-06-1735788-g004.tif">
<alt-text content-type="machine-generated">Bar chart showing weekly arrivals counts from week 1 to 52. Counts fluctuate between 20 and 40.</alt-text>
</graphic>
</fig>
<p>Approximately 30&#x2013;40 operations are recorded per week. Even if the official statistics reports that exchanged volumes were in line with the year 2022, the first quarter suffered a reduction with a critical point falling between February and March, where a sensible port calls reduction was detected. In line with this evidence, online reports (<xref ref-type="bibr" rid="B39">Port of Los Angeles, 2023</xref>) in February states a reduction of 43.13% of total TEUs values with respect to the previous year and approximately a 33% reduction with respect to the previous month. Similarly, the daily distribution of arrivals (<xref ref-type="fig" rid="F5">Figure 5</xref>) shows no clear trend; and, differentiating between the two maritime infrastructures, it emerges that in Los Angeles, berth operations are more concentrated at the beginning of the week, whereas in Long Beach no significant variation is observed across weekdays. <xref ref-type="fig" rid="F5">Figure 5</xref> reports the hour-based arrivals/departures trend over the year. It emerges how arrivals at the dock usually are concentrated between 11 a.m. and 2 p.m., with a further peak in the last couple of hours of the day from 9 p.m. to 11 p.m. Departures are concentrated mainly within two-time windows: the first one centered between 10 a.m. and 13 p.m., the second one between midnight and 3 a.m.</p>
<fig id="F5" position="float">
<label>FIGURE 5</label>
<caption>
<p>Vessel&#x2019;s arrivals/departures distribution per hour, year 2023 (source: own elaboration).</p>
</caption>
<graphic xlink:href="ffutr-06-1735788-g005.tif">
<alt-text content-type="machine-generated">Bar chart showing vessel arrivals and departures by hour. Blue bars represent arrivals, red bars represent departures.</alt-text>
</graphic>
</fig>
</sec>
<sec id="s4-4">
<label>4.4</label>
<title>Berth calls activities</title>
<p>A total amount of 1,591 valid berth calls were extracted from the database, whose share is 52% in LA and 48% in LB. <xref ref-type="table" rid="T2">Table 2</xref> offers an overview of the distribution of dwell time frequencies. It emerged that the dwell time (<italic>T</italic>
<sub>
<italic>op</italic>
</sub>) can largely vary, encompassing different classes of time windows, so a frequency analysis on dwelling time was executed to identify time intervals distribution. The analysis was carried out by evaluating different options, including fixed hour time windows, quantile distributions, and automated data-driven solutions. Considering the need to reduce the number of bins, and to minimize the variance among the data, the Scott formula (<xref ref-type="bibr" rid="B10">Cunningham, 2021</xref>) was chosen as the most effective to reproduce class time windows for berthing operations. Most of the operations are completed in less than a week, one out two vessels spend approximately 3&#xa0;days at the dock, and approximately 90% of operations are completed in less than 5&#xa0;days.</p>
<table-wrap id="T2" position="float">
<label>TABLE 2</label>
<caption>
<p>Berthing events and frequency distribution at LALB year 2023.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Time windows [h]</th>
<th align="center">Vessels count [units]</th>
<th align="center">Frequency [%]</th>
<th align="center">Cumulated frequency [%]</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">7&#x2013;21</td>
<td align="center">99</td>
<td align="center">6.22</td>
<td align="center">6.22</td>
</tr>
<tr>
<td align="left">21&#x2013;35</td>
<td align="center">219</td>
<td align="center">13.76</td>
<td align="center">19.99</td>
</tr>
<tr>
<td align="left">35&#x2013;49</td>
<td align="center">245</td>
<td align="center">15.40</td>
<td align="center">35.39</td>
</tr>
<tr>
<td align="left">49&#x2013;63</td>
<td align="center">145</td>
<td align="center">9.11</td>
<td align="center">44.50</td>
</tr>
<tr>
<td align="left">63&#x2013;77</td>
<td align="center">126</td>
<td align="center">7.92</td>
<td align="center">52.42</td>
</tr>
<tr>
<td align="left">77&#x2013;91</td>
<td align="center">126</td>
<td align="center">7.92</td>
<td align="center">60.34</td>
</tr>
<tr>
<td align="left">91&#x2013;105</td>
<td align="center">133</td>
<td align="center">8.36</td>
<td align="center">68.70</td>
</tr>
<tr>
<td align="left">105&#x2013;119</td>
<td align="center">164</td>
<td align="center">10.31</td>
<td align="center">79.01</td>
</tr>
<tr>
<td align="left">119&#x2013;133</td>
<td align="center">94</td>
<td align="center">5.91</td>
<td align="center">84.92</td>
</tr>
<tr>
<td align="left">133&#x2013;147</td>
<td align="center">87</td>
<td align="center">5.47</td>
<td align="center">90.38</td>
</tr>
<tr>
<td align="left">147&#x2013;161</td>
<td align="center">59</td>
<td align="center">3.71</td>
<td align="center">94.09</td>
</tr>
<tr>
<td align="left">161&#x2013;175</td>
<td align="center">32</td>
<td align="center">2.01</td>
<td align="center">96.10</td>
</tr>
<tr>
<td align="left">175&#x2013;189</td>
<td align="center">21</td>
<td align="center">1.32</td>
<td align="center">97.42</td>
</tr>
<tr>
<td align="left">189&#x2013;203</td>
<td align="center">20</td>
<td align="center">1.26</td>
<td align="center">98.68</td>
</tr>
<tr>
<td align="left">203 &#x2b;</td>
<td align="center">21</td>
<td align="center">1.32</td>
<td align="center">100.00</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>Observing the dwelling time for the port calls over the year does not emerge significant variations, however, the elapsed time varies among different docks. The <xref ref-type="fig" rid="F6">Figures 6</xref>, <xref ref-type="fig" rid="F7">7</xref> report information above the average dwell time by differentiating between Los Angeles and Long Beach docks. Similarly, <xref ref-type="fig" rid="F8">Figures 8</xref>, <xref ref-type="fig" rid="F9">9</xref> informs over total berth use for month. It is possible to differentiate between two classes of docks, those where the average dwell time usually lasts a maximum of 2&#xa0;days, and the others where operation usually takes at least three to 5&#xa0;days to complete their activities.</p>
<fig id="F6" position="float">
<label>FIGURE 6</label>
<caption>
<p>Average dwell time in Los Angeles docks, year 2023.</p>
</caption>
<graphic xlink:href="ffutr-06-1735788-g006.tif">
<alt-text content-type="machine-generated">Bar chart showing average dwell time in hours at six terminals over the year 2023. Terminals include CHINA SH, EVERGREEN CT, PIER 300, PIER 400, TRAPAC CT, and YUSEN CT.</alt-text>
</graphic>
</fig>
<fig id="F7" position="float">
<label>FIGURE 7</label>
<caption>
<p>Average dwell time in Long Beach docks, year 2023.</p>
</caption>
<graphic xlink:href="ffutr-06-1735788-g007.tif">
<alt-text content-type="machine-generated">A bar chart that shows the average time spent at six piers (A, C, E, G, J, T) over the year 2023. Each month, it displays colorful bars for each pier. Pier J and T usually have higher values than the mean.</alt-text>
</graphic>
</fig>
<fig id="F8" position="float">
<label>FIGURE 8</label>
<caption>
<p>Total dwell time in Los Angeles docks, year 2023.</p>
</caption>
<graphic xlink:href="ffutr-06-1735788-g008.tif">
<alt-text content-type="machine-generated">Bar chart displaying total dwell time in hours for six shipping terminals in Los Angeles over the year 2023. The terminals are represented by different colored bars, showing different utilization among the different infrastructures, with Pier 400 consistently having the highest dwell times.</alt-text>
</graphic>
</fig>
<fig id="F9" position="float">
<label>FIGURE 9</label>
<caption>
<p>Total dwell time in Long Beach docks, year 2023.</p>
</caption>
<graphic xlink:href="ffutr-06-1735788-g009.tif">
<alt-text content-type="machine-generated">This bar chart illustrates the total dwell time in Liong Beach over the year 2023. Each month shows different-colored bars representing PIER A, C, E, G, J, and T, with varying heights indicating differences in dwell time.</alt-text>
</graphic>
</fig>
<p>From <xref ref-type="fig" rid="F6">Figures 6</xref>, <xref ref-type="fig" rid="F7">7</xref>, the average dwell time of Pier A and Pier C in Long Beach has a range of approximately 35&#x2013;50&#xa0;h (two working days), with a slight inter-period variation, thus suggesting a good degree of performance in terms of efficiency. Those performances are not affected by the increasing total amount for served vessels during the summer period. It also emerged that increasing the number of visits also decreases the time necessary to complete operations, so a good margin of resources and workload is available at the dock.</p>
<p>Between June and August, the total dwell time (<xref ref-type="fig" rid="F8">Figures 8</xref>, <xref ref-type="fig" rid="F9">9</xref>) sensibly increases, and considering that the average time for this period is quite stable with the trend performance, this confirms how this quarter represents the most active. It emerged that the average dwell time is higher for Pier 300 and 400 for Los Angeles and Pier G for Long Beach; this evidence may be motivated by the presence of vessels of different shipping lines. Moreover, it opens the way for further detailed analyses that will focus on dock equipment and workloads that are out of the scope of the paper.</p>
</sec>
<sec id="s4-5">
<label>4.5</label>
<title>Congestion and performance measures analysis</title>
<p>The analysis on annual vessel traffic opened the way to a further degree of analysis to find some statistical measures to quantify the effective berth utilization rate using key performance indicators and enhanced measures. At first, the indicator that is considered in relation to the average berth utilization, is the Congestion Index. It is a congestion measure that lets the analyst observe, over different time frames, the average availability of a free berth for each dock. <xref ref-type="fig" rid="F10">Figures 10</xref>, <xref ref-type="fig" rid="F11">11</xref> report the monthly average occupation index. The monthly analyses states how the occupation index ranges between 30% and 60%, thus implying the possibility of having an available berth for an incoming vessel. The availability of a free berth sensibly varies depending on the dock. In Los Angeles average occupation values are higher for those docks whose total exchange values have a higher market share. For example, Pier 400 and Pier 300 account for more than the 50% port calls handled. A similar trend is observed in Long Beach, where the average degree of occupation is higher at Pier E that yearly handles most of the container traffic.</p>
<fig id="F10" position="float">
<label>FIGURE 10</label>
<caption>
<p>Congestion Index (average value) per dock in Los Angeles (LA), year 2023.</p>
</caption>
<graphic xlink:href="ffutr-06-1735788-g010.tif">
<alt-text content-type="machine-generated">Line graph showing congestion index trends for various terminals for Los Angeles over the year 2023. Terminals include China SH, Evergreen C, Pier 300, Pier 400, Tracpac CT, and Yusen CT. The index ranges from 0.2 to 1.0. Each terminal displays distinct fluctuations, with notable peak and trough patterns across the months.</alt-text>
</graphic>
</fig>
<fig id="F11" position="float">
<label>FIGURE 11</label>
<caption>
<p>Congestion Index (average value) per dock in Long Beach (LB) year 2023.</p>
</caption>
<graphic xlink:href="ffutr-06-1735788-g011.tif">
<alt-text content-type="machine-generated">Line graph showing the congestion index in Long Beach over the year 2023. Pier E has the highest fluctuation, peaking in August. Other piers remain relatively stable, with minor variations throughout the year.</alt-text>
</graphic>
</fig>
<p>It is noticeable that, in general, Long Beach docks have a lower rate than those in Los Angeles, suggesting that the infrastructure is underutilized. Over the year, activities are more intense in Los Angeles where docks work with a higher degree of occupation; from April to November, LA has numerous vessels, and occupancy ranges from 0.60 to 0.90. It emerges that some docks do not operate at their maximum capacity and over the year dwell time may largely vary. In fact, it was decided to focus both on the evaluation of the <italic>CCI</italic> and on the use of berth to derive some performance indicators by analyzing berth activities.</p>
<p>
<italic>CCI</italic> (<xref ref-type="fig" rid="F12">Figure 12</xref>) assesses the balance between the presence of vessels in the anchorage area and the active operation at the dock. Over the year the <italic>CCI</italic> ranges between [0.10&#x2013;0.40]; the relatively low ratio of the value asses the possibility of the vessel to be served at the first available berth. Peaks are rare so those vessels that occupy the anchorage area represent a limited share, and the majority directly access the dock.</p>
<fig id="F12" position="float">
<label>FIGURE 12</label>
<caption>
<p>Weekly based Cumulative Congestion Index.</p>
</caption>
<graphic xlink:href="ffutr-06-1735788-g012.tif">
<alt-text content-type="machine-generated">Line graph depicting the Cumulative Congestion inddex for the whole maritime area of Los Angeles Loing Beach over the year 2023. The CCI, on weekly base analyuses, fluctuates between 0.1 and 0.4</alt-text>
</graphic>
</fig>
<p>Finally, as previously highlighted in <xref ref-type="fig" rid="F5">Figure 5</xref>, the mooring arrival/departure at the berths may represent a critical issue due to the overlapping presence of multiple vessels. Therefore, a more in-depth study was conducted to effectively characterize the docks&#x2019; residual capacity in both space and time dimension and quantify dock efficiency and occupancy ratio. <xref ref-type="table" rid="T3">Table 3</xref> resumes the outputs, the analyses are conducted always at dock scale, offering an overview of expected performance under different traffic conditions.</p>
<table-wrap id="T3" position="float">
<label>TABLE 3</label>
<caption>
<p>Docks activities measures.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Dock</th>
<th align="center">B<sub>use,l</sub> [%]</th>
<th align="center">B<sub>use,t</sub> [%]</th>
<th align="center">V<sub>r</sub> [%]</th>
<th align="center">F<sub>ur</sub> [%]</th>
<th align="center">R<sub>ur</sub> [%]</th>
<th align="center">B<sub>ur</sub> [%]</th>
</tr>
</thead>
<tbody valign="top">
<tr style="background-color:#CCCCCC">
<td colspan="7" align="center">Los Angeles (LA)</td>
</tr>
<tr>
<td align="left">CH shipping</td>
<td align="center">88.50</td>
<td align="center">63.60</td>
<td align="center">0.36</td>
<td align="center">0.20</td>
<td align="center">0.43</td>
<td align="center">---</td>
</tr>
<tr>
<td align="left">EverGreen</td>
<td align="center">35.00</td>
<td align="center">57.80</td>
<td align="center">0.42</td>
<td align="center">0.05</td>
<td align="center">0.53</td>
<td align="center">---</td>
</tr>
<tr>
<td align="left">Pier 300</td>
<td align="center">83.20</td>
<td align="center">93.20</td>
<td align="center">0.07</td>
<td align="center">0.25</td>
<td align="center">0.68</td>
<td align="center">---</td>
</tr>
<tr>
<td align="left">Pier 400</td>
<td align="center">53.00</td>
<td align="center">96.70</td>
<td align="center">0.04</td>
<td align="center">0.03</td>
<td align="center">0.94</td>
<td align="center">---</td>
</tr>
<tr>
<td align="left">TraPac</td>
<td align="center">38.30</td>
<td align="center">75.40</td>
<td align="center">0.25</td>
<td align="center">0.05</td>
<td align="center">0.70</td>
<td align="center">---</td>
</tr>
<tr>
<td align="left">Yusen</td>
<td align="center">46.90</td>
<td align="center">79.90</td>
<td align="center">0.20</td>
<td align="center">0.07</td>
<td align="center">0.72</td>
<td align="center">---</td>
</tr>
<tr style="background-color:#CCCCCC">
<td colspan="7" align="center">Long Beach (LB)</td>
</tr>
<tr>
<td align="left">Pier A</td>
<td align="center">63.20</td>
<td align="center">62.70</td>
<td align="center">0.37</td>
<td align="center">0.07</td>
<td align="center">0.53</td>
<td align="center">0.02</td>
</tr>
<tr>
<td align="left">Pier C</td>
<td align="center">48.00</td>
<td align="center">50.40</td>
<td align="center">0.49</td>
<td align="center">---</td>
<td align="center">0.48</td>
<td align="center">0.03</td>
</tr>
<tr>
<td align="left">Pier E</td>
<td align="center">81.70</td>
<td align="center">94.2 0</td>
<td align="center">0.06</td>
<td align="center">0.32</td>
<td align="center">0.62</td>
<td align="center">---</td>
</tr>
<tr>
<td align="left">Pier G</td>
<td align="center">56.40</td>
<td align="center">90.20</td>
<td align="center">0.10</td>
<td align="center">0.05</td>
<td align="center">0.79</td>
<td align="center">0.05</td>
</tr>
<tr>
<td align="left">Pier J</td>
<td align="center">26.40</td>
<td align="center">39.10</td>
<td align="center">0.60</td>
<td align="center">---</td>
<td align="center">0.39</td>
<td align="center">---</td>
</tr>
<tr>
<td align="left">Pier T</td>
<td align="center">70.80</td>
<td align="center">88.40</td>
<td align="center">0.11</td>
<td align="center">0.05</td>
<td align="center">0.78</td>
<td align="center">0.06</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>
<xref ref-type="table" rid="T3">Table 3</xref> shows berth activities are for all docks; however at least one berth is always occupied; the average berth use (<italic>B</italic>
<sub>
<italic>use,l</italic>
</sub>) assesses how vessels may occupy different degrees of space. For example, activities at the Evergreen docks only require an average occupation ratio of 35% with respect to available length, this implies a valuable resource of space for incoming vessels, the same circumstance is also evidenced by the higher degree of vacancy ratio on time. On the other hand, activities at Pier 300 are more intense, both spatial and temporal indexes on berth use assess how at the terminal good efficiency is reached. Similar performances were highlighted by Pier E at Long Beach, in both the residual capacity ratio indicates the possibility to host also bigger classes of vessels. The analysis also states how vacancy time ratio (<italic>V</italic>
<sub>
<italic>r</italic>
</sub>) has higher degree in those docks where the full capacity ratio is rarely reached (e.g., Evergreen and Pier A). This suggests for the year 2023 that port calls were not intense, and a further reserve of capacity is available to deal with not expected events, in general this safety margin can be considered crucial in preventing extreme events of congestion. In general, it emerged that, considering the current level of traffic, the available infrastructures guarantee a satisfying performance. Also, the value of the blocked utilization ratio (<italic>B</italic>
<sub>
<italic>ur</italic>
</sub>) is not significant for most docks. The output implies the capability of the system to deal with the incoming vessels and possibly recovering to unexpected delays on navigation. Moreover, for those docks operated by different shipping companies, the expected waiting to recover from failures should be reduced.</p>
</sec>
<sec id="s4-6">
<label>4.6</label>
<title>Vessel turnaround time</title>
<p>Finally, port call analysis is performed ordering events at the dock level. Differentiating vessel sizes through cross-section, as defined in the official reports (<xref ref-type="bibr" rid="B6">Bureau of Transportation Statistics, 2025</xref>), vessels were grouped into four different classes. <xref ref-type="fig" rid="F13">Figure 13</xref> reports the monthly share of the anchoring operation, thus valuing the percentage of each vessel class that occupies the anchorage area. <xref ref-type="fig" rid="F13">Figure 13</xref> provides a valuable insight into the relationship between vessel size and anchorage operations. The analyses underline that a higher percentage of vessels involved in anchoring operation usually have a capacity is below 5,000 TEUs. However, no direct evidence emerges on how vessel size can affect the total time spent at the anchor area; the data indicate that neo-Panamax and above are generally assigned to the first available berth. From the berth side, although a preliminary analysis was carried out, the results were not fully significant. This result is consistent with the findings provided by <xref ref-type="bibr" rid="B50">Smith (2021)</xref>, who tried to develop a model to improve the relationship between vessel size and dwelling time at the berth. Moreover, as suggested by <xref ref-type="bibr" rid="B32">Musolino et al. (2026b)</xref>, the relationship between the dwelling time and vessel capacity should be fully addressed considering ICT technology in the port. For such a reason, this analysis was postponed, to try to overcome this limitation by analyzing further data repositories.</p>
<fig id="F13" position="float">
<label>FIGURE 13</label>
<caption>
<p>Vessels involved in anchoring operation in LALB, share year 2023.</p>
</caption>
<graphic xlink:href="ffutr-06-1735788-g013.tif">
<alt-text content-type="machine-generated">Bar chart showing anchorage share fover the year 2023. Utilizing a Bot report ships are classified as Megaship, Neo-Panamax, Panamax, and Post-Panamax. Share remains quite constat over the year, Panamax vessel has an hifgher probability to be involved into anchorign operations.</alt-text>
</graphic>
</fig>
<p>
<xref ref-type="table" rid="T4">Table 4</xref> assesses the sequence of operations, underlying how much each phase influences the total time spent by a vessel at the terminal. Data reported refers to an ideal port call, at dock level, for those ships who followed each subphase up to leaving the terminal area. As previously stated by <xref ref-type="bibr" rid="B1">AbuAlhaol et al. (2018)</xref> and <xref ref-type="bibr" rid="B7">Chen et al. (2016)</xref> it emerged that <italic>T</italic>
<sub>
<italic>ber</italic>
</sub> and <italic>T</italic>
<sub>
<italic>un</italic>
</sub>, operations have only a limited impact on <italic>T</italic>
<sub>
<italic>V</italic>
</sub>.</p>
<table-wrap id="T4" position="float">
<label>TABLE 4</label>
<caption>
<p>Vessel Turnaround Time composition at dock level.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th rowspan="2" align="center">Dock</th>
<th colspan="2" align="center">Anchoring (<italic>T</italic>
<sub>
<italic>w</italic>
</sub>)</th>
<th colspan="2" align="center">Maneuvering (<italic>T</italic>
<sub>
<italic>ber</italic>
</sub>)</th>
<th colspan="2" align="center">Dwell time (<italic>T</italic>
<sub>
<italic>op</italic>
</sub>)</th>
<th colspan="2" align="center">Maneuvering (<italic>T</italic>
<sub>
<italic>un</italic>
</sub>)</th>
</tr>
<tr>
<th align="center">
<italic>[h:mm]</italic>
</th>
<th align="center">
<italic>[%]</italic>
</th>
<th align="center">
<italic>[h:mm]</italic>
</th>
<th align="center">
<italic>[%]</italic>
</th>
<th align="center">
<italic>[h:mm]</italic>
</th>
<th align="center">
<italic>[%]</italic>
</th>
<th align="center">
<italic>[h:mm]</italic>
</th>
<th align="center">
<italic>[%]</italic>
</th>
</tr>
</thead>
<tbody valign="top">
<tr style="background-color:#CCCCCC">
<td colspan="9" align="center">Los Angeles (LA)</td>
</tr>
<tr>
<td align="left">CH shipping</td>
<td align="center">41:25&#x2032;</td>
<td align="center">45.0</td>
<td align="center">2:15&#x2032;</td>
<td align="center">2.3</td>
<td align="center">46:20&#x2032;</td>
<td align="center">50.4</td>
<td align="center">2:15&#x2032;</td>
<td align="center">2.3</td>
</tr>
<tr>
<td align="left">EverGreen</td>
<td align="center">08:00&#x2032;</td>
<td align="center">9.2</td>
<td align="center">1:40&#x2032;</td>
<td align="center">1.9</td>
<td align="center">76:00</td>
<td align="center">87.4</td>
<td align="center">1:30&#x2032;</td>
<td align="center">1.6</td>
</tr>
<tr>
<td align="left">Pier 300</td>
<td align="center">24:00&#x2032;</td>
<td align="center">27.2</td>
<td align="center">2:15&#x2032;</td>
<td align="center">2.5</td>
<td align="center">61:50&#x2032;</td>
<td align="center">68.7</td>
<td align="center">1:30&#x2032;</td>
<td align="center">1.6</td>
</tr>
<tr>
<td align="left">Pier 400</td>
<td align="center">24:50&#x2032;</td>
<td align="center">37.8</td>
<td align="center">2:50&#x2032;</td>
<td align="center">2.9</td>
<td align="center">38:30&#x2032;</td>
<td align="center">56.6</td>
<td align="center">1:45&#x2032;</td>
<td align="center">2.7</td>
</tr>
<tr>
<td align="left">TraPac</td>
<td align="center">17:50&#x2032;</td>
<td align="center">20.1</td>
<td align="center">3:00&#x2032;</td>
<td align="center">3.4</td>
<td align="center">66:00&#x2032;</td>
<td align="center">74.3</td>
<td align="center">1:50&#x2032;</td>
<td align="center">2.1</td>
</tr>
<tr>
<td align="left">Yusen</td>
<td align="center">40:00&#x2032;</td>
<td align="center">44.2</td>
<td align="center">2:15&#x2032;</td>
<td align="center">2.5</td>
<td align="center">46:25&#x2032;</td>
<td align="center">51.1</td>
<td align="center">2:10&#x2032;</td>
<td align="center">2.3</td>
</tr>
<tr style="background-color:#CCCCCC">
<td colspan="9" align="center">Long Beach (LB)</td>
</tr>
<tr>
<td align="left">Pier A</td>
<td align="center">14:30&#x2032;</td>
<td align="center">34.1</td>
<td align="center">4:40&#x2032;</td>
<td align="center">4.6</td>
<td align="center">24:15&#x2032;</td>
<td align="center">57.3</td>
<td align="center">4:00&#x2032;</td>
<td align="center">4.0</td>
</tr>
<tr>
<td align="left">Pier C</td>
<td align="center">20:15&#x2032;</td>
<td align="center">20.2</td>
<td align="center">5:45&#x2032;</td>
<td align="center">5.8</td>
<td align="center">48:45&#x2032;</td>
<td align="center">68.8</td>
<td align="center">5:15&#x2032;</td>
<td align="center">5.2</td>
</tr>
<tr>
<td align="left">Pier E</td>
<td align="center">15:15&#x2032;</td>
<td align="center">11.1</td>
<td align="center">2:45&#x2032;</td>
<td align="center">2.0</td>
<td align="center">117:00&#x2032;</td>
<td align="center">85.1</td>
<td align="center">1:30&#x2032;</td>
<td align="center">1.7</td>
</tr>
<tr>
<td align="left">Pier G</td>
<td align="center">77:00&#x2032;</td>
<td align="center">47.1</td>
<td align="center">1:15&#x2032;</td>
<td align="center">0.7</td>
<td align="center">81:00&#x2032;</td>
<td align="center">50.7</td>
<td align="center">1:15&#x2032;</td>
<td align="center">0.7</td>
</tr>
<tr>
<td align="left">Pier J</td>
<td align="center">38:00&#x2032;</td>
<td align="center">34.0</td>
<td align="center">1:00&#x2032;</td>
<td align="center">0.9</td>
<td align="center">72:00&#x2032;</td>
<td align="center">64.4</td>
<td align="center">0:45&#x2032;</td>
<td align="center">0.7</td>
</tr>
<tr>
<td align="left">Pier T</td>
<td align="center">14:00&#x2032;</td>
<td align="center">13.5</td>
<td align="center">2:00&#x2032;</td>
<td align="center">1.8</td>
<td align="center">86:00&#x2032;</td>
<td align="center">83.1</td>
<td align="center">1:45&#x2032;</td>
<td align="center">1.6</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>At the Los Angeles container terminals, dwell time usually dominates vessel turnaround time, ranging from 50% to 89%, as seen at the Evergreen terminal. Anchoring time showed a wide variation, where some docks usually operate with lower anchoring stages compared to others, as is the case of Ch Shipping. For those vessels involved in anchoring operations, the occupation of the anchorage area may cover more than 40% of <italic>T</italic>
<sub>
<italic>v</italic>
</sub>. This output result is consistent as far as the dock mentioned above works with a degree of full capacity close to 20%. It also emerged that vessels visit the anchorage area once berth operations are concluded. Maneuvering results are usually below 3%.</p>
<p>Conversely, Long Beach gives back a more heterogeneous scheme; even in general dwell time strongly prevails on anchorage. Finally, Piers A and G occupy an intermediate position, with anchoring shares of 35%&#x2013;47% and berth around 50%&#x2013;60%. Piloting times at LB terminals are more variable than in LA, occasionally reaching values above 4%&#x2013;6% (Pier A, Pier C), but still marginal compared to the total cycle.</p>
<p>Resuming the berthing operations still represent the main component, but anchoring operations strongly emerge as an influencing factor for that sequence of operations that may be divergent from the expected schedule. Due to the configuration of the maritime, maneuvering within the terminal is structurally negligible for both ports, the wide range in anchoring shares points to uneven capacity distribution across docks and highlights the strategic importance of berth allocation and call management.</p>
</sec>
</sec>
<sec sec-type="conclusion" id="s5">
<label>5</label>
<title>Conclusion</title>
<p>Given the wider availability of AIS data, this paper has explored the potential of such data as a source for analyzing port operations, with particular emphasis on vessel activities within container terminals. The development of a modular procedure has demonstrated how raw AIS data can be transformed into structured information, allowing performance analysis and assessment of port operations. To achieve this, the proposed framework integrates several stages, including data cleaning, trajectory segmentation, and event classification. By processing data sources, this study confirmed the feasibility of integrating AIS information into maritime operational analysis. In fact, the tool allows the assessment of port operations by linking navigation phases with anchorage and berth phases, as well as maneuvering. The tool itself has been structured as a flexible modular framework designed to support automatic detection and classification of key stages in a vessel&#x2019;s port call. Its architecture comprises interconnected modules, starting with a data layer that manages and preprocesses raw AIS signals, through trajectory segmentation and event classification components, to advanced visualization and reporting functionalities. The framework incorporates spatial and temporal filtering, rule-based algorithms for determining vessel status, and geospatial enrichment to distinguish each step that characterizes a port call. The final dashboard provides both vessel- and system-level overviews, enabling analysts to investigate operations across different docks, vessel classes, and time frames. This modular structure not only ensures scalability and adaptability to various port environments but also provides a robust foundation for ongoing monitoring and data-driven decision-making. The ability to distinguish these phases enables calculation of berth use and area occupation, thereby allowing comparison across different time windows. This procedure also provides the analyst with the opportunity to assess the utilization of the berth and analyze in detail the cases in which the docks are fully operational and those in which incoming vessels have to wait before accessing the channel to reach the berth. Finally, the procedure provides a set of statistical indicators that represent berth utilization and resumption of ship behavior at the terminal. The tool proved to be effective in identifying and quantifying operational patterns, measuring dwell time without relying on direct surveys or port authority records.</p>
<p>The case study of the Los Angeles-Long Beach port system provided empirical evidence of the framework&#x2019;s applicability. The results indicated that, during the period examined, the terminals retain a valuable capacity reserve to accommodate incoming vessels, ensuring that berths are generally available even during heavy traffic. Although saturation phenomena frequently appear in Los Angeles, congestion in Long Beach rarely exceeds 0.6. Furthermore, the analysis revealed that higher vessel call frequencies are associated with shorter operating times, suggesting efficient allocation of resources and robust capacity to manage variable workloads on the dock. During the vessel turnaround cycle, it was important to highlight that most docks are capable of accommodating incoming vessels. Several performance indicators were introduced to exploit information from AIS data and provide deeper detail on berth operations. These descriptors are intended to reinforce the knowledge of a port call analysis. In particular, the average and total dwell time highlight operational trends, while incorporating the length of the vessel provides a clearer understanding of how much of the berth is occupied. Furthermore, the ability to identify when a berth is fully or partially vacant, or when an incoming vessel must wait due to insufficient available length, provides information on the berth use ratio.</p>
<p>In general, the proposed procedure provides stakeholders with a versatile tool for visualizing and summarizing port conditions across various traffic scenarios. Extending the observations over a yearly horizon further allowed for the identification of long-term trends and potential impacts of future events. These results underscore the strategic value of AIS in understanding terminal performance and in supporting both operational decisions and infrastructure planning. This approach also enabled the detection of cyclic behaviors, recovery times after disruptions, and the role of traffic heterogeneity across different docks.</p>
<p>At the current stage of development, the tool emphasized the capability enabled by AIS information extraction, however further step forward should be represented by the possibility to use historical data to foresee future port conditions and enable what-if analyses. Although the AIS database has been enriched with reference to TEU, GT, DWT, and channel depth has been verified for each berth, future work should focus on a more in-depth analysis of traffic heterogeneity. An additional research direction could involve the investigation of correlations between the volumes handled at each berth and the dwelling times and/or vessel tonnage, which would require the development of an appropriate model to reproduce handling operations.</p>
</sec>
</body>
<back>
<sec sec-type="data-availability" id="s6">
<title>Data availability statement</title>
<p>Publicly available datasets were analyzed in this study. This data can be found here: <ext-link ext-link-type="uri" xlink:href="https://hub.marinecadastre.gov/">https://hub.marinecadastre.gov/</ext-link>.</p>
</sec>
<sec sec-type="author-contributions" id="s7">
<title>Author contributions</title>
<p>OB: Methodology, Investigation, Software, Data curation, Conceptualization, Writing &#x2013; original draft, Formal Analysis, Writing &#x2013; review and editing, Visualization. AP: Visualization, Conceptualization, Validation, Project administration, Funding acquisition, Methodology, Supervision, Writing &#x2013; review and editing.</p>
</sec>
<sec sec-type="COI-statement" id="s9">
<title>Conflict of interest</title>
<p>The author(s) declared that this work was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.</p>
</sec>
<sec sec-type="ai-statement" id="s10">
<title>Generative AI statement</title>
<p>The author(s) declared that generative AI was not used in the creation of this manuscript.</p>
<p>Any alternative text (alt text) provided alongside figures in this article has been generated by Frontiers with the support of artificial intelligence and reasonable efforts have been made to ensure accuracy, including review by the authors wherever possible. If you identify any issues, please contact us.</p>
</sec>
<sec sec-type="disclaimer" id="s11">
<title>Publisher&#x2019;s note</title>
<p>All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.</p>
</sec>
<fn-group>
<fn fn-type="custom" custom-type="edited-by">
<p>
<bold>Edited by:</bold> <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/748951/overview">Emrah Demir</ext-link>, Cardiff University, United Kingdom</p>
</fn>
<fn fn-type="custom" custom-type="reviewed-by">
<p>
<bold>Reviewed by:</bold> <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/1367393/overview">Francesco Russo</ext-link>, Mediterranea University of Reggio Calabria, Italy</p>
<p>
<ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/1532561/overview">David Guerrero</ext-link>, Universit&#xe9; Gustave Eiffel, France</p>
<p>
<ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/852404/overview">Sang Jin Kweon</ext-link>, Ulsan National Institute of Science and Technology, Republic of Korea</p>
</fn>
</fn-group>
<fn-group>
<fn fn-type="abbr" id="abbrev1">
<label>Abbreviations:</label>
<p>AIS, Automatic Identification System; B<sub>ur</sub>, Blocked Utilization Ratio; B<sub>use,l</sub>, Berth Utilization (length); B<sub>use,t</sub>, Berth Utilization (time); CCI, Cumulative Congestion Index; CI, Congestion Index; COG, Course Over Ground; DWT, Dead Weight Tonnage; F<sub>ur</sub>, Full Utilization Ratio; GT, Gross Tonnage; IMO, International Maritime Organization; MMSI, Maritime Mobile Service Identity; R<sub>ur</sub>, Residual Utilization Ratio; SOG, Speed Over Ground; SOLAS, International Convention for the Safety of Life at Sea; T<sub>b</sub>, Blocked time; T<sub>ber</sub>, Time to access berth; T<sub>eb</sub>, Total Empty Time; T<sub>fu</sub>, Full Utilization Time; T<sub>l</sub>, Time to leave port; T<sub>op</sub>, Dwell Time; T<sub>ot</sub>, Operational Time; T<sub>un</sub>, Time to leave berth; T<sub>us</sub>, Docks Underused Time; T<sub>v</sub>, Vessel Turnaround Time; T<sub>w</sub>, Anchorage time; V<sub>r</sub>, Vacancy Ratio; ZoI, Zone of Interest.</p>
</fn>
</fn-group>
<ref-list>
<title>References</title>
<ref id="B1">
<mixed-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>AbuAlhaol</surname>
<given-names>I.</given-names>
</name>
<name>
<surname>Falcon</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Abielmona</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Petriu</surname>
<given-names>E.</given-names>
</name>
</person-group> (<year>2018</year>). <article-title>Mining port congestion indicators from big AIS data</article-title>. In: <conf-name>2018 international joint conference on neural networks (IJCNN)</conf-name>, <fpage>1</fpage>&#x2013;<lpage>8</lpage>. <pub-id pub-id-type="doi">10.1109/IJCNN.2018.8489187</pub-id>
</mixed-citation>
</ref>
<ref id="B2">
<mixed-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Belcore</surname>
<given-names>O. M.</given-names>
</name>
<name>
<surname>Polimeni</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>2025</year>). <article-title>Marine transport analyses: a toolkit to assess vessel operations at the container port</article-title>. In: <source>2025 IEEE international conference on environment and electrical engineering and 2025 IEEE industrial and commercial power systems Europe (EEEIC/I&#x26;CPS Europe)</source>, <fpage>1</fpage>&#x2013;<lpage>7</lpage>. <pub-id pub-id-type="doi">10.1109/EEEIC/ICPSEurope64998.2025.11169025</pub-id>
</mixed-citation>
</ref>
<ref id="B3">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Belcore</surname>
<given-names>O. M.</given-names>
</name>
<name>
<surname>Di Gangi</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Polimeni</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>2025a</year>). <article-title>Automatic identification system data to assess container port performances</article-title>. <source>Transp. Res. Procedia</source> <volume>86</volume>, <fpage>612</fpage>&#x2013;<lpage>619</lpage>. <pub-id pub-id-type="doi">10.1016/j.trpro.2025.04.077</pub-id>
</mixed-citation>
</ref>
<ref id="B4">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Belcore</surname>
<given-names>O. M.</given-names>
</name>
<name>
<surname>Di Gangi</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Polimeni</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>2025b</year>). <article-title>Open AIS data to assess seaside operations in container ports</article-title>. <source>Prog. Mar. Sci. Technol.</source> <volume>10</volume>, <fpage>198</fpage>&#x2013;<lpage>207</lpage>. <pub-id pub-id-type="doi">10.3233/PMST250026</pub-id>
</mixed-citation>
</ref>
<ref id="B5">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Belmoukari</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Audy</surname>
<given-names>J.-F.</given-names>
</name>
<name>
<surname>Forget</surname>
<given-names>P.</given-names>
</name>
</person-group> (<year>2023</year>). <article-title>Smart port: a systematic literature review</article-title>. <source>Eur. Transp. Res. Rev.</source> <volume>15</volume> (<issue>1</issue>), <fpage>4</fpage>. <pub-id pub-id-type="doi">10.1186/s12544-023-00581-6</pub-id>
</mixed-citation>
</ref>
<ref id="B6">
<mixed-citation publication-type="book">
<collab>Bureau of Transportation Statistics</collab> (<year>2025</year>). <source>
<italic>Port performance freight statistics: 2025 annual report</italic> (Version annual report) [Application/pdf]</source>. <publisher-name>Washington, DC, United States: Bureau of Transportation Statistics</publisher-name>. <pub-id pub-id-type="doi">10.21949/Z3WJ-HD65</pub-id>
</mixed-citation>
</ref>
<ref id="B7">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Chen</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Zhang</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Ma</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Li</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Wu</surname>
<given-names>Z.</given-names>
</name>
<etal/>
</person-group> (<year>2016</year>). <article-title>Container port performance measurement and comparison leveraging ship gps traces and maritime open data</article-title>. <source>IEEE Trans. Intelligent Transp. Syst.</source> <volume>17</volume> (<issue>5</issue>), <fpage>1227</fpage>&#x2013;<lpage>1242</lpage>. <pub-id pub-id-type="doi">10.1109/TITS.2015.2498409</pub-id>
</mixed-citation>
</ref>
<ref id="B8">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Chen</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Geng</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Ye</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Yan</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Shi</surname>
<given-names>J.</given-names>
</name>
<etal/>
</person-group> (<year>2023</year>). <article-title>Monitoring and evaluation of ship operation congestion status at container ports based on AIS data</article-title>. <source>Ocean and Coast. Manag.</source> <volume>245</volume>, <fpage>106836</fpage>. <pub-id pub-id-type="doi">10.1016/j.ocecoaman.2023.106836</pub-id>
</mixed-citation>
</ref>
<ref id="B9">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Chu</surname>
<given-names>Z.</given-names>
</name>
<name>
<surname>Yan</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>S.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>Vessel turnaround time prediction: a machine learning approach</article-title>. <source>Ocean and Coast. Manag.</source> <volume>249</volume>, <fpage>107021</fpage>. <pub-id pub-id-type="doi">10.1016/j.ocecoaman.2024.107021</pub-id>
</mixed-citation>
</ref>
<ref id="B10">
<mixed-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Cunningham</surname>
<given-names>S.</given-names>
</name>
</person-group> (<year>2021</year>). <source>Causal inference: the mixtape</source>. <publisher-loc>New Haven, CT</publisher-loc>: <publisher-name>Yale University Press</publisher-name>. <pub-id pub-id-type="doi">10.2307/j.ctv1c29t27</pub-id>
</mixed-citation>
</ref>
<ref id="B11">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Di Gangi</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Belcore</surname>
<given-names>O. M.</given-names>
</name>
<name>
<surname>Polimeni</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>2026</year>). <article-title>Spatial-temporal simulation of routes connecting containers ports</article-title>. <source>Comput. Sci. Its Appl.</source> <volume>2025</volume>, <fpage>167</fpage>&#x2013;<lpage>180</lpage>. <pub-id pub-id-type="doi">10.1007/978-3-031-97660-5_13</pub-id>
</mixed-citation>
</ref>
<ref id="B12">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Ducruet</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Itoh</surname>
<given-names>H.</given-names>
</name>
</person-group> (<year>2022</year>). <article-title>Spatial network analysis of container port operations: the case of ship turnaround times</article-title>. <source>Netw. Spatial Econ.</source> <volume>22</volume> (<issue>4</issue>), <fpage>883</fpage>&#x2013;<lpage>902</lpage>. <pub-id pub-id-type="doi">10.1007/s11067-022-09570-z</pub-id>
</mixed-citation>
</ref>
<ref id="B13">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Eljabu</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Etemad</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Matwin</surname>
<given-names>S.</given-names>
</name>
</person-group> (<year>2023</year>). <article-title>Spatial clustering method of historical AIS data for maritime traffic routes extraction</article-title>. <source>Big Data</source>, <fpage>893</fpage>&#x2013;<lpage>902</lpage>. <pub-id pub-id-type="doi">10.1109/BigData55660.2022.10020646</pub-id>
</mixed-citation>
</ref>
<ref id="B14">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Feng</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Shaw</surname>
<given-names>S. L.</given-names>
</name>
<name>
<surname>Peng</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Fang</surname>
<given-names>Z.</given-names>
</name>
</person-group> (<year>2020</year>). <article-title>Time efficiency assessment of ship movements in maritime ports: a case study of two ports based on AIS data</article-title>. <source>J. Transp. Geogr.</source> <volume>86</volume>, <fpage>102741</fpage>. <pub-id pub-id-type="doi">10.1016/j.jtrangeo.2020.102741</pub-id>
</mixed-citation>
</ref>
<ref id="B15">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Gao</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Zhu</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Zhang</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>He</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Yan</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Yan</surname>
<given-names>B.</given-names>
</name>
</person-group> (<year>2021</year>). <article-title>A novel MP-LSTM method for ship trajectory prediction based on AIS data</article-title>. <source>Ocean. Eng.</source> <volume>228</volume>, <fpage>108956</fpage>. <pub-id pub-id-type="doi">10.1016/j.oceaneng.2021.108956</pub-id>
</mixed-citation>
</ref>
<ref id="B16">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Heilig</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Vo&#xdf;</surname>
<given-names>S.</given-names>
</name>
</person-group> (<year>2017</year>). <article-title>Status quo and innovative approaches for maritime logistics in the age of digitalization: a guest editors&#x2019; introduction</article-title>. <source>Inf. Technol. Manag.</source> <volume>18</volume> (<issue>3</issue>), <fpage>175</fpage>&#x2013;<lpage>177</lpage>. <pub-id pub-id-type="doi">10.1007/s10799-017-0282-z</pub-id>
</mixed-citation>
</ref>
<ref id="B17">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Huang</surname>
<given-names>I.-L.</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>M.-C.</given-names>
</name>
<name>
<surname>Nieh</surname>
<given-names>C.-Y.</given-names>
</name>
<name>
<surname>Huang</surname>
<given-names>J.-C.</given-names>
</name>
</person-group> (<year>2023</year>). <article-title>Ship classification based on AIS data and machine learning methods</article-title>. <source>Electronics</source> <volume>13</volume> (<issue>1</issue>), <fpage>98</fpage>. <pub-id pub-id-type="doi">10.3390/electronics13010098</pub-id>
</mixed-citation>
</ref>
<ref id="B18">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Huang</surname>
<given-names>I.-L.</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>M.-C.</given-names>
</name>
<name>
<surname>Chang</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Huang</surname>
<given-names>J.-C.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>Development and application of an advanced automatic identification system (AIS)-based ship trajectory extraction framework for maritime traffic analysis</article-title>. <source>J. Mar. Sci. Eng.</source> <volume>12</volume>, <fpage>1672</fpage>. <pub-id pub-id-type="doi">10.3390/jmse12091672</pub-id>
</mixed-citation>
</ref>
<ref id="B19">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Jankowski</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Lamm</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Hahn</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>2021</year>). <article-title>Determination of AIS position accuracy and evaluation of reconstruction methods for maritime observation data</article-title>. <source>IFAC-PapersOnLine</source> <volume>54</volume> (<issue>16</issue>), <fpage>97</fpage>&#x2013;<lpage>104</lpage>. <pub-id pub-id-type="doi">10.1016/j.ifacol.2021.10.079</pub-id>
</mixed-citation>
</ref>
<ref id="B20">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Jones</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Koehler</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Jerge</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Graves</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>King</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Dalrymple</surname>
<given-names>R.</given-names>
</name>
<etal/>
</person-group> (<year>2023</year>). <article-title>BATMAN: a brain-like approach for tracking maritime activity and nuance</article-title>. <source>Sensors</source> <volume>23</volume>, <fpage>2424</fpage>. <pub-id pub-id-type="doi">10.3390/s23052424</pub-id>
<pub-id pub-id-type="pmid">36904627</pub-id>
</mixed-citation>
</ref>
<ref id="B21">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kim</surname>
<given-names>H.-S.</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>E.-J.</given-names>
</name>
<name>
<surname>Hyun</surname>
<given-names>J.-W.</given-names>
</name>
<name>
<surname>Gong</surname>
<given-names>I.-Y.</given-names>
</name>
<name>
<surname>Kim</surname>
<given-names>K.</given-names>
</name>
<etal/>
</person-group> (<year>2023</year>). <article-title>A study on grid-cell-type maritime traffic distribution analysis based on AIS data for establishing a coastal maritime transportation network</article-title>. <source>J. Mar. Sci. Eng.</source> <volume>11</volume>, <fpage>354</fpage>. <pub-id pub-id-type="doi">10.3390/jmse11020354</pub-id>
</mixed-citation>
</ref>
<ref id="B22">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kishore</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Pai</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Ghosh</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Pakkan</surname>
<given-names>S.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>Maritime shipping ports performance: a systematic literature review</article-title>. <source>Discov. Sustain.</source> <volume>5</volume>, <fpage>108</fpage>. <pub-id pub-id-type="doi">10.1007/s43621-024-00299-y</pub-id>
</mixed-citation>
</ref>
<ref id="B23">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kolley</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>R&#xfc;ckert</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Kastner</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Jahn</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Fischer</surname>
<given-names>K.</given-names>
</name>
</person-group> (<year>2022</year>). <article-title>Robust berth scheduling using machine learning for vessel arrival time prediction</article-title>. <source>Flexible Serv. Manuf. J.</source> <volume>35</volume>, <fpage>29</fpage>&#x2013;<lpage>69</lpage>. <pub-id pub-id-type="doi">10.1007/s10696-022-09462-x</pub-id>
</mixed-citation>
</ref>
<ref id="B24">
<mixed-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Kraus</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Mohrdieck</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Schwenker</surname>
<given-names>F.</given-names>
</name>
</person-group> (<year>2018</year>). <article-title>Ship classification based on trajectory data with machine-learning methods</article-title>. In: <source>2018 19th International Radar Symposium (IRS)</source>. <publisher-name>Bonn, Germany: IEEE</publisher-name>. <fpage>1</fpage>&#x2013;<lpage>10</lpage>. <pub-id pub-id-type="doi">10.23919/IRS.2018.8448028</pub-id>
</mixed-citation>
</ref>
<ref id="B25">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kruse</surname>
<given-names>C. J.</given-names>
</name>
<name>
<surname>Mitchell</surname>
<given-names>K. N.</given-names>
</name>
<name>
<surname>DiJoseph</surname>
<given-names>P. K.</given-names>
</name>
<name>
<surname>Kang</surname>
<given-names>D. H.</given-names>
</name>
<name>
<surname>Schrank</surname>
<given-names>D. L.</given-names>
</name>
<name>
<surname>Eisele</surname>
<given-names>W. L.</given-names>
</name>
</person-group> (<year>2018</year>). <article-title>Developing and implementing a port fluidity performance measurement methodology using automatic identification system data</article-title>. <source>Transp. Res. Rec.</source> <volume>2672</volume> (<issue>11</issue>), <fpage>30</fpage>&#x2013;<lpage>40</lpage>. <pub-id pub-id-type="doi">10.1177/0361198118796353</pub-id>
</mixed-citation>
</ref>
<ref id="B26">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kweon</surname>
<given-names>S. J.</given-names>
</name>
<name>
<surname>Hwang</surname>
<given-names>S. W.</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Jo</surname>
<given-names>M. J.</given-names>
</name>
</person-group> (<year>2022</year>). <article-title>Demurrage pattern analysis using logical analysis of data: a case study of the Ulsan port authority</article-title>. <source>Expert Syst. Appl.</source> <volume>206</volume>, <fpage>117745</fpage>. <pub-id pub-id-type="doi">10.1016/j.eswa.2022.117745</pub-id>
</mixed-citation>
</ref>
<ref id="B27">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Lee</surname>
<given-names>J. S.</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>H. T.</given-names>
</name>
<name>
<surname>Cho</surname>
<given-names>I. S.</given-names>
</name>
</person-group> (<year>2022</year>). <article-title>Maritime traffic route detection framework based on statistical density analysis from AIS data using a clustering algorithm</article-title>. <source>IEEE Access</source> <volume>10</volume>, <fpage>23355</fpage>&#x2013;<lpage>23366</lpage>. <pub-id pub-id-type="doi">10.1109/ACCESS.2022.3154363</pub-id>
</mixed-citation>
</ref>
<ref id="B28">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Liang</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Zhi-hao</surname>
<given-names>Z.</given-names>
</name>
<name>
<surname>Yuan-qiao</surname>
<given-names>W. E. N.</given-names>
</name>
<name>
<surname>Man</surname>
<given-names>Z. H. U.</given-names>
</name>
<name>
<surname>Ya-min</surname>
<given-names>H.</given-names>
</name>
</person-group> (<year>2021</year>). <article-title>Stopping behavior recognition and classification of ship based on trajectory characteristics</article-title>. <source>J. Traffic Transp. Eng.</source> <volume>21</volume> (<issue>5</issue>), <fpage>189</fpage>&#x2013;<lpage>198</lpage>. <pub-id pub-id-type="doi">10.19818/j.cnki.1671-1637.2021.05.016</pub-id>
</mixed-citation>
</ref>
<ref id="B29">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Meng</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Ge</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Yan</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Han</surname>
<given-names>C.</given-names>
</name>
</person-group> (<year>2023</year>). <article-title>Optimization of ship routing and allocation in a container transport network considering port congestion: a variational inequality model</article-title>. <source>Ocean Coast. Manag.</source> <volume>244</volume>, <fpage>106798</fpage>. <pub-id pub-id-type="doi">10.1016/j.ocecoaman.2023.106798</pub-id>
</mixed-citation>
</ref>
<ref id="B30">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Molavi</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Lim</surname>
<given-names>G. J.</given-names>
</name>
<name>
<surname>Race</surname>
<given-names>B.</given-names>
</name>
</person-group> (<year>2020</year>). <article-title>A framework for building a smart port and smart port index</article-title>. <source>Int. J. Sustain. Transp.</source> <volume>14</volume> (<issue>9</issue>), <fpage>686</fpage>&#x2013;<lpage>700</lpage>. <pub-id pub-id-type="doi">10.1080/15568318.2019.1610919</pub-id>
</mixed-citation>
</ref>
<ref id="B31">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Musolino</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Panuccio</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Rindone</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Russo</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Vitetta</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>2026a</year>). <article-title>National and local factors affecting ship time in container ports: system of models at country and port levels</article-title>. <source>Lect. Notes Comput. Sci.</source> <volume>15897</volume> (<issue>LNCS</issue>), <fpage>144</fpage>&#x2013;<lpage>155</lpage>. <pub-id pub-id-type="doi">10.1007/978-3-031-97660-5_11</pub-id>
</mixed-citation>
</ref>
<ref id="B32">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Musolino</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Ped&#xe0;</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Russo</surname>
<given-names>F.</given-names>
</name>
</person-group> (<year>2026b</year>). <article-title>ICT factors affecting ship times in container ports: experimental analysis at country level</article-title>. <source>Lect. Notes Comput. Sci.</source> <volume>15897</volume>, <fpage>131</fpage>&#x2013;<lpage>143</lpage>. <pub-id pub-id-type="doi">10.1007/978-3-031-97660-5_10</pub-id>
</mixed-citation>
</ref>
<ref id="B33">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Nguyen</surname>
<given-names>V.</given-names>
</name>
<name>
<surname>Im</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>S.</given-names>
</name>
</person-group> (<year>2015</year>). <article-title>The interpolation method for the missing AIS data of ship</article-title>. <source>J. Navigation Port Res.</source> <volume>39</volume>, <fpage>377</fpage>&#x2013;<lpage>384</lpage>. <pub-id pub-id-type="doi">10.5394/KINPR.2015.39.5.377</pub-id>
</mixed-citation>
</ref>
<ref id="B34">
<mixed-citation publication-type="book">
<collab>NOOA</collab> (<year>2025</year>). <source>Marine cadastre hub</source>. <comment>Washington, DC, United States. Available online at: <ext-link ext-link-type="uri" xlink:href="https://hub.marinecadastre.gov/">https://hub.marinecadastre.gov/</ext-link>.</comment>
</mixed-citation>
</ref>
<ref id="B35">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Notteboom</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Haralambides</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Cullinane</surname>
<given-names>K.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>The Red Sea crisis: ramifications for vessel operations, shipping networks, and maritime supply chains</article-title>. <source>Marit. Econ. Logist.</source> <volume>26</volume> (<issue>1</issue>), <fpage>1</fpage>&#x2013;<lpage>20</lpage>. <pub-id pub-id-type="doi">10.1057/s41278-024-00287-z</pub-id>
</mixed-citation>
</ref>
<ref id="B36">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Odeck</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Sch&#xf8;yen</surname>
<given-names>H.</given-names>
</name>
</person-group> (<year>2020</year>). <article-title>Productivity and convergence in Norwegian container seaports: an SFA-based malmquist productivity index approach</article-title>. <source>Transp. Res.</source> <volume>137</volume>, <fpage>222</fpage>&#x2013;<lpage>239</lpage>. <pub-id pub-id-type="doi">10.1016/j.tra.2020.05.001</pub-id>
</mixed-citation>
</ref>
<ref id="B37">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Peng</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Lu</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Cheng</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Mou</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>R.</given-names>
</name>
</person-group> (<year>2018</year>). <article-title>Modelling the competitiveness of the ports along the maritime silk road with big data</article-title>. <source>Transp. Res.</source> <volume>118</volume>, <fpage>852</fpage>&#x2013;<lpage>867</lpage>. <pub-id pub-id-type="doi">10.1016/j.tra.2018.10.041</pub-id>
</mixed-citation>
</ref>
<ref id="B38">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Peng</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Bai</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Yuen</surname>
<given-names>K. F.</given-names>
</name>
<name>
<surname>Wu</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2023</year>). <article-title>A deep learning approach for port congestion estimation and prediction</article-title>. <source>Marit. Policy Manag.</source> <volume>50</volume> (<issue>7</issue>), <fpage>835</fpage>&#x2013;<lpage>860</lpage>. <pub-id pub-id-type="doi">10.1080/03088839.2022.2057608</pub-id>
</mixed-citation>
</ref>
<ref id="B39">
<mixed-citation publication-type="book">
<collab>Port of Los Angeles</collab> (<year>2023</year>). <source>2023 port of Los Angeles container statistics &#x7c; container statistics &#x7c; port of Los Angeles</source>. <comment>CA, United States. Available online at: <ext-link ext-link-type="uri" xlink:href="https://www.portoflosangeles.org/business/statistics/container-statistics/historical-teu-statistics-2023">https://www.portoflosangeles.org/business/statistics/container-statistics/historical-teu-statistics-2023</ext-link>.</comment>
</mixed-citation>
</ref>
<ref id="B40">
<mixed-citation publication-type="book">
<collab>Port of Los Angeles</collab> (<year>2025</year>). <source>Container statistics &#x7c; port of Los Angeles</source>. <comment>CA, United States. Available online at: <ext-link ext-link-type="uri" xlink:href="https://www.portoflosangeles.org/business/statistics/container-statistics">https://www.portoflosangeles.org/business/statistics/container-statistics</ext-link>.</comment>
</mixed-citation>
</ref>
<ref id="B41">
<mixed-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Rajabi</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Khodadad Saryazdi</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Belfkih</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Duvallet</surname>
<given-names>C.</given-names>
</name>
</person-group> (<year>2018</year>). <article-title>Towards smart port: an application of AIS data</article-title>. In: <conf-name>2018 IEEE 20th international conference on high performance computing and communications; IEEE 16th international conference on smart City; IEEE 4th international conference on data science and systems (HPCC/SmartCity/DSS)</conf-name>, <fpage>1414</fpage>&#x2013;<lpage>1421</lpage>. <pub-id pub-id-type="doi">10.1109/HPCC/SmartCity/DSS.2018.00234</pub-id>
</mixed-citation>
</ref>
<ref id="B42">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Ribeiro</surname>
<given-names>C. V.</given-names>
</name>
<name>
<surname>Paes</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Oliveira</surname>
<given-names>D. de.</given-names>
</name>
</person-group> (<year>2023</year>). <article-title>AIS-based maritime anomaly traffic detection: a review</article-title>. <source>Expert Syst. Appl.</source> <volume>231</volume>, <fpage>120561</fpage>. <pub-id pub-id-type="doi">10.1016/j.eswa.2023.120561</pub-id>
</mixed-citation>
</ref>
<ref id="B43">
<mixed-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Rindone</surname>
<given-names>C.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>State of the art of factors affecting times of ships in container ports: AIS data for building a transport supply network</article-title>. in: <conf-name>Conference ICCSA 2024: computational science and its applications</conf-name>.</mixed-citation>
</ref>
<ref id="B44">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Russo</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Musolino</surname>
<given-names>G.</given-names>
</name>
</person-group> (<year>2021</year>). <article-title>The role of emerging ICT in the ports: increasing utilities according to shared decisions</article-title>. <source>Front. Future Transp.</source> <volume>2</volume>, <fpage>722812</fpage>. <pub-id pub-id-type="doi">10.3389/ffutr.2021.722812</pub-id>
</mixed-citation>
</ref>
<ref id="B45">
<mixed-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Russo</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Musolino</surname>
<given-names>G.</given-names>
</name>
</person-group> (<year>2022</year>). <article-title>Emerging ICT in port operations: case studies</article-title>. in: <source>Trends in maritime technology and engineering</source>. <publisher-loc>Boca Raton, FL</publisher-loc>: <publisher-name>CRC Press</publisher-name>.</mixed-citation>
</ref>
<ref id="B46">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Russo</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Musolino</surname>
<given-names>G.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>Transportation system models to analyse ports competition and cooperation</article-title>. <source>WMU J. Marit. Aff.</source> <volume>23</volume> (<issue>3</issue>), <fpage>393</fpage>&#x2013;<lpage>413</lpage>. <pub-id pub-id-type="doi">10.1007/s13437-024-00345-6</pub-id>
</mixed-citation>
</ref>
<ref id="B47">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Russo</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Ped&#xe0;</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Musolino</surname>
<given-names>G.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>Attributes influencing port times of container ships</article-title>. <source>WMU J. Marit. Aff.</source> <volume>23</volume>, <fpage>375</fpage>&#x2013;<lpage>392</lpage>. <pub-id pub-id-type="doi">10.1007/s13437-024-00336-7</pub-id>
</mixed-citation>
</ref>
<ref id="B48">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Sahoo</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Song</surname>
<given-names>D.-W.</given-names>
</name>
</person-group> (<year>2022</year>). <article-title>Recent patterns of competition and Co-operation among major container ports in Asia: an implication for Busan</article-title>. <source>Int. J. Marit. Aff. Fish.</source> <volume>14</volume>, <fpage>1</fpage>&#x2013;<lpage>28</lpage>. <pub-id pub-id-type="doi">10.54007/ijmaf.2022.14.1.1</pub-id>
</mixed-citation>
</ref>
<ref id="B49">
<mixed-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Shuo</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Jian</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Ruoxi</surname>
<given-names>Z.</given-names>
</name>
</person-group> (<year>2016</year>). <article-title>The analysis of the necessity of constructing the huizhou &#x2018;Smart Port&#x2019; and overall framework</article-title>. in: <conf-name>2016 international conference on intelligent transportation, big data and smart City (ICITBS)</conf-name>, <fpage>159</fpage>&#x2013;<lpage>162</lpage>. <pub-id pub-id-type="doi">10.1109/ICITBS.2016.15</pub-id>
</mixed-citation>
</ref>
<ref id="B50">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Smith</surname>
<given-names>D.</given-names>
</name>
</person-group> (<year>2021</year>). <article-title>Big data insights into container vessel dwell times</article-title>. <source>Transp. Res. Rec</source> <volume>2675</volume>, <fpage>1222</fpage>&#x2013;<lpage>1235</lpage>. <pub-id pub-id-type="doi">10.1177/03611981211015248</pub-id>
</mixed-citation>
</ref>
<ref id="B51">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Song</surname>
<given-names>Z. Y.</given-names>
</name>
<name>
<surname>Lin</surname>
<given-names>C. W.</given-names>
</name>
<name>
<surname>Feng</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>P. T.-W.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>An empirical study of the performance of the sixth generation ports model with smart ports with reference to major container ports in mainland China</article-title>. <source>Transp. Res.</source> <volume>184</volume>, <fpage>103460</fpage>. <pub-id pub-id-type="doi">10.1016/j.tre.2024.103460</pub-id>
</mixed-citation>
</ref>
<ref id="B52">
<mixed-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Spadon</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Kumar</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Smith</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Hilliard</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Vela</surname>
<given-names>S.</given-names>
</name>
<etal/>
</person-group> (<year>2024</year>). <source>Maritime tracking data analysis and integration with AISdb</source>. <pub-id pub-id-type="doi">10.1016/j.softx.2024.101952</pub-id>
</mixed-citation>
</ref>
<ref id="B53">
<mixed-citation publication-type="book">
<collab>United Nations Conference on Trade and Development</collab> (<year>2024</year>). <source>Review of maritime transport 2024</source>. <publisher-name>Geneve (CH): United Nations Publications</publisher-name>.</mixed-citation>
</ref>
<ref id="B54">
<mixed-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Wijaya</surname>
<given-names>W. M.</given-names>
</name>
<name>
<surname>Nakamura</surname>
<given-names>Y.</given-names>
</name>
</person-group> (<year>2024</year>). <source>Port performance indicators construction based on the AIS-generated trajectory segmentation and classification</source>. <pub-id pub-id-type="doi">10.1007/s41060-024-00614-w</pub-id>
</mixed-citation>
</ref>
<ref id="B55">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Wolsing</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Roepert</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Bauer</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Wehrle</surname>
<given-names>K.</given-names>
</name>
</person-group> (<year>2022</year>). <article-title>Anomaly detection in maritime AIS tracks: a review of recent approaches</article-title>. <source>J. Mar. Sci. Eng.</source> <volume>10</volume> (<issue>1</issue>), <fpage>112</fpage>. <pub-id pub-id-type="doi">10.3390/jmse10010112</pub-id>
</mixed-citation>
</ref>
<ref id="B56">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Xin</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Pan</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Yan</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Ai</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Zhang</surname>
<given-names>Q.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>Graph deep learning recognition of port ship behavior patterns from a network approach</article-title>. <source>Ocean. Eng.</source> <volume>305</volume>, <fpage>117921</fpage>. <pub-id pub-id-type="doi">10.1016/j.oceaneng.2024.117921</pub-id>
</mixed-citation>
</ref>
<ref id="B57">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Xu</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Peng</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Lu</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Claramunt</surname>
<given-names>C.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>Uncovering the multiplex network of global container shipping: insights from shipping companies</article-title>. <source>J. Transp. Geogr.</source> <volume>120</volume>, <fpage>103991</fpage>. <pub-id pub-id-type="doi">10.1016/j.jtrangeo.2024.103991</pub-id>
</mixed-citation>
</ref>
<ref id="B58">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Yan</surname>
<given-names>Z.</given-names>
</name>
<name>
<surname>Xiao</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Cheng</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>He</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Ruan</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Zhou</surname>
<given-names>X.</given-names>
</name>
<etal/>
</person-group> (<year>2020</year>). <article-title>Exploring AIS data for intelligent maritime routes extraction</article-title>. <source>Appl. Ocean Res.</source> <volume>101</volume>, <fpage>102271</fpage>. <pub-id pub-id-type="doi">10.1016/j.apor.2020.102271</pub-id>
</mixed-citation>
</ref>
<ref id="B59">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Yan</surname>
<given-names>Z.</given-names>
</name>
<name>
<surname>Cheng</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>He</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>H.</given-names>
</name>
</person-group> (<year>2022</year>). <article-title>Extracting ship stopping information from AIS data</article-title>. <source>Ocean. Eng.</source> <volume>250</volume>, <fpage>111004</fpage>. <pub-id pub-id-type="doi">10.1016/j.oceaneng.2022.111004</pub-id>
</mixed-citation>
</ref>
<ref id="B60">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Yue</surname>
<given-names>Z.</given-names>
</name>
<name>
<surname>Mangan</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2023</year>). <article-title>A framework for understanding reliability in container shipping networks</article-title>. <source>Marit. Econ. Logist.</source> <volume>26</volume>, <fpage>523</fpage>&#x2013;<lpage>544</lpage>. <pub-id pub-id-type="doi">10.1057/s41278-023-00269-7</pub-id>
</mixed-citation>
</ref>
<ref id="B61">
<mixed-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Zhang</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>He</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Tang</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Mou</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Gong</surname>
<given-names>S.</given-names>
</name>
</person-group> (<year>2018</year>). <article-title>A novel method for reconstruct ship trajectory using raw AIS data</article-title>. In: <conf-name>2018 3rd IEEE international conference on intelligent transportation engineering (ICITE)</conf-name>, <fpage>192</fpage>&#x2013;<lpage>198</lpage>. <pub-id pub-id-type="doi">10.1109/ICITE.2018.8492619</pub-id>
</mixed-citation>
</ref>
<ref id="B62">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Zhang</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Meng</surname>
<given-names>Q.</given-names>
</name>
<name>
<surname>Fang Fwa</surname>
<given-names>T.</given-names>
</name>
</person-group> (<year>2019</year>). <article-title>Big AIS data based spatial-temporal analyses of ship traffic in Singapore port waters</article-title>. <source>Transp. Res. Part E Logist. Transp. Rev.</source> <volume>129</volume>, <fpage>287</fpage>&#x2013;<lpage>304</lpage>. <pub-id pub-id-type="doi">10.1016/j.tre.2017.07.011</pub-id>
</mixed-citation>
</ref>
<ref id="B63">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Ziran</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Xu</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Li</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Jiang</surname>
<given-names>Z.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>The application of artificial intelligence technology in shipping: a bibliometric review</article-title>. <source>J. Mar. Sci. Eng.</source> <volume>12</volume>, <fpage>624</fpage>. <pub-id pub-id-type="doi">10.3390/jmse12040624</pub-id>
</mixed-citation>
</ref>
</ref-list>
</back>
</article>