Legacy Text Examples - Administrative Message (AM/AML)

Administrative Message Legacy Specifications

This section describes Legacy format specifications and provides Legacy examples of Administrative Message (AM) transactions for state, regional and all points broadcasts.

To send an Administrative Message, enter the following:

"AM." (2-4 character message type). Sender's ORI (9 character ORI is mandatory) agency identifier followed by a period.

Destination ORI for the agency that is to receive the message, followed by a period. If the
intended receiver of the message is a state control terminal, a 2-character ORI may be used.
In all other cases the ORI(s) must be 9 characters.

Control field - optional. The three characters - "TXT" Message reference number. (This is the number that will be referenced in all responses or
future references to this message.) Name of originating agency. Date message was originated. Name of destination agency (address).

If the message is additional information, continuation, correction, reply or cancellation, the
message text should reference the previous message using the date and reference number
of the previous message.

Narrative portion of the text. Last name or initials of the terminal operator or author of the message and his/her location. Time - use the 24-hour clock and include time zone (i.e., 0945EST).

The table below describes the message format a station will receive.

Station Will Receive: Message type. Sending ORI. Time and date when message was received by Nlets. Number of messages sent from the sending POE (point of entry). Time and date when message was sent from Nlets. Number of messages received by destination POE (point of entry). Destination ORI. Text (always preceded by "TXT").

Each field on a line will be separated by a space.

Message Format

Each Nlets member, including states and other agencies or organizations, must insert the caption "MESSAGE INITIATED BY A NON-CRIMINAL JUSTICE AGENCY" immediately after the "TXT" on all Administrative Messages (AM) sent by agencies or organizations without an NCIC assigned law enforcement or criminal justice ORI.

Legacy Multiple Destination Message Specifications

Specifications for messages to multiple destinations include the following:

To send a message to more than one agency, enter multiple ORIs or region codes separated by a comma.
A message may be sent to a maximum of five locations.
Each terminal designated as a destination in the input message receives a copy of the message.
All destination ORIs will be included in the text of the message directly after the text (TXT) in parentheses.

Legacy State Broadcast Message Specifications

All rules of the Administrative Message apply with the following exceptions:

The words "REQUEST FOR STATEWIDE BROADCAST" should immediately follow the "TXT".
The two-character ORI (state code) is always used because this message is always sent to a state control terminal.
State broadcasts may be sent to up to five (5) states.

Legacy Regional Broadcast Message

The three types of regional broadcast messages and their format and usage rules are described in the table below:

Message Type Format and Usage Rules Administrative Messages
(Message type = AM)

These messages must comply with both the format and
usage rules.
Note: If the administrative message includes information that
is related to officer safety (e.g., armed and dangerous) this
phrase should be placed at the front of the message on its
own line to highlight it.

Vehicle Registration
inquiries
by LIC/LIY/LIT
or by VIN
(Message type = RQ)

If a user uses a RQG, Nlets will change it to a RQ.
A state may optionally use an RQG.

Driver License inquiries
by NAM/DOB
(Message type = DQ).

When a user uses a DQG Nlets will change it to a DQ.
A state may optionally use a DQG.

The specifications for legacy regional broadcasts are listed below.

Specifications for Legacy Regional Broadcasts There may be up to five destination addresses.

These addresses may be a mixture of any existing regional codes, two-character point-of-
entry codes (i.e., TX, NY, FB, etc.) or 9-character ORIs currently accepted by the Nlets
computer.

Each address is separated by a comma with no embedded spaces. A period follows the last destination address.

If the period is inadvertently placed after an address that is not meant to be the final
destination, the message will not be sent and an error message indication "NO TXT FOUND"
will be issued by the Nlets computer.

Final destinations will receive the normal Nlets header except that, immediately following
the TXT, the region broadcast code and/or other destination codes will be enclosed in
parentheses on the same line.

The next line will contain the phrase "REQUEST FOR REGIONAL BROADCAST" and also
will be inserted by Nlets. For "RQs" and "DQs" sent regionally neither the phrase nor the parenthesized addresses will
be inserted.

To assist control terminals in further disseminating administrative type regional requests, the
sender may include a request such as: "Deliver to State Crime Lab" or "Deliver to Major
Cities".

Legacy All Points Broadcast Specifications

An APB must comply with both the format and usage rules.

For messages addressed to "AP", addressees will receive the normal Nlets header except that, immediately following the TXT, the parenthesized code ("AP") will be inserted by the Nlets computer. On the next line Nlets will insert the phrase "REQUEST FOR NATIONWIDE BROADCAST".
To assist control terminals in further disseminating APB requests, the sender may request, for example, "Deliver to State Crime Lab" or "Deliver to Major Cities".

In rare instances it may be appropriate to send a death or funeral notice APB. In these instances the following format should be used.

Death/Funeral Notice Format for All Points Broadcast

NAME:
AGENCY:
CRIMINAL JUSTICE ORGANIZATIONAL AFFILIATE:
DATE OF DEATH:
LINE OF DUTY (Y OR N):
DATE OF FUNERAL:
LOCATION OF FUNERAL:
PREVIOUS CRIMINAL AGENCIES EMPLOYED:
FOR ADDITIONAL INFORMATION CONTACT:
TELEPHONE NUMBER:

Administrative Message Legacy Examples

Example 1: An Administrative Message sent to Nlets with only one destination.

AM.NL100AM00.NL200AM00.TXT
MESSAGE

Example 2: An Administrative Message received by a user with only one destination.

AM.NL100AM00
12:30 08/18/2011 00057
12:30 08/18/2011 00080 NL200AM00
TXT
MESSAGE

Example 3: An Administrative Message sent to Nlets with Multiple destinations.

AM.NL100AM00.NL200AM00,NL300AM00.*JGXBAGXXXX.TXT
MESSAGE

Example 4: An Administrative Message received by a user with multiple destinations.

AM.NL100AM00
12:21 08/18/2011 00054
12:22 08/18/2011 00077 NL300AM00
*JGXBAGXXXX
TXT (NL200AM00,NL300AM00)
MESSAGE

Example 5: An Administrative Message sent to Nlets using a state code.

AM.AZNLETS20.IN.TXT
MESSAGE

Example 6: An Administrative Message received with a state code.

AM.AZNLETS20
05:00 09/22/2011 00008
05:00 09/22/2011 27882 IN
TXT
* Powered by NLETS *

REQUEST FOR STATEWIDE BROADCAST

MESSAGE

Example 7: An Administrative Message sent to Nlets using a region code.

AM.AZNLETS20.A1.TXT
MESSAGE

Example 8: An Administrative Message received with a region code.

AM.AZNLETS20
05:00 09/22/2011 00008
05:00 09/22/2011 27882 MA
TXT (A1)
* Powered by NLETS *

REQUEST FOR STATEWIDE BROADCAST

MESSAGE

Example 9: An Administrative Message sent to Nlets using the All Points Broadcast code.

AM.AZNLETS20.AP.TXT
MESSAGE

Example 10: An Administrative Message received with an All Points Broadcast code.

AM.AZNLETS20
05:00 09/22/2011 00008
05:00 09/22/2011 87134 LA
TXT (AP)
* Powered by NLETS *

REQUEST FOR NATIONAL BROADCAST

MESSAGE