SyncSign Infrastructure Overview

The SyncSign infrastructure is composed of 4 parts:

  • Calendar System for Booking

  • SyncSign Server (SaaS Cloud / On-Premise)

  • SyncSign Hub

  • SyncSign Node (Display or Sensor)

../_images/syncsign_system_blocks_diagram.png

Calendar System

The calendar system is what you are currently using for managing the reservation of your meeting rooms. As SyncSign will use your existing booking system, you can continue working as usual and additionally use the SyncSign Displays as a new way to interact with your meeting room resources. SyncSign supports connector types such as Google Calendar (Google Workspace), Office 365, and Exchange.

Note

An on-premise server must be installed to support Exchange Server. The SyncSign SaaS Cloud doesn’t connect to the Exchange Servers.

SyncSign Server

The SyncSign Server allows the administrator/user to:

  • Manages all devices (e.g., hubs and nodes) status, and handles OTA updates

  • Sign in the booking system and authorize the access to the calendars

  • Associate each SyncSign display with a room agenda calendar

  • Configure the parameters (e.g., language, locale, LOGO, templates, …)

SaaS Cloud

With SyncSign SaaS Cloud, the cloud service receives calendar event data through the authorized calendar API and processes it to generate the device-ready Display layout. Depending on the selected template, the rendered layout may contain event information such as the meeting subject, organizer, time, location, or attendee information. SyncSign does not maintain a separate database or long-term archive of the source calendar or event records. The rendered Display layout is cached for up to 7 days solely so that the most recently rendered schedule can continue to be displayed during a temporary calendar-service interruption. The cached information is not used for analytics or any purpose unrelated to providing the SyncSign service.

On-Premise

With SyncSign On-Premise Server (SOPS), calendar event data is retrieved, processed, and rendered within the customer’s network. Event details are not sent to SyncSign SaaS Cloud. Only an Event Updated notification passes through the cloud service to notify the SyncSign Hubs that refreshed content is available.

SOPS is the bridge between the booking system and the SyncSign Hubs/Displays. It can be installed as a standalone hardware device or virtual machine within the company’s infrastructure.

SyncSign Hub

The SyncSign Hub serves as the bridge between nodes and the selected SyncSign Server. It manages multiple nodes, such as Displays and sensors, receives update notifications and rendering content, and delivers that content to the appropriate nodes.

SyncSign Node

The nodes are battery-powered and cable-free. They utilize BLE wireless communication technology to transmit data to the hub.

Under usual circumstances, the hub sends rendering messages which contain texts, images or shapes to the SyncSign Display, and the display then can render them onto the screen. The SyncSign Display does not store the content of the rendering information.

The sensors report their latest state to the SyncSign Hub, the hub gathers the data and upload to the SyncSign Server for analytics.