Tag Archives: ecgrid

Focus on HUBS – One of Three Types of EDI Customers

Image

A HUB is just one type of EDI customer. Hubs are characterized by high volume, lots of partners, high availability and high accuracy. The concept of the “Hub” is simple. These are the companies who reach out to their trading partners and request those partners to trade electronically.
Let’s characterize the three types of EDI customers:

(1) Hubs

(2) Spokes (low turnover of trading partners but higher technical requirements)

(3) Ecommerce Service Providers (ECSB) (a “hybrid” with high turnover rate, deal with all implementation guides, and amount to a “Hub of Spokes”).  An ECSP is what we previously called VAS (value added services) such as SPS Commerce.

EDI data has historically been exchanged between business partners through value-added network services (VANS), employing a simple hub-and-spoke model, the business partners being the spokes and the VAN operators assuming the central hub role. While being quite effective in the pre-Internet era, VANS are hardly competitive anymore. However, more recent approaches to the reliable exchange of EDI data like EDIINT AS/2 create new issues: While eliminating the VANS’s high volume costs, Internet-based point-to-point approaches like AS/2 dramatically increase the one-off setup costs by requiring all participants to assume server roles, not just a single dedicated hub. While acceptable for large companies, this is bad news for small and medium-sized businesses (SMBs).

An Iteration of the Hub – SuperHUB

Image

The most noticeable difference between VAN1 (the “traditional” VAN from the 1980’s) and VAN2 (today’s technology) is the fact that a company can operate their own network instead of being a customer on somebody else’s. Control the network according to your needs, Embed EDI Network functions within your code, and start creating completely unique EDI management functions that will overturn 20+ years of non-optimized EDI integration nightmares!

ECGrid is an example of VAN2. It supports AS2 and FTP and API, combined with superior account control, all at a fraction of the cost of running your own communications racks. It includes:

  • Intersystem interconnections via API calls and world class net ops.
  • Next generation routing architecture connecting to a world of global commerce networks.
  • VAN2 empowers cloud ventures to penetrate the SME sector – the next EDI frontier – with an estimated $30B of untapped IT revenue waiting to be captured.
  • These new B2B cloud services are the place to participate in supply chain and horizontal commerce operations. It allows you to run a “virtual VAN”.

Todd Gould and GXS a.k.a. David and Goliath

Image

Well the David and Goliath battle continues. See the letter below. We all hope David can find a stone for his slingshot and get the giant between his you-know-whats.

GXS to Terminate Loren Data Interconnects

Marina del Rey, California – June 4, 2013 – GXS has begun notifying its customers of its intention to terminate connectivity to Loren Data’s ECGrid® EDI Network on March 4, 2014. GXS has posted this notice on its website: Interconnect Service Announcements (http://ow.ly/lERIw — if that link is broken, another copy of the notice can be found at http://tinyurl.com/kyv2x55). Additionally, Steven Scala, Senior Vice President Corporate Strategy and Development, has informed Loren Data that its ECGrid Service Provider customers must negotiate new connections directly with GXS and will not be allowed to move their accounts to any other VAN.

Loren Data disputes all allegations of that notice, including the misinformation claiming any part of this egregious act was negotiated with Loren Data. Any service issues mentioned in the GXS advisory are self-serving and falsely attributed to ECGrid. The uptime, visibility, accuracy and reliability of ECGrid are among the top in the industry. GXS’s refusal to establish industry standard interconnects between the competing networks since 2001 has forced excessive and unnecessary support burdens and expenses on Loren Data and on trading partners of both systems. GXS’s attempt to frame this as anything other than an anticompetitive attack on Loren Data and its customers is disingenuous.

Todd Gould, President of Loren Data, comments, “Far greater than the termination of the ICC interconnect by GXS in 2002, this is an unprecedented act of monopolistic power to control and eliminate competition in this market. The fundamental premise of EDI is to allow each trading partner to pick the solution provider and system that best suits its needs, not the one that best suits GXS.

“The list of actions taken by GXS against all EDI service providers, and Loren Data as a VAN for service providers, demonstrates a long and concerted effort to prevent new competition from entering the industry by controlling interconnects. These are the same interconnects that GXS enjoyed for its own benefit, and could not live without, through the early years of EDI.

“The acquisitions of both the IBM and Inovis VANs allowed GXS to acquire enough subscribers on its system to become an essential facility to connect to for all other EDI providers. GXS is now exploiting this purchased monopoly position to knock competition out of the market, rather than competing with better-valued products to win customers. How the GXS-Inovis merger survived a Hart-Scott-Rodino review in 2010 will always puzzle me, but with 20/20 hindsight it is clear that the merger should never have been allowed.”

Gould continues, “With over 1,000,000 mailbags successfully processed between GXS and Loren Data in May 2013 alone, it is unconscionable the amount of chaos and instability this latest move by GXS will create in the market.”

In response to GXS’s newest attempt to coerce its customers’ trading partners to sign up with “GXS-approved” providers or GXS directly, Loren Data is now offering end-users unprecedented direct access to ECGrid. This will insure continuity to the more than 12,000 trading partnerships that GXS is determined to disrupt. Any companies interested in taking advantage of this offer should contact Loren Data at gxs.alternative@ecgrid.com.

Loren Data continues to pursue all legal and administrative avenues available in addition to industry outreach. A Petition for Writ of Certiorari was submitted to the U.S. Supreme Court (No. 12-1273) on April 23, 2013 for the antitrust case of Loren Data Corp. v. GXS, Inc. Please contact Thomas Kettenmann (tkettenmann@LD.com) for access to the entire case history and any legal inquiries.

Loren Data’s ECGrid system is the preferred network for more than 10,000 trading partners, the majority of which are on major service providers such as SPS Commerce, CovalentWorks, NetEDI, EC InfoSystems, Radley Corporation, Pinnacle Data Systems, DiCentral and others. ECGrid currently services their customers’ 30,000+ trading partners on over 100 different systems including VANs, X.400 networks and direct connections. ECGrid is the only system developed specifically to meet the needs of EDI service providers, delivering the tools, visibility and reliability necessary to be a backbone EDI routing network. The industry leading ECGridOSSM web services API allows developers to deeply integrate EDI applications on top of the powerful ECGrid infrastructure. See http://www.LD.com and http://www.ECGridOS.com for more information.

ECGrid is a registered service mark and ECGridOS is a service mark of Loren Data Corp.

Contact:

Kristine Finlay
kfinlay@LD.com
Ph: +1-310-491-0380

Todd Gould’s Call For Input

Image

Call for Input: Accessing Web Services in various environments. Contribute your experience.

There are many new languages that support REST (POST / GET) and ECGridOS allows this, albeit without the rich error handlers of SOAP – but there are many instances where new language enthusiasts will find themselves in a position to use ECGridOS, and the collective knowledge amassed in our developer community is invaluable.

ECGridOS developers:

An increasing number of web developers that use text editors and non-IDE non Visual Studio coding environments are looking for advice on the best way to make Web Services function calls from popular web languages, such as Ruby, Python, PHP, Scala, Hasklell, I think you get the idea.

If you can contribute your favorite non Visual Studio method for importing and unwrapping the ECGridOS WSDL (.ASMX), could you please help a brother out and post your ideas on the ECGrid Developers Forum – Users of Eclipse, you could weigh in, too. There are many new languages that support REST (POST / GET) and ECGridOS for the moment allows this, albeit without the rich error handlers of SOAP – but there are many instances that a new language enthusiast will find themselves in a position to use E

For those that have not joined, the geniuses that never needed nor asked for help, Jim….I am asking you and folks like yourself, to please go to  http://forums.ecgrid.com/index.php and let us know the inner working of PHP web clients and stuff. Note: The forum is much faster now, thanks to Todd.

This entry was posted on Wednesday, March 20th, 2013 at 12:06 pm and is filed under ECGridOS Developers. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.