Specifications
An overview of the system architecture, runtime requirements, device and exhibit integration, operations, and delivery boundaries.
Product architecture
| Layer | Components | Responsibility |
|---|---|---|
| Experience | Desktop, tablet, and phone clients | Present areas, exhibits, scenes, workflows, and alerts by role |
| Business | Areas, device groups, scenes, workflows, schedules | Turn device capability into understandable venue operations |
| Control | Local edge gateway, task queue, state probing | Execute actions on the venue network, handle timeouts, report results |
| Device | Lighting, AV, power, environment, exhibit hosts | Provide the final control capability and feedback |
Deployment and runtime
| Item | Specification |
|---|---|
| Gateway | Edge gateway host (Raspberry Pi CM) or customer-supplied PC |
| Clients | Chrome / Edge with WebAssembly support; desktop, tablet, and phone browsers |
| Client delivery | Web, PWA, Android, iOS, and Windows; implementation, guides, and operations share the same configuration and interaction logic |
| Interface configuration | Project-specific pages, areas, buttons, sliders, status cards, and media controls; layouts remain adjustable after delivery |
| Exhibit hosts | Windows industrial PCs; the remote player also runs on Linux and ARM Linux |
| Network | Venue local network; control and content do not depend on public internet |
| Offline operation | Sign-in, control, opening and closing routines, and status checks work without internet |
| Licensing | Licence file bound to the gateway hardware fingerprint |
Device integration
| Category | Typical devices | Integration |
|---|---|---|
| Power and relays | Power sequencers, multi-channel relay modules | Modbus TCP / RTU with per-channel control |
| Building automation and environment | HVAC and environmental monitoring devices | BACnet; integration details depend on the device and project configuration |
| Lighting | Dimming modules, lighting controllers, Borneo-IoT lighting products | Vendor open interfaces; Borneo-IoT products join through the shared device model |
| Projection and display | Projectors, projection edge-blenders, LED walls, video matrices | PJLink or vendor open interfaces |
| Audio | Audio processors, amplifiers | Vendor open interfaces |
| Playback and exhibits | Remote video player, photo waterfall wall | Common device protocol (CoAP over UDP + JSON) and HTTP content endpoints |
| Other exhibits | Electronic sand tables, interactive screens, signature walls, addressable LED strips, and more | Power, lighting, or vendor interfaces, managed by area and scene |
Standard exhibits
Common standard exhibits are listed below; custom exhibits can also be integrated per project.
| Exhibit | Description |
|---|---|
| Remote video player | A playback host driven from the control room: playback, volume, and progress are sent remotely, and media files are uploaded over the network. |
| Photo waterfall wall | An interactive image and video waterfall; visitors tap to focus, and content is re-ordered and published from the console. |
| Electronic sand table | A physical sand table built from a touch host, projection, and addressable LED strips: the touch host handles interaction, projection renders the scene, and the strips follow content and scenes. |
| Interactive screen | Touch all-in-one interaction, scheduled together with areas and scenes. |
| Signature wall | A terminal where visitors leave a handwritten signature and photo, with content following the current event theme. |
| Addressable LED strip | Segment-addressable strips that run dynamic light effects with exhibit content and scenes. |
| Other exhibits | Custom interactive installations, mechanical models, lighting installations, and more, integrated through the same device model. |
Operations
| Capability | Description |
|---|---|
| Areas and device groups | Split by location, group by purpose, switch in bulk |
| Scenes | Package multiple device actions into a single action |
| Opening and closing | Run device actions in sequence, with emergency power-off |
| Schedules and exceptions | Weekly automatic routines; holidays and ad-hoc events take priority |
| Health diagnostics | Availability, probe results, error messages, licence status |
| Content maintenance | Upload, order, push programmes; exhibits keep local copies |
| Roles | Guide, customer administrator, super administrator |
| Event log | Control and execution results are recorded for traceability |
Delivery boundaries
Delivery is organised around the equipment list, network topology, role matrix, scene scripts, and acceptance records. Integration, binding, control configuration, probing, and commissioning form a complete path from an equipment list to an operable exhibit.
Devices without an open control interface can only provide an operator prompt or a state record. Professional content production, deep device commissioning, and special vendor services remain with the relevant specialist team. Supported devices and performance targets are defined by each project configuration.