SPEED Training

1. SPEED Training May 2005 Presented by Nancy Remus Supply Chain M&A

2. Introductions Presenter: Nancy Remus Sr. Supply Chain Coach M&A Northfield, IL Phone: 847-646-2361 Extension: 6-2361 Email: nremus@kraft.com Participants: What facility are you from? What are your reasons for attending this training? What are you expecting to learn?

3. Today’s Agenda • Presentation • Introductions • Objectives • What is SPEED? • SPEED and Other Systems • SPEED versus Rocet G • Importance of SPEED • Process of Finite Scheduling • SPEED Demonstration • Demonstration • Mistakes to Avoid • SPEED Practice • SPEED Review • Questions & Answers

4. Objectives As a result of this training, you will be able to: • Define SPEED • Name the differences between SPEED and Rocet G • Create a daily 6 WEEK finite schedule using SPEED • Publish a daily finite schedule to the Schedule Repository using SPEED

5. What is SPEED? • SPEED (Scheduled Production Electronic Entry Data) is a Manugistics web-based application (Collaborate) designed to: • Enter daily scheduled production to feed the Schedule Repository based upon the weekly Master Schedule • SPEED is designed to be used by: • Plant Schedulers at Kraft facilities (Davenport, Columbia, etc.) and co-manufacturers (Cloud, Marathon, etc.) • All facilities that produce items not currently scheduled through Schedule-X or IMPACT SPEED is NOT intended for finite sequencing

6. Schedule Repository (MRP System) SPEED and Other Systems Allows entering daily scheduled production Holds the “knitted” schedule from all scheduling tools Generates initial Master Schedule used to define finite schedule Uses “knitted” schedule from Schedule Repository to generate material replenishment requirements

7. SPEED versus Rocet G

8. Importance of SPEED Enables proper MRP planning in Crystal • Provides Material Managers with a more accurate 6 week raw/pack requirements by publishing daily schedules to the SR • Tells Material Managers what raw materials to order Allows plants to schedule the week’sproduction activity

9. ViewMaster Schedule Quantity in Master Schedule field Enter Finite Schedule into Finite Schedule field Save Schedule by clicking the Save button Schedule is published to the Schedule Repository Schedule Repository Process of Finite Scheduling

10. SPEED Demonstration • Logging in • Fields & Dropdowns • Entering Finite Schedule

11. Mistakes to Avoid • Mistake 1: NOT ENTERING A FULL 6 WEEK SCHEDULE What will happen: SPEED will send a “0” qty in the days you have not populated. That means, if you were currently only scheduling 2 weeks, you need to look farther out at your Master Schedule and at least enter in the weekly quantity out past the 2 week initial Finite Schedule. Otherwise, Crystal will NOT have the appropriate requirements. • Mistake 2: Entering a schedule in a “weekly” bucket What will happen:SPEED will disaggregate the schedule to a “daily” bucket, which 1) will not consider run times (when the line is “up” versus “down”), and 2) will load the line beyond capacity. • Mistake 3: Entering a schedule at a “higher” level, such as by line or location What will happen:SPEED will disaggregate the schedule down to an item level, which will not consider true demand for items needed for production.

12. SPEED Practice

13. SPEED Review • What is the purpose of SPEED? • To enter a Finite Schedule. • Who uses SPEED? • Finite Scheduler and/or NPP. • What systems does SPEED feed? • Crystal/Prism and Manugistics • How often does SPEED publish to and receive from the SR? • Four times a day (every three hours). • Should you enter schedules at the weekly level? • NEVER!!!

14. SPEED Review • Should you enter schedules at the location/line level? • No you should always enter at the Line/item level. • Do you have to enter a “1” at the end of the horizon? • No Thank Goodness! • Who is responsible for reviewing/updating prod rates? • Finite Scheduler or NPP (whomever is entering Schedule)

15. Questions and Answers