The following tips and tricks have been compiled to help you ensure a smooth digital signage implementation and maintenance.
Committee driven projects tend to experience ‘drag’ and a loss of productive hours resulting in additional time resources and expense. As a best practice, designate a central team of individuals responsible for each key area of responsibility. They can delegate as necessary.
|Project Manager (all projects)||A single point of contact for the overall project and any required documentation/deliverables.|
|IT/Network/Systems Engineer (all projects)||Will coordinate with the FWi System Engineer for network/systems access/questions.|
|Creative Team Member (projects w/ creative)||Responsible for the branding/creative assets and coordinates with the Signage Architect and Creative team.|
Keep everyone informed, from the core administrative team to individual content contributors. Create a ‘listserv’ email group for all users/contacts involved in the digital signage project, including FWi team members (PM, CSA, Sales Rep). This allows the team to stay connected with each other through an e-mail distribution list and ask the group questions as a whole. It’s much better for long-term management solution to utilize your in-department/on-campus knowledge base before contacting FWi support.
If you’ve purchased a campus wide site license, keep FWi informed of your independently staged rollouts. Let us know how many signs you are adding, access credentials for new machines, new users/team members, etc. This will go a long way in helping us better support your system. Simply call or email your dedicated Customer Service Manager that will be assigned at the conclusion of your implementation.
While it will always be a suggested step to back up your DB prior to upgrade/migration, it is also a good best practice to set up regular database backups in case of network/hardware failure. This is especially true if there are significant changes made (layout/template changes, new functionality incorporated, etc.). If you have a backup of the Content Manager DB, it’s much easier to get back up and running if any of these circumstances were to occur.
It’s a good best practice to create an FWi file/folder for the users to access (when needed). There is a lot of information (software links, license keys, Release Notes, invoices, etc.), that customers tend to refer back to for future reference. Having this information easily accessible for your current users as well as any new users that might become involved with your DS system is extremely helpful.
Four Winds Interactive has developed on online wiki for reference. All FWi documentation (Release Notes, Player Requirements, Best Practices, etc.), are being made available there. All users and IT contacts involved in the FWi project should have a wiki account. Register your system for access.