Miami Cargo Community System: Rollout and Shipment Handoff Checks

01 / Verified announcement

A common portal for an airport community

MIA's official announcement identifies Kalé as the developer of its Airport Cargo Community System, or ACCS. It describes a shared online portal linking forwarders, truckers, carriers and cargo-handling businesses. The stated aims include better information exchange, advance planning and truck scheduling.

The announcement was made at TIACA's Air Cargo Forum in Miami on 27 October. The airport says its cargo operation involves more than 1,600 truck trips per day. That makes the ground-side exchange of release information and collection plans relevant to shipment execution, alongside the flight itinerary.

The airport presents reduced waiting, operating costs and emissions as potential benefits of adoption. Those are expected outcomes, not measured results from a completed airport-wide rollout.

02 / Implementation status

Launch publicity does not mean every handoff is already connected

Independent reporting by FreightWaves on the same day provides important implementation detail. Kalé's chief executive told the publication that community workshops would begin in January, followed by implementation over 18 months. Electronic document sharing and truck-traffic management are described as the starting point.

The report also describes a system intended to connect with participants' existing systems through interfaces. It does not establish that every handler is connected today, that each function is already available, or that a shipper can replace existing release instructions immediately.

For planning purposes, treat the announcement as a programme to follow. Ask the responsible local forwarder or handling agent for confirmed onboarding dates and the process applying to the particular shipment.

03 / Shipper implications

Confirm four handoffs before changing a collection plan

The following checks are operational implications of a shared platform, not additional commitments made by MIA or Kalé:

• Identify the participating parties. Record the airline, handler, forwarder, broker and collecting haulier. Establish which can exchange information through the new system and which still require their existing channel.
• Define what “ready” means. A shipment's arrival, customs clearance, handler release and booked truck slot are separate milestones. Ask which status permits collection and who confirms it.
• Agree document ownership. Confirm who supplies the air waybill references, release authority and pickup details, and how a correction reaches the next party. Re-entering inconsistent data into several systems can undermine the value of a common portal.
• Keep a fallback and a cost record. Agree whom the driver should contact if a status or appointment cannot be retrieved. Compare waiting and handling charges using the same shipment scope before attributing savings to the platform.

For time-sensitive goods, an earlier flight arrival only helps if release and collection follow in time. Build the air-freight handoff plan around the receiving facility's hours, the cargo's handling requirements and the confirmed local process.

Keep commercial assumptions separate from system capability

The announcement does not change a sales contract, customs obligation or agreed delivery responsibility. Buyers should retain their documented arrival and delivery windows until the parties confirm a workable process. A common information platform can support coordination; it does not by itself guarantee clearance, capacity or an on-time delivery.