*DLM 4000.25-4, April 09, 2022*

*Change 7*

**AP1. APPENDIX 1**

**EDS Defense Automatic Addressing System (DAAS)’ PROFILES**

AP1.1.  Department of Defense (DoD) DATA SERVICES (DData) Profile

	AP1.1.1.  General.  DData is the overarching profile that provides access to logistics data and various reports to support the Department of Defense, Federal Activities, Civilian Agencies, Commercial Suppliers, Foreign Military Sales (FMS) and Security Assistance Countries.  DData captures and reports on logistics data processed through DAAS and maintains DoD level system repositories in support of the customer base of over 228,000 activities located around the world.  The customers from these activities are able to query repositories, extract information, download reports, and are able to access an integrated DoD view of assorted data.  All of the data repositories are managed by DoD direction and are maintained from a DoD perspective.

	AP1.1.2.  System Descriptions

		AP1.1.2.1.  Billing and Materiel Obligation Support System (BMOSS) Process.  The BMOSS manages the Military Interfund Billing/Materiel Obligation Validation (MILSMOV) repository and provides query capability and recovery/ retransmission of bills and backorder validations.  BMOSS provides the capability to maintain and distribute fund codes used in the DoD Interfund billing process through the following processes:

			AP1.1.2.1.1.  Military Standard Billing System (MILSBILLS).  The Defense Automatic Addressing System (DAAS) receives, edits, routes and transmits MILSBILLS interfund transactions for the DoD.  Each requisition processed into a shipping action results in the generation of a billing transaction.  These interfund bills are archived by the DAAS and are available for retrieval and retransmission.  The DoD bills data is stored In Accordance With (IAW) DoD Instruction (DoDI) 5015.02, while the DoD Foreign Military Sales (FMS) bills are stored IAW DoDI 5015.02.  The DoD Components are required to submit automated inquiries to the DAAS to retrieve bills for their use or may direct that the bills be sent to another activity, which is not identified in the MILSBILLS document.  DAAS maintains the MILSMOV inquiry system and provides the capability to interrogate the repository for recovery and retransmission of bills.  See Appendix 3.2.4.

			AP1.1.2.1.2.  MILSBILLS Fund Code.  The MILSBILLS fund code is a two-character code used to identify the appropriate accounting data to be charged.  DAAS maintains the fund codes and serves as the DoD focal point for receipt of all file revisions.  The codes are updated monthly and posted to the DAAS web site for activities to download.  The DAAS Micro Automated Routing System (DMARS) Automated Information System (AIS) uses the fund code repository for performing DoD Component requested edits against specific logistics transactions.

MILSBILLS Fund Codes can be accessed athttp://www.dla.mil/HQ/InformationOperations/DLMS/

			AP1.1.2.1.3.  MILSBILLS Inquiry (MILSINQ).  This query system provides both local and remote users the capability to interrogate/display Interfund Bills (MILSBILLS) and Material Obligation Validation (MOV) batches, and generate/retransmit requests on-line.

			AP1.1.2.1.4.  Military Interfund Billing/Material Obligation Validation (MILSMOV).  The DoD validates all backordered requisitions each quarter.  These validations are scheduled as required by the business rules established in Defense Logistics Management Standards (DLMS).  The validation process requires the recipient of the MOV to respond within 45 calendar days or have their backorder cancelled.  Since many backorders have been funded with prior year’s money, a cancellation of the requirement can be catastrophic and cause a considerable impact on the DoD Components/Participating Agencies.  The DAAS processes the MOV, ensuring the batch contains all the individual transactions as determined by the transaction count in the header control document.  DAAS receives approximately 4 - 7 million MOV transactions each quarter, maintaining the MILSMOV inquiry system and providing the capability to interrogate the repository for recovery and retransmission of MOV batches.  The MOV system retains all MOV batches and batch acknowledgment receipt transactions sent during the current quarter.  Thereafter, transactions should be maintained IAW DoDI 5015.02, DoD Records Management Program.

		AP1.1.2.2.  DAAS Master Routing System.  Includes the following directories:

			AP1.1.2.2.1.  The DAAS Allied Communications Procedure (DAASACP).  This environment encompasses both data pattern and narrative message routing information and holds the communications routing criteria for both data pattern and narrative message routing for the DAAS customer base.

			AP1.1.2.2.2.  The DAAS Inquiry System (DAASINQ) and Enhanced DAAS Inquiry system (eDAASINQ).  DAASINQ provides information on Department of Defense Activity Address Directory (DoDAAD), National Item Identification Number (NIIN), Military Assistance Program Address Directory (MAPAD), and Routing Identifier Code (RIC) data elements to DAAS customers. eDAASINQ is a Common Access Card (CAC)-enabled version of DAASINQ that offers an enhanced capabilities over the DAASINQ application including options to query the Communication Routing Indicator (COMMRI) and Distribution Code. eDAASINQ also allows you to download the DoDAAD and MAPAD files. It provides additional queries and downloads by Service or "All" in "TA1" delimited format. eDAASINQ is Public Key Infrastructure (PKI)-enabled and access to the application may be requested by submitting a System Access Request (SAR) at~~~~https://www.transactionservices.dla.mil/sar/sar_menu.asp.

			AP1.1.2.2.3.  Department of Defense Activity Address Directory (DoDAAD).  The DoDAAD is one of the primary files used in the DMARS validation and verification processes.  DMARS must verify that the DoD Activity Address Code (DoDAAC), contained in the DMARS processed transactions, is a valid requisitioning activity, based upon being resident in the DoDAAD.  The DoDAAD has four different Type Address Codes (TACs) which provide an address for:  (1) mail and small parcel shipments (TAC 1); (2) Outside Continental United States (OCONUS) and surface shipments (TAC 2); (3) the billing address for the DoD interfund bills (TAC 3); and (4) small parcel shipments (TAC 4).  DAAS is the DoD Central Consolidation Point (CCP) for maintenance of this file and disseminates updates (adds, changes, and deletions) to the DoD Components/Participating Agencies.  See Appendix 3.2.1. for more information.

			AP1.1.2.2.4.  RIC and Distribution Code.  The RIC serves multiple purposes in providing source-of-supply, intersystem routing, intra-system routing, and consigner (shipper) information.  DAAS is the DoD-designated Central Service Point (CSP) for maintenance of the RIC, maintains the RIC file, and is the focal point for the receipt and dissemination of all file revisions.  Distribution codes are assigned by the DoD Components, under the DLMS~~)~~, to identify activities to be furnished 100 percent supply and shipment status on all priorities in addition to other given status.  DAAS is, also, the central DoD repository for the distribution code file and the focal point for all file revisions.  See Appendix 3.2.3. for more information.

			AP1.1.2.2.5.  Military Assistance Program Address Directory (MAPAD).  DAAS is the DoD CSP for maintenance of the MAPAD and sends updates (adds, changes, and deletes) to the DoD Components/Participating Agencies to provide address information for their shipping of materiel and sending of documentation.  There are nine TACs in the directory, containing addresses for various processes.  As an example, the TAC 1 address is used for shipping unclassified materiel.  The TAC 4 address is used to send supply status to the FMS country or their designated representative.  They in-turn, submit changes to DAAS for incorporation into the directory.  See Appendix 3.2.2, for more information.

			AP1.1.2.2.6.  Master Source of Supply (SoS) System.  The DAAS NIIN/SoS File is maintained to ensure DLMS system transactions are routed to the correct SoS as required by the DoD Component/ Participating Agency’s business rules.  Daily updates are obtained from the DLA Logistics Information Service to ensure the repository is current.

			AP1.1.2.2.7.  Plain Language Address Directory (PLAD).  The DAAS PLAD capability provides a linkage between a DoDAAC and its associated Plain Language Address (PLA).  The PLA is used in the ‘From:’ and ‘To:’ line of a narrative message.  Users may address narrative messages to the DAAS PLA conversion process, and it will look up the DoDAAC(s) placed in the ‘From:’ and ‘To:’ lines of the input message, replace the DoDAAC(s) with their appropriate PLAs, and, finally, send the messages to the appropriate destination.  PLA information is integrated into the DAASINQ capability, and is displayed as part of the DoDAAC query response.

			AP1.1.2.2.8.  Standard Point Location Code (SPLC).  The Military Surface Deployment and Distribution Command (SDDC)-Global Freight Management (GFM) is required to maintain accurate and current SPLC values in their DoDAAC-to-SPLC cross-reference file.  The National Motor Freight Traffic Association maintains and publishes all valid SPLC assignments and updates newly assigned nine-digit values.  DAAS administers the SPLC maintenance in the DoDAAF in support of the DoD transportation payment program.  Maintenance of the SPLC values in the DoDAAF is done in accordance with the Logistics Management Institute Report, Generating Nine-Digit Standard Point Location Codes for the Defense Transportation Payment Program, June 1995, with changes submitted daily.  DAAS ensures the accuracy and completeness of the SPLC data and generates changes when appropriate.  SPLC is a critical element in support of the DoD transportation payment program.

		AP1.1.2.3.  Logistics Data Gateway (LDG).  LDG is a comprehensive architecture that provides a set of business intelligence tools allowing a customer fast and easy online access to the vast amount of data processed and maintained in the DAAS data bases.  This DoD-level data warehouse provides easy web access to current and historical data in an integrated form that flows through the DAAS.  Data is available for operational research via the internet to support analysis, create reports, track requisitions, monitor trends, and project future needs based on the true demands of the customer.  The customer is able to format output to fit their exact needs and save that output securely on the DAAS server, or distribute the results, as desired.  Standard Commercial Off-The-Shelf (COTS) tools are used to allow users access to information and data resident at ~~DAAS~~.  These tools allow retrieval of needed data from multiple repositories within DAAS and the application of customer business rules to accomplish the translation and aggregation of DAAS managed data.  The ultimate goal is to work more effectively with the war-fighter by: improving the capability to track the movement of critical spare parts; identify logistics bottlenecks; provide visibility of misdirected shipments, and facilitate the identification of processing errors using the data provided by the LDG.  The LDG is a vital element in supplying logistics data from one source to support the total logistics reporting requirements throughout the DoD.

		AP1.1.2.4.  Logistics Information Data Systems.  Includes the following information systems:

Logistics Information Data Services (LIDS).  The LIDS is a report generation system providing standard monthly, quarterly, semiannual, and ad-hoc reports for DAAS and the DoD Components/Participating Agencies.  The reports are stored on the DAAS’ web site for customer review.  The data is compiled from historical files and later correlated into various sections of the LIDS report.  Special ad hoc reports, related to logistical transactions, can be accommodated by special request on a ‘one-time’ or ‘temporary basis.’

		AP1.1.2.5.  Logistics Metrics Analysis Reporting System (LMARS).  The LMARS tracks materiel as it moves through the logistics pipeline and reports the associated response times.  LMARS has archived data IAW DoDI 5015.02    LMARS uses information from DLMS transactions processed by the DAAS, Electronic Data Interchange (EDI) transaction feeds, off-line data feeds, and transportation data received from the Integrated Data Environment Global Transportation Network Convergence (IGC) to measure the logistic response time for wholesale-managed items.  The data recorded in the Logistics On-line Tracking System (LOTS) repository regarding wholesale-managed items is used to produce transaction counts and average pipeline processing times, in days, for the 12 segments comprising the life cycle of a logistics transaction.  The measurement begins with the serial (i. e. birth) date of the requisition and ends with receipt by the DAAS of the Material Receipt Acknowledgement (MRA) transaction.  Standard LMARS reports (See appendix 5.2.) are produced weekly and monthly.  LMARS provides the DoD community with the capability to maintain, track, extract, and tailor logistics data to their needs and its supporting infrastructure through the life- cycle tracking of logistics transactions, further supporting command and control decisions, through an ad-hoc query capability that runs in seconds instead of weeks.  This capability generates reports on DoD-wide Logistics Response Time (LRT) measurements and on the performance of the logistics pipeline.  See appendix 3.2.7. and appendix 5.2, for more information.  Components include:

			AP1.1.2.5.1.  Logistics Response Time (LRT).  LRT measures the logistics processing time elapsed at the wholesale level.  LRT begins with the requisition entry into the wholesale level by the originating Supply Support Activity (SSA), and ends with the receipt of the item at the wholesale level SSA.  LRT does not include the elapsed time from the identification of the item need by the customer (mechanic, electrician) until the item is received by that customer.  The DoD has identified LRT as a key performance measure to monitor supply chain effectiveness.  Using data that is readily available from DAAS, the DoD performs analysis on the logistics response time of the pipeline processes.  DAAS provides the LRT data to the DoD Components in a web-based environment for their use in preparing local LRT reports.  Other categories of materiel, such as medical supplies and subsistence, were added to the LRT measure to show impact to their areas of supply.  All transactions related to medical and subsistence do not flow through DAAS, but are provided through off-line feeds.

		AP1.1.2.6.  Logistics On-line Tracking System (LOTS).  The LOTS is a DAAS managed repository providing enhanced capabilities for extracting pertinent logistics transaction information that flows through DAAS.  This information supports logistics management, information query, transaction tracking, and reporting requirements.  The LOTS is populated from images of transactions processed by the DAAS.  Requisition related transactions or excess transactions are stored in the LOTS repository for research, tracking, production of reports, and management services.  The LOTS repository can be accessed by DAAS produced tools (e.g. Web Visual Logistics Information Processing System (WebVLIPS) and Web Logistics On-Line Tracking System (WebLOTS) which allow tracking and retrieval of requisition, passive RFID, and excess life cycle information.  WebVLIPS provides access to addressing and stock number information stored at DAAS, linking that information to the DLMS transactions stored in LOTS.  LOTS shows the life cycle of logistics transactions, tracking requisitions from their release into the DoD pipeline until the materiel is posted to the accountable record at the destination activity.  The LOTS provides tracking of excess transactions and the movement of those excesses to the destination depot or disposal site.  It, also, provides two tables in support of passive RFID implementation: one to facilitate registration of passive RFID readers/portals and the other to record the actual passive RFID tag read by those readers/portals.  WebLOTS provides the capability for external systems to utilize direct tailored system queries to access LOTS data.  See appendix 3.2.6. for more information.  LOTS can be accessed through the following two web-enabled systems:

			AP1.1.2.6.1.  Web Visual LIPS Query System (WebVLIPS).  WebVLIPS is a web based query system that can be accessed from any internet attached personal computer using either the Internet Explorer or Firefox browser.  WebVLIPS accesses data in the LOTS repository.  The WebVLIPS customer can track a requisition throughout the logistics pipeline from the time the requisition is released into the DoD pipeline until the materiel is posted to the accountable records at the requisitioning activity.  WebVLIPS has the capability to track reports of excess and the movement of those excesses either to the destination depot or to a disposal facility.  WebVLIPS integrates information on DoDAAD, MILRI, SoS, project code, port code, status code, unit of issue code, signal code, hold code, advice code, condition code, and mode code to assist the customer in tracking the life cycle of the requisition.****It also captures and visualizes the extended transportation data (e.g., secondary transportation tracking numbers, commercial carrier identification by Standard Carrier Alpha Code (SCAC), transportation priority, and origin shipper identification) in DLMS Supply Shipment Status messages.  This is not otherwise available in Defense Logistics Standard System (DLSS) or Military Standard Requisitioning and Issue Procedures (MILSTRIP) legacy transaction shipment status transactions.  WebVLIPS is typically used by the customer for single queries, which do not require the results to be input directly into their logistics systems.  WebVLIPS returns query results to the customers in the form of a web page and provides a Distribution Standard System (DSS) asset query (asset balance/due-in) for the Defense Logistics Agency (DLA) supply centers, except for DLA Aviation.

			AP1.1.2.6.2.  Web Logistics On-line Tracking System (WebLOTS).  WebLOTS is a system-to-system web interface which allows the customer’s system to query the LOTS database for the latest status for their requisitions.  WebLOTS queries return requisition status data (such as National Stock Number (NSN), Quantity, Inventory Control Point (ICP), etc.).  Prior to establishing a WebLOTS interface, users must complete a SAR and negotiate a Memorandum of Agreement (MOA) with the WebLOTS project manager.  When completed, the user’s system can be setup to perform queries by document number, Transportation Control Number (TCN), unit of issue, and Julian date.  The MOA will detail the type and number of queries being utilized by each customer.  WebLOTS interfaces are typically utilized when the customer has a requirement for large amounts of logistics data to be input directly into their system(s) for processing.

AP1.2.  DoD GATEWAY (DGATE) PROFILE

	AP1.2.1.  General.  The DGATE profile represents the entry point for DLSS or MILSTRIP legacy transactions, and selected EDI transactions into the DAAS infrastructure.  DGATE is a key profile for DAAS, which provides a strategic gateway for processing and transmitting the received legacy logistics data to a myriad of activities that operate within the logistics community.  The DGATE profile, also, provides for the network and data interoperability within these activities to facilitate the exchange of logistics data.  It supports the interoperability of mission support functions, including the capturing of requirements, repository file maintenance, communications exchange, logistics data routing, and distribution.

	AP1.2.2.  Profile Component Description.  DGATE is composed for the following systems:

		AP1.2.2.1. DAAS Automated Message Exchange System (DAMES).  DAMES is a locally written Personal Computer (PC) client software that provides a communications capability, allowing Foreign Military Sales (FMS) customers to exchange logistics data with the US Government and the DoD logistics community.  DAMES PC based Software functions as an interface for the customer and provides the capability to communicate directly with DAAS, sending and receiving logistics transactions and narrative message traffic.  The Microsoft© Windows version of DAMES communicates via Secure File Transfer Protocol (SFTP) over the internet.  The DAAS’ Single Gateway manages the input and output files for those DAMES users that utilize SFTP as their method of exchanging logistics data with DAAS.  As data is received, Service Oriented Messaging Architecture (SOMA) validates the format of the input message file for further processing.  Transaction files, produced by end users’ programs, are built using standard Joint Army-Navy-Air Force Publication (JANAP) data pattern message format.  Messages containing narrative text, MILSTRIP transactions and non-standard part number requisitions may also be built interactively through the DAMES software interface.  Messages built for transmission are contained within a portion of a file in the software until the next communication connection.  When a communication session has been established, all active messages are sent from the end users PC to DAAS, and then all messages stored at DAAS, addressed to the end user are transmitted back to the end user’s PC.  Various menu options are available to process the receive file such as displaying, editing, printing, sorting, or saving to a disk file.  See Appendix 2.2.2. for more information.

AP1.2.2.2.  DAAS Logistics Gateway System (DLOGS).  DLOGS is a collection of services and programs within DAAS, which provides an entry point and central communications node that enables DoD Components/Participating Agencies to communicate seamlessly over disparate networks and with each other.  It accepts numerous formats including transactions in DLMS ASC X12 or eXtensible Markup Language (XML), and User Defined File (UDF) and then converts the non-standard formats to a DAAS internal message format (DIMF) suitable for processing.  The four major components within the DLOGS are the (1) DAAS Single Gateway (DSG), (2) SOMA, (3) DAAS Routing Control System (DRCS), and (4) DMARS.  The DSG provides secure front-end communications services for the DAAS, utilizing communication protocols such as, SFTP, IBM Messaging Queue~~~~(MQ), Hyper Text Transfer Protocol Secure (HTTPS), Simple Mail Transfer Protocol (SMTP), etc.  The DSG also provides initial authentication and login services.  SOMA provides message validation, message transformation, back-end authentication and logging services, enterprise service bus functionality, and other services.  The DMARS performs transaction level services, such as, validation, editing, routing, imaging and exception processing.  DRCS provides batching, batch integrity, statistics, exception and reject handling, and special processing.  The following major services are provided under the DLOGS umbrella:

			AP1.2.2.2.1.  DAAS Single Gateway (DSG).  ***As an integral part of the overall SOMA System,***the majority of ***the communication gateway components of DSG are deployed in the Demilitarized Zone (DMZ) while MQ and SMTP gateways are deployed in the BLZ (Business Logic Zone) servers*** providing a ***custom-developed, multi-tiered***secure front-end communications service for the DAAS; utilizing communication protocols, such as, SFTP, IBM MQ, ***AS2,***HTTPS, SMTP, etc.  Connections into the DSG are prevented from directly accessing the DAAS internal enclave ***utilizing custom developed Proxy servers***.  All ***DSG***communication attempts, ***addresses, interactions, and data exchanges***are authenticated and logged.

			AP1.2.2.2.2.  Service Oriented Messaging Architecture (SOMA).  SOMA provides message validation, message transformation, back-end authentication, logging***,******and transmission*** services.  ***SOMA, as a primary routing service, processes DLSS, EDI, UDF formatted messages.*** Messages may contain one or more transactions.  SOMA receives and transmits files and messages using ***a wide array of transmission protocols including IBM WebSphere MQ, HTTPS, AS2, SMTP, and***SFTP.  SOMA performs a number of other functions, including:

				AP1.2.2.2.2.1.  Receiving files outside of the DLSS transaction format and forwarding them to the appropriate internal applications based on the file's filename.

				AP1.2.2.2.2.2.  Performing duplicate header information checks.

				AP1.2.2.2.2.3.  Converting file formats to the DAAS Internal Message Format (DIMF).

				AP1.2.2.2.2.4.  Transformation of messages based upon the required delivery protocol and message format.

				AP1.2.2.2.2.5.  Transmission of output message information to the archive process for historical retransmission and reporting purposes.

			AP1.2.2.2.3.  DAAS Micro Automated Routing System.  DMARS receives messages containing one or more transactions from SOMA.  It then performs transaction level services, such as, transaction validation, editing, routing, imaging, and exception processing based on customer supplied business rules.  These business rules are routing, editing, and image instructions maintained within the DMARS program logic.  Each DoD Component/Participating Agency has its own business rules relative to the routing and editing of its transactions.  The DAAS Management Support Directorate, with input from DoD Component/Participating Agency Point of Contact (POC), dictates the application of business rules encoded in the DMARS.  Once transactions have been validated, edited, and routed, they are sent to the DRCS for further processing.

			AP1.2.2.2.4.  DAAS Routing Control System DRCS).  DRCS is responsible for receiving transactions from the DMARS and forwarding them to the SOMA for delivery.  DRCS provides batching and batch integrity services for the routed transactions from DMARS and then forwards the transactions to SOMA for message creation and transmission.  The DRCS is also responsible for statistical reporting, exception and reject handling, archiving all transactions, and performing special processing. 

			AP1.2.2.2.5.  Web Requisitioning (WebREQ).   Provides the DoD Components/Participating Agencies with the capability to build and submit transactions via HTTPS.  These transactions are sent to DAAS for processing.  This capability allows for submission of any DLSS or MILSTRIP legacy transaction type.  The supply status transactions can be returned back to the customer using this same methodology.

			AP 1.2.2.2.6.  DoD Web Supply Discrepancy Report (WebSDR).  An application system that provides a web-based entry method for inputting Supply Discrepancy Reports (SDRs) attributable to shipping or packaging discrepancies, which supports DLMS transaction exchange requirements.  The DoD WebSDR provides the capability to automate the SF 364 SDR paper-based form and transition the format to a Commercial EDI standard.  The DoD WebSDR system facilitates communications and interoperability between U.S. Military, DoD, and Federal Agencies in order to determine the cause of such discrepancies, effect corrective action, and prevent recurrence of the discrepancy.  It allows routing for web submissions and logistics transactions according to business rules, translation to standard DLMS transaction formats in X12 and XML, conversion to e-mail format, as needed, and, by exception, the Army pre-DLMS user-defined file format, which supports information exchange between the action office and the shipper.  When requested by DoD Components/Participating Agencies, the WebSDR application supports business rules for information copy preparation and distribution to provide visibility of discrepancies to relevant organizations.  DoD WebSDR captures the SDR and response management statistics to facilitate performance reviews and provides an automated process for tracking SDR response information.  The Auto-fill feature uses the DAAS requisition history to populate the SDR.  ICPs, Depots, and Action Agencies can initiate their responses via the DoD Component-sponsored SDR application for transmission via DLMS interface or use the DoD WebSDR on-line capability pending DLMS implementation.  This allows for faster resolution of discrepancies and near-real time SDR reporting for immediate identification of discrepancies.  It, also, reduces response delays resulting from misrouted SDRs or mailed documents.  Automated edit and rejection capability enforces SDR procedure and transaction format compliance by returning inappropriate transmissions to the originator for correction, thereby, reducing Component receiving system errors.  Web–based queries allow users to have immediate access to the DAAS historical data related to the discrepant shipments.  DoD WebSDR provides the capability to upload documentation and pictures in support of the discrepancy claim.  Queries and management reports make it possible to locate specific SDRs by various criteria and identify trends, establish volume and dollar values of SDRs, bring management attention to problems with shipping activities, measure compliance with SDR timeframes, and improve the requisitioning and distribution processes within logistics operations.  The DoD WebSDR application moves the SDRs into an integrated transactional environment, providing an effective means to report, resolve, and measure discrepancies related to pipeline performance.

		AP1.2.2.3.  System Access Request (SAR).  The SAR system provides a formal request mechanism for obtaining access to the various systems activities on the DAAS website.

AP1.3.  DAAS ELECTRONIC BUSINESS (EBUS) PROFILE

	AP1.3.1.  General.  The DAAS EBUS**profile processes standard logistics transactions (Accredited Standards Committee (ASC) X12, or XML) covered by specific DLMS Implementation Conventions (ICs).  As the DoD Components/ Participating Agencies implement the DLMS formats, the DAAS’ transaction processing workload is continuing to grow for both the DLMS and the DLSS transactions.  It is expected that, eventually, as most customers migrate from the DLSS, the DMLS ASC X12 or other variable-length transactions, such as XML, will eventually predominate.  The DAAS architecture will ensure that all standard transaction formats, as authorized within the DLMS, are accommodated in the DAAS processing.  DAAS has assumed program management responsibility for the GEX as part of the dissolution of the Business Transformation Agency (BTA) and is subsuming the two Defense Information Systems Agency (DISA) GEX sites by migrating all of their customers/connections to the two DLA GEX eB gateway sites.

	AP1.3.2.  eBusiness System Description.  EDI Gateway System Process.  EDI provides standard transaction formats for use in the automated, machine-to-machine, exchange of eB transactions between the DoD Components/ Participating Agencies, and their commercial sector trading partners.  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) mail-boxing services through the following:

		AP1.3.2.1.  DoD Global Exchange (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.

		AP1.3.2.2.  Transaction Translation.  The COTS IBM Transformation Extender (ITX) (formerly Mercator) mapping and transformation software toolset currently provides the translation capability to convert incoming transaction formats into the appropriate outgoing transaction formats, via business mapping rules.  DAAS is also utilizing a second commercial translation software product called Ab Initio that has been employed by the DISA GEXs for some of their customer mappings.

AP1.5.  DLA INTEGRATED DATA ENVIRONMENT (IDE) PROFILE

	AP1.5.1.  General.  DAAS, along with the DLA Logistics Information Service, have assumed responsibility for the sustainment of the DLA IDE.  ***DLA IDE function within the DAAS environment is embedded within the SOMA/DSG operational parameters.***

	AP1.5.2.  System Description:  The DLA IDE supports data and information sharing through a single point of access that supports the exchange of DLA data between systems, sharing of DLA corporate logistics information, and enhanced DoD Asset Visibility.  Additionally, IDE provides assured access to supply chain management data, centrally managed metadata, authoritative data sources, and DoD logistics business rules.  Additionally, IDE supports logistics (supply chain & distribution) Communities of Interest and reduces system-to-system interface costs through implementation of net-centric (webMethods) data strategy goals.

	AP1.5.3.****Discussion:  Per the DLA IDE Transition Initiative, ***DAAS has migrated and integrated all IDE interfaces from DISA into the existing DAAS architecture (SOMA/DSG). Since its completion,*** the former IDE mission, services, and interfaces have been incorporated and considered a part of DAAS proper, at which time the IDE profile ***has*** ceased to exist and be considered a part of the standard DAAS business through the use of its various AIS applications, including but not limited to the DSG, SOMA, and GEX.  Currently the entirety of the Non Secure Internet Protocol Router Network (NIPRNet) ***and the Secure Internet Protocol Router Network (SIPRNet) portions of the IDE environment have been transitioned into the DAAS infrastructure.***

	AP1-12	APPENDIX 1