When a fresh-from-the-factory BrightSign player is unboxed, it cannot do much without first being configured.
Configuring a player is the process in which a Setup is applied to the player. The Setup applies various settings to the player (network settings, logging, etc.) and includes a Player App which provides instructions for what the player should do upon startup.
Provisioning
Provisioning specifically refers to using BSN.cloud to configure a player. Given that BSN.cloud (either the Control Cloud or Content Cloud tiers) is used the vast majority of time to configure players, the term provision is often used when referring to player configuration.
The primary cases where a player might be configured instead of provisioned (i.e., BSN.cloud is not used to configure the player) are:
Standalone player configurations where the Setup is manually copied to a storage device and then the storage device is connected to a player.
Uncommon situations where a partner chooses to configure players without using BSN.cloud.
Given that BSN.cloud is the primary method of configuring players, the term provision is very often used to refer to the process of configuring a player.
Setup
A Player Setup establishes various settings for the player that include things like network settings, player identification (name and description), logging, and more. One of the most important player settings is the Publishing Mode which defines the method of content delivery to the player. Various Publishing Mode options exist and more info can be found here.
Setups can be created in BrightAuthor:connected or the aforementioned free and unbranded Control Cloud at control.bsn.cloud. Setups can be saved to a library, modified, and applied to other players.
Once created, Setups can be applied to a player or group of players using either BrightAuthor:connected or control.bsn.cloud. Alternatively, the information contained in a Setup can be directly incorporated into the Player App (described below) and manually copied to the player’s storage device.
Partners also have the ability to use our APIs to connect their CMS directly to the Control Cloud, enabling their CMS, rather than the Control Cloud, to function as the user interface for player provisioning.
More info about Setups can be found here and more info about provisioning can be found here.
Player App
The set of files and folders that instruct the player what to do upon boot up is collectively known as the Player App. At a minimum, the Player App must contain an autorun.brs file (the .brs extension denotes a BrightScript file) which instructs the player what to do upon startup.
When a Setup is applied to a player via BSN.cloud, an autorun.brs file is automatically created on the player.
Partners can write custom Player Apps according to their specific needs. For example, the Player App may be designed to connect to the partner CMS to download content from the CMS for the player to display.
The term Partner App may sometimes be used when referring to the partner’s Player App.