Professional Documents
Culture Documents
Recap: Smurfit-Stone Container Operational Excellence Boot Camp
Recap: Smurfit-Stone Container Operational Excellence Boot Camp
Motivated,
capable people
A powerful
change engine
Management
information and
systems
Mindsets and
capabilities
“the driver”
Performance
Behavioral
effect
“Technical”
improvement
Time
Stability Step change Sustainability
.... making
There
.The
and
But
We . aknow
there
waste
bad
lot
areof
news
Generalis
how
good
these
iswaste
some
bad…
isto
newsmanager
that
very
good
turn
changes we
waste
bad
news
andfound
can
bad.into
.create
.
news . . .
waste
value
value!
Operator Supervisor
(7 years’ (12 years’
experience) experience)
– A clear view on the current and future state guides the design, using inputs from the
operational and organizational assessments
– People change over time and the stages of change are fairly predictable ;
successful change programs take this into account and are rolled-out in a sequence
that reinforces these stages
People development
Behaviors are a
Visible example
result of
What we see underlying
and attempt to • I don’t make time for
coaching mindsets and
address Behavior capabilities
Fostering understanding
Role-modeling and conviction
• Leadership actions “…I see superiors, “…I know what is • Story development
• Opinion shapers peers and subordinates expected of me – I (includes all the key
• Interactions behaving in the new agree with it, and it is elements, e.g., values,
way” meaningful” strategy, case for
change)
• Story delivery (across
relevant levels, i.e.,
organizational,
employee, functional)
What you do
• Develop managerial capability
– Establishing/monitoring KPI’s
OPX – Conducting performance
dialogues
Management – Supervising compliance and
System improvement to standard work
OPX Operating
Tools
System
• Visual management boards
• Machine operating logs
Smurfit-Stone • Standard metrics and targets
Performance
Culture
Metrics &
• OPX KPIs cascaded to floor
targets
• Targets provide performance stretch
• Individuals held accountable for performance
Performance
dialogue
• Cascaded meetings with clear structures and agendas
• Meetings are well prepared and attended with good team dynamics
Actions /
Rewards &
Consequences • Problem solving approach used (problem identified, prioritized, solutions and actions)
• Poor individual performance identified and addressed. Good performance rewarded
• Safety • Safety
Area Ops • Operational execution
Managers
• Cost / MSF
– Margin • Margin / MSF
– Waste [informational]
– Quality
• Safety • Safety
Plant • Plant performance • Cost / MSF
Managers – Cost
• MSF / machine hour
– OEE • OEE
• Waste
• Quality
Plant
Superintendent
• Safety
Supervisors • Machine center performance • Safety
– Production • Production / machine
*Machine type – Waste hour*
dependent – Quality
(lineal ft / MH,
MSF / MH, or Hourly
kicks / MH)
Smurfit-Stone Container * Operational Excellence Boot Camp 17
Source: OPX Playbook
Smurfit-Stone Container * Operational Excellence Boot Camp 18
MANAGEMENT TOOLS PROVIDE CLARITY INTO PERFORMANCE
Initial
Supv
63,800
Hr
58,000
1
52,200
46,400 2
40,600
3
Total Kicks Made
34,800
29,000
4
23,200
17,400 5
11,600
5,800 6
HOUR 1 1 2 3 4 5 6 7 8 9 10 11 12 7
Machine running at Y Machine running at Y If "N" at start or end of shift, record
start of shift? N end of shift? N reason in box #1 or #12 8
Kicks (# last HR)
9
Total Kicks
Downtime (for
Hr)
10
Speed
(kicks/min)
11
Tgt Speed 252 252 252 252 252 252 252 252 252 252 252 252
S 15
Target Actual Available at Set Up? (Y/N)
E 15 S Order Time Time Stock Ink Plates Cut Die Paperwork Pallets # BOX
T 15 E 15
U T
15 15
P U
S 15 15
P
15 S 15
15 15
Initial
Supv
63,800
Hr
58,000
1
52,200
46,400 2
40,600
3
Total Kicks Made
34,800
29,000
4
23,200
17,400 5
11,600
5,800 6
HOUR 1 1 2 3 4 5 6 7 8 9 10 11 12 7
Machine running at Y Machine running at Y If "N" at start or end of shift, record
start of shift? N end of shift? N reason in box #1 or #12 8
Kicks (# last HR)
9
Total Kicks
Downtime (for
Hr)
10
Speed
(kicks/min)
11
Tgt Speed 252 252 252 252 252 252 252 252 252 252 252 252
S 15
Target Actual Available at Set Up? (Y/N)
E 15 S Order Time Time Stock Ink Plates Cut Die Paperwork Pallets # BOX
T 15 E 15
U T
15 15
P U
S 15 15
P
15 S 15
15 15
Initial
Supv
63,800
Hr
58,000
1
52,200
46,400 2
40,600
3
Total Kicks Made
34,800
29,000
4
23,200
17,400 5
11,600
5,800 6
HOUR 1 1 2 3 4 5 6 7 8 9 10 11 12 7
Machine running at Y Machine running at Y If "N" at start or end of shift, record
start of shift? N end of shift? N reason in box #1 or #12 8
Kicks (# last HR)
9
Total Kicks
Downtime (for
Hr)
10
Speed
(kicks/min)
11
Tgt Speed 252 252 252 252 252 252 252 252 252 252 252 252
S 15
Target Actual Available at Set Up? (Y/N)
E 15 S Order Time Time Stock Ink Plates Cut Die Paperwork Pallets # BOX
T 15 E 15
U T
15 15
P U
S 15 15
P
15 S 15
15 15
Initial
Supv
63,800
Hr
58,000
1
52,200
46,400 2
40,600
3
Total Kicks Made
34,800
29,000
4
23,200
17,400 5
11,600
5,800 6
HOUR 1 1 2 3 4 5 6 7 8 9 10 11 12 7
Machine running at Y Machine running at Y If "N" at start or end of shift, record
start of shift? N end of shift? N reason in box #1 or #12 8
Kicks (# last HR)
9
Total Kicks
Downtime (for
Hr)
10
Speed
(kicks/min)
11
Tgt Speed 252 252 252 252 252 252 252 252 252 252 252 252
S 15
Target Actual Available at Set Up? (Y/N)
E 15 S Order Time Time Stock Ink Plates Cut Die Paperwork Pallets # BOX
T 15 E 15
U T
15 15
P U
S 15 15
P
15 S 15
15 15
Initial
Supv
63,800
Hr
58,000
1
52,200
46,400 2
40,600
3
Total Kicks Made
34,800
29,000
4
23,200
17,400 5
11,600
5,800 6
HOUR 1 1 2 3 4 5 6 7 8 9 10 11 12 7
Machine running at Y Machine running at Y If "N" at start or end of shift, record
start of shift? N end of shift? N reason in box #1 or #12 8
Kicks (# last HR)
9
Total Kicks
Downtime (for
Hr)
10
Speed
(kicks/min)
11
Tgt Speed 252 252 252 252 252 252 252 252 252 252 252 252
S 15
Target Actual Available at Set Up? (Y/N)
E 15 S Order Time Time Stock Ink Plates Cut Die Paperwork Pallets # BOX
T 15 E 15
U T
15 15
P U
S 15 15
P
15 S 15
15 15
Description
Clear
target for Green if above
each goal, Red if
area below goal
Single-
person
owner
Due Dates
Our aim is to generate at least one action for each area in within 48 hours
the red …and then complete them within 48 hours!
Systematic,
Chronic and High
Complexity
problems can be
elevated to weekly
steering
• Must Attend:
– Superintendent (leader in morning and
afternoon)
– Outgoing supervisors (conv & corr)
– Incoming supervisors (conv & corr)
– Maintenance supervisor / representative
• Optional Attendees:
– Scheduler, Customer Service Rep, Plant
Manager
• When:
– Soon after shift change
– Allow enough time for outgoing supervisors to update
the board and incoming supervisors to get machines
started
– Last no longer than 15 minutes
• Where:
– In a visible, public location (no sitting)
– Quiet enough to hear each other
– In front of the Shift Handover Board
• Actions!
– That will help the performance of the machines in the next 24
hours.
• Elevating tougher problems
– Get the to the Production Manager as soon as possible
• Recognition
– Recognition should start with installation of the board
– Award performance publicly
– Recognize crews that meet their targets
• Mindsets
and
capabilities
• Model • Model
Checklists for
supervisors may
include items not part
core OPX but are still
their responsibility
e.g., safety
– Coaches work through supervisor – Coaches do not tell hourly staff what
to do, press buttons or pick up board
.
– Supervisor coaches spend most of – A hands off approach with limited
shift with supervisors and leadership interactions
coaches spend ~25% of day with
superintendent and plant manager
– Coaches should expect feedback on – Become defensive when questioned
coaching performance from OPX – treat as a learning experience
leadership
– Complete daily coaching logs to – Hold communications from team
share performanceSmurfit-Stone
issues Container * Operational Excellence Boot Camp 52
A DAILY COACHING SUMMARY TRACKS PROGRESS AND PROVIDES
INFORMATION TO PLANT LEADERSHIP
• Drives a common focus on hitting
new throughput targets – green
target is hit, red is under target
• Identify
any help
required
by OPX
team
• How
supervisor is
performing
Smurfit-Stone Container * Operational Excellence Boot Camp 53
Influencing techniques
• Stating • Avoiding
• Legitimizing • Intimidating
• Persuading logically • Threatening
• Appealing to friendship • Manipulating
• Socializing
• Exchanging
• Consulting
• Appealing to values
• Modeling
• Building alliances
*Although these techniques can be effective, they can damage relationships and doom future
influencing attempts Smurfit-Stone Container * Operational Excellence Boot Camp 56
Source: Interpersonal and Interactive Skills, Lore International Institute, Inc., 1996
SOURCES OF ORGANIZATIONAL POWER
– Status, position, or authority
Role
– Ability to make decisions affecting others’ work or careers
– Power to reward or punish
– Ability to give or withhold recognition, promotions, or favours
Description
Background • Maintenance is the backbone of any successful manufacturing operation and
a large “enabler” of increased throughput. Poor maintenance practices lead
to substandard machine utilization, poor quality product, and wasted SSCC
funds
• Standardized procedures for the reporting and completion of work orders are
not being consistently followed, resulting in poor recording of machine
breakdown issues and inhibiting scheduling of plant assets
• Repair part storeroom organization is poor and represents wasted time and
plant resources
Work Order • Work orders used to report, assign and • Work Orders are underutilized
Utilization schedule all non-preventive maintenance • Maintenance leadership not enforcing “no work
• Operators trained in how to fill them out and without a work order mentality”
supervisors should be ensuring that the proper • Plant personnel do not see value in functioning
work order process flow is followed work order system
Work Order • The plant has a process in place for the • Machine centers have no idea how to fill out work
Process submission, approval, prioritization, and orders and are not expected to
Flow assignment of work orders • Maintenance leadership assigns and completes
• Feedback loops are in place to inform corrective maintenance without using work orders
machine centers of the status of their • Machine centers and floor leadership have little
machines’ work orders confidence in work order system they consider a
• Plant leadership is regularly updated with the “black hole”, since they never hear back on
status of all open work orders and associated status of submitted work orders
required parts
Equipment • Completed work orders form the material • Although electronic database captures some
History history for a piece of machinery machine history, plant relies on the memory of its
• Whether retained electronically in a personnel for machine history
spreadsheet, in a logbook for a machine, or • Limited time for administrative work by
as a collection of completed work orders, maintenance leadership, little computer sills
some history is maintained to troubleshoot among technicians
repeated issues causing machine downtime
PM • PMs are done on the day they are scheduled • PM process has been done incorrectly for so long
execution at the time they are scheduled, and are only people are resigned to continue it
switched by the Plant Manager under • Maintenance leadership does not have a structured
extreme circumstances approach to rebuild their PM program
• PMs and work orders start on time, finish • Plant leadership wants to switch PM times due to
when all maintenance is complete, and are “flexibility concerns”
followed immediately by machine startup • If maintenance is complete, machine sits idle until the
end of the PM period instead of being started back
up
PM design • PMs are a hybrid of: OEM • Sparse records of machine maintenance history
recommendations, operator/maintenance • OEM technical documents missing for some
input, and material history machines
• PMs designed to prevent the major causes • Some OEM-provided checklists are little more than
of machine breakdown and slower than a lubrication schedule
required speed • Plant is unwilling to “lend” operators to workshop
process, or scheduled operators don’t show up
Operator • Operators share with the maintenance • Hard to train operators on basic maintenance
involvement department the responsibility of keeping their • Union issues (i.e. change to job description)
machine in top working order. • Operators and maintenance not used to “working”
• Cleaning of the machine is conducted during on machine at the same time
weekly cleanups, not during the PM time.
• Operators are involved in the development
of the PM sheets, as their day-to-day
experience provides valuable insights
Training • All OPX plants emphasize the following • Maintenance technicians have widely
when it comes to the training of their varying skill levels
maintenance personnel • No training plan in place to improve skills
– Basic technical skills and training of young technicians
– Knowledge of OEM Equipment • Manning centered around wants of
– Effective placement of their technicians rather than needs of plant
technicians to meet both plant and
training needs
• Additional detail can be found in the See performance management section on
OPX playbook maintenance meetings and dialogues for
further detail on maintenance scheduling
New Meetings/interactions
New Reports + tools
Performance dialogue cascade
Frequency
On-shift/real-time Shift Daily Weekly Monthly
Plant Manager +
Superintendent
Maintenance
planning &
Organizational level
prioritization
Maintenance
Shift work plan
Supervisors
Review work-
orders and
Planning
determine root-
board
Maintenance causes
Techs
Parts
availability file
Work-order
board
Work orders Work orders
Operators developed completed file
Provides crews with Planning for day, next day Posted at machine
prioritized work for shift and discussion of major centers to allow operators
issues to review progress
Inputs
• PM bottlenecks, opportunities from
Superintendent
• Parts availability log
*Once the system is in place consider planningContainer
Smurfit-Stone one week in advance Excellence
* Operational rather than Boot
dailyCamp 67
Equipment Strategy Workshop
Operators
• More time running boxes
• More predictable schedules
• Job made easier
• Higher throughput
• More time running
machines
• Less scheduled •More, better,
overtime (fewer
weekends worked) Maintenance faster….
Supervisors • Money freed up for Department •Be competitive in
improvements • Frees up budget used the industry
• Less time for shipping (~50%)
fighting fires • Higher utilization of
• Meet volume maintenance
goals personnel
• Minimize • Not pulled off PMs
waste to fix breakdowns
elsewhere
Identification Development of
Root cause analysis Definition of operator
of major causes daily/weekly/monthly
and action steps responsibilities
of failure PM items
Reason • Because so little • Once root causes • OEM specs and group • Operators currently
maintenance is currently identified, root causes input used to set correct have little knowledge of
unplanned, root causes identified and maintenance schedule failure modes and feel
of frequent failures must prioritized in order of that both addresses root little sense of
be identified. impact. causes and minimizes ownership for the
machine downtime. machine
Product Tree diagram of major Listing of steps to Formal division of daily, Detailed descriptions of
failure modes, sorted by address top causes of weekly, and monthly required cleaning and
component, used to set failure, helping establish maintenance checks, maintenance to be
preventive maintenance priorities based on OEM specs performed by operator
priorities. and group input
Wrong/mismatched Belt
Leaks
Solenoid failure
Leaks
Dirty
Photo Eye
Blocked
Smurfit-Stone Container * Operational Excellence Boot Camp 74
ROOT CAUSE ANALYSIS
Purpose: Once major causes of equipment breakdown are identified by component and
root cause, they can be assigned a corrective action that fixes root cause in the future
Example 3 Rounded bolt Maintenance time Poor tooling, not •Make regular PM
heads on pull wasted to drill out changing often to change bolts
collars bolts enough •Regular
inspection/replace
ment of tooling
Ideally potential fix should result in a PM of agreed-
upon frequency, a new corrective work order to fix
problem, inclusion into operator basic care
Smurfit-Stone Container * Operational Excellence Boot Camp 75
PRIORITIZATION OF FAILURE MODES
Should be done in order of impact on production
High
Probability of Failure
Low High
Impact on Production
Daily OC - FFG
Time
Shutdown During Required( mi
? Setup? n) Signature Issues Discovered
Prefeeder
Feed Table
• Break into two groups. One group from starch to stacker, the
other from stacker to starch, write down all mechanical or
Process process problems observed
• Time: ~30min tour and ~15min debrief
• Tools: Paper and pen
Back- • Poor quality coming off the corrugator was impacting converting machine
ground performance
Using the Toolkit: Audit the current process and see how it compares to the Desired State. Areas lacking should be addressed on a priority basis.
Impact Levels are based on following:
• A = Is likely to directly affect throughput on downstream machines
• B = Results in minimal segregating at the converting machine
• C = Results in extra work at the output of the corrugator
• D = Is an external enabler to sustained corrugator quality
Current
Topic Ideal End State Impact State
Corrugator 1. What are the biggest sources of poor quality in • No low-quality sheets reach the converting • A
the WIP area? machines
quality output
2. Does corrugator stack quality meet standards • Stack quality does not inhibit converting • A
or inhibit converting performance? throughput
3. Who is perceived to “own” sheets lying in the • The corrugator “owns” the sheets until it is fed • D
WIP area? into the converting machines
4. Is there a method of communicating poor • There is rapid and quantitative feedback
quality from the converting machines to the regarding poor quality from the converting
corrugator? machines to the corrugator
• D
Quality 1. Does the plant’s quality office maintain • Crews receive regular training on quality
measurement documented training for crews on quality measurement, the effect of poor quality, and • D
checks, including the use of Plant Test specific operations that affect quality
Methods?
2. Are plant operators conducting quality checks • Quality checks are conducted during corrugator
during corrugator operations operations, not to interfere with corrugator • A
throughput
3. Are quality standards posted in the vicinity of the • Quality standards are visible to all pertinent
operators? operators
4. Do operators have the knowledge and tools • Measurement tools and procedures are placed • D
necessary to ensure board quality? within working distance of the operation (5S)
5. Does the supervisor understand quality • Supervisors are active in ensuring corrugator • D
standards, measurement techniques, and quality
how to observe an operator’s performance? • A
CORRUGATOR PROCESS DIAGNOSTIC (1 of 2) DIAGNOSTIC
Objective: Rapid diagnostic results in identification and repair of mechanical and process issues affecting corrugator output, both quality and
throughput related
Using the Toolkit: Audit the current process and see how it compares to the Desired State. Areas lacking should be addressed on a priority basis.
Impact Levels are based on following:
•A = Major repair is needed to meet quality or throughput standards OR enables follow-on critical repairs to be done
•B = Repair or enhancements that are likely to affect throughput and threaten the ability to hit throughput targets. Likely a chronic source of downtime
•C = May be a longer-term repair, does not affect throughput within the OPX timeframe
Current
Topic Ideal End State Impact State
• B
4. Other systems
• A/B
Smurfit-Stone Container * Operational Excellence Boot Camp 86
CORRUGATOR PROCESS DIAGNOSTIC (2 of 2) DIAGNOSTIC
Current
Topic Ideal End State Impact State
1. Machine cleanliness
Other /
• Machine cleanliness is maintained so that
General
material abnormalities may be detected early • B
(e.g. no splattered adhesive hiding rust spot
2. Machine structural stability from small steam leak)
• Machine frame provides stability for all
3. Bearings and motors operations • A
• Bearings are lubricated and not worn; motors
are clean and run as expected • A
From To
Board
Quality
Stack
Quality
Locally developed
procedure
Description
Back- • FI had already established some habits of pushing speed, and rolling shift performance
ground into supervisor dialogues
• Repeatable speed trial process did not exist
• Downtime recording did exist, but there was no active analysis of results, and no
incorporation into performance management
• No existing procedures in use for typical corrugator operations like splicing, butt-roll
management, automatic-order-change (AOC)
• If procedures existed, they were used infrequently, with no enforcement by supervisors
• “Circles” had not been used on corrugator to date
• No equivalent to “Rainbows” exists for corrugator (exception –Rainbows for the triplex)
Using the Toolkit: Audit the current process and see how it compares to the Desired State. Areas lacking should be addressed on a priority basis.
Impact Levels are based on following:
2. Speed Trials
• B
• A
• A
• B
• B
• A
Using the Toolkit: Audit the current process and see how it compares to the Desired State. Areas lacking should be addressed on a priority basis.
Impact Levels are based on following:
• Ensure basic quality control has been • Stable starting point in place
achieved
Pre-work • Identify “hot-running” board combinations • Identify board combinations to include in
speed trial data collection
• Make speed trial results boards for both • Provide supervisor and operators the
supervisors and operators (physical baseline parameters at which to run all
Post the construction as appropriate to the board combos
Results environment) • Provides confidence in running at high
speed
• Speed trial results become part of • Faster operations while meeting quality
performance and speed expectations for standards
Supervisors
crews’ performance
reinforce
Speed
Board
Downtime
Monitoring
Overhead
Management
(LED’s)
1 2 3 4 5
Description • Establish prerequisites • Create baseline • Design end-state • Execute through • Check-in and follow-
• Fill data requests • Prioritize efforts • Create workplan plant team on coaching
• Introductory training • Establish unit • Plan for area • Upward feedback on
specific targets implementation OPX
Key activities 1.1• Collect data & aid 2.1• Develop overall 3.1• Develop master 4.1• Rollout and re- 5.1• Follow-up
prerequisites intro plant baseline implementation fine the phased performance
(MIFA & OEE) plan OPX elements dialogues (area
1.2• Plan out important and plant)
meetings and 2.2• Plant opportunity 3.2• Tailor OPX ele- 4.2• Rollout the
reviews assessment of ments to suit performance 5.2• OPX team circle
OPX elements local plant con- management back for audit
1.3• Prepare local man- ditions system and potential
agement for OPX 2.3• Prioritization of Kaizen events
OPX element 3.3• Develop detailed 4.3• Coach & train
1.4• Establish the team, implementation workstreams plant 5.3• Update OPX
organise logistics action plans transformation
and provide OPX 2.4• Set plant perfor- approach and
team training mance targets playbook based
on lessons
Learned
Key individuals •RVP and AOMs •OPX team •OPX team •Plant team •Plant management
•Plant management •Plant team •OPX team •RMMs
•OPX leads •OPX PMO
Workplace WIP organization Low Med • Poor WIP organisation causing lost stock
Organization
Indirect
M/c center Med Low
• Will aid sustainability but not critical
Support function Med Low
M&C: Coach Low High • Supervisors and mgnt not driving throughput
and training
Smurfit-Stone Container * Operational Excellence Boot Camp 103
MANNING DIAGNOSTIC EXAMPLE
Sample Issue
• P erf ormance focus of staff is low as supervisors not driving any sense of urgency and plant management not holding supervisors accountable for poor perf ormance
(L,M,H)
• Excessive absenteeism H
Staff not • No sick cover or shift cover policy
available to • Excessive training undertaken
work • Annual leave issues?
A diagnostic template
will be provided
• Meal breaks longer than planned H
Staff not at for most elements H
• Break cover process not in place
machine L
• Shifts handover process failing
• Operators repeatedly pulled away from
m/c during shift time for mgnt issues or
meetings
M
Staff idle or • Waiting for another operator to run
time is • Waiting on other personnel to fix
wasted machine or make a decision
• Waiting on materials
• Lack of urgency to perform
1 2 3 4 5
Description • Establish prerequisites • Create baseline • Design end-state • Execute through • Check-in and follow-
• Fill data requests • Prioritize efforts • Create workplan plant team on coaching
• Introductory training • Establish unit • Plan for area • Upward feedback on
specific targets implementation OPX
Key activities 1.1• Collect data & aid 2.1• Develop overall 3.1• Develop master 4.1• Rollout and re- 5.1• Follow-up
prerequisites intro plant baseline implementation fine the phased performance
(MIFA & OEE) plan OPX elements dialogues (area
1.2• Plan out important and plant)
meetings and 2.2• Plant opportunity 3.2• Tailor OPX ele- 4.2• Rollout the
reviews assessment of ments to suit performance 5.2• OPX team circle
OPX elements local plant con- management back for audit
1.3• Prepare local man- ditions system and potential
agement for OPX 2.3• Prioritization of Kaizen events
OPX element 3.3• Develop detailed 4.3• Coach & train
1.4• Establish the team, implementation workstreams plant 5.3• Update OPX
organise logistics action plans transformation
and provide OPX 2.4• Set plant perfor- approach and
team training mance targets playbook based
on lessons
Learned
Key individuals •RVP and AOMs •OPX team •OPX team •Plant team •Plant management
•Plant management •Plant team •OPX team •RMMs
•OPX leads •OPX PMO
• Obtain/order materials
3.4 SC review (develop material) OPX team lead
Purpose • Get a hands-on feel for the diagnostic, end-products and performance culture required
within this team (roll-up the sleeves and make things happen quickly)
• Test run some of the material the pilot plant has developed
• Get to know other team members
• Provide this area a good head start in assessing opportunities in two of their plants
• Remember what it will feel like for the plant to have 10-15 OPX team
members crashing in for the day
• Don’t worry about trying to develop the perfect answer; you are doing what
we’d expect in 1-2 weeks in less than a day
• Be very end product orientated- only focus on the slide(s) you need to
complete for the presentation
• Separate into the two groups that will go to each plant and
then:
Process – Conduct a brief intro of the plant
– Divide the work streams (and hand out ghost pages)
– Discuss logistics (when, where, how, etc)