{domain:"www.qualitydigest.com",server:"169.47.211.87"} Skip to main content

User account menu
Main navigation
  • Topics
    • Customer Care
    • FDA Compliance
    • Healthcare
    • Innovation
    • Lean
    • Management
    • Metrology
    • Operations
    • Risk Management
    • Six Sigma
    • Standards
    • Statistics
    • Supply Chain
    • Sustainability
    • Training
  • Videos/Webinars
    • All videos
    • Product Demos
    • Webinars
  • Advertise
    • Advertise
    • Submit B2B Press Release
    • Write for us
  • Metrology Hub
  • Training
  • Subscribe
  • Log in
Mobile Menu
  • Home
  • Topics
    • 3D Metrology-CMSC
    • Customer Care
    • FDA Compliance
    • Healthcare
    • Innovation
    • Lean
    • Management
    • Metrology
    • Operations
    • Risk Management
    • Six Sigma
    • Standards
    • Statistics
    • Supply Chain
    • Sustainability
    • Training
  • Login / Subscribe
  • More...
    • All Features
    • All News
    • All Videos
    • Contact
    • Training

Value Stream Mapping Math

The lead-time ladder process ‘branch’

Mark R. Hamel
Thu, 03/21/2013 - 10:33
  • Comment
  • RSS

Social Sharing block

  • Print
  • Add new comment
Body

ADVERTISEMENT


Here’s some often overlooked and misunderstood value-stream mapping math.

ADVERTISEMENT

The lead time ladder has two levels or “rungs.” The bottom rung is the process or processing rung on which the relevant process time is dropped down. This is usually pretty straightforward... unless there is a split or branch in the material, service, or knowledge flow within the value stream.

For example, after a fabrication process, the material may flow 35 percent of the time to a coating process and then to an assembly process, while 65 percent of the time the coating process is skipped altogether. The value-stream map essentially reflects a process time for a hybrid (or weighted average) product or service, in such a situation. Accordingly, the process times for these branches must be apportioned by the split percentage, as illustrated in the figure below.

 …

Want to continue?
Log in or create a FREE account.
Enter your username or email address
Enter the password that accompanies your username.
By logging in you agree to receive communication from Quality Digest. Privacy Policy.
Create a FREE account
Forgot My Password

Comments

Submitted by Rajohnson on Thu, 04/04/2013 - 09:57

Branch is a new stream

With different operations, don't we have a different value stream?  which would then have different demand (e.g. TAKT time) and operator loading and different playbook(s) and...and...and...

By merging the streams, we are in danger of not recognizing the variety needed and designing necessary flexibility to accomodate the variety.   By manipulating the math to merge streams, we muddy the view of the process.  When our streams get muddy and many, our process starts to look like a puddle.  My preference is to view clean, clear streams and not muddy puddles.

 

  • Reply

Add new comment

Image CAPTCHA
Enter the characters shown in the image.
Please login to comment.
      

© 2025 Quality Digest. Copyright on content held by Quality Digest or by individual authors. Contact Quality Digest for reprint information.
“Quality Digest" is a trademark owned by Quality Circle Institute Inc.

footer
  • Home
  • Print QD: 1995-2008
  • Print QD: 2008-2009
  • Videos
  • Privacy Policy
  • Write for us
footer second menu
  • Subscribe to Quality Digest
  • About Us
  • Contact Us