Congratulations on becoming a pilot for the Nourish to Flourish Data Sharing & Analytics Initiative.
This guide lists documents to pull together, as well as steps to take that will make the process of integrating your menus into the tool as fast and easy as possible.
1 - Gather the pieces
- Cycle menus. Note - Creating a 4-5 week cycle menu, even if seasonal changes occur a cycle helps streamline menu planning and procurement.
- Item order lists, bid sheets, item data lists from distributor(s) including prime distributor, dairy, produce, bakery, etc. This report obtained from each vendor/distributor typically has item information including nutrition, serving size, CN Crediting, allergen flags, net weight, and most importantly GTIN's for each item.
- Order tablets to use with the Daily Wrap Up App. The device must use the Android operating system. Approved devices include:
- Samsung Galaxy Tab A SM-T350
- Samsung Galaxy Tab A SM-T385
2 - Complete the eLearning training courses
- inTEAM will set up eLearning and CN Central access for all district personnel.
- Complete all courses in the onboarding program. Courses can be accessed an unlimited amount of times for free throughout the pilot period.
3 - Populate Item Database
- A manual upload of all ordered items into the District Item Database will be completed by an inTEAM consultant in collaboration with the development team. Additional items to be added to the District Item database can be done so by:
- Search for GTIN's using the (+) button and choosing "Search". If the item is in GDSN's database it will show up in the results and can be added to the District Item Database.
- If an item is not pulled up with a GDSN or Generic search, the item will need to be entered manually. Instructions to do this are in the eLearning tutorials as well as here on ZenDesk.
- Update CN Crediting for any item that did not pull in CN Cerditing information upon import.
4 - Create Recipes
- Using Items from the local Item Database and from Generic sources, create all recipes that are currently being used in menus.
- The tool will scale the quantities of ingredients necessary when planned numbers are updated for a recipe on any given day. For example, if you have a sheet of enchiladas that usually serves 100, enter your recipe as such. When your planned number for a day is updated in CN Central, the recipe in the menu for that day will scale the number of ingredients necessary to prepare only the quantity you need.
5 - Create Cycle Menus
- Enter base menus in a week that is a non-serving week (eg. the week before school starts, or a week during summer break). inTEAM usually uses the first week of July since it is typically not a serving day for many districts.
- Think of a consistent naming scheme:
- High School Master Menu Week 1, High School Master Menu Week 2, and so on...
- Lunch Master Menu Week 1, Week 2, Week 3...
- Breakfast Master Menu Week 1, Week 2, Week 3...
- Leave base menus without an assigned school.
- Add static items to a menu first (milk, juices, cereals, assorted fruits, assorted vegetables, entree items that are offered as alternatives every day, etc...). Then, copy out that menu to the other base menus to save time.
- Add all unique daily items and recipes to the menus after static items are added.
6 - Copy Menus to Match Cycle
- Following the school year calendar, begin to assign master menus to the appropriate weeks in the appropriate schools.
- Building or copy groups may be created to save time when copying out cycle weeks. If a menu is used in all elementary schools, for instance, creating an elementary building group allows a user to copy menus to the whole group instead of each school one-by-one. Building groups are configured in CN Central V5.
- Examples of building groups:
- All Schools Breakfast
- Elementary Lunch or Breakfast
- Middle School Lunch or Breakfast
- High School Lunch or Breakfast
- Copy menus out for only a few weeks at a time (one or two months in the future).