--- title: "TMS 7.11 Container Tracking" slug: "tms-711-container-tracking" tags: ["7.11", "Compiled from User Guide", "Container Tracking", "Admin", "End User", "Load Tracking"] updated: 2024-06-28T20:25:14Z published: 2024-06-28T20:25:14Z canonical: "documents.revenova.com/tms-711-container-tracking" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revenova.com/llms.txt > Use this file to discover all available pages before exploring further. # TMS 7.11 Container Tracking ## Overview ## **Container Tracking** Containers can be associated with loads and also tracked via the Project44 Unified Tracking API. ### **Container Tracking Setup** 1. Two tables – **Container** and **Container Console Configuration** – support container tracking. Provide CRUD access to these tables as appropriate, and add the **Container Console tab** access as appropriate. 2. There is also a **Containers tab** for bulk actions on container records. 3. Add every port that might be a port of load or port of discharge as an account with **TMS Type** of **Seaport**. Make sure to enter the **Timezone** and **UN Location Code** for each port. 4. If there are any missing time zones add them to the **Timezones** picklist value set. Use the **IANA time zone codes** only. 5. Note that accounts of type **Seaport** refer to the generic seaport in question. Accounts of type **Seaport Terminal** refer to actual locations within the port that dray drivers will be directed to. 6. Add the **Containers related list** to the Load page with a mode-based visibility filter. 7. Add to the page and check the **Show Containers on Load Creation** checkbox for each **Mode** record that requires container data entry during load creation. 8. Populate the following **Container Field Sets** as appropriate: 1. **TMS1** – Default Container fields entered during load creation. 2. **TMS2** – Default Container fields that appear on documents. 9. You can create **mode-specific versions of these field sets**. Name them by concatenating the mode name to the field set name. For example, “ **TMS1_Truckload**”. 10. The **Load Map** component includes a “Show Containers” icon button and breadcrumb map when a load has containers associated with it. 11. From **TMS Admin 🡪 Credentials** enter credentials for the **Project44 Tracking API (Unified Tracking API)**. 12. Note that the **webhook URL** for Unified Tracking is automatically provided in the code. You also need to alert P44 to the webhook as they have to provision it on their side. 13. Container date, time, and status updates are provided via the API “push” mechanism. 14. Note that the following .PDF documents support an optional **Containers section**: 1. Customer Rate and Load Confirmation 2. Carrier RFQ 3. Carrier Rate and Load Confirmation 4. Driver Load Confirmation ### **To start tracking a container:** 1. A valid **Container Number, Booking Number, or Master Bill of Lading Number,** and **SCAC** must be provided. 2. Change the **Tracking** field to **On** and save the record. 3. The **Queued Transaction Job** will initiate the tracking session with **Project44**. 4. The Container **Tracking Provider** and **Tracking Number** fields will be populated if the tracking session is properly initiated. 5. **Container status updates** arrive via the “push” API mechanism. 6. Note that **container tracking is independent of load tracking**. For example, you may track (via Project44) the container from Port of Hong Kong to Port of Long Beach, and then track the (dray) load from Port of Long beach to the Consignee using Macropoint. 7. Change the **Tracking** field to **Off** to terminate tracking on a container.