Configuring Dashboard Columns
Last updated: July 30, 2025
OpenTug collects, ingests, and generates a significant amount of data for each voyage, including information from GPS trackers, AIS data, carrier traffic reports, lock delay, river flood level, weather, and system-generated events. This data powers real-time visibility, historical reporting, and automated workflows across the inland and coastal marine logistics ecosystem.
To make this data actionable, it’s critical to configure the Voyage Dashboard columns to reflect your operational priorities. Whether you're focused on dispatching, monitoring customer load and discharge activity, tracking fleet positioning, or reconciling voyage completion, each column can be tailored to highlight the data that matters most to your workflow.
The following section breaks down each dashboard column and its purpose to help you optimize your view for decision-making and efficiency.
Column Header | Description | Data Source | Editable in Dashboard |
Name | Unique voyage identifier, often formatted as "Barge" + some value from the traffic report if there is no specific voyage identifier given. | Traffic | No |
Load Port | Port where the cargo is loaded onto the barge. | Traffic | No |
Discharge Port | Port where the cargo is discharged from the barge. | Traffic | No |
Current Position | The last known position based on AIS/GPS or reported traffic location. | Traffic | No |
Notes | Manually entered freeform notes. | User | Yes |
Customer Assignment Date | Date when the customer assignment was officially logged to the voyage. | User | Yes |
Voyage Status | General lifecycle status of the voyage (e.g., Scheduled, In Transit, Completed). | OpenTug | No |
Carrier Status | Status update from the carrier | Traffic | No |
Carrier Name | Carrier responsible for operating or managing the voyage. | Traffic | No |
Tugs | Tugboat(s) assigned to the voyage, if applicable. | Traffic | Yes |
Barges | Barge(s) assigned to the voyage. | Traffic | Yes |
Load Laycan Start | Start date for the window in which loading is scheduled to occur. | Traffic | No |
Load Laycan End | End date for the window in which loading is scheduled to occur. | Traffic | No |
Product | Type of cargo or product being transported (e.g., CPP, grain, chemicals). | Traffic | No |
Load State | Current state of the load (e.g., Loading, Loaded, Awaiting Load). | Traffic | No |
Actual Load Arrival | Actual timestamp when the barge arrived at the load port. | OpenTug | No |
Time Completed | Timestamp when the entire voyage is considered complete.
| OpenTug | No |
Discharge Laycan Start | Start date for the window in which discharging is scheduled to occur. The laycan field is typically used for shippers that send out official voyage orders. If traffic reports alone are used for voyage ingestion, this field may be picked up from load date or defaulted to the date the report was ingested. | Traffic | No |
Discharge Laycan End | End date for the window in which discharging is scheduled to occur. | Traffic | No |
Actual Discharge Arrival | Actual timestamp when the barge arrived at the discharge port. | OpenTug | No |
ETA | Estimated time of arrival at the next port or waypoint. | OpenTug | No |
ETA Provided by Carrier | ETA reported by the carrier, may differ from system-calculated ETA. | Traffic | No |
Current Position | The last known position based on AIS/GPS or reported traffic location. | OpenTug | No |
Reported Location | Latest location provided in a carrier traffic report. | Traffic | No |
Tendered Load Reported | Date/time when barge was first reported as tendered at load port. | Traffic | No |
Load Start Reported | Date/time when loading began. | Traffic | No |
Load End Reported | Date/time when loading was completed. | Traffic | No |
Load Release Reported | Date/time when barge was released from the load port. | Traffic | No |
Tendered Discharge Reported | Date/time when barge was tendered at discharge port. | Traffic | No |
Discharge Start Reported | Date/time when discharge began. | Traffic | No |
Discharge End Reported | Date/time when discharge was completed. | Traffic | No |
Discharge Release Reported | Date/time when barge was released from discharge port. | Traffic | No |
Last Traffic Update | Timestamp of the last received traffic report update. | Traffic | No |
Charterer Name | Customer listed as the charterer for the voyage. | User | Yes |
Assets | Assets assigned to the voyage, often includes barge/tug IDs. | Traffic | Yes |
On-Hire Port | Port where the charter period officially began. | Traffic | No |
On-Hire Laycan | Laycan window for on-hire (charter start) period. | Traffic | No |
Off-Hire Port | Port where the charter period officially ends. | Traffic | No |
Off-Hire Laycan | Laycan window for off-hire (charter end) period. | Traffic | No |
Current Location | Parsed location name from traffic reports or GPS location. | OpenTug | No |
Demurrage Days Incurred | Number of days demurrage charges have accumulated. | OpenTug | No |
Free Days Remaining | Number of remaining free days before demurrage applies. | OpenTug | No |
Demurrage Incurred | Total amount of demurrage accrued in dollars. | OpenTug | No |
Total Demurrage Per Day | Daily rate charged for demurrage. | OpenTug | No |
Prior Cargo | Description of the cargo previously carried in this barge. | Traffic | No |
Cleaning Required Type | Cleaning requirements based on prior cargo (e.g., hot wash, caustic). | Traffic | No |
Rate | Contracted or quoted freight rate for the voyage. | OpenTug | No |
Number of Legs | Number of distinct voyage segments (legs) tracked. | OpenTug | No |
Reporting | Reporting status or mode (e.g., Auto via GPS, Manual traffic updates). | OpenTug | No |
Subservice ID | Internal or external subservice identifier for billing or reconciliation. | OpenTug | No |
Is Outcharter | Indicates whether this barge/tug is being outchartered (Yes/No). | OpenTug | No |
Pressure Rating | Max pressure supported for cargo, where relevant. | Traffic | No |
Needs Orders | Indicates whether voyage is awaiting operational orders. | OpenTug | No |
Alt Ref Number | Alternative reference number used by carriers or charterers. | OpenTug | No |
Last Reported | Last known reported status update (manual or system-generated). | OpenTug | No |
Load Terminal | Terminal name at the load port. | Traffic | No |
Discharge Terminal | Terminal name at the discharge port. | Traffic | No |
Latest Reported Event | Most recent logged event related to the voyage lifecycle. | OpenTug | No |
Voyage Owner | User or company responsible for setting up the voyage record. | OpenTug | No |
Current Destination | The Destination currently entered by the carrier or planner. | OpenTug | No |
Destination Area | Wider geographic area or region of the destination port. | OpenTug | No |