Hours of Service (HOS) integration

We are configuring OTM to integrate with OmniTracs truck-mounted mobile devices. The devices expose an API which return driver HOS data in a format that looks like this:

<DriverExportData>
<DriverId>XXDRIVER</DriverId>
<Password>99999</Password>
<LastName>Joe</LastName>
<FirstName>Smith</FirstName>
<DepotId>2</DepotId>
<TractorId>123456789</TractorId>
<ActivityStarted>2015-11-07T10:22:00</ActivityStarted>
<DayRestBreak>179</DayRestBreak>
<DayDrive>447</DayDrive>
<DayDuty>539</DayDuty>
<WeekDuty>3899</WeekDuty>
<DayOff>0</DayOff>
<Shift>0</Shift>
<LastAvailHoursRecalc>2015-11-07T11:04:00</LastAvailHoursRecalc>
<TodayOnDuty>88</TodayOnDuty>
<TodayOffDuty>363</TodayOffDuty>
<TodaySleeper>0</TodaySleeper>
<TodayDrive>213</TodayDrive>
<YesterdayOnDuty>0</YesterdayOnDuty>
<YesterdayOffDuty>1440</YesterdayOffDuty>
<YesterdaySleeper>0</YesterdaySleeper>
<YesterdayDrive>0</YesterdayDrive>
<Activity>3</Activity>
<TimeZone>Central Standard Time</TimeZone>
<USDutyCycle>EightDay</USDutyCycle>
<CANDutyCycle>SevenDay</CANDutyCycle>
<CurrentRuleSet>USA</CurrentRuleSet>
<CycleResetTime>2015-11-07T02:33:00</CycleResetTime>
<ContiguousActivityDuration>42</ContiguousActivityDuration>
<ContiguousNonworkingDuration>0</ContiguousNonworkingDuration>
</DriverExportData>

Where DayDrive and DayDuty and WeekDuty are calculated available minutes for the driver, and TodayOnDuty and TodayDrive are elapsed minutes today.

These calculations account for the current DOT regulations, so I don't believe there is a need to use the OTM HOS rule mechanism.

How can we send these up to OTM in such a way that truck dispatching will account correctly for the HOS rules? Do we need to independently set up the HOS rules in OTM? Do we need agents to apply the Integrations?