The Use of Operational Data to Improve Results

74
The Use of Operational The Use of Operational Data to Improve Results Data to Improve Results Eric Allen Data Driven Manufacturing LLC DataDrivenManufacturing.c om

description

This presentation was originally developed over 10 years ago to highlight ways to make use of data in manufacturing to improve operational results. Key points include: Data is an important tool in reducing cost. We often focus on less important data. The things we measure for result improvement are the same as those we should measure for start-ups. Engineering plays a key role in the design of processes, the acquisition of data, and the level of long-term costs It takes a lot of data to tell the whole story. Written by Eric Allen of Data Driven Manufacturing, this presentation is meant to give an overview to those starting down a path to use data for improving manufacturing results.

Transcript of The Use of Operational Data to Improve Results

Page 1: The Use of Operational Data to Improve Results

The Use of Operational Data The Use of Operational Data to Improve Resultsto Improve Results

Eric Allen

Data Driven Manufacturing LLC

DataDrivenManufacturing.com

Page 2: The Use of Operational Data to Improve Results

AgendaAgenda

Background on use of dataRanking data by importanceHow data is usedData, Design, and Start-upsRecommendations

Page 3: The Use of Operational Data to Improve Results

Introduction Introduction Data is an important tool in reducing costWe often focus on less important dataThe things we measure for result improvement are

the same as those we should measure for start-upsEngineering plays a key role in the design of

processes, the acquisition of data, and the level of long-term costs

It takes a lot of data to tell the whole story

Page 4: The Use of Operational Data to Improve Results

The Goal of Data is… ???The Goal of Data is… ???

Page 5: The Use of Operational Data to Improve Results

VocabularyVocabulary

Uptime/DowntimeStopMTTR/MTBFAvailabilityOEE

Page 6: The Use of Operational Data to Improve Results

Uptime and DowntimeUptime and Downtime

Uptime is the total time the line is runningDowntime is the total time the line is downA Stop is every event when the line stops

running, no matter how long it has been running or why it stopped

Overall Equipment Effectiveness (OEE) is a standard measure that quantifies the production made as a percentage of what was possible to have been made.

Page 7: The Use of Operational Data to Improve Results

MTTR & MTBFMTTR & MTBF

Mean time to repairMTTR = downtime / stops

____________________Mean time between failuresMTBF = uptime / stops

Page 8: The Use of Operational Data to Improve Results

AvailablityAvailablity

Availability is the percent of time the line is running.

Availability = uptime / scheduled timeAvailability = MTBF / (MTBF + MTTR)OEE = Availability - Uptime Losses

Page 9: The Use of Operational Data to Improve Results

Overall Equipment EffectivenessOverall Equipment Effectiveness

OEE = Availability x Rate Performance x %Acceptable Quality, a holistic measure of Efficiency or Reliability.

Rate Performance = Actual Rate / Planned Rate, a measure of Rate Loss/Gain

% Acceptable Quality= Amount of Shippable Product / All product produced, a measure of Quality Loss or “Scrap”

Another way to calculate OEE is to divide quality product made by the the ideal amount that could have been made during the scheduled time.

Page 10: The Use of Operational Data to Improve Results

Traditional OEE ImprovementTraditional OEE Improvement

R eliab ility L osses

U n it O p 3 AL oss = 4 %

U n it O p 3 BL oss = 4 %

U n it O p 5L oss = 1 %

U n it O p 4L oss = 6 %

U n it O p 2L oss = 3 %

U n it O p 1L oss = 5 %

L in e B L in e C

P rod u c t F eedL oss = 2 %

Track Downtime for each unit op

Pareto LossesFocus on biggest

Downtime unit opGo after chunks of

downtimeGet operators to fix it

faster (MTTR)0%

2%

4%

6% Unit Op 4

Unit Op 1

Unit Op 3

Unit Op 2

Supply

Unit Op 5

Page 11: The Use of Operational Data to Improve Results

The Goal of Data is…The Goal of Data is…

to Reduce Downtime???

Page 12: The Use of Operational Data to Improve Results

Downtime LossesDowntime Losses

BreakdownsMinor StopsPlanned MaintenanceChangeoversLunches/Breaks/MeetingsMaterial Supply

Page 13: The Use of Operational Data to Improve Results

Downtime LossesDowntime Losses

BreakdownsMinor StopsPlanned MaintenanceChangeoversLunches/Breaks/MeetingsMaterial Supply

Equipment Specific Stops- The rest are associated with the whole line.

Page 14: The Use of Operational Data to Improve Results

Downtime LossesDowntime Losses

BreakdownsMinor StopsPlanned MaintenanceChangeoversLunches/Breaks/MeetingsMaterial Supply

Since Minor Stops are shorter in duration than all other stops, reducing the number of minors stops will increase MTTR.

Page 15: The Use of Operational Data to Improve Results

Downtime LossesDowntime Losses

BreakdownsMinor StopsPlanned MaintenanceChangeoversLunches/Breaks/MeetingsMaterial Supply

Eliminate with Equipment Design, Prevention, and Planning

Page 16: The Use of Operational Data to Improve Results

Downtime LossesDowntime Losses

BreakdownsMinor StopsPlanned MaintenanceChangeoversLunches/Breaks/MeetingsMaterial Supply

Reduce with planning and skills. Of all downtime, only these two are truly speed dependent. (With proper design, most of this work can be done during uptime anyway.)

Page 17: The Use of Operational Data to Improve Results

OEE and STOPSOEE and STOPSOEE

COMPONENTSSHIFT

COMPONENTSIN-PROCESS MEASURES SENSITIVITY

RuntimeMTBF (Variable)

Availability StopsMTTR (Constant

Downtime w/in Range)% OEE

% Scrap (Constant ~ 1%)

Rate Loss (Constantexcept start-up)

Page 18: The Use of Operational Data to Improve Results

OEE and STOPSOEE and STOPS

Downtime Focus only addresses part of Reliability

OEE COMPONENTS

SHIFT COMPONENTS

IN-PROCESS MEASURES SENSITIVITY

RuntimeMTBF (Variable)

Availability StopsMTTR (Constant

Downtime w/in Range)% OEE

% Scrap (Constant ~ 1%)

Rate Loss (Constantexcept start-up)

Page 19: The Use of Operational Data to Improve Results

OEE and STOPSOEE and STOPSOVERALL EQUIPMENT EFFECTIVENESS & STOPS

OEE COMPONENTS

SHIFT COMPONENTS

IN-PROCESS MEASURES SENSITIVITY LEVER

RuntimeMTBF (Variable) Stop Elimination

Availability StopsMTTR (Constant Stop Elimination

Downtime w/in Range)% OEE

% Scrap (Constant ~ 1%) Stop Elimination

Rate Loss (Constant Stop Eliminationexcept start-up)

Page 20: The Use of Operational Data to Improve Results

OEE and STOPSOEE and STOPS

Stop Elimination addresses all components of Reliability

OVERALL EQUIPMENT EFFECTIVENESS & STOPS

OEE COMPONENTS

SHIFT COMPONENTS

IN-PROCESS MEASURES SENSITIVITY LEVER

RuntimeMTBF (Variable) Stop Elimination

Availability StopsMTTR (Constant Stop Elimination

Downtime w/in Range)% OEE

% Scrap (Constant ~ 1%) Stop Elimination

Rate Loss (Constant Stop Eliminationexcept start-up)

Page 21: The Use of Operational Data to Improve Results

Downtime Reduction, Stop Downtime Reduction, Stop Elimination, What’s the difference?Elimination, What’s the difference?

Focus on Time Get it back up Repair Skills Focus

Focus on Events Stay down until fixed Root Cause

Elimination

Downtime Stops

Page 22: The Use of Operational Data to Improve Results

The Goal of Data is…The Goal of Data is…

to Reduce Downtime

to Eliminate Stops???

Page 23: The Use of Operational Data to Improve Results

OEE and STOPSOEE and STOPS

Stop Elimination won’t fix uptime losses

OVERALL EQUIPMENT EFFECTIVENESS & STOPS

OEE COMPONENTS

SHIFT COMPONENTS

IN-PROCESS MEASURES SENSITIVITY LEVER

RuntimeMTBF (Variable) Stop Elimination

Availability StopsMTTR (Constant Stop Elimination

Downtime w/in Range)% OEE

% Scrap (Constant ~ 1%) Stop Elimination

Rate Loss (Constant Stop Eliminationexcept start-up)

Page 24: The Use of Operational Data to Improve Results

Uptime LossesUptime Losses

Scrap (Destructive Quality Sampling & Rework)

Rate Losses (speed ramp-ups at start-up and running off target speeds at steady state)

Empty or missed products (could be rate or scrap loss depending on situation)

Page 25: The Use of Operational Data to Improve Results

Quality Samples, Defective Quality Samples, Defective Product, and Rate Can Be Product, and Rate Can Be Hidden LossesHidden Losses

Page 26: The Use of Operational Data to Improve Results

10.2%

11.5%

78.3%

Dow ntime

Uptime Losses

Making Good Product(%OEE)

Uptime Losses Can be Uptime Losses Can be SignificantSignificant

Source: Case Study- Oct ‘99

Page 27: The Use of Operational Data to Improve Results

Uptime Losses, Stops,Uptime Losses, Stops,What Else?What Else?

Eliminate Stops & Uptime Losses to Increase PR

Page 28: The Use of Operational Data to Improve Results

The Goal of Data is…The Goal of Data is…

to Reduce Downtime

to Eliminate Stops???

to Eliminate OEE Losses???

Page 29: The Use of Operational Data to Improve Results

Show Me the Money!Show Me the Money!

We are in business to make money, not OEE

Page 30: The Use of Operational Data to Improve Results

Our Biggest On-going Cost Our Biggest On-going Cost is...is...

People!

Page 31: The Use of Operational Data to Improve Results

Stops and Touches Tie Stops and Touches Tie Operators to EquipmentOperators to Equipment

Unit Op A

50 stops/shiftUnit Op A

30 stops/shift

Unit Op A

60 stops/shift

Unit Op B

75 stops/shift

Page 32: The Use of Operational Data to Improve Results

Eliminating Stops Improves Eliminating Stops Improves ProductivityProductivity

Every stop requires operator effort.

The more stops there are, the closer the operator is tied to the line.

The closer the operator is tied to each unit operation, the more operators are required.

Page 33: The Use of Operational Data to Improve Results

TouchesTouches

Operators often adjust and assist the line to keep it from stopping

Often these assists are jam clearsMany adjustments can be automatedFind ways to detect and count

Page 34: The Use of Operational Data to Improve Results

How Do You Eliminate?How Do You Eliminate?

StopsTouchesScrapRate Loss

AdjustmentsAssists

Page 35: The Use of Operational Data to Improve Results

How Do You Eliminate?How Do You Eliminate?

StopsTouchesScrapRate Loss

Stabilize the Process

AdjustmentsAssists

Page 36: The Use of Operational Data to Improve Results

All processes vary-All processes vary-The challenge is to minimizeThe challenge is to minimize

Steady State Variation- when the line is running normally, how much does the process vary and why?

Start-up Variation- during ramp-up of the equipment, what is impacted and how can the variation be reduced in magnitude and time?

Process Upsets- How do sudden events (splices,batch changes, etc.) affect stability?

Page 37: The Use of Operational Data to Improve Results

What Varies?What Varies?

Materials Equipment Utilities Control Systems Environment Set Points Operators Cleanliness

Page 38: The Use of Operational Data to Improve Results

Eliminating VariationEliminating Variation

Use stops and touch data to determine area where variation is impacting

Investigate process for variation

Develop methods to eliminate or control the source

Page 39: The Use of Operational Data to Improve Results

Stability gets ResultsStability gets Results

Quality is improved with lower Standard Deviation and reduced defects

Touches are needed less as adjustments are not needed

Most stops can be traced to instability in part of the process

More stable processes need less sampling

Page 40: The Use of Operational Data to Improve Results

Don’t forget ThroughputDon’t forget Throughput

OEEOEE

==

ThroughputThroughput

Know your rate limiter(s).

List them.

Study them.

Stabilize them.

Speed them up.

Page 41: The Use of Operational Data to Improve Results

Cost = Cost =

Throughput Throughput xx Productivity Productivity Rate Stops uptime Losses

Material Handling Quality Sampling Touches Equipment Geography

Page 42: The Use of Operational Data to Improve Results

The Goal of Data is…The Goal of Data is…

to Reduce Downtime

to Eliminate Stops???

to Eliminate OEE Losses???

to Reduce Cost!

Page 43: The Use of Operational Data to Improve Results

Data Overload!Data Overload!What Data is Most Important?What Data is Most Important?

Page 44: The Use of Operational Data to Improve Results

1. Quality1. Quality

Without quality, there is no reliabilityGet quality data easy to access and analyzeAutomate quality data collectionGet in process data to replace destructive

finished product samplingIdeally, incorporate quality data into same

system as Reliability measures

Page 45: The Use of Operational Data to Improve Results

2. Count Stops2. Count Stops

Line StopsUnit Op Stops

Eliminating Stops improves every aspect of OEE

Stops are the best in-process measure of progress of work

Page 46: The Use of Operational Data to Improve Results

3. Uptime Losses3. Uptime Losses

Track Availability vs. OEESeparate Rate from ScrapSplit Quality Sampling Scrap from Quality

Defect Scrap

Page 47: The Use of Operational Data to Improve Results

4. Process Stability Measures4. Process Stability Measures

More in-process data leads to faster improvement capability and root cause analysis

Track all variable data (pressures, temperatures, tensions, weights, speeds, amps, etc.)- Install transducers to get data

Utilize to discover sources of variationEliminate or use as feedback to other parts of

the process to reduce

Page 48: The Use of Operational Data to Improve Results

5. Causes5. Causes

Stop CausesReject/Scrap CausesCauses are hard to determine automatically

but valuable to know

Page 49: The Use of Operational Data to Improve Results

6. Other Data6. Other Data

TouchesDowntime

Page 50: The Use of Operational Data to Improve Results

Ranking of Data ImportanceRanking of Data Importance

Quality Stop CountsUptime LossesProcess Stability MeasuresCausesTouches and Downtime

Page 51: The Use of Operational Data to Improve Results

Data can be collected and Data can be collected and used many waysused many ways

PLC programming is critical to capturing events for operator display and long-term storage.

Find effective ways to display data to operator

Store data for long-term trending in databases

Page 52: The Use of Operational Data to Improve Results

Data has many sourcesData has many sources

Counts (stops, starts, products, defects, rejects, cases, touches)

Time (uptime, downtime)Variables (pressures, tensions, temperature,

speeds, currents)Causes (stops, rejects)

Page 53: The Use of Operational Data to Improve Results

Customer is the OperatorCustomer is the Operator

Turret Stops

0

20

40

60

80

100

120

140

160

5/5

-Nite

5/1

2-D

ay

5/2

5-N

ite

6/2

-Day

6/8

-Nite

6/2

1-N

ite

6/2

8-N

ite

7/6

-Day

7/1

3-D

ay

7/1

9-N

ite

7/2

7-N

ite

8/3

-Nite

8/2

4-D

ay

9/1

5-D

ay

9/2

8

10/7

Date

Sto

ps

Stops-Turret System

No Datato Operator

Data Broken out

Page 54: The Use of Operational Data to Improve Results

Data Helps Focus Efforts DailyData Helps Focus Efforts Daily “You get what you measure” Results occur minute-by-

minute and are controlled by operators

With updated data, operators can make good decisions

Use on-line data to eliminate short-term data variation

Page 55: The Use of Operational Data to Improve Results

Use data averages and trends to Use data averages and trends to develop long term improvementsdevelop long term improvements

MTBF shows progress and opportunities in stop reduction

Scrap rates show uptime losses

Variation measures show stability opportunities

?

Page 56: The Use of Operational Data to Improve Results

For Stable OperationsFor Stable OperationsYou need good Design plus You need good Design plus good Process Managementgood Process Management

vs.

Page 57: The Use of Operational Data to Improve Results

Built in Impacts of Design on Built in Impacts of Design on Manufacturing CostManufacturing Cost

Simplicity of Equipment (# of unit ops)Geography- Position of Touch PointsDesigned in Stops/Touches (material changes,

etc.)Data Systems- How much information does the

operator have?Ease of ChangeoverMaintainability- resistance to Breakdowns

Page 58: The Use of Operational Data to Improve Results

Impacts of Process Impacts of Process ManagementManagement

Outage ResolutionIf-Down-Do / Planned InterventionsRun to Target

Page 59: The Use of Operational Data to Improve Results

What does this have to do with What does this have to do with Engineering and Vertical Start-ups?Engineering and Vertical Start-ups?

Design is a critical component of long-term costs

Data is essential to make wise decisions

Vertical start-up tools and targets lead to right methodology if used correctly

Page 60: The Use of Operational Data to Improve Results

Use of Data and ResultsUse of Data and Results in Case Study in Case Study

A multiple unit-operation line used these principles in a rigorous method to make substantial improvement. The following slides show results as measured by the site.

Page 61: The Use of Operational Data to Improve Results

Uptime Results

10.1

13.0

17.3

11.0

18.8

15.4

26.4

24.9

39.4

30.7

34.2

9.18.1 8.1 7.8

10.4 10.29.5

7.7

4.4

6.2

3.6

-

5.0

10.0

15.0

20.0

25.0

30.0

35.0

40.0

De

c-9

8

Ja

n-9

9

Fe

b-9

9

Ma

r-9

9

Ap

r-9

9

Ma

y-9

9

Ju

n-9

9

Ju

l-9

9

Au

g-9

9

Se

p-9

9

Th

is M

on

th

month

min

utes

MTBF

Goal

MTTR

MTBF GOOD

Page 62: The Use of Operational Data to Improve Results

Scrap Results

41.0%

28.7%

21.9%

24.8%

18.2%

20.9%

16.7%

11.0%

8.9%

11.2%

12.9%

0.0%

5.0%

10.0%

15.0%

20.0%

25.0%

30.0%

35.0%

40.0%

45.0%

De

c-9

8

Ja

n-9

9

Fe

b-9

9

Ma

r-9

9

Ap

r-9

9

Ma

y-9

9

Ju

n-9

9

Ju

l-9

9

Au

g-9

9

Se

p-9

9

Th

is M

on

th

month

perc

en

t

Scrap

Goal

GOOD

Page 63: The Use of Operational Data to Improve Results

FFS Stops

0

10

20

30

40

50

60

70

5/10

-Day

5/24

-Nite

6/2-

Day

6/9-

Nite

6/23

-Nite

7/6-

Day

7/14

-Day

7/26

-Nite

8/3-

Nite

8/25

-Day

9/22

10/7

Date

nu

mb

er o

f st

op

s

Stops

6 per. Mov.Avg. (Stops)

Page 64: The Use of Operational Data to Improve Results

Month to Date Results Averages

Turret 1 Turret 2 Turret 3 Turret 4 Turret 5

System MTBF 87.0 49.8 35.4 57.9 45.9 Scrap % 0.4% 1.3% 2.4% 0.8% 1.3%Turret Stops/Day 6.1 12.4 17.8 10.4 13.0 Bag Stops/Day 2.2 2.0 2.5 2.1 2.7

Total Turret Scrap 1.9%MD Phasing Scrap 1.1%No Poly Cut Scrap 2.7%Start-up/Manual Scrap 2.5%Sampling/Quality Scrap 4.0%

Oct 12, ‘99

This type of data was posted and reviewed daily with operators to focus their efforts.

Page 65: The Use of Operational Data to Improve Results

Later ResultsLater Results

Results on this line continued to improve in over time after this case study was completed, and the line became a benchmark for re-application.

OEE routinely exceeded 90%Downtime for unplanned stops generally

was less than 2% of scheduled time.

Page 66: The Use of Operational Data to Improve Results

ReviewReview

Page 67: The Use of Operational Data to Improve Results

Cost = Cost =

Throughput Throughput xx Productivity Productivity Rate Stops uptime Losses

Material Handling Quality Sampling Touches Equipment Geography

Page 68: The Use of Operational Data to Improve Results

OEE and STOPSOEE and STOPS

Stop Elimination addresses all components of Reliability

OVERALL EQUIPMENT EFFECTIVENESS & STOPS

OEE COMPONENTS

SHIFT COMPONENTS

IN-PROCESS MEASURES SENSITIVITY LEVER

RuntimeMTBF (Variable) Stop Elimination

Availability StopsMTTR (Constant Stop Elimination

Downtime w/in Range)% OEE

% Scrap (Constant ~ 1%) Stop Elimination

Rate Loss (Constant Stop Eliminationexcept start-up)

Page 69: The Use of Operational Data to Improve Results

Stops and Touches Tie Stops and Touches Tie Operators to EquipmentOperators to Equipment

Unit Op A

50 stops/shiftUnit Op A

30 stops/shift

Unit Op A

60 stops/shift

Unit Op B

75 stops/shift

Page 70: The Use of Operational Data to Improve Results

Ranking of Data ImportanceRanking of Data Importance

Quality Stop CountsUptime LossesProcess Stability MeasuresCausesTouches and Downtime

Page 71: The Use of Operational Data to Improve Results

Engineering and Vertical Start-upsEngineering and Vertical Start-ups

Design is a critical component of long-term costs

Data is essential to make wise decisions

Vertical Start-up tools and targets lead to right methodology if used correctly

Page 72: The Use of Operational Data to Improve Results

SummarySummary

Downtime data is not nearly as important as many other data types

Focus data systems to reduce costsGet real-time data to operatorsProcess Stability reduces all lossesDesign and Process Management combine

to produce results at start-up and long-term

Page 73: The Use of Operational Data to Improve Results

Specific RecommendationsSpecific Recommendations

Focus on Quality data to reduce variation and sampling losses

Focus on Stops (especially in unit ops) to improve OEE and productivity

Include productivity considerations and data capture ability in design efforts

Get easy to use data to operators

Page 74: The Use of Operational Data to Improve Results

Feedback?Feedback?

Send Email to [email protected]