Operations Performance with TOC

TOC 202
TOC Challenge
2-Day Workshop

What results can we expect from using TOC?
• Tenfold return on Continuous Improvement projects
• Improvements that benefit the entire organization, not just a single department
• Increased revenue
• More profits, with a better return on investments
• Better Cash Control
• Ability to attack either existing markets or even open up new markets
• Be able to integrate Lean and Six Sigma in a new and more powerful way into,
  and throughout, the whole organisation.

By making the right strategic changes to your continuous improvement strategy, it is
possible to create a unified approach where all the teams within the organisation will
be working on the right issues using the right tools to get the right job done. All the
teams will begin to do what they are supposed to do; facilitate focused, lasting
improvements that improve the position of the company as a whole.

 

2-Day Workshop

DAY-1
THE SCENARIO (Setting the stage)
MICSS SIMULATION - FIRST RUN (existing situation)
Role play - Dettmer as general manager of notional company (ADV-200 Co.). Participants as “hired consultants.” GM provides guided tour of the plant (the simulation, which approximates a simple ERP system). Participants load MICSS onto their laptops.
Company is in debt and losing money. GM solicits ideas from the participants. Insert suggested policy changes into software, run the simulation. [Typically, the “shotgun” approach produces piecemeal improvements that actually make the whole system situation worse.]

BREAK

PowerPoint presentation (The “Cliffs Notes Version of TOC”)
- Systems approach - Principles of TOC - Overview of the TOC Tools - “P-Q” Problem - Transition to the ADV-200 situation: Apply preceding material to the simulation situation; LTP: CRT, Ecs, FRTs

Participants follow along on their own laptops.
- Apply injections from LTP analysis to simulation

LUNCH

INTRODUCTION / OVERVIEW OF TOC

MICSS SIMULATION - SECOND RUN
(Include injections from first Thinking Process trees)

ANALYZE SECOND MICSS RUN.
MICSS SIMULATION - THIRD RUN
(Include injections from second Thinking Process trees)
FIRST DAY WRAP-UP