Taking Off From An IT Runway Instead Of Regular Tarmac – Leveraging Ramco's Leap Methodology

    Introduction to LEAN:

    Lean philosophy regards anything that doesn’t add value to a process or a product or that for which the customer is not willing to pay for, as waste and should be eliminated. The lean thinking had its beginning in the early 20th century from the works of Mr. Henry Ford, who integrated an entire production process to eliminate wastes. The lean thinking was further taken to a new level by Toyota who defined the Toyota Production System.

    All the while, lean thinking was finding itself confined to the manufacturing industry. It took time for industry specialists to understand the lean opportunity present in the services sector. Of this, the venture of Lean into IT products & services is a very recent development.

    Usually in an organization, when the idea of implementing lean initiatives is considered, the first question that pops up is “Why Lean??” - acasual question asked by someone who doesn’t understand lean philosophy. In simple terms, “it’s just a better way of doing things”. ‘Better’, in this sentence translates to saving time and reducing cost incurred byeliminating wastes in multiple facets. The wastes as identified by the Toyota’s TaichiiOhno, were:

    a) Transportation

    b) Inventory

    c) Motion

    d) Waiting

    e) Over-production

    f) Over-Processing

    g) Defects

    The easier way to remember the 7 wastes of lean manufacturing is the mnemonic TIMWOOD. All these wastes were identified in the production or mainly in a manufacturing setup. But to identify the same for an IT services or products industry is not easy. A software deployment process, has its set standard procedures. This has been followed for many years thus indoctrinated as standards of the system. The matter of concern was the time and cost incurred in Software implementation. This was not affordable to smaller players in industries. Thus,came the idea of bringing in the Lean thinking in the implementation process. RAMCO uses LEAN IMPLEMENTATION METHODOLOGY entitled as Ramco’s LEAP methodology. LEAP methodology was designed and formulated specifically for small operators allowing them to experience and realize the benefits of comprehensive mainstream full suite Aviation solutions.

    Ramco’s LEAP Methodology:

    Ramco’s LEAP methodology surgically augments the basic principal of LEAN philosophy to improve the software implementation process. The 7 wastes of Lean manufacturing can be categorized as:

    1. TRANSPORTATION: The wastage due to the transfer of goods from one place to another is the wastage of transportation. In software implementation process, this can be attributed to the data transfers or migration.The major time consuming activity during implementation is the data transfer from the legacy systems.LEAP methodology utilizes the concept of lean data migration templates. These data collection templates would only require the customer to fill in lesser data as compared to the traditional data collection templates. The rest of the data that is not collected through these templates are entered as defaults based on the industry standards.
    2. INVENTORY: The inventory would comprise normally of the finished goods, raw materials and the work in progress goods. These for a software implementation would be the basic infrastructure required to make it functional. Ramco’s aviation suite works over cloud network eliminating the need for the physical setup to be present onsite.
    3. MOTION: This is the wastage incurred due to unwanted transfer of the resources. The implementation process followed in the LEAP methodology avoids the need for the resource transfer to onsite. This is facilitated by virtual blue printing and training, through SKYPE or WEBEX sessions.
    4. WAITING: This is the wastage incurred when there is a delay in deployment resulting in Customers having to wait for the product. This is eliminated by following strict project plan with minimum project period. Ramco has done implementations in a month’s time as compared to the traditional 8-12 months by following the leap methodology.
    5. OVER-PROCESSING: Over-processing is due to the unwanted repetitive processes which doesn’t necessarily add value. An in-depth analysis of current processes will reveal better ways to improve the same. The processes like User acceptance testing can be avoided as the product is given in a “NO CUSTOMIZATION” mode, which means the customers have to use the product as such.
    6. OVER-PRODUCTION: This wastage is due to producing more than what is required. Ramco’s aviation suite is streamlined to customer’s requirements based on conference room piloting, where the consultants understand the client requirement and provide only what is necessary for them.
    7. DEFECTS: The main aim of LEAP methodology is to eliminate wastes of which defects are considered more seriously. LEAP methodology advocates zero-defects. For this, the concept of poka yoke is being followed, which means defect-proofing or mistake proofing. This is done by using checklists to avoid omitting the major activities ensuring mistake proofing.

    Over the years, there is an 8th waste that was identified – SKILLS, due to under-utilization of resources & delegating tasks with inadequate training. This waste can be eliminated by efficient training and effort tracking. Ramco follows a stringent effort tracking process.

    All this enabled the reduction of the software implementation process time from 8-12 months to 3-4 months or to even 33-45 days. Using Ramco’s LEAP Methodology, Customers benefit from faster realization of the software. LEAP thinking is an asset both to Ramco and its Customers!

    (Inputs by: Akhil Farook and Janeese Jacob Cherian)

     

    Ramco Aviation Suite

    Prajit K Jayarajan

    Written by Prajit K Jayarajan

    Related posts

    Subscribe to our Blog

    FOLLOW US

    Like Us

    ARCHIVES