8Software requirements#

8.1Remote Sign Control System (RSCS) software#

The requirements defined in MRTS201 General Equipment Requirements apply to this Technical Specification. Additional requirements are provided under this Technical Specification are described below. The RSCS may be used on site or via a location which is remote to the roadwork site. The RSCS, control and monitoring shall be hosted on an operating platform, such as Microsoft Windows®, which is industry standard at the time of application of this Technical Specification. Any software provided must be capable of operating on all such operating systems. The software may be web-enabled and display the location of the managed TVSL signs on a GIS layer which has up-to-date maps and associated geographic or spatial information. The software shall allow the default speed of a TVSL sign to be selected from a list. The software shall only allow the setting of speeds that are below or equal to the default speed – i.e., the current speed combo box type selection object will only be populated with permissible speed entries that are below the default speed for that TVSL sign or site. The software shall allow for single Master / multiple Slave TVSL sign deployments that are required under a TGS to be fully controlled and monitored. Each traffic control direction TVSL deployment shall be completely separate to the opposite traffic control TVSL deployment. That is, for a bidirectional traffic flow, there shall be one SRC only for each direction, which controls only one arrangement of TVSL signs. Under no circumstances shall one SRC control both directions of traffic. This software shall not permit any administration of the pre-programmed TVSL site deployment.

8.1.1Software user interface and security#

The RSCS, control and monitoring software user interface shall be such that user access is controlled through username and password logon credentials. The following types of user accounts shall be provisioned for in the RSCS software user interface:

1. a)Administrator: For user access management and full access to all features of the TVSL RSCS, control and monitoring software user interfaces.
2. b)Standard user: For conducting general operating functions as defined by the Administrator account (clearing alarms, blanking the sign and other administrator authorised functions).

The factory default user credentials shall not be used and these shall be changed prior to any operation of the TVSL sign(s). Passwords shall be generally in accordance with IS18.

8.2TVSL configuration / maintenance software (via direct connection)#

The TVSL sign shall only be able to be programmed through the use of factory supplied configuration / maintenance software through a direct connection. The software shall be installed and run on laptop or other HMI device which is directly connected to the TVSL sign via the dedicated maintenance port. Prior to any configuration of a TVSL sign's DP, the respective LFS switch shall have the "Blank Display" mode selected. The primary functions of this software shall be, but not limited to:

1. a)Allowing the required initial setup of a TVSL sign (including, but not limited to, Master and Slave pairing configuration, configuration of PF, SRC administration functions such as removing lost SRC units and replacing with other SRC via SRC IDs).
2. b)Perform any periodic maintenance and diagnostic functions required during the life of the product (including, but not limited to, reporting and extraction of fault / event logs, internal health statuses of internal TVSL sign components such as Battery, Solar Panel, other I/O statuses, connection states for Master / Slave, SRC / Master, RSCS / Master communications).
3. c)Configured to request passwords as part of the signs controller access and configuration authorisation process.
4. d)Able to present to the user a graphic image of the DP and the signs connected to it with icons or features that indicate whether there are any alarms or faults on any of the devices.
5. e)Prompt the user to confirm a change to the DP's mode of operation.
6. f)Capable of suggesting ranges for each parameter as applicable when programming and not allow these limits to be exceeded.
7. g)Have a test program to facilitate testing of all the essential sign features, including ability to activate, deactivate all pixels and vary LED brightness. Capability to display and store on file a mimic of the sign showing defective LEDs is required, and
8. h)The software must allow querying of events according to set criteria, such as by sign(s), time, date, event type or by duration.

8.3Configuration management#

All software configuration changes shall be date and time stamp logged and included with the username of the software user who made the configuration setting change.

All firmware or software required for the TVSL sign, SRC or RSCS shall be fully backwards compatible.

All software associated with the use of TVSL shall allow the saving of existing configuration settings for backup.

The saved backup settings file shall be able to be used to restore previously saved configuration should this be required.

8.3.1Device Processor (DP) configuration#

All settings in the DP, including settings included in Appendix A and PF, shall be accessible using the configuration software.

The configuration shall be site-specific and must ensure that only the DP with the correct configuration for the respective TVSL site is allowed to control its respective TVSL site.

The site PF and other user configurable settings shall be stored in non-volatile memory.

Prior to the application of any software configuration change, a backup of the existing configuration shall be copied and stored in non-volatile memory.