Differences between Vocera Report Server and Vocera Analytics

Some features in Vocera Analytics and Vocera Report Server are similar but vary in operation. The differences between Vocera Report Server and Vocera Analytics is provided in this topic.

The following table lists the features in Vocera Report Server (VRS) and Vocera Analytics (VA) that are similar but vary in operation:

Feature	Vocera Report Server	Vocera Analytics
Data Latency	Nightly updates	Variable: Users: Updates every 10 minutes Calls/Texts/Activity: Updates every 4 minutes Engage: Configurable, default is every 60 minutes. Vocera Analytics also allows the refresh rate for Users and for Calls/Texts/Activity to be configured.
Call Duration	Includes network connection time. The time that the user hits genie button to the time the user ends the call with genie button is calculated.	Only actual talk time. Duration of actual call. Only display calls above 0 seconds.
Login Attempts	No login attempts counted.	User logins are included as speech attempts (both successful and unsuccessful) in Speech Recognition Activity.
Broadcast Messages
General	Does not include broadcasts without a duration and hence the count shows only successful broadcast calls.	Includes broadcasts with zero duration. Hence unsuccessful broadcasts are also included. Note: Broadcast duration is calculated based on the talk time of the actual broadcast.
Broadcast Counts	Maintains one record in the database for broadcast or multicast even though there are multiple recipients in the broadcast. Maintains data from the caller perspective only and does include receiver details.	Maintains separate entries for all the recipients for broadcast. Maintains both caller and receiver message counts.
Users that are included in multiple units (permanent or temporary)	-	User Facility is the displayed facility. Some users also belong to several physical units from both facilities. Attempts are shown for each unit but total shows only a single speech attempt.
Grouping	Unique grouping. For example, Unit + Unit + Unit, and so on.	Individual Unit (department) groupings.
User statistics	All User type reports are tracked as the device owner or unit Individuals assigned permanently to many units maintain dates and history. Reported individually but not rolled into grand totals.	-
User/Login Activity	Login is considered an activity.	Login is not considered as an activity. User must actually perform an activity.
Units	Group or Department (simply appended + if in multiple dept)	Group with Department box checked.
Device (Badge or Smartphone) Details	Does not include the device type that caller utilized.	Includes the caller device.
User Access	Only allows a single admin user login.	Active directory and role based system allowing clinical end users access to reports and dashboards but not administration functions.
Scheduling Reports	User emails no longer from Voice Server using name attributes.	Does not link back to voice server. Admins must enter full user email address. Recommend using distribution lists and active directory functionality.
Speech Recognition Note: No speech occurrences when user hit the button but did not say anything.	Includes No Speech Occurrences.	Removed references to No Speech Occurrences and excluded these from actual speech attempts count.
Device Activity	Limited to VRS logs and limited activities.	Captures the complete and detailed device activity logs for much more detailed transactions.
Integrations Activity	Groupings mostly by time or message ID.	Filters and groupings available by Facility and Unit.
PBX Call Data	Only keeps a record of the first person that accepts PBX calls.	All responses (unavailable, accepted, rejected, and so on) are reported.
Badge Firmware	Limited data available and limited filters.	Stores and reports actual software version.
Device Usage	Considers only Group and User calls.	Considers all calls such as Broadcast, Address Book, User, and Group.

The following table lists the features and the items that taken into consideration for calculating the data in Vocera Analytics (VA):

Features	Considerations in Vocera Analytics (VA)
Badge Last Used	Any genie interaction is considered as an activity in VA.
Device Version Usage	VA considers all calls (User, Group, Broadcast, Telephone) that are rejected by receiver and Aborted calls (canceled by caller), whereas VRS only considers answered user calls and group calls.
Genie Summary	VA filters out records if speech duration is null whereas VRS considers all. Note: In VRS, total unique users are counted as 1 by default when login counts cannot be determined.
Hourly Usage	While logging, genie sessions are captured with user names in VA whereas in VRS it is captured as NLI (Not logged in). VA captures more granular data. If the user presses the Call button on badge multiple times, all genie sessions are recorded in VA whereas VRS does not capture all genie sessions. In some cases VA does not capture genie session whereas VRS does. For example, auto annunciated messages, starting genie after call hold, and so on.
Inactive Address Book Entries	Both Inactive Address Book Entries and Address Book Entry Summary are considered as Inactive Address Book Entries.
Inactive Groups	All group activities such as Voice message, VMI alerts, Calls, Broadcast, and VMP messages are considered.
Inactive Users	VA considers any activity of user such as Login, VMP message sent, call, genie initialization by the user as active user and does not list under inactive whereas VRS does not consider VMP messages.