Welcome, Guest Login

Data Sheet E: Assessment & Implementation of the SnapComms Hosted Solution

Last Updated: Feb 20, 2017 09:15AM NZDT

Data sheet E:
Assessment & Implementation of the SnapComms Hosted Solution


Technology Review

Review of SnapComms technical documentation - This will allow the organization’s technology team to assess the architecture, compatibility and functional elements of the Snap solution. Additional clarification can be obtained from the SnapComms technical team.

Discussions with the SnapComms technical team - Discussions, which can also include online demonstrations and audio conferences, provide a forum for a more in depth investigation of the architecture, network impact and functionality of the Snap solution.

Preliminary Testing

Install the SnapComms client / app on test users’ PCs - A trial instance of the Snap solution is made available to the organization’s technology team in order to test the compatibility of the Snap Client on users’ PCs and to gauge the network impact of communications delivered using the Snap tools.

Review the operational functionality of SnapComms - Access to the hosted instance of the SnapComms Content Manager is provided allowing operational testing of the message creation, publication and download processes including integration with Active Directory and management of users and communications targeting groups.

Assess compatibility and network impact - SnapComms client / app deployment into various environments and review of content display statistics will allow assessment of software compatibility.

Solution Definition

Agree the service level agreement (SLA) terms - Review and discussion around the terms contained within the SnapComms Service Level Agreement. The SLA defines SnapComms responsibilities in terms of providing ongoing support and service.

Specify the required SnapComms client / app configuration - The SnapComms client / app can be configured to reflect the settings required by the organization. These settings are applied when the SnapComms client / app MSI is created and include client-server poll frequency, hiding links on the Message History window and disabling screensaver settings.

Extend testing to a full pilot as required - The organization may wish to extend the initial trial to a full pilot across a wider audience to better gauge the impact and benefit of using the SnapComms tools. Pricing for a pilot can be agreed with your SnapComms representative as required.


SnapComms client / app deployment

Create and configure the SnapComms client / app MSI - SnapComms will create and configure the SnapComms client / app according to needs and specification of the customer and pass the packaged MSI file onto the organizations technical team for deployment out to the desktop.

Test SnapComms client / app connectivity with server - Test client-server connectivity by installing the SnapComms client / app onto various PCs and ensuring published content is displayed on screen and is visible from the Message History. User registration and connectivity statistics should also be visible from the SnapComms Content Manager.

Globally deploy SnapComms client / app to all PCs - Once installation testing has been satisfactorily completed, the SnapComms client / app can be deployed out to the wider organization user-base using any centrally managed application deployment tool as used by the organization.

Ongoing Support

Users and SnapComms client / app software

Single Point of Contact - The technology team, in accordance with the SnapComms SLA, need to nominate a single point of contact to respond to inquiries or issues than may arise from their internal user audience as well as being the primary technical liaison with Snap as may be required from time to time.

SnapComms client / App updates - Updates to the SnapComms client / app software will be advised by SnapComms as soon as they are available SnapComms client / app update release cycles occur every 3 - 4 months. Testing of new SnapComms client / app releases should be undertaken before deployment out to the wider organization.


seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found