search

nmfta-repo / nmfta-opentelematics-api

API Blueprint for Open Telematics API
Apache License 2.0
14 stars 6 forks source link

Use Case: Driver Availability - Add Driver Current Status #60

Closed HVCSFriend closed 5 years ago

HVCSFriend commented 5 years ago
Table 1    
Duty Status Categories    
     
Duty Status Abbreviation Data Coding
Off Duty OFF 1
Sleeper Berth SB 2
Driving D 3
On-duty Not Driving ON 4
Table 2    

Categories for Driver's Indication of Situations Impacting Driving Time Recording   |   |     |   |   Category | Abbreviation | Data Coding Authorized Personal Use of CMV | PC | 1 Yard Moves | YM | 2 Default: None | --- | 0

BenGardiner commented 5 years ago

I don't know how to resolve this issue. I'll need more details please.

HVCSFriend commented 5 years ago

I see now that you have these 4 included as status_off, status_sb, status_d and status_on.

We may need 2 tree levels for these. For instance, I think On-duty Not Driving above is really comprised of: status_ym, status_wt,

Status_on should include status_ym,

Status_off should include status_pc, status_int-pc. In a webinar on the end of the grandfathering clause for AOBRDs last week, the trainer noted that currently carriers may set time and/or distance limits for pc where it doesn't count against HOS, but the FMCSA should issue guidance on this.

What is an intermediate drive event (status_int_d)?