ZUSA

Campaign Manager Zusa is the business end of the Campaign Manager system. The Zusa is responsible for playing back media and managing playlists, media downloads as well as monitoring system health.

Zusa’s details view panel when user selects it from the list view. Under details view of the zusas we have some unique information about them. We have information about the name, the status, when the zusa was last online, up time of zusa, subscribed channels, gateway IP, screen status, client version, alert, location and time zone.

Also with selected zusa appear another right panel that contains three sections.

These features are disabled at the moment and works only for CMPlayers that are configured with remote desktop software.

In this section we can see the channels associated on the zusa. Under currently playing we can see which campaigns are published to the zusa and which campaigns are downloading or pulling from the zusa.

Also we can see which media is in the campaigns and we can preview it by clicking on its name.

The context menu contains all the options for the specific type of entity. The context menu for devices is located on the left side and replaces the site’s navigational menu. You can also approach Device’s context menu by right click on the list view area.

The options from the context menu are explained below.

Export Device List	Clicking on this option will create a csv file of all devices that are currently in the list view with all information about them.
Change The Channel	This option is enabled only for single selected device row, and will redirect the user to device’s Channel Settings.
Pause Download	When this option is set, the player does not download new content: You can publish new content or pull published campaigns, tickers or commands, but player will not receive requests. After this option is disabled by clicking on the Resume Downloading, the player will receive all the changes.
Player Log Report	User can approach the Neptune Player Report by clicking on this option only if the service is linked with Neptune service. Also if you want Neptune to make reports, you have to go to domain’s Control Panel and check Record what has been played in play log.
Rename	We can use this option to change the name of the selected player.
Delete	If some player is inactive for a long time, and we want to remove it from the Devices list view, we can delete it by selecting its row first. More than one device can be deleted at once.
Refine Location	When no device row is selected in Devices page, on the panel above the list view is displayed the devices status pie and the map with location pointers of all devices in the list. When you select one device, the details view for this device replaces the all devices view. Among the devices information is shown the physical location of the device. The physical location is not precise all the time and can point a nearby location of your actual. If you like to change the location and where the pin points on the map, you can press on Refine Location. You can drag and drop the pin in a wanted location. Also you can change the description of the location in the field above. This field also will offer suggestions of existing location while typing. If user choses to go by suggestion, the pointer will automatically change to new location. Relocate button will save the changes, and Reset to default will reset to predefined location.
Reboot device	This option will restart selected player’s device.

Beside the CM Player Configuration file, user can set settings for devices in device’s configurational page in CampaignManager Web. This page differs from the configurational file with the fact that the player must play when user make changes in this page. This page can be opened with double click on specific zusa’s row, and from here user can set settings for zusa.

Under Zusa Details are listed three sections: Summary, Player Activity and Status information.

This section gives you information about player’s status, number of attached display devices, how many of available devices are configured to run the CM Player and the channels used in configuration.

Note that if your device have more than one screen attached, zusa will be played only on your screen with index 1.

In the Player Activity subsection we have information about the channel that the zusa is configured with. There is also information about which campaigns are Currently Playing and how much they have been downloaded.

And below the Currently Playing there is the Live Playlist section which is displaying the files in a campaign. These files can be also previewed by clicking on them and their content will be displayed in the Preview box.

In the Status information sub section there is information about further details of the machine that is running the player.

There is information about: Gateway IP, DNS Name, Last Seen (this information explains when was the last time the player checked in live), O/S, RAM, Disk, CPU, Rebooted (when was the last time this machine was rebooted), Up time (what is the time that the machine is running actively), Physical location, Time zone, Player version, AMT Capable, Average speed (the average speed of download), Live download speed, Sync Percentage, Call interval (what is the interval in seconds that the CM Player should check in with the CampaignManager).

In the top of the channel settings is placed the section for selecting channel and screen orientation for the player.

In the Connection Settings there are three settings that we can set.

We can set the time that the player checks back (contacts) the CM service and the zusa’s background color. This applies when the media is not covering the whole screen of the player, and the rest will be with the specified background.

In the Display Settings we can set Watermark to the screen and resolution. If the Custom watermark radio button is selected, an image can be chosen and its opacity on the screen.

The General Settings section in the CM Player configuration is made of two subsections.

The Network Settings is made of the Connection Settings and the Network interface section. Under the Connection Settings we can set the settings if we are using Node Server, Proxy Server or to enable external trigger events.