Understand the Layarva Object Model

Core hierarchy

Workspace
├── Locations
├── Channels ── Screens
├── Library ── Assets and Fonts
├── Studio Designs
├── Playlists ── immutable Playlist Versions
├── Publications ── Playlist Version → Channel
├── Schedules ── timed Publication rules
├── Campaigns ── Placements → generated Schedules
└── Queue Units
    ├── Categories
    ├── Counters and Operators
    ├── Kiosks
    └── Queue Displays → Channels → Screens

Distribution chain

The most important chain is:

Design or media → Playlist draft → Ready Playlist Version
→ Publication → Channel → one or more Screens

A Channel is the distribution unit. A Screen follows one Channel; publishing directly to an individual Screen is not the normal delivery model. Ten televisions showing the same content can share one Channel and remain ten separate Screens.

Mutable and immutable boundaries

Object	Mutable?	Purpose
Design	Yes	Editable Canvas document.
Playlist draft	Yes	Editable item sequence.
Playlist Version	No	Exact sequence used for delivery and reporting.
Publication	No	Exact Playlist Version assigned to a Channel.
Schedule	Yes	Timing rule that activates an immutable version.
Campaign Draft	Yes	Commercial plan containing Placements.

Players never resolve a mutable Playlist draft at runtime. Publishing first pins the exact Ready version.

Workspace and Location timezones

Layarva uses two timezone concepts:

Workspace timezone controls how dashboard readers interpret and display dates and times.

Location timezone represents where the Screen physically operates. It controls local playback-day boundaries and reporting dates.

For example, an Admin in Jakarta can read the dashboard in Asia/Jakarta while a Screen in Makassar uses its Location timezone for the day on which a playback event is counted.

Queue isolation

A Queue Unit is an isolated branch operation. Its Categories, Counters, Operators, Kiosks, Displays, API credentials, and ticket sequence cannot be mixed with another Queue Unit.

Queue content has additional structural rules:

One Queue Design belongs to one Queue Unit.

A Queue Playlist contains exactly one Queue Design with a 24-hour duration.

Queue Channels and Displays must remain inside the same Queue Unit chain.

Overview

Workspace administration

Getting started

Layarva Studio

Screens

Layarva Edge

Queue Management

Operations and reporting

What you’ll accomplish

Core hierarchy

Distribution chain

Mutable and immutable boundaries

Workspace and Location timezones

Queue isolation

​What you’ll accomplish

​Core hierarchy

​Distribution chain

​Mutable and immutable boundaries

​Workspace and Location timezones

​Queue isolation

​Related guides

What you’ll accomplish

Core hierarchy

Distribution chain

Mutable and immutable boundaries

Workspace and Location timezones

Queue isolation

Related guides