Date post: | 19-Mar-2023 |
Category: |
Documents |
Upload: | khangminh22 |
View: | 0 times |
Download: | 0 times |
3131
Recall and Response at Whole Foods Market• Why does Whole Foods need a Recall Application?• What does our process look like? • What were the Business Problems we were looking to solve?• How did we choose FoodLogiQ?• What do we hope to gain from using the Recall and Response Module?• Where are we today? • Communication Plan Examples• Challenges• Next Steps
3232
Why does Whole Foods need a Recall Application?
• 486 Stores• 12 Regions• 40 Distribution Centers/WFM
Owned Facilities• 450,000 Products
3333
What does the WFM process look like?
Notification is received at
global or regional
office
Determineclassification
Send tostores that
carryproduct(s)
Stores are notified via email, text, or phone
Store team memberrecords
quantity of product removed
Global or regional
office closes event once all
stores have reported
Provide reports to regulatory agency or supplier
3434
What were the Business Problems we were looking to solve? • Reliable communication• Intuitive user interface • Automate escalation process • Track and manage response times• Real Time Dashboard• Enhanced Reporting
3535
Why did we select FoodLogiQ?• Integrated with FoodLogiQ Connect • The People! • Agile Development approach/frequent releases• Meets Business Problems we were trying to solve
3636
What do we hope to gain?• Quicker response times • Enhanced reporting • Spot trends and improve business process• Real time visibility for leadership
3737
Where are we today?
Stak
ehol
der
Appr
oval
Scop
e & D
ates
Com
mun
icatio
n
Plan Testi
ng
Train
ing
Go-Li
ve
3838
Communication Plan Examples• Attended Key Stakeholder Team Meetings• One-Pager • Training – video and user guides• Mock Recalls and surveys• Open Conference Lines – real time support• Demos and Open Q&A
3939
Objectives• Increase the speed and accuracy of recalls and withdrawals. • Improve reporting to drive process improvement.
BenefitsMore user friendly and efficient
• Email notifications will have a working link that takes you directly to the recall.• Individual logins - no more “generic” logins for each store.• No need for regions to review, filter and pass along notifications to stores.• Possibility for text message recall notifications in the future.
Improved reporting and escalation features• A dashboard view for easier, real-time tracking by global and regional recall initiators.
• Automated escalations to alert leadership when a store has not completed a recall within specified time frame.
Recall Management
4040
Project TimelineWeek of May 21st – 25th
• Multiple demos accompanied by Q&A Sessions offered. Invitations will be sent in Mid-May.
May 29th
• Training and Login Information will be provided on the morning of Tuesday, May 29th.
• A mock recall will be sent to all stores. A representative from all stores must respond.
• After May 29th, ICIX will no longer be used for recall and withdrawal management.
Recall Management
4242
Challenges• 10,000 User Accounts• Communication• Change Management• Scope Management• Legalities of Text and Phone Calls• Data Wrangling