Port gate automation: lanes, weighbridges, data flow and what to specify

What is port gate automation at the system level?

Most writing on port gates asks one question: ANPR or RFID? Our note on ANPR vs RFID answers that. This page looks at everything around the readers: how many lanes, what sits in each lane, where the weighbridge goes, where the data goes, and what happens when a check fails.

Think of the gate as two layers. The lane layer is the equipment a truck drives past: readers, cameras, a weighbridge, a barrier and a display. The system layer is the software that turns those reads into one gate transaction, checks it against a booking or pass, and sends it to the terminal, the port and customs.

A gate can have good cameras and still fail. Common causes are too few exception lanes, a weighbridge that is not verified, or a transaction that never reaches the terminal operating system (TOS). The sections below cover each of these.

What equipment sits in one gate lane?

A full truck lane at a container gate usually has the devices below. Not every lane needs all of them. A lane for two-wheelers or staff needs far less than a lane for laden export trucks.

How should gate lanes be laid out?

Start from traffic types, not from a lane count. Kamarajar Port's gate system covers the entry and exit of a two-wheeler lane, a main lane and an ODC (over-dimensional cargo) lane at its new gate complex, plus its truck pre-parking yard. Each type has its own speed, its own checks and its own failure points.

A pre-parking or holding yard takes queueing off the public road. It also lets the port check a truck before it reaches the terminal gate. Kamarajar Port reports that after it added RFID and ANPR at the truck pre-parking yard, trailer movement from the yard to the container terminal fell from 10 minutes to 2 minutes.

Plan where failed trucks go. Without a separate lane for trucks that fail a check, a single truck with a missing pass blocks every truck behind it.

• Separate in and out lanes, so a backlog on one side does not stop the other
• At least one staffed exception lane at each gate, reachable without reversing
• A lane wide and high enough for ODC, kept clear of fixed OCR gantries
• A queue length inside the port or holding yard sized for the peak hour
• Room for a customs e-seal reader and for under vehicle scanning where security asks for it

Where does the weighbridge fit, and what do VGM and Legal Metrology require?

The weighbridge is the gate device with the clearest legal weight. Amendments to SOLAS regulation VI/2 entered into force on 1 July 2016. Since then, IMO says, "the verified gross mass is a condition for loading a packed container onto a ship." The shipper is responsible for it. The shipper can weigh the packed container, or weigh all the contents and add the container's tare mass.

The terminal can step in. IMO's guidelines (MSC.1/Circ.1475) say that when a container arrives without a verified gross mass, the master and the terminal representative "may obtain the verified gross mass of the packed container on behalf of the shipper. This may be done by weighing the packed container in the terminal or elsewhere." Who pays is left to the commercial parties. A gate weighbridge is one place to do this weighing.

The equipment has to meet local law. Paragraph 7.1 of the guidelines says the weighbridge "should meet the applicable accuracy standards and requirements of the State in which the equipment is being used." In India that means the Legal Metrology (General) Rules, 2011.

Those rules changed on 3 July 2026. G.S.R. 568(E) says that when instruments are tested at the place of use, a constant load may replace some standard weights, but standard weights of "not less than one half of the maximum capacity" must be used. If the repeatability error is no more than 0.3e, that drops to one third of capacity. If it is no more than 0.2e, it drops to one fifth. This reduces the standard weights needed to test a large weighing instrument on site. A gate RFP should still ask the bidder to show the weighbridge's verification, not just its rated accuracy.

How does gate data reach the TOS, the PCS and customs?

Each truck visit should end as one gate transaction record. It holds the time, the lane, the tag, the plate and its image, the driver, the container number, the weight, the seal status and the decision. The TOS uses it to plan the yard move. The port uses it for passes and charges.

The container number has to be right before it is sent. ISO 6346 covers the coding, identification and marking of containers. As the Bureau International des Containers (BIC) describes it, the number ends in a check digit that provides "a means of validating the recording and transmission accuracies of the owner code and serial number." BIC also says the characters must be at least 100 mm high. That figure helps set camera resolution and mounting distance for OCR. The category letter is U for freight containers and Z for trailers and chassis, so the system can tell a box from a chassis read.

Customs runs a parallel check. Circular 41/2017-Customs says that once a self-sealed container's RFID e-seal "is read as intact or not tampered", there is no need to examine it unless there is good reason or intelligence. Full containers that arrive without e-seals go to a CFS or are allowed direct port entry, under the usual risk management. Vendors may supply fixed readers "in consultation with custodians at Ports and ICDs" or handheld ones, and the web application must record where each e-seal was read. The circular describes these as readers that the vendor "shall provide to customs". So the gate design should give them their own space and network link, agreed with customs and the custodian.

What happens when a gate check fails?

Throughput is set by the exceptions, not the clean trucks. A clean truck passes in seconds. A truck with a tag-plate mismatch, an unreadable container number, a broken seal, an overweight reading or no booking needs a person. The system should send each type to the right place and log who cleared it.

Clock sync and logs tie it together. CERT-In's directions of 28 April 2022 require organisations to sync all ICT system clocks to the NTP servers of NIC or NPL, or to servers traceable to them. They also require logs of all ICT systems to be kept for "a rolling period of 180 days" within India, and listed incidents to be reported within 6 hours. If the ANPR camera, OCR server and weighbridge disagree on the time, an image cannot be matched to a weight after an incident.

• Tag and plate do not match: hold at the barrier, send to the exception lane, alert security
• Container number fails the check digit: re-read, then manual entry with the image kept
• E-seal reads as tampered: hand over to customs; the container leaves the e-seal procedure
• No verified gross mass: weigh at the gate if the terminal offers it, as agreed with the shipper
• No booking or pass: send to the exception lane and tell the transporter why
• Network or TOS link down: a written fallback mode, with every manual opening logged

What should a port gate RFP specify?

Our ANPR vs RFID note lists what to write for identification accuracy. The items below cover the rest of the gate system.

• Lane types and counts by direction: truck, ODC, two-wheeler and staff, plus exception lanes and any pre-parking yard
• Peak-hour design volume per lane, and the seconds per clean truck the bidder must prove on site
• The gate transaction record: every field, its format, and which system receives it
• Named interfaces to the TOS, the port's pass and billing systems, the PCS where used, CCTV and the command centre
• Container OCR with an ISO 6346 check-digit test on every read, and an image kept for each read
• Weighbridge capacity, Legal Metrology verification at handover and on schedule, and the VGM workflow if the terminal weighs for shippers
• Space, power and network for the e-seal readers vendors provide to customs, agreed with customs and the custodian
• Exception handling for each failure type, with an audit log of every manual override
• Time sync to NIC or NPL for every camera, reader, weighbridge and server, and logs kept 180 days in India
• Degraded modes: what each lane does when power, network or a central system fails, and the barrier's fail-safe state

How Ahuva approaches port gate systems

Ports and maritime is one of the sectors Ahuva serves. Its access control line covers smart card, biometric and mobile credentials, turnstiles, boom barriers and visitor management, integrated with CCTV. Its surveillance line covers IP surveillance, AI/ML analytics and ANPR on a centralised VMS. Zebra is among its OEM partners for auto-ID, RFID and industrial scanning.