Checking capacity licensing status

Every station that runs on a platform with global capacity licensing keeps a running tally on all corresponding resources in the Resource Manager view.

You are using Workbench and are connected to a station with global capacity licensing.

Right-click the opened Station and select Views > Resource Manager.
The Resource Manager opens.

Any station with global capacity licensing has specific entries in the lower Resource Information table of this view.
In this example, three capacityLicensing.recount statistics include a timestamp that indicates when the global capacity recount last ran.
Another group of globalCapacity.resource statuses show the current counts along with respective license limits (if any). The station view above reflects the first globalCapacity example given is:
```
<feature name="globalCapacity" expiration="2016-04-01" point.limit="1250" 
device.limit="50" excludedDevices="ndio;nrio;niagaraDriver" 
excludedPoints="ndio;nrio;niagaraDriver"/>
```
where global limits exist only on devices (Limit: 50) and proxy points (Limit: 1,250) with ndio, nrio and niagaraDriver devices and points being excluded from any limits.
To refresh the count, click Update.
Often you delete as well as add resources in the process of engineering a station. Capacity licensing never decrements any resource counter. This could result in inaccurate counts over a long period of time. Therefore, any resource created with an over-capacity error will never get out of fault. You must delete it.
A station restart corrects global capacity counts. However, since this is often inconvenient, the system performs a global capacity recount approximately every 10 minutes to correct any inflated counts. You can always see the recount status, along with the current global licensing counts and limits in the station’s Resource Manager view (or spy view).
If you are a super user, you can get this same information by right-clicking the spy page on a station, at the following location: Spy > metrics.
Special permission is required to view spy pages.

The Remote Station | metrics view opens.

This information matches the Resource Manager view example with the exception of the recountLastRun timestamp shown (one hour later).
Added components that exceed global capacity limits provide a Fault Cause explaining the reason. In this example, where there are 46 global existing devices, if five (5) new ModbusTcpDevices are added this results in a fault, as 51 devices is one over the 50 device limit.

As shown above, the property sheet for the device shows this reason in Fault Cause.
Delete this (or any) component with a similar fault cause.

If you do not delete the component, it remains in fault. Corresponding events are also entered in the station’s LogHistory.

The globalCapacity count for any exceeded resource appears in the corresponding entry in the station’s Resource Manager.

The necessary deletion of an over-limit device (51) does not decrement the count back at that time. Instead, a periodic recount (about every 10 minutes) or station restart is needed to update the count.

Similar component faults and error logs apply to networks, points, links, and schedules.

As shown above, the ProxyExt for a proxy point shows a Fault Cause reason. The property sheet of a network in global capacity fault is similar Exceeded network limit for globalCapacity, and this applies also to a schedule in global capacity fault: Exceeded schedule limit for globalCapacity.

Exceeding the globalCapacity link limit produces a popup Capacity Licensing window on the wire sheet or active view that reports: “Exceeded Link Limit,” and the link is not functional.