*DLM 4000.25-4, August 15, 2018*

*Change 5*

**AP8. APPENDIX 8**

**NON LOGISTICS ELECTRONIC DATA INTERCHANGE (EDI) SUPPORT**

AP8.1.  General.  The Defense Automatic Addressing System (DAAS) has been supporting non-Logistics EDI-based transactions for the past 30 years.  Electronic Data Interchange (EDI) is the exchange of routine business transactions from one computer system to another by standardized message formatting.  DAAS’ primary business has been to accurately route electronic logistics data and provide an interoperable gateway to exchange logistics data in disparate data formats between various federal activities and commercial trading partners.  However, the Electronic Business (EBUS) profile has grown over the years and spans much further than logistics processing.  DAAS currently provides data translation and routing support for several non-logistics based transaction categories supporting Department of Defense (DoD) business, including:  Transportation, Financial, and Procurement / Acquisition.  The DAAS’ EBUS profile processes financial, transportation, and procurement/acquisition transactions in a variety of formats including:  Accredited Standards Committee (ASC) X12 standards, eXtensible Markup Language (XML), User Defined Formats (UDF), Intermediate Document (IDOC), XML IDOC, Portable Document Format (PDF), and Comma Separated Values (CSV), depending on customer requirements.  The Defense Logistics Management Standards (DLMS) do not provide implementation conventions (ICs) for financial, transportation, and procurement/acquisition transactions since those domains are not governed by the DLMS Program Office. 

	AP8.1.1.  eBusiness System Description

		AP8.1.1.1.  EDI Gateway System Process.  EDI provides standard transaction formats for use in the automated, machine-to-machine, exchange of eBusiness transactions between the DoD Components/participating Agencies, and their commercial sector trading partners.  The Global Exchange (GEX), IBM Transformation Extender (ITX), and Ab Initio applications provide a high volume, high capacity environment to meet the needs of their customers.  DAAS currently processes over 10 million EDI transactions each day and supports a vast variety of capabilities based on customers’ requirements by providing routing and delivery of data, based on frequency and priority, performing translation of multiple formats (MILS, X12, XML, UDF, XML IDOC, PDF/CSV) if applicable, monitoring and alert notifications based on necessity, as well as data integrity.  Protocols such as IBM Message Queuing (MQ), Secure File Transfer Protocol (SFTP), Hyper Text Transfer Protocol Secure (HTTPS), and Applicability Statement 2 (AS2) are supported.  DAAS can provide encryption/decryption, compression/decompression, and special logic of data as needed.  A vast number of reporting capabilities are available including traffic, communication, transaction type, data-quality, error, as well as customized customer-driven.  The EDI team provides fast and reliable customer service 24/7.  

DAAS operates a centralized DoD eBusiness Communications Gateway capability that provides standard EDI and XML transaction routing, delivery, archiving, translation, and Value Added Network (VAN) delivery services through the following:  

		AP8.1.1.2.  DoD GEX Gateway.  In providing EDI telecommunication services, DAAS utilizes the standard GEX software suite developed to support the DoD Electronic Commerce Infrastructure.  The GEX application provides the capability to securely receive/send transactions via many different telecommunication protocols, sort/route the transactions, apply the appropriate translation/mapping utilities, provide decoding/validation of X12 syntax rules, log all activities, archive files, alert users of errors, and apply routing/distribution list processes. 

		AP8.1.1.3.  Transaction Translation.  The COTS IBM ITX, and Ab Initio mapping and transformation software tool sets currently provide the translation capability to convert incoming transaction formats into the appropriate outgoing transaction formats, via business mapping rules.  There are specific maps used to translate  financial, procurement/acquisition, and transportation transactions that are outside of the DLMS logistics guidelines.  Custom maps for data translation can be developed via approved DAAS methodologies.  Utilizing approved methodologies ensures that the maps will integrate with the DAAS  environment and are properly supported.  Customers with questions can contact the Electronic Business Program Manager.  Maps developed outside of core services are paid by customers,  maps are determined by the inbound format to the outbound format.  Some customers also have requirements for data encryption, validation, or special mapping.  

	AP8.1.2.  Financial / Transportation / Procurement Transactions.  All EDI transactions are archived in accordance with DoD Instruction 5015.02 for audit purposes.  Use of database and file lookups exist for data validation and routing purposes. 

TREASURY:

-  Data exchanges with the Treasury supporting DoD Financial Management

-  Single Line of Accounting (SLOA) data validation

PROCUREMENT:

-  Procurement Data Standard

-  Purchase Request Data Standard

-  Wide Area Workflow (WAWF)/invoicing, Receipt, Acceptance, and Property   Transfer (iRAPT) Support

-  Clause Logic Support

TRANSPORTATION:

-  Shipment information processing via EDI 210, 214, 315 transactions

	AP8.1.3.  Financial / Transportation / Procurement Regulations:  DoD regulation documents include: Defense Logistics Management Standards (DLMS) for logistics transactions:***(******http://www.dla.mil/HQ/InformationOperations/DLMS/******)***Defense Transportation Electronic Business (DTEB) for transportation transactions:***(******http://www.ustranscom.mil/cmd/associated/dteb/******)***

Defense Procurement Acquisition Policy (DPAP) for procurement transactions:***(******http://www.acq.osd.mil/dpap/pdi/eb/index.html******)***

Federal Acquisition Regulations (FAR), Defense Federal Acquisition Regulation Supplement (DFARS), and Procedures Guidance and Information (PGI) for acquisition transactions: ***(******https://www.acquisition.gov/far/******), (******https://www.acquisition.gov/?q=Supplemental_Regulations******), (******http://www.acq.osd.mil/dpap/dars/about_dfarspgi.html******)***

The DAAS EBUS profile and EDI processing programs supports these standards through the requirements received from customers.

AP8-1	APPENDIX 8