Saturday, May 1, 2010

“Act Vertical” vs. “Go Extinct” Retailers – Part 3

In his Harvard Business Review 1997 article entitled “What Is the Right Supply Chain for Your Product?” Marshall L. Fisher distinguished two types of products that call for different supply chain strategies: functional and innovative. They differ as follows:

* Functional products, like canned soup and blue jeans, have longer life cycles (perhaps more than two years), relatively low contribution margins, and little variety. Because demand for them is stable, they are fairly easy to forecast, with a margin of error in the 10 percent range, very few out-of-stock situations, and no end-of-season markdowns.
* Innovative products differ from functional products in every aspect. They have unpredictable demand, relatively short life cycles (e.g., three months for seasonal clothing), and high contribution margins of 20 to 60 percent. They may have millions of variants in each category, an average stock-out rate from 10 to 40 percent, and end-of-season markdowns in the range of 10 to 25 percent of the regular price. The margin of error on forecasts for innovative products is as high as 40 to 100 percent, but the lead time to make them to order may be as low as one day and is generally no more than two weeks.

The idea that the same type of product can be either functional or innovative implies that one company might have more than one supply chain. And that’s the contention of Jonathan Byrnes, a professor at MIT. Writing in the Harvard Business School’s Working Knowledge 2005 article entitled “You Only Have One Supply Chain?”, Byrnes also asserts that one supply chain is not enough: two, three, or more would be preferable.

“One size fits all” supply chains may have been sufficient in the past, he believes, when that was the competitive norm, but modern IT makes it possible to have multiple, dynamic chains that can accommodate different product and information flows. Byrnes breaks apparel products into the following three categories: staples, seasonal products, and fashion. These products have very distinct design and replenishment characteristics.

Much like Fisher’s functional products, staples (e.g., white underwear) have steady, year-round demand and low margins. He advises stocking them only in retail outlets in small quantities and transporting them in truckload quantities (a full truck is more cost-effective for the shipper than a partially loaded vehicle, i.e. less-than-truckload [LTL] shipping.) Fashion products are like Fisher’s innovative items with unpredictable demand.

Consequently, Zara, the famous Spanish clothing manufacturer, has two supply chains, one for staples and the other for fashion clothing. To get the fastest response time, Zara uses pricey Western European suppliers for the fashion items. But for the more predictable demand items, it uses Eastern European suppliers, which have poorer response time (not a major concern here) but at much lower cost.

APICS 2009 From the Expo Floor: Is S&OP Coming of Age? – Part 2

Until recently S&OP has had a purely tactical and reactive near-term focus, and was therefore disconnected from overall business strategy, which can result in many missed opportunities. Moreover, many laggard companies still have an unstructured and fragmented S&OP process, whereby each department tends to have a spreadsheet-driven process with critical company data stored on dangerously unmanageable (and unsynchronized) spreadsheet documents.

Too often, while the business unit teams involved in creating S&OP plans are executing according to one set of numbers, corporate and financial management offices may be setting, expecting, and communicating a completely different set of financial plans and projections to the board of directors and other key stakeholders. Plan inputs typically reside in multiple sources and formats, challenging unified and timely visibility and the rapid synchronization of plan adjustments.

Disparate plans that do not incorporate key functional and trading partner insights can create a credibility gap for any company and its key executives when performance falls short and customers are left unsatisfied. But even when there is the awareness of aligning plans, it then requires a non value-added manual effort. Namely, corporations spend more time and effort collecting and aggregating data than on planning or making decisions.

When departmental plans are not aligned, there is also a misalignment between how departments are measured against the overall company objectives. For example, sales management is often measured by whether a sales quota is met, even if the sales team is selling products that the supply chain is unable to produce.

This misalignment tends to lead to a very time-consuming and manual process of trying to come to an agreement on what “the forecast” should be. This painful consensus-making process typically yields an inaccurate forecast in the end. This forecast is then “tossed over the wall” to supply chain operations to figure out how to expedite production(”extinguish another fire”) to meet the demand, with no thought to the profitability of the decisions.

This predicament is often further compounded by the aforementioned situation where “approved” plans are only a spreadsheet filed somewhere, while the actual plans being executed are customarily quite different.

To recap, reactive S&OP has no connection between departmental plans, and the overall strategic plan is not tied to execution. Other typical shortcomings are as follows:

* misalignment between departmental key performance indicators (KPI’s) and corporate strategic objectives;
* unreliable forecasts and production plans;
* a rigid and prescriptive process, based on incoherent and not integrated software tools; and (last but not least)
* outdated, incomplete, or incorrect data and lengthy S&OP cycles with little provision for adjustments within a planning cycle seriously limit a corporation’s ability to detect market changes and assess any demand or supply shaping decisions.

Microsoft Dynamics CRM: Much More Than Meets the Eye – Part 1

Contrary to the downward trend for its four enterprise resource planning (ERP) brethren, the Microsoft Dynamics CRM product (although still only a fraction of the overall Dynamics revenue) grew significantly in revenue year over year and surpassed the one-million-users mark in 2009. The customer relationship management (CRM) suite consisting of marketing automation, sales force automation (SFA), and customer service modules now has over 20,000 corporate customers from small businesses to large enterprises in over 80 countries and over 40 languages. More than 4,000 partners deliver Dynamics CRM software and services worldwide, and the company has more than 50 partners worldwide that are offering Microsoft Dynamics CRM as a partner-hosted service.

Certainly, Oracle Corporation remains the world’s CRM leader with 5,000 of the largest customers, 4.6 million users, and 125 million self-service users. Oracle’s CRM, business intelligence (BI), and customer data integration (CDI) products include Oracle Siebel CRM, Oracle CRM On Demand, Oracle E-Business Suite (EBS), Oracle PeopleSoft Enterprise, and Oracle Contact Center Anywhere (CCA). For its part, Salesforce.com boasts nearly 70,000 corporate customers and 2 million on-demand subscribers for its sales and service cloud computing offerings. But Microsoft Dynamics CRM [evaluate this product] points to that fact that it grew to one million users in just over six years while other vendors took more than eight years to achieve the same milestone.

What we are seeing and hearing is that Microsoft customers are choosing Dynamics CRM for its fast deployment, native Microsoft Office user experience (UX) design, flexible customization (made easy through metadata-driven definitions and point-and-click configuration), ease of integration with existing systems (due to native Web Services architecture), and affordability. From partners, Microsoft is hearing that deal sizes are increasing between 40 and 80 percent with the use of available marketing assets in the Microsoft Partner Network.

Who Are Microsoft Dynamics CRM Customers?

In general, there is no typical Microsoft Dynamics CRM customer amongst those 20,000 customers and one million users. Microsoft Dynamics CRM is being used by small, medium, and large enterprise organizations in a diverse range of industries, including financial services, manufacturing, the public sector, retail and hospitality, health and life sciences, and entertainment. The product is continuing to see strong growth in terms of seats and revenue, and this growth has not been limited to one particular market segment or geography.

But the offering is certainly most attractive to the many organizations around the world that already use a wide variety of Microsoft technologies and platforms, such as SharePoint, .NET Framework, Internet Information Services (IIS), and SQL Server. Microsoft Dynamics CRM can amplify the value of those products through its seamless connectivity and tight alignment.

First and foremost, organizations have the luxury of using a functional CRM product natively within Microsoft Office Outlook. In addition, companies that already use Microsoft Office can take advantage of built-in Word mail merge capabilities, e-mail templates, Microsoft Office Excel reports, and easy data transfer between Excel and Microsoft Dynamics CRM.