Terms to Know Before Getting Started

Before using the Omnixx Console, become familiar with the following terms and their definitions. Understanding these terms will aid you in the use of this manual, as well as provide valuable background information that will help make your use of the Omnixx Console as efficient as possible.

•

Agency – An organization that provides and controls access to law enforcement information through a message switch. In many cases, an agency is a state Control Terminal Agency (CTA), but could also be a local agency such as a Sheriff’s office or police department.

•

Applications – Refers to client applications such as Omnixx Force, Omnixx Trainer, and Omnixx Console, all-inclusive in the Omnixx Suite of products.

•

Business Rules – Data necessary to configure Omnixx client applications to an agency’s specific requirements. Examples: menus, forms, edits, help, and message processing rules.

•

Omnixx – Stores all of the application programs and data needed by Omnixx Force, Omnixx Trainer, and Omnixx Console. It also allows LEMS to retrieve information concerning user logons, certifications, devices, and is able to update a share of this information.

•

Omnixx Console – Provides the end-user functionality needed to maintain the application repository. It allows authorized users to update the repository database. A remote version exists that allows agency administrators to maintain database records for users and devices assigned to their own agencies. A central console version provides global control over the entire system.

•

Omnixx™ Force – Provides functionality for entering queries, updating state and NCIC databases, and exchanging messages with other end-users via LEMS. It is a thin-client application that runs on both Netscape Navigator and Microsoft Internet Explorer.

•

Omnixx™ Trainer – Allows users to train, complete exercises, and take certification tests. It is a thin-client application that runs on both Netscape Navigator and Microsoft Internet Explorer.

•

Programs – Executable code and support files necessary to run an application. Examples: applets, classes, and resources.

•

Subagency – An agency can be divided into subagencies to allow assigned operators at local agencies to administer users and devices for their own agency.

•

Support Documents – Documents included in an application and used by end-users. Examples: NCIC user manual, NLETS user manual, product user manual, and agency-specific documents.