In general, a service-level application covers modifying the contents of the service. For database-type services, this includes tasks such as adding, deleting, and editing records. For current value services, it covers tasks such as performing setpoint commands and clearing communication statistics.
An Event is one or more tasks that can be performed for a particular Application. For service-level Applications, the name of an Event is pre-defined, as are the authorization levels required to perform the various tasks governed by the Event. For component-level Applications, you can use a pre-defined Event name or create a new one.
Some Events have varying levels of authorization, while others are used to simply grant or deny permission.
An example of an Event with varying levels for authorization is the MSS Event named ACCESS. If you have Level 1 authorization for this event, you can view the properties of a record in the MSS. If you have Level 2 authorization, you can additionally edit records in the service.
An example of an Event that is used to grant or deny is the CAS Event named ACK. If you have Level 2 authorization you can acknowledge alarms. If you have a lower authorization you cannot.
The Events for each service Application are outlined in the Security Reference section.
An Event can be assigned one or more permissions.
Example
Three different permissions have been assigned to the PNT ACCESS event in the example below. All users (*) have Level 1 (read) authorization. The CygNet Group named SCADA_TEAM has Level 5 (admin) authorization. And bill.walsh on the acme domain has Level 2 (update) authorization.
|
|
| Users assigned to the PNT ACCESS event |
|
|
|
