Licensing
This chapter describes the NGA license options and available package sizes.
The archiving is a part of WinCC OA. You can select between three different types of archiving:
- NGA archiving: NGA is part of the basic WinCC OA runtime environment.
- HDB archiving: HDB is part of the basic WinCC OA runtime environment.
- RDB archiving: RDB can be added as a license option.
The following NGA license options are available:
| NGA Basic1 | NGA Standard package | NGA Premium package | NGA Backend Connection | |
|---|---|---|---|---|
| Local PostgreSQL®, InfluxDB® or MS SQL® | ✓ | ✓ | ✓ | - |
| Archiving in a redundant system | ✓ | ✓ | ✓ | - |
| NGA Backend connection2 | Not available | 13 | 13 | +1 |
| Project size (PowerTags) | Unlimited | ≤ 150,000 | Unlimited | - |
| Project size (BACnet objects) | Unlimited | ≤ 30,000 | Unlimited | |
| Archive Groups | Limited4 | Unlimited | Unlimited | - |
1 - included in WinCC OA – Server Basic
2 - An NGA backend connection allows the operation of an additional backend both locally and remotely.
3 - Additional backends can be purchased separately. One freely usable NGA backend connection is included in the NGA Standard and NGA Premium license options.
Note: Other NGA Backend Connection license option entries - apart
from those included or additionally purchased – are reserved for internal use and
cannot be freely used.
Note: When using NGA in a redundant system, the NGA backend
connection to the redundant partner DB is covered by the redundancy licence.
4 - You can create up to 7 archive groups (6 EVENT groups and 1 ALERT group). The one ALERT group and one EVENT group are available by default).
Note: BACnet Objects and Power Tags are calculated separately.
Note: The NGA basic license does not allow remote
scenarios from the NGA. The local operation of PostgreSQL®, InfluxDB® or MS SQL® is
possible (not more than 1 backend may be active at the same time). The operation of
further backends is not permitted. For scenarios, see chapter Deployment Scenarios.
