Legacy Text Examples - ORION (TA, TD, TQ, TR & TU)

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. ROA/
4 Prefix to identify the agency roles to add field. Agency Roles to Add
100

Must be one or more of the valid roles followed by a

period. If more than one role is being added, then the roles should be

listed in a comma separated list (ex. HEAT, RTCC)

The agency role codes are:

RTCC = Real Time Crime Center

HEAT = Human Exploitation and Trafficking

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

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

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. ROA/
4 Prefix to identify the agency roles to add field. Agency Roles to Add
100

Must be one or more of the valid roles followed by a

period. If more than one role is being added, then the roles should be

listed in a comma separated list (ex. HEAT, RTCC)

The agency role codes are:

RTCC = Real Time Crime Center

HEAT = Human Exploitation and Trafficking

ROR/
4 Prefix to identify the agency roles to remove field.
Agency Roles to Remove
100

Must be one or more of the valid roles followed by a

period. If more than one role is being removed, then the roles should be

listed in a comma separated list (ex. HEAT, RTCC)

The agency role codes are:

RTCC = Real Time Crime Center

HEAT = Human Exploitation and Trafficking

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 Record by Role

Searching the file for an ORI by specifying a role 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 or OD followed by a period. TXT 3 Fixed filed prefix to beginning of message. ROL/ 4 Prefix to identify role field. Agency Role 100 Must be one of the valid roles followed by a period.

The agency role codes are:

RTCC = Real Time Crime Center

HEAT = Human Exploitation and Trafficking

The ROL is required. All records that match the specified role are returned to the sending ORI.

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: A response to an inquiry with multiple Location.

TR.NYORION00
09:46 08/24/2011 18810
09:46 08/24/2011 08603 AZNLETS20
TXT
NLETS SERVICE CENTER 1 PHOENIX AZNLETS01 B NF*
NLETS SERVICE CENTER 2 PHOENIX AZNLETS02 B Y *
NLETS SERVICE CENTER 3 PHOENIX AZNLETS03 A NF*
NLETS SERVICE CENTER 4 PHOENIX AZNLETS04 B YF
NLETS SERVICE CENTER 5 PHOENIX AZNLETS05 B YF
NLETS SERVICE CENTER 6 PHOENIX AZNLETS06 B YF
NLETS SERVICE CENTER 7 PHOENIX AZNLETS07 B YF
NLETS SERVICE CENTER 8 PHOENIX AZNLETS08 B NF
NLETS SERVICE CENTER 9 PHOENIX AZNLETS09 A YF
NLETS SERVICE CENTER 10 PHOENIX AZNLETS10 A YF*
NLETS SERVICE CENTER 11 PHOENIX AZNLETS11 B YF

- 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

Example 12: Message to create a new ORI with a role

Example 13: Message to create a new ORI with multiple roles

Example 14: An inquiry by role.

TQ.AZNLETS20.OD.TXT
ROL/HEAT

Example 15: Message to update an existing ORI with roles to add and remove

TU.AZNLETS20.OD.TXT
ORI/AZNLETS25.LOC/PHOENIX.ROA/HEAT.ROR/RTCC