Difference between revisions of "Section 04: Administrative Messages"

From Nlets Wiki
Jump to: navigation, search
(→‎Administrative Message NIEM Examples)
(→‎Administrative Message NIEM Examples)
Line 729: Line 729:
  
 
<syntaxhighlight lang="xml">
 
<syntaxhighlight lang="xml">
−
<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
+
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
−
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
+
<n2:NLETSMessageHeader>
−
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+
<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
−
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
+
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
−
  <n2:NLETSMessageHeader>
+
<nh2:DestinationORIID>IN</nh2:DestinationORIID>
−
    <nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
+
<nh2:DocumentControlFieldText>
−
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
+
<![CDATA[NLETSTEST1]]>
−
    <nh2:DestinationORIID>IN</nh2:DestinationORIID>
+
</nh2:DocumentControlFieldText>
−
  </n2:NLETSMessageHeader>
+
</n2:NLETSMessageHeader>
−
  <n2:NLETSMailData n2:key="AM">
+
<n2:NLETSMailData n2:key="AM">
−
    <n2:MailMessageText>MESSAGE</n2:MailMessageText>
+
<n2:MailMessageText>
−
  </n2:NLETSMailData>
+
* Powered by NLETS
 +
 
 +
    REQUEST FOR STATEWIDE BROADCAST
 +
    TEST MESSAGE</n2:MailMessageText>
 +
</n2:NLETSMailData>
 
</n2:NLETS>
 
</n2:NLETS>
 
</syntaxhighlight>
 
</syntaxhighlight>
Line 755: Line 759:
  
 
<syntaxhighlight lang="xml">
 
<syntaxhighlight lang="xml">
−
<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
+
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
−
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
+
<n2:NLETSMessageHeader>
−
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+
<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
−
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
+
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
−
  <n2:NLETSMessageHeader>
+
<nh2:DestinationORIID>IN</nh2:DestinationORIID>
−
    <nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
+
<nh2:DocumentControlFieldText>
−
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
+
<![CDATA[NLETSTEST1]]>
−
    <nh2:DestinationORIID>IN</nh2:DestinationORIID>
+
</nh2:DocumentControlFieldText>
−
    <nh2:DocumentControlFieldText><![CDATA[0123456789]]></nh2:DocumentControlFieldText>
+
<nh2:MessageReceiveDate>11/27/2019</nh2:MessageReceiveDate>
−
    <nh2:MessageReceiveDate>03/26/2013</nh2:MessageReceiveDate>
+
<nh2:MessageReceiveTime>05:03</nh2:MessageReceiveTime>
−
    <nh2:MessageReceiveTime>13:58</nh2:MessageReceiveTime>
+
<nh2:MessageSendDate>11/27/2019</nh2:MessageSendDate>
−
    <nh2:MessageSendDate>03/26/2013</nh2:MessageSendDate>
+
<nh2:MessageSendTime>05:03</nh2:MessageSendTime>
−
    <nh2:MessageSendTime>13:58</nh2:MessageSendTime>
+
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
−
    <nh2:ReceiveMessageNumeric>00020</nh2:ReceiveMessageNumeric>
+
<nh2:SendMessageNumeric>00347</nh2:SendMessageNumeric>
−
    <nh2:SendMessageNumeric>00027</nh2:SendMessageNumeric>
+
</n2:NLETSMessageHeader>
−
  </n2:NLETSMessageHeader>
+
<n2:NLETSMailData n2:key="AM">
−
  <n2:NLETSMailData n2:key="AM">
+
<n2:MailMessageText>
−
    <n2:MailMessageText>* Powered by NLETS
+
  * Powered by NLETS
−
+
 
 
     REQUEST FOR STATEWIDE BROADCAST
 
     REQUEST FOR STATEWIDE BROADCAST
−
     TEST MESSAGE
+
     TEST MESSAGE</n2:MailMessageText>
−
    </n2:MailMessageText>
+
</n2:NLETSMailData>
−
  </n2:NLETSMailData>
 
 
</n2:NLETS>
 
</n2:NLETS>
 
</syntaxhighlight>
 
</syntaxhighlight>
Line 792: Line 795:
  
 
<syntaxhighlight lang="xml">
 
<syntaxhighlight lang="xml">
−
<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
+
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
−
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
+
<n2:NLETSMessageHeader>
−
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+
<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
−
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
+
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
−
  <n2:NLETSMessageHeader>
+
<nh2:DestinationORIID>A1</nh2:DestinationORIID>
−
    <nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
+
<nh2:DocumentControlFieldText>
−
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
+
<![CDATA[NLETSTEST1]]>
−
    <nh2:DestinationORIID>A1</nh2:DestinationORIID>
+
</nh2:DocumentControlFieldText>
−
  </n2:NLETSMessageHeader>
+
</n2:NLETSMessageHeader>
−
  <n2:NLETSMailData n2:key="AM">
+
<n2:NLETSMailData n2:key="AM">
−
    <n2:MailMessageText>MESSAGE</n2:MailMessageText>
+
<n2:MailMessageText>
−
  </n2:NLETSMailData>
+
* Powered by NLETS
 +
 
 +
    REQUEST FOR REGIONAL BROADCAST
 +
    TEST MESSAGE</n2:MailMessageText>
 +
</n2:NLETSMailData>
 
</n2:NLETS>
 
</n2:NLETS>
 
</syntaxhighlight>
 
</syntaxhighlight>
Line 818: Line 825:
  
 
<syntaxhighlight lang="xml">
 
<syntaxhighlight lang="xml">
−
<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
+
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
−
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
+
<n2:NLETSMessageHeader>
−
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+
<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
−
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
+
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
−
  <n2:NLETSMessageHeader>
+
<nh2:DestinationORIID>A1</nh2:DestinationORIID>
−
    <nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
+
<nh2:DocumentControlFieldText>
−
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
+
<![CDATA[NLETSTEST1]]>
−
    <nh2:DestinationORIID>A1</nh2:DestinationORIID>
+
</nh2:DocumentControlFieldText>
−
    <nh2:DocumentControlFieldText><![CDATA[CONTROLFLD]]></nh2:DocumentControlFieldText>
+
<nh2:MessageReceiveDate>11/27/2019</nh2:MessageReceiveDate>
−
    <nh2:MessageReceiveDate>03/28/2013</nh2:MessageReceiveDate>
+
<nh2:MessageReceiveTime>05:06</nh2:MessageReceiveTime>
−
    <nh2:MessageReceiveTime>11:30</nh2:MessageReceiveTime>
+
<nh2:MessageSendDate>11/27/2019</nh2:MessageSendDate>
−
    <nh2:MessageSendDate>03/28/2013</nh2:MessageSendDate>
+
<nh2:MessageSendTime>05:06</nh2:MessageSendTime>
−
    <nh2:MessageSendTime>11:30</nh2:MessageSendTime>
+
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
−
    <nh2:ReceiveMessageNumeric>00005</nh2:ReceiveMessageNumeric>
+
<nh2:SendMessageNumeric>00348</nh2:SendMessageNumeric>
−
    <nh2:SendMessageNumeric>00005</nh2:SendMessageNumeric>
+
</n2:NLETSMessageHeader>
−
  </n2:NLETSMessageHeader>
+
<n2:NLETSMailData n2:key="AM">
−
  <n2:NLETSMailData n2:key="AM">
+
<n2:MailMessageText>
−
    <n2:MailMessageText>* Powered by NLETS
+
  * Powered by NLETS
−
+
 
 
     REQUEST FOR REGIONAL BROADCAST
 
     REQUEST FOR REGIONAL BROADCAST
−
     TEST MESSAGE AM 1
+
     TEST MESSAGE</n2:MailMessageText>
−
    </n2:MailMessageText>
+
</n2:NLETSMailData>
−
  </n2:NLETSMailData>
 
 
</n2:NLETS>
 
</n2:NLETS>
 
</syntaxhighlight>
 
</syntaxhighlight>
Line 855: Line 861:
  
 
<syntaxhighlight lang="xml">
 
<syntaxhighlight lang="xml">
−
<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
+
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
−
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
+
<n2:NLETSMessageHeader>
−
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+
<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
−
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
+
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
−
  <n2:NLETSMessageHeader>
+
<nh2:DestinationORIID>AP</nh2:DestinationORIID>
−
    <nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
+
<nh2:DocumentControlFieldText>
−
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
+
<![CDATA[NLETSTEST1]]>
−
    <nh2:DestinationORIID>AP</nh2:DestinationORIID>
+
</nh2:DocumentControlFieldText>
−
    <nh2:DocumentControlFieldText><![CDATA[CONTROLFLD]]></nh2:DocumentControlFieldText>
+
</n2:NLETSMessageHeader>
−
  </n2:NLETSMessageHeader>
+
<n2:NLETSMailData n2:key="AM">
−
  <n2:NLETSMailData n2:key="AM">
+
<n2:MailMessageText>
−
    <n2:MailMessageText>* Powered by NLETS
+
* Powered by NLETS
−
+
 
 
     REQUEST FOR NATIONAL BROADCAST
 
     REQUEST FOR NATIONAL BROADCAST
−
     TEST AP MESSAGE
+
     TEST AP MESSAGE</n2:MailMessageText>
−
    </n2:MailMessageText>
+
</n2:NLETSMailData>
−
  </n2:NLETSMailData>
 
 
</n2:NLETS>
 
</n2:NLETS>
 +
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Line 886: Line 892:
  
 
<syntaxhighlight lang="xml">
 
<syntaxhighlight lang="xml">
−
<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
+
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
−
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
+
<n2:NLETSMessageHeader>
−
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+
<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
−
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
+
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
−
  <n2:NLETSMessageHeader>
+
<nh2:DestinationORIID>AP</nh2:DestinationORIID>
−
    <nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
+
<nh2:DocumentControlFieldText>
−
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
+
<![CDATA[NLETSTEST1]]>
−
    <nh2:DestinationORIID>AZ</nh2:DestinationORIID>
+
</nh2:DocumentControlFieldText>
−
    <nh2:DocumentControlFieldText><![CDATA[CONTROLFLD]]></nh2:DocumentControlFieldText>
+
<nh2:MessageReceiveDate>11/27/2019</nh2:MessageReceiveDate>
−
    <nh2:MessageReceiveDate>03/28/2013</nh2:MessageReceiveDate>
+
<nh2:MessageReceiveTime>05:08</nh2:MessageReceiveTime>
−
    <nh2:MessageReceiveTime>17:07</nh2:MessageReceiveTime>
+
<nh2:MessageSendDate>11/27/2019</nh2:MessageSendDate>
−
    <nh2:MessageSendDate>03/28/2013</nh2:MessageSendDate>
+
<nh2:MessageSendTime>05:08</nh2:MessageSendTime>
−
    <nh2:MessageSendTime>17:07</nh2:MessageSendTime>
+
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
−
    <nh2:ReceiveMessageNumeric>00009</nh2:ReceiveMessageNumeric>
+
<nh2:SendMessageNumeric>00349</nh2:SendMessageNumeric>
−
    <nh2:SendMessageNumeric>00007</nh2:SendMessageNumeric>
+
</n2:NLETSMessageHeader>
−
  </n2:NLETSMessageHeader>
+
<n2:NLETSMailData n2:key="AM">
−
  <n2:NLETSMailData n2:key="AM">
+
<n2:MailMessageText>
−
    <n2:MailMessageText>* Powered by NLETS
+
  * Powered by NLETS
−
+
 
 
     REQUEST FOR NATIONAL BROADCAST
 
     REQUEST FOR NATIONAL BROADCAST
−
     TEST AP MESSAGE
+
     TEST AP MESSAGE</n2:MailMessageText>
−
    </n2:MailMessageText>
+
</n2:NLETSMailData>
−
  </n2:NLETSMailData>
 
 
</n2:NLETS>
 
</n2:NLETS>
 
</syntaxhighlight>
 
</syntaxhighlight>

Revision as of 06:12, 27 November 2019

Administrative Messages (AM & AML)

This section describes administrative messages and how to use them for multiple destinations and state, regional and all points broadcasts.

Overview

An Administrative Message (AM) is:

  • A criminal justice related point-to-point free form message.
  • Differentiated from other Nlets traffic in that it is free form.
  • May be used for practically any type of information transmission not associated with a specific message type.
  • May ask for information or assistance.
  • May be in response to a request from another agency.

An Administrative Message "law enforcement only" (AML) is:

  • A "law enforcement only" related point-to-point free form message.
  • May be used for practically any type of law enforcement only information transmission not associated with a specific message type.
  • May ask for information or assistance.
  • May be in response to a request from another agency.
  • Nlets will insert the caveat "FOR LAW ENFORCEMENT DISSEMINATION ONLY" within the body of the message prior to sending.

General guidelines for statewide, regional or all points messages:

  • To request a statewide, regional, or all points message, all Nlets members must use an administrative message (AM/AML).
  • Users should confine broadcast type messages to individual states, regions, or "community of interest" states.
  • State broadcasts may be sent to up to five (5) states.
  • Regional broadcast codes and two-character state codes may be intermixed in the destination portion of the header.
  • The general use of all points messages is discouraged.

Note: Information related to officer safety (e.g. "armed and dangerous") should be placed at the front of the message on its own line to highlight it.

Administrative messages to Canada should be addressed to the individual 2-character province or territory (AB, BC, MB, NF, NK, NS, NT, NU, ON, PE, PQ, SN and YT). Only narrative messages dealing with urgent operational police matters will be considered for broadcast in Canada.

Multiple Destination Administrative Messages

Multiple ORIs or region codes may be used to send a message to more than one agency or region, up to a maximum of five locations.

State Broadcast Messages

A state broadcast is an administrative message (AM/AML) sent to a state control terminal requesting that state to send an APB within the state.

Note: Information related to officer safety (e.g. "armed and dangerous") should be placed at the
front of the message on its own line to highlight it.

Regional Broadcast Messages

A regional broadcast provides Nlets users with the ability to send selected types of messages to the control terminal in a group(s) of predefined states and agencies located in a geographical area. The control terminal will handle further dissemination at its discretion.

The five types of regional broadcast messages are:

  • Administrative Messages (AM)
  • Administrative Messages "Law Enforcement Only" (AML)
  • Driver's License Queries (DQ)
  • Idenity Queries (IQ)
  • Vehicle Registration Queries (RQ)

Regional Broadcast Messages will be transmitted to points-of-entry only once. For example, if a message is addressed to two regions, the FBI and Dept. Of Treasury (TECS) would receive only one copy of the message, not two.

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".

Regional Codes

The Regional Codes with their respective states and agencies are listed in the tables that follow. Users that are preceded by an asterisk * do not receive regional broadcast messages.

Region A Code: A1 Region B Code: B1 Region C Code: C1 Region D Code: D1
Connecticut District of Columbia Kentucky Alabama
Maine Delaware North Carolina Arkansas
Massachusetts Maryland South Carolina Florida
New Hampshire New Jersey Tennessee Georgia
Rhode Island New York Virginia Louisiana
Vermont Pennsylvania West Virginia Mississippi
FBI/NCIC FBI/NCIC FBI/NCIC Puerto Rico
TECS TECS TECS FBI/NCIC
Interpol Interpol Interpol TECS
GSA TSA TSA TSA
TSA *Army *Army Interpol
*Army *Navy *Navy *Army
*Navy *Department of Interior *Department of Interior *Navy
*Department of Interior *Department of Justice *Department of Justice *Department of Interior
*Department of Justice     *Department of Justice
Region E Code: E1 Region F Code: F1 Region G Code: G1 Region H Code: H1
Indiana Iowa Arizona Alaska
Illinois Minnesota Colorado California
Michigan Montana Kansas Guam
Missouri Nebraska New Mexico Hawaii
Ohio North Dakota Oklahoma Idaho
Wisconsin South Dakota Texas Nevada
FBI/NCIC Wyoming Utah Oregon
TECS FBI/NCIC FBI/NCIC Washington
Interpol TECS TECS FBI/NCIC
TSA Interpol Interpol TECS
*Army TSA TSA Interpol
*Navy *Army *Army TSA
*Department of Interior *Navy *Navy *Army
*Department of Justice *Department of Interior *Department of Interior *Navy
  *Department of Justice *Department of Justice *Department of Interior
      *Department of Justice

Restrictions on Regional Broadcast Messages

There are two types of restrictions placed on regional broadcast messages. They include:

  • Secondary dissemination of regional broadcast messages received.
  • Content and use of regional broadcast messages sent.

Secondary Dissemination of Regional Broadcast Messages

Regional broadcasts may not be secondarily disseminated to non-criminal justice agencies without first obtaining specific approval from the originator.

Message Use and Content of Regional Broadcast Messages

Users are encouraged to use regional codes rather than APBs if possible. In instances where a regional code may not contain every state to which you wish to send a message, the use of multiple 2-character state codes and regional codes (up to a maximum of 5 destinations) can address many states without using a blanket APB. The list that follows outlines the restrictions on regional broadcast message content.

Restrictions Adopted for Regional Broadcast Content:
No social announcements (i.e., holiday messages or retirements).
No recruitment of personnel.
No messages in which the complainant is interested only in recovery of property.
No attempts to locate vehicle (breach of trust) without warrant.
No messages supportive or in opposition to political issues or announcements of meetings relative to such issues.
No messages supportive or in opposition to labor management issues or announcements relative to such issues.
No messages supportive or in opposition of legislative bills.
No messages relating to requests for information concerning salary, uniforms, personnel, or related items that can
be routinely obtained by correspondence or means other than Nlets.
No messages relating to the advertisement or sale of equipment.
No requests for criminal history record information. IQ, FQ and AQ must be used for this purpose.
No reply only if wanted (ROIWS).
No solicitation of funds.
No training messages that include the name of the company that is providing the training unless the company is
not-for-profit and is providing a direct service to law enforcement.

Exceptions to Restrictions on Regional Broadcast Messages

The restrictions may be waived under the following conditions:

  • A user has information that is pertinent to a criminal investigation, is of interest to a group of states, and cannot be entered into NCIC.
  • A user has information regarding kidnapping, skyjacking or other serious criminal acts. Keep messages as brief as possible.
  • A user has information on a wanted person that cannot be entered into NCIC but may be of interest to a group of states.
  • Permission has been granted by Nlets on a "per case" basis.
Note: Information related to officer safety (e.g. "armed and dangerous") should be placed at the front of the
message on its own line to highlight it.
Note: Users initiating want messages of any type; wanted persons missing persons or runaways must cancel
these messages when they no longer apply.

All Points Broadcast

An all points broadcast (APB) provides Nlets users with the ability to send administrative type messages (AM/AML) to each state and Federal member terminal.

A destination code of "AP" will result in the message being directed to all state and Federal control terminals.

Restrictions on All Points Broadcasts

There are two types of restrictions placed on nationwide broadcast messages. They include the following:

  • Secondary dissemination of APBs received and
  • Content and use of APBs sent.

Secondary Dissemination of All Points Broadcasts

Regarding secondary dissemination, nationwide broadcasts may not be secondarily disseminated to non-criminal justice agencies without first obtaining specific approval from the originator.

Message Use and Content of All Points Broadcasts

Regarding the content and use of APBs, users are urged to carefully consider whether there is a necessity to send the message to all states. If the message pertains to a geographical area of the United States (i.e., East Coast, Sunbelt) the user should seriously consider the use of a regional broadcast that will more narrowly focus on the states that could provide assistance.

The following table outlines the restrictions on all points broadcast content.

Restrictions Adopted for All Points Broadcasts
No social announcements (i.e., holiday messages or retirements).
No seminar, training class or convention announcements. Training and seminar announcements may be sent via
Regional broadcast codes to states in geographic proximity of the sender.
No recruitment of personnel.
No messages in which the complainant is interested only in recovery of property.
No attempts to locate vehicle (breach of trust) without warrant.
No excessively long messages.
No messages supportive or in opposition to political issues or announcements of meetings relative to such issues.
No messages supportive or in opposition to labor management issues or announcements relative to such issues.
No messages supportive or in opposition of legislative bills.
No messages relating to requests for information concerning salary, uniforms, personnel, or related items that
can be routinely obtained by correspondence or means other than Nlets.
No messages relating to the advertisement or sale of equipment.
No messages regarding wanted subjects or vehicles if they can be entered into NCIC.
No attempt to locate messages.
No reply only if records (ROIRS).
No reply only if wanted (ROIWS).
No runaways.
No missing persons.
No solicitation of funds.

Exceptions to Restrictions for All Points Broadcast Messages

The restrictions may be waived under the following conditions:

  • A user has information that is pertinent to a criminal investigation that is of interest to all states and cannot be entered into NCIC.
  • A user has information regarding kidnapping, skyjacking or other serious criminal acts. Keep messages as brief as possible.
  • A user has information on a wanted person that cannot be entered into NCIC but is of interest to all states.
  • Permission has been granted by Nlets on a "per case" basis.
Note: Information related to officer safety (e.g., "armed and dangerous") should be placed at the front of the
message on its own line to highlight it.
Note: Users initiating want messages of any type; wanted persons missing persons or runaways must cancel
these messages when they no longer apply.

Top

GJXDM (DEPRECATED)

GJXDM has been deprecated. Please contact Nlets for additional assistance with GJXDM.

Top

NIEM

Administrative Message NIEM Specifications

This section describes NIEM format specifications and provides NIEM examples of Administrative Message (AM) and Administrative Message Law Enforcement Only (AML) transactions for state, regional and all points broadcasts.

All Nlets NIEM messages must be based on the Nlets NIEM Message Structure and include the standard Nlets XML Header as detailed in Message Structure. The NIEM header and hierarchy of the elements in this section have been omitted to avoid redundancy. The associated schemas and instances should be consulted to determine the correct XPaths of the elements.

Element Dictionary

Transaction types detailed below include: Administrative Message (AM) & Administrative Message for Law Enforcement Only (AML).

Message Format

Administrative Message (AM)

Mail Data (n2:NLETSMailData)
This element will contain all elements specific to this transaction.

  Mail Text (n2:MailMessageText)
  This element will contain the free text administrative message. Nlets recommends the use of <![CDATA[]]> tags to ensure
  that the response does not contain any characters illegal in XML.

  nc:Image
  Optional image tag. This element will contain an image if one is available.

    nc:BinaryBase64Object
    NIEM: A binary encoding of data.

      nc:BinaryCaptureDate
      NIEM:A date on which a binary object is captured or created.

      nc:BinaryDescriptionText
      NIEM:A description of a binary object.

      nc:BinaryFormatID
      NIEM:An identifier for a file format or content type of a binary object.

      nc:BinarySizeValue
      NIEM:A size of a binary object in kilobytes.

      nc:BinaryCategoryText
      NIEM:A kind of object that has been encoded.

  nc:PersonDigitalImage
  Optional image tag. This element will contain an image if one is available.

    nc:BinaryBase64Object
    NIEM: A binary encoding of data.

      nc:BinaryCaptureDate
      NIEM:A date on which a binary object is captured or created.

      nc:BinaryDescriptionText
      NIEM:A description of a binary object.

      nc:BinaryFormatID
      NIEM:An identifier for a file format or content type of a binary object.

      nc:BinarySizeValue
      NIEM:A size of a binary object in kilobytes.

      nc:BinaryCategoryText
      NIEM:A kind of object that has been encoded.

Administrative Message for Law Enforcement Only (AML)

Mail Data (n2:NLETSMailData)
This element will contain all elements specific to this transaction.

  Mail Text (n2:MailMessageText)
  This element will contain the free text administrative message. Nlets recommends the use of <![CDATA[]]> tags to ensure
  that the response does not contain any characters illegal in XML.

  nc:Image
  Optional image tag. This element will contain an image if one is available.

    nc:BinaryBase64Object
    NIEM: A binary encoding of data.

      nc:BinaryCaptureDate
      NIEM:A date on which a binary object is captured or created.

      nc:BinaryDescriptionText
      NIEM:A description of a binary object.

      nc:BinaryFormatID
      NIEM:An identifier for a file format or content type of a binary object.

      nc:BinarySizeValue
      NIEM:A size of a binary object in kilobytes.

      nc:BinaryCategoryText
      NIEM:A kind of object that has been encoded.

  nc:PersonDigitalImage
  Optional image tag. This element will contain an image if one is available.

    nc:BinaryBase64Object
    NIEM: A binary encoding of data.

      nc:BinaryCaptureDate
      NIEM:A date on which a binary object is captured or created.

      nc:BinaryDescriptionText
      NIEM:A description of a binary object.

      nc:BinaryFormatID
      NIEM:An identifier for a file format or content type of a binary object.

      nc:BinarySizeValue
      NIEM:A size of a binary object in kilobytes.

      nc:BinaryCategoryText
      NIEM:A kind of object that has been encoded.

Administrative Message NIEM Examples

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

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>AZNLETS19</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[NLETSTEST1]]>
		</nh2:DocumentControlFieldText>
	</n2:NLETSMessageHeader>
	<n2:NLETSMailData n2:key="AM">
		<n2:MailMessageText>TEST MESSAGE</n2:MailMessageText>
	</n2:NLETSMailData>
</n2:NLETS>

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

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>AZNLETS19</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[NLETSTEST1]]>
		</nh2:DocumentControlFieldText>
		<nh2:MessageReceiveDate>11/27/2019</nh2:MessageReceiveDate>
		<nh2:MessageReceiveTime>00:43</nh2:MessageReceiveTime>
		<nh2:MessageSendDate>11/27/2019</nh2:MessageSendDate>
		<nh2:MessageSendTime>00:43</nh2:MessageSendTime>
		<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
		<nh2:SendMessageNumeric>00086</nh2:SendMessageNumeric>
	</n2:NLETSMessageHeader>
	<n2:NLETSMailData n2:key="AM">
		<n2:MailMessageText>TEST MESSAGE</n2:MailMessageText>
	</n2:NLETSMailData>
</n2:NLETS>

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

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS10</nh2:DestinationORIID>
    <nh2:DestinationORIID>AZNLETS11</nh2:DestinationORIID>
    <nh2:DestinationORIID>AZNLETS12</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[NLETSTEST1]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSMailData n2:key="AM">
    <n2:MailMessageText>TEST MESSAGE</n2:MailMessageText>
  </n2:NLETSMailData>
</n2:NLETS>

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

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>AZNLETS12</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[NLETSTEST1]]>
		</nh2:DocumentControlFieldText>
		<nh2:MessageReceiveDate>11/27/2019</nh2:MessageReceiveDate>
		<nh2:MessageReceiveTime>00:49</nh2:MessageReceiveTime>
		<nh2:MessageSendDate>11/27/2019</nh2:MessageSendDate>
		<nh2:MessageSendTime>00:49</nh2:MessageSendTime>
		<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
		<nh2:SendMessageNumeric>00090</nh2:SendMessageNumeric>
	</n2:NLETSMessageHeader>
	<n2:NLETSMailData n2:key="AM">
		<n2:MailMessageText>(AZNLETS10,AZNLETS11,AZNLETS12)
TEST MESSAGE</n2:MailMessageText>
	</n2:NLETSMailData>
</n2:NLETS>

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

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>IN</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[NLETSTEST1]]>
		</nh2:DocumentControlFieldText>
	</n2:NLETSMessageHeader>
	<n2:NLETSMailData n2:key="AM">
		<n2:MailMessageText>
		* Powered by NLETS

     REQUEST FOR STATEWIDE BROADCAST
     TEST MESSAGE</n2:MailMessageText>
	</n2:NLETSMailData>
</n2:NLETS>

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

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>IN</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[NLETSTEST1]]>
		</nh2:DocumentControlFieldText>
		<nh2:MessageReceiveDate>11/27/2019</nh2:MessageReceiveDate>
		<nh2:MessageReceiveTime>05:03</nh2:MessageReceiveTime>
		<nh2:MessageSendDate>11/27/2019</nh2:MessageSendDate>
		<nh2:MessageSendTime>05:03</nh2:MessageSendTime>
		<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
		<nh2:SendMessageNumeric>00347</nh2:SendMessageNumeric>
	</n2:NLETSMessageHeader>
	<n2:NLETSMailData n2:key="AM">
		<n2:MailMessageText>
  * Powered by NLETS

     REQUEST FOR STATEWIDE BROADCAST
     TEST MESSAGE</n2:MailMessageText>
	</n2:NLETSMailData>
</n2:NLETS>

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

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>A1</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[NLETSTEST1]]>
		</nh2:DocumentControlFieldText>
	</n2:NLETSMessageHeader>
	<n2:NLETSMailData n2:key="AM">
		<n2:MailMessageText>
		* Powered by NLETS

     REQUEST FOR REGIONAL BROADCAST
     TEST MESSAGE</n2:MailMessageText>
	</n2:NLETSMailData>
</n2:NLETS>

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

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>A1</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[NLETSTEST1]]>
		</nh2:DocumentControlFieldText>
		<nh2:MessageReceiveDate>11/27/2019</nh2:MessageReceiveDate>
		<nh2:MessageReceiveTime>05:06</nh2:MessageReceiveTime>
		<nh2:MessageSendDate>11/27/2019</nh2:MessageSendDate>
		<nh2:MessageSendTime>05:06</nh2:MessageSendTime>
		<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
		<nh2:SendMessageNumeric>00348</nh2:SendMessageNumeric>
	</n2:NLETSMessageHeader>
	<n2:NLETSMailData n2:key="AM">
		<n2:MailMessageText>
  * Powered by NLETS

     REQUEST FOR REGIONAL BROADCAST
     TEST MESSAGE</n2:MailMessageText>
	</n2:NLETSMailData>
</n2:NLETS>

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

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>AP</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[NLETSTEST1]]>
		</nh2:DocumentControlFieldText>
	</n2:NLETSMessageHeader>
	<n2:NLETSMailData n2:key="AM">
		<n2:MailMessageText>
		* Powered by NLETS

     REQUEST FOR NATIONAL BROADCAST
     TEST AP MESSAGE</n2:MailMessageText>
	</n2:NLETSMailData>
</n2:NLETS>

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

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>AP</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[NLETSTEST1]]>
		</nh2:DocumentControlFieldText>
		<nh2:MessageReceiveDate>11/27/2019</nh2:MessageReceiveDate>
		<nh2:MessageReceiveTime>05:08</nh2:MessageReceiveTime>
		<nh2:MessageSendDate>11/27/2019</nh2:MessageSendDate>
		<nh2:MessageSendTime>05:08</nh2:MessageSendTime>
		<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
		<nh2:SendMessageNumeric>00349</nh2:SendMessageNumeric>
	</n2:NLETSMessageHeader>
	<n2:NLETSMailData n2:key="AM">
		<n2:MailMessageText>
  * Powered by NLETS

     REQUEST FOR NATIONAL BROADCAST
     TEST AP MESSAGE</n2:MailMessageText>
	</n2:NLETSMailData>
</n2:NLETS>

Top

Legacy (DEPRECATED)

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

Top

Downloads

Download AM Schema

Download AM Stylesheet

Top

Retrieved from "https://wiki.nlets.org/index.php?title=Section_04:_Administrative_Messages&oldid=431"