Creating Optimal Digital Signage CMS Workflows

Creating Optimal Digital Signage CMS Workflows

The typical digital signage content management system is like a blank canvas that you can approach in many different ways. Before we tackle workflows, let’s start by exploring what a CMS is and what it does.

What is a CMS?

CMS stands for content management system. It’s digital signage software that lets you perform a multitude of digital signage related tasks.

  • Upload content files to a backend server. Files can be animations, videos, images, presentation decks, or links to external resources such as web pages, data feeds or video streams.
  • Assign attributes to content, including duration, transition effects, tags, and other properties.
  • Schedule content using playlists or rule-based scripts.
  • Deploy content to a network of media player devices and smart TVs.
  • Remotely manage media player devices and track their performance.
  • Track content playback and generate proof of play reports.

Advanced CMS software products offer additional features that let users automate certain processes. Some, like Navori Labs’ QL software, include tools that let users create digital signage templates within the app. QL Mobile is the company’s remote content management UI that lets team members interact with the system using smartphones or tablets.

The content management system is the heart of every digital signage deployment. Users interact with the system over an internet connection via a graphic interface. It’s important to look at all available features before choosing the CMS that is right for you.

Digital Signage CMS - QL mobile GUI

Types of CMS software

There are two basic types of content management systems.

  • Cloud-based or SaaS — software is hosted and maintained by a service provider.
  • On-premise — software is purchased and installed on a local or hosted server.

Those who opt for a cloud-based version pay a monthly fee per media player while on-premise software buyers purchase permanent licenses for the CMS server and each media player they deploy. There are pros and cons to each option depending on the customer’s profile.

You’ve picked your CMS, what comes next?

Let’s say you already have a CMS or have decided on which one you will use. It’s time to start planning for what comes next.

Ask yourself:

  • How will my teams get things done as efficiently as possible?
  • How do we prevent costly mistakes?

At first glance, using a CMS can seem daunting. In the beginning, your team will need training and support to get up to speed. It pays to spend some time setting up the system so your people are productive from day-one.

Here are some suggestions:

  • Organize your media players in groups based on their physical location, intended use or any other criteria that is relevant to your operations.
  • Assign user-friendly names to your players and content. Avoid cryptic naming conventions that can confuse team members. In the long run, it will help when onboarding new users or when you require assistance from external support teams.
  • Take note of your hardware serial numbers and cross-reference this information with device names you have assigned. Keep a database of all deployed equipment for future reference.
  • Spend some time learning about meta tags and other time saving features. Make sure the entire team is on-board and implement these features right from the start.
  • When creating user accounts for your team, make sure you assign user roles that are based on each person’s responsibilities.
  • Not all team members need access to every player group and subgroup. Create domains that only provide access to the assets each team members need. If someone works out of a branch office, give them access to their own location’s players and any other level that hosts content they will need.
  • If your organization has implemented active directory or single sign-on, activate this capability in the CMS. This will simplify user authentication.
QL Player Monitoring

Managing your CMS assets

Content management systems can manage many types of assets.

  • Content files (images, videos, PDFs, presentation decks).
  • Links to web pages, data feeds and streaming video sources.
  • Templates and tickers created in the CMS itself.

Here are some tips to optimize your content management.

Think global and local

When organizing your player groups and subgroups, remember that each level has its own content library. The library at the top, or root level, is where you should store content that you want to share across the entire organization. Content you store at the root level can be made accessible to any team member.

If you want to be efficient, don’t duplicate your content. Instead, re-use the same assets multiple times. Store your reusable content at or near the root level and control access so only authorized team members can use these assets.

Create master templates for your teams

If you want to implement a particular corporate look or branding, look no further than master templates. These templates are meant to be duplicated and modified by individual team members. They can be personalized to serve different locations or uses throughout the organization.

You can store master templates at the root level or on any level above the one where your media players are assigned.

Here’s an example. A franchised organization stores it’s master templates and other global content at the root level of their CMS network so franchise operators can copy the content down to their local group so they can customize it for their own needs. If this is a template menu for a restaurant chain, the local store operator will be able to customize the menu without impacting other franchisees.

The same technique can be applied to any type of business or organization.

Merging playlists for smarter workflows

Playlists follow the same logic as content. When a playlist is created in a global level, it becomes available to every sublevel below. You can share these playlists or restrict access as needed.

Playlists that are created in a sublevel where players are assigned are deemed local and can only be played on those players.

When you overlap global and local playlists in your schedules, you merge their content. This  creates some interesting opportunities. Take for example a team member in charge of content for an entire organization who manages global programming. They add or delete content in a global playlist.

Meanwhile, local teams manage their local programs and their media players show a mix of global and local content. Everyone can focus on their own assignments independently.

This approach also lends itself to situations where you have multiple teams managing different types of content. One playlist could be made up of informational content while the other playlist is made up of advertisements. You end up with a combined program that blends both types of content.

Merging playlists also provides for a more organic content flow since there are less repetitions in your programming.

QL Content Management System GUI

Additional CMS tips

  • Mix global and local playlist or media zones in your templates for more flexibility.
  • Hide playlists from non-authorized users to preserve content integrity.
  • Use global content to reinforce your branding and corporate identity standards.
  • Implement custom user roles with permissions that match each team member’s responsibilities.
  • If your organization requires it, use protected groups with content authorization rules that require a manager or designated team member to sign-off. Whenever a staff member requests authorization, the content manager will receive an email with all the details. This will ensure no unauthorized content is ever shown on-screen.

About Navori Labs

Navori Labs’ QL digital signage CMS delivers all the features growing businesses need. QL supports multi-level, multi-user management for any size organization. The software is available in cloud and on-premise versions for maximum flexibility.

Want to find out more? Click here for more details.