User Manual

Configuring the System
101
• RSN Movement – RSN detects and reports that it has begun to move, stopped moving, or
has not moved (depending on the application) for some period of time (set by you).
• RSN Shock – RSN detects and reports a shock that exceeds some pre-programmed
threshold.
Depending on the application, the RSN will be used to dictate the behavioral requirements of
each device. It is through the configuring of the RSN through the RSN Configuration Tool
that these behaviors are defined.
Each RSN configuration has approximately 70 parameters that can be set. All settings have
factory defaults established that may or may not require editing based on your system. In
addition, depending on your access rights to the application, not all parameters may be
available to you. Some parameters are intended to be managed by a technical administrator
(Advanced role) with network experience, while others are intended for general configuration
purposes (User role).
Behavior Profiles are set within each RSN that define how the RSN will behave under
specified field conditions or from commands from a user application. Throughout this
section, we will be referencing the First Responder application as an example.
8.2.4 The RCT Configuration Inheritance
The RCT manages all of the configurations that are required to define the behavior of an
RSN. Configurations are organized in an inheritance structure with lower levels deriving
settings and behaviors from higher levels. The structure is similar to that of a waterfall,
whereas, data from the upper level configurations cascades down to those below it. Each
lower configuration takes on the behaviors of the upper configurations unless specifically
changed within the Configuration Tool.
Depending on the application, the assets may need one or many configurations to handle the
behavior desired of their RSNs. The RCT allows the user to create a database of many
configurations and assign the RSNs to use the applicable configurations. This is achieved by
defining and setting up all of the needed configurations for the defined set of RSNs and then
associating each RSN with the configurations through an assigning process.
As mentioned previously, configurations are organized into a tree (inheritance) structure.
The application is provided with one-top level default configuration. For the IMS with
Automated Accountability application, all configurations should derive from the First
Responder market configuration. All inherited configurations are derived from this one top-
level default configuration. All default settings can be changed in subsequent lower levels.
The default values are provided by THN at the time of delivery to provide the basic
behaviors for each configuration.
When creating a new configuration, its parameter settings are derived from the top-level
default settings until those settings are individually overridden. You may derive all of an
RSN’s configurations from the top level or you may derive your own configurations, thus
creating a library of configurations. Each setting has an inheritance control that allows you to
override the default.