Vendor access
This part is for Aigna staff
Vendors see their own installation and the device reference they need to build it: device types, setup guides and models. Everything else stays with Aigna.
Go to your installationModule
Assets is switched off
Device types, units, models, setup guides, standards, IT stores and cables. This demo has the Assets module switched off in Organisation settings.
Setup guideSignage playerSignage cloudFirmware 9.1.151Simulated
XT1145 signage player, BSN.cloud managed
Every unit in use matches itchecked just now
Configuring happens in a project's Deploy page
Each device is provisioned, installed, configured in this setup order and commissioned there, ticked off with who and when. This page is the standard it follows.
No project is configuring it now. Every project
On the units running it
- Units in service
- 18
- Records drifted
- None
A practice run. A new install, in order. Ticks stay on this browser. The real run is ticked device by device in a project's Deploy page.
0 of 6Aigna registers every BrightSign player in BSN.cloud and sets its network and time from BrightAuthor:Connected. The Local DWS stays reachable for on-site diagnostics, locked behind its own password, and OS updates are applied manually once the Lab has passed them.
BSN.cloud registrationBSN.cloud
- SetDevice NameThe hostnameMatches DNS, device management and monitoring, so one name finds the player everywhere.source
- VerifySetup file network configurationUse current device settingsKeeps the player's own certificates and network settings intact instead of overwriting them from a generic group setup file.source
Network (BrightAuthor:Connected)BrightAuthor:Connected > Network tab
- VerifyDHCP enabledOn, address fixed by a DHCP reservation rather than a static entry hereAigna's network team reserves the address by MAC in DHCP, so a change to the reservation doesn't need a site visit.source
- VerifyDNS1 / DNS2The site's DNS serversHanded out by DHCP; only checked here, not set by hand.source
- SetTime zoneNetwork tab › Time zoneThe site's time zoneBSN.cloud schedules (content dayparting, OS updates) run in the player's local time.source
- VerifyEnable 802.1x authenticationNetwork tab › Enable 802.1x authenticationOffAigna's AV ports authenticate devices at the switch instead.source
Local DWS (on-site diagnostics)Device web interface (Local DWS)
- SetEnable Local Diagnostic Web ServerBrightAuthor:Connected › player settings › Enable Local Diagnostic Web ServerOnLets an on-site technician reach the player's own diagnostics page without going through BSN.cloud.source
- SetSet PasswordLocal DWS › Control tab › Set PasswordFrom the password vault, per siteThe DWS ships with the admin account but no password; the vendor requires 8+ characters with upper, lower, number and symbol, and Aigna takes it from the site vault rather than leaving it open.source
UpdatesLocal DWS
- SetBrightSignOS UpdateLocal DWS › Advanced tab › BrightSignOS Update (production/beta/custom)Production, applied manually after the Lab passes itThere is no scheduled/automatic update toggle documented for this tab; Aigna applies a release by hand once the Lab has passed it.source
What the vendor's documents don't say (3)
- BSN.cloud's own device-group console isn't publicly documented beyond registration and 'use current device settings'; the day-to-day network and time fields are set from BrightAuthor:Connected's Network tab instead, which pairs with BSN.cloud.
- No documented hostname/domain field on the player itself, only Device Name in BSN.cloud and the Network tab's DHCP/DNS fields.
- No documented scheduled/automatic OS update toggle; only the Local DWS's manual production/beta/custom selector.
Provision is the first step of Deploy: before or as each signage player arrives, every system gets its record, so the device is known the moment it is plugged in. It is ticked in the project's Deploy page; this is what each record needs.
Hostname
<site>-<room>-sigNN
For example dub-301-sig01: the site, the space number without its dot, sig for signage player, and the number in the space. Full name: …aigna.example.
Firmware
9.1.151
9.1.151. Check it before configuring.
Licence and management
No licence named in this setup guide.
Managed in: BrightSign BSN.cloud.
AssetboxAsset register
assets/<asset tag>.json
Needs
- Asset tag
- Serial
- Model
- Space
- Status
- Hostname
Healthy when status is active; space matches where the device is installed.
InfoDNSAddresses and DNS
zones/aigna.example/<hostname>
Needs
- Hostname
- Mac address
- Ip address
Healthy when address reservation matches the MAC address; forward and reverse DNS records resolve.
Fleet LensDevice managementNot used
No record: signage player units are not kept in Fleet Lens.
DarkSignSignage players
players/<hostname>.json
Needs
- Device name
- Serial
- Firmware version
Healthy when online in the vendor's content and device management service; firmware at the fleet standard for the model; settings match the setup guide for the model.
AppStateRoom booking and signage fleet
rooms/<room id>.yaml
Needs
- Room
- Resource
- Device
Monitor DogMonitoring
checks/<hostname>.yml
Needs
- Monitor name
Healthy when reporting; no open critical alerts.
BSN.cloud › BSN.cloud registration
- SetDevice NameThe hostname
- VerifySetup file network configurationUse current device settings
BrightAuthor:Connected > Network tab › Network (BrightAuthor:Connected)
- VerifyDHCP enabledOn, address fixed by a DHCP reservation rather than a static entry here
- VerifyDNS1 / DNS2The site's DNS servers
Network tab › Time zone
- SetTime zoneThe site's time zone
Network tab › Enable 802.1x authentication
- VerifyEnable 802.1x authenticationOff
BrightAuthor:Connected › player settings › Enable Local Diagnostic Web Server
- SetEnable Local Diagnostic Web ServerOn
Local DWS › Control tab › Set Password
- SetSet PasswordFrom the password vault, per site
Local DWS › Advanced tab › BrightSignOS Update (production/beta/custom)
- SetBrightSignOS UpdateProduction, applied manually after the Lab passes it
Where dub-301-sig01 (3.01 Reception, Dublin office) is recorded in each system, against what Keia Atlas expects. Simulated values.-found +expected
AssetboxAsset registerIn sync
# assets/AG-000276.json asset_tag: AG-000276 serial: DEMO-DUB-000276 model: BrightSign XT1145 location: Dublin office, 3.01 Reception status: In service
InfoDNSAddresses and DNSIn sync
# zones/aigna.example/dub-301-sig01 fqdn: dub-301-sig01.aigna.example address: 10.20.3.28 mac: 02:20:89:df:ba:92 reservation: yes
DarkSignSignage playersIn sync
# players/dub-301-sig01.json player: dub-301-sig01 group: Dublin office signage firmware: not tracked
AppStateRoom booking and signage fleetIn sync
# rooms/dub-3-01.yaml room: 3.01 Reception resource: dub-3-01@resource.aigna.example device: dub-301-sig01
Monitor DogMonitoringIn sync
# checks/dub-301-sig01.yml host: dub-301-sig01.aigna.example checks: ping, https alerts_to: av-dub
Fleet LensDevice managementNot used
No record: signage players are not kept in Fleet Lens.
Being configured now
In each project's Deploy pageNo project is configuring it now.
Units running it
18 in service · 0 drifted · simulated check| Unit | Space | Office | Model | Status | Records |
|---|---|---|---|---|---|
| Reception signage playerchi-1201-sig01 | 12.01 Reception | Chicago office | BrightSign XT1145 | In service | In sync |
| Cafeteria signage playerchi-1202-sig01 | 12.02 Cafeteria | Chicago office | BrightSign XT1145 | In service | In sync |
| Pantry signage playerchi-1315-sig01 | 13.15 Pantry | Chicago office | BrightSign XT1145 | In service | In sync |
| Reception signage playercph-401-sig01 | 4.01 Reception | Copenhagen office | BrightSign XT1145 | In service | In sync |
| Pantry signage playercph-402-sig01 | 4.02 Pantry | Copenhagen office | BrightSign XT1145 | In service | In sync |
| Reception signage playerdub-301-sig01 | 3.01 Reception | Dublin office | BrightSign XT1145 | In service | In sync |
| Pantry signage playerdub-302-sig01 | 3.02 Pantry | Dublin office | BrightSign XT1145 | In service | In sync |
| Pantry signage playerdub-415-sig01 | 4.15 Pantry | Dublin office | BrightSign XT1145 | In service | In sync |
| Welcome lounge signage playerdub-501-sig01 | 5.01 Welcome lounge | Dublin office | BrightSign XT1145 | In service | In sync |
| Reception signage playermel-801-sig01 | 8.01 Reception | Melbourne office | BrightSign XT1145 | In service | In sync |
| Pantry signage playermel-802-sig01 | 8.02 Pantry | Melbourne office | BrightSign XT1145 | In service | In sync |
| Reception signage playernyc-2001-sig01 | 20.01 Reception | New York office | BrightSign XT1145 | In service | In sync |
| Cafeteria signage playernyc-2002-sig01 | 20.02 Cafeteria | New York office | BrightSign XT1145 | In service | In sync |
| Pantry signage playernyc-2003-sig01 | 20.03 Pantry | New York office | BrightSign XT1145 | In service | In sync |
| Pantry signage playernyc-2118-sig01 | 21.18 Pantry | New York office | BrightSign XT1145 | In service | In sync |
| Pantry signage playernyc-2217-sig01 | 22.17 Pantry | New York office | BrightSign XT1145 | In service | In sync |
| Reception signage playertyo-1501-sig01 | 15.01 Reception | Tokyo office | BrightSign XT1145 | In service | In sync |
| Pantry signage playertyo-1502-sig01 | 15.02 Pantry | Tokyo office | BrightSign XT1145 | In service | In sync |
| Pantry signage playerjnu-201-sig01 | 2.01 Pantry | Juneau office | BrightSign XT1145 | Being installed | Checked when live |