Skip to Main Content
Bulk Materials Ideas

Idea and discussion portal for the bulk materials product line. Users may submit, view and vote on ideas submitted by all users.

Status Reviewing
Categories Ticket
Created by Simon Edwards
Created on Aug 9, 2018

Split the Configuration / Behavior of Check In vs Tare in

I thought I'd added this a year ago, but I don't find it. Apologies if this duplicates anything.

Check In vs Tare In

Scenario: Asphalt Plants with a pool of subcontracted trucks that need tares, but are not yet assigned to Orders.The plant uses a third party batch asphalt system (Libra).

Issue: If System Configuration Ticket->Scale Ticket Options -> Tare / Assign Control->Have Valid Ticket Fields for Tare is set to ‘Yes’, then taring trucks becomes problematic. We would have to put a fake Customer, Order, or Product on the Vehicle record just to tare the truck. We don't yet know the real job the truck is going to service but need to tare regularly.

We have made the Configuration setting 'No', but this causes issues occasionally when sending a truck to the third party Libra system using Bin 88 and Ctrl-I, as there is no validation of the load data.

Suggested Option: Make the Tare In and Check In separate functions, with separate configuration choices, so that it is possible to not require valid Order information just to get a tare, and still require good information before batching asphalt. If the data was validated before it was sent to the third party system, it would prevent many Error Tickets. These include 'no assignment for vehicle', 'order quantity exceeded', and similar showstopper issues. We don’t want to load perishable product on a truck only to find out there is a problem on the Order. The validation would be subset of the checks that are used for a valid ticket, other than weight-related checks. The weights would not be known until after the product is manufactured.

  • Attach files
  • Justin Higdon
    Reply
    |
    Aug 9, 2018

    Yeah, even if you configure it to use the begin loadout button instead of ctrl+I the whole concept of validating load for loadout should be separate from validate information for tare in. Regardless of 3rd party loadout or Apex loadout. 

  • Robert LaRue
    Reply
    |
    Aug 9, 2018

    I agree that Tare Control and Assign Control should be separate things.

    Having valid fields for Tare should be optional.

    Having valid fields for Assignment should not be optional.

    This is the case when using the Assign Vehicles screen. You cannot assign a vehicle to an invalid Customer, Order, Destination, Product, etc.

    The same should be true when sending a vehicle assignment to 3rd party loadout through the Ticket Interface.

    See  the proposed changes to the System Configuration screen below.

  • +3