COMMANDseries V2 Ideas
Idea and discussion portal for the COMMANDseries V2 product line. Users may submit, view and vote on value-added ideas submitted by all users.
Idea and discussion portal for the COMMANDseries V2 product line. Users may submit, view and vote on value-added ideas submitted by all users.
I think the best way would be to have a reason code that can be configured but would be a standard response to then allow for consistent reporting (Option #2)
[cid:image001.png@01D1AF60.72242E30]
Aaron Snowdon | Summit Materials |
Ready Mix Performance Team
email: Aaron.Snowdon@summit-materials.com
1550 Wynkoop Street 3R | Denver, CO 80202
Cell: 780 446 7203
It sounds like we want a field on this screen when some or all of the material isn't used as pre-batched on the next ticket.
Option 1: Have free text field. They can type whatever they want, but this makes report aggregation harder. Effort is small.
Option 2: Have a predefined list to pick from. But different producers may want this list customizable. Would have to have an editor somewhere else. Effort is more.
I do agree having a reason code when material produced is answered yes; this would help with some advanced reporting but it will not help when we are returning from a jobsite with leftovers on the truck. This is the scenario where we'd want to have a few more options to flag what was done with the material when it's returned.
Right now we have reason codes for ticket (if not batched). Maybe this could be solved by ability to use reason codes for Produced concrete (yes to was concrete produced question)?
Most of the time dispatch would know the reason
Typically as the trucks are returning, dispatch is instructing the driver what to do with the material; block, reclaim, dump, reuse etc.
Would dispatch typically know that at time of truck return and ticket cancellation or is that a Invoicing Prep function?