T.1.07.0

Last updated
Save as PDF

T.1.07.0 - Status Report Transaction

Many of the fields in the transaction are optional. For example, you are not guaranteed to get two proximities and you are not guaranteed to get reefer information.

Here is a SAMPLE XML segment showing what this transaction WITHOUT REEFER INFO will look like:

<tran ID="37984" companyID="LIVE" auxID="1752046889">

<T.1.07.0>

<eventTS>2015-07-01T12:04:27Z</eventTS>

<equipment ID="CSI1077" mobileType="10" unitAddress="0121001077" equipType="trailer" SCAC="LABZ"/>

<position lat="40.157222222" lon="-75.881388888" posTS="2015-07-01T11:58:46Z"/>

<proximity city="Reading" postal="19601" country="US" distance="12.73" direction="SSE" placeType="CITY" stateProv="PA"/>

<proximity city="Morgantown" postal="19543" country="US" distance=".55" direction="ENE" placeType="TOWN" stateProv="PA"/>

<connectStatus>1</connectStatus>

<cargoSensorState>1</cargoSensorState>

<doorSensorState>2</doorSensorState>

<auxSensorState>2</auxSensorState>

<T2BatteryStatus>1</T2BatteryStatus>

<trailerTripStatus>1</trailerTripStatus>

<powerState>0</powerState>

<mileageCounter>100100</mileageCounter>

<mileageCounterTS>2015-07-01T12:01:32Z</mileageCounterTS>

</T.1.07.0>

</tran>

Here is a SAMPLE XML segment showing what this transaction WITH REEFER INFO will look like:

<tran ID="166819" companyID="LIVE" auxID="1752046889">

<T.1.07.0>

<eventTS>2015-07-01T12:04:27Z</eventTS>

<equipment ID="CSI1077R" mobileType="10" unitAddress="0121001077" equipType="trailer" SCAC="LABZ"/>

<position lat="40.157222222" lon="-75.881388888" posTS="2015-07-01T11:58:46Z"/>

<proximity city="Reading" postal="19601" country="US" distance="12.73" direction="SSE" placeType="CITY" stateProv="PA"/>

<proximity city="Morgantown" postal="19543" country="US" distance=".55" direction="ENE" placeType="TOWN" stateProv="PA"/>

<connectStatus>1</connectStatus>

<cargoSensorState>0</cargoSensorState>

<doorSensorState>0</doorSensorState>

<auxSensorState>0</auxSensorState>

<T2BatteryStatus>1</T2BatteryStatus>

<trailerTripStatus>D</trailerTripStatus>

<powerState>0</powerState>

<reeferType>1</reeferType>

<reeferMode>002</reeferMode>

<reeferEngHrs>305.0</reeferEngHrs>

<reeferZone zoneID="1" retTemp="25.0" setTemp="25.0" supTemp="25.0" opStatus="002"/>

<reeferOEMAlarmSeverity>0</reeferOEMAlarmSeverity>

<reeferTempRangeAlarm>0</reeferTempRangeAlarm>

<reeferLowFuelAlarm>0</reeferLowFuelAlarm>

<reeferSetPointAlarm>0</reeferSetPointAlarm>

<mileageCounter>100100</mileageCounter>

<mileageCounterTS>2015-07-01T12:01:32Z</mileageCounterTS>

</T.1.07.0>

</tran>

The following diagram illustrates the XML schema for the Status Report transaction. The transaction contains optional reefer status information for trailers equipped and enabled to monitor and report refrigerated trailer information and status conditions. There are several Shared Complex Types which are re-used within most of the Services Portal transactions.