Appendix DType Approval Compliance Checklist#

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause	Field OR Bench Test
5 Functional requirements
1	The use of the TVSL signs shall be in accordance with Chapter 2 of the Guideline – Traffic Management at Works on Roads (and have the capability of operating as either: • Single units as in Figure 5.1(a), or • a Master and Slave Pair as in Figure 5.1(b) as defined by the approved Traffic Guidance Scheme (TGS).	5.1	X
2	All TVSL system shall have a minimum of 99.9% system operating reliability.	5.2	X
3	The TVSL shall be operated through the listed methods in the Table 5.3 below.	5.3	X
4	Each component carries out specific functions associated with the operation of the TVSL sign and can be broadly categorised into hardware or software as shown in Figure 5.4 and described in Table 5.4.1.	5.4	X
5	The software components associated with the TVSL sign shall typically be as described in Table 5.4.2.	5.4.2	X

Table in words

Item 1: The use of the TVSL signs shall be in accordance with Chapter 2 of the Guideline – Traffic Management at Works on Roads (and have the capability of operating as either: • Single units as in Figure 5.1(a), or • a Master and Slave Pair as in Figure 5.1(b) as defined by the approved Traffic Guidance Scheme (TGS). (MRTS Clause 5.1; Compliance: Other records (Datasheets, internal testing, RPEQ)).
Item 2: All TVSL system shall have a minimum of 99.9% system operating reliability. (MRTS Clause 5.2; Compliance: Other records (Datasheets, internal testing, RPEQ)).
Item 3: The TVSL shall be operated through the listed methods in the Table 5.3 below. (MRTS Clause 5.3; Compliance: Other records (Datasheets, internal testing, RPEQ)).
Item 4: Each component carries out specific functions associated with the operation of the TVSL sign and can be broadly categorised into hardware or software as shown in Figure 5.4 and described in Table 5.4.1. (MRTS Clause 5.4; Compliance: Other records (Datasheets, internal testing, RPEQ)).
Item 5: The software components associated with the TVSL sign shall typically be as described in Table 5.4.2. (MRTS Clause 5.4.2; Compliance: Other records (Datasheets, internal testing, RPEQ)).

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause	Verification Method	Compliance (Y, TBC, N, N/A)	Visual Inspection	NATA Certification	Field OR Bench Test	Detailed Drawings	Other records (Datasheets, internal testing, RPEQ)
6 Technical requirements
6	Each TVSL sign shall have a Device Processor (DP) and it shall: a) conduct all processing associated with the communications support for paired slave sign(s) b) ensure that the requested speeds are displayed on the TVSL sign LED display and carries out all associated processing and monitoring functions c) monitor, log and report the operation of each connected sign display individually d) allow the TVSL sign to be controlled individually or as part of a pair e) be capable of storing up to 255 frames in its non- volatile memory. The full list of frame designations is captured in Appendix C f) command signs to display only the allowable frame combinations for that respective site as defined by the TGS g) allow local automatic reset of sign displays and the DP itself such as via watchdog(s) h) be capable of automatically dimming connected signs based on the average of the light sensor outputs. Automatic dimming of the sign occurs to increase luminance and hence conspicuity. The dimming levels and factory default settings are shown in Appendix A. Automatic dimming is not to be used for the purpose of extending battery life i) accept / reject valid or invalid commands made by the SRC, RSCS, configuration software or connected Master / Slave DPs j) allow a unique electronic identification for each DP to be configured k) electronically verify with the connected sign display that the displayed speed is consistent with the speed originally requested and permitted l) upon power up, ensure the sign LED display shall be initially blank and a valid frame is only displayed after all internal tests have passed, and m) accept an analogue input from a Local Facility Switch (LFS).	6.1					X

Table in words

Item 6: Each TVSL sign shall have a Device Processor (DP) and it shall: a) conduct all processing associated with the communications support for paired slave sign(s) b) ensure that the requested speeds are displayed on the TVSL sign LED display and carries out all associated processing and monitoring functions c) monitor, log and report the operation of each connected sign display individually d) allow the TVSL sign to be controlled individually or as part of a pair e) be capable of storing up to 255 frames in its non- volatile memory. The full list of frame designations is captured in Appendix C f) command signs to display only the allowable frame combinations for that respective site as defined by the TGS g) allow local automatic reset of sign displays and the DP itself such as via watchdog(s) h) be capable of automatically dimming connected signs based on the average of the light sensor outputs. Automatic dimming of the sign occurs to increase luminance and hence conspicuity. The dimming levels and factory default settings are shown in Appendix A. Automatic dimming is not to be used for the purpose of extending battery life i) accept / reject valid or invalid commands made by the SRC, RSCS, configuration software or connected Master / Slave DPs j) allow a unique electronic identification for each DP to be configured k) electronically verify with the connected sign display that the displayed speed is consistent with the speed originally requested and permitted l) upon power up, ensure the sign LED display shall be initially blank and a valid frame is only displayed after all internal tests have passed, and m) accept an analogue input from a Local Facility Switch (LFS). (MRTS Clause 6.1; Compliance: Other records (Datasheets, internal testing, RPEQ)).

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause	Field OR Bench Test
7	Each TVSL sign DP shall be configured to store only those frames permitted to be displayed as defined in the approved TGS for the site in which they are operating (refer the list of frame designations in Appendix C).	6.2	X
8	This will be achieved through the RSCS or configuration software referred to in this Technical Specification.	6.2	X
9	The DP shall ensure that only permitted frame displays in the signs.	6.2	X
10	In addition to the other logged events detailed in Clause 9.1 below, the DP shall generate, log, and report an alarm if a frame display request by the RSCS or SRC is for non-permitted frames.	6.2	X
11	The DP shall allow: a) the configuration and RSCS software to read and write its permitted frame (PF), and b) the display of stored frames only when requested by the SRC or RSCS.	6.2	X
12	This includes the default, maximum and minimum speeds allowed at the respective TVSL site.	6.2	X
13	Where TVSL signs are deployed in a pair, both TVSL sign displays shall only display the same permissible frame.	6.2	X
14	TVSL signs are not required to display lane closure symbols.	6.2	X
15	The minimum display duration of each frame shall be configurable and accessible via the configuration software via the maintenance port.	6.3	X
16	The time range and factory default settings shall be as shown in Appendix A.	6.3	X
17	The DP shall command inner rings of the annulus to flash when speeds other than the site’s default speed are displayed.	6.4	X
18	The outermost ring shall remain on whilst the inner rings are flashing.	6.4	X

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause	Verification Method
19	Where 2 or more signs are connected to the same DP, the flashing elements of all signs at that site must flash in synchronisation.	6.4			X
20	The flash rate and display cycle shall be configurable and factory default settings are shown in Appendix A.	6.4
21	The TVSL sign display and DP must each monitor the state of its respective processor and blank the respective display(s) if processor failure occurs.	6.5			X
22	The DP shall generate an alarm and perform a graceful power shutdown all signs if the integrity of the firmware or configuration is compromised.	6.5			X
23	Each TVSL sign shall be fitted with a GPS receiver.	6.6			X
24	The on-board GPS receiver shall monitor the location in 3 dimensions (Latitude, Longitude and Altitude) of each sign and also synchronise the TVSL DP internal clock.	6.6			X
25	Each TVSL sign shall have provision for the numeric display to be synchronised by means of the sign's DP internal clock and the Master / Slave arrangement.	6.6			X
26	The DP shall provide an alarm if a sign is moved beyond a 30 m radius of its installed position. This may be achieved using a virtual perimeter or “geo- fence”.	6.6		X	X
27	Each TVSL sign may have the ability to discern the installed directional orientation (yaw) and whether any subsequent change in direction has been detected, through the use of a Magnetometer Inertial type sensor.	6.7			X
28	The accuracy of the compass shall be at least – 1 degree of yaw after calibration.	6.7			X
29	An alarm shall be raised should the orientation be changed by – 20 degrees from the installed position.	6.7		X	X
30	Each TVSL sign may have the ability to discern whether the unit’s position has been altered from the installed position through the use of gyroscope.	6.8			X
31	The local method of control is via a hand-held Short- Range Controller (SRC) wireless communications device.	6.9	X		X

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause	Verification Method
32	The following requirements shall apply to the use of the SRC: a) Once TVSL signs have been configured for a particular construction site, they shall be capable of operating with the following modes only: i. Mode 1 Work Mode – During Construction Hours Display ii. Mode 2 No-Work Mode – After Construction Hours Display, and iii. Mode 3 Blank Mode – Blank Display.	6.9			X
33	b) Use “code hopping” or “rolling code” technology to prevent unauthorised use of the signs through methods such as “replay attacks”.	6.9			X
34	c) Have a unique ID (refer to Clause 7.4 below) that is transmitted with each mode change request.	6.9		X	X
35	d) The SRC shall have 3 programmable, and clearly labelled buttons to reflect the above modes, and be visually identified as shown below.	6.9	X		X
36	e) When a SRC mode activation button is pressed and held for 2 seconds, then an LED indication within the button shall be illuminated to confirm to the Site Supervisor the desired mode of operation.	6.9		X	X
37	f) If an SRC mode activation button LED is illuminated and the SRC Transmit Button is pressed and held for 2 seconds a control message shall be transmitted to the Master DP.	6.9		X	X
38	g) Should a RSCS mode change request occur at the same time as the mode change request from an SRC, the SRC mode request shall have priority and the RSCS mode request shall be ignored (refer to Table 5.3 TVSL Control Methods).	6.9		X	X
39	h) SRC batteries shall last for at least one year without requiring to be replaced.	6.9
40	i) Where a Master and Slave DP pair has been configured, the SRC shall only communicate with the relevant Master.	6.9		X	X
41	j) The DP may have the ability to deactivate a SRC from controlling the TVSL sign (e.g., Due to lost or damaged SRCs) through the TVSL configuration software, RSCS software, and	6.9		X	X

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause	Verification Method
42	k) The physical buttons of the SRC are to be sufficiently spaced apart from each other so as not to prevent accidental incorrect activation.	6.9			X
43	Where 2 signs are installed in a pair, one DP from the pair shall act as the Master controller for both signs and the other as the Slave.	6.10		X	X
44	This shall be achieved through the setting a TVSL sign to operate either as a Master or Slave via the connected RSCS or configuration software described in Clauses 8.1 or 8.2 below respectively.	6.10
45	Where a DP is set to operate in Master mode, all secure remote communications requests from a SRC or RSCS for a configured Master and Slave pair shall be accepted by this DP.	6.10.1			X
46	The DP shall be configured to simultaneously control up to a maximum of 5 slave DPs, each with the same control message including the unique slave DP ids.	6.10.1		X	X
47	Where a DP is set to operate in Slave mode, all remote communications from any SRC or RSCS for a configured Master and Slave pair shall be ignored.	6.10.2		X	X
48	Each TVSL sign shall have a physical Local Facility Switch (LFS) for onsite backup control.	6.11	X		X
49	The LFS will allow the manual setting of the following modes:	6.11		X	X
50	1. “BLANK Display” Mode: Blank the TVSL Sign Display, allow maintenance port connections 2. “Display 40” Mode: Displays “40” on the respective TVSL Sign LED display panel 3. “Display 60” Mode: Displays “60” on the respective TVSL Sign LED display panel 4. “Display 70” Mode: Displays “70” on the respective TVSL Sign LED display panel 5. “Display 80” Mode: Displays “80” on the respective TVSL Sign LED display panel 6. “Display 100” Mode: Displays “100” on the respective TVSL Sign LED display panel 7. “Display 110” Mode: Displays “110” on the respective TVSL Sign LED display panel, and 8. “REMOTE” Mode: Sets the TVSL Sign to accept remote communications from SRC and RSCS.	6.11		X	X
51	Where selection on the LFS has been made, the DP shall wait for 3 seconds prior to activating the selected mode. This will ensure no other mode is inadvertently activated when physically toggling through the available options.	6.11		X	X
52	The DP shall allow configuration of each LFS selection such that only allowable display frames can be invoked per site.	6.11		X	X
53	The physical LFS switch shall be key-lockable to prevent vandalism and unauthorised control.	6.11	X		X
54	When a mode has been activated, the DP shall store the current GPS, compass bearing (if available) and inclination angle (if available).	6.11		X	X
55	These values will represent the installed position for the purposes of the DP detecting and providing notification on any subsequent movement due to unauthorised tampering, vehicular incident, wind, accidents and other reasons.	6.11		X	X

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause
56	"Where BLANK mode is selected on an LFS, the following requirement shall apply: a) Whilst this mode is selected at the particular TVSL sign, any subsequent display requests from a RSCS Software session or SRC device(s) shall be ignored by the DP (applies to Master and Slave)." b) If there is an established RSCS software session, monitoring and alarms from the Master DP shall still be transmitted to the RSCS Software. c) Critical alert SMS-based notifications shall still be transmitted by the DP (applies to Master and Slave). d) The TVSL sign shall remain powered up. e) Activate the dedicated maintenance port (the maintenance port is deactivated in all other LFS modes). f) Where 2 signs have been configured as a Master / Slave pair, selecting the LFS to “BLANK Display” on one TVSL sign shall NOT blank the other paired TVSL sign, and g) The LFS shall be designed as fail-safe operation and as such should it fail or be disconnected, “BLANK Display” mode will be activated. Appendix B summarises the conditions at which the TVSL sign display is blanked.	6.11.1	X	X
57	Irrespective of whether Master / Slave designation, the "Display 40" mode will allow the speed limit of “40” to be continuously displayed on the respective Master or Slave TVSL sign. Only when the LFS mode selector is moved to another position will the sign display be changed.	6.11.2	X	X
58	Irrespective of whether Master / Slave designation, the "Display 60" mode will allow the speed limit of “60” to be continuously displayed on the respective Master or Slave TVSL sign. Only when the LFS mode selector is moved to another position will the sign display be changed.	6.11.3	X	X

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause
59	Irrespective of whether Master / Slave designation, the "Display 70" mode will allow the speed limit of “70” to be continuously displayed on the respective Master or Slave TVSL sign. Only when the LFS mode selector is moved to another position will the sign display be changed.	6.11.4	X	X
60	Irrespective of whether Master / Slave designation, the "Display 80" mode will allow the speed limit of “80” to be continuously displayed on the respective Master or Slave TVSL sign. Only when the LFS mode selector is moved to another position will the sign display be changed.	6.11.5	X	X
61	Irrespective of whether Master / Slave designation, the "Display 100" mode will allow the speed limit of “100” to be continuously displayed on the respective Master or Slave TVSL sign. Only when the LFS mode selector is moved to another position will the sign display be changed.	6.11.6	X	X
62	Irrespective of whether Master / Slave designation, the "Display 110"mode will allow the speed limit of “110” to be continuously displayed on the respective Master or Slave TVSL sign. Only when the LFS mode selector is moved to another position will the sign display be changed.	6.11.7	X	X

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause	Visual Inspection	Field OR Bench Test
63	"Where Remote mode is selected on the LFS, the following requirements apply: a) The Master DP shall accept control communications from a hand-held SRC device (s) only if the SRC device(s) are configured as being authorised to control the respective Master DP." b) The Master DP shall accept control communications from a PC / laptop running the RSCS software over a wireless or hardwired connection. c) The Slave DP shall accept control communications from a configured Master DP if it is configured as part of this Master and Slave TVSL pair. d) The Master DP shall transmit all messages associated with all monitoring and alarming categories under this Technical Specification. e) Critical alert SMS-based notifications shall be transmitted by the respective DP (Master and Slave). f) With the exception of Critical alert SMS-based notifications, where configured as part of a pair, all communications from a Slave DP shall be to its Master DP ONLY.	6.11.8	X	X
64	A separate dedicated maintenance communications port shall be provided at the TVSL Sign DP to allow a PC or laptop running the supplied TVSL sign configuration software to perform all maintenance and diagnostic functions on the respective TVSL sign.	6.12		X
65	The communications port shall be a dedicated 10/100Base-T Ethernet (RJ45) port.	6.12		X
66	If at any time during an existing maintenance port configuration session, an attempt is made to select an LFS mode other than the “Display Blank” mode, then the DP shall ignore the LFS request(s) and provide a visual notification to the maintenance operator such as a popup alarm(s) on the configuration software.	6.12	X	X
67	The DP shall continue to ignore any LFS control mode change requests until such time, the existing maintenance port configuration session has been terminated.	6.12	X	X

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause	Verification Method	Visual Inspection	Field OR Bench Test
68	Disconnection of the configuration software laptop from the maintenance port must not require further interaction from the user, nor in anyway interrupt operation or require rebooting of the DP.	6.12		X	X
69	Upon disconnection of the direct connection between the configuration laptop and the DP, the existing maintenance port configuration session shall be immediately terminated within the DP and “Blank Display” Mode re-initiated.	6.12		X	X
7 Communication requirements
70	The communications system shall be tamperproof and fully enclosed.	7.1.1	X		X
71	Communication between the local DP and LED sign display shall be via a direct wired connection.	7.1.1			X
72	The communications shall be encrypted.	7.1.1			X
73	Messages transmitted between the DP and the LED display shall be completed within 50 ms of being sent. Refer to item 1 in Figure 7.1.	7.1.1			X
74	Communication between the Master, Slave DP(s) and SRC(s) shall be via a local wireless communication technology, such as Ultra-High Frequency (UHF) radio band or other reliable wireless technology.	7.1.2			X
75	Wireless communications shall also be encrypted. Refer to item 2 in Figure 7.1.	7.1.2			X
76	The SRC and Master DP shall communicate with 99.9% reliability over point-to-point ranges of greater than 30 m.	7.1.2		X	X
77	The Master and Slave DP(s) shall communicate with 99.9% reliability over point-to-point ranges of greater than 500 m. This will account for communications to multiple Slave DP(s)—some of which are separated from the Master DP at a maximum distance of 500 m at a site.	7.1.2		X	X
78	Where 2 TVSL signs are configured as a Master and Slave, periodic one-second communications (time- out period) polling messages shall be transmitted for the purposes of establishing whether a loss of communications has occurred.	7.1.2			X

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause	Visual Inspection	Field OR Bench Test
79	When loss of communications has been detected, an alert shall be raised on both signs.	7.1.2	X	X
80	Where a SRC has requested a change of speed on a TVLS sign DP, the speed change shall be completed within 250 ms of the request—i.e., the respective DP’s display shall energise the requested frame LED pixels.	7.1.2		X
81	Any radio frequency communications antennas shall be positioned at the highest point on the TVSL sign to make effective use of available signal gain and avoid line of sight signal attenuation by objects such as concrete barriers and shrubs.	7.1.2		X
82	Communications shall be in accordance with Australian Communications and Media Authority (ACMA) requirements.	7.1.2		X
83	Communications between the configuration software and the DP shall be over a direct 10/100base-T Ethernet connection.	7.1.3		X
84	The communications cable shall be CAT5 and pre- terminated with EIA-568A RJ45 connectors.	7.1.3		X
85	The IP address of the configuration laptop or other HMI device shall be able to be set to the same range of the DP’s maintenance port network address. Refer to Table 7.1.3 for example IP settings.	7.1.3		X
86	Once an initial configuration connection has been established, the IP address settings shall be able to be changed from the defaults.	7.1.3		X
87	If an existing remote RSCS connection is currently in session when the LFS is changed to the “Blank Display” mode, the DP shall provide notification to the RSCS software logged on user that a local configuration connection is in session and any remote RCSC communication control requests will be ignored.	7.1.3	X	X

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause
88	After the local session has been disconnected and the LFS is returned to the “Remote” mode position, any remote session will be immediately re-established (only after an RSCS software confirmation dialog is raised to the RSCS operator for authorisation to proceed with the previously executed TGS plan and associated parameters), all data will be resynchronised between the connected DP (or pair) and RSCS software.	7.1.3
89	During an existing configuration maintenance port session, monitoring and alarms shall continue to be transmitted to the interrupted RSCS Software communications session. Refer to item 5 in Figure 7.1.	7.1.3	X	X
90	There are essentially 2 remote site methods which can be used to allow communications between the DP and the RSCS.	7.2.1
91	The DP, if required by Transport and Main Roads, can be connected to STREAMS.	7.2.1.1		X
92	The supplier of the DP shall ensure that it is fully compatible with the version of STREAMS at the time of delivery and submit a Transmax STREAMS Certificate of Support to Engineering and Technology section of Transport and Main Roads.	7.2.1.1		X
93	Network communications between the DP and STREAMS shall be in accordance with the requirements of MRTS245 ITS Telecommunications Network (ITS TN).	7.2.1.1		X
94	Communication between the DP and a laptop or desktop computer running the RSCS software shall be 10/100 Base-T Ethernet over a connection such as third party wireless 4G / 5G mobile, ADSL or optical fibre.	7.2.1.2		X
95	The carrier selected shall have sufficient and reliable coverage at the project site. Refer to item 3 in Figure 7.1 (TVSL must be compatible with at least one carrier).	7.2.1.2		X
96	The DP shall have a dedicated RJ45 10/100Base-T Ethernet port for the purposes of remote communications to the RSCS.	7.2.1.2		X

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause
97	This port will be used as the primary remote communications connection point for any wireless third-party modem, Ethernet switches or other devices required as per the remote communications design.	7.2.1.2	X
98	All messages transmitted from the RSCS software to the Master DP embedded firmware shall not exceed 5 seconds.	7.2.1.2	X
99	All messages transmitted from the Master DP to the RSCS software shall also not exceed 5 seconds.	7.2.1.2	X
100	Setup and ongoing provision of the mobile service required is the responsibility of the contractor who owns the TVSL sign.	7.2.1.2
101	All insecure protocols services, such as telnet, HTTP, etc., shall be able to be disabled on the DP to prevent any unauthorised communications terminal access to the local DP.	7.2.1.2	X
102	Should maintenance and diagnostic functions be required to be undertaken on the DP, then secure communication protocols such as SSH, HTTPS shall be supported.	7.2.1.2	X
103	Utilising a VPN will ensure that any communications over the internet is secure and unauthorised access is prevented.	7.2.1.2	X
104	All communication over third party communications network shall utilise a secure connection, such as a Virtual Private Network (VPN).	7.2.1.2	X
105	Communication between the DP and a mobile phone for the purposes of the transmission of critical alert SMS notifications as defined in Clause 9.2 below shall be via a third-party SMS mobile service provider with sufficient and reliable coverage.	7.2.2	X
106	For general operations of Master / Slave pair, if a slave does not receive an acknowledgement from the master within one second, the slave shall be blanked. Refer to Appendix B.	7.3	X

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause	Verification Method
107	If the Master does not receive an acknowledgement from the slave within one second of message transmission, then the slave shall be blanked (i.e., a blanking message will be transmitted to the slave). Refer to Appendix B.	7.3			X
108	All timeout periods shall be software configurable with ranges and default values stated in Appendix A. This is required to allow a refinement of timeout periods to reflect current practices and scenarios.	7.3
109	For BLANK display mode, if configuration software session remains inactive for a period as defined in Appendix A, then the user session will be terminated, and the user will need to re-logon and establish another session.	7.3			X
110	If the Master TVSL sign DP detects a loss of communications with the RSCS, then both the Master and Slave shall be blanked.	7.3			X
111	The DP must be capable of monitoring loss of communications with the RSCS and timeout after a specified period.	7.3			X
112	When the Master DP LFS is in the ‘REMOTE’ mode, expiry of this time must cause the DP to blank all physically connected signs (refer Appendix B).	7.3			X
113	This period shall be a configurable parameter and is denoted ‘Session timeout’.	7.3			X
114	The range and factory default settings of session timeout is shown in Appendix A.	7.3
115	The DP must also be capable of monitoring communications with the signs connected to it and timeout after a specified period when such communication is lost.	7.3			X
116	Communications timeout check shall be performed periodically as shown in Appendix A.	7.3			X
117	When the Master LFS is on any other mode, the session timeout check with the RSCS shall be ignored.	7.3			X
118	The SRC, Master and Slave DPs shall each have a configurable unique communications ID.	7.4			X
119	Each Master and Slave pair combination may have a unique site pairing ID for the purposes of communication with the RSCS software.	7.4			X
120	Communications messages between the DPs (Master and Slave) and SRC shall include a checksum unique to each TVSL roadwork site that is based on the message information exchanged to ensure integrity of the communication is upheld.	7.4			X
121	The checksum shall be available for confirmation by the RSCS that the permitted frames at each TVSL site are the same as those stored within the RSCS software.	7.4		X	X
122	The checksum shall be verified periodically and recomputed each time the permitted frames are changed and/or that the DP is reset / rebooted.	7.4			X
123	Each TVSL sign DP shall have a unique factory hardware ID which cannot be changed.	7.4.1			X
124	This ID will be referenced by DPs of other TVSL signs, such as those in a Master / Slave pair arrangement.	7.4.1		X	X
125	Any communications messages transmitted by a DP shall embed the DP’s respective ID.	7.4.1		X	X
126	A physical label displaying this ID must be clearly visible on the TVSL sign trailer / concrete block.	7.4.1	X		X
127	A unique SRC ID shall be configured on a SRC through an on-board settable dipswitch. This ID will be referenced by the Master TVSL DP.	7.4.2			X
8 Software requirements
128	The software requirements defined in MRTS201 General Equipment Requirements apply to this Technical Specification.	8.1			X
129	The RSCS may be used on site or via a location which is remote to the roadwork site.	8.1			X
130	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.	8.1			X

Table in words

Item 107 (MRTS Clause 7.3): If the Master does not receive an acknowledgement from the slave within one second of message transmission, then the slave shall be blanked (i.e., a blanking message will be transmitted to the slave). Refer to Appendix B.
Item 108 (MRTS Clause 7.3): All timeout periods shall be software configurable with ranges and default values stated in Appendix A. This is required to allow a refinement of timeout periods to reflect current practices and scenarios.
Item 109 (MRTS Clause 7.3): For BLANK display mode, if configuration software session remains inactive for a period as defined in Appendix A, then the user session will be terminated, and the user will need to re-logon and establish another session.
Item 110 (MRTS Clause 7.3): If the Master TVSL sign DP detects a loss of communications with the RSCS, then both the Master and Slave shall be blanked.
Item 111 (MRTS Clause 7.3): The DP must be capable of monitoring loss of communications with the RSCS and timeout after a specified period.
Item 112 (MRTS Clause 7.3): When the Master DP LFS is in the ‘REMOTE’ mode, expiry of this time must cause the DP to blank all physically connected signs (refer Appendix B).
Item 113 (MRTS Clause 7.3): This period shall be a configurable parameter and is denoted ‘Session timeout’.
Item 114 (MRTS Clause 7.3): The range and factory default settings of session timeout is shown in Appendix A.
Item 115 (MRTS Clause 7.3): The DP must also be capable of monitoring communications with the signs connected to it and timeout after a specified period when such communication is lost.
Item 116 (MRTS Clause 7.3): Communications timeout check shall be performed periodically as shown in Appendix A.
Item 117 (MRTS Clause 7.3): When the Master LFS is on any other mode, the session timeout check with the RSCS shall be ignored.
Item 118 (MRTS Clause 7.4): The SRC, Master and Slave DPs shall each have a configurable unique communications ID.
Item 119 (MRTS Clause 7.4): Each Master and Slave pair combination may have a unique site pairing ID for the purposes of communication with the RSCS software.
Item 120 (MRTS Clause 7.4): Communications messages between the DPs (Master and Slave) and SRC shall include a checksum unique to each TVSL roadwork site that is based on the message information exchanged to ensure integrity of the communication is upheld.
Item 121 (MRTS Clause 7.4): The checksum shall be available for confirmation by the RSCS that the permitted frames at each TVSL site are the same as those stored within the RSCS software.
Item 122 (MRTS Clause 7.4): The checksum shall be verified periodically and recomputed each time the permitted frames are changed and/or that the DP is reset / rebooted.
Item 123 (MRTS Clause 7.4.1): Each TVSL sign DP shall have a unique factory hardware ID which cannot be changed.
Item 124 (MRTS Clause 7.4.1): This ID will be referenced by DPs of other TVSL signs, such as those in a Master / Slave pair arrangement.
Item 125 (MRTS Clause 7.4.1): Any communications messages transmitted by a DP shall embed the DP’s respective ID.
Item 126 (MRTS Clause 7.4.1): A physical label displaying this ID must be clearly visible on the TVSL sign trailer / concrete block.
Item 127 (MRTS Clause 7.4.2): A unique SRC ID shall be configured on a SRC through an on-board settable dipswitch. This ID will be referenced by the Master TVSL DP.
Item 128 (MRTS Clause 8.1): The software requirements defined in MRTS201 General Equipment Requirements apply to this Technical Specification.
Item 129 (MRTS Clause 8.1): The RSCS may be used on site or via a location which is remote to the roadwork site.
Item 130 (MRTS Clause 8.1): 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.

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause
131	Any software provided must be capable of operating on all such operating systems.	8.1		X
132	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.	8.1		X
133	The software shall allow the default speed of a TVSL sign to be selected from a list.	8.1		X
134	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.	8.1	X	X
135	The software shall allow for single Master / multiple Slave TVSL sign deployments that are required under a TGS to be fully controlled and monitored.	8.1	X	X
136	Each traffic control direction TVSL deployment shall be separate to the opposite traffic control TVSL deployment.	8.1	X	X
137	That is, for a bidirectional traffic flow, there shall be one SRC only for each direction, which controls only one arrangement of TVSL signs.	8.1	X	X
138	Under no circumstances shall one SRC control both directions of traffic.	8.1	X	X
139	This software shall not permit any administration of the pre-programmed TVSL site deployment.	8.1	X	X
140	The RSCS, control and monitoring software user interface shall be such that user access is controlled through username and password logon credentials.	8.1.1	X	X

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause
141	The following types of user accounts shall be provisioned for in the RSCS software user interface: a) Administrator: For user access management and full access to all features of the TVSL RSCS, control and monitoring software user interfaces. Note: For the purposes of site control of the TVSL signs only the Contractors’ Site Supervisor is authorised to undertake such actions, and b) Standard user: For conducting general operating functions as defined by the Administrator account (clearing alarms, blanking the sign and other administrator authorised functions).	8.1.1	X	X
142	The factory default user credentials shall not be used, and these shall be changed prior to any operation of the TVSL sign(s).	8.1.1	X	X
143	Passwords shall be generally in accordance with IS18.	8.1.1	X	X
144	The TVSL sign shall only be able to be programmed using factory supplied configuration / maintenance software through a direct connection.	8.2	X	X
145	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.	8.2	X	X
146	Prior to any configuration of a TVSL sign’s DP, the respective LFS switch shall have the “Blank Display” mode selected.	8.2	X	X
147	The primary functions of TVSL configuration / maintenance software shall be, but not limited to: 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). 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). c) Configured to request passwords as part of the signs controller access and configuration authorisation process. 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. e) Prompt the user to confirm a change to the DP’s mode of operation. f) Capable of suggesting ranges for each parameter as applicable when programming and not allow these limits to be exceeded. 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, 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.2	X	X
148	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.	8.3	X	X

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause
149	All firmware or software required for the TVSL sign, SRC or RSCS shall be fully backwards compatible.	8.3	X	X
150	All software associated with the use of TVSL shall allow the saving of existing configuration settings for backup.	8.3	X	X
151	The saved backup settings file shall be able to be used to restore previously saved configuration should this be required.	8.3	X	X
152	All settings in the DP, including settings included in Appendix A and PF, shall be accessible using the configuration software.	8.3.1	X	X
153	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.	8.3.1	X	X
154	The site PF and other user configurable settings shall be stored in non-volatile memory.	8.3.1		X
155	Prior to the application of any software configuration change, a backup of the existing configuration shall be copied and stored in non-volatile memory.	8.3.1	X	X
9 TVSL sign monitoring, reporting and alarm requirements
156	The DP shall monitor and log the following items in real-time as they occur: a) Log any SRC frame requests of the DP, including the unique identifier of the SRC requesting the speed change.	9.1	X	X
157	b) All RSCS software requests of the DP, including the RSCS username under which the request was made.	9.1	X	X
158	c) Loss of communications with the sign (noting the type of communication—for example, RSCS or Master / Slave).	9.1	X	X
159	d) High internal sign enclosure temperature.	9.1	X	X
160	e) When the TVSL sign is set to blank and the blanking trigger description.	9.1	X	X
161	f) Report the GPS location of the sign from its installed position every 10 minutes.	9.1	X	X

Table in words

Item 149 (MRTS Clause 8.3): All firmware or software required for the TVSL sign, SRC or RSCS shall be fully backwards compatible.
Item 150 (MRTS Clause 8.3): All software associated with the use of TVSL shall allow the saving of existing configuration settings for backup.
Item 151 (MRTS Clause 8.3): The saved backup settings file shall be able to be used to restore previously saved configuration should this be required.
Item 152 (MRTS Clause 8.3.1): All settings in the DP, including settings included in Appendix A and PF, shall be accessible using the configuration software.
Item 153 (MRTS Clause 8.3.1): 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.
Item 154 (MRTS Clause 8.3.1): The site PF and other user configurable settings shall be stored in non-volatile memory.
Item 155 (MRTS Clause 8.3.1): Prior to the application of any software configuration change, a backup of the existing configuration shall be copied and stored in non-volatile memory.
Item 156 (MRTS Clause 9.1): The DP shall monitor and log the following items in real-time as they occur: a) Log any SRC frame requests of the DP, including the unique identifier of the SRC requesting the speed change.
Item 157 (MRTS Clause 9.1): b) All RSCS software requests of the DP, including the RSCS username under which the request was made.
Item 158 (MRTS Clause 9.1): c) Loss of communications with the sign (noting the type of communication—for example, RSCS or Master / Slave).
Item 159 (MRTS Clause 9.1): d) High internal sign enclosure temperature.
Item 160 (MRTS Clause 9.1): e) When the TVSL sign is set to blank and the blanking trigger description.
Item 161 (MRTS Clause 9.1): f) Report the GPS location of the sign from its installed position every 10 minutes.

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause
162	g) Log an alarm when movement has been detected (GPS geo-fence, directional orientation and inclination angle).	9.1	X	X
163	h) LED faults (LED pixel failures).	9.1	X	X
164	i) Initialisation of TVSL (power up).	9.1	X	X
165	j) When an SMS critical alert request has been transmitted by the DP.	9.1	X	X
166	k) Changed state of LFS (i.e., Blank Display, 40, 60, 80 and Remote modes).	9.1	X	X
167	l) Low battery voltage (e.g., Where the voltage of the power supply battery drops to a level that would prevent the battery from being recharged by the charging system).	9.1	X	X
168	m) Loss of solar charge current / voltage.	9.1	X	X
169	n) Loss of load current.	9.1	X	X
170	o) Internal component faults (GPS and other modular hardware components), and	9.1	X	X
171	p) All configuration changes shall include any user credentials associated with the change and respective ID (e.g., made through configuration or RSCS software).	9.1	X	X
172	The log shall identify the sign (through its respective sign ID) and its fault.	9.1	X	X
173	The log shall include the date and time stamp for all entries and may be exported in a readily acceptable format, such as comma delimited text file (.csv), Microsoft Excel (.xls) or other formats as agreed with the project representative.	9.1	X	X
174	Time shall be reported on the log file to centisecond (0.01 s) accuracy or better.	9.1		X
175	The log shall also report the change of fault state. For example, when the fault condition has cleared and subsequently returns to normal operation.	9.1		X
176	The log file storage for the event log shall be sufficient to allow at least 12 months of continuous logging without overwriting.	9.1		X
177	The log file storage shall be in the form of removable non-volatile memory module, such as an SD memory card.	9.1		X
178	The oldest event record shall be overwritten first when the log file storage capacity has been exceeded.	9.1		X
179	For critical faults defined in Clause 9.3 below, the log shall include the RSCS or configuration software username ID which performed the acknowledgement and clearing of the fault.	9.1		X
180	Where a RSCS connection is in session, the RSCS software shall be synchronised and receive updates dynamically from the respective Master DP.	9.1		X
181	Each sign shall be fitted with: a) a yellow flashing light (refer to Clause 10.2.2) on top of the sign, and b) an SMS Mobile Phone Alert system (referred to in Clauses 7.1 and 7.2)	9.2		X
182	Where critical faults occur (SEE 186 BELOW): i. A yellow alert light (refer to Clause 10.2.2 below) on top of the sign shall flash until the fault is cleared through the RSCS or configuration software	9.2	X	X
183	ii. An SMS notification will be sent from the respective DP to pre-specified phone numbers with a clear description of the site, sign ID and a description of the fault.	9.2	X	X
184	iii. If the sign is connected to the RSCS, an alarm shall also be generated on the user alarm monitoring interface.	9.2	X	X
185	iv. The TVSL sign(s) display shall be blanked as shown in Appendix B.	9.2	X	X

Item#	MRTS260 Temporary Variable Speed Limit Signs	MRTS Clause	Verification Method	Compliance (Y, TBC, N, N/A)
186	Critical faults shall include the following: a) Movement of the sign after installation detected through: i. Monitored GPS location of the TVSL sign exceeding the installed location Geo-fence 30 m perimeter, or ii. Monitored Directional Compass position (if available) exceeds installed position by ± 20 degrees (yaw), or iii. Monitored inclination (if available) exceeds installed position by ± 5 degrees (roll or pitch) b) LED pixel faults (refer to Clause 12.6)." c) Low battery voltage level alarm – when the battery level falls to the specified DoD (e.g., indicating insufficient charge or problem with charging circuit). At this stage, the sign shall perform a graceful shutdown down in a controlled manner and as part of the shutdown process due to low power, the TVSL Sign flashing amber light shall be activated on each trailer. d) Charging Voltage too high – when the battery charge voltage exceeds the maximum charge voltage for the selected battery (e.g., indicating a possible battery charge regulator problem). e) If the DP has been requested to display a speed frame greater than what is permitted by the TGS for the TVSL site installation. f) Loss of solar module (e.g., open circuit detected on solar power charging circuit). g) Loss of load (e.g., possible disconnection of extension cable between trailer / concrete block and sign display. h) Loss of communications – where a loss of communications occurs between the RSCS and the DP, then the RSCS software shall raise an alarm to the operator advising that the data displayed may no longer be valid as a result.	9.3