The AMIE/ba product was designed to support the needs of the AAMVA user community for message translation. While AAMVA distributes a software product (the Unified Network Interface, or UNI) which provides, among other features, a message translation capability, many AAMVA customers desired a "translation only" solution.
The AMIE/ba product targets mainly non-DMV AAMVA Application users who use a batch network service and typically participate in only one AAMVA application. The primary function of the AMIE/ba software is to translate network AMIE messages into a "flat file" format (Call List) easy to use by an application. The translation can also be done from the "flat file" format into the network AMIE format.
The interface to the AMIE/ba consists of four files: the Outbound Call List file, the Outbound Network Message file, the Inbound Network Message file, and the Inbound Call List file.
Call List Files
The Call List file is the interface to the site's AAMVA-compliant application. For Outbound processing, the site’s application creates a Call List file. This file is passed to the AMIE/ba, which translates it into a Network Message file, consistent with the AAMVA network environment. For Inbound processing, a Network Message file is translated by the AMIE/ba into a Call List file, which is in turn read by the site’s application.
The format of the Call List file is dependent on the AAMVA application being used. Call List formats are described with COBOL PICTURE clauses which are provided as part of the AMIE/ba product. C header files can also be provided for applications developed in C or C++.
Network Message Files
The Network Message file contains AAMVAnet™ Message Interchange Envelope (AMIE) formatted messages. These are the translated Call List messages. They are in the format expected by the AMIE/ba Inbound Process and the Unified Network Interface (UNI) for inbound messages.