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
Projects is switched off
Projects, the schedule, planning, the work plan and the Lab. This demo has the Projects module switched off in Organisation settings.
Batch 11 of 12 · Project PRJ-19Simulated live
1 BrightSign XT1145 signage player
0 of 1 unit set up · nothing to reviewchecked just now
Setup is done by Aigna's engineers. Your installs are on the Deploy page.
Once for all 1
Through Fleet Lens, the Melbourne office policyNot applied yet. One setup guide sets the shared settings on all 1; 0 can take it now, the rest when they can be reached.
5 settings to set and 4 to check; 0 left at the manufacturer's default.See every settingThe setup guide
The same on every unit
- Enable Local Diagnostic Web Server
- On
- BrightSignOS Update
- Production, applied manually after the Lab passes it
The units
Only what differs per unit. Each unit's build sheet has every setting worked out.Nothing is ready for you here. Keia Atlas keeps checking these units.
| Unit | Hostname | Provision | Install | Configure | |
|---|---|---|---|---|---|
| Build sheet | mel-801-sig0110.70.8.165 | ||||
Setup order
Optional: tick as you go, or let the checks do it1Patch into the space's PoE+ AV port; the player takes its reserved address.0/1
2Enable the Local DWS in BrightAuthor:Connected and set its password before the player leaves the bench.0/1
3Register the player's serial number in BSN.cloud and assign it to the space's device group.0/1
4Set the Network tab's time zone, DHCP and 802.1x settings, or let the group's setup file apply them.0/1
5Check the OS build is the current production release and that no automatic update is scheduled.0/1
6Run the space's verification.0/1
Every setting
9 in the setup guide, as patternsValues marked Per unit are patterns here. Each unit's build sheet has them worked out: mel-801-sig01.
BSN.cloud registration2
- Device NamePer unitSet to The hostnameWorked out on the build sheet
Why
Matches DNS, device management and monitoring, so one name finds the player everywhere.
- Setup file network configurationCheck it is Use current device settings
Why
Keeps the player's own certificates and network settings intact instead of overwriting them from a generic group setup file.
Network (BrightAuthor:Connected)4
- DHCP enabledCheck it is On, address fixed by a DHCP reservation rather than a static entry here
Why
Aigna's network team reserves the address by MAC in DHCP, so a change to the reservation doesn't need a site visit.
- DNS1 / DNS2Check it is The site's DNS servers
Why
Handed out by DHCP; only checked here, not set by hand.
- Time zonePer unitNetwork tab > Time zoneSet to The site's time zoneWorked out on the build sheet
Why
BSN.cloud schedules (content dayparting, OS updates) run in the player's local time.
- Enable 802.1x authenticationNetwork tab > Enable 802.1x authenticationCheck it is Off
Why
Aigna's AV ports authenticate devices at the switch instead.
Local DWS (on-site diagnostics)2
- Enable Local Diagnostic Web ServerBrightAuthor:Connected > player settings > Enable Local Diagnostic Web ServerSet to On
Why
Lets an on-site technician reach the player's own diagnostics page without going through BSN.cloud.
- Set PasswordPer unitLocal DWS > Control tab > Set PasswordSet to From the password vault, per siteWorked out on the build sheet
Why
The 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.
Updates1
- BrightSignOS UpdateLocal DWS > Advanced tab > BrightSignOS Update (production/beta/custom)Set to Production, applied manually after the Lab passes it
Why
There is no scheduled/automatic update toggle documented for this tab; Aigna applies a release by hand once the Lab has passed it.