Time will tell. For sure this isn't the first time there's been pressure on the X12 standard. We still get comments like "Isn't EDI a dying protocol because of data tools like XML?" Granted that most recent comment coming just last week was from an international implementer. But that only begs the question about the relevance of EDI in the international community.
The basic facts about the new pricing schedule are this. Beginning with the 006050 specification, pricing will be based on a per-year usage with an annual maintenance fee equal to 20% of the original cost. The basic standards set now sells for $800, so it's easy to say that the costs are relatively minor. But most commercial translator vendors, or those larger entities that create and maintain their own applications, purchase the table data for as much as $19,000.
Those prices may not be news to those who have purchased the standards set as non-members of the ASC X12. But what is new for 2013 is the annual renewal fee. Here's the text from the store.x12.org site:
One issue that Leah Halpin, Senior EDI Consultant with Project Management and Consulting of America raised is how the organization intends to enforce its renewal fees. "If some kind of kill switch is built into the code that disables its use if the renewal fee is not paid, massive disruptions could result." That's because the licensors of the specifications are generally larger EDI service providers who create software applications/translators derived from the specifications and sell that software to customers. Potentially the code delivered to those customers could become disabled if the licensor didn't pay their renewal fees affecting hundreds or even thousands of the software users, and causing significant disruption of the supply chain.
As Halpin puts it, "I think the standards organization is shooting itself in the foot with the fee. It's good that it is not retroactive, but the cost will become significant, and could force a move away, or simply not to use the updated specifications."
We think it's highly unlikely that the organization will, or even is able to deliver a kill switch within the applications that are derived from its use. But it may be that it has gone even farther and added a kill switch to its own business. Last modified on Wednesday, 03 July 2013