What is Remote CMS? Remote CMS Base System What can Remote CMS Do? Display Outputs Scheduling and Automation What's Included? How Do I Connect? Device Connection Options
Display Output Types Live Content Schools Parking Systems Retail Applications Safety Displays Scoreboards Third Party Integration Ticker Displays Video Systems
User Licensing Device Internet Connection Enterprise Licensing
Contact Us General Concepts Technical Information User Manual Training Videos
About Use Cases Pricing Support Login

Access training videos online and subscribe so you never miss an update


General Concepts

What is a CMS?

CMS stands for "Content Management System", a type of software (typically a website) that provides a user interface for creating and editing content for publication. Web blogs, video hosting sites and news websites are all examples of different types of CMS. Remote CMS in comparison manages a network of Devices that connect to embedded inputs and outputs.

What is a Device?

A Remote CMS device is an embedded computer system that connects to Remote CMS over an internet connection to be remotely controlled. The CMS sends instructions to the device including the schedule calendar and which documents to display on connected device outputs. The device updates the CMS with monitoring information, sensor readings, and information about connected hardware inputs.

What is a Device Input?

An input is a source of data that connects to the device and provides asynchronously updated information. There are a variety of inputs, that can be passive simple sensors like temperature and humidity; or active control systems like an array of parking counters, switching relays, control buttons, or a thirdparty control device. When input states are reported to the device, they update the CMS with that information for monitoring. Additionally, the device can have scripts that respond to the information with configurable actions. For example, a device with a parking counter may display the number of available car parks until a specified number has been reached, then display a "full" message.

What is a Device Output?

An output is a presentation component that connects to the device. Typically, an output is a digital display (e.g. an LED sign, an LCD panel, or an array of LED panels), but can also be an audio device (e.g. a scoreboard siren, fire alarm or school bell). A device output plays documents that have been created specifically for that type of output.

What is a Document?

A document is a self contained unit of display content, with specialised editors for any type of output or display. For example, a document may be a text frame with pages of text formatted with different fonts, widgets, colours and layout; or a media frame with images, video, text and shapes arranged within the display.

How does Scheduling Work?

The device is always running. Using the device schedule means you can specify what the device should do on certain days, certain times, or specified dates. For example, a device can be scheduled to display daily content all day, from Monday to Friday, and also display specific content for 9am - 5pm on those same days; and then override this with a custom display for public holidays. Once the schedule is set, no further interaction is required and the device will operate accordingly.

What is a Widget?

A widget is a display element that is included in a document to provide live and dynamic content; that is, it will update automatically without needing manual intervention. A widget can be as simple as a digital clock, the current date, the number of days until Christmas, the current temperature, or more complex elements like a weather forecast, a customisable analogue clock and so on.

What is a Script?

Scripting is an optional module that allows the creation of "scripts", which are a simple but powerful macro system that can be used to automate events. A script consists of a number of conditions and a number of actions. When the conditions are all met (e.g., "If the temperature is > 35 degrees, and it is a week day"), all of the actions will be executed ("Display the document 'Warehouse is closed', and email the relevant information to 'employees@example.com'"). Scripts may also have zero conditions, which means they are "manually activated". A manually activated script is triggered at the push of a button on the CMS.

What is Media?

Media is any multimedia file that is uploaded to Remote CMS, such as images, animations or videos. Images and videos can be any resolution (provided they fit within the upload limit) and are inserted into media frames to fit the connected output display. Remote CMS accounts have an allocated amount of storage space called a "Media Library". More storage space can be provided as an add-on for your Remote CMS subscription.

What is a Module?

Remote CMS is a modular system. This means that the features of a device can be pared down to only a simple display with no schedule, scripts or media - or it can have more modules installed to extend functionality for systems with complex requirements. With a basic display system (e.g., a single LED sign pylon), standard modules are always available such as scheduling and monitoring.

What are Remote CMS Applications?

Modules that add interactivity to a device are called "applications". An application can be activated, which takes over control of the device for a specific purpose overriding all other schedules, scripts and displayed content. When the application is closed, the device returns to its regular behaviour. An example of an application is "Scoreboard", where an LED advertising display can be turned into a scoreboard for a variety of indoor or outdoor sports and competitions. The Remote CMS device takes care of scores, game times, siren, team names and so on. The scoreboard can be operated via the Remote CMS website or by a handheld controller. While a game is running, promotional documents can be played for events like displaying "Goal!" or advertisements that play on loop. When the game is over, the scoreboard is deactivated and the device resumes normal operation.

Technical Information

The following information is relevant to technical professionals and developers who require specifications for security and network capabilities, or may be interested in third-party development and integration with Remote CMS systems.

Remote CMS Requirements

Remote CMS requires a modern web browser complying to HTML5, CSS3 and EcmaScript 5 standards. This covers every major web browser across all platforms and devices manufactured or updated after 2017. Remote CMS is tested on Apple Safari, Google Chrome, Mozilla Firefox and Microsoft Edge.

Alternative web browsers should be compatible, but they are not explicitly supported by Remote CMS.


Security is a primary concern for Remote CMS. As such, we emphasise these principles:

  • HTTPS - Remote CMS requires HTTPS (HTTP encrypted with SSL) for all connections, between the user/web browser and CMS; and between the CMS and the device.
  • Minimal Connectivity - communication between the device and Remote CMS operate over standard HTTPS, meaning devices can operate without issue on locked down networks so long as www.myrcms.com.au is accessible via port 443.
  • Secure Authentication - account passwords are never stored in plaintext and securely salted and hashed. Two-factor authentication (email or SMS) are available where required.
  • Regular Updates - devices receive regular security patches and updates to ensure security and stability.
  • Paper Trail - changes to content, devices and settings are logged for auditing. This allows group administrators to track user activity when delegating access to users.
  • Data Compliance and Security - Remote CMS uses Microsoft Azure technologies Web Services, SQL Server and Azure Storage. These services are all hosted in New South Wales, Australia. Third party web services (e.g. Open Weather data) are accessed through strictly controlled API requests and are not permitted access to internal data or functionality.

Device Specifications

Remote CMS devices run a customised Linux distribution on a range of hardware options depending on size and environmental constraints.

Network Connectivity

Remoet CMS devices require an internet connection to operate. In the case of a network disconnection, the device will continue operating with the most recent configuration.

The following network connection types are available:

  • Ethernet / WiFi - static IP or DHCP. Devices can be connected via existing infrastructure, provided www.myrcms.com.au on port 443 is accessible. The third party DNS servers at and are supplemented to provided DNS servers.
  • Mobile Networks - an industrial modem connects the device to a 4G mobile network. Remoet CMS can provide a SIM card for the Optus or Telstra network, or a BYO SIM card can be used. Relevant charges apply, RCM Systems is not responsible for network interruptions or poor signal quality due to the selected 4G network. 3G mobile connectivity is no longer offered, and 5G mobile connectivity may be explicitly requested.

Third-Party Development

Remote CMS provides an array of web APIs for connectivity depending on the required functionality, for integration into external systems.

The Remote CMS developer API consists of two access keys, which are used to authenticate access via a unique URL and using HTTP Basic Authentication. API access is limited to only the functions subscribed, and will expire when the subscription is ended. Unauthorised use of the API will result in the access grant being immediately revoked, and potentially a cancellation of all Remote CMS services.

Online documentation for the Remote CMS API can be accessed here. With a Remote CMS API subscription, a sample utility for assisting development is provided, and will include documentation specific to the API functions granted.

Additionally, external web APIs can be accessed from Remote CMS using

General Concepts and Terminology Technical Information for Developers and IT