As I stated in my last post on the Green Coffee Association’s XML standard offers an excellent example of the Long Tail of B2B Standards.  The standard automates a highly specialized set of business processes within a niche industry subsector.  Tremendous benefits can be derived from market participants as a result of the flexibility offered from the wide variety of tendering, payment, pricing and performance management terms that can be modeled in the XML.  Such benefits would not be practically achievable with a more generalized standard such as EDI. 

Benefits of Green Coffee XML 

Examples of the benefits of Green Coffee XML include:

• Lower Days Sales Outstanding (DSOs) for sellers of coffee bean products are achieved by creating an electronic audit trail of commercial transactions that reduces the likelihood of post-shipment quality and invoicing disputes.
• Improved Order Fulfillment rates are accomplished by routing contracts directly from buyer procurement applications to seller order management systems thereby obviating the need for error-prone, human interactions.
• Reduced Total Landed Costs for transportation are realized by standardizing and digitizing the import and export processes that often delay shipments at international borders and result in unexpected penalties or fines.

Challenges of Green Coffee XML 

Specialized e-commerce standards such as Green Coffee XML offer unparalleled levels of automation and efficiency within a particular market sub-segment.  However, such niche XML standards create challenges for market participants whose core business utilizes a different e-commerce framework.  Green Coffee XML offers an all-inclusive solution for the agricultural businesses that grow the coffee beans and the specialized brokers who act as middlemen in sales transactions.  However, the standards complicate e-commerce scenarios for other market participants such as consumer products manufacturers, food service retailers, government trade ministries, transportation providers, commercial insurer and banking institutions.

• Consumer Products Manufacturers – Brand owners such as Kraft and P&G who purchase large quantities of green coffee beans can benefit from the GCA standards during procurement processes.  However, Green Coffee XML is not the only standard utilized by consumer products manufacturers.  Other non-coffee suppliers of ingredients, raw materials or packaging materials are adopting the GUSI XML standards.  Retail customers expect their suppliers to exchange information in the EDI document standard via AS2 Internet transmission protocols.  Furthermore, retailers expect product branding, pricing, packaging, promotion, taxation and regulatory data to be transmitted using the Global Data Synchronization (GDS) standards.  A wealth of information about coffee bean quality can be exchanged using GCA XML, but the data must be transformed into GDS XML formats for distribution to downstream retailers.
• Banking Institutions – Financial institutions provide risk mitigation and working capital solutions to coffee buyers and sellers.  Examples include letters of credit and post-export supply chain finance.  Cost effective and timely processing of such services requires electronic communication with the buyer and seller.  Consequently, banks engaged in coffee-related transactions must either embrace the GCA XML standards or develop a process for mapping data to and from their own preferred standards.   Financial institutions utilize the SWIFT FIN MT standards for international trade processing.  Additionally, a new set of Trade Services Utility (TSU) standards are being developed for supply chain finance.
• Transportation Vendors – Ocean, rail and ground freight carriers as well as third party logistics providers offer a variety of transportation, warehousing, freight forwarding and customs clearing services to buyers and sellers of coffee products.  The cost-effective and timely processing of coffee-related shipments necessitates electronic communications between buyers, sellers and government trade ministries.  Consequently, transportation vendors engaged in coffee-related shipments must either embrace the GCA XML standards or develop a process for mapping data to and from their own preferred standards.  Transportation providers utilize higher volumes of EDI than any other e-commerce standard.  However, due to the broad range of industries serviced by logistics providers, a myriad of standards including AS2, RosettaNet, Odette, STAR and OAG are being embraced by transportation vendors.   The emerging multi-standard model in the transportation industry is customer-friendly, but costly and complex for the carriers who must manage highly customized e-commerce infrastructures.

Coffee Product Ecosystem and B2B Information Flows

Similar challenges exist for other trading partners involved in coffee-related transactions:

• Government Trade Ministries – are charged with monitoring the import and export of coffee products across their borders.  Imports and exports must be properly classified to ensure the appropriate taxation of goods.  Incomplete or inaccurate documentation will result in delayed processing and financial penalties to either the buyer or supplier.  To expedite trade processing, governments support electronic interfaces with importers and exporters of goods.  However, government ministries focus e-commerce capabilities on broader, industry-neutral standards such as EDI or ebXML.  Such an approach creates challenges for long tail standards adopters such as Green Coffee bean buyers and sellers.
• Commercial Insurers – offer policies that compensate the buyer or seller of a coffee-related transaction for losses, damages or theft that occurs during the transportation of goods from origin to destination.  Such losses might occur from inclement weather, collisions, stranding, pirates or acts of war.  Damages might be caused by seawater, fire, smoke or chemical contact with the coffee goods.  Insurers require documentation of the shipment contents and value in order to underwrite a marine coverage policy.  To expedite the processing of the policy, insurers offer electronic interfaces to submit documents such as shipment advices, bills of lading and packing lists.  Similarly, insurers can distribute insurance certificates electronically to a buyer, seller, shipper or banker facilitating the trade.  Insurers utilize specialized standards to support underwriting, policy rating, claims processing and customer billing processes.  For example, the ACORD standards offer a highly specialized set of transactions designed to orchestrate insurance transactions.  Both ANSI X12 EDI and EDIFACT offer insurance document sets as well.  Varying standards between insurers and their customers creates challenges for all parties.

Green Coffee XML offers tremendous return on investment and unparalleled levels of efficiency for producers and brokers of coffee.  However, the value proposition becomes substantially diluted for other market participants with core businesses that utilize alternative e-commerce frameworks.  Consequently, there are tradeoffs to be considered when evaluating whether to adopt specialized, industry sub-sector level e-commerce standards or to rely on less robust, but more highly adopted standards such as EDI.   As cross-industry trade continues to grow, there will be an increasing level of tension between competing e-commerce frameworks.

Steve Keifer

© Copyright 2008 GXS, Inc.  All Rights Reserved.

The Long Tail gets Longer 

I was visiting a US consumer products brand leader a few weeks ago to present GXS view of market trends and best practices.  Of course, one of the concepts I introduced was my theory on the Long Tail of B2B Standards.  The chart actually initiated a provocative discussion on the varying e-commerce standards in use throughout industry today.  The discussion revealed to me that the tail is even longer than I originally anticipated…

This particular brand owner markets a variety of consumer packaged goods in the coffee category.    As a result, they engage in the purchase of ingredients such as green coffee beans from suppliers in Latin America and other parts of the world.  I was surprised to learn that there is actually an e-commerce standard that governs how contracts, pricing and transportation documentation is exchanged amongst buyers, sellers, brokers and shippers of green coffee bean products.  Over the past two weeks I have been researching this standard and have arrived at a number of fascinating insights about the coffee sector…

My Coffee isn’t Green it is Brown 

This is true.  The coffee we drink is not green.  It is dark brown or some might say black.  However, the coffee does not start out that color.  Coffee is created from green beans grown on coffee plants typically harvested in large commercial plantations.  The beans are actually wrapped in a fruit-like flesh while being grown.  Once harvested, the exterior is removed to reveal the bean itself.  Prior to roasting, the beans are soaked, cleansed then dried by air and sunlight.  The roasting process transforms the color of the bean from green to yellow then light brown.  As the bean expands in density and doubles in size it will eventually crack resulting in the powdery material which is used to produce the beverage we drink every day.

Green Coffee Association (1923-Present) 

The XML standards for the coffee sector are created by the Green Coffee Association (GCA), an industry organization which serves to promote the commercial and regulatory interests of coffee growers, brokers and buyers.  GCA provides the industry with a number of critical functions including:

• Standards to ensure the uniformity of coffee contracts, bills of lading and other commercial documents.
• Liaisons with third parties such as the International Coffee Organization and Coffee, Sugar and Cocoa Exchange.
• Lobbying with the governments of various countries to promote free trade policies devoid of import quotas and fixed pricing.
• Rules and procedures for the arbitration of disputes amongst buyers and sellers arising from order fulfillment discrepancies or payment delinquencies.

Green Coffee XML Launches 

On July 23^rd, 2001, GCA launched a series of XML schemas designed to digitize and standardize processes for buying, selling and transporting coffee.  Historically, contracts for coffee were processed on standardized forms purchased by the GCA and completed using a typewriter.  As computer automation evolved, GCA sought to develop a machine-to-machine e-commerce process for buyers and sellers to exchange orders, pricing and transportation data.  The XML standards prevent trading partners from designing their own forms which may not contain sufficient detail to fulfill an order to arbitrate a dispute.  The flexibility of XML offers the benefit of standardization, while offering buyers the latitude to specify a wide variety of tendering, payment, transportation, insurance, pricing and performance measurement terms in the contracts.   The GCA XML schemas can be exchanged directly over the Internet or through a third party network. 

Green Coffee Association in 1923

Why does Green Coffee need its own XML Standard? 

The commercial trade processes for coffee beans are much more complex than you might imagine.  Below are a few examples of the variability that can exist in terms and conditions for coffee contracts:

• Contract Types – There are nine different types of coffee contracts to accommodate a variety of sales scenarios for transactions outside, inside and at the border of the country of destination.
• Quantity – Bulk coffee can be measured in metric tons, long tons, pounds, kilograms or weight denominated bag sizes (e.g. 75 kg bag).
• Packaging – Coffee can be packaged into natural fiber bags, bulk container liners or synthetic fiber super sacks.
• Insurance and Freight – parties must agree upon who will pay for cargo insurance as well as freight charges such as currency adjustments or congestion surcharges.
• Technical Descriptions - including crop year, grade, color and moisture tolerances are used to specify quality levels.
• Quality Claims – must be filed within specified timeframes such as 15 days of discharge, tender or government clearance.
• Weighing – processes are typically agreed upon in advance to specify when, where, how and by whom coffee will be weighed for invoicing purposes.
• Position – the transfer of ownership can occur at five different points in the supply chain.  GCA refers to these locations as shipment, afloat, arrival, deliver and spot.
• Tender – transfer of ownership can only occur with the presence of the specified types and numbers of documents such as the bill of lading, insurance certificate and commercial invoice.
• Payment – Funds transfer can occur directly between buyer and seller on open account terms or by a bank facilitated transaction such as letter of credit.

The Green Coffee Association’s XML standard offers an excellent example of the Long Tail of B2B Standards.  The standard orchestrates a highly specialized set of business processes within an industry subsector.  Tremendous benefits can be derived from market participants as a result of the flexibility offered via the wide variety of tendering, payment, pricing and performance management terms that can be modeled in the XML.  Such benefits would not be practically achievable with a more generalized standard such as EDI… 

Steve Keifer

© Copyright 2008 GXS, Inc.  All Rights Reserved.

Last weekend we had some friends over to visit our house and rather than cooking we decided to place an order for pizza delivery from Dominos.  Ordering a pizza today is amazingly convenient.  We didn’t even have to pick up the phone.  Instead we placed the pizza delivery order online using the Dominos web site and a credit card.  The fact that you can order a pizza online should probably come as little surprise in today’s increasingly Internet-centric world.  What did surprise me, however, was the new Domino’s Pizza Tracker site that provides you a step-by-step update on the status of your order.  Using the phone number that you used to place the order you can login to a graphical interface that monitors the progress of your delivery.  The web site also displays the street address of your delivery, the complete contents of your purchase and the exact time of your order.   The tracker shows five different steps throughout the food preparation and delivery process:

1. Order placement
2. Food preparation
3. Baking
4. Boxing and packaging
5. Delivery en route

My tracker even told me the name of the driver who was coming to our house!  All that was missing was a link the to the driver’s MySpace page so you could learn more about he or she before they arrived….

Dominos launched this new tracker service on January 30^th.   I am not sure exactly how it works, but the system somehow ties the local operations systems in each store to the B2C web site on a real time basis. One thing I will bet on is that it doesn’t use RFID.

The tracker site is one of the more customer friendly web experiences that I have seen in recent years.  In fact, there is even a survey that consumers can fill out after the delivery to comment on their experience.  So as I ate my pizza I started thinking about the idea of providing customers real time visibility into the status of their orders.  And I began to relate this to some of the customer visits I have conducted recently with multi-national corporations in the automotive, high tech and retail industries.  One thing that I am consistently surprised by is how little visibility many of the largest companies have to inventory moving through their supply chains.  Most of the order management portals large manufacturers provide their customers don’t come anywhere close to the supply chain visibility that Dominos offers its consumers.  So I ask you - if the average Dominos franchise with an employee base of 10 and annual revenues of $580K can notify me of the exact time that a pizza is boxed and taken out the door for delivery, why can’t a multi-billion dollar manufacturer of airplane parts be able to tell their customers when a $50M shipment of goods has arrived at a port and cleared US customs?

The good news is that many manufacturing leaders seem to be recognizing the challenges associated with lack of supply chain visibility.  At GXS, we have seen a recent surge in interest amongst large manufacturers seeking to provide their key distributors and customers with better visibility to outbound shipments.  The highest concentration of demand seems to be with industrial goods manufacturers who are seeking better quality data on ocean freight traversing long distance trans-Pacific routes.   Consumer products companies are slightly ahead of their peers in the automotive, high tech, aerospace and industrial machinery sectors when it comes to supply chain visibility.  In the industrial sector, it is not uncommon to find that neither buyer nor supplier has visibility to the location and status of shipments of goods once they leave the manufacturing plant.  Interestingly, this situation applies even to high value goods including consumer electronics such as high definition plasma televisions, kitchen appliances such as refrigerators and computing equipment such as robotic tape backup libraries.  Not only are these expensive goods targets for theft and counterfeiting, but many of them can be easily damaged without proper handling.  Due to the value of the goods, suppliers often purchase cargo insurance to protect against these types of threats.  Also due to the value of the goods, many suppliers seek out third party financing for their inventory in transit.  The financing frees up working capital that would otherwise be tied up in long distance supply chains. 

So the point here is that we have multi-million dollar shipments of industrial goods insured and financed by third parties and no one other than the transportation provider holding the actual inventory seems to know the location at any point in time.  Should industrial manufacturers hire pizza delivery persons to help them?  That is probably unnecessary.  But they should consider investing further in transportation management applications, particularly in logistics visibility suites that offer customers insights into the status of inbound freight.  I have written a few recent posts about the value of transportation management suites and some of the new software-as-a-service deployment models which are emerging that outline these concepts in further detail…

• Is Your TMS Application Costing You an Arm and a Leg? 
• SaaS – A Less Crude Approach to TMS

Steve Keifer

© Copyright 2008 GXS, Inc.  All Rights Reserved.

In July 2006 Chris Anderson published a book called The Long Tail which illustrated how new Internet business models from pioneers such as amazon.com, Netflix and Apple have enabled an entirely new economic model for the media and entertainment industry.  Even if you have not read the book, you are probably familiar with the concept.  Traditional mass market economics have led to product strategies focused on developing the few blockbuster “hits” that appeal to the mass market.  Niche products with smaller target markets were generally not stocked in stores, played on radio stations or featured in movie theatres due to the lack of a profitable distribution model. 

Chris Anderson states that in the traditional brick and mortar retail model, selection was limited by the “tyranny of the lowest-common-denominator.”  In other words, historically selection was driven by economics rather than actual end-user demand.  For example:

• “Wal-Mart must sell at least 100,000 copies of a CD to cover its retail overhead and make a sufficient profit; less than 1 percent of CDs do that kind of volume.”
• “An average movie theatre will not show a film unless it can attract at least 1500 people over a two-week run, that’s essentially the rent for a screen.”

In The Long Tail Anderson proposes that entertainment industry is shifting away from the traditional mass-market model towards a broader market of niche-oriented, micro-segments.   The change is made possible by the unlimited selection of books, movies and music available through Internet channels.  Chris explained that the Long Tail phenomenon is not limited to just the Media & Entertainment sector, but can also be observed in the retail market with eBay; the manufacturing industry with KitchenAid; the advertising sector with Google and the software segment with Salesforce.com.

The Long Tail Concept Applied to B2B

I believe that a long tail effect also has developed in the B2B standards community.  During the early history of B2B in the 1980s and 1990s, EDI was the dominant standard.  There were several variants of EDI utilized in different geographies, most notably ANSI X12 in North America and UN/EDIFACT in Europe and Asia.  Adoption of B2B was concentrated primarily amongst the largest of companies. And data exchange was limited to the use of third party VANs (value added networks) whose applications only supported EDI.   The immaturity of technology and limited market combined to create economics discouraging the development of alternative standards.  In many respects, the B2B e-commerce ecosystem suffered from “the tyranny of the lowest-common-denominator effect” throughout the first two decades of standards.

In the late 1990s, the Internet began to enjoy widespread adoption.  With the Internet, the economics and technology paradigms for B2B fundamentally changed.  Documents could be exchanged using Internet protocols such as SMTP, FTP and HTTP liberating B2B from the traditional private networking models.  XML was created offering unparalleled flexibility to model new transaction types and business processes.  New groups of non-profit organizations (Dot Orgs) were formed with the goal of developing a successor to EDI.  Together these Dot Orgs have introduced dozens of new XML-based standards designed to meet the specialized needs of industry subsectors.  Examples of the new standards include PIDX in the Oil & Gas market, CIDX in the chemicals industry, SPEC2000 in the aerospace sector, RosettaNet in the high tech industry, GUSI in the consumer products sector and papiNet in the forestry market.   The new XML standards offer a level industry specialization and technology flexibility not possible with traditional EDI.  However, the new XML standards have failed to achieve critical mass.  Over 80% of B2B transactions remain EDI-based.  There are a number of Darwinian arguments that could be made about EDI’s ability to fend off multiple targeted attempts to eliminate it.  See my posts on EDI and Darwin (Part 1 and Part 2).  XML, with its genetically superior framework, has yet to achieve significant adoption beyond 10% of the target industry segment.  As a result, the state of the market for adoption of B2B e-commerce standards can be represented in a long tail diagram.

The short head is represented by the handful of dominant standards used globally across various industry sectors.  EDI, with its two major variants ANSI X12 (North America) and EDIFACT (Europe and Asia), is certainly the most prevalent.  The only other noteworthy standard I am aware of is the SWIFT FIN message format used widely in the international financial services sector.  Open Office XML is quickly gaining adoption as Microsoft’s Office 2007 is deployed to more and more desktops. However, all of the other standards remain confined to niches used by only a subset of the targeted community, but each with aspirations of migrating up the tail to become a short head player.I believe that we will see a rapid transformation in the adoption of B2B standards in the coming five years.  More and more industries will migrate from using EDI (the lowest-common-denominator, short head) standards towards industry specific XML (the highly specialized, industry-specific long tail) standards.  There are four major transformational catalysts that are emerging to offer the potential to change the economics of standards for ever.  In upcoming posts I will outline these forces and the evolution of the Long Tail of B2B Standards in greater detail….

Steve Keifer

© Copyright 2008 GXS, Inc.  All Rights Reserved.

In my last post, I made the argument that ERP applications are not designed to support the growing levels of outsourcing in today’s manufacturing ecosystem.  I think what is needed is an “ERP Firewall” for manufacturers to protect their enterprise systems from bad data.  Let me explain this ERP Firewall concept further:

ERP Firewall Defined 

ERP Firewall -         

noun

1.       fire•wall \’fī(-ə)r,wȯl\: an application which permits, denies or takes correction action to electronic data interchanges between an enterprises’ applications and its external business partners systems based upon a configurable set of rules or criteria. 

Restated, an ERP Firewall ensures that bad data from external business partners doesn’t enter your ERP system polluting the quality of information in your enterprise applications.  Much like a normal firewall, an ERP firewall examines all incoming and outgoing data against a pre-configured rule set.  A traditional firewall rule might be to block all incoming clear text FTP traffic on port 21.  Similarly, an ERP firewall rule might be to block all documents which are not in the manufacturer’s list of standardized e-commerce processes.  For example, the firewall might block all ANSI X12 EDI formats which are not 810, 820, 850, 856 or 997 (or EDIFACT formats INVOIC, PAYMUL, ORDERS, DESADV, CONTRL).  As a result, a document such as a 214 or 824 which is not the expected input for any ERP module does not even pass the firewall.    Another example of a rule set might be to route any 810/INVOIC documents without a street address, general ledger code or appropriate tax identifier to an exception queue for manual resolution by the supplier.

Firewall Severity Classes and Actions 

There are four typical actions that an ERP firewall might take based upon its configured rule set.  The action taken will, of course, depend upon the scenario encountered:

1.       Fatal – In this scenario, the electronic document is beyond repair.  Not only will the document fail during later processing, but it could result in financial losses to the company or its trading partners if not stopped.  As a result, the firewall should reject the electronic document entirely by sending a failure notification back to the originator.

2.       Error – The electronic document has a critical error that will fail upon attempted processing.  In this scenario, the error can be remedied, but only with the manual intervention of an end-user at the originating company.  For such scenarios, the firewall should hold the electronic document in an exception queue for the originator to review and repair.

3.       Warning – The electronic document has a minor data quality error that will not disrupt processing, but should be corrected, if possible, in future scenarios.  The firewall will pass the document through to the ERP, but also log the data quality issues in a report.  The logged warnings should be trended for frequency and root cause.  The most common occurrences should be identified and remedied through collaboration with the originating trading partner.

4.       Auto-Fix – In this scenario, the original document has an error that can be automatically corrected by the firewall.  This is the real power of the ERP firewall.   In many cases, bad data can be corrected automatically before reaching the ERP.  For example, missing fields may be looked up in a table, database or via an application web services call.  The original document is then augmented or enriched with the new fields then forwarded for processing.  What other types of auto-fix functionality might exist?  Documents can be split and routed to different ERP systems.  Conversely, outputs from multiple ERPs might be merged into a single document.  A fourth function is data filtering, in which, unnecessary data can be stripped out of incoming or outgoing documents to simplify subsequent processing at the destination.

Manufacturers are investing tens of millions to consolidate, standardize, upgrade and extend their ERP applications to optimize value from their ERP applications.  However, these efforts are undermined and compromised when bad data from business partners corrupts and pollutes the ERP.  An ERP firewall, which can be implemented at a small fraction of the annual maintenance royalty you pay your software vendor, can reduce bad data by up to 50% with just a few simple rule sets.

Steve Keifer

© Copyright 2008 GXS, Inc.  All Rights Reserved.

This week is the annual SAP Sapphire conference in Orlando, Florida.  I didn’t make it to the show this year, but I thought I would offer some insights on ERP and its increasingly interdependent relationship with B2B e-commerce.   The ERP vendors have spent much of the past few years focused on rewriting their applications to support a services oriented architecture approach.  SAP has its Netweaver initiative and Oracle has Fusion.  However, one area I think the ERP vendors have underestimated is the need to redesign their applications to support the extensive level of outsourcing that is becoming predominant amongst their customer base.

The Outsourced Supply Chain

In today’s manufacturing market, outsourcing is becoming more the norm than the exception.  Companies have become more and more specialized within their value chains.  OEMs that traditionally have been manufacturing-oriented are increasingly outsourcing many of their supply chain functions to third parties (contract manufacturers, freight forwarders and third party logistics providers).  Back office functions such as accounts payable, human resources and IT management are being sourced as well to specialized BPO firms.  The overall result of this outsourcing phenomenon is that manufacturers are more dependent than ever on business partners to perform daily operations.  It also means that enterprise IT systems are more dependent than ever on moving data to and from business partner IT applications.  In order to gain visibility to outsourced, external processes, manufacturers must be able to synchronize data in real time with their business partners.  For many manufacturers who outsource critical manufacturing, logistics, distribution and service functions, a growing percentage of the data housed in corporate ERP systems actually originates outside the enterprise.

50% of ERP Data Originates Outside the Enterprise 

I was talking to a customer the other day who told me that over 50% of the data in their ERP system comes from trading partners.  This comment puts in perspective the critical role that B2B integration technologies play in enabling ERP.  It also underscores the need to ensure that bad data isn’t flowing in from external interfaces and thereby corrupting information quality.  Much has been written about the challenges with maintaining what is called “Master Data” for products, customers, employees, assets and suppliers in the past few years.  But I am not referring to bad address information for consumers who move around every few years (i.e. customer master data).  I am referring to non-master, transactional data related to a specific order.  The order data originates from large customer accounts as well as contract manufacturers, third party logistics providers, banking institutions and business process outsourcers.

ERP Needs a Firewall to Protect it from Bad Data 

Who cares about bad data in an ERP?  Both line of business managers and IT personnel should be concerned about the consequences of this growing problem.  Bad data pollutes a manufacturer’s ERP system.  The result is a loss of productivity.  But to be more specific, data quality errors result in three negative impacts to a manufacturing organization:

1.       Longer time to process – Time sensitive processes may be delayed while accounting, warehouse and customer service personnel research and resolve data issues.  For example, if an invoice is posted to an accounts payable system without a general ledger number to apply the cost against, then an accounting clerk must phone the supplier or internal buyer to capture the appropriate data.  If a purchase order is pushed to an order management system with an invalid part number or SKU then the sales organization must contact the customer to discuss an appropriate substitution. 

2.       Higher cost to process – Personnel must spend time and effort manually correcting data in the ERP application or fixing problems resulting from the processing of the bad data.  Higher volumes of manual processing unnecessarily inflate costs and erode margins.  For example, in the retail industry studies have determined that over 60% of invoices have data errors.  And each error costs between $40 and $400 to correct.

3.       More mistakes during processing – The probability of an error increases exponentially as soon as manual processing begins.  By comparison, however, human intervention could be relatively inexpensive when compared with scenarios in which bad data goes undetected.  What are the costs of missing a contract commitment with one of your top 5 accounts?  Or of fulfilling an order incorrectly with the wrong parts shipped to the wrong location? Such data quality errors might seem like insignificant problems when viewed at a microscopic level for each individual order.  However, the costs of increased Days Sales Outstanding from invoice processing delays and customer penalties from failed order fulfillment commitments can quickly compound to have a macroeconomic impact on financial performance.

Why Firewall your ERP? 

Why aren’t ERP applications designed to capture these types of business process and data quality errors?   Actually, SAP and Oracle do provide extensive business logic and data integrity checks within their applications.  When an end user keys in data to a graphical interface the native ERP business logic will detect a wide variety of errors.  However, when the data flows through a B2B gateway and is subsequently uploaded into the ERP database there is very little data checking that occurs. What can manufacturers running ERP do to prevent bad data from corrupting their enterprise applications?  One option would be to hire a systems integrator to develop custom code to enforce data integrity standards for B2B imports and exports.  Additionally, a new set of user interfaces would be required to manage exceptions identified by the data checks.  Any customizations to ERP applications come with a significant overhead.   With each new release of the vendor’s software, the customer must perform extensive regression testing and often software updates.  I think a better option is to deploy an application at the edge of the enterprise that inspects incoming and outgoing documents from trading partners for data integrity issues.  Such an application would effectively be acting as an “ERP Firewall” for bad data.  The firewall would inspect the contents of EDI, XML and other files in a Demilitarized Zone for quality of content.  Bad data would be rejected to the sender or held in a queue for exception processing.  Good data would be passed straight through to the ERP for immediate processing. 

Not only is EDI the dominant standard but it is use is growing more accepted, not less.  Microsoft recently added an EDI adaptor to its BizTalk Server 2006 product to make its integration platform more competitive in the B2B segment.  This may seem strange to those who view Microsoft as chief evangelist for XML and Web Services technologies.   

EDI adapted to the Internet  

Rewind the clock 10 years and you will recall that it was not just Microsoft, but countless marketplaces, exchanges and industry standards organizations each proclaiming themselves’ EDI killers.  Few technologies have the survived so many focused attacks as EDI has.  These attempts to replace EDI were not unreasonable theories.  The introduction of the new disruptive technologies that emerged during the Internet era would have been a natural transition period to migrate from EDI to XML.  But while the new XML messaging standards groups were busy plotting to exterminate their predecessor, EDI found a way to adapt to the changing ecosystem by evolving in two new directions:   

• ASX Models – Much of the negative sentiment around EDI in the late 1990s was actually unrelated to the standard itself, but instead focused on the expensive communications and transmissions processes for EDI documents.  With the Internet perceived to be “free,” many questioned why there was continued use of expensive, proprietary 3^rd party VAN networks.  From this vision the ASX (e.g. AS1, AS2, etc.) standards were borne and EDI’s lifespan was extended indefinitely.  EDI documents could be wrapped in a popular Internet protocol such as HTTP or SMTP then transmitted directly between trading partners avoiding the use of VANs.
• Web EDI –Another key limitation of EDI was its complexity.  Many small businesses struggled to find the budget or expertise to deploy a translator.  The user-friendly, universally deployed Internet browser was an obvious choice to simplify B2B e-commerce.  With just an Internet connection and no B2B software, an end-user could access web-based applications to send and receive electronic documents.  The web application converted the user inputs into an electronic document for exchange with business partners.  Of course, EDI, due to its ubiquity, was the default output format for these new web portals.  The result?  A further extension of EDI’s longevity. 

GXS TradeWeb - One of the first Web EDI Platforms

EDI is reborn in Emerging Markets  

Perhaps, XML advocates should try an alternative approach to adoption.  Instead of seeking to replace established EDI programs in Western markets, perhaps they should seek out green field opportunities in emerging markets to institutionalize XML.  While this is another logical theory, the global nature of commerce in today’s market preempts such an approach.  EDI has already embedded itself in the critical value chains of the developing BRIC (Brazil, Russia, India, China) countries.  Western automotive manufacturers such as Volkswagen, Daimler, Ford and GM imported EDI standards to China years ago along with the new plants they constructed.   Similarly, western retailers such as Metro, Kingfisher, Home Depot and Wal-Mart, each of which source billions in merchandise from emerging markets, have driven adoption of EDI amongst manufacturing communities in China, India, Southeast Asia and Eastern Europe.  As a result, every day hundreds of businesses in emerging markets are implementing new B2B platforms based on EDI, because it is the standard their customers wish to communicate with them in.   

Will EDI ever die? 

My guess is “no.”  However, I do think in the next decade we will see a gradual increase in XML-based standards to represent 40-50% of e-commerce transactions.  More thoughts on this in a future post…

Steve Keifer

© Copyright 2008 GXS, Inc.  All Rights Reserved.

EDI continues to be the dominant standard in B2B e-commerce.  If you don’t believe me, I would encourage you to take a look at the report titled B2B Integration Trends: Message Formats published last year by Ken Vollmer of Forrester Research.  Forrester estimated that out of all B2B transaction volumes in 2007, 85-90% use EDI.  XML and other file formats, while growing at nearly double the rate of EDI, remain, at best, 15% of transaction volume.  EDI’s dominance is a subject that mystifies many outside the industry.  How does a technology dinosaur such as EDI manage to remain so popular and prevalent through an era that has witnessed the birth of unprecedented levels of disruptive technology?  If Charles Darwin were alive today he might enjoy studying the characteristics that have led to EDI’s survival despite the introduction of genetically-superior species to its ecosystem.   Here is my assessment. 

Charles Darwin

Six Survival Characteristics of EDI   

There are six factors, in my opinion, that lead to the continued prevalence of EDI as the world’s dominant e-commerce standard:

1.       EDI is mature.  It has been in use for over 20 years resulting in a proven, reliable, business critical reputation amongst its widespread users.  If you are selecting a technology to run your business on – would you select a new, emerging framework or a proven, mature standard?

2.       EDI is working.  Why fix what isn’t broken?  EDI is successfully supporting the value chains for many of the world’s largest companies today.  Corporations need a compelling business benefit to migrate to XML.  The business plan must justify the expense to perform a migration, risk of possible business disruption and opportunity cost compared to alternative investments.

3.       EDI is cheap.  The costs of EDI were often cited as its top barrier to adoption throughout the 1990s.  However, the barriers to entry for EDI based technologies have declined significantly in recent years.  As the de facto standard almost all B2B integration software packages and SaaS-based services include out-of-the-box EDI functionality.  XML often requires customization, especially for low end packages.

4.       EDI is ubiquitous.  EDI had the advantage of being the only standard for e-commerce for over a decade.  During that time, EDI became pervasive in a number of industries such as health care, automotive, banking and retail.  As a result, businesses that choose to utilize EDI have a high level of confidence that their trading partners will be able to receive their documents.  By contrast, businesses that try to standardize on XML face significant headwinds as their entire trading partner community must become XML-enabled.

5.       EDI is not industry specific.  EDI’s lack of industry-specific data fields and process models is often listed as a shortcoming.   However, one of the keys to EDI’s ubiquity has been is applicability across multiple industries and geographic regions.  Very few industries in today’s world are truly vertical leading to challenges when partners transact commerce across industries.  For example, some of the fastest growing channels for high tech manufacturers are the aerospace, retail, medical and automotive sectors, none of which use the high tech XML standard - RosettaNet.

6.       EDI is network protocol independent.  It works across value added networks.  It works with legacy dial-up protocols.  It works with newer Internet standards such as AS2.

These six factors are the critical genetic and environmental factors that have led to EDI’s longevity.  In today’s world of multiple, competing e-commerce frameworks, dominance will come from survival of the fittest.

Steve Keifer

© Copyright 2008 GXS, Inc.  All Rights Reserved.

Most readers of this headline will doubt the veracity of such a claim. Surely, the translator bundled with one of the leading integration brokers from Sterling Commerce, Software AG’s webMethods or IBM must have the highest market share.  One could argue GXS’s Application Integrator could also compete for such a title.  Well…Microsoft does now boast over 7,000 customers for its BizTalk Server.  And the new version, BizTalk 2006 R2, has several significant enhancements to its feature set including native support for EDI.  By the way - it is about time!  I am pleased to see that even Microsoft has acknowledged the continued dominance of EDI as the world’s most popular B2B document format.  But I am not referring to BizTalk when I stated that Microsoft’s translator had the largest market share.  I am actually referring to Office 2007.

Microsoft Office 2007 – The Translator 

The newest version of Office is based upon XML standards, specifically the Open Office XML standard.  This new XML standard is a different file format and structure than the previous binary format used in prior versions up to Office 2003.  The older binary formats .xls for Microsoft Excel, .doc for Microsoft Word and .ppt for Microsoft PowerPoint have actually become so well known that many people I know use them as if they were words.  I often see e-mails or on-line chats referring to .xls and .ppt.  XLS is much simpler to type than “spreadsheet” and everyone knows what a “PPT” is.  Open Office XML will challenge the established shorthand with a new four letter naming convention for file extensions.  Starting with Office 2007 .xlsx is the default format used by Microsoft Excel, .docx is used by Microsoft Word and .pptx by Microsoft PowerPoint.  If you are not using Office 2007 yet, you may have received an e-mail with a .docx file that you could not open.   In fact, this is causing considerable confusion across the industry as most users on earlier versions of Microsoft Office do not know of the new file formats.

Fortunately, Microsoft has not abandoned the binary file formats.  Using the “Save As” command or what Microsoft refers to as “Compatibility Mode” a user can save a file created in Office 2007 in the .doc, .xls and .ppt formats, which brings me back to the title of this blog.  I have been using Office 2007 for almost a year now and I must spend, at least, 20 minutes a day converting files back and forth between Open Office XML and the binary format.  GXS is only about mid-way through the Office 2007 upgrade.   And many of my colleagues at other companies have not upgraded to 2007.  The rules of proper e-mail etiquette suggest that one should send the older Office 2003 binary file format by default to avoid frustrating your peers.  As a result, my office software has become a powerful spreadsheet tool, word processor, presentation designer and document translator.   And I am not alone.  Hundreds of thousands of other end-users like myself are translating Open Office XML files to Microsoft’s binary Office file format every day.  By my estimates, the conversion of Microsoft Office file formats is occurring on a broader scale than any other document transformation process making Microsoft Office 2007 the world’s most popular translator.

How Long will Microsoft’s Reign as Leading Translator Last? 

Although Microsoft Office may enjoy top standing today in translation volumes, its reign will not extend forever.  Forrester Research recently conducted a study of Office 2007 adoption amongst North American and Western European businesses.  The study found that 43% of enterprises surveyed have some level of Office 2007 in use.  Furthermore, 93% of respondents stated they will be deploying Office 2007 in the next 12 months.  Adoption is occurring much faster than I would have expected.  However, the looming economic recession may decelerate upgrade efforts for some users.  The tapeworm-like memory usage of Office 2007 necessitates a PC hardware upgrade for many users.  Such non-essential capital spending may be deferred until 2009 or 2010 by corporations suffering from recessionary pressures.  Nonetheless, at some point in the next five years, Office 2007 will enjoy a leadership position on the desktop.  And at such time, translations to the older binary formats will likely drop dramatically.

Open Office XML – The Conspiracy Theories 

There has been a significant amount of controversy surrounding the new Open Office XML standard.  Open Office XML recently became an official ISO standard along with PDF, HTML and the other office standard – Open Document Format.   Remember that standard should always be assumed to be plural even when used without the trailing “s.”   Microsoft has been accused of unfairly influencing the ISO standardization process as part of its plan to promote its own interests.  I actually don’t think it was Microsoft that is really behind the aggressive lobbying efforts.  My conspiracy theory is that the disk drive companies such as Seagate and Western Digital are really championing the effort.  The storage manufacturers have the most to gain from a new office document standard.  For the next five years while there is a parallel set of document formats in use by Microsoft Office applications, end users will need to store two versions of many files - one in the new XML-based 2007+ format and the other in the older, binary 2003 format.  The effect is a doubling of disk capacity required by end user.

Open Office XML has a number of fascinating dimensions to it, both from an industry standards perspective and from a business applications standpoint, but my PR Director has told me that my blog entries are too long so I will not carry on, but instead leave you with some links to research the standards on your own:

• Wikipedia entry on Open Office XML ( http://en.wikipedia.org/wiki/Open_Office_XML)
• Forrester Research - The State of Microsoft Office 2007 Desktop Adoption - March 31 2008
• Wall Street Journal - Microsoft’s Office Push Scrutinized by EU – February 8, 2008
• Gartner - Standards Bodies’ Approval of OOXML Doesn’t Change Status Quo – April 8, 2008

Steve Keifer

© Copyright 2008 GXS, Inc.  All Rights Reserved.

Last week I spent three days in London conducting a series of meetings with customers, partners, analysts and local media.  These trips are always insightful for me, but last week was a particularly interesting time to be in London.  First, the French President Nicolas Sarkozy and his new wife Carla Bruni Sarkozy were visiting the UK, which generated a lot of attention in the local press.  Second, there was a significant disappointment over the problems at Heathrow’s new Terminal 5.  On the opening day of the new terminal, the baggage handling system failed leaving thousands of passengers without luggage and resulting in the cancellation of dozens of flights.  Fortunately, I was not flying British Airways so I was not impacted.

The third reason I found this trip more interesting than others was the sense of urgency amongst everyone I met with.  Everyone was rushing to finalize activities before the end of first quarter.  This year’s first quarter is an important economic event to be sure.  Not only will it be the first financial period for 2008, but the quarterly earnings will provide insights into how widespread and deep the recession has become.  Of course, every CEO wants to be able to downplay the impact of the recession on their financial results during the upcoming quarterly earnings call.  So there is added pressure on both sales and finance organizations to ensure that they reach their forecasted goals. 

End of Quarter Stress 

End of quarter stress is not unusual for leaders in sales and finance, but it is becoming increasingly challenging for IT operations personnel as well.  I was speaking to a customer in the manufacturing sector last week.  He was explaining how critical their IT infrastructure is for their quarter-end operations.  The last three weeks of the quarter are extremely hectic for these types of manufacturers who are trying to outdo the previous quarter’s revenue results.  Sales, order processing and warehousing operations are often operating 24 hours a day including Saturday and Sundays.  Frequently, it all comes down to the last day of the quarter.   Products that ship as late as one minute before midnight can still qualify for booking in the quarterly sales reports. IT systems must be able to keep pace with the performance requirements of demanding end-users during this stressful period.  And they absolutely cannot have downtime – either scheduled or unscheduled.  Order processing, warehouse management and transportation management are critical for manufacturers.   It is no surprise that ERP applications must deliver 100% uptime to support business operations.  However, I doubt many realize how mission critical B2B (EDI and XML) connectivity is for quarter-end activities.  An interruption in electronic document flow with business partners can bring a company’s supply chain to a halt – much like the failure of a baggage handling system at Heathrow’s Terminal 5.  As supply chains become increasingly digitally integrated more and more buyer-to-supplier communications are being sent electronically.  A loss of connectivity even for a matter of a few hours can jeopardize a company’s ability to meet its quarterly financial targets.  A loss of data, specifically new orders, could be catastrophic.

The Impact of IT Failures 

The root cause of the meltdown at Heathrow was that the baggage handlers IDs were not recognized by computers.  As a result not only were airport personnel not able to log in to the bagging handling system, but they also could not navigate physically around the airport in and out of secured areas.  Eventually the system became overloaded and checking of baggage was suspended.  Delays unloading and loading of baggage postponed and even cancelled some flights.  Spanish owned BAA (British Airports Authority) had invested over £4B and 20 years of planning to construct the new concourse.  And the bagging handlers and computer applications had undergone 18 months of extensive testing, which proves that even the most well designed and planned systems can fail under peak loads.

What would happen if B2B (EDI and XML) connectivity at a multi-billion dollar manufacturer were lost on the last day of the quarter?  Electronic purchase orders from large customers and distributors would not be able to be received.  Even orders placed prior to the outage could not be confirmed electronically.  Third party logistics providers could not be notified of shipments that were ready for pickup.  In effect, the company’s supply chain would be significantly handicapped.  Of course, orders could be taken over the phone and then processed manually.  However, this would likely be a nuisance to high volume buyers accustomed to utilizing highly automated ordering processes in their procurement systems.  Theoretically, electronic documents would not be lost as a result of an interruption to B2B communications.  Most B2B transactions are asynchronous.  As a result, purchase orders, confirmations and shipping instructions would be held in a queue until the connectivity was re-established.  But depending upon the length of outage and the time period it occurred, the backlog may not be recoverable.  Suppose an outage occurred from 1PM to 5PM on March 31^st.  Sales, warehouse and transportation personnel would probably not be able to process the backlog of orders even if they worked until midnight.

I wonder how many companies and vendors will experience an outage in their B2B applications during this quarter’s final day…or how many are expecting to fulfill orders based upon incoming parts shipped via BA’s Cargo service…

Steve Keifer

© Copyright 2007 GXS, Inc.  All Rights Reserved.