Cycle Record Maintenance
Creation, amendment, deletion and enquiry facilities for Cycles. Bank Holiday Maintenance.
A Menu Cycle is simply a list of menus to be served by date and time.
It has a start date and a length in days.
Every Operational Unit may have its own independent cycle, e.g. a cycle for every restaurant, kitchen, shop, etc.
Creation of a Menu Cycle
The Cycle requires a start date (Day 1 on the cycle) and a length. Normally, the
length is divisible by seven so that the cycle restarts on the same day of the week
as the first Day 1. Typically, this is a Monday.
The most common Cycle lengths are 2, 3 and 4 weeks. (14, 21 and 28 days).
However, some users such as Catering Colleges have a cycle of 364 days for the academic year so that the entire catering training course for each class of students is laid out for the year. By merely entering student numbers expected to attend each class, all food, utensils, resources etc., are planned ahead for automatic ordering, and costing information is available in advance.
Once the Cycle has been created, procedure is as for Cycle amendment.
Amendment of a Menu Cycle
On entering the Amendment function, the number of days in the cycle are displayed and
the user is asked to supply a roll-from date.
The cycle is then displayed starting at that roll-from date (which defaults to today's date if no entry is made) for either the full cycle length or 5 weeks, whichever is the shorter.
Menus already listed for a day/time have a deletion button next to them, so that they can be removed from the cycle simply by clicking the button.
To add a new menu to the cycle, the user first inputs either a day number or a date.
The day number indicates a day on the cycle and the menu entered will occur every time the cycle day is encountered in the future until it is removed.
The entry of a date instead of a day number indicates a single future date on which the menu will occur.
A time is then entered to indicate when the menu is to be served or prepared, depending on the type of operational unit and circumstance.
Finally, a menu is entered either as an identifier or by alphmatching (see Menu Display).
On entry, the screen is re-displayed showing the updated situation.
If no change has been made, the amendment function is deemed to be completed.
Deletion of a Menu Cycle
The Menu Cycle is displayed as for the Display Option below.
The user may then delete the Menu Cycle if required.
As creating a complex menu cycle could have required a large amount of work, it is advisable to restrict this facility to high-level passwords only.
Display of a Menu Cycle
To display a Menu Cycle, enter the roll-from date as above.
The cycle will then be displayed either in full or for five weeks, whichever is the shorter.
An option is given to roll forward the cycle if required (the equivalent of displaying it again with the next roll-from date after the last date displayed).
A "Bank Holiday" is a euphemism for any day on which the cycle is to be ignored.
For example, a day when a restaurant normally open on that day in its cycle is to be closed for any reason.
The system will not suggest orders for menus usually served on that day, and will schedule deliveries for the previous working day.
CATERMAN checks to see that there is at least one entry for the future in the list of bank holidays (to ensure that required entries have been made). If no entry is found, a warning message is shown to anybody logging in to the operational unit.
Return to Menu Facilities List