What DAAS Offers

The DAAS primary business is the accurate routing of electronic logistics requisitions between various federal activities. The DAAS eB hub currently employ's the Global Exchange (GEX) software and the Mercator translator.

DAAS has been operating in the eB domain for over 30 years, concentrating primarily on military standard transactions. Since 1993, DLA DAAS has been operating an eB hub of primarily X12-based EDI transactions. In terms of transaction volume (over 10 million every week), the DAAS eB hub is the largest in DoD, providing a single communications pathway to many Value-Added Networks (VANS), and the private sector trading partners served by those VANS. The DAAS Hub handles all of the details involved in routing and communicating with VANS, freeing DLA buying community to concentrate on electronic business applications. Each VAN offers different communications options and requires different access procedures, which creates extra work for electronic commerce projects that need to trade with many partners. The VANS primarily send/receive X12 data files with DLA DAAS, via a secure FTP protocol.

The DAAS EB hubs process over two million eB transactions every week. Electronic Business Translation/Mapping Services DAAS offers standard mapping based upon the DLMS standards in X12 or XML (MILS to X12, X12 to MILS, MILS to XML, XML to MILS, X12 to XML, XML to X12). The Implementation Conventions (IC) are available at: http://www.dla.mil/j-6/dlmso/. DAAS also offers custom mapping for other types of formats. Our fee for doing mapping is based upon an hourly rate of per hour. DAAS estimates the number of hours needed to do the work and charges accordingly. Normally this is a one-time fee, unless major changes or updates to the maps are necessary. Map costs run somewhere between $5,000 and $10,000.   

VAN/HUB/GATEWAY Services DAAS provides VAN services to federal eB projects for the routing of transactions between DOD customers and some of their Prime Vendor Partners. This means DAAS serves as the central distribution center for the routing of transactions to external sites, Prime Vendors, and internal VAN mailboxes for pickup by Prime Vendors.

DAAS/EDI routes transactions to external commercial VANS, such as AT&T/Easylink, who then distribute the transactions to their customers/vendors. DAAS' gateway accepts communication protocols, SFTP, HTTPS, and MQ from both government and contractor customers.

EDI Defense Logistics Supply Centers

DLA Energy POC:  Craig Lockard, 703-767-8663, email:  Craig.Lockard@desc.dla.mil

DLA Troop Support General & Industrial  POC:  Rick Fitzgerald, 215-737-2130, email: Richard.Fitzgerald@dla.mil

DLA Troop Support POC's:   Robert Starrs, 215.737.7240, email:  robert.starrs@dla.mil; Rick Fitzgerald, 215-737-2130, email:  Richard.Fitzgerald@dla.mil

DLA Land and Maritime POC:  Shawn Schartiger, 614-692-1057, email:  ecedi@dscc.dla.mil

DLA Aviation POC's:   Floyd Moore, 804-279-4433, email:  Floyd.Moore@dla.mil; Dewey Herst, 804-279-3199, email:  Dewey.Herst@dla.mil

We recommend sending email to the eB group at : edi@dla.mil

eB Help Desk Number (24x7x365): 937-656-3247 or DSN 986-3247

eB Help Desk Number (During Normal Working Hours): 209-839-4944 or DSN 462-4944

If it's an emergency and after normal working hours, the Customer Service Help Desk will page someone from the eB support group. To speed up this process, provide as much information as you can. For example, state who you are, where you are calling from, a telephone number to call back to, what the problem is, the purpose of the immediate request, and when the problem started. The Customer Service Help Desk will create a Problem Ticket (PR) and assign it to someone from the eB support group who will immediately handle your problem.

Exchanging eB data with Transaction Services over the internet

The DAAS GEX EDI supports SFTP, HTTPS, SMTP/MIME, and MQ to transport X12 transmission files over the internet and the NIPRNET. DAAS Data Delivery via a secured protocol and implementation of Firewalls throughout DoD, will require the customers assistance.

If a customer requires an SFTP connection using the SFTP/SSH protocol, then this protocol is similar to FTP, but it uses encryption to secure the connection. The technical details are discussed: in this document

Additional information about this protocol and implementations can be found at: OpenSSH home page

This page describes the OpenSSH project, which provides an Open Source implementation of the protocol. For commercial vendors that support the protocol there is a section on that page labeled 'Alternatives.'

DLA DAAS requires that Public Key Authentication (PKA) be performed when DLA DAAS initiates the connection to the customers SSH/SFTP server. Password authentication is possible when your connection is made with a DLA DAAS server, but is not preferred.

You are referred to this discussion of Public Key Authentication for more information: Public Key Authentication

DAAS has several SFTP IP addresses. While it is not required, programming one IP address as a primary and the other IP address as a backup should be considered to prevent loss of connectivity. We make every effort to ensure that we keep one of the two machines up at all times, but if you program a single address, you'll be unable to send in files while that machine is down for maintenance.

Network Addresses for FTP

DAAS has several IP addresses that you may use for FTP destinations. While it is not required, you should consider programming one IP address as a primary and the other IP address as a backup. We make every effort to ensure that we keep one of the two machines up at all times. If you program a single address, you'll be unable to send in files while that machine is down for maintenance.

We prefer that you send your data to the Dayton, OH hub unless we have instructed you to do otherwise.

SMTP Mail Destination

DAAS has flexible support for transmission and receipt of eB data via SMTP.  The data can be in the body of the message or as a MIME attachment.

If you are interested in exchanging eB data via SMTP, please request sample transmissions by email to edi@dla.mil.

AS/1 is not currently supported.

HTTPS Transfers

DAAS supports a form-based interface for sending and receiving files via HTTPS.  The options here varied and are currently the subject of ongoing development and testing.

We’ve found that it is fairly easy to interface using HTTPS with only a trivial CGI program.

An interactive file-based dialog is available via HTTPS for uploading to DAAS. 

DAAS currently requires specific firewall rules to be applied locally to allow inbound HTTPS transmissions to our systems.  Please contact edi@dla.mil for more information about this mode of communication.

AS/2 is not currently supported, but DAAS is looking into this increasingly popular mode of communication.  If you have a requirement for AS/2, please contact us at edi@dla.mil.

Pushing/Pulling with FTP

We support your pulling data from our servers or pushing data to our servers.  By push we mean that for files coming to DAAS, the sending site will run its FTP client, log on with a user name and password provided by DAAS and initiate placing data.  By pull we mean that the receiving site will run its FTP client, log on with a user name and password and initiate a retrieval.

We also support pulling data from your server or pushing data to your server.  IfDAASs is initiating the transmission, then DAAS will need to be provided with a user ID and password on the host at  your site.

If you wish to pull your files from DAAS, you should do so with an FTP GET or MGET command. After you pull the files, it is your responsibility to make sure that you have received them completely and then delete them. DAAS cannot delete EDI files for users who pull.

Make sure that you only pull files whose names begin with the letter "D" followed by your site code. That way, you will not pull down files that may reside in your directory for administrative or other purposes. In the following example, suppose that your site code is MGSC:

FTP> mget DMGSC*.*
After checking that your received everything...
FTP> mdel DMGSC*.*
FTP> quit

Our DEBX system, where all new setups are performed, guarantees that no new files can come into the directory after you login, thus ensuring that the above procedure does not delete any files that have arrived after the mget and before the mdel command

File Naming Conventions

DAAS prefers that you uniquely name every file that is sent to us. Likewise, DAAS' file transfer software will uniquely name files it sends to your site.

Files that you send to us should be named as follows:

I.jjj where is the 4-letter site code that we will assign to you. nnn is an arbitrary sequence number and jjj is the julian date.
Example: IQBAX001.109

A technique most of our customers use is to transfer in their file with a "Z" as the first letter. After the transfer has successfully completed, the file is renamed, changing the first letter to "I". This way, we don't attempt to process a partial file that is doomed to fail.


SFTP> put ourfile ZQWER348.255
SFTP> rename ZQWER348.255 IQWER348.255

You can make the sequence numbers longer or shorter as you wish, or use alphanumeric sequence numbers. The primary requirement is that the file names begin with the letter "I". File names are case-sensitive on our GEX system. We can support file names that begin with a lower case 'i' if required.

We prefer this naming convention because it identifies the file as yours, and contains elements to ensure a unique name. The better the name, the easier it is to find a file when a problem occurs.

Other file naming conventions can be supported for special interfacing requirements, such as to MVS or AS/400 systems.

The files we send to you will be named as follows:

Dnnn.jjj where is your user name on the DAAS computer, nnn is a sequence number which we generate, and jjj is the julian date. Generally, the DAAS FTP client software generates uppercase file names on UNIX systems.

Example: DQXYZ002.109

Other file naming conventions for transmission can be supported for special interfacing requirements, such as data set names.  ‘Site’ commands custom to your application can also be accommodated

How long does it take DAAS to process an interchange?

The median time required to move an interchange through the system and deliver to a VAN is 15 minutes. The median time required to deliver an interchange to a mailbox on our own VAN is 5 minutes.

We are connected to many VANs via dedicated circuits. Median delivery times to these VANs are about 10 minutes.

For VANs we reach via dial-up BISYNC, the normal transfer time for an interchange is closer to 20 minutes. DAASs is currently converting all BISYNC customers to FTP protocol for better and faster communications.

Are public requests for quote (RFQ) available from DAAS?

Yes. RFQ's from the Navy Electronic Commerc Office (NECO) are available on request.

What forms of communication does DAAS support?

  • SFTP across a dedicated circuit.
  • HTTPS (Hypertext Transfer Protocol Secure) provides authentication of the web site and server providing bidirectional encryption communications between client and server.
  • SMTP (MIME) across the NIPRNET/INTERNET and dedicated circuits.

What eB standards and versions are supported by DAAS?

The eB standards that DAAS can process include X12, XML, UDF's and IDOC. Currently, most DAAS eB customers use X12. All X12 versions from 2002 are supported.

What X12 transaction sets will you process?

All ASC X12 approved transaction sets.  Transactions must conform to X12 syntax and contain all required elements

Does DAAS require any particular separators or terminators?

You can use anything that is supported by the standards, and is acceptable to your trading partner(s) and the VANs. DAAS imposes no restrictions.

What kind of computer hardware and software are you running?

The DAAS eB hubs run on HP N-Class platforms connected to a high speed Storage Area Network (SAN). The Defense Global Exchange (GEX) Hub software runs on a UNIX operating system and utilizes Mercator as the translation/mapping engine.

We're a vendor and want to do business with DoD/DLA?  How do we get started?

DAAS is a data communications center for the buying centers of DoD/DLA. In essence, we perform like the post office median in routing transactions to the proper destination(s). Potential new customers will need to contact the various DoD/DLA procurement centers that purchase goods and services to establish a business relationship at the supply centers as an eB trading partner. From our website see the url link for EDI Defense Logistics Supply Centers.

How does our VAN establish a relationship with DAAS and Dod/DLA?

Contact the eB Program Manager at edi@dla.mil   Be prepared to provide information regarding the communication regimes that you support, and instructions on how to process connections.

If you expect to exchange files with DAAS using FTP, be prepared to provide a username, password and IP address that we can program into our file transfer software.

Also, please read our pages on Host Systems and file naming conventions.

Does DAAS provide services to DLA only?

No. DAAS' eB customers include the Defense Logistics Agency, all of the Military Services/Agencies, the Administrative Office of the US Courts, and others. If you're interested in obtaining services from DAAS for your federal or state government activity, contact edi@dla.mil for more information.

Does DAAS do translation?

DAAS has translation & mapping software for most eB standards, including all versions of X12.

DAAS provides translation services for those customers who desire it. If the requirement for significant resources must be applied to a mapping project, then it is based on standard hourly rates.

Does DAAS support encryption?

Yes. DAAS will encrypt or decrypt data for VANs and/or DoD/DLAl clients. We currently support PGP (Pretty Good Privacy)--the most widely used public key encryption scheme currently available--and the proprietary Compress encryption software. DAASs, also, supports HTTPS for delivery of transaction

External Link Disclaimer

The appearance of external hyperlinks to commercial value-added networks (VANs) does not constitute endorsement by the United States Department of Defense of the linked web sites, or the information, products or services contained therein. For other than authorized activities, the United States Department of Defense does not exercise any editorial control over the information you may find at these locations. Such links provided are consistent with the stated purpose of this DoD Web site.

Please be advised:  DAAS does not endorse any one of the VANS listed below or claim content responsibility.

Glenn House
75 West Street
Walpole, MA 02081
(508) 850-7520
(508) 850-7521 (fax)
email: glenn_house@2is-inc.com

2Is home page
Government Program Support
25054 Lorain Rd.
North Olmstead, OH 44070
(800) 223-5424
(440) 779-5424
(440) 779-9462 (fax)
email: sales@acsmail.com
Sam Saffari
23535 Palomino Dr.
Diamond Bar, CA 91765
(949) 464-9999 
e-mail: sams@alicorp.com

ALI home page


Global Sales
29313 Clemens Road #2-A
Westlake, OH 44145
(866) 226-4488
(440) 377-5668
(440) 808-1844 (fax)
e-mail: headquarters@bidlink.net

BidLink.NET home page


East Coast Office:
12 SE 7th Street Suite 610
Ft. Lauderdale, FL 33301
e-mail: support@section-seven.com


West Coast Office:
5267 Warner Ave #127
Huntington Beach, CA 92647
e-mail: support@section-seven.com
TEL: 954-707-3733

Section Seven home page


950 East Paces Ferry Place
Suite 925
Atlanta, GA 30326
(404) 261-7800
(404) 261-9697 (fax)

Connolly Consulting home page


Ray Huntley
33 Knightsbridge Rd.
Piscataway, NJ  08854
(800) 828-7115 x3639
(732) 352-7680 (fax)
(800) 872-6711 (help desk)
e-mail: rhuntley@easylink.com

AT&T Easylink home page


Inside Sales
100 Edison Park Drive
Gaithersburg, MD  20878
(800) 334-5669 (sales)
(800) 334-2255 x6816 (EDI TP set ups-help desk)

GXS home page


201 Commack Road
Commack, New York 11725
(888) 334-5465
(516) 493-0613 (fax)


Kenneth Krempin
7000 Columbia Gateway Dr.
Columbia, MD 21046
(410) 964-7738
(410) 964-7589 (fax)
e-mail: kenneth.krempin@honeywell.com


3495 Kent Ave, Suite A100
West Lafayette, IN 47906
(765) 464-1700
e-mail: Sales@imaginestics.com

Imaginestics home page


Government Sales Department
1055 Lenox Park Blvd.
Atlanta, GA 30319-5309
(800) 367-4272
(404) 841-4364 (fax)

Inovis home page


Chuck Fortier
3325 Plus Park Blvd.
Suite 101
Nashville, TN 37217
(888) 246-1777
(615) 360-7716 (fax)
email:  govediin@intervan.com


450 Lake Cook Road
Deerfield IL 60015-4619
(847) 945-1000
(847) 945-4619(fax)

Kleinschmidt homepage


1750 Tysons Blvd Suite 1500
McLean, VA 22102
Toll Free: 855.KFG.isIT (855.534.4748)
(703) 594-8204(fax)


DBA Lamlinks Corp
560 No. Larchmont Blvd
Los Angeles, CA 90004
(323) 469-4560
(323) 938-4112 (fax)
e-mail: sales@lamlinks.com


3157 Royal Drive Suite 200
Alpharetta, GA 30022
Within US: (866) 830-3600 Option 4
Outside US: (770) 850-6963
(770) 829-2361 (fax)



Chet Roberts
7200 Poe Avenue Suite 400
Dayton, OH 45414
(937) 415-29047
(937) 913-5660
e-mail: CRoberts@lionprotects.com
Visit LION: LION Protects Hompage
Interact with LION Lion Connects Hompage
Follow LION at FaceBook


P.O. Box 600
Indian Rocks Beach, FL 33785
(800) 745-6736
(813)-298-0356 (fax)
e-mail: Sales@ld.com

LOREN home page


MIL-PAC Network Services
1672 Main Street
Suite 254
Ramona, CA 92065
(760) 788-3030
(760) 788-3779
e-mail: info@milpac.com

MilPac home page


8200 Republic Airport Hangar 43
Farmingdale, NY 11735
(631) 847-3504
e-mail: info@nsn-now.com

NSN-Now home page


Paul Lockart
E-mail: plockart@nubridges.com
Headquarters - Atlanta
1000 Abernathy Road
Building 400 / Suite 250
Atlanta, GA 30328
(800) 251-4930 (toll free)
(770) 730-3600 (main)
(866) 830-3600 (support)
e-mail: info@nubridges.com (info)
e-mail: support@nubridges.com (support)

nuBridges home page


7059 Production Court
Florence, KY 41042
(859) 449-7068
(815) 8301-3900 (fax)
e-mail: james.lusk@odysseyrfid.com (sales)


4608 Cedar Avenue
Suite #106
Wilmington, NC  28403-4429
(800) 746-9554
(800) 746-8307 (fax)
e-mail: ediservices@prime-vendor.com (info)
e-mail: burney@prime-vendor.com (technical)

Prime Vendor, Inc. home page


2358 Lakeview Drive
Suite A
Beavercreek, OH 45431-2569
(937) 431-8000
(937) 431-8090 (fax)
e-mail: info@rainbowdata.com (info)
e-mail: support@rainbowdata.com (support)

Rainbow Data Systems Inc. Home Page


Audrey Helou
2925 Bond Straight
Rochester Hills, MI 48309
(800)-SIMPLIX (746-7549)
(248) 740-8150
(248) 740-8180 (fax)
e-mail: sales@edi.com
Simplix Home Page: http://www.edi.com or http://www.simplix.com


EDI Sales Department
2241 Stanwood Dr.
Santa Barbara, CA 93103
(800) 346-6703
(805) 882-2599 (fax)

Softshare home page


Vicki Amirault
4600 Lakehurst Court
Dublin, OH 43017
(800) 876-9627
(614) 793-7322
(614) 793-7092 (fax)
e-mail: vickie_amirault@stercomm.com

Sterling Commerce home page


Bob Anderson
PO Box 188063
1725 Geranium St.
Carlsbad, CA 92009
(858) 431-8133
(858) 431-2644 (fax)
e-mail: tec@rfqnet.com


Richard Snyder
385 Bol Marin Keys Blvd.
Novato, CA 94949
(800) 346-6459
(415) 883-3754 (fax)


Steven Hobbs
1745 Phoenix Rd., Suite 150
Atlanta, GA 30349
(800) 432-6428
(404) 996-8109
(404) 996-8305 (fax)

TranSettlements home page


ADVANTIS   (Inter-Connect for LOREN DATA)
Mike Neadeau
VP of Sales
1199 NASA Prkwy
Houston, Tx 77058
(281) 480-1121 x113
e-mail: mneadeau@dicentral.com
ECOM   (Inter-Connect for STERLING COMMERCE)
Krishna Mohan
12330 Perry Highway, Suite 200
Wexford, PA 15090
(240) 498-0040
e-mail: k.mohan@ecomtoday.com
ICC   (Inter-Connect for LOREN DATA)
SPRINT   (Inter-Connect for LOREN DATA)
Natalie Domhoff, Sales Manager
12330 Perry Highway, Suite 200
Wexford, PA 15090
(724) 940-5520 x309
(412) 586-2240 (fax)
e-mail: nrdomhoff@truecommerce.com

True Commerce home page
Electronic Data Interchange (EDI) is the exchange of routine business transactions in a computer processible format, covering such traditional applications as inquiries, planning, purchasing, acknowledgements, pricing, order status, scheduling, test results, shipping and receiving, invoices, payments and financial reporting.  Additional standards cover interchange of data relating to security, administrative data, trading partner information, specifications, contracts, production data, and distribution and sales activities. 

Through the use of the Accredited Standards Committee (ASC) X12, electronic data interchange is based on interdependency.  This way, internally or externally developed software and public-access communications vendors, all sizes of firms and institutions using intelligent computational devices may benefit from the use of the standard.  Thereby, all institutions reap the efficiencies of a common interchange language, rather than experience the difficulties of an increase of methods and procedures that could occur if each institution were to impose its own format on every institution with which it does business.