About Bridge

Company

What We Do

Management Team

Our Thought Leaders

Strategic Partnerships

For Added Value

Global Presence

Developed & Emerging Markets

Why Bridge?

5 Reasons To Partner With Us

Your Experienced Trusted Advisor

Customer Case Studies

Business Challenges Solved

Our Customers

Well Known and Global

Testimonials

What our customers are saying

White Papers & Data Sheets

Excellent Resources

Order Management & Optimization

Fluent Commerce

SaaS Order Management

IBM

Order Management & B2B Integration

Magento

Order Management

Akana

Enterprise API

Commerce Solutions

Ultra Commerce

E-Commerce Solution

Mirakl

Marketplace

Bridge Products

Bridge Rabbit

Subscription Order Management

Bridge Eagle

Process and Transaction Monitoring Tool

Bridge Coral

Enterprise Commerce Integration Platform

Yantra Commerce WMS

Increase warehouse efficiency

Spare Parts Logistics

Streamline Your Spare Parts Logistics

Business Strategy

Omni-Channel Fulfillment Strategy

Ensure profitable fulfillment

Inventory Visibility Strategy

Reduce carrying costs

Delivery Experience Assessment

How well do you deliver orders?

Solution Support

Consulting

Strategy, design, implementation

Performance Testing

Don't let peak loads slow you down

Managed Services

On-site and hosted

Education

Product Training

Solutions

Order Management Systems

And related solutions

Warehouse Management Systems

And related solutions

Enterprise Application Integration

iPaaS, ESB, EDI, MFT

Industries

Retail

Deliver well

Manufacturing

Industrial Distribution

3PL

Activity Based Billing

Development Services

Custom Development

Custom Software and Applications

Elastic Stack Development

Enable Real-time Analytics

Offshore Services

Quality Off-Shore Resources

Data Services

Data Warehousing

For Business Intelligence

How to Avoid 10 Common Mistakes in WMS Implementations: Part 3

April 11, 2013 by The Bridge Solutions Group Team

Topic 3:  Lack of Risk Planning

In our initial article we presented 10 common mistakes made during the implementation of any WMS application. This article is the third installment in the series and will focus on the issue of ‘Lack of Risk Planning.’

In our opening article, we stated that incorporating a Risk Plan within the overall implementation plan is vital. Many WMS implementations exclude risk planning and as a result, fail to meet implementation schedules due to the fact that they fail to predict the “what if” aspects.  In fact, projects without Risk Management Plans are significantly more likely to take longer, go over budget, and ultimately they may even fail.

To mitigate this, the Risk Management Plan (RMP) should be developed and approved even before the project begins.  Failure to create an RMP up front is a little bit like forgetting to create a fire department in your town.  Everything is fine until there is a fire.  Then everyone will be running around screaming ‘every man for himself’ because no one knows who to call, or what to do.  Even worse, they don’t have any of the tools or knowledge on hand to prevent the situation from escalating.  Even when the fires do get put out, no one can assess the damage and get everything back on track.

Alas! Risk is part of any project and all Team Members must be made aware of the risks up front and know how to recognize the emergence of the risk and alert the Team to take action. This is where another common mistake generally happens. Everyone knows something is going wrong, but there is still a failure to take action!

The project manager should ‘facilitate’ the development of the RMP with each Team and with the Management Team. The RMP should identify the major “risks” for the project, the potential impacts or consequences and finally, a plan to either eliminate the risk or significantly reduce the potential impact. This is generally defined by a “Risk Matrix.”  In general practice, the following risk management strategies are generally used within an RMP to categorize risk, though there are numerous variations.

  1. Accept the risk = Take a chance on the negative impact and adjust plans accordingly.
  2. Transfer the risk = Outsource the risk to specialists who are experienced in handling the risk and have the resources to minimize the consequences.
  3. Avoid the risk = Adjust plans to eliminate the risk or reduce the consequences to a minimum.
  4. Mitigate the risk = Take immediate action to lessen the impact.

Categorizing risk also helps define your response strategies a little more generally, so that unforeseen issues can still be categorized and summarily dealt with in a manner consistent with your overall risk strategy.

If you’ve bought into the idea of an RMP, then the next step is to figure out how to create one.  Generally, there are 4 basic steps to creating a RMP:

  1. Identify the risks.
  2. Qualify each risk in terms of impact and probability of occurrence.
  3. Incorporate the risks within the project plan with triggers that activate the risk action plan.
  4. Create monitors that alert the project teams to the occurrence of the risk and actions to be immediately taken should the risk emerge.
  5. Continue to monitor the risks.

One of the best practices for a successful WMS implementation is the incorporation of the Risk Mitigation Plans within the actual project plan. The mitigation plan is in actuality a series of sub-steps within the project activity step that defines and assigns tasks that are intended to minimize the risk. The following is a basic representation of this concept.

In the illustration above, the risk actions have been incorporated into the project plan as a series of sub-steps that are triggered if the risk emerges as a realistic possibility. The main project activities continue in parallel with the risk action steps which have been designed to “mitigate’ the risk (minimize the impact).

 

An example might look something like this. Activity X is a planned data load and Activity X+1 is the validation that the data load was successful. In addition, there is an identified ‘Risk’ that during the data load there may be issues. If no issues emerge, then Activity X passes directly to X+1 (Validation). If an issue emerges, ‘Risk Step 1’ is triggered and the data is corrected. The data is loaded in Risk Step ‘N’ and flow continues back to Activity X+1.

 

There are hundreds of Project Risk Management and Project Risk Analysis templates available, and which one you choose is largely a matter of personal and organizational preference. The important thing is to select one that works well for the current project and integrate it early in the planning stage. There are even several add-ins for Microsoft® Project Management that seamlessly integrates a RMP into the project schedule.

 

Bridge Solutions Group understands that your business is unique, which is why we integrate our best practice knowledge with your organizational strategy seamlessly. We have the experience, skills, and resources to assist any organization in the development of a Project Risk Management Plan that is pertinent to their industry, software package, and business.

Filed under: Warehouse Management