Section 06: ORION

From Nlets Wiki
Jump to: navigation, search

ORION (TA, TD, TQ, TR & TU)

The objective of the ORION application are:

  • First, it allows a user to find the ORI of an Nlets user agency when only the location (city and state) or Federal agency (name of agency and state) is known.
  • Second, if only the ORI is known it allows a user to gather information (i.e., address, phone, FAX number) on an agency.
  • Primary validation for agency's permissions on the Nlets system.

The functions associated with the ORION file include:

Function Destination ORI to Use
Create/Add Record (TA) OD
Modify/Update Record (TU) OD
Cancel/Delete Record (TD) OD
Query Record (TQ) 2-character code of the location of the agency
(e.g., 50 state codes, CN, NL, DC, PR, or FN)

ORION Validation, Creation and Certification

The objective of the ORION FILE is to assure that only authorized users are using the network and these users are using the network for authorized purposes. Once created, Nlets ensures that it is both accurate and complete.

Validation

Validation of sending ORIs must be accomplished on every transaction passed to Nlets.

Creation

Only NCIC approved ORIs, Nlets generic ORIs and Board approved ORIs may be entered on Nlets. For example, Indiana may not enter an Illinois ORI. Only terminals authorized by the Nlets System Agency (NSA) may add entries to ORION. The "add/cancel" authorization flag can be manipulated only by the NSA ORI. After initial creation, Nlets will print every ORI that is added to the file. They will be checked against NCIC's ORI file to determine whether it is on NCIC. If it is not, it must have been approved by the Board of Directors.

Once approved for access, Nlets controls daily access to the network through comparison to an Nlets-resident table of authorized ORIs called the ORI On-line Directory (ORION). The sender and destination ORIs are checked on every transmission sent through the network. Nlets also uses the ORI in conjunction with ORION to control the types of information sent through the network. It is therefore a critical piece of every transmission over the network.

Nlets divides ORIs into two types: criminal justice and non-criminal justice ORIs.

  • The non-criminal justice agencies are further divided:
  • Those that have an ORI assigned by the FBI
  • Those that have an ORI assigned by Nlets.

Law Enforcement:
  PD - any agency of city government.
  SO - any agency of county government including parishes where apropos.
  SA - any agency employed by a state with statewide jurisdiction.
  LE - used as a catchall for any agency not fitting the above criteria. May be used on inquiry or record creation.
  FE - Federal agency.

Criminal Justice:
  JA - any prosecutor.
  JC - any corrections agency.
  JG - any probation agency.
  JJ - any court agency.
  JF - any Federal non-law enforcement criminal justice agency.
  CJ - will return all defined non-law enforcement criminal justice agencies and should be used as a general type for all
    ORIs ending in B, M, N or Y.

Non-Criminal Justice Organizations or Agencies (i.e., DMV):
  NJ - non-criminal justice agencies.
  (Note: Generally, the second letter of these two character codes is the same one used by NCIC in breaking down their
  ORIs for criminal justice agencies).

When a criminal justice agency performs a service on behalf of a governmental non-criminal justice agency, each agency must have an ORI. In all transactions the ORI of the governmental non-criminal justice agency must be used. If the non-criminal justice agency does not have an ORI and is using Nlets for approved purposes, Nlets staff will assign an Nlets ORI. This is the "S" ORI.

If the non-criminal justice agency contracts with a private firm, there must be an agreement signed by a representative from the non-criminal justice agency, the private contractor and the Nlets representative. This agreement guarantees that the non-criminal justice agency will assure that Nlets policies and procedures are followed by the private contractor.

All law enforcement and criminal justice agencies in the United State and Canada are authorized to access Nlets. There are many non-criminal justice agencies that are authorized to access Nlets. These fall into three groups as described below.

Generic Types of Agencies:

Non-Criminal Justice Governmental Agencies with an FBI ORI
These agencies have been assigned an ORI by the FBI but are not criminal justice agencies.
Example: Department of Motor Vehicles (DMV) within the states.

Non-Criminal Justice Governmental Agencies with an Nlets ORI
These agencies have been assigned an ORI by Nlets but are not criminal justice agencies.
These ORIs may be identified by an "s" in the 9th character.
Example: A child support enforcement agency within a state.

Private Not-for-Profit Organizations with an Nlets or NCIC ORI
These organizations may have an ORI assigned by the FBI or Nlets. Through their membership
they provide a service to the law enforcement or criminal justice community. These Nlets ORIs
may be identified by an "S" in the 9th character.
Example: An organization such as the National Insurance Crime Bureau (NICB).

Certification

It is the responsibility of the Nlets representative to ensure that all ORION entries owned by that user (state, federal, international or associate) have been certified as up to date and accurate at least every two years. These dates will coincide with NCIC's validation of their ORI file.

Every two years media containing all ORIs will be made available to each Nlets representative. The Nlets representative will certify that all records are valid, accurate and up to date. He or she will then sign a certification document attesting to the validity of each record owned by the member. Nlets staff will cause the certification date in each record to be updated to reflect the successful completion of the certification procedure. Users will have 90 days to certify their ORIs.

Following the 90 day certification period, Nlets will notify members who have not certified their ORI file that their ORIs will be deactivated in thirty days unless certified within that time period. A return receipt for the second notice will be requested. If after thirty days from the time the member has received the second notice, the ORIs still have not been certified, the ORIs will be deactivated.

Create Your File

The ORION application has been developed to provide the user with a variety of ways to access information. In order to take full advantage of this design the user must have a clear understanding of how the file is created. Each user creates his/her own file. The usefulness and flexibility of a file is determined by the record input.

It is the responsibility of the state representative to enter and maintain ORIs for all state, local, Federal and other agencies that have a terminal on their state system that can access Nlets.

The Federal member representative is responsible for entering ORI records for the appropriate state sub-files for all terminals for which they provide service and for entering any of their ORIs that they deem appropriate into the corresponding state sub-files.

Entry of a New ORI (TA)

The criteria for entry of ORIs on ORION is as follows:

  • Any agency whose assigned ORI accesses Nlets either directly, or by agreement through another agency, shall have an entry on ORION.
  • If there are multiple terminals within a law enforcement agency that have access to Nlets, separate entries are required when the first 7 characters of the ORI are the same and at least one other data field in the ORION record (e.g., phone #, address, etc.) differs.
  • For criminal justice agencies, if multiple ORIS are assigned to the same agency, an entry is required for each ORI that accesses Nlets.
ORI Entry Requirements

All fields except PH2, ATH, PRI, FAX. CTO, AOC, ACT and REM are required, and are checked for data presence. The ATH field is a combined authorization field that combines the old CHR field with additional authorization flags.

Leading zeros in the optional fields (PH2, FAX, REM) cause the fields to be cleared and not displayed. Other field edits are as described. Federal ORIs receive special processing.

The flags represent methods of controlling maintenance of the file.

Flag Tag Description
CTO flag

Originally set by Nlets upon creation of the file, defaults to "N" on all other
records.
Allows the flagged ORI to set all other flags within their ORION file.

AOC flag Authorizes an ORI to add or cancel a record and defaults to "N".
Can only be set by an ORI that has the CTO flag set to "Y".
ACT flag

Denotes the status of an ORI; either active or inactive.
Inquiry upon this ORI results in a response with the record information but the
ORI will not be able to send or receive messages over Nlets.
Can only be set by an ORI that has the CTO flag set to "Y" (control terminal
agency).

ATH flag

The ATH field is the replacement for the CHR field and controls access in
general, including CHR (but not including ORION maintenance, which is still
controlled by the CTO and AOC flags).
Four categories of access are defined:

  • A = Permission to send administrative messages
  • C = Permission to send criminal history message types (IQ, FQ & AQ)
  • D = Permission to send DMV related message types (DQ,RQ & KQ)
  • Z = Permission to send other Nlets message types


The Nlets table of valid message types associates one of the above codes
with each message type (except ORION maintenance), and allows the user
access to the message type if the user's ORI has the appropriate code.

The priority (<j:AgencyBaselinePriorityValue> or "PRI") field defines a baseline priority for low-priority ORIs. Nlets sends all messages with one of 12 priorities, based on the message type and designates 1-12, with 1 the highest and 12 the lowest. The baseline priority specifies that messages to this ORI be assigned at least the specified baseline.

  • Messages with lower priority number (i.e., that are higher priority) will be set to this baseline number.
  • Messages with higher priority numbers (i.e., that have lower priority) will be left unchanged.

For example, a message typically sent at priority 3 would be sent at reduced priority 10 if the ORI has a baseline priority of 10.

If the baseline priority field is not specified, Nlets defaults it to 10 for ORIs ending in "S", and to 0 (use standard priorities) for all other ORIs.

The sender ORI must be valid for the line on which the transaction was received. In addition, the data ORI, which is the ORI to be entered into the file, also must be valid for the line. (i.e., AZ0120023 (with AOC/ set to Y) can add/update an entry in the Arizona Orion File provided that AZ012003 is in the Arizona Orion File and Nlets receives the message from the Arizona Line.)

Finally, a check is made to ensure there is no existing ORI record with the same state code, location and ORI.

If all checks are successful, the line name that the transaction was received on is stored as the owner of the ORI record and the current date is stored as the creation date.

The sub-file that the record will be inserted into is derived from the first two characters of the data ORI. If the first two characters are a state code, "DC", or "PR", the record is entered into that sub-file. All other records are entered into the foreign (or miscellaneous) sub-file.

In the simplest case, a user will enter a single record for each agency, giving the agency's location, agency name, ORI and all other data elements.

The only optional data elements are as follows:

  • Alternate phone number
  • FAX phone number
  • Alternate FAX number
  • Remarks field

Additional records may be entered for the same location with different ORIs (i.e., PD, Sheriff's Office and State Police offices in the same location).

Similarly, additional records may be added for the same ORI at different locations (i.e., an agency may serve several locations). This will enable a user to locate, for example, a Sheriff's Office when only the city name is known.

No State or Federal member may enter an ORI that it would not be allowed to use as a sending ORI.

Only ORIs that are assigned by NCIC or those that are approved by Nlets will be allowed in the ORION file.

Control Terminal Functions

With the addition of ORI validation and attending control flags, the NSA assumes additional responsibility for the maintenance and control of its portion of the ORION file. The NSA, or any ORI designated by the NSA, will have the ability to modify authorization flags or perform any maintenance on the member's file.

For example, only NSAs can:

  • Designate the ORIs from their user population who can add/cancel records, activate or deactivate ORIs.
  • Designate who is authorized to send/receive criminal history information.

Although it is recognized that NSAs may authorize other ORIs to add/cancel records, by turning on the add/cancel flag (AOC); it is strongly suggested that the NSA retain sole authority to:

  • Modify the status of an ORI (active or inactive).
  • Modify the authorization for an ORI to send/receive criminal history information.

Regardless of the delegation of authority for maintenance of the ORION file, Nlets will always consider the NSA from each member state or Federal agency as the responsible agency regarding the accuracy and completeness of their ORI file.

ORI Record Definition

There are several fields that are created by the ORION system to provide information on the record. This information is supplied by Nlets and will show up on the response but is not put in by the user when adding a record. It includes the following:

Entry Explanation
Record Owner Name of line that record was received from initially; update is restricted
to this line, and record will be included in file listing for this line only.
Creation Date Date ORI record was added to the ORION file.
Update Date Date ORI record was most recently updated.
Certification Date Date ORI record was last certified.

Federal ORI Entry

Special processing is done on entry of Federal ORIs. If the ORI being added is a Federal agency (as determined by the following table), the system will insert a three character Federal code, followed by a dash, as the first four characters of the location field (<j:LocationName> or LOC). The code to be inserted for each type of Federal ORI is defined below.

Federal Agency (LOC) 3rd, 4th, 5th
Characters in ORI
3 Characters In
Location (LOC) Field
FBI FBI FBI
Drug Enforcement Agency DEA DEA
U.S. Customs USC USC
Alcohol, Tobacco, and Firearms ATF ATF
Immigration and Naturalization Service INS INS
Department of Justice DOJ DOJ
Secret Service SS1, SS2 SS3, SS4 SSA
Postal Inspection Service PO0 PIS
Naval Investigative Service NIS NIS
Coast Guard CGO MSC
Veterans Administration VA0 MSC
Food and Drug Administration FDA MSC
Health & Human Services HHS MSC
Department of Commerce DCO MSC
Dulles Airport DUL MSC
Washington National Airport WNS MSC
Capital Police CAP MSC
U.S. Air Force AFO MSC
Air Force Office of Special Investigation OSI OSI
U.S. Navy USN MSC
U.S. Army U.S. USA U.S. USA
U.S. Marshals USM USM
U.S. Marine Corps CGH, MCD, MCO MSC
Internal Revenue Service IRS IRS
Federal Aviation Administration FAA FAA
Federal Protective Service FPS MSC
Department of State DOS DOS
Department of Interior DOI DOI
Defense Investigative Service DIS MSC
Bureau of Indian Affairs BIA BIA
Department of Agriculture DOA MSC
Department of Labor DOL MSC
Department of Defense DOD MSC
Department of Treasury TRE MSC

The system will also verify that agency type code "FE" was specified if the ORI is found in the table for Federal law enforcement agencies. (No special agency type edit will be done on non-law enforcement ORIs.)

Foreign (Miscellaneous) ORI File

A "foreign" sub-file (member code "FN") will be provided for entering ORIs that are not located in a state, D.C., Puerto Rico or Canada. Normal authorization checks will be done.

For example, "JANIS0400" would be a valid ORI for the Yokohama, Japan office of the Naval Investigative Service, but the first two characters do not match any member code. Therefore, the record is entered in the "FN" sub-file. Should a Federal agency use a general code of "US", this also would be placed in the file.

For example, the Naval Investigative Service Headquarters is in Suitland, Maryland, but its ORI is USNIS0000. Since the first two characters are not a state, D.C., Puerto Rico, or Canada, it would go in the "FN" catch-all file. To inquire on it you would use a destination of "FN" and "FED/NIS". You would receive all NIS ORIs in the foreign file. By adding more information to the "NIS" (e.g., NIS - SUITLAND) you would retrieve only the Suitland record in the "FN" file.

Entry Authorization Checks

Record entry authorization requires that the ORI being entered is valid for the line on which the transaction was received. In addition the ORI that is entering the record must be authorized, as determined by the AOC flag, to enter records. When entering a record all flags are set at the default. Only a NSA, as determined by the CTO flag is authorized to modify the flag fields.

Record update and delete authorization requires that the transaction be received on the same line that originally entered the ORI record.

Modify an Existing ORI Record (TU)

The ORI and location are both required in order to modify a record. Only records matching both the location and ORI will be modified.

The sender's line code is compared to the record owner's line code to verify the sender is authorized to update the ORI record.

At least one additional field must be specified, along with the new data to be stored in that field. Any fields given, including agency type, must pass the specific field edits.

Note: It is possible to clear out a REM field by sending a single "0". It is not possible to clear
out any other field, but they can be changed to a value of a single "-" or "0" depending on the
field that is being updated.

Note: The state code, location and ORI cannot be changed through an update command.
Changing these items will require deletion of the old record and entry of a new ORI record
with correct state code, location and ORI.
The flag fields may only be modified by authorized ORIs.

Delete an Existing ORI Record (TD)

Note: Only an ORI that has been authorized to add or cancel an ORION record may
submit an <n:MessageKeyCode>TD</n:MessageKeyCode> (XML) or "TD" (Legacy).
This authorization is provided by the NSA through setting of the AOC flag in the
sender's ORION record.

The location and ORI are required and must match the location and ORI fields in the record to be deleted. The sender's line code is compared to the record owner's line code to verify the sender is authorized to delete the ORI record.

If all checks are successful, the record is deleted.

Note: If multiple locations (and thus, records) occur for a single ORI, deletion of the ORI
requires deletion of the records individually.

For example, Maricopa County SO serves Phoenix, Mesa, and Scottsdale. Therefore, three records for the agency's ORI may have been entered that specified different locations for the ORI. Deleting the ORI would then require three separate delete transactions.

Access the ORION File (TQ)

There are three types of inquiries that one may use to access the ORION file. They are described in the table below.

Inquiry Response
Retrieve specific records by ORI.

The response will be the complete text of all
records on file for the ORI, unless there are more
than three.
If there are more than three, summary records will
be returned.

A file search by location, limited if
desired to a particular agency type.

The response to an inquiry by location will usually
comprise summaries of all matching records.
However, if there are three or fewer matches,
complete records for the matches are returned.

A file search by Federal agency ID,
limited if desired, to a particular location.

The response to an inquiry by Federal agency ID
will usually comprise summaries of all matching
records.
However, if there are three or fewer matches,
complete records for the matches are returned.

Note: The response will include a designation of the owner or line mnemonic of the record at
the bottom of the record. This indicates the line that actually entered the record. Only this
line can modify or cancel this record.

Retrieve a Record by ORI

Note: If an ORI is submitted and an exact match is not found, a search of eight and
seven characters will be made. This may result in some voluminous responses but it will
provide the inquirer with ORIs of the agency if not the exact terminal.

The complete record response includes the following:

ORI
location
agency name
type of agency
address
city
zip code
phone
alternate phone number, if present
hours of service
authorization flag
baseline priority

FAX phone number (sender pays), if present
alternate FAX phone number, if present
NSA flag
add/cancel authorization flag
active/inactive flag
record owner
creation date
update date
certification date
remarks

Retrieve a Record by Location

  • The location is required and the type is optional.
  • All records in the specified member subfile that match the specified location and agency type, as described below, are returned to the sending ORI.
  • The type field is optional, and if not specified defaults to search all law enforcement ORIs (types PD, SO, SA, LE, FE, RP) since the vast majority of inquiries will be for law enforcement ORIs.
  • Federal agency records are not retrieved.
  • If a criminal justice agency (other than law enforcement) or a non-criminal justice agency (such as NICB) is being sought, the appropriate type code should be used. If a type code of "CJ" is used all criminal justice agencies (other than law enforcement and Federal agencies) will be returned as well as non-criminal justice agencies. The non-criminal justice agencies will clearly be identified in the response as a non-criminal justice agency.

Search Method

The requirements for a search are as follows:

  • At least 2 characters are required.
  • The complete location need not be specified.
  • The system searches for exact matches of the characters provided.

For example, if the user does not know how to spell Tucson (or is it Tuscon?), the user may inquire on <j:OrganizationLocation>TU</j:OrganizationLocation> or LOC/TU and the system will retrieve all entries that begin with "TU". The system will search from 2 to 7 characters with this method. It is intended to eliminate the need for a soundexed system and yet still provide assistance with spelling difficulties.

Entry Return Examples

If seven or fewer
characters are given,
the system tries first to
find records whose
entire location field
matches the specified
characters.

If the location matches
a location on file, only
that record will be
returned.
If no records match
exactly, then the
system searches for
records that begin with
the specified
characters.

A query on <j:OrganizationLocation>ROCK</j:Organization
Location> or LOC/ROCK would produce only the complete
record for the police department in Rock, Illinois. A query
<j:OrganizationLocation>ROC or LOC/ROC would
produce summary records for ROCK, ROCK FALLS,
ROCKFORD, AND ROCK ISLAND

If the user supplies
more than 7 characters,
only the first seven will
be compared unless an
exact match can be
made of the entire
location field in the
inquiry with one or more
location fields in the file
records.

Only the exact
matching records will
be returned regardless
of the number of
characters searched.

If one inquires on Kalamazoo and there are records with
"Kalamazoo" and "Kalamazo" only the exact matching
record will be returned.
If one inquires on "Kalamazu" both records would be
returned since there was no exact match.

If the user specifies only
two location characters,
and no matches are
found.

A "no record" message
is returned.
 

If more than two
characters are given
and no records match all
the characters.

The system will delete
the user's last specified
character and try again
for one or more
matches.
This process is
repeated until matches
are found, or until the
system can find no
matches on even the
first two characters.
The response will
indicate that an
extended search was
performed.

If the user specified "TUCSON" as the location, the location
will be shortened by one character to TUCSO, then TUCS,
TUC and finally TU, and, as above, the system will return all
locations beginning with "TU".

Response to Inquiry (TR)
Matching Records Nlets Returns
If there are three or fewer
matching records:
The complete content of all matching records is returned.
If there are four or more matches: A summary of each matching record is returned.
  • Should the inquirer receive multiple summary records, a second inquiry can be made on the specific ORI in order to retrieve the complete ORI record.
  • If the user still receives only summary data, an inquiry with both ORI and location must be submitted to narrow the search.
  • No more than 100 hits will be returned on a single query. If this occurs, the user must narrow the search by providing more information in the location or type field.
  • The record summary is designed to fit on a Legacy 72-character line and includes the following:
    • Agency name
    • Location
    • ORI
    • Indicates hours of service
    • CHRI authorization flag
    • Indicates if the record is for a non-criminal justice agency
    • Indicates whether the agency has a FAX # in their record

The legend for code interpretation follows:

For Sending Address Nlets Response
Positive ORION responses xxORION00

The xx = 2 character state code
specifies the subfile from which the
records were retrieved.

Negative responses
indicating no records were
found

xxORIONN0

A "Not Found" message suggesting
that the inquirer send an
administrative message so that the
Nlets representative can provide
assistance.

  • For the foreign (or miscellaneous) subfile, "FN", the user should route the administrative message to the related Federal agency 2-character code or 9-character address.
  • Nlets will extract negative responses from its log tapes periodically and supply them to the members for identification of ORI records that should be added. In this way states can locate common misspellings or add entries to the file that may have inadvertently been omitted.

Retrieve a Federal Agency Record

To search a Federal agency's ORI record, specify a Federal agency 3-character code with <FederalAgency> or "FED" prefix rather than <j:LocationName> or "LOC" prefix. The destination code indicates the state where the Federal agency resides.

To limit the search to a particular location, the agency code is followed by a dash and one or more characters of the location.

Inquiry Response
A file search by Federal agency
3-character code.
  • All records in the specified state sub file for the
    agency, limited to those matching the location,
    if any, are returned to the sending ORI.
  • If there are three or fewer matching records, the
    complete content of all matching records is
    returned. However, if there are four or more
    matches, a summary of each matching record
    is returned. The formats of
    the two types of responses are provided.
  • No more than 100 hits will be returned on a
    single query. If this occurs, the user must
    narrow the search by providing more
    information.

Federal agencies will be handled differently since, for example, the user might be looking for the closest Federal office but may not know where the office is actually located. Inquiring by Federal agency ID returns all the Federal agency's offices within a state.

  • For example, if a user needs to contact the closest FBI office to Kalamazoo, Michigan he will send the state code "MI" and the agency name "FBI". The system will return all FBI offices in Michigan and the user will select the one he prefers.
  • To narrow the search, modify the request. Adding the letters DE after FBI, (FBI/DE) would result in the search being limited to only FBI offices in Michigan that are at a location with a name beginning with the letters "DE".

There are several Federal agencies with designated ORION codes of "MSC" who have only a few terminals on Nlets. They are all placed in a single miscellaneous sub file.

FNORIHELP

By sending an administrative message ("AM") message to FNORIHELP the user will receive a list of the Federal agencies, their 3 character codes from their ORIs and the associated ORION Federal code used to search by FED/.

Top

GJXDM (DEPRECATED)

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

Top

NIEM

ORION NIEM Specifications

This section describes the NIEM format to enter, modify, delete and access ORION records and provides examples.

The sender's line code is compared to the record owner's line code to verify the sender is authorized to update the ORI record.

At least one additional field must be specified, along with the new data to be stored in that field. Any fields given, including agency type, must pass the specific field edits, which are described above.

If all checks are successful, the current date is stored as the date of last update, and the modified record is written back to the ORI file.

There are four optional fields that may be blanked out. You may blank out these fields by filling them with zeros. These are: alternate phone number, fax number, alternate fax number and remarks.

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: ORION Entry (TA), ORION Modify (TU), ORION Delete (TD), Orion Query by ORI (TQ), Orion Query by Location (TQ), Orion Query by Federal (TQ) & Orion Query for Representative (TQ).

Query Formats

ORION Entry (TA)

n2:NLETSUpdateData

  n2:Agency
  This element will contain information about the agency being added to ORION.

    n2:OrganizationActiveCode
    Designates whether the ORI being entered is active or inactive; may only be set by a terminal with control terminal
    capabilities.
    Designates whether the ORI being entered is active or inactive; may only be set by a terminal with control terminal
    capabilities; must be A or I.

    j:OrganizationAugmentation
    Additional information about an organization.

      j:OrganizationORIIdentification
      A unique identifier assigned to a justice-related organization by the federal government.

        nc:IdentificationID
        A value that identifies something.
        This element will contain the ORI of the agency being added.

      j:AgencyAddCancelIndicator
      Must be Y or N (defaults to N).
      Designates whether or not the terminal(s) being entered is/are authorized to add or cancel an ORION record.

      j:AgencyBaselinePriorityValue
      Values must be 0-12.
      Contains a value indicating the Baseline Priority, 0-12:
      0 = use system default priority.
      1-12 = use baseline as minimum priority.

      j:AgencyControlTerminalIndicator
      Must be Y or N.
      Contains a Boolean value indicating whether or not this agency is a control terminal.

      j:AgencyServiceHoursCode
      A availability of an agency.
      The hours of service of the terminal being entered. Must be one of the following:
      A = 24 hr service w/terminal.
      B = not 24 hr service w/terminal.
      C = 24 hr service, w/o terminal.
      D = not 24 hr service, w/o terminal.

      j:AgencyAuthorizationCode
      An agency's access category to data.
      Indicates levels of authorization for the ORI being entered. Value(s) should be added in subelements
      n:OrganizationAuthorizationIndicator. One or more of the following:
      A = User is authorized to send/receive administrative messages.
      C = User is authorized to send/receive CHRI.
      D = User is authorized to receive DMV data.
      Z = User is authorized to other Nlets messages.

      j:OrganizationCategoryNLETSCode
      A functional kind of an organization.
      Must be one of the valid type codes; law enforcement, criminal justice, and non-criminal justice.

    nc:OrganizationLocation
    A location of an organization.
    This element will contain all information relating to the particular location of this agency.

      nc:LocationAddress
      A geophysical location described by postal information.

        nc:StructuredAddress
        An address.

          nc:LocationStreet
          A road, thoroughfare or highway.

            nc:StreetFullText
            A complete reference for a street.
            This conditional element contains the street address.

        nc:LocationCityName
        A name of a city or town.
        This conditional element contains the city.

        nc:LocationPostalCode
        An identifier of a post office-assigned zone for an address.
        This conditional element contains the postal code, or zip code.

      nc:LocationName
      A name of a location.
      City or County; for Federal agency, user has only 16 characters since program will supply the Federal identifier and the
      dash. Alpha/Numeric & spaces except dash (-). The dash will be ignored on inquiries.

    nc:OrganizationName
    A name of an organization.
    This element will contain the name of the agency.

    nc:OrganizationPrimaryContactInformation
    A preferred means of contacting an organization.
    Contact information for the location of this agency.

      nc:ContactTelephoneNumber
      A telephone number for a telecommunication device by which a person or organization may be contacted.

        nc:FullTelephoneNumber
        A full telephone number.

          nc:TelephoneNumberFullID
          A complete telephone number.
          Telephone number for this location of the agency. The value "Primary" or "Secondary" must be contained in the
          sibling element <nc:ContactInformationDescriptionText>.

        nc:ContactFaxNumber
        A telephone number for a facsimile device by which a person or organization may be contacted.

          nc:FullTelephoneNumber
          A full telephone number.

            nc:TelephoneNumberFullID
            A complete telephone number.
            Primary fax number for this location of the agency.

  n2:MiscellaneousUpdateText
  Optional Miscellaneous Field. Free text format.
  Remarks about organization.

ORION Modify (TU)

n2:NLETSUpdateData

  n2:Agency
  This element will contain information about the agency being added to ORION.

    n2:OrganizationActiveCode
    Designates whether the ORI being entered is active or inactive; may only be set by a terminal with control terminal
    capabilities.
    Designates whether the ORI being entered is active or inactive; may only be set by a terminal with control terminal
    capabilities; must be A or I.

    j:OrganizationAugmentation
    Additional information about an organization.

      j:OrganizationORIIdentification
      A unique identifier assigned to a justice-related organization by the federal government.

        nc:IdentificationID
        A value that identifies something.
        This element will contain the ORI of the agency being added.

      j:AgencyAddCancelIndicator
      Must be Y or N (defaults to N).
      Designates whether or not the terminal(s) being entered is/are authorized to add or cancel an ORION record.

      j:AgencyBaselinePriorityValue
      Values must be 0-12.
      Contains a value indicating the Baseline Priority, 0-12:
      0 = use system default priority.
      1-12 = use baseline as minimum priority.

      j:AgencyControlTerminalIndicator
      Must be Y or N.
      Contains a Boolean value indicating whether or not this agency is a control terminal.

      j:AgencyServiceHoursCode
      A availability of an agency.
      The hours of service of the terminal being entered. Must be one of the following:
      A = 24 hr service w/terminal.
      B = not 24 hr service w/terminal.
      C = 24 hr service, w/o terminal.
      D = not 24 hr service, w/o terminal.

      j:AgencyAuthorizationCode
      An agency's access category to data.
      Indicates levels of authorization for the ORI being entered. Value(s) should be added in subelements
      n:OrganizationAuthorizationIndicator. One or more of the following:
      A = User is authorized to send/receive administrative messages.
      C = User is authorized to send/receive CHRI.
      D = User is authorized to receive DMV data.
      Z = User is authorized to other Nlets messages.

      j:OrganizationCategoryNLETSCode
      A functional kind of an organization.
      Must be one of the valid type codes; law enforcement, criminal justice, and non-criminal justice.

    nc:OrganizationLocation
    A location of an organization.
    This element will contain all information relating to the particular location of this agency.

      nc:LocationAddress
      A geophysical location described by postal information.

        nc:StructuredAddress
        An address.

          nc:LocationStreet
          A road, thoroughfare or highway.

            nc:StreetFullText
            A complete reference for a street.
            This conditional element contains the street address.

        nc:LocationCityName
        A name of a city or town.
        This conditional element contains the city.

        nc:LocationPostalCode
        An identifier of a post office-assigned zone for an address.
        This conditional element contains the postal code, or zip code.

      nc:LocationName
      A name of a location.
      City or County; for Federal agency, user has only 16 characters since program will supply the Federal identifier and the
      dash. Alpha/Numeric & spaces except dash (-). The dash will be ignored on inquiries.

    nc:OrganizationName
    A name of an organization.
    This element will contain the name of the agency.

    nc:OrganizationPrimaryContactInformation
    A preferred means of contacting an organization.
    Contact information for the location of this agency.

      nc:ContactTelephoneNumber
      A telephone number for a telecommunication device by which a person or organization may be contacted.

        nc:FullTelephoneNumber
        A full telephone number.

          nc:TelephoneNumberFullID
          A complete telephone number.
          Telephone number for this location of the agency. The value "Primary" or "Secondary" must be contained in the
          sibling element <nc:ContactInformationDescriptionText>.

        nc:ContactFaxNumber
        A telephone number for a facsimile device by which a person or organization may be contacted. The actual telephone
        number should be placed in nc:FullTelephoneNumber/nc:TelephoneNumberFullID.

  n2:MiscellaneousUpdateText
  Optional Miscellaneous Field. Free text format.
  Remarks about organization.

ORION Delete (TD)

n2:NLETSUpdateData

  n2:Agency
  This element will contain information about the agency being added to ORION.

    j:OrganizationAugmentation
    Additional information about an organization.

      j:OrganizationORIIdentification
      A unique identifier assigned to a justice-related organization by the federal government.
      This element will contain information about the agency being deleted from ORION.

        nc:IdentificationID
        A value that identifies something.
        This element will contain the ORI of the agency being modified.

    nc:OrganizationLocation
    A location of an organization.

      nc:LocationName
      A name of a location.
      City or County; for Federal agency, user has only 16 characters since program will supply the Federal identifier and the
      dash. Alpha/Numeric & spaces except dash (-). The dash will be ignored on inquiries. This element, along with ORI is
      an identifier of the record. If you wish to modify the location name itself you must first delete the ORI then re-enter it.

ORION Query by ORI (TQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:Agency
  This element will contain information about the agency being added to ORION.

    j:OrganizationAugmentation
    Additional information about an organization.

      j:OrganizationORIIdentification
      A unique identifier assigned to a justice-related organization by the federal government.

        nc:IdentificationID
        A value that identifies something.
        This element will contain the ORI of the agency.

    nc:OrganizationLocation
    A location of an organization.

      nc:LocationName
      A name of a location.
      City or County; for Federal agency, user has only 16 characters since program will supply the Federal identifier and the
      dash. Alpha/Numeric & spaces except dash (-). The dash will be ignored on inquiries.

ORION Query by Location (TQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:Agency
  This element will contain information about the agency being added to ORION.

    nc:OrganizationLocation
    A location of an organization.

      nc:LocationName
      A name of a location.
      City or County; for Federal agency, user has only 16 characters since program will supply the Federal identifier and the
      dash. Alpha/Numeric & spaces except dash (-). The dash will be ignored on inquiries.

ORION Query by Federal (TQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:Agency
  This element will contain information about the agency being added to ORION.

    nc:OrganizationAbbreviationText
    An abbreviation, acronym, or code for an organization name.
    This element will contain the Federal agency type. May append a location to this field to narrow the search
    (i.e., FBI-DETROIT).

Response Formats

ORION Response (TR)

n2:NLETSResponseData
This element will contain all elements specific to this transaction.

  n2:OrionRecord
  This element will contain a single recored result returned by a TQ

    n2:OwnerIdentification
    Ownership code associated with the ORION Agency

      nc:IdentificationID
      The Two Character Ownership code

    n2:CreateDate
    The date the ORI was first added to the ORION database

    n2:UpdateDate
    The date the ORI was last updated the ORION database

    n2:CertifiedDate
    The date the ORI was certified as a Valid NCIC ORI by the Owner Nlets Rep

    n2:Agency
    This element will contain information about the ORION Agency.

     j:OrganizationCategoryNLETSCode
     A functional kind of an organization.
     Must be one of the valid type codes; law enforcement, criminal justice, and non-criminal justice.

     nc:OrganizationLocation
     This element will contain information about the ORION Agency Location and Contact Information.

      nc:LocationName
      A name of a location.
      City or County; Federal Agency will be prepended with a XXX- where XXX is a three character Federal identifier

      nc:LocationAddress
      A location of an organization.
      This element will contain all information relating to the particular location of this agency.

       nc:LocationAddress
       A geophysical location described by postal information.

        nc:StructuredAddress
        An address.

         nc:LocationStreet
         A road, thoroughfare or highway.

          nc:StreetFullText
          A complete reference for a street.
          This conditional element contains the street address.

         nc:LocationCityName
         A name of a city or town.
         This conditional element contains the city.

         nc:LocationPostalCode
         An identifier of a post office-assigned zone for an address.
         This conditional element contains the postal code, or zip code.

       nc:LocationContactInformation
       Details about contact information for a location.

        nc:ContactTelephoneNumber
        The Primary telephone number for a telecommunication device by which a person or organization may be contacted.

         nc:FullTelephoneNumber
         A full telephone number.

          nc:TelephoneNumberFullID
          A complete telephone number

        nc:ContactFaxNumber
        The Primary telephone number for a facsimile device by which a person or organization may be contacted.

         nc:FullTelephoneNumber
         A full telephone number.

          nc:TelephoneNumberFullID
          A complete telephone number

        nc:ContactSecondaryTelephoneNumber
        The Secondary telephone number for a telecommunication device by which a person or organization may be contacted.

         nc:FullTelephoneNumber
         A full telephone number.

          nc:TelephoneNumberFullID
          A complete telephone number

        nc:ContactSecondaryFaxNumber
        The Secondary telephone number for a facsimile device by which a person or organization may be contacted.

         nc:FullTelephoneNumber
         A full telephone number.

          nc:TelephoneNumberFullID
          A complete telephone number

     nc:OrganizationName
     A name of an organization.
     This element will contain the name of the agency

     j:OrganizationAugmentation
     Additional information about an organization.

      j:OrganizationORIIdentification
      A unique identifier assigned to a justice-related organization by the federal government.

       nc:IdentificationID
       A value that identifies something.
       This element will contain the ORI of the agency returned.

      j:AgencyAddCancelIndicator
      True if an agency is authorized to add or cancel a record; false otherwise.
      Designates whether or not the terminal(s) being entered is/are authorized to add or cancel an ORION record.

      j:AgencyBaselinePriorityValue
      Values will be 0-12.
      Contains a value indicating the Baseline Priority, 0-12:
      0 = use system default priority
      1-12 = use baseline as minimum priority.

      j:AgencyCHRIAuthorizedIndicator
      True if an agency is authorized to access criminal history information; false otherwise.
      Indicates whether or not the ORI being entered is authorized to receive criminal history messages.
      Will be one of the following:
      True = User is authorized to receive CHRI via Nlets.
      False = user is not authorized to receive CHRI via Nlets.

      j:AgencyControlTerminalIndicator
      True if an agency is a control terminal; false otherwise.
      Contains a Boolean value indicating whether or not this agency is a control terminal.

      j:AgencyServiceHoursCode
      A availability of an agency
      The hours of service of the terminal being entered. Will be one of the following:
      A = 24 hr service w/terminal.
      B = not 24 hr service w/terminal.
      C = 24 hr service, w/o terminal.
      D = not 24 hr service, w/o terminal.

      j:AgencyAuthorizationCode
      An agency's access category to data.
      Indicates levels of authorization for the ORI being entered. Value(s) should be added in subelements
      n:OrganizationAuthorizationIndicator. One or more of the following:
      A = User is authorized to send/receive administrative messages.
      C = User is authorized to send/receive CHRI.
      D = User is authorized to receive DMV data.
      Z = User is authorized to other Nlets messages.

     j:OrganizationActiveCode
     Designates whether the ORI being entered is active or inactive.
     Will be A or I.

    n2:MiscellaneousUpdateText
    Optional Miscellaneous Field. Free text format
    Remarks about organization.

ORION NIEM Examples

Example 1: Message to create a new ORI.

<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:scr="http://niem.gov/niem/domains/screening/2.1" xmlns:j="http://niem.gov/niem/domains/jxdm/4.1">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>TA</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS45</nh2:OriginatingORIID>
    <nh2:DestinationORIID>OD</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[26CC0001BD]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSUpdateData n2:key="TA">
    <n2:Agency>
      <j:OrganizationCategoryNLETSCode>PD</j:OrganizationCategoryNLETSCode>
      <nc:OrganizationLocation>
        <nc:LocationAddress>
          <nc:StructuredAddress>
            <nc:LocationStreet>
              <nc:StreetFullText>123 TEST ST</nc:StreetFullText>
            </nc:LocationStreet>
            <nc:LocationCityName>ST PAUL</nc:LocationCityName>
            <nc:LocationPostalCode>20000</nc:LocationPostalCode>
          </nc:StructuredAddress>
        </nc:LocationAddress>
        <nc:LocationName>PHOENIX</nc:LocationName>
      </nc:OrganizationLocation>
      <nc:OrganizationName>TEST AGY</nc:OrganizationName>
      <nc:OrganizationPrimaryContactInformation>
        <nc:ContactTelephoneNumber>
          <nc:FullTelephoneNumber>
            <nc:TelephoneNumberFullID>7777777777</nc:TelephoneNumberFullID>
          </nc:FullTelephoneNumber>
        </nc:ContactTelephoneNumber>
        <nc:ContactInformationDescriptionText>Primary</nc:ContactInformationDescriptionText>
      </nc:OrganizationPrimaryContactInformation>
      <j:OrganizationAugmentation>
        <j:OrganizationORIIdentification>
          <nc:IdentificationID>AZNLETS55</nc:IdentificationID>
        </j:OrganizationORIIdentification>
        <j:AgencyAddCancelIndicator>true</j:AgencyAddCancelIndicator>
        <j:AgencyBaselinePriorityValue>0</j:AgencyBaselinePriorityValue>
        <j:AgencyControlTerminalIndicator>true</j:AgencyControlTerminalIndicator>
        <j:AgencyServiceHoursCode>A</j:AgencyServiceHoursCode>
        <j:AgencyAuthorizationCode>A</j:AgencyAuthorizationCode>
      </j:OrganizationAugmentation>
      <n2:OrganizationActiveCode>A</n2:OrganizationActiveCode>
    </n2:Agency>
    <n2:MiscellaneousUpdateText>TESTING</n2:MiscellaneousUpdateText>
  </n2:NLETSUpdateData>
</n2:NLETS>

Example 2: Response from ORION after creating a new ORI.

<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>TR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>ODORION00</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS45</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[26CC0001BD]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>06/17/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>08:32</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>06/17/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>08:32</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00132</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData>
  <n2:ResponseText>
      TR:PYORION00:RECORD ADDED FOR ORI/AZNLETS55</n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 3: Message to update an existing ORI.

<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:scr="http://niem.gov/niem/domains/screening/2.1" xmlns:j="http://niem.gov/niem/domains/jxdm/4.1">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>TU</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS45</nh2:OriginatingORIID>
    <nh2:DestinationORIID>OD</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText>MR01714171</nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSUpdateData n2:key="TU">
    <n2:Agency>
      <nc:OrganizationLocation>
        <nc:LocationAddress>
          <nc:StructuredAddress>
            <nc:LocationStreet/>
          </nc:StructuredAddress>
        </nc:LocationAddress>
        <nc:LocationName>PHOENIX</nc:LocationName>
      </nc:OrganizationLocation>
      <j:OrganizationAugmentation>
        <j:OrganizationORIIdentification>
          <nc:IdentificationID>AZNLETS55</nc:IdentificationID>
        </j:OrganizationORIIdentification>
        <j:AgencyControlTerminalIndicator>no</j:AgencyControlTerminalIndicator>
        <j:AgencyAuthorizationCode>ACDZ</j:AgencyAuthorizationCode>
      </j:OrganizationAugmentation>
    </n2:Agency>
  </n2:NLETSUpdateData>
</n2:NLETS>

Example 4: Response to updating an ORI.

<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>TR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>ODORION00</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS45</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[MR01714171]]></nh2:DocumentControlFieldText>
    <h2:MessageReceiveDate>06/17/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>09:06</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>06/17/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>09:06</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00134</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData>
    <n2:ResponseText>
      ?TR:PYORION00:RECORD UPDATED FOR ORI/AZNLETS55
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 5: Message to delete an existing ORI.

<n2:NLETS xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:J="http://niem.gov/niem/domains/jxdm/4.1" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0"
xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>TD</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>OD</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[1234567890]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSUpdateData n2:key="TD">
    <n2:Agency>
      <nc:OrganizationLocation>
        <nc:LocationName>PHOENIX</nc:LocationName>
      </nc:OrganizationLocation>
      <J:OrganizationAugmentation>
        <J:OrganizationORIIdentification>
          <nc:IdentificationID>AZNLETS43</nc:IdentificationID>
        </J:OrganizationORIIdentification>
      </J:OrganizationAugmentation>
    </n2:Agency>
  </n2:NLETSUpdateData>
</n2:NLETS>

Example 6: Response from ORION when deleting an ORI.

<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>TR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>ODORION00</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS45</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE5]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>06/17/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>09:18</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>06/17/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>09:18</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00136</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData>
    <n2:ResponseText>
      ?TR:PYORION00:RECORD DELETED FOR ORI/AZNLETS55
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 7: An inquiry on an ORI.

<n2:NLETS xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:J="http://niem.gov/niem/domains/jxdm/4.1" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>TQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS44</nh2:OriginatingORIID>
    <nh2:DestinationORIID>OD</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE5]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="TQ">
    <n2:Agency>
      <J:OrganizationAugmentation>
        <J:OrganizationORIIdentification>
          <nc:IdentificationID>AZNLETS20</nc:IdentificationID>
        </J:OrganizationORIIdentification>
      </J:OrganizationAugmentation>
    </n2:Agency>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 8: An inquiry by location.

<n2:NLETS xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:J="http://niem.gov/niem/domains/jxdm/4.1" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>TQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS45</nh2:OriginatingORIID>
    <nh2:DestinationORIID>OD</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE5]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="TQ">
    <n2:Agency>
      <nc:OrganizationLocation>
        <nc:LocationName>PHOENIX</nc:LocationName>
      </nc:OrganizationLocation>
      <J:OrganizationCategoryNLETSCode>PD</J:OrganizationCategoryNLETSCode>
    </n2:Agency>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 9: A response to an ORI inquiry.

<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>TR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>ODORION00</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS45</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE5]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>06/17/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>09:32</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>06/17/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>09:32</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00142</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData>
    <n2:OrionRecord>
      <n2:OwnerIdentification>
        <nc:IdentificationID>PY</nc:IdentificationID>
      </n2:OwnerIdentification>
      <n2:CreateDate>2010-02-17</n2:CreateDate>
      <n2:UpdateDate>2019-01-14</n2:UpdateDate>
      <n2:CertifiedDate>
    </n2:CertifiedDate>
    <n2:Agency>
      <j:OrganizationCategoryNLETSCode xmlns:j="http://niem.gov/niem/domains/jxdm/4.1">SA</j:OrganizationCategoryNLETSCode>
      <nc:OrganizationLocation>
        <nc:LocationName>PHOENIX</nc:LocationName>
        <nc:LocationAddress>
          <nc:StructuredAddress>
            <nc:LocationStreet>
              <nc:StreetFullText>1918 W WISPERING WIND</nc:StreetFullText>
            </nc:LocationStreet>
            <nc:LocationCityName>PHOENIX</nc:LocationCityName>
            <nc:LocationPostalCode>85083</nc:LocationPostalCode>
          </nc:StructuredAddress>
        </nc:LocationAddress>
        <nc:LocationContactInformation>
        <nc:ContactTelephoneNumber>
          <nc:FullTelephoneNumber>
            <nc:TelephoneNumberFullID>(623)308-3531</nc:TelephoneNumberFullID>
          </nc:FullTelephoneNumber>
        </nc:ContactTelephoneNumber>
        <nc:ContactFaxNumber>
          <nc:FullTelephoneNumber>
            <nc:TelephoneNumberFullID>(623)308-3501</nc:TelephoneNumberFullID>
          </nc:FullTelephoneNumber>
        </nc:ContactFaxNumber>
        <nc:ContactSecondaryTelephoneNumber>
          <nc:FullTelephoneNumber>
            <nc:TelephoneNumberFullID>(800)528-4020</nc:TelephoneNumberFullID>
          </nc:FullTelephoneNumber>
        </nc:ContactSecondaryTelephoneNumber>
        <nc:ContactSecondaryFaxNumber>
          <nc:FullTelephoneNumber>
            <nc:TelephoneNumberFullID>(623)308-3501</nc:TelephoneNumberFullID>
          </nc:FullTelephoneNumber>
        </nc:ContactSecondaryFaxNumber>
      </nc:LocationContactInformation>
    </nc:OrganizationLocation>
    <nc:OrganizationName>NLETS CONTROL CENTER</nc:OrganizationName>
    <j:OrganizationAugmentation xmlns:j="http://niem.gov/niem/domains/jxdm/4.1">
      <j:OrganizationORIIdentification>
        <nc:IdentificationID>AZNLETS43</nc:IdentificationID>
      </j:OrganizationORIIdentification>
      <j:AgencyAddCancelIndicator>true</j:AgencyAddCancelIndicator>
      <j:AgencyBaselinePriorityValue>0</j:AgencyBaselinePriorityValue>
      <j:AgencyCHRIAuthorizedIndicator>true</j:AgencyCHRIAuthorizedIndicator>
      <j:AgencyControlTerminalIndicator>true</j:AgencyControlTerminalIndicator>
      <j:AgencyServiceHoursCode>24 HR SERVICE W/TERMINAL</j:AgencyServiceHoursCode>
      <j:AgencyAuthorizationCode>ACDZ</j:AgencyAuthorizationCode>
    </j:OrganizationAugmentation>
    <n2:OrganizationActiveCode>A</n2:OrganizationActiveCode>
    </n2:Agency>
    <n2:MiscellaneousUpdateText></n2:MiscellaneousUpdateText>
    </n2:OrionRecord>
  </n2:NLETSResponseData>
</n2:NLETS>

Top

Legacy (DEPRECATED)

ORION Legacy Specifications (DEPRECATED)

This section describes the format to enter, modify, delete and access Nlets ORION records. Examples for ORION transactions are also included.

Query Formats

ORI Record Definition/Creation

The table below describes the format for creating an ORION record.

Entry Size Explanation
TA. 2 Message type for adding an ORION record.
Sender ORI 9 Sender ORI followed by a period.
Destination ORI 2 Must always be OD (ORION Directory) followed by a period.
TXT 3 Fixed field prefix denoting beginning of message.
ORI/ 4 Prefix to identify ORI to be entered into the record.
ORI 9 ORI of ORION record followed by a period.
LOC/ 4 Prefix to identify location field.
Location 2-20

City or County; for Federal agency, user has only 16
characters since program will supply the Federal identifier and
the dash. Alpha/Numeric & spaces except dash (-). The dash
will be ignored on inquiries. Field is followed by a period.

TYP/ 4 Prefix to identify the type of agency
Type of Agency 2

Must be one of the valid type codes; law enforcement, criminal
justice, and non-criminal justice followed by a period. The type
codes are:
Law Enforcement
PD - any agency of city government.
SO - any agency of county government incl. parishes where
apropos.
SA - any agency employed by a state with statewide
jurisdiction.
LE - used as a catchall for any agency not fitting the above
criteria. May be used on inquiry or record creation.
FE - Federal agency.
 
Criminal Justice
JA - any prosecutor.
JC - any corrections agency.
JG - any probation agency.
JJ - any court agency.
JF - any Federal non-law enforcement criminal justice agency.
CJ - will return all defined non-law enforcement criminal justice
agencies and should be used as a general type for all ORIs
ending in B, M, N or Y.
 
Non-Criminal Justice Organizations or Agencies (i.e., DMV)
NJ - non-criminal justice agencies.
(Note: Generally, the second letter of these two character
codes are the same ones used by NCIC in breaking down their
ORIs for criminal justice agencies).

AGY/ 4 Prefix to identify agency name.
Agency Name 3-70 Agency name followed by a period.
ADR/ 4 Prefix to identify address.
Address 4-60 Street address followed by a period.
CIT/ 4 Prefix to identify city name.
City 2-30 Name of city followed by a period.
ZIP/ 4 Prefix to identify ZIP code.
ZIP Code 9 ZIP code followed by a period.
PHN/ 4 Prefix to identify phone number.
Phone # 10 Numeric; no dashes, followed by a period.
PH2/ 4 Prefix to identify alternate phone number.
Alternate Phone # 10 Numeric; no dashes, designates a secondary phone # for
agency, followed by a period.
HOS/ 4 Prefix to identify hours of service.
Hours of Service 1

Must be one of the following:
    A = 24 hr service w/terminal.
    B = not 24 hr service w/terminal.
    C = 24 hr service, w/o terminal.
    D = not 24 hr service, w/o terminal.
Field is followed by a period.

ATH/ 4 Prefix to identify Authorization Flags.
Authorization Flags 1-4

One or more of the following:
    A = User is authorized to send/receive administrative
    messages.
    C = User is authorized to send/receive CHRI.
    D = User is authorized to receive DMV data.
    Z = User is authorized to other Nlets messages.

PRI/ 4 Prefix to identify Baseline Priority.
Baseline Priority 1-2

Baseline Priority, 0-12:
    0 = use system default priority.
    1-12 = use baseline as minimum priority.

FAX/ 4 Prefix to identify FAX #.
FAX #/ 10

Numeric, no dashes. Agency sending document via FAX will
pay for transmission when using this number. Field is followed
by a period.

FX2/ 4 Prefix to identify FX2 #.
Alternate FAX #/ 10

Numeric, no dashes. Agency sending document via FX2 will
pay for transmission when using this number. Field is followed
by a period.

CTO/ 4 Prefix to identify control terminal identity flag.
Control Terminal
Flag
1

Designates the terminal(s) authorized to perform all functions
on ORION; must be Y or N (defaults to N), followed by a
period.

AOC/ 4 Prefix to identify add/cancel flag.
Add/Cancel Flag 1

Designates the terminal(s) authorized to add or cancel an
ORION record; must be Y or N (defaults to N), followed by a
period.

ACT/ 4 Prefix to identify active/inactive flag.
Active/Inactive Flag 1

Designates whether the ORI is active or inactive; may only be
set by a terminal with control terminal capabilities; must be A or
I (defaults to A), followed by a period.

REM/ 4 Prefix to identify remarks field.
Remarks 160 Remarks field.

There are several fields that are created by the ORION system to provide information on the record. This information will show up on the response but is not put in by the user when adding a record.

Entry Size Explanation
Record Owner 2

Name of line that record was received from initially; supplied by
Nlets; update is restricted to this line, and record will be
included in file listing for this line only.

Creation Date 6 Date ORI record was added to the ORION file; supplied by
Nlets.
Update Date 6 Date ORI record was most recently updated; supplied by
Nlets.
Certification Date 6 Date ORI record was last certified; supplied by Nlets.

Modify an ORION Record

The record update transaction will have the following format. All users may modify various data fields except where noted below (*).

Entry Size Explanation
TU. 2 Message type for adding an ORION record followed by a
period.
Sender ORI 9 Sender ORI followed by a period.
Destination ORI 2 Must always be OD (ORION Directory) followed by a period.
TXT 3 Fixed field prefix denoting beginning of message.
ORI/ 4 Prefix to identify ORI to be entered into the record.
ORI to be modified 9 *ORI may not be modified. Field is followed by a period.
LOC/ 4 Prefix to identify location field.
Location 2-20

*City or County; for Federal agency, user has only 16
characters since program will supply the Federal identifier and
the dash. This field may not be modified. Field is followed by
a period.

TYP/ 4 Prefix to identify the type of agency.
Type of Agency 2

*Type may be modified to any of the following provided it is
not in conflict with other editing rules. Field is followed by a
period. The type codes are:
Law Enforcement
PD - any agency of city government.
SO - any agency of county government Incl. parishes where
apropos).
SA - any agency employed by a state with statewide
jurisdiction.
LE - used as a catchall for any agency not fitting the above
criteria. May be used on inquiry or record creation.
FE - Federal agency.
Criminal Justice
JA - any prosecutor.
JC - any corrections agency.
JF - any probation agency.
JJ - any court agency.
JF - any Federal non-law enforcement criminal justice agency.
CJ - will return all defined non-law enforcement criminal
justice
agencies and should be used as a general type for all ORIs
ending in B, M, N or Y.
Non-Criminal Justice Organizations or Agencies (i.e.,
DMV)
NJ - non-criminal justice agencies.
(Note: Generally, the second letter of these two character
codes are the same ones used by NCIC in breaking down
their ORIs for criminal justice agencies).

AGY/ 4 Prefix to identify agency name.
Agency Name 3-70 Agency name followed by a period.
ADR/ 4 Prefix to identify address.
Address 4-60 Street address followed by a period.
CIT/ 4 Prefix to identify city name.
City 2-30 Name of city followed by a period.
ZIP/ 4 Prefix to identify ZIP code.
ZIP Code 9 ZIP code followed by a period.
PHN/ 4 Prefix to identify phone number.
Phone # 10 Numeric; no dashes, followed by a period.
PH2/ 4 Prefix to identify alternate phone number.
Alternate Phone # 10 Numeric; no dashes, designates a secondary phone # for
agency, followed by a period.
HOS/ 4 Prefix to identify hours of service.
Hours of Service 1

Must be one of the following:
    A = 24 hr service w/terminal.
    B = not 24 hr service w/terminal.
    C = 24 hr service, w/o terminal.
    D = not 24 hr service, w/o terminal.
Field is followed by a period.

ATH/ 4 Prefix to identify Authorization Flags
Authorization Flags 1-4

One or more of the following:
    A = User is authorized to send/receive administrative
    messages.
    C = User is authorized to send/receive CHRI.
    D = User is authorized to receive DMV data.
    Z = User is authorized to other Nlets messages.

PRI/ 4 Prefix to identify Baseline Priority.
Baseline Priority 1-2

Baseline Priority, 0-12:
    0 = use system default priority.
    1-12 = use baseline as minimum priority.

FAX/ 4 Prefix to identify FAX #.
FAX #(sender pays
charges)
10

Numeric, no dashes. Agency sending document via FAX will
pay for transmission when using this number. Field is
followed by a period.

FX2/ 4 Prefix to identify alternate FAX number.
Alternate FAX # 10 Numeric, no dashes, followed by a period.
CTO/ 4 Prefix to identify control terminal identity flag.
Control Terminal
Flag
1

*Designates the terminal(s) authorized to perform all functions
on ORION; must be Y or N (defaults to N), followed by a
period. May be modified only by Nlets or a designated
control terminal.

AOC/ 4 Prefix to identify add/cancel flag.
Add/Cancel Flag 1

Designates terminal(s) authorized to add or cancel an ORION
record; must be Y or N (defaults to N), followed by a period.
May be modified only by designated control terminal agency.

ACT/ 4 Prefix to identify active/inactive flag.
Active/Inactive Flag 1

*Designates whether the ORI is active or inactive; may only be
set by a terminal with control terminal capabilities; must be A
or I (defaults to A), followed by a period. May be modified
only by designated NSA.

REM/ 4 Prefix to identify remarks field.
Remarks 160 Remarks field.
  • If only the ORI is used in the modify transaction, all records with that ORI will be modified.
  • If the user includes the LOC field, only records matching both the location and ORI will be modified.
    Exception: If an agency wishes to change the TYP field, both the LOC and ORI must be included and match the record before modification is executed.
  • The sender's line code is compared to the record owner's line code to verify the sender is authorized to update the ORI record.
  • At least one additional field must be specified, along with the new data to be stored in that field.
  • Any fields given, including agency type, must pass the specific field edits, which are described above.
  • If all checks are successful, the current date is stored as the date of last update, and the modified record is written back to the ORI file.
  • There are four optional fields that may be blanked out by filling them with zeros.
Optional Field Entry
Alternated phone number PH2
FAX number FAX
Alternate FAX number FX2
Remarks REM

Delete an Existing ORION Record

The record delete transaction will have the following format:

Entry # Char. Explanation
TD. 2 Message type followed by a period.
Sender ORI 9 Sender ORI followed by a period.
Destination ORI 2 Always "OD" for cancel requests, followed by a period.
TXT 3 Fixed field prefix to beginning of message.
ORI/ 4 Prefix to identify ORI to be canceled.
ORI 9 ORI to be canceled, followed by a period.
LOC/ 4 Prefix to identify location field.
Location 2-20 Location must match what is on file exactly in order to
cancel the record.

Access an ORION Record

Formats and examples for accessing an ORION record are described in the sections that follow.

Retrieve a Record by ORI

The inquiry by ORI will have the following format.

Entry # Char. Explanation
TQ. 2 Message type followed by a period.
Sender ORI 9 Sender ORI followed by a period.
Destination ORI 2 2 character code indicating the location of the agency
followed by a period.
TXT 3 Fixed filed prefix to beginning of message.
ORI/ 4 Prefix to identify ORI.
ORI 7 or 9 ORI may be either 7 or 9 characters. System will return up
to 100 entries.
LOC/ (optional) 4 Prefix to identify location.
Location 2-20 Location.

The ORI is required, and LOC is optional. If the location field is included only records that match both the ORI and the location will be returned.

Note: If only an ORI is submitted and an exact match is not found, a search of eight and
seven characters will be made. This may result in some voluminous responses but it will
provide the inquirer with ORIs of the agency if not the exact terminal.

Retrieve a Record by Location

Searching the file for an ORI by specifying a location is accomplished with the following transaction:

Entry # Char. Explanation
TQ. 2 Message type followed by a period.
Sender ORI 9 Sender ORI followed by a period.
Destination ORI 2 2 character code specifying the physical location of the
agency followed by a period.
TXT 3 Fixed filed prefix to beginning of message.
LOC/ 4 Prefix to identify location field.
Location 2-20 Location; system will match 7 characters and, if no match,
decrease the number of characters down to a minimum of 2.
TYP/ 4 Prefix to identify type of agency
Type 9

The type codes are:
Law Enforcement
PD - any agency of city government
SO - any agency of county government (Incl. Parishes
where apropos)
SA - any agency employed by a state with statewide
jurisdiction.
LE - used as a catchall for any agency not fitting the above
criteria. May be used on inquiry or record creation.
FE - Federal agency
Criminal Justice
JA - any prosecutor
JC - any corrections agency
JF - any probation agency
JJ - any court agency
JF - any Federal non-law enforcement criminal justice
agency
CJ - will return all defined non-law enforcement criminal
justice agencies and should be used as a general type for
all ORIs ending in B, M, N or Y.
Non-Criminal Justice Organizations or Agencies (i.e.,
DMV)
NJ - non-criminal justice agencies
(Note: Generally, the second letter of these two character
codes are the same ones used by NCIC in breaking down
their ORIs for criminal justice agencies).

The LOC is required, and TYP is optional. All records in the specified member sub file that match the specified location and agency type, as described below, are returned to the sending ORI.

The type field is optional, and if not specified, defaults to search all law enforcement ORIs (types PD, SO, SA, LE) since the vast majority of inquiries will be for law enforcement ORIs. Federal agency records are not retrieved.

If a criminal justice agency (other than law enforcement) or a non-criminal justice agency (such as NICB) is being sought, the appropriate type code should be used. If a type code of "CJ" is used all criminal justice agencies (other than law enforcement and Federal agencies) will be returned as well as non-criminal justice agencies. The non-criminal justice agencies will clearly be identified in the response as a non-criminal justice agency.

Retrieve a Federal Agency Record

Searching a Federal agency's ORI record is accomplished by specifying a Federal agency 3-character code with a "FED" prefix rather than "LOC" prefix. The destination code indicates the state where the Federal agency resides.

The format for retrieving a federal agency record is described below.

Entry # Char. Explanation
TQ. 2 Message type followed by a period
Sender ORI 9 Sender ORI followed by a period
Destination ORI 2 2 character code indicating the physical location of the ORI
followed by a period.
TXT 3 Fixed filed prefix to beginning of message
FED/ 4 Prefix to identify federal agency/location field
Federal
agency/location
4

Prefix to identify the type of federal agency, may append a
location to this field to narrow the search (i.e.,
FED/FBI-DETROIT)

To limit the search to a particular location, the agency code is followed by a dash and one or more characters of the location. All records in the specified state sub file for the agency, limited to those matching the location, if any, are returned to the sending ORI.

Federal agencies will be handled differently since, for example, the user might be looking for the closest Federal office but may not know where the office is actually located. Inquiring by Federal agency ID returns all the Federal agency's offices within a state.

For example, if a user needs to contact the closest FBI office to Kalamazoo, Michigan he will send the state code "MI" and the agency name "FBI". The system will return all FBI offices in Michigan and the user will select the one he prefers.

ORION Legacy Examples

Example 1: Message to create a new ORI.

TA.AZNLETS20.OD.TXT
ORI/AZNLETS25.LOC/PHOENIX.TYP/SA.AGY/NLETS CONTROL CENTER.
ADR/1918 W WISPERING WIND.CIT/PHOENIX.ZIP/85083.
PHN/6233083531.HOS/A.ATH/ACDZ.PRI/0.PH2/8005284020.FAX/6233083501.
FX2/6233083501.CTO/Y.AOC/Y.ACT/A.REM/REMARKS

Example 2: Response from ORION after creating a new ORI.

TR.ODORION00
12:26 08/19/2011 00068
12:26 08/19/2011 00093 AZNLETS20
TXT
TR:NLORION00:RECORD ADDED FOR ORI/AZNLETS25

Example 3: Message to update an existing ORI.

TU.AZNLETS20.OD.TXT
ORI/AZNLETS25.LOC/PHOENIX.REM/UPDATED REMARKS

Example 4: Response to updating an ORI.

TR.ODORION00
08:36 08/25/2011 12743
08:36 08/25/2011 08777 AZNLETS20
TXT
TR:PYORION00:RECORD UPDATED FOR ORI/AZNLETS25

Example 5: Message to delete an existing ORI.

TD.AZNLETS20.OD.TXT
ORI/AZNLETS25.LOC/PHOENIX

Example 6: Response from ORION when deleting an ORI.

TR.ODORION00
09:33 08/24/2011 12670
09:33 08/24/2011 08589 AZNLETS20
TXT
TR:PYORION00:RECORD DELETED FOR ORI/AZNLETS25

Example 7: An inquiry on an ORI.

TQ.AZNLETS20.OD.TXT
ORI/AZNLETS25

Example 8: A response to an inquiry by ORI.

TR.ODORION00
08:38 08/25/2011 12745
08:38 08/25/2011 08779 AZNLETS20
TXT
ORI/AZNLETS25 LOC/PHOENIX

NLETS CONTROL CENTER
1918 W WISPERING WIND
PHOENIX, 85083

TYPE - SA
PHN # (623)308-3531
ALT PHN # (800)528-4020
FAX # (623)308-3501
ALT FAX # (623)308-3501
24 HR SERVICE W/TERMINAL
ANY AGENCY EMPLOYED BY A STATE WITH STATEWIDE JURISDICTION.
USER IS AUTHORIZED TO SEND/RECEIVE ADMINISTRATIVE MESSAGES.
USER IS AUTHORIZED TO SEND/RECEIVE CHRI.
USER IS AUTHORIZED TO RECEIVE DMV DATA.
USER IS AUTHORIZED TO OTHER NLETS MESSAGES.
ORI IS ACTIVE
BASELINE PRIORITY IS - 0
AUTHORIZED TO ADD/CANCEL ORIS
AUTHORIZED TO PERFORM CONTROL TERMINAL FUNCTIONS
OWNER: PY CREATED: 2011-08-24 UPDATED: 2011-08-25 CERTIFIED:
REMARKS:
REMARKS

Example 9: An inquiry by location.

TQ.AZNLETS20.NY.TXT
LOC/PHOENIX

Example 10: A response to an inquiry by Location.

TR.NYORION00
09:46 08/24/2011 18810
09:46 08/24/2011 08603 AZNLETS20
TXT
ORI/NY0372900 LOC/PHOENIX

PHOENIX VILLAGE PD -
455 MAIN STREET
PHOENIX, 13135

TYPE - PD
PHN # (315)695-2001
ALT PHN # (315)343-1313
FAX # (315)695-1305
24 HR SERVICE W/O TERMINAL
ANY AGENCY OF CITY GOVERNMENT
USER IS AUTHORIZED TO SEND/RECEIVE ADMINISTRATIVE MESSAGES.
USER IS AUTHORIZED TO SEND/RECEIVE CHRI.
USER IS AUTHORIZED TO RECEIVE DMV DATA.
USER IS AUTHORIZED TO OTHER NLETS MESSAGES.
ORI IS ACTIVE
BASELINE PRIORITY IS - 0
NOT AUTHORIZED TO ADD/CANCEL ORIS
NOT AUTHORIZED TO PERFORM CONTROL TERMINAL FUNCTIONS
OWNER: NY CREATED: 1990-03-29 UPDATED: 2003-02-05 CERTIFIED: 2010-11-30
REMARKS:
DISPATCHED BY OSWGO COUNTY 911

ORI/NY037531J LOC/PHOENIX

T/COURT SCHROEPPEL -
69 COUNTY ROUTE 57 A
PHOENIX, 13135

TYPE - JJ
PHN # (315)695-6177
NOT 24 HR SERVICE W/O TERMINAL
ANY COURT AGENCY.
USER IS AUTHORIZED TO SEND/RECEIVE ADMINISTRATIVE MESSAGES.
USER IS AUTHORIZED TO SEND/RECEIVE CHRI.
USER IS AUTHORIZED TO RECEIVE DMV DATA.
USER IS AUTHORIZED TO OTHER NLETS MESSAGES.
ORI IS ACTIVE
BASELINE PRIORITY IS - 0
NOT AUTHORIZED TO ADD/CANCEL ORIS
NOT AUTHORIZED TO PERFORM CONTROL TERMINAL FUNCTIONS
OWNER: NY CREATED: 2002-07-16 UPDATED: 2003-02-05
CERTIFIED: 2010-11-30
REMARKS:
00000000000000000000000000000000000000000000000000

Example 11: An inquiry by Federal agency.

TQ.AZNLETS20.NY.TXT
FED/DOJ

Example 12: A response to an inquiry by Federal agency.

TR.NYORION00
09:19 08/25/2011 59112
09:19 08/25/2011 08791 AZNLETS20
TXT
DOE NAVAL REACTOR SECURITY POLIC SCHENECTADY NYDOE0000 B Y
DOE NAVAL REACTOR SECURITY POLIC SCHENECTADY NYDOE0001 B Y
US DOJ OIG INV NYFO DOJ-NEW YORK NYDOJ0100 B Y
DOE NAVAL REACTOR SECURITY POLIC DOJ-SCHENECTADY NYDOE0100 B Y
DOE NAVAL REACTOR SECURITY POLIC DOJ-SCHENECTADY NYDOE0002 B Y

- CODE TRANSLATION FOR LAST 3 COLUMNS -
A = 24 HR SERVICE, W/TERMINAL
B = NOT 24 HR SERVICE, W/TERMINAL
C = 24 HR SERVICE, NO TERMINAL
D = NOT 24 HR SERVICE, NO TERMINAL
Y = AUTH TO SND/RCV CHRI VIA NLETS
N = NOT AUTH TO SND/RCV CHRI VIA NLETS
F = FAX TRANSMISSION AVAILABLE
* = NON-CRIMINAL JUSTICE AGENCY

Top

Downloads

Download TA Schema

Download TA Stylesheet

Download TD Schema

Download TD Stylesheet

Download TQ Schema

Download TR Schema

Download TR Stylesheet

Download TU Schema

Download TU Stylesheet

Top