Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ops Report #19

Open
vcardillo opened this issue Jan 23, 2016 · 0 comments
Open

Ops Report #19

vcardillo opened this issue Jan 23, 2016 · 0 comments
Assignees
Milestone

Comments

@vcardillo
Copy link
Member

Here's my take on how this needs to work.

  1. At 10:00:00am, the "Calculate" button becomes available for the ops team to click. We pass Routific all of the orders, and Routific gives us back the number of drivers.
  2. The ops team selects the drivers who will be going on shift, and click "Done".
  3. We run the Routific calculation again, this time also passing Routific the driver_weight data.
  4. IF driver qty hasn't changed, we're done, and automatically assign the orders to the drivers based on this latest calculation.
  5. ELSE, driver qty has changed (perhaps a driver is too slow). Proceed back to step 2, until step 4 matches.

Once the drivers have been finalized, a "Generate Report" button is clicked, which generates a PDF of the qty of each item to be packed with each driver.

  • One driver per page.
  • Sort by hot/cold items (data is in the DB).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants