Know Before Installing

Before installing the KMC Commander Gateway Service, read the following sections to understand the potential impact of the service on the station.

Impact of the Service on Station Operation

The KMC Commander Niagara Gateway Service is designed to provide data from the Niagara Station to the KMC Commander Cloud. Providing this data will mean that the service will have to poll the points in the station. The polling of these points can impact the station performance.

CPU Usage

Prior to installing the service, review the JACE's resources by viewing the resource manager on the station. Note the CPU% and Memory Usage during normal operation.

After installing the service and setting up all the points that will be leveraged by the service, revisit the JACE’s resource manager to confirm normal operation. For details on normal operation, see the Tridium documentation (docIT.pdf, System Performance).

Point Polling

The KMC Commander Niagara Gateway Service will poll points based on the project level point update time in KMC Commander Cloud (default: 5 minutes). As points are added to the cloud, the service will create a listing of these points in the service within the station.

Upon a point update cycle, the service will get an updated value from the object by subscribing to that point in Niagara. The default point subscription in Niagara is 1 minute. During this time the point being polled will be polled based on its Niagara tuning policy settings.

Tuning Policies

Configuration of the Niagara object’s tuning policies can severely impact the JACE’s performance when exchanging data with the KMC Commander Cloud. Proper tuning policies should be implemented across all points of interest to be exchanged with the KMC Commander Gateway Service.

For example, the default Niagara tuning policy is set to 5 seconds. If that policy is used for the points of interest, then at every KMC Commander Cloud update request (default interval of 5 minutes) those points will be polled every 5 seconds for 1 minute.

Note: For details on tuning policy setup, refer to the Tridium documentation (docDrivers.pdf, Tuning).