Notices that expire
The single thing a corkboard cannot do.
Electronic bulletin board
The corkboard,
without the drawing pins.
Every building has a board covered in notices, half of them expired. A published board carries a date, comes down on its own, and looks the same in every building you run.
Plans, prices and trials are set by your ScreenQube partner.
Where it ends up
You work in a browser.
They see the wall.
The screen above is what you publish. This is where it ends up.
How it is made
What is actually behind it.
Named against the product's own modules rather than invented for a marketing page.
-
A notice is a composition
Written once, arranged once, published to the boards that should carry it.
-
With an end as well as a start
Publish carries the schedule, so an expired notice removes itself.
-
Per building, per department
Facilities keep sites apart; groups keep publishing rights apart.
-
On record
Audits shows who put a notice up, and who took it down.
What you get
Six things it does today.
More than one publisher
Users belong to groups, so it is not one person's job.
Templates reused
Notice layouts live in the library and are reused.
Per site
Publish targets the facilities you choose.
An audit trail
Created, updated and deleted, with a name against each.
A dark board is counted
Total Disconnected Screens on the dashboard.
Who runs this
The industries that ask for it.
Nearby
Solutions that go with it.
Questions
The things people actually ask.
Can departments post their own notices?
Users belong to groups, and groups decide what a person can reach.
Can a notice be dated to disappear?
Publish sends a composition on the schedule you set.
Can we run one board per floor?
Yes. Screens belong to facilities, and Publish targets the screens you choose.
What runs on the board?
An Android player app on a display you own.