Question 1

What is a digital signage CMS?

Accepted Answer

A digital signage CMS (content management system) is the platform that lets you design, schedule, and broadcast visual content to physical displays — TVs, kiosks, lobby screens, video walls — from one central web app. A modern signage CMS like Zeour GRAVIA does five things: a canvas-based layout editor where you design what each screen shows, a content library where you upload videos / images / web tiles, a playlist + schedule engine that decides what plays when, an emergency-broadcast layer for overrides, and a real-time player runtime that streams to every device with sub-second update latency.

Question 2

How does GRAVIA digital signage work?

Accepted Answer

Five steps. (1) Design a layout in the canvas editor — drag video, image, text, YouTube, weather, clock, RSS, QR, social, or chart components onto the layout canvas, whose resolution you set per layout (1920×1080 by default; portrait and video-wall sizes supported). (2) Upload media to the content library (every file is antivirus-scanned before serving). (3) Create a schedule targeting specific displays, screen groups, floors, buildings, or departments — with day-of-week + time-window filters and priority. (4) Each physical display runs the player runtime, paired via a display-scoped API key over an authenticated real-time connection; schedule changes hit the screen in under a second. (5) Play-history telemetry captures every item completion; a 30-second sweep flags any offline display before anyone notices.

Question 3

What content types can run on the displays?

Accepted Answer

GRAVIA supports 15 component types out of the box: Text, Image, Video, WebView (any URL), YouTube (embedded), Clock, Weather, Shape, Container, nested Playlist, QR Code, RSS Feed, Countdown, Social Media, and Data Visualization. You can mix them freely on one layout — for example, a video background with a transparent weather widget in the corner, an RSS news ticker at the bottom, and a countdown to a scheduled event in the top-right. The canvas editor handles per-component positioning, z-index, rotation, opacity, animations, and per-component config (text content, YouTube URL, weather location, countdown target, RSS source, etc).

Question 4

What hardware can run as a display?

Accepted Answer

Anything with a modern web browser. The player runtime is a long-running web page, so you can use Android STB / TVs, Linux mini-PCs, BrightSign / ChromeOS, Windows IoT, smart TVs with a browser, or Zeour's own GRAVIA06 industrial Android signage controller (quad-core Cortex-A55, 4K UHD, HDMI + VGA, PoE-powered, Android 11). The runtime detects video stalls and falls back automatically via the built-in HealingVideo component, so a flaky network never leaves a screen blank.

Question 5

How does multi-screen scheduling work?

Accepted Answer

Schedules in GRAVIA target one of five levels: a single Display, a Screen Group (flat orthogonal grouping), a Floor, a Building, or a Department. Each schedule has a start date, end date, time window, day-of-week filter, and priority value. When two schedules overlap, the higher-priority one wins. Each schedule plays a Layout, a Playlist, or both layered together. The engine resolves the active schedule per screen in real time — change a schedule in the dashboard and every targeted screen refreshes within a second.

Question 6

How does emergency broadcasting work?

Accepted Answer

GRAVIA ships with a first-class Emergency model with four severity levels (Alert, Warning, Critical, Info) and the same five targeting levels as Schedules. When an admin activates an emergency, every targeted player is notified in real time and overrides its current playback within 5 seconds. The override stays up until you deactivate it. Use cases: fire/medical alerts in hospitals, security incidents at corporate sites, weather warnings at airports, runtime takeovers for breaking news at retail HQs.

Question 7

What happens if a display goes offline?

Accepted Answer

Three safeguards. (1) The player runtime caches its last-known schedule + media locally, so a brief network outage doesn't blank the screen — it just keeps playing what it already has. (2) When connectivity returns, the player reconnects with exponential backoff and reconciles to the latest schedule automatically. (3) Server-side, a 30-second sweep marks any unresponsive display as offline and broadcasts the status change to the admin dashboard — so you see the problem before a customer does. The offline sweep can also run as a standalone scheduled watchdog.

Question 8

Can I run YouTube, weather, clock, and RSS feeds together on one screen?

Accepted Answer

Yes — that's exactly what the canvas editor is for. A typical lobby layout might have a video background filling the top 70%, a weather widget in the top-right corner, a clock in the top-left, an RSS news ticker scrolling along the bottom 10%, and a QR code at the bottom-right for a feedback survey. All 15 component types coexist on the same canvas with full control over position, z-index, rotation, opacity, and per-component animations. The Layout itself can be paired with a Playlist that rotates the central video element on a schedule.

Question 9

How is content updated on the screens?

Accepted Answer

Three paths, all real-time. (1) When you upload a new media file, it's antivirus-scanned, then every player using that media is notified — screens refresh within a second. (2) When you change a schedule, every targeted screen is notified and re-renders. (3) When you activate an emergency, every targeted screen overrides within seconds. No truck rolls. No USB sticks. No manual sync. Media is served via signed, time-limited URLs so cached browser content can't be replayed past its expiry.

Question 10

Cloud SaaS or on-premise — which do customers pick?

Accepted Answer

Both are available. Most commercial deployments (retail chains, hospitality groups, corporate campuses) pick the managed cloud edition for speed of pilot and zero ops overhead. Regulated environments — banks, hospitals, government ministries, defence, and operators with strict data residency — go on-premise so all media and operational data stays inside the customer's perimeter. The application is identical in both modes; the only structural difference is mandatory 2FA in cloud mode and the multi-tenant DB layout.

Question 11

Is GRAVIA Digital Signage GDPR / HIPAA / PDPL compliant?

Accepted Answer

The platform is engineered to meet GDPR (EU / UK), HIPAA (US healthcare display content), PDPL (Saudi Arabia, UAE), and ISO 27001 controls. Media is served over signed, short-lived URLs so cached content can't be replayed. Every upload is antivirus-scanned. Per-display API keys are hashed at rest and compared safely. Account lockout (5 failed attempts → 15 min), mandatory 2FA in cloud mode, role-based access, cross-tenant audit logging, and hardened security headers close the technical surface. On-premise deployments keep every byte inside the customer's data centre.

Question 12

How does Building → Floor → Department targeting work?

Accepted Answer

GRAVIA models the physical estate the way a real organization is structured: Buildings contain Floors (unique per building + floor number), Floors contain Departments. Every Display is mapped to one of those levels. Screen Groups are a flat orthogonal layer for ad-hoc bundles (e.g. "All cafeteria TVs across the campus"). When you schedule content, you target whichever level makes sense — one schedule can drive every floor in every building, or just one display in one department. Role-based access lets a Building Manager only see their site and a Department Manager only see their department's screens.

Question 13

Can I use floor maps to visualize screen placement?

Accepted Answer

Yes. Upload a floor plan image per floor; place each display visually with x/y coordinates. The admin dashboard shows a live map with each display dot colored by status (online / offline / playing / emergency). Click a display to see its current schedule, playlist, last heartbeat, and playback history. This is the fastest way to spot a problem in a 200-screen estate.

Question 14

How is media security handled?

Accepted Answer

Every media file is antivirus-scanned before it can be served. Files are stored outside the web root. Media URLs are signed and short-lived (a few minutes by default, configurable) — a signed URL is replay-resistant and time-bound, so a leaked URL stops working before someone can copy and abuse it. Per-display API keys are display-scoped, hashed at rest, compared safely, and rate-limited.

Question 15

How does account security work?

Accepted Answer

Email-and-password sign-in with hashed credentials and signed sessions, plus mandatory 2FA in cloud mode via TOTP (Google Authenticator, Authy, 1Password, etc.). Account lockout after 5 failed login attempts (15-minute auto-unlock). Password reset is short-lived-token-based, never stores the token in plaintext, and is rate-limited. The audit log captures login attempts and cross-tenant access attempts. The dashboard never returns a player API key after creation — only a hint of the last few characters.

Question 16

How long does deployment take?

Accepted Answer

A single-site pilot with a handful of screens, one layout template, and a simple schedule typically goes live in 2 to 3 weeks: 1 week of discovery (hierarchy design — buildings, floors, departments, groups; content sources; emergency policy), 1 week of configuration and layout design, 1 week of UAT plus training. Multi-site rollouts use the same templates and add ~1 week per wave. Custom integrations (queue management overlays, kiosk content, ERP-driven menu boards) extend the timeline; our partner network sizes each engagement up front.

Question 17

Can GRAVIA integrate with our existing systems?

Accepted Answer

Yes. GRAVIA exposes a full REST API for content, displays, schedules, playlists, layouts, emergencies, users, roles, dashboard, analytics, play history, floor maps, social media, RSS, weather, and more. Real-time consumers can subscribe to live event streams. Typical integrations: queue management overlays (GLARUS QMS), kiosk content sync, wayfinding maps, ERP-driven menu boards, weather + traffic APIs, AD / SSO for user authentication, BI tools (Power BI, Tableau, Looker) consuming play-history and analytics. Custom integrations are built by the Zeour partner network.

Question 18

Does it integrate with the rest of the GLARUS platform?

Accepted Answer

Yes — and that's often the reason customers pick GRAVIA over a standalone signage CMS. Queue Management ticket calls drive overlays on lobby TVs in real time; self-service kiosks share branding and ticket templates; visitor management updates meeting-room TVs the second a reservation is checked in; wayfinding maps are pushed to lobby screens with the same content pipeline. One central CMS, one operator experience, one audit trail — across queue, kiosk, signage, wayfinding, visitor, and feedback.

Question 19

Is GRAVIA suitable for high-stakes lobbies like banks, hospitals, and airports?

Accepted Answer

Yes. The platform is engineered for high-availability signage operations. HealingVideo retries stalled HLS streams automatically. SmartPlay falls back to Playlist → Clock so a screen never goes blank. 30-second OFFLINE sweep flags problems before anyone notices. Emergency broadcasts override any current content in 5 seconds across any subset of screens. Role-based access keeps the system locked down across multi-site estates. On-premise deployment with private database keeps content sovereign for regulated industries.

Question 20

How does GRAVIA pricing work?

Accepted Answer

Cloud customers subscribe per-display per-month with continuous updates, multi-region failover, and a 99.9% uptime SLA — billed monthly or quarterly. On-premise customers buy a perpetual licence (sized per building / per display tier) plus annual maintenance (typically 18–22% of licence) covering updates, security patches, and SLA support. The application is identical in both modes; the deployment topology is a configuration knob. Hardware controllers (GRAVIA06 signage controllers, LED panels, RS485 hubs) are priced separately as a one-time bundle, scaled to your screen estate. WhatsApp / SMS / weather / RSS / social-media data feeds run on your own provider accounts — we never mark up third-party costs.

Digital Signage System

Comprehensive Digital Signage

Understanding Digital Signage — Built on the GLARUS GRAVIA CMS

Key Functionalities

Canvas WYSIWYG Layout Editor

15 Component Types

Content Library with Folder Tree

Playlist + Schedule Engine

Emergency Broadcast System

Building → Floor → Department Hierarchy

Floor Maps with Visual Screen Placement

Real-Time Player Pipeline

SmartPlay Fallback + HealingVideo

Play-History Telemetry + Analytics

Display Pairing + Lifecycle

Multi-Tenant Isolation

Software Components

Operator Dashboard

GRAVIA CMS Dashboard

Canvas Layout Editor

Analytics + Play History

Player Runtime

Long-Running Player Page

HealingVideo Fallback

Offline Mode + Reconnect

Real-Time & API Layer

Authenticated Real-Time Pipeline

REST API

Display API Keys

Security & Compliance

Authentication + 2FA

Media Security

Audit Logging

Hardened Security Headers

Operations & Tooling

Standard Process Management

Maintenance Tasks

Secret Rotation

Hardware Components

GRAVIA Signage Controllers

GRAVIA06 (GLARUS Signage Controller)

IPTV06VI (IP Video Encoder)

Counter & Lobby Displays

SSD06 (LED Counter Display)

SSD066 AHW (LCD Counter Display)

Self-Service Kiosks

GLARUS Kiosk (KIOSAPP066)

AUTO Free-standing Self-Service Kiosk (AUTO666-HW-L-AD)

Branch & Power Infrastructure

CONT06 Industrial Branch Server

Glarus_Hub (PoE Power Distribution)

Digital Signage Architecture — GLARUS GRAVIA CMS

Tier 1 — Player Runtime

Tier 2 — Central CMS (Cloud or On-Prem)

Tier 3 — Operator Dashboards & Editors

Real-Time Update Pipeline

Digital Signage CMS vs USB Sticks vs Consumer Apps vs Enterprise — What You Need

GRAVIA Digital Signage CMS (Enterprise)

USB Stick / Sneakernet

Consumer Signage App

YouTube TV / Home-Brewed Browser Display

Digital Signage System — Deployment Checklist

1) Discovery & Hierarchy Design

2) Central Setup & Content Library

3) Display Pairing & Floor Mapping

4) Schedule Activation & Emergency Setup

5) Optimize, Measure & Scale

Digital Signage System Gallery

Why USB-Stick Signage Fails

USB-Stick Content Updates

One-Click Updates Across the Estate

Single-Tenant Toy CMS

Multi-Tenant + Hierarchical Targeting

No Real Emergency Override

Emergency Broadcast in 5 Seconds

Network Blip = Black Screens

Zero Blank Screens — HealingVideo + SmartPlay + Offline Cache

No Telemetry, No Accountability

PlayHistory + Analytics — Prove the Impression

No Audit Trail, No Compliance