Hello,
As you will see below, I'm about as experienced with EDI as it is possible to be. Oh, about the X12, if you use EDI, it will Ansi X12 EDI :). The comm header for EDI is the ISA segments which are a wrapper for the EDI transactions sent (it's easier to figure out than it sounds).
Over my years of working with EDI, I have built a set of components and an EDI framework that can be used to to build a complete EDI system customized to your system, and includes an EDI admin program for your employees to use to monitor, modify.
I worked for NLM (National Logistics Management) in Detroit, MI for almost 10 years, where I designed, built and managed their entire EDI program which grew from nothing to more than 110 different customer/ transaction set combinations. NLM managed expedited freight for GM, Ford, Chrysler and many others using an auction system for freight companies in real time.
I've been working with EDI for almost 20 years now, and I've designed, built and managed a complete EDI system including translator, management system, and transmission protocols. While I can work with any EDI Transaction Set (X12, EDIFACT, or UN-EDIFACT), I have extensive experience with the following transaction sets ( 110, 204, 210, 211, 214, 275, 810, 820, 824, 834, 835, 837, 850, 855, 856, 858, 997, plus others ).
I attached a picture of my own copy of an EDI-X12 specs book. You will be able to see how worn and well-used it is.
Cheers,
Brad Gies