Commercial LED Lighting & Sign — Mini Sign CO.,LTD

Basic Requirements of One Customized LCD Display System

Aug 23

adminLCD Display System, Project Examples Display Management, display system, LCD Dislayer System, lcd display, LCD Display Software, LCD Net Series 2 Comments

Basic Display Management and Server software requirements:

The objective of the screen/device management software is to provide CaerVision with a single location to actively manage all screens in the network. The software needs to include the ability to create and deploy playlists, manage display content, deploy content and report on the content played at each location. CaerVision expects to rapidly grow to a network of 100,000 screens and the software should be able to scale accordingly. The list below is a list of current requirements provided as a basis for discussion and review of available packages.

1. Software needs to be capable of managing up to 100,000 simultaneous devices

Our backend is a distributed system, it’s possible to extend the capability according to the requirements.

1. Software needs to be able to run on a Windows platform

Our system is a wholly Web based system, all operations can be done through IE (or other standard web browser) running on Windows.

1. Operator client can be local install as well as basic available via web interface.

You can log on and use the service as long as Windows had been installed on your PC.

1. Software needs to be able to group devices

Yes. The device can be organized for independent media content distribution.

1. Software needs to be able to manage devices as group or single devices

We recommend to use group only for media content distribution to simplify the layer concept. To avoid and conflicts, currently we enforce that one device must belong to one group for content distribution.

1. Groups need to be able to be assigned to operators. Operators can only see and administer the screens in their groups.

It can be done.

Many customers in China want to manage multiple groups, because in many cases, the playlist and corresponding content are required to be applied to multiple groups.

1. Software Administrator can assign devices to groups and assign groups (one or more) to operators.

Yes.

1. Software needs to provide for different levels of operator security and functionality

Yes. Currently we have 3 levels:

1. Administrator: for system administration.

2. Operator: Of playlist and program schedule design.

3. Audit: Program schedule needs to be approved before issuing.

4. Customer: Check the statistic and report for their own content issuing.

1. Software needs to report when devices fail to connect to server via email/text message/on-screen (color coding)

Yes.

1. Software needs to allow for tuning of individual devices to prevent too many false alarms.

The device can be suspended or revoked to avoid the above situations.

1. Software needs to have the ability to perform a remote reboot on a device

Yes.

1. Software needs to be able to report all basic details (software version etc) about the device.

Yes. The working status of the device can be reported periodically.

1. Software need to provide the operator with an interface to quickly upload new content to a content library

Yes.

1. Software needs to be able to provide operator with ability to preview content

Can be done in the later version.

1. Operator needs to be able to see what is playing on the screen at any time (in real time) via remote control

The detail of media content playback status (including start time, executive result, device ID will be transferred to the backend periodically (the duration can be set on the backend).

1. Software needs to allow operator to develop a playlist from the available content

Yes.

1. Software needs to allow operator the ability to publish a playlist to a specific or group of devices

Yes.

1. Software needs to be able to accept playlists from external sources (ie CSV or XML)

Besides network connection, the playlist can be updated through external USB device, a XML file will be used for updating the schedule, playlist and relevant content.

1. Software needs to display a calendar of playlists for the device reaching into the future (so that future playlists and media can be loaded ahead of time)

Yes. 2 program schedules can be designed and released, one as current schedule which is running on the device now, one as a pre-downloaded schedule for future.

1. Each device will have defined on/off times for playlists (working hours). The player should only update media during non working hours.

Yes.

1. Software operator needs to be able to force an update of the screen with new content (this will override previous requirement on a one time basis)

Sorry! Not quite understand this requirement, would you please let know more information?

1. Server software needs to be able to store all media files to be played by device

Yes. But the content need to be downloaded to the certain devices in advance before playback.

1. Media server should be a separate server (Windows based) in order to be able to scale for demand but is managed from software

Yes. The media server is distributed.

1. Server software needs to support pushing of media playlists to groups of devices based on business rules (ie time of day for push etc)

Not quite understand the details of the “business rule”

Many kinds of business rule can be defined in the playlist, multiple templates can be selected for different business rules.

1. Software needs to report and display download status for all players/files in live time and on demand reporting

Yes.

1. Server software needs to include content management ability to create playlist based on business rules including clinic type, zip code, user special content requests.

I’ll appreciate if you can give me more information of the business rule.

1. Server software needs to provide the operator with the ability to update on/off times of the device

Yes.

1. Server software needs to provide the operator the ability to set additional properties (ie phone number, contact information etc) per device

Current, we only reserve a field called “description” which can be used to put all additional information. It’s no problem to extent the properties as you desire.

1. Software needs to be able to report media that has been played by device by period of time (ie month, week etc) – proof of play report.

Yes. As I mentioned on No. 15, many kinds of information of the devices and content will be collected, reports can be made as we want.

1. Software should be able to report whether the device volume has been muted

The volume of the device can be adjusted individually, it’s no problem to pop up a message to alarm the user that the device is muted.

1. Software needs to be able to define business rules for when to display, or not display, content based on current playlist (for example, if media 1 then display media 2 and do not display media 3).

Many kinds of rules had been done on the backend and device, but we preper to know more about the business rules.

Server hardware

1. Please provide recommendations on server hardware required to manage and support up to 10,000 screens; 25,000, 50,000 and 100,000 screens.
2. Please provide guidance on media server specifications.
3. Please provide information on operating system and database software requirements for management and media servers.