The Enterprise Ecosystem, enables the participation of large and small organizations (or individuals) in creating value at a scale beyond the possibilities of a single firm. In these ecosystems, participants co-create and interact in a way which would be impossible to manage in a traditional top down (industrial) manner. As a result of this massive collaboration effort and value creation, participants (including so-called customers) are bonded by a shared interest and purpose and they protect and contribute to the ecosystem as a “commons” that enables them.
-
Lower transaction cost to drive evolution in markets
-
Look for fragmented markets as an opportunity to seek for efficiencies
-
Pass on to the customer the savings introduced by efficiencies
-
Innovate pricing thanks to marketplace mechanism and data
-
Build mechanisms that support suppliers of all size
-
Invest in creating a mechanism that brings the best to the top (i.e. rate of failure)
-
Invest in mechanisms for empowerment, augmenting workers potential
| Section | Number |
|---|---|
General |
100 |
Governance |
200 |
Network & Clearing Participants |
300 |
Delivery and Settlement |
400 |
Obligations |
500 |
Suspension |
600 |
Reserved |
700 |
An enterprise service bus (ESB) is a software architecture construct that enables communication among various applications. Instead of having to make each of your applications communicate directly with each other in all their various formats, each application simply communicates with the ESB, which handles transforming and routing the messages to their appropriate destinations.
link:https://medium.com/freighttrust/the-dominant-design-of-information-processing-for-the-21st-century-9acdbc86ade7[Freight Trust Whitepaper
| Yellow Paper | Gwei | EDI Transaction | Cost in gwei |
|---|---|---|---|
GxdataZero |
4 |
Segments |
unit256 |
GxdataNonZero |
6,800 |
Interchange |
1,136 |
GxminTransaction |
21,000 |
File Data |
77,248 |
|
Important
|
$EDI Token Contract Address |
EDI |
Description |
Version |
204 |
Motor Carrier Shipment Information |
Version 4010 |
210 |
Freight Details and Invoice |
Version 4010 |
211 |
Motor Carrier Bill of Lading |
Version 4010 |
214 |
Shipment Status Message |
Version 4010 |
997 |
Functional Acknowledgement |
N/A |
Diffreent standards define the commonly used business transactions in a formal, structured manner called transaction sets. X12 standards differ from data exchange protocols, in that a protocol allows data to flow from one computer to another without regard to the structure or meaning of the exchange.
EDI consists of text data, and the text is restricted to using specific
ASCII characters. A basic character set is defined for all exchanges,
and this set may be extended with additional characters by mutual
agreement of the trading partners. Using any additional characters is discouraged
if not prohibited. For certain areas, such as Japan, China, and Korea, a special pipe is used. Please contact us for more information at [email protected]
Uppercase letters A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Numeric digits 0 1 2 3 4 5 6 7 8 9 Special characters ! " & ' ( ) * + , - . / : ; ? = The space character Control characters: BEL HT LF VT FF CR FS GS RS US NL ASCII hex values: 07 09 0A 0B 0C 0D 1C 1D 1E 1F
Lowercase letters a b c d e f g h i j k l m n o p q r s t u v w x y z
Other special chars % ~ @ [ ] _ { } \ | < >
National characters # $
Control characters: SOH STX ETX EOT ENQ ACK DC1 DC2 DC3 DC4 NAK SYN ETB
ASCII hex values: 01 02 03 04 05 06 11 12 13 14 15 16 17
Symbols representing delimiters
| Symbol | Type of delimiter |
|---|---|
<tr> |
Segment terminator |
<gs> |
Data element separator |
<us> |
Component element separator |
Elements and higher structures of the EDI transaction sets are
distinguished by delimiters
EDI standards do not impose requirements on delimiter choices other than to prohibit the use of a delimiter within a data element. Recommended delimiters are shown in the following table, along with values suggested in the standards and values in common use in industry:
| Delimiter | TradeDoc | Standards suggest | Industry practice |
|---|---|---|---|
<tr> |
Unix newline
0A hex, 10 dec
|
any control char
1C hex preferred
|
return/linefeed
0D0A hex, CR/LF
|
<gs> |
Unix backtick (`)
60 hex, 96 dec
|
special or control
1D hex preferred
|
asterisk (*) tilde (~) |
<us> |
Unix carat (^)
5E hex, 94 dec
|
special or control
1F hex preferred
|
colon (:) |
EDI data is exchanged in different ways, but always comes down to encoding.
Specifically the backtick and carat symbols are not included in the EDI character set, and therefore are not present in data elements. Please see our section on Codecs for more information on the subject.
The data element is the smallest named unit of information in the standard. Data elements are identified as either simple or component. A data element which occurs within a composite data structure is identified as a component data element.
A data element which is outside
the boundaries of a composite structure is a simple data element.
The distinction between simple and component elements is based on the
placement of the element in the set and not on the attributes of the
element.
Each data element is assigned a unique reference identifier of from one to four digits. Data elements have three attributes: the type, the length minimum, and the length maximum. Data element types are as follows:
| Type | Code | Data Element Type Description |
|---|---|---|
Numeric |
Nn |
Numeric value with a predefined implied decimal point |
Decimal |
R |
Numeric with an explicit decimal place |
Identifier |
ID |
A unique coded value from a predetermined list |
String |
AN |
A sequence of basic or extended characters |
Date |
DT |
A standard date in the format YYMMDD |
Time |
TM |
A time in the format HHMMSSd…d |
Binary |
B |
Numeric sequence of binary octets |
Fixed String |
FS |
Space-padded sequence of basic or extended characters |
The composite data structure is an intermediate unit of information in a
segment. The definition of a composite data structure consists of two or
more component data elements. In the actual data transmission the
composite may consist of one or more component data elements. Adjacent
component elements in a composite data structure are delimited by the
component element separator <us>. Composite data
structures are delimited from other adjacent elements in a segment by
the data element separator <gs>.
Each composite data structure has a unique four-character reference identifier. The identifiers for composite data structures which appear in control segments start with an S; a C is the first letter of composite identifiers which are used in data segments.
A detail table defines the component data elements in a composite data
structure. Each component referenced has a requirement and an ordinal
sequence in the structure. In the actual data transmission omitted
elements are indicated by including their delimiters to preserve this
sequence, except for elements which are omitted at the end of the
component data structure.
-
component
-
component data structure
-
composite data structure
-
delimiter
-
segments
The data segment is an intermediate unit of related information in a transaction set. Simple data elements and composite data structures are the data parts of the segment. Each segment in a transmission starts with the segment identifier, followed by at least one data element or component structure, and ending with a segment terminator <tr>.
Each data segment has a unique two- or three-character identifier which also serves as a label for the segment in the data transmission. Segment labels are separated from the following data element by an element separator <gs>. The label is considered to be position zero of the segment, so that the first data element following the label is in position one.
A detail table defines the sequence of simple data elements and composite data structures in a segment. Each unit referenced has a requirement and an ordinal sequence in the segment.
|
Warning
|
=== In the actual data transmission omitted elements are indicated by including their delimiters to preserve this sequence, except for elements which are omitted at the end of the segment. === |
The transaction set is a complete unit of information exchanged between trading partners, representing a business document. Each transaction starts with a header segment (ST) and ends with a trailer segment (SE). At least one data segment is required between the header segment and the trailer. Each segment in the transaction set ends with the segment terminator <tr>.
The transaction set identifier uniquely identifies each transaction set. This identifier is the first data element of the transaction set header segment. The transaction set header and trailer segments contain a control number which must be identical for any given transaction. Transaction set control numbers should not repeat in the history of exchanges of the transaction set between two trading partners. The transaction set trailer segment also contains a count of the number of segments in the transaction including the ST and SE segments.
The sequence of data segments in a transaction set definition is presented in detail tables for the set. Up to three tables may be used to represent transaction header information, repeating details, and a summary area. Each segment in a set has a requirement designator, a position in the set definition, and a maximum occurrence. An example set detail table is shown below:
Single data segments within a transaction set may repeat up to a specified maximum number of occurrences, as shown in the MaxUse column. The notation >1 is used to show that the number of repeats for a segment is unlimited. Groups of two or more related data segments may be repeated as a loop.
|
Important
|
===
Loops may be either unbounded, or bounded by
loop start (LS) and loop end (LE) segments.
===
|
The start of an unbounded loop is marked by the occurrence of the first
segment of the loop. The beginning segment of an unbounded loop shall
not appear anywhere else in a loop. The requirement for a loop is
implicitly the requirement of the loop’s first segment.
If the requirement designator for the first segment of a loop is mandatory, then the loop must appear at least once in the transaction set`. A loop may be repeated up to a specified maximum number of times. The notation >1 designates an unlimited repeat.
A level entry indicates the nesting of loops, and the start of a loop
structure is indicated by a loop label on the first segment of the loop.
When unbounded loops are nested within loops, the inner loop shall not
start at the same position as any outer loop. The inner loop shall not
start with the same segment identifier as the start of any outer loop,
nor may the inner loop contain a segment that is also the beginning
segment of any outer loop in the same structure.
The characteristics of unbounded loops also apply to bounded loops, except that bounded loops have no restriction on which segment begins the loop. For bounded loops, a unique loop identifier defined in the standard is used in the LS and LE segments to convey segment position or loop hierarchy, or both, within the transaction set.
A transmission consists of a sequence of interchanges in a stream which are all addressed to a specific trading partner (as when receiving) or all addressed from a specific partner (as when sending).
The Sender and Receiver Identifiers in the ISA header of an interchange address the interchange envelope between partners. Therefore a transmission is analogous to a mail delivery to or a mail pickup from a mailbox.
Content of ASC X12 standards is proprietary, and FreightTrust and Clearing Corporation makes no claim over its copyright, and only provides this for educational purposes only.
This work is copyrighted under the Creative Commons NC-ND 2.5 License
You are free to: Share & copy and redistribute the material in any medium or format, Under the following terms*:
Attribution: You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. * Non-Commercial: You may not use the material for commercial purposes. * No-Derivatives: If you remix, transform, or build upon the material, you may not distribute the modified material. * No additional restrictions: You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits. If you are seeking a Commerical license you may contact us at: [email protected]