When feed plan is approved, farm managers will plan operations around expected delivery dates. There may be logistical and planning reasons which require the feed mill to commit to the agreed upon dates, one such an example provided is when it snows, and farmers have to plan for plowing services to clear the road for scheduled deliveries. Once something like this has to be coordinated, deliveries optimized by flock performance take a lower priority to showing up at a certain times and dates.
The feed plan fixed date feature will force the regeneration process to lock down specific delivery dates and prioritize creating records with those dates.
| Table of Contents |
|---|
Adding Single Fixed Dates
...
Because delivery date buffers change with overall consumption, and because our logic for rounding will assume past or future hours of consumption to make rounded delivery amounts, we could not code the fixed date logic to look for exact delivery dates. Because of the code above that will wrap up deliveries prior to a fixed date, and because the feed plan process is already designed to optimize delivery sizes without causing overflows or feed returns, the approximation of the dates always results if a difference of hours that should not cause any concerns.
...
A new key can be added to the app.config. This key, "FeedPlanAuditPath" will enable the audit of each feed plan to be written to a file on the local machine.
<add key="FeedPlanAuditPath" value="C:\imp\fp\" />
...