Category Archives: Vendor Review

Supply Risk Management IV: WisdomNet’s Point of View

As mentioned in Jason Busch’s recent post Another Perspective on Supply Chain Risk* on SpendMatters , WisdomNet recently published a whitepaper that serves as a good introduction to Supply Chain Risk, and a good companion to my introductory posts on Supply Chain Risk (An Introduction, Risks and the Need for Resilience, and Managing Risk) that ran this weekend on e-Sourcing Forum [WayBackMachine]. Although I agree that there are not any breakthrough findings or thoughts in the work, I also found it to be quite a worthwhile read — a perfect supply risk management 101 type of study, if you will. As such, I’m going to highlight the key points made by the author as a comparison and contrast to the key points that I made this weekend (in an effort to encourage you to read more).

According to the white paper, five key factors have an impact on supply chain resilience:

  1. Supply Chain Design
  2. Business Process Management (BPM)
  3. Demand and Supply Visibility throughout the Supply Chain
  4. Supplier Relationship Management (SRM)
  5. Culture

Supply chain design is the primary driver of resilience, and the level of risk in a supply chain is affected by process structure, level of vertical integration (that results from make or buy decisions), the location of supply, the concentration of capacity, and inventory decisions. Process structure is dictated by the choice of make to stock, configure to order, make to order, and design to order. The extent to which suppliers that cannot be easily replaced perform critical steps in the vertically integrated supply chain increases the level of risk. Sourcing outside of the local market in which the goods are to be sold adds considerable transportation and delivery risk. Concentrating supply to a single region, country, or city adds considerable risk and risk (which includes obsolescence, quality, shelf-life, and loss) increases with the number of inventories in the chain.

Resilience can be added to the supply chain design by:

  • using common components and configure to order processes whenever feasible,
  • avoiding sole source arrangements,
  • reserving capacity, implementing maintenance and spares strategies when single sourcing must be used, and allowing for process redundancy,
  • distributing supply among multiple cities, countries, and regions
  • centralizing safety stocks regionally,
  • holding inventory in unprocessed states for flexibility,
  • consistently and regularly measuring and improving forecast accuracy,
  • rationalizing product lines,
  • building rapid re-supply provisions into supplier contracts,
  • collaborating with customers for “early warning” of potential needs,
  • using performance-based contracts with Service Level Agreements, and
  • sourcing locally within your target market to facilitate site visits, minimize cultural differences, and increase manageability.

A focus on business process management can enhance capability through the supply chain. Participants whose processes are controlled and reliable are less likely to induce supply chain disruptions internally than those whose processes are not under control. Operations where statistical process controls and improvement programs, such as Six Sigma, are in place tend to have more predictable processes and introduce less variability when compared to those operations without such controls.

Resilience is the result of business process management that includes

  • using fact-base process improvement and control techniques like Six Sigma,
  • working with partners to build the same process disciplines into their operations (as your supply chain is only as strong as your weakest link),
  • focusing improvements on reducing economic order quantities to increase flexibility, and
  • building the ability for flex capacity.

Enhancing visibility through the supply chain improves your ability to deploy appropriate levels of resources where needed and reduces the risk of internally generated disruptions. Also, the more open the participants are about providing early warnings about (potential) disruptions, the more likely the chain can either avoid them altogether, or at least reduce their effect and duration.

Resilience results from increased visibility when you

  • implement collaborative forecasting, planning, and replenishment,
  • use partner agreements to provide inventory visibility,
  • implement systems that integrate data feeds in (near) real-time, and
  • (contractually) require suppliers to provide immediate and specific notification of (potential) disruptions as soon as any event of significance occurs.

Competency in Supplier Relationship Management is the key to building and maintaining a strong supply chain team. SRM skills enable an organization to reduce supply chain interruption risk by strategically spreading business among multiple suppliers and multiple locations. SRM techniques include good performance measurement processes, collaboration and supplier development, and solid category management programs wherever sole sourcing is required.

With regards to performance measurement, it is important to establish clear expectations, provide timely feedback when performance falls short, and manage consequences. Reward suppliers that succeed and penalize suppliers that fail. Performance is increased when joint efforts with strategic suppliers are undertaken to optimize cost, inventory, processes and flexibility. Manage key categories with a sound understanding of the underlying commodity markets and devise substitution options when you foresee an impending shortage or crisis.

Resilience results from Supplier Relationship Management when you

  • establish supplier performance measurement processes and apply them consistently,
  • invest selectively in strategic supplier development,
  • manage categories for strategic and single-sourced components,
  • use supplier segmentation to guide relationship management, and
  • move toward performance-based contracts that build risk sharing into contract pricing.

Culture is used to refer to the level of trust, delegated decision-making structure, and rapid information movement. In order to build resilience:

  • participants need to share information about demand, inventory positions, capacities, and vulnerabilities,
  • lower levels of the organization need to be empowered to sound alerts regarding problems or potential problems (as the sooner a problem is found, the cheaper it is to fix, and the smaller the duration of the associated disruption), and
  • processes should be in place to enable timely information flow.

In addition to the steps that have been outlined above to improve resilience, there are actions that can, and should, be taken by an organization to prepare for a disruption. These are:

  • Identify potential risks, possible ramifications, and associated likelihoods.
  • Explore risk-reducing measures and decide on actions to mitigate risk, investing more in plans and processes to mitigate high likelihood and high impact risk scenarios.
  • Prepare business continuity plans that address both emergency response and plans for business resumption.
  • Practice drill the continuity plans against different scenarios to uncover and address potential weaknesses before a crisis happens.
  • Work with critical suppliers to make sure they are prepared and have business continuity plans in place.
  • Update plans regularly and as conditions change.
  • Respond to disruptive events as they occur.

In addition, the business continuity plans should include:

  • event impact analysis,
  • organizational roles and responsibilities for crisis management,
  • crisis communication plans,
  • well defined procedures for the evacuation of personnel,
  • consideration for means to provide food, water, shelter, clean air, security, and basic medical, and
  • secure back up of key business data and systems required to run the business and service your customers.

Events that cause supply chain disruptions are inevitable. The impact of these events, however, can be minimized by proactively taking steps to build a resilient supply chain and by preparing for disruption. For an in depth discussion, I refer you to WisdomNet’s white paper “Managing Supply Chain Risk: Building in Resilience and Preparing for Disruption” (registration required).

* All posts prior to 2012 were removed in the Spend Matters site refresh in June, 2023.

Procurement Independence at the Coupa Cabana Cafe

This month, Dave Stephens of Procurement Central (WayBackMachine) will formally launch Coupa eProcurement, an open source offering with the ambitious goal of becoming the first self-service buying tool that employees actually want to use. Besides eliminating manual processes (and you should know by now that I believe in purchasing automation with the eventual goal of completely eliminating purchase orders), Coupa eProcurement claims to enable better buying decisions, easily support special requests, create and manage content, and spread the word on “how to buy”.

Now I’m as skeptical as Jason Busch of SpendMatters and Doug Hudgeon  of Vendor Management (Renamed Contract Capital Management, archived on the WayBackMachine), but I have to admit that I’d like to “… Imagine a world where it’s easier to follow the rules than to break them. Imagine receiving accolades for providing users with an easy system for what should be an easy process: buying what they need, when they need it. Imaging deploying … a complete requisition to order system with best-in-class usability and collaboration features …“.

Now, I was lucky enough to get a webex preview of this system last Tuesday and would like to say that it is looking really good. A web-based solution, your buyers can open their browser and log in to a procurement portal customized to their needs.

On the main page, besides your usual main bar, news section, and intranet document access, you have an RSS-based news feed which is always automatically up-to-date, a one-stop google-style search-box that you can use to search for information and items in your approved purchase catalog, and an ask-an-expert question box that will submit questions to an in-house expert. Once answered, these best practices will be institutionalized in a dynamically evolving FAQ. In addition, instead of forcing a rigid organizational structure on your best practices and policies documents, news items, and catalog items, it offers the concept of a self-updating “tag cloud” that shows users what index terms are currently in common use and allows them to evolve the indexing methodology to what they feel comfortable, and productive, with as a team.

Furthermore, it also integrates one of the easiest-to-use shopping-cart based requisitioning systems that I’ve ever seen. (And I’ve designed a few slick offerings myself as a former e-commerce developer.) It’s easier then amazon’s “one-click”, since that’s only one-click after you’ve made multiple clicks through the site trying to fill your cart and only one click if you use all default buying options. Coupa’s offering lets you find an offering, add it to your requisition cart, and then add items to the cart in the cart screen based on integrated smart drop-downs and editable smart-search fields – it’s as easy as filling out a line on a purchase order. If you know what you need, you can go right to the cart, define what you want in the cart, have the line items appear, click “requisition” and off shoots an e-mail to your supervisor indicating an order is waiting for her approval.

Now you’re probably thinking … “If it’s that easy for a user, I bet it’s an administrative nightmare to keep it running”. Well, although Dave hasn’t released any details to me on the technology stack yet and I don’t know how hard it will be to install, I can say that keeping it up to date is pretty simple. Adding your catalog of approved items is as simple as sucking in a well formatted file or integrating with a PIM (Product Information Management) exchange on a push/pull model. Adding policy documents or news items is a snap. And approvals, nicely summarized on clear and crisp screens, are as easy as a mouse click.

The only thing that bothered me slightly was the fact that there is no separation between “catalog” and “contract”. However, from a procure-to-pay point of view, this is a brilliant idea (as long as you associate expiry dates with the catalog items). After all, you should not have items in your system that are not under contract or not approved for purchase, so the separation of these concepts would only add complexity to what would otherwise be a simple system (again, providing catalog items have an expiry date associated with your contracts and these catalog items disappear if those contracts do not get renewed).

Now, add all this to the fact that Coupa intends the total cost of system ownership to be 2x to 3x less then the cost of ownership of the typical e-procurement offerings from SAP and Oracle, and Coupa starts looking very attractive.

However, I have to agree with Doug and say that “ Dave’s chance of success depends entirely on the shape of his target market. If he goes after the most demanding customers in the spend management market with a version 1.0 system then he will have a long slog in front of him … ” but if he instead focuses on “ ‘overshot’ customers who do not require all of the features of the current suite of products or to non-customers who are excluded from the current suite of products for reasons of price or complexity … “, I think he has a great chance, especially if he focuses on the benefits a customer can receive by pairing his tactical e-Procurement offering up with affordable on-demand e-Sourcing suites like Iasta’s SmartSource suite (with release 7.0 slated for this summer) that covers the strategic aspects of the procurement function. After all, low cost on-demand sourcing software plus low cost procurement software (which can be hosted on-demand as well) equals a full Total Value Management e-Solution (on-demand) at a low cost, and this is a powerful proposition for small to mid-market firms that really need a world-class solution but can’t afford an IBM, Ariba, Emptoris, Oracle, or SAP to make it happen.