A district with three hundred panels across twelve campuses rarely fails because a screen breaks. It fails because nobody can tell which panel in room 204 went offline last Tuesday, or which firmware a campus is running. This article walks through what Riotouch DMS does, module by module, using the platform's own operation manual as the only source. It is written for integrators, distributors and IT leads evaluating a fleet.
DMS is a cloud console built on DaisyOS that puts interactive flat panels scattered across campuses and cities into one place: accounts and permissions, device registration, grouping, remote control, live monitoring, file and application distribution, firmware OTA, teaching resources and reporting. A single dashboard supports up to 5,000 devices.
Devices register with a MAC address plus OEM, model, region and device type, and appear in the console once registered. Two deployment models exist: public cloud SaaS, and an OEM white-label edition with a custom domain and multi-tenant structure. It runs on AWS, Azure, Alibaba Cloud, Huawei Cloud, Tencent Cloud, or on-premises. Panels and their audio devices share one backend, so speakers need no second system.
Five permission levels narrow as they descend. The guardrail worth knowing: only the cloud administrator deletes devices and manages OTA packages, so a reseller cannot remove a school's devices by accident.
| Level | Role | What it can do |
|---|---|---|
| 1 | Cloud administrator | Sub-accounts, device deletion, OTA firmware packages, global configuration |
| 2 | OEM / reseller | Device management, firmware and OTA, app store management (OEM accounts do not distribute applications) |
| 3 | School administrator | Courseware upload, device control, message notification, screen lock, scheduled power |
| 4 | Teacher | Courseware, quizzes, file transfer to devices in own class |
| 5 | Student / parent | Class replay and online quizzes, read-only |
A group can be built by city, school or grade, or along the campus to building to grade to class hierarchy. The point is batch execution: one command applies to every device in it at once. Before a term you push applications to a whole campus; during exams you lock one grade's screens with a click; for holidays you schedule power per group.
Power group: shutdown, restart, factory reset. Screen group: lock and unlock, child lock, screenshot, online inspection. Parameter group: backlight, volume, input source switching, scheduled power on and off, and interface language. All of it completes inside the browser, with no site visit. Factory reset is restricted to the cloud administrator.
Monitoring has three capabilities: a real-time screen view as a thumbnail stream, camera inspection snapshots, and online status. These touch classroom privacy, so grant them only to school administrators, with the scope written into the contract rather than left to habit.
Remote testing gives three self-tests: touch, camera and microphone. Their value is after-sales. When a customer reports that touch is not accurate or the camera will not open, the test runs first and separates a hardware fault from a firmware or network problem before anyone books a flight. On the microphone test, the manual notes that an improvement is already scheduled, so treat it as a helper rather than a verdict.
Distribution covers files, APK push installation, and an app store that allocates by device, group or category with automatic installation at the receiving end. Teaching material reaches the devices of selected classes in batch instead of being copied from a USB drive room by room.
Firmware OTA is how a fleet stays current: upload a package and push it by device, group or category. Each package records its model, name, version, update type, upgrade type and the time it was added, so you can see what a campus runs. Pilot one group, confirm nothing anomalous, then go fleet-wide.
Workflow automation chains up to nine preset commands and runs them in sequence: shutdown, restart, alarm, message, lock or unlock, backlight, volume and input source. Routine maintenance becomes one click instead of a checklist.
Above the device layer sits the teaching stack: resources archived by subject and grade; courseware marked public or private; an editor that adds hotspots for images, video, links, audio and questions; 3D courseware through the Umind environment with OBJ and other supported formats; built-in resources such as PhET simulations and the periodic table; and AI generation of courseware, quizzes and word cards by subject, grade, language and length, to be reviewed by a teacher before use.
The smart pick-up module runs on QR codes: a location generates its code, parents scan it on arrival and enter the fixed pick-up code, and the configured speaker plays the targeted announcement, for example that a class has been dismissed. The school must have speakers configured for that last step.
Six categories of metrics: user activity, device status split into online, offline and abnormal, usage trends, application usage, online device ranking and the device growth curve. Together they answer the three questions a procurement committee asks a year later: which devices nobody uses, which applications were installed and never opened, and at what pace capacity should grow.
| Job | Without a console | With DMS |
|---|---|---|
| Pushing a new app to one campus | USB drive, room by room | One command to the campus group |
| Locking screens for an exam | A person walks the corridor | One click on the grade group |
| Firmware on 200 panels | Engineer on site, per unit | Upload once, push by model or group |
| Diagnosing "touch is not working" | Ship a replacement, then test | Run the touch test and read the result first |
| Reporting usage to the board | Manual counting | Six metric categories already recorded |
No. It manages Riotouch interactive flat panels and LED displays with their audio devices. It is a device management system for our panels, not a brand-agnostic tool.
Up to 5,000 devices per dashboard. Larger deployments are split by tenant or OEM account.
No. The standard edition is public cloud SaaS; on-premises is possible, on AWS, Azure, Alibaba Cloud, Huawei Cloud or Tencent Cloud.
No. A teacher account manages only its own classes, and pushes files only to devices in them.
No, and it is not positioned as one. It manages panels, their firmware and their teaching layer; policies for laptops and general IT endpoints belong to another class of tool.
Julia | International Sales Manager | Riotouch Technology
julia@riotouch.com | WhatsApp +86 158 1773 7671 | www.riotouch.com
Riotouch DMS runs on cloud.daisyos.ai. Feature availability follows the release notes for your account.
Tell us what you're looking for and we'll tailor a quote to your requirements — with pricing, lead time, and expert advice.