| Table of Contents |
|---|
Introduction
The feed plan feature allows users to generate feed records based on flock consumption and bin availability on houses. One of the greatest shortcomings of this feature is that it lacks some logistical elements. One example of this is delivery times- with the exception of some settings we can set for buffered delivery dates, the software will recommend that feed be delivered outside of the operating hours of the feed mills that produce them, and the farmers that receive them. This feature will be the start of resolving that.
...
- Flocks with feed profiles, and other feed plan configurations.
- Security affiliation to flocks and facilities.
- Security access to the delivery scheduling screen.
...
Deliveries Calculated On a Non-Operational Day
At present, we are not creating these deliveries. They are omitted from the end results and a message was logged that it was not created. Users will have to create records manually to account for these.
These deliveries are logged in the messages section of a generated feed plan.
These are the records that we will need to solicit feedback on to figure out how to deal with them. Do we move the forward? backwards? split them between delivery windows? give users a simple interface to make the decision on a case by case basis?
We will move the deliveries back and try to fill the bin to capacity. Any remaining feed will be regenerated into the feed plan moving forward. If there is a delivery on a non-op day that cannot be delivered prior because of bin capacity, we will move it back to the next operational day, if the start consumption date is greater than the delivery date. We will highlight these deliveries in Orange to let you know that there is a chance you birds will run out of feed due to this scenario.
Auditing the Results
...