Process Cycle Efficiency (PCE)

What is a Process?

A process is an systematic activity comprising of smaller activities that culminate in an outcome — service or product. A process can take up time, space, and resources. All processes can be categorized into the following categories: Value-added, Non-value added but necessary, and Non-value added.

From the Customer’s Perspective:

  1. Value-added: This step in the process adds form, function, and value to the end product and for the customer.
  2. Non-Value-Added: This step does not add form, function, or assist in the finished goods manufacturing of the product.
  3. Non-Value-Added-But-Necessary: This step does not add value, but is a necessary step in the final value-added product.

(2) & (3) naturally create waste, of which there are 7 types:

  1. Over-Production: Producing more than is needed, faster than needed or before needed.
  2. Wait-time: Idle time that occurs when co-dependent events are not synchronized.
  3. Transportation: Any material movement that does not directly support immediate production.
  4. Processing: Redundant effort (production or communication) which adds no value to a product or service.
  5. Inventory: Any supply in excess of process or demand requirements.
  6. Motion: Any movement of people which does not contribute added value to the product or service.
  7. Defect: Repair or rework of a product or service to fulfill customer requirements.

It’s important to understand “Value” in terms of the customer. From the custoemer’s perspective, “Value” could be defined in the form of a question:

Which process steps (and associated costs) do our customers not have to bear?

It’s a revealing question — most companies are glad that they do not have to reveal how their product or service is created, for fear of their inefficient processes and wasteful operations revealed to the customer.  This stance is sometimes aptly called "not revealing how the hotdog is made", amicably referring to the unknown contents of the hotdog.

Process Cycle Efficiency

There is a metric that helps to identify how much of a process is actually value-added.  It requires a few things:

  1. Map the process.
  2. Identify the Value-added steps, non-value added steps, and the non-value added but necessary steps.
  3. Stratify your map according to the items in #2
  4. Add a time dimension to the process steps.

Once you have completed steps (1) – (4), then you can simply calculate how much is actually value-added, as a percentage.  The time for the entire process — end-to-end — is called a cycle time.  To identify the Process Cycle Efficiency, you just divide the value-added time by the cycle time for the process.

Process Cycle Efficiency = (Value-added Time / Cycle Time)

For example, take the hypothetical process below:

process cycle efficiency, lean consumption maps

The process above has a cycle time of 860 seconds.  So, the Process Cycle Efficiency could then be calculated by doing the following:

Process Cycle Efficiency = 182 / 860 = .21, or 21%

In other words, only 21% of the process above is considered value-added to the customer. 

Data like this can help the firm increase their value-added percent to the customer by eliminating or reducing the waste in their process.  Doing this would put the customer first and allow the firm to "get their house in order."  I consider the above excercise to be simple, yet incredibly helpful for the firm to make sure that they provide maximum value to the customer; it’s almost a fudiciary duty to the customer. 

Think about your processes?  How much is really value-added to the customer? 

For articles on queueing theory, time-traps, operations, lean and six sigma, please visit the links below:


Short URL: http://bit.ly/JOma

Share This Post:



  • Digg
  • Facebook
  • del.icio.us
  • Suggest to Techmeme via Twitter
  • StumbleUpon
  • LinkedIn
  • email

2-pizza teams (10)
3 C's (3)
5S (38)
A3 Report (9)
adoption (7)
agile/software (59)
ajax (4)
amazon (53)
apple (3)
apple iphone (7)
axiom (3)
Aza Raskin (9)
backcountry.com (2)
berlin (1)
bill gates (1)
bill marriott (1)
blog tag (1)
book reviews (4)
bullwhip effect (5)
business (394)
business plans (3)
busm361 (13)
BzzAgent (12)
call center and queueing (11)
car buying (2)
Carbonite (1)
change management (5)
chicago (1)
click fraud (1)
click-to-ship (21)
clocky (2)
colin powell (2)
community (2)
company interviews (18)
company interviews (6)
complexity (32)
costs (8)
culture (7)
customer experience (10)
customer obsession (52)
customer recovery function (1)
customer segmentation (8)
customer service (17)
design thinking (14)
digg (4)
drum-buffer-rope (38)
dublin (1)
dynamic systems (24)
eBay (6)
economics (3)
efficiency (4)
ethnography (29)
family (18)
featuritis (15)
flexibility (1)
forecasting (2)
four performance dimensions (2)
Fun With The 2×2 Matrix (1)
game theory (7)
Gemba (67)
genchi genbutsu (68)
general (135)
germany (1)
google (15)
heijunka (65)
holidays (1)
hoshin kanri (1)
how to be a human (1)
IDEO (2)
image uploading (1)
iphone (5)
ishikawa (69)
IT at Toyota (67)
just-in-time (4)
kaizen (4)
kanban (46)
law of instinct (1)
Leadership (43)
lean (165)
Lean Consumption Maps (98)
learning curve (1)
licketyship (1)
mark cuban (1)
martin luther king (1)
mary poppendieck (1)
metrics (73)
microsoft (6)
milton friedman (1)
moving average (1)
muda (68)
nba fines (1)
net promoter score (nps) (1)
obeya (39)
Off-Topic (1)
onstar (1)
operations (108)
pageviews (3)
pareto principle (39)
patent (1)
peanut butter manifesto (2)
philosophy (3)
Poka-Yoke (6)
poppendieck (3)
powerpoint sucks (2)
private equity (4)
process measures (6)
product development (20)
productivity (4)
quality (41)
quasimodal design (1)
queueing theory (41)
Raffle (1)
rational choice (2)
regression analysis (18)
respect for people (6)
root cause analysis (60)
sarah+palin (2)
seth godin (1)
simplicity principle (10)
six sigma (128)
snowboarding (2)
social media (3)
spam (1)
statistical process control (46)
strategy (46)
suburban (1)
supply chain (24)
takt time (8)
teaching (2)
team size (9)
technology (104)
the beer distribution game (1)
the profit tree (7)
The Visual Factory (11)
theory of constraints (41)
time (2)
timeline (3)
tony+hsieh (11)
toyota (75)
travel (1)
trump bankruptcy (1)
turnaround (5)
twitter (8)
uspto (1)
utah deal flow (2)
variation (69)
venture capital (1)
Visual Management (11)
waste (59)
website traffic (2)
Wing Chun (2)
wisdom of crowds (1)
wisdom teeth (1)
word-of-mouth marketing (18)
yahoo (2)
zappos.com (12)
zero defects (3)

WP Cumulus Flash tag cloud by Roy Tanck and Luke Morton requires Flash Player 9 or better.


If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.

Comments

[...] Process Cycle Efficiency (… [...]

Leave a comment

(required)

(required)


Additional comments powered by BackType