Archive for September, 2010
How Does Your Company Measure Supply Chain Complexity?
Thursday, September 23rd, 2010Today’s supply chains are very complex with suppliers having to service customers in different industries, across many different countries around the world, with many different B2B standards and support many different business processes within a customer’s supply chain.
Globalization of the manufacturing industry has only served to increase supply chain complexity still further with a need to work across different time zones, support different languages and work across different cultures. Have you ever sat down for ten minutes and tried to map out on a piece of paper how many different standards and processes your customers are asking you to support and more importantly how and who manages this complexity within your company? On the surface things may appear straightforward, but underneath, process and technology complexity can increase significantly, very quickly.
Supply chain complexity can be measured in many different ways and in some ways I am surprised that there does not seem to be a standard way to measure supply chain complexity. If there was a way to measure this and you had visibility of everything that was happening across your supply chain then surely you could take steps to simplify business processes, consolidate technologies and introduce improved efficiencies right across your downstream supply chain?
One of the key mandates of any company is to improve customer satisfaction levels, now does ‘improve customer satisfaction’ mean that you have to support new B2B standards and supply chain processes outlined by a supplier’s customer?, in short yes. Suppliers typically work with many customers and each of these customers has a unique set of business processes and rules that the supplier must adhere to. Now I have spent four years at GXS working across the automotive, high tech and general manufacturing industries and I guess if I am being biased here I would say that companies working across these value chains have to utilize some of the most diverse set of standards and business processes of any industry sector.
Let me try and explain this through a simple example, OK it may start simple but as you will see things get complex very quickly. A supplier in the high tech industry based in Europe manufactures in-car infotainment systems for OEM1 and OEM2. OEM1 is a car manufacturer based in Tokyo, Japan and OEM2 is based in Detroit, North America. So this looks at first glance to be fairly straight forward, one supplier supplying two customers, but the demands of these customers is very different. What I have tried to do in the diagram below is to map out the complexity of the supplier’s sell side value chain, but for the purposes of keeping things simple for this blog entry I have only focused on three degrees of complexity, regional, technology/standard and industry/process.
OEM 1 has recently replaced their inhouse ERP system with a system from SAP. They have asked all their suppliers to exchange business documents using either the HULFT file transfer standard, (this is unique to Japan) or HTTPS. OEM1 is connected to the Japanese Network Exchange (JNX), a private network for automotive companies based in Japan. OEM1 is a high volume car manufacturer and they use Just-In-Time (JIT) production techniques which means that supplies must be delivered to their plants within a specified time slot and they require ASNs to be sent through to notify them that goods are enroute to the plant. The OEM needs to send and receive documents in both EDIFACT and XML.
OEM2 has slightly more complicated requirements due to the fact that they have manufacturing plants in North America, Mexico and Europe. They have just standardized their global ERP platform on Oracle and they have recently implemented Oracle’s Transport Management System. As OEM2 has additional plants in both Mexico and Europe, there is complexity around supporting invoices and tax compliance in these regions. This company uses the Evaluated Receipt Settlement (ERS) process with their North American operations in order to speed up payments to suppliers. OEM2 is a high end premium car manufacturer and most of their vehicles tend to be built to order. This means that different vehicles need to be assembled on the same production line. They use Supply In Line Sequence (SILS) production techniques to supply components at the right time to the production line depending on which type of vehicle is coming down the line. All major parts or sub-systems are tagged with an RFID tag so that they can keep track of parts movements within their plants.
All goods entering North America must now meet the new 10+2 customs compliance standard. OEM2’s plants in North America are connected to the American Network Exchange (ANX) and in Europe their plants are connected to the European Network Exchange (ENX). In North America they would prefer payments to be made through the SWIFT banking network and they are thinking of adopting the EBICS standard for bank payments in Europe. OEM2 has been using OFTP communications in Europe and AS2 in North America but they would like to consolidate on to the new OFTP2 internet standard across all their plants in the near future. Finally, EDI documents should be supplied in both ANSI and EDIFACT standards as required.
Now if I was a supplier to both of these companies I would be thinking, “where do I start?”. So many different regional, technology, process standards to adhere to and it could take a significant amount of time to establish the connections to these OEMs, let alone make sure they receive their EDI documents in the right format, at the right time and at the right location. Supply chain complexity, don’t you just love it !, So how can a supplier meet all these requirements and yet still maintain continuity of their own business and work with many other customers? Well that will be a topic for another blog entry.
In the meantime if you would like to understand a bit more about the complexities facing today’s supply chains then you might be interested in attending an upcoming GXS webinar called “Enhancing Customer-Centric Supply Chains” . This webinar is related to a new research study that GXS will be launching in the very near future and it follows on from our three previous research studies around B2B Outsourcing, Total Cost of Ownership and B2B/ERP Integration. To register for this webinar please CLICK HERE
Video Interview with Ken Vollmer of Forrester
Wednesday, September 8th, 2010Earlier this year, GXS had the opportunity to participate in a multi-vendor research study with Forrester Consulting on the topic of B2B Integration. The full results of the study are available on our web site. The findings include a wealth of current data on B2B technology usage, but there were a few particular trends that I found interesting. I recently had the opportunity to interview Ken Vollmer of Forrester to gain his perspective on the survey results. Ken’s research covers trends, issues, and strategies related to all forms of integration, including Business Process Management (BPM), Enterprise Application Integration (EAI), B2B integration (B2Bi), and Electronic Data Interchange (EDI). Below are some of the findings as well as a link to my video interview with Ken.
Spreadsheet Popularity Remains High
One of the findings of the study was that 95% of surveyed were using spreadsheets or other text documents for B2B transactions. When most people think about the documents used in B2B e-Commerce, standards such as XML or EDI probably come to mind. However, there are numerous scenarios in which the existing standards do not meet trading partner needs. For example, standards may not model a particular business process or may not offer the flexibility needed to share custom views of data. In such scenarios, spreadsheets from leading vendors have become a popular alternative.
Massive Upgrade Trend in B2B Integration
Another interesting finding from the survey was that 77% of organizations were planning to upgrade their capability to exchange information more effectively with external business partners. The upgrade plans were consistent across all sizes of companies, geographic regions and vertical industries. In fact, most companies are planning to upgrade within the next 12 months. Such a high percentage of upgrades may be difficult to believe given the current economic malaise. However, the survey was actually conducted around the beginning of the year at a time when there was greater optimism about the economic recovery than currently exists.
Managed Services Growing in Popularity
The survey asked what approach enterprises are taking for the transport of EDI/B2B documents. There was not one dominant approach. 15% of organizations use software only such as integration brokers or Managed File Transfer packages for B2B. Nearly twice as many, 28%, use Managed Services, in which a technology vendor is engaged to provide day-to-day activities such as map development, ERP integration and community on-boarding. Hybrid approaches, combining both software and Managed Services, was the most popular choice, selected by almost half the participants.
Watch my interview with Ken Vollmer to learn more about the survey findings above.
The Cloud may have the Computing, but the River has the data….
Wednesday, September 1st, 2010
Every day, companies exchange millions of electronic documents with each other that have some very special characteristics:
- the data matches actual transactions occurring in the “real world” (orders, shipments, payments)
- the data is structured in a way that provides meaning, it can be processed and turned into information
- the transaction data has relationships to other transactions in the River that can be correlated
Unfortunately, for most organizations, the potential to tap into this powerful source of information remains just that, potential. The challenges inherent in examining, correlating, and acting upon the massive flows of data generated by even modest enterprises have typically been overcome only rarely, and often not at a sufficient scale to truly exploit the opportunity. In this post I’d like to look at some of the challenges that make this difficult, and I will explore the opportunities in future posts.
Some of the Challenges….
- Context: even today, most B2B transactions utilize traditional EDI standards like ANSI X12 or EDIFACT. Despite the standardization of documents, it is frequently tricky to understand the context in which a given transaction is operating (e.g. for a given ASN — ship notice — what order process is it part of?). Without context, it is a free floating piece of data, requiring some associations to turn it into information. If a critical shipment is one day away from delivery to a store about to run a promotion, that is information — if Shipment #101 has been processed, and I don’t know what process it is part of, that’s just data
- Timeliness: while immediacy is a great benefit of the data flowing between trading partners, age is its enemy. With today’s more efficient supply chains, data starts to go stale very rapidly. The challenge is to connect data flowing between partners to other information and to business processes before it is too late to act upon the information. The data flow is not unlike electricity generated by a dam, which must be sent over wires to be consumed in real time. Data warehouses can use the last three years of data to help forecast, but a logistics system has to act upon what is happening the chain today to deliver ROI
- Exceptions: until “the perfect order” is actually achieved, some of the most critical issues between partners are those that generate exceptions, either technically (cannot process an order or logistics document) or on the business side (wrong product, amount, price). It is truly scary at the latency involved in resolving these exceptions, with most of them basically “failing out” to a manual process. Despite the fact that for the “success case” there may be 100% automation, the most common “automated” exception handling is an email alert (how full is your inbox?)
- Integration: the “father of all challenges” when it comes to automation (and its role in resolving the previous three challenges), is the ability to integrate the flow of data into the many systems that are capable of rapidly providing context, and identifying and handling exceptions. This challenge has always been daunting, but recent developments in technology and the ongoing march of technology have started to improve the integration possibilities
- Scale: the sheer volume of data, while being its greatest strength, may also be its biggest challenge. Since millions of transactions flow between partners on a given day, to understand what is happening, all of those transactions have to be interpreted, put into context and analyzed for meaning. RIGHT NOW! If the approach is to methodical, you succumb to the timeliness challenge, but if the approach is too loose, you may generate so many “false exceptions” that you actually degrade business performance, rather than improving it






