Scenario Overview

In this scenario, a broadcaster operates a centralized production facility or campus, but without the need to distribute signals to external regional studios.

Instead, the focus lies on enabling flexible signal exchange between multiple internal tenants, such as:

  • Different TV program brands
  • Radio and TV departments
  • Independent production units or editorial teams

These tenants may operate logically separated environments, even though they share the same physical infrastructure.

Operational Challenge

The main requirement is to enable controlled, flexible, and often temporary signal sharing between tenants, while maintaining a clear separation of responsibilities and resources.

Typical drivers for such workflows include:

  • Multi-purpose production environments
  • Temporary production setups
  • Event-based collaboration across programs

The degree of separation between tenants (technical, operational, or organizational) heavily influences the exact implementation.

Implementation Using Stream Share App

The Stream Share App (SSA) provides an ideal mechanism to support these requirements, particularly when dynamic and on-demand signal exchange is needed.

Depending on the operational model:

  • Dedicated SSA instances can be created for specific tenant-to-tenant exchanges
  • Each SSA acts as a controlled interface layer between otherwise separated environments
  • Flows are exposed via NMOS and can be selectively consumed by other tenants

This approach ensures:

  • Clear ownership of signal provisioning
  • Controlled visibility and access
  • High flexibility in reconfiguration

Multi-Purpose Production Environments

A common application is the use of shared production spaces, such as:

  • Studios
  • Recording rooms
  • Foyers or event areas

These environments:

  • Are equipped with production hardware
  • Are not permanently assigned to a specific tenant
  • Can be dynamically allocated to different productions

Workflow

  • When a production starts, the required resources are assigned to a specific tenant
  • An SSA is used to expose and connect the relevant signals between the shared infrastructure and the tenant’s environment
  • After production ends, the configuration is easily dismantled by stopping or reconfiguring the SSA instance

This enables a clean, temporary association of resources, without long-term configuration overhead.

Temporary Inter-Program Signal Sharing

Another frequent use case involves temporary signal exchange between different program units.

Examples include:

  • Election coverage
  • Major sports events
  • Special cultural broadcasts

In these scenarios:

  • Signals may originate from a central ingest point or remote production setup
  • The same signals may need to be simultaneously distributed to multiple tenants

Using SSA:

  • A single SSA instance can aggregate incoming signals
  • These flows can then be shared with multiple tenant systems in parallel
  • Each tenant can independently route and use the signals as needed

Key Benefits

  • Flexible, on-demand signal exchange between tenants
  • Support for temporary and event-driven workflows
  • Clean separation between operational domains
  • Efficient use of shared production resources
  • Centralized control combined with decentralized consumption

Involved Lawo Products

  • Lawo HOME with NMOS Exporter
  • Lawo HOME Apps

Required other Products

  • NMOS Registry (1 per remote site, e.g. Lawo HOME)

Required setup

  • Network links (eg. 100G, 200G, 400G) between involved systems.
  • Friendly address ranges (reachable, no duplicates)

More useful Information

  • Manual Lawo HOME (link)
  • Manual Lawo HOME NMOS Exporter (link)
  • Manual Stream Share App (link)