iSixSigma

LEAN for Transcational Process – IT Specific

Six Sigma – iSixSigma Forums Old Forums General LEAN for Transcational Process – IT Specific

This topic contains 6 replies, has 5 voices, and was last updated by  Walter McGregor 12 years, 1 month ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #46874

    Walter McGregor
    Member

    LEAN Gurus,We’re working on a lean event for transactional processes for the very first time in our company. We were task to do reduction of IT systems downtime. And our mentor pointed out that our work should involve on the response time in handling IT systems downtime. I’m new to LEAN and I’ve been searching the Internet for materials that I would like to make as reference as LEAN is mostly done for manufacturing processes, I haven’t seen anyone doing LEAN for transactional specifically on IT. I hope I can find a white paper or case study regarding on my query.Thanks.

    0
    #155586

    Vidyadhar
    Member

    For implementation of Lean first walkt the process, Map it as it is… Then try and find out what steps are Non Value adding… eliminate the same.
    However for Server Downtimes, You would like to build a Poka Yoke, to prevent any unplanned outages, or if these occur, see if an option of a different gateway/switch is available to save the down times.This thread has been moved to the IT/Software discussion forum. Please click here to continue the discussion.

    0
    #155587

    Walter McGregor
    Member

    The whole IT system itself is built on the concept of redundancy. Sometimes when a failure occurs it would take us 6 hours to fix the problem whereas our SLA with our customer is 30 minutes. Any paper that is similar to what I’m working on?Thanks.

    0
    #155588

    Ovidiu Contras
    Participant

    Walter,
    White papers won’t do any good, without a deep understanding of Lean principles. Copying a formula without knowing what’s behind it is dangereous, especially when problems in the new setting arise.
    My recommendation would be to learn about flow, pull, waste, root cause and all the related good stuff before doing anything .
    Hope this helps

    0
    #155594

    Steven Bonacorsi
    Member

    Hello Walter,
    I’ve worked in IT for many years and have a number of projects in this area. First there are a number of books on Lean in transactional environments and white papers, keep looking. Note: also search “Lean Six Sigma” and “Services” or “office” environments. True, it may be hard for you to find the white paper on your specific project case – perhaps you can write and publish? Here are a few Lean concepts ypu should consider for application to this area:
    1. Mistake-Proofing (also known as poke-yoke (also review regulartory requirements and system limitations) – basically – eliminating the opportunity for a root cause to even occur.
    2. 5s (sort, set in order, shine, standardize, sustain) is an organization approach that applies to systems too.
    3. Value Stream Map – yes, listen to your mentor – the time it takes to respond to the system is probably a sub-process that is parellel but could be serial depending on the issue – map it to find out (note: in transactional environments and sytems – using screenshots when needed can also be used to show the transactional steps or decision points)
    4. Setup Time reduction – Could also be linked to the response time of bring server back up, backup processes, upgrade or TPM processes.
    5. TPM – how to you apply regular needed maintenence to the system to ensure downtime is minimal (its like a car – no maintenence – huge repairs at once – or regular care and repairs and problems become rare)
    6. Visual Workplace – don’t forget thos network triggers for alerts – how can you use not to tell you just when the server is down, but when TPM is needed! Think about other metrics for this project such as time between “downtime” incidents, etc…
    Best Wishes,
    Steven Bonacorsi

    0
    #155600

    jtomac01
    Participant

    Most, if not all, Transactional Lean events follow the same pattern, so the preparation is very similar irregardless if it is IT or some other process specific.
    A poster mentions study the concepts of Lean (i.e. flow, leveling, etc.), this is by far the best advice.  Study up on the concepts and try to understand how it directly applies to what you do at a HIGH level.  Do not get caught up in the 1-off scenarios.
    Another poster mentions the VSM & walk the process, do this as pre-work, but also do it during the event as a x-functional team (hopefully you have some suppliers & customers of the information & process you are working on, not just all IT developers/etc.).  This builds a common understanding of the problems faced & I can almost guarantee a lot of lessons will be learned as well as misconceptions will be dispelled.
    Short answer is study previous T-Lean events or projects & you will see the framework that will help you succeed in the event.

    0
    #155645

    Walter McGregor
    Member

    I forgot to mention that we’ve undergone 2 weeks of LEAN training. It’s the first time that LEAN for TRANSACTIONAL PROCESSES were to be implemented. Since it’s our first time, I would like to see if any other company have implemented such event or project.

    0
Viewing 7 posts - 1 through 7 (of 7 total)

The forum ‘General’ is closed to new topics and replies.