VSM is a visual technique used to analyze and improve workflow processes. It involves mapping value-added versus non-value added activities to identify areas for improvement. The document discusses applying VSM to analyze a company's media extraction and migration workflow. It found that making the processes flow in a continuous manner and establishing first-in-first-out queues at each step could reduce the total workflow time by 40% by removing dependencies between steps. It recommends piloting these changes initially for smaller media sets to achieve more consistent and predictable lead times.

1. Visual Stream Mapping

3. Value Added activities enhance the functionality of product /output that customers would be willing to pay for

4. All magnitudes are noted in terms of time taken

5. Process Cycle Efficiency is ratio of VA by Total Time Taken

6. Considered representative total time around the median – prepared their activity Gantt Chart

7. VSM was prepared with inputs from the Gantt Charts

9. VSM The Total machine time is 5.6 hours Continuous flow has the potential to reduce PCT to ~6 hrs from current ~35 hrs

10. Native Data 10.7 25.7 *Median Time considered The Total is 40% more than the sum of parts  Individual processes are not independent

11. Consistency, Predictability – a prerequisite Median Mean Median Mean Mean Median The randomness and spread don’t allow precise estimation

13. To remove inter-process dependency (Slide 6)  40% ↓ in TAT

14. Have process owners as against case/project owners.

15. Pilot for small native media sets (CDs/DVDs/FTPs)Two people required per shift; one person owns Extraction and other owns BE Ops and Mig.

16. Only known constraint ‘Migration Window’ to be elevated i.e. BE Ops is done /tabulated backwards from Migration window

17. Need Problem Mgmt (TS/Engg) for time based troubleshooting. E.g. Why certain NSF media took 4+ hours and feed the fix /workaround into knowledge-base /best-practices

18. Midway changes to be made expensive – They disrupt continuous flow

19. Eliminate wastes like – check-n-resolve, on-hold, keep open for custom work

20. We host ~10 batches a day and have some activity on 20+batch tickets and totally ~50 tickets in day (customizations excluded)