ESS Transactions

• Return Messages From Owned Vehicles

Transaction Type	Name	Description
T.2.01.0	Text Return Freeform Messages	Generated whenever a freeform return message is received from an owned vehicle. Vehicles are said to be "owned" when the mobile device in the vehicle is associated with the Omnitracs NMC account of the company that is connecting to the NMC. A "foreign" vehicle is a vehicle whose information is being copied to the connected NMC account from a different account through the QMASS feature.
T.2.RM01.0 thru T.2.RM63.0	Text Return Macro Messages (01 - 63)	Generated whenever a macro return message is received from an owned vehicle. Sixty-three separate return transactions are published and available for independent subscription
T.2.10.0	Binary Return Messages	Conveys binary return messages sent from owned vehicles by "third-party applications" (not Trailer Tracks and not Performance Monitoring).

Transaction Type

Name

Description

T.2.01.0

Text Return Freeform Messages

Generated whenever a freeform return message is received from an owned vehicle. Vehicles are said to be "owned" when the mobile device in the vehicle is associated with the Omnitracs NMC account of the company that is connecting to the NMC. A "foreign" vehicle is a vehicle whose information is being copied to the connected NMC account from a different account through the QMASS feature.

T.2.RM01.0 thru T.2.RM63.0

Text Return Macro Messages (01 - 63)

Generated whenever a macro return message is received from an owned vehicle. Sixty-three separate return transactions are published and available for independent subscription

T.2.10.0

Binary Return Messages

Conveys binary return messages sent from owned vehicles by "third-party applications" (not Trailer Tracks and not Performance Monitoring).

• Forward Message Dispositions

(info) Note that these messages are published via ESS only when the prior/referenced forward message:

was sent to a vehicle, and
was not sent via a broadcast message group, and
originated from integration

Transaction Type	Name	Description
T.2.02.0	All Forward Message Dispositions	Generated whenever a prior forward text or binary message is received successfully or failed to be received by the mobile unit.
T.2.03.0	Negative-only Forward Message Dispositions	Generated whenever a prior forward text or binary message fails to be delivered for any reason.
T.2.04.0	Forward Message Read Notifications	Generated whenever a prior forward text messages is read by the driver (if return receipt was requested).

Transaction Type

Name

Description

T.2.02.0

All Forward Message Dispositions

Generated whenever a prior forward text or binary message is received successfully or failed to be received by the mobile unit.

T.2.03.0

Negative-only Forward Message Dispositions

Generated whenever a prior forward text or binary message fails to be delivered for any reason.

T.2.04.0

Forward Message Read Notifications

Generated whenever a prior forward text messages is read by the driver (if return receipt was requested).

• Message Copies to/from Auxiliary Vehicles

Transaction Type	Name	Description
T.2.05.0	Routed Text Messages	Generated whenever a routed (Q/BluMASS) text forward or return message is sent from/to a vehicle from another Omni account. Macro messages are expanded to freeform by the Omnitracs network operations center
T.2.11.0	Routed Binary Messages	Conveys binary message copies to/from auxiliary vehicles. They are published whenever a routed (QMASS/BluMASS) binary forward or return message is exchanged between an auxiliary vehicle its owner's account

Transaction Type

Name

Description

T.2.05.0

Routed Text Messages

Generated whenever a routed (Q/BluMASS) text forward or return message is sent from/to a vehicle from another Omni account. Macro messages are expanded to freeform by the Omnitracs network operations center

T.2.11.0

Routed Binary Messages

Conveys binary message copies to/from auxiliary vehicles. They are published whenever a routed (QMASS/BluMASS) binary forward or return message is exchanged between an auxiliary vehicle its owner's account

• Position Feeds

Transaction Type	Name	Description
T.2.06.0	Vehicle Position Reports	Generated whenever an updated position is received from a vehicle
T.2.12.0	High Frequency Vehicle Position Reports	Generated whenever an enhanced position (GIPR) is received from an MCP-equipped or IVG-equipped vehicle
T.1.08.0	Trailer Position Reports	Generated whenever an updated position is received from a trailer, or from the vehicle to which it is connected
T.1.18.0	High Frequency Trailer Position Reports	Generated whenever a high-volume position is received from an MCP/IVG-equipped vehicle connected to a trailer

• Entity Definition Synchronization Notifications

Transaction Type	Name	Description
T.2.07.0	Vehicle Definition Notifications	Generated whenever a vehicle is created, deleted, renamed or has its UA changed
T.2.08.0	Driver Definition Notifications	Generated whenever a driver is created, deleted or renamed
T.1.09.0	Trailer Definition Notifications	Generated whenever a trailer is created, deleted, renamed or has its UA changed
T.2.09.0	Macro Template Definition Notifications	Generated whenever a macro message template definition initiated from any source has been acknowledged by the Omnitracs network operations center.

• Trailer Tracking Events

Transaction Type	Name	Applies to TT100-equipped trailers	Description
T.1.01.0	Connect/Disconnect Notifications		Generated whenever a Connect or Disconnect event, to or from an Omni-equipped vehicle, is received for a UTT-equipped or tethered trailer
T.1.03.0	Door Event Notifications		Generated whenever a Door Open or Door Close event is received from a UTT-equipped trailer
T.1.04.0	Auxiliary Sensor Event Notifications		Generated whenever a Auxiliary (Sensor 4) Open or Auxiliary Close event is received from a UTT-equipped trailer
T.1.02.0	Cargo Event Notifications		Generated whenever a Cargo Loaded or Cargo Empty event is received from a UTT-equipped trailer
T.1.05.0	Battery Event Notifications		Generated whenever a Battery Needs Charged or Battery Needs Replaced event is received from a UTT-equipped trailer
T.1.06.0	Geofence Event Notifications		Generated whenever a Geofence entry or exist event is received from a UTT-equipped trailer
T.1.07.0	Status Reports		Generated whenever a Status Report is received from a UTT-equipped trailer
T.1.10.0	Mobile Health Status Reports		Generated whenever a "mobile unit error" for a UTT-equipped or tethered trailer is detected, or an error that was previously detected is cleared.
T.1.12.0	Trailer Trip Reporting Events	Edit link	Generated whenever a trailer trip event is detected and received from a UTT-equipped trailer.
T.1.13.0	Trailer External Power Events		Generated whenever an external power event is detected and received from a UTT-equipped trailer.
T.1.14.0	Reefer Trailer OEM Alarm Events		Generated when a new OEM alarm condition is detected on properly equipped reefer trailers.
T.1.15.0	Reefer Trailer Temperature Events		Generated when a temperature out-of-range condition is detected and when the temperature out-of-range condition is cleared on properly equipped reefer trailers.
T.1.16.0	Reefer Trailer Set Point Events		Generated when a wrong temperature set point condition is detected and when the wrong temperature set point condition is cleared on properly equipped reefer trailers.
T.1.17.0	Reefer Trailer Low Fuel Events		Generated when a low fuel condition has been detected and when the low fuel condition is cleared on properly equipped reefer trailers.
T.1.19.0	Tethered Reefer Status Reports		Generated when a tethered reefer-equipped trailer returns its Reefer Status Report.
T.1.20.0	Data Sharing Disposition Notification		Generated when a Data Sharing relationship is enabled/disabled.
T.1.21.0	Mileage Counter Exceeded Notification		Generated when a TT210 device's mileage counter exceeds the configured threshold. The TT210 device must have supporting firmware.

• Driver Events

Transaction Type	Name	Description
T.2.13.0	Driver Login Event Notification	Generated whenever a login event is received from a mobile device. It provides a mechanism to notify of driver logins, logouts, and security breach events. Notifications are only generated when the Global Login feature is enabled.

Transaction Type

Name

Description

T.2.13.0

Driver Login Event Notification

Generated whenever a login event is received from a mobile device. It provides a mechanism to notify of driver logins, logouts, and security breach events. Notifications are only generated when the Global Login feature is enabled.

• Mobile (On-Board) Events

Transaction Type	Name	Description
T.3.01.0	Vehicle Control Event Notifications	Generated whenever a vehicle command and control event subject to notification is detected on the vehicle.
T.3.02.0	Critical Event Reporting Incident Notifications	Generated whenever a critical event subject to notification is detected on the vehicle.
T.3.03.0	Vehicle Diagnostics Event Notifications	Generated whenever an on-board device reports monitoring or fault event information.
T.3.04.0	Vehicle Diagnostics Parameter Information	Generated whenever monitored on-board sensor and device parameter information is being reported.
T.3.05.0	Vehicle Diagnostics Status Reports	Generated whenever a vehicle reports status information through the Vehicle Maintenance application.
T.3.06.0	Trailer ABS-Detected Connect / Disconnect Events	Generated whenever a vehicle detects a connect/disconnect as reported from the attached trailer's Antilock Brake System.
T.3.07.0	Exact Fuel Events	Generated whenever a fuel-related event is returned from the vehicle.
T.3.08.0	Trip Manager Return Data Messages	Generated whenever the Trip Manager application publishes a workflow-like message in response to an event received from the vehicle.
T.3.09.0	Terrestrial Browsing Alert	Generated whenever a data volume cap threshold is exceeded.
T.3.10.0	Trailer Tire Inflation Alert	Generated whenever a TTIA-configured MCP has determined that a trailer tire airing alert should be returned to the host.
T.3.11.0	Tire Pressure Monitoring Event	Generated whenever a TPM-configured MCP has determined that a tire pressure monitoring event should be returned to the host.
T.3.12.0	Critical Event Reporting Incident Update Notifications	Generated whenever there is an update to an existing critical event.
T.3.13.0	Critical Event Reporting Coaching Notification	Generated whenever any changes to Driver Coaching information are made at the CER UI.

• Performance Monitoring Events

Transaction Type	Name	Description
T.4.01.0	Performance Data Extract Events	Conveys driver performance extract information from the given vehicle enabled for Performance Monitoring.
T.4.02.0	Fault Events	Conveys J1708-based fault conditions detected for the given vehicle equipped for Performance Monitoring.

Transaction Type

Name

Description

T.4.01.0

Performance Data Extract Events

Conveys driver performance extract information from the given vehicle enabled for Performance Monitoring.

T.4.02.0

Fault Events

Conveys J1708-based fault conditions detected for the given vehicle equipped for Performance Monitoring.

• GeoServices Events

Transaction Type	Name	Description
T.5.01.0	Geo-Spatial Events	Generated whenever GeoServices detects that a geo-spatial event (e.g. arrival, departure) has occurred for a given asset.

Transaction Type

Name

Description

T.5.01.0

Geo-Spatial Events

Generated whenever GeoServices detects that a geo-spatial event (e.g. arrival, departure) has occurred for a given asset.

• Workflow Events

Transaction Type	Name	Description
T.6.01.0	Workflow forward message disposition	This transaction type is published whenever a workflow forward message is submitted for over the air transmission to a mobile unit. The transaction will indicate the success or failure disposition of the forward message submittal.
T.6.02.0	Workflow message delivery notification	This transaction type is published whenever a previously transmitted workflow forward message is received by a mobile unit.
T.6.03.0	Workflow data message	This transaction type is published whenever a return workflow data message is received from a mobile unit.
T.6.04.0	Workflow unit change notification	This transaction type is published whenever a Workflow unit change notification is generated as a result of a configuration change on a mobile unit.

• Vehicle Inspection Report Events

Transaction Type	Name	Description
T.7.01.0	VIR defect message	This transaction type is published whenever a return VIR defect message is received from a mobile unit.
T.7.02.0	VIR forward message disposition	This transaction type is published whenever a VIR forward message is submitted for over the air transmission to a mobile unit. The transaction will indicate the success or failure disposition of the forward message submittal.
T.7.03.0	VIR message delivery notification	This transaction type is published whenever a previously transmitted VIR forward message is received by a mobile unit.

Transaction Type

Name

Description

T.7.01.0

VIR defect message

This transaction type is published whenever a return VIR defect message is received from a mobile unit.

T.7.02.0

VIR forward message disposition

This transaction type is published whenever a VIR forward message is submitted for over the air transmission to a mobile unit. The transaction will indicate the success or failure disposition of the forward message submittal.

T.7.03.0

VIR message delivery notification

This transaction type is published whenever a previously transmitted VIR forward message is received by a mobile unit.

• Media Manager Events

Transaction Type	Name	Description
T.8.01.0	MMS File Disposition Notification	This transaction is published by Media Manager to indicate the disposition of a prior file delivery request. These notifications are published on a per-vehicle basis whenever files are delivered, consumed, or deleted at the mobile.

Transaction Type

Name

Description

T.8.01.0

MMS File Disposition Notification

This transaction is published by Media Manager to indicate the disposition of a prior file delivery request. These notifications are published on a per-vehicle basis whenever files are delivered, consumed, or deleted at the mobile.