About Genetec Mission Control™ profiles - Genetec Mission Control™ 2.10

Genetec Mission Control™ User Guide 2.10

series
Genetec Mission Control™ 2.10
revised_modified
2018-11-30

A profile in Genetec Mission Control™ is an incident filter used to ensure the adequate distribution of the active incidents among the operators who are currently logged on to the system. Profiles filter incidents by type and by occurrence location.

How profiles work

Profiles can be assigned by the system, by a supervisor, or by the operators themselves (if they have the Change profile assignment privilege). A profile can only be assigned to an operator who is configured as an allowed user of the profile, and if the operator is connected to the system through Security Desk.

Operators can only see incidents that are dispatched to them, either because they are the recipients of an incident type, or because someone has forwarded or transferred the incident to them.

When a profile is assigned to an operator, the system hides from the operator's view all incidents that are not qualified (based on incident types and occurrence locations) by the profile. This allows the operator to better focus on the tasks at hand. If multiple profiles are assigned to an operator, the operator sees the combined result of all assigned profiles.

Note that the system will not hide from an operator, incidents that they have taken ownership of, and an operator will never see an incident that has not been dispatched to them as a result of a profile assignment.

Consider the following setup:
  • Paul is an operator and recipient of incident type A, B, and C.
  • Paul is logged on through Security Desk and has the Incident monitoring task open.
  • Mary is an operator and recipient of incident type B, C, and D.
  • Mary is not logged on to the system.
  • There are active incidents of type A, B, C, and D in the system.
  • Profile A' filters on type A incidents, and has Everyone as allowed users.
  • Profile B' filters on type B incidents, and has Everyone as allowed users.
  • Profile C' filters on type C incidents, and only has Mary as allowed user.
  • Profile D' filters on type D incidents, and has Paul and Mary as allowed users.
The following series of statements and action-results illustrate how the system behaves.
  • Before any profile is assigned to Paul, Paul can see all active incidents of type A, B, and C that are in the system, but not type D incidents.
  • Profile A' is assigned to Paul → Paul only sees type A incidents in the system.
  • Profile B' is also assigned to Paul → Paul sees both type A and B incidents in the system.
  • Profile C' cannot be assigned to Paul because Paul is not an allowed user of Profile C'.
  • Profile D' is assigned to Paul → No difference, because Paul is not a recipient of type D incidents.
  • No profile can be assigned to Mary because Mary is not yet logged on.
  • Mary logs on through Security Desk → Profiles can now be assigned to Mary.
  • Mary opens the Incident monitoring task and forwards a type D incident to Paul → Paul sees the forwarded type D incident because Profile D' is assigned to Paul.