SCATS and STREAM Interface Through The SCATS ITS Port

AP-T224-12
AUSTROADS TECHNICAL REPORT
SCATS and STREAM Interface through the

SCATS ITS Port
SCATS and STREAMS Interface through the
SCATS ITS PORT
SCATS and STREAMS Interface through the SCATS ITS PORT
Published December 2012
© Austroads Ltd 2012
This work is copyright. Apart from any use as permitted under the Copyright Act 1968,
no part may be reproduced by any process without the prior written permission of Austroads.
SCATS and STREAMS Interface through the SCATS ITS PORT

ISBN 978-1-921991-64-6
Austroads Project No. NT1724
Austroads Publication No. AP–T224-12
Project Manager
Mark Shotton
Department of Planning, Transport and Infrastructure SA
Prepared by
Dr Clarissa Han and Dr James Luk
ARRB Group
Published by Austroads Ltd

Level 9, Robell House
287 Elizabeth Street
Sydney NSW 2000 Australia
Phone: +61 2 9264 7088
Fax: +61 2 9264 1657
Email: austroads@austroads.com.au
www.austroads.com.au
Austroads believes this publication to be correct at the time of printing and does not accept
responsibility for any consequences arising from the use of information herein. Readers should
rely on their own skill and judgement to apply information to particular issues.
SCATS and STREAMS Interface through the
SCATS ITS PORT
Sydney 2012
About Austroads
Austroads’ purpose is to:
 promote improved Australian and New Zealand transport outcomes
 provide expert technical input to national policy development on road and road transport
issues
 promote improved practice and capability by road agencies.
 promote consistency in road and road agency operations.
Austroads membership comprises the six state and two territory road transport and traffic
authorities, the Commonwealth Department of Infrastructure and Transport, the Australian Local
Government Association, and NZ Transport Agency. Austroads is governed by a Board consisting
of the chief executive officer (or an alternative senior executive officer) of each of its eleven
member organisations:
 Roads and Maritime Services New South Wales
 Roads Corporation Victoria
 Department of Transport and Main Roads Queensland
 Main Roads Western Australia
 Department of Planning, Transport and Infrastructure South Australia
 Department of Infrastructure, Energy and Resources Tasmania
 Department of Transport Northern Territory
 Department of Territory and Municipal Services Australian Capital Territory
 Commonwealth Department of Infrastructure and Transport
 Australian Local Government Association
 New Zealand Transport Agency.
The success of Austroads is derived from the collaboration of member organisations and others in
the road industry. It aims to be the Australasian leader in providing high quality information, advice
and fostering research in the road transport sector.
SCATS and STREAMS Interface through the SCATS ITS Port
CONTENTS
1 INTRODUCTION ................................................................................................................... 1
2 RELEVANT EXPERIENCE ON SCATS/STREAMS INTEGRATION ..................................... 2
2.1 DPTI SCATS/STREAMS Integration ...................................................................................... 2
2.2 VicRoads SCATS/STREAMS Interface Development ............................................................ 4
2.3 MRWA on Using the SCATS ITS Port .................................................................................... 6
2.4 TMR on STREAMS Integration with Another Traffic Control System...................................... 6
2.5 Dialogue with Transmax ........................................................................................................ 7
3 THE ITS PORT IN SCATS..................................................................................................... 8
3.1 Background ........................................................................................................................... 8
3.2 Licensing ............................................................................................................................... 8
3.3 Available Message Types from the ITS Port .......................................................................... 9
3.3.1 Message Type 1: Action List .................................................................................. 10
3.3.2 Message Type 2: Alarms........................................................................................ 10
3.3.3 Message Type 3: ANTTS ....................................................................................... 10
3.3.4 Message Type 4: Congestion ................................................................................. 11
3.3.5 Message Type 5: Controller Details........................................................................ 11
3.3.6 Message Type 6: Date and Time ........................................................................... 11
3.3.7 Message Type 7: Detector Count ........................................................................... 11
3.3.8 Message Type 8: Dwell .......................................................................................... 11
3.3.9 Message Type 9: Error ........................................................................................... 11
3.3.10 Message Type 10: Event Log ................................................................................. 11
3.3.11 Message Type 11: Extended Controller Details ...................................................... 12
3.3.12 Message Type 12: Extended Region Details .......................................................... 12
3.3.13 Message Type 13: File ........................................................................................... 12
3.3.14 Message Type 14: Green Window ......................................................................... 13
3.3.15 Message Type 15: Incident Plan ............................................................................ 13
3.3.16 Message Type 16: Licence Validation .................................................................... 13
3.3.17 Message Type 17: Locks and Trims ....................................................................... 13
3.3.18 Message Type 18: Ramp Metering System ............................................................ 13
3.3.19 Message Type 19: Region Details .......................................................................... 13
3.3.20 Message Type 20: Route Pre-emption ................................................................... 14
3.3.21 Message Type 21: Server Registration .................................................................. 14
3.3.22 Message Type 22: Site Graphics ........................................................................... 14
3.3.23 Message Type 23: Site Layout ............................................................................... 15
3.3.24 Message Type 24: Site Status................................................................................ 15
3.3.25 Message Type 25: Strategic Monitor ...................................................................... 16
3.3.26 Message Type 26: System and Site Notes ............................................................. 16
3.3.27 Message Type 27: User Log On............................................................................. 16
3.3.28 Message Type 28: Watchdog ................................................................................. 16
4 FUNCTIONAL REQUIREMENTS FOR SCATS/STREAMS INTERFACE THROUGH
THE SCATS ITS PORT ....................................................................................................... 17
5 CONCLUSIONS .................................................................................................................. 22
REFERENCES ............................................................................................................................. 23
APPENDIX A LIST OF ABBREVIATIONS ..................................................................... 24
Austroads 2012
— i—
APPENDIX B PRIORITY RANKINGS FROM JURISDICTIONS ..................................... 25
TABLES
Table 3.1: Message types supported by the SCATS ITS Port ................................................... 9
Table 4.1: Functional requirements of the SCATS/STREAMS interface through the
ITS port .................................................................................................................. 17
FIGURES
Figure 2.1: Congestion display in STREAMS using the SCATS data through the
SCATS/STREAMS interface .................................................................................... 3
Figure 2.2: SCATS Access application launched through the SCATS/STREAMS
interface ................................................................................................................... 3
Figure 2.3: Display of SCATS control actions in STREAMS ....................................................... 4
Figure 2.4: Calling the SCATS Action List from STREAMS in VicRoads test
environment ............................................................................................................. 5
Austroads 2012
— ii —
SUMMARY
SCATS is a road signal control system that is used in many cities in Australia and New Zealand
and many overseas countries. STREAMS is an integrated platform for signal coordination (in
Queensland), freeway management and other traffic management measures. STREAMS has
been recently used for freeway management and as an interface for SCATS in Adelaide and for
ramp metering in Melbourne. This project aims to document current activities amongst road
agencies on the SCATS/STREAMS interface through the SCATS Intelligent Transport System
(ITS) Port, and identify a set of functional requirements for this interface to guide the development
of applications that make use of the data through this ITS Port.
This project successfully developed 26 functional requirements for the interface between SCATS
and STREAMS through the ITS Port. The data sets required for 24 out of the 26 requirements are
already available through the ITS Port, and about half of the requirements have been implemented
or partially implemented in South Australia.
RMS would further consider the investigation of the following STREAMS requirements not currently
supported with data through the SCATS ITS Port:
 STREAMS shall display current SCATS user such as an operator or a system that placed
site locks and trims, to ensure they are not left around inadvertently (functional requirement
12(a)).
 STREAMS shall query and display the Action List for SCATS sites, i.e., show the current
Action List(s) by the scheduler and/or variation routines.
 STREAMS shall provide (arterial) online national performance indicators (NPI) calculation
based on cycle-by-cycle signal timings, flow and occupancy (or equivalent density
indicators), link length and speed limit for a through movement.
 STREAMS shall be advised of any changes in SCATS site configurations.
RMS also clarified the licensing requirements in using the data from the ITS Port and the SCATS
development kit. A third party software/firmware developer will be able to deal with both its client
road agency and RMS on matters that involve the use of both SCATS and the data through the ITS
Port.
The functional requirements compiled in this report show the roadmap for the on-going
development and application of the SCATS/STREAMS interface. When all of the proposed
requirements are implemented in both systems, a powerful ITS platform will be available to road
agencies to improve the productivity and reliability of the road network in moving people and
goods.
ACKNOWLEDGEMENTS
Most materials were compiled from the documents supplied by the NS1724 team members. The
project team consists of Mark Shotton (Project Manager) and Jim Cluse from DPTI, Craig Moran,
Steven Shaw and Andrew Mehaffey from RMS, Richard Zhou and Andrew Somers from VicRoads,
David Stewart and Matthew Wood from TMR, Stefan Hoffman from MRWA, Michael Day from
TAMS, Danny Johnson from DIER, Geoff Horni from DOT and Russell Pinchen from NZTA.
Austroads 2012
— iii —
1 INTRODUCTION
SCATS (RMS 2012) and STREAMS (Transmax 2010) are network operational tools used by road
agencies in Australia and New Zealand to manage the road network. Several jurisdictions have
commissioned both products to deliver a combined operating system.
The Austroads Network Taskforce identified that discussions between the owners and users of
both SCATS and STREAMS may benefit all jurisdictions, particularly if the learnings from each
involved jurisdiction can be shared and agreed functional requirements for an integrated platform
can be developed.
The purpose of Austroads project NS1724: Development of SCATS and STREAMS Interface was
to develop an agreed set of functional requirements for connecting SCATS to STREAMS through
the Intelligent Transport System (ITS) Port in SCATS based on the experience of jurisdictions that
have commissioned both products.
A secondary purpose of the project was to improve the dialogue and working relationship between
the owners of SCATS and STREAMS. Two project workshops with project team members were
organised and a further meeting with Transmax was held.
This report provides the following information:

 relevant experience on SCATS/STREAMS integration (Section 2)
 the ITS Port in SCATS (Section 3)
 functional requirements for the SCATS/STREAMS interface through the ITS Port (Section 4)
 conclusions (Section 5).
Appendix A provides a list of abbreviations. Appendix B records the priority ranking from individual
jurisdictions on those functional requirements that have not been implemented in STREAMS.
In this report, the term ‘SCATS/STREAMS interface’ refers to the SCATS/STREAMS interface
through the ITS Port, and the term ‘SCATS ITS Port’ is often shortened as ‘the ITS Port’. Note that
the SCATS ITS Port has been interfaced to other devices/systems apart from STREAMS.
It must be emphasised that this project is not about the SCATS ITS Port. It is not about STREAMS
facilities either. As mentioned, the expected output from this project is an agreed set of functional
requirements for connecting SCATS to STREAMS through the ITS Port. The detailed technical
specifications or protocols are outside the scope of project NS1724.
For clarification, Transmax is a private company wholly owned by TMR for the development,
maintenance and commercialisation of STREAMS.
Austroads 2012
— 1—
2 RELEVANT EXPERIENCE ON SCATS/STREAMS

INTEGRATION
Relevant experience amongst road agencies on SCATS and STREAMS integration includes the
following:
 DPTI SCATS and STREAMS integration (Section 2.1)
 VicRoads SCATS/STREAMS interface development (Section 2.2)
 MRWA on using the SCATS ITS Port (Section 2.3)
 TMR on STREAMS integration with another traffic control system (Section 2.4)
 Dialogue with Transmax (Section 2.5).
2.1 DPTI SCATS/STREAMS Integration

In 2007 DPTI contracted Transmax to employ STREAMS to replace 11 separate systems
managing ITS around South Australia including the Heysen tunnels, Port River Expressway
opening bridges, all closed circuit television (CCTV), and the reversible flow of Southern
Expressway. STREAMS controls all ITS devices such as CCTV, changeable message signs
(CMS), variable speed limits (VSL), alarm management systems, automatic variable message
signs (VMS) and video incident detection through one common interface. STREAMS has become
the network-wide ITS platform for DPTI.
SCATS and STREAMS integration was part of the project (Transmax 2010). An interface to
SCATS through the ITS Port was developed to support the following functions:
 SCATS alarms were transferred to STREAMS. SCATS Regional text messages were
received by STREAMS and incorporated into event and alarm logs.
 Real-time operational information for SCATS sites was provided via list and map views in the
STREAMS Explorer interface, including an indication of operational status, current cycle
length, dwells, route pre-emption controls and associated current alarms.
 Information related to traffic congestion adjacent to SCATS sites was transferred to
STREAMS and indicated on the map view by colouring the associated link according to the
level of congestion (Figure 2.1).
 The SCATS Access (a graphical user interface for SCATS) can be launched in response to a
SCATS alarm through the Alarm Management interface, or through the list or map view via
the context menu (Figure 2.2).
Austroads 2012
— 2—
Source: Supplied by DPTI SA.
Figure 2.1: Congestion display in STREAMS using the SCATS data through the SCATS/STREAMS interface
Figure 2.2: SCATS Access application launched through the SCATS/STREAMS interface
Austroads 2012
— 3—
 The following SCATS control actions were accessible via STREAMS Response Plans
(Figure 2.3) or via manual overrides:
— activation of Action Lists
— activation of plan locks
— activation of cycle time locks
— activation of dwells
— activation of route pre-emption control (RPC).
Note that the ITS Port has not been designed for sophisticated real time control of the signals.
However, some messages such as message type 8: dwell (Section 3.3.8), message type 14: green
window (Section 3.3.14) and message type 20: route pre-emption (Section 3.3.20) from the ITS
Port can be used to trigger certain control actions such as emergency vehicle pre-emption (EVP).
Traffic operators of DPTI commented that the SCATS/STREAMS interface allowed users to use
SCATS data easily without knowing details of SCATS.
Figure 2.3: Display of SCATS control actions in STREAMS
2.2 VicRoads SCATS/STREAMS Interface Development

SCATS and STREAMS are key traffic management systems at VicRoads. SCATS is the primary
traffic signal control system for arterial roads. STREAMS is currently managing ITS devices along
freeways and also has a growing role as a network-wide ITS platform.
Austroads 2012
— 4—
VicRoads has been developing various applications to extract SCATS data via the ITS Port. One
such application maps degrees of congestion over the network and records congested minutes for
each mid-block road segment. A user familiar with TCP/IP and socket connections should be able
to safely communicate with SCATS via the ITS Port without interfering with SCATS operations.
The VicRoads M1 upgrade project made use of STREAMS as a platform for ramp metering
(VicRoads 2010). The project also included the development of a SCATS/STREAMS interface
through the ITS Port for freeway ramp signal management (VicRoads 2011). The purposes of
developing a SCATS and STREAMS single user interface were to:
 enable more streamlined user experience
 reduce the number of software graphical user interfaces (GUI) required to be displayed on
the screen
 enable TMC staff to respond rapidly to accidents and traffic disruptions with the assistance of
other ITS devices such as CCTV and VMS available on a single map interface
 enable newly recruited TMC operators with the right access level to perform more intuitive
traffic management tasks after training.
Some functions such as calling the SCATS Action List from STREAMS through the ITS Port were
developed in the test environment but are not yet commissioned (Figure 2.4). VicRoads is also
committed to trial the DPTI SCATS/STREAMS interface in a test environment to assess whether it
is suitable as an interim solution for VicRoads.
A set of functional requirements was prepared for the SCATS/STREAMS interface through the ITS
Port for the M1 upgrade project (VicRoads 2011). This set was used as the start point of preparing
the recommended Austroads NS1724 functional requirements in Section 4.
Source: Supplied by VicRoads.
Figure 2.4: Calling the SCATS Action List from STREAMS in VicRoads test environment
Austroads 2012
— 5—
2.3 MRWA on Using the SCATS ITS Port

MRWA has no experience with interfacing to STREAMS. Its experience in using the SCATS ITS
Port includes:
 detection of advanced loop faults (e.g. chatting loops) for every 5 min through the ITS port.
The loop faults that can be analysed included:
— counts greater than 350 in a 5 min period
— no counts in a 15 min period
— fluctuating counts (many then few counts) in short succession.
 development of SCATS alarms view
 development of a green light application to simplify dwells.
MRWA also trialled the retrieval of SCATS SM data for arterial travel time estimation using the
ARRB Travel Time Model (ATTM) (e.g. Luk et al. 2006). The SM data was retrieved in real time
through a special interface to SCATS and processed in a travel time server at the traffic
management centre (TMC) in Perth.
Beacon Technology (2009, 2010) and ARRB further investigated the issues of collecting all the
required data from the ITS Port for travel time calculation. The SCATS ITS Port was identified as
the best means of extracting SCATS data as it does not interfere with SCATS operation. However,
data obtainable through the ITS Port would still be limited and the delay times to requests made
through the ITS Port were considered too great to enable the reporting of travel time estimates
within a period considered close enough to real-time. The limitation could be due to the current
communication protocol between controllers and SCATS, e.g. the SCATS Access application does
not know the status of controllers. RMS is working on upgrading the communication protocols
between controllers and SCATS to enable much richer data types to be available from the ITS port.
The ATTM was implemented in STREAMS. Arterial travel time using the SCATS data from the ITS
Port is a proposed functional requirement of SCATS/STREAMS interface (no. 22 in Section 4).
2.4 TMR on STREAMS Integration with Another Traffic Control

System
The work by Transmax on the ITS port for DPTI and the M1 ramp metering project for VicRoads
was described in Section 2.1 and Section 2.2 respectively.
TMR through Transmax further provided an interface between STREAMS and the traffic
management and control system (called the Meridian) for the Tugun Bypass. The Tugun Bypass
is a 334 m long tunnel located between NSW (with the traffic network managed by SCATS) and
QLD (with the traffic network in the Gold Coast region managed by STREAMS). The purpose of
the interface was to monitor the Bypass status through the STREAMS platform.
The interface between STREAMS and Meridian is a programmable logic controller (PLC). The
interface provides eight relay outputs which were monitored by a STREAMS Field Processor.
These outputs provided the status of the Tugun Bypass to the STREAMS system including:
 bypass operating normally (all lanes open)
 bypass operating congested (lane closures / congestion level ‘x’ or worse)
 bypass closed (all lanes closed)
Austroads 2012
— 6—
 over-height vehicle detected southbound

 over-height vehicle detected northbound
 tunnel fire alarm
 traffic management control centre fault
 spare.
Each of these signals was reflected by a corresponding signal back from STREAMS to
acknowledge the above inputs. The Tugun Bypass returns to RMS control in 2018 and a
centre-to-centre (C2C) communication between Meridian and SCATS through the ITS port will be
set up in future.
2.5 Dialogue with Transmax

As part of this project, a meeting between Transmax and some project team members was
organised in March 2012 in Brisbane. The purpose of this meeting was for Transmax and team
members to discuss aspects of the current interface between STREAMS and SCATS.
The following issues were discussed at the meeting:

 The STREAMS/SCATS interface and any other access to SCATS data shall go through the
SCATS ITS Port. RMS encourages as many people as possible to access data from SCATS
through the ITS Port.
 An interested party approved by RMS can purchase the ITS Port developer’s kits plus
licence dongle (including WinTRAF and up to 10 configured intersections) and a SCATS
Client licence in order to develop software interface through the ITS Port. RMS would
provide necessary support following the purchase of a licence (Section 3.2).
Transmax has already ordered the ITS Port developer’s kit and will develop and test the
STREAMS/SCATS software interface by using the simulated SCATS environment following the
purchase of the licence.
Austroads 2012
— 7—
3 THE ITS PORT IN SCATS

The SCATS ITS Port allows ITS applications to retrieve messages from a SCATS host using
Transmission Control Protocol/Internet Protocol (TCP/IP). The SCATS host may be a Central
Manager or a Regional computer. This section provides an overview of the SCATS ITS Port based
on RTA (2009), RMS (2012) and the discussions and presentations amongst project team
members via project workshops.
3.1 Background
The SCATS ITS interface was introduced in SCATS version 6.0. At that time, there were only a
small number of message types and all ITS communications were handled by SCATS Regional
computers. The SCATS Central Manager was introduced with SCATS version 6.1.2, and this
Central Manager also supported the ITS interface. The number of message types increased with
subsequent releases of SCATS and has continued to increase to meet the needs of SCATS users
and ITS application developers.
Users can use the ITS Port to extract data out of SCATS. Generally users cannot provide major
input or critical real time control to SCATS through the ITS Port. As mentioned, the ITS Port has
not been designed for sophisticated real time control of the signals and some messages (e.g.
message types 8 and 20) from the ITS Port can be used to trigger certain control actions such as
emergency vehicle pre-emption (EVP).
RMS encourages all user applications to exchange data with SCATS through the ITS Port. All
other applications that access SCATS data rather than through the ITS Port are not guaranteed.
In future the SCATS ITS Port will provide an international interface by employing the National
Transportation Communications for ITS Protocol (e.g. Joint Committee on the NTCIP 2009).
RMS welcomes the development of the Austroads SCATS/STREAMS interface and saw SCATS
as a core arterial road manager that can be used in a range of third party platforms such as
STREAMS and Serco (2012).
3.2 Licensing
The user must purchase an ITS licence before writing an ITS application using the ITS Port. With
an ITS licence, the user receives:
 the licence details needed for the user’s ITS application
 one or more specifications, including the SCATS ITS interface specification
 help desk support.
The ITS licence specifies which SCATS host the user can use, which ITS message types the user
can use and how many simultaneous connections the user can have. Various licensing options
are available and all ITS licences are user-specific.
There are two types of ITS licences – the Client licence and the Server licence. Both licences
support all message types and have one maximum connection. Existing single licence will be shut
down and replaced by the dual licensing system.
Austroads 2012
— 8—
RMS provides an ITS developer’s kit to support users to develop and test ITS applications through
the ITS Port. A developer licence can use all message types but application licences are
user-specific. All new ITS licences are categorised as either developer licence or application
licence, both shall use dual licensing (i.e. the Client licence and the Server licence).
3.3 Available Message Types from the ITS Port

Table 3.1 summarises the 28 available message types through the ITS Port in SCATS
version 6.6.2 (RTA 2009). The explanation of the column headers in Table 3.1 is as follows:
 ‘Message type’ is the name used to identify the message type.
 ‘Version’ is the version of SCATS when the message type was introduced. (The user’s
SCATS host must be greater than or equal to this version in order to support this message
type).
 ‘Region’ indicates whether the message type can be used when communicating with a
SCATS Region. All message types are valid when the host is a SCATS Central Manager,
but some message types cannot be used with a SCATS Region because the data being
requested is only available from the SCATS Central Manager.
 ‘Availability’ indicates the availability of the message type to the user’s ITS licence, where:
— 'Core' means that it is available to all ITS licences.
— 'Optional' means it is an optional message type that is only available to the licence if
the user has purchased it. The users must purchase at least one optional message
type in order to write a useful ITS application.
The number of message types has increased with subsequent releases of SCATS and will
continue to increase to meet the needs of SCATS users and ITS application developers.
Table 3.1: Message types supported by the SCATS ITS Port

No. Message type Version Region Availability
1 Action list 6.0 √ Optional
2 Alarms 6.3.0 Optional
3 ANTTS 6.4.1 √ Optional
4 Congestions 6.1.2 √ Optional
5 Controller details 6.4.1 √ Optional
6 Data and time 6.1.2 √ Core
7 Detector count 6.3.0 √ Optional
8 Dwell 6.3.0 √ Optional
9 Error 6.4.1 √ Core
10 Event log 6.0 √ Optional
11 Extended controller details 6.4.1 √ Optional
12 Extended region details 6.4.1 √ Optional
13 File 6.1.2 √ Optional
14 Green window 6.1.2 √ Optional
15 Incident plan 6.5.4.5 Optional
16 Licence validation 6.0 √ Core
17 Locks and Trims 6.3.0 √ Optional
Austroads 2012
— 9—
No. Message type Version Region Availability

18 Ramp metering system 6.3.0 √ Optional
19 Region details 6.1.2 √ Core
20 Route pre-emption 6.4.1 Optional
21 Server registration 6.4.1 √ Optional
22 Site graphics 6.4.1 Optional
23 Site layout 6.5.2 Optional
24 Site status 6.0 √ Core
25 Strategic monitor 6.0 √ Optional
26 System and site notes 6.5.1 SPI Optional
27 User log on 6.3.0 √ Optional
28 Watchdog 6.0 √ Core
Source: RTA (2009).
Detailed description of these 28 available message types from the ITS Port are as follows.
3.3.1 Message Type 1: Action List

The Action List message is used to apply one or more Action Lists at a SCATS Region. It cannot
be used to create, edit or delete an Action List. This is done using SCATS Access.
See also message type 15: incident plan in Section 3.3.15.
3.3.2 Message Type 2: Alarms

The alarms message is used to:
 list maintenance areas
 get site, subsystem, region and system alarms or status
 acknowledge alarms
 hide alarms
 show alarms
 clear alarms
 delete alarms.
If the ITS licence includes this message type, the user will be supplied with a specification of the
alarm identifier format. This is used to identify the alarm type, source, various time stamps and
status.
See also message type 24: site status in Section 3.3.24.
3.3.3 Message Type 3: ANTTS

The ANTTS message is used to send or receive Automatic Network Travel Time System (ANTTS)
tag data.
Austroads 2012
— 10 —
3.3.4 Message Type 4: Congestion

The congestion message is used to receive congestion data from detectors defined as strategic
inputs. The congestion data includes:
 congested detectors from all sites in all regions
 a congestion index from all sites in all regions
 the degree of saturation index and flow ratio index from one or more specific sites
 mapping of detectors to strategic approaches from one or more specific sites (from version
6.5.1).
3.3.5 Message Type 5: Controller Details

The controller details message is used to get information from a controller, including:
 controller memory
 controller software version, type and release number.
See also message type 11: extended controller details in Section 3.3.11.
3.3.6 Message Type 6: Date and Time

The date and time message is used to get the current date and time from the SCATS host.
3.3.7 Message Type 7: Detector Count

The detector count message is used to get detector counts for all sites in all regions. These will be
5-minute or 15-minute counts, depending on the region configuration.
3.3.8 Message Type 8: Dwell

The dwell message is used to apply or remove a dwell at a single site. The dwell may be
demand-only, timed or permanent. Unlike SCATS Access, the user can specify alternative dwell
phases. From version 6.5.4, the user can also specify the 'no skip' flag.
See also message type 14: green window in Section 3.3.14 and message type 20: route
pre-emption in Section 3.3.20.
3.3.9 Message Type 9: Error

The error message is used to notify the ITS application that it sent a request that the SCATS host
could not process, typically because the ITS application used an unknown message type or an
unlicensed message type.
3.3.10 Message Type 10: Event Log

The event log message is used to write a text entry to the SCATS event log. From version 6.4.1,
the user can also write a command entry to the event log.
This message can also be used to generate user-defined alarms. If the ITS application needs to
do this, the user will be supplied with a specification of the alarm identifier format.
Austroads 2012
— 11 —
3.3.11 Message Type 11: Extended Controller Details

The extended controller details message is used to get enhanced version details from version 5 (or
higher) controllers, including:
 controller software version, type and release number
 module type and/or hardware revision number
 number of modules
 module serial number for each module
 TRAFF build number.
The user should use the controller details message to check the controller version number before
using this message.
See also message type 5: controller details in Section 3.3.5.
3.3.12 Message Type 12: Extended Region Details

The extended region details message is used to get details of all regions, including:
 region number and name
 SCATS version
 SCATS licence options
 IP address
 GUI port number (used by SCATS Access and SCATS Picture)
 the ITS Port number (used by ITS applications)
 networked sites port usage
 list of sites and their subsystem numbers.
See also message type 19: region details in Section 3.3.19.
3.3.13 Message Type 13: File

The file message is used to read any of the following file types:
 event log
 history (from version 6.5.2)
 strategic monitor
 detector counts
 ANTTS
 Sys.lx, Sys.msg and Sys.ram system files (from version 6.5.1 SP1).
If the ITS licence includes this message type, the user will be supplied with any specifications that
exist for the relevant file formats.
Austroads 2012
— 12 —
3.3.14 Message Type 14: Green Window

The green window message is used to apply a dwell at multiple sites and monitor the status of the
dwells. This is normally used for public transport priority.
The dwells at each site may be timed or permanent. Unlike SCATS Access, the user can specify
alternate dwell phases and/or a start delay for each site. From version 6.5.4, the user can also
specify the 'no skip' flag.
This message can also be used to remove all the dwells for the same green window.
See also message type 8: dwell in Section 3.3.8 and message type 20: route pre-emption in
Section 3.3.20.
3.3.15 Message Type 15: Incident Plan

The incident plan message is used to create, delete, apply or remove incident plans. It cannot be
used to create, edit or delete the Action Lists that are applied by the incident plans. This is done
using SCATS Access.
See also message type 1: Action List in Section 3.3.1.
3.3.16 Message Type 16: Licence Validation

The licence validation message is used to:
 pass the ITS licence details to the SCATS host so that a connection can be established
 get the version of the ITS protocol and SCATS host so that the user can determine which
message types can be understood by that host.
3.3.17 Message Type 17: Locks and Trims

The locks and trims message is used to apply or remove locks and trims to cycle lengths, cycle
length plans, subsystem plans, link plans and marriage/divorce. Locks can be timed or permanent.
3.3.18 Message Type 18: Ramp Metering System

The ramp metering system messages are used to manage a SCATS ramp metering site by:
 getting detector data
 setting the red time.
This is normally only used by the SCATS ramp metering system (SRMS).
3.3.19 Message Type 19: Region Details

The region details message is used to get details of all regions, including:
 region number and name
 SCATS version
 SCATS licence options
 IP address
 GUI port number (used by SCATS Access and SCATS Picture)
 the ITS Port number (used by ITS applications)
Austroads 2012
— 13 —
 list of sites and their subsystem numbers.
See also message type 12: extended region details in Section 3.3.12.
3.3.20 Message Type 20: Route Pre-emption

The route pre-emption message is used to manage route pre-emption plans, including:
 loading and unloading route pre-emption plans
 starting and stopping route pre-emption plans
 monitoring active route pre-emption plans
 pausing and re-starting active route pre-emption plans
 querying route pre-emption plans
 getting details of route pre-emption plans
 setting the start and end site prior to starting a route pre-emption plan
 setting the timing rate of route pre-emption plans
 editing route pre-emption plans.
See also message type 8: dwell in Section 3.3.8 and message type 14: green window in
Section 3.3.14.
3.3.21 Message Type 21: Server Registration

The server registration message is used to extend the ITS interface by registering up to four
custom message types. In this way, an ITS application can act as a server to provide non-SCATS
data to its clients instead of, or in addition to, SCATS data.
In order to prevent clashes with other ITS applications, the unique numbers allocated to the custom
message types will be allocated to be used by the RMS. As the number of available custom
message types is limited, it should restrict to one custom message type per application and use
sub-message types if the user needs multiple custom messages.
3.3.22 Message Type 22: Site Graphics

The site graphics message is used to get encoded site graphics data from the SCATS Central
Manager database. This includes:
 street names
 location (i.e. town or suburb)
 area
 coordinates
 map reference
 viewport position
 arm angles, offsets and street names
 number of approach, departure and slip lanes for each arm
 transverse and longitudinal line marking and pedestrian movement numbers for each arm
Austroads 2012
— 14 —
 corner island dimensions

 pavement arrows
 adjacent sites
 phasing
 signal group numbers
 'movement box' positions
 movement details
 detector numbers and positions
 detector feeder cable locations
 controller location
 railway line locations.
It is up to the ITS application to extract any information that is needed from the encoded data
and/or render the graphics.
If the ITS licence includes this message type, the user will be supplied with a specification that
describes the encoded data format.
See also message type 23: site layout in Section 3.3.23.
3.3.23 Message Type 23: Site Layout

The site layout message is used to get a subset of the site graphics information from the SCATS
Central Manager database in a more human friendly format than the site graphics message. This
includes:
 street names
 location (i.e. town or suburb)
 coordinates
 bearings (not angles), street names and adjacent sites along each arm
 detector locations.
See also message type 22: site graphics in Section 3.3.22.
3.3.24 Message Type 24: Site Status

The site status message is used to get status changes at one or more sites. This includes:
 alarms
 detector alarm details
 fallback status
 locks
 dwells
 lamp state
 congestion state
Austroads 2012
— 15 —
 link mode
 active split plan number
 active offset plan number
 special facilities (Y–, Z–, Z+, extra special facilities, miscellaneous status, remote special
facilities and Z flags)
 phase intervals
 phase times
 demand status
 walk termination status
 slave status
 false green status
 vehicle and pedestrian signal group status (i.e. green or not green)
 subsystem number
 congestion index
 marriage status
 nominal cycle length
 required cycle length.
3.3.25 Message Type 25: Strategic Monitor

The strategic monitor message is used to get strategic monitor data for one or more subsystems in
a region.
describes the strategic monitor data format.
3.3.26 Message Type 26: System and Site Notes

The system and site notes message is used to view system and site notes. From version 6.5.4,
this can also be used to create, edit and delete system and site notes.
3.3.27 Message Type 27: User Log On

The user log on message is used to allow a user to log on to the SCATS host via the ITS
application. This will be necessary if the user wants to use any of the message types that allow the
ITS application to change SCATS data, including locks, trims, dwells and plan changes.
describes the password encryption algorithm.
3.3.28 Message Type 28: Watchdog

The watchdog message is used by the SCATS host to confirm that the ITS application is still
online. The ITS application can also use this message to confirm that the SCATS host is still
online.
Austroads 2012
— 16 —
4 FUNCTIONAL REQUIREMENTS FOR SCATS/STREAMS

INTERFACE THROUGH THE SCATS ITS PORT
An interface, by definition, involves the systems on both sides of the interface. The functional
requirements of the SCATS/STREAMS interface (through the ITS Port) therefore involves system
attributes in both SCATS and STREAMS. Some of the attributes are now available or
implemented in either SCATS or STREAMS, or in both systems, and some require future
development.
At the March 2012 project workshop, members of NS1724 project team reviewed and modified the
VicRoads (2011) functional requirements and developed the Austroads functional requirement for
a SCATS/STREAMS interface through the ITS Port. These functional requirements were compiled
in Table 4.1. The explanation of the column headers in Table 4.1 is as follows:
 ‘Availability’ means the data required for this functional requirement is available or not
available thought the SCATS ITS Port.
 ‘Comments’ were mainly supplied by RMS.
 ‘Implementation’ means the functionality specified was implemented or has not been
implemented in STREAMS.
 ‘Agreed priority of implementation’ provides the average priority ranking (1 – low priority;
2 – medium priority; 3 – high priority) for those functional requirements that have not been
implemented in STREAMS through the ITS Port. The priority is the average value of the
rankings supplied by individual jurisdictions. Ranking values from individual jurisdictions
were attached in Appendix B for reference.
Table 4.1: Functional requirements of the SCATS/STREAMS interface through the ITS port
SCATS ITS Port STREAMS
Agreed priority
of
implementation
No. Functional requirements
Availability Comments Implementation 1 – Low priority
2 – Medium
priority
3 – High priority
ITS Port cannot identify
SCATS operators shall apply settings
different users using the same Implemented
with their own SCATS user key and
1 Available ITS port. The log information
any modifications shall be reflected in (road agency to use the DPTI model)
will specify the application that
SCATS log for auditing purpose.
made the request.
STREAMS shall query and display Marriage data is available in
Not
2 current Subsystem marriage status Available both the Site Status and 2
implemented
graphically. Subsystem messages.
STREAMS shall search SCATS sites
from inputs such as: The Extended Region Details
(a) a site number message can be used to
(b) road names and intersection determine the sites belonging
3 Available to a region. Implemented partially
similar to current SCATS Access (e.g.
entering ‘High St / Station St’ and Road names are not available
‘Station St / High St’ returns the same on the ITS Port.
intersection).
Austroads 2012
— 17 —

Agreed priority
of
implementation
2 – Medium
priority
3 – High priority
STREAMS shall display the current
SCATS sites operation modes on the
map including alarm types where
applicable, such as but not limited to:
(a) operation modes such as: Available in the Site Status Not
4 Available 2
Masterlink, Fexilink, Isolated,etc. message. implemented
(b) major alarm type such as: ST, DZ,
etc.
(c) minor alarm.
STREAMS shall display multiple
SCATS graphics for items on the map
such as:
(a) time pie chart Available in the Site Status Not
5 Available 2
message. implemented
(b) signal group
(c) active phase (e.g. phase A, B, C,
D, etc.).
STREAMS shall be able to query and
display current cycle time of multiple
Provided in the Site Status and Not
6 SCATS sites on the graphical map Available 2
Subsystem messages. implemented
interface with customisable colour
code representation of time range.
STREAMS shall query and display the
Provided in the Subsystem Not
7 current link plan (LP) of multiple Available 2
message. implemented
SCATS sites on the map interface.
STREAMS shall draw and/or select An ad hoc route pre-emption Not
multiple SCATS sites on the map to plan can be created and run, implemented
8 Available 2
create predefined routes, e.g. for route but cannot be saved via the ITS
pre-emption. Port.
STREAMS shall display current
SCATS site status graphically with a
Alarm information is available
total number of each occurrence, for Not
9 Available in the Alarm and Site Status 2
example, status is Black Out (BO) implemented
messages.
and/or on flash (OF) with a total
number.
Information from Alarm and
STREAMS shall query and display
Route pre-emption messages
selected routes (such as from a Not
10 Available can be correlated to determine 2
pre-emption list) to check for alarms in implemented
which sites in a pre-emption
graphical map format.
plan have alarms.
STREAMS shall set a function of site
to permeant, and/or cancel, and/or
with a specific time duration, for
example: Supported via the Locks and
11 Available Implemented
Trims message.
(a) to lock cycle length (CL), split plan
(SP), link plan (LP)
(b) to apply dwell to a phase.
Austroads 2012
— 18 —

Agreed priority
of
implementation
2 – Medium
priority
3 – High priority
STREAMS shall display current
SCATS site locks and trims and the
user who placed them, to ensure they
are not left around inadvertently, for Supported in the Locks and Not
Available 2
example: Trims message. implemented
12
(a) locks and trims such as
CL + SP + LP + dwell
(b) current user such as an operator or Not
Not available 2
system. implemented
STREAMS shall display and show
status of predefined plans for route Provided in the route Not
13 Available 2
pre-emption with details such as sites, pre-emption message. implemented
phase, and time.
Action List for SCATS sites, i.e. show
Action List(s) currently in actions by: SCATS issue, will be resolved Not
14 Not available 2
in future. implemented
(a) scheduler
(b) Variation Routing (VR1, VR2, etc.).
Action List for SCATS sites, i.e. show
Action List(s) currently in actions by: SCATS issue, will be resolved Not
14 Not available 2
in future. implemented
(a) scheduler
(b) Variation Routing (VR1, VR2, etc.).
STREAMS shall display SCATS usual
and unusual congestion graphically in
colour modes including details such
as: Can be provided if Congestion Not
15 (a) duration in minutes Available 3
Server is purchased. implemented
(b) direction of congestion
(c) a number top occurrence sites as
defined by user (e.g. top 20).
STREAMS shall display current road
congestion condition information DS available in Subsystem
graphically such as degree of message.
saturation (DS).
STREAMS shall run route pre-emption
control (RPC).
STREAMS shall lock cycle length
plan.
STREAMS shall launch SCATS
Access.
STREAMS shall display SCATS
20 congestion data on the STREAMS Available Implemented
congestion map.
STREAMS shall export all the alarms
to the STREAMS alarm manager.
Austroads 2012
— 19 —

Agreed priority
of
implementation
2 – Medium
priority
3 – High priority
STREAMS shall provide online
calculation of (arterial) national Implemented in
performance indicators (NPI) based
STREAMS
22 on cycle-by-cycle signal timings, flow Not available See Section 2.3. 2
and occupancy (or equivalent density using
indicators), link length and speed limit STREAMS data
for a through movement.
(a) STREAMS shall conduct Lx and pcintgraff files can be
automated data migration from provided, but data migration Not
Available 3
SCATS such as, site configuration tools are not provided on the implemented
data, etc. ITS Port.
23
(b) STREAMS shall be advised of any Not
changes in SACTS site configurations. Not available implemented 3
but critical
STREAMS shall generate flags for
Ability to run an Action List is
SCATS to action for freeway ramp
provided via the ITS Port; no
metering operation, e.g. STREAMS
24 Available information available from the Implemented via Action List
shall generate a flag when a ramp is
ITS Port on SCATS actions
full for SCATS to reduce the time for
taken.
traffic turning into the ramp.
STREAMS shall generate and initiate
response plans when stimuli from
Ability to run an Action List is
alarms, congestion/link blockage or
provided via the ITS Port; no
incidents occur. For example, if queue
25 Available information available from the Implemented via Action List
blockage occurs in a link, STREAMS
ITS Port on SCATS actions
shall initial a response plan for SCATS
taken.
to reduce green time for traffic coming
from upstream.
STREAMS shall implement ramp
closure with data from the ITS Port in
the following steps:
(a) STREAMS shall send a message Ability to run an Action List is
to SCATS for appropriate signal provided via the ITS Port; no
26 settings for ramp closure. Available information available from the Implemented via Action List
(b) SCATS shall send a confirmation ITS Port on SCATS actions
message back to STREAMS when (a) taken.
is implemented.
(c) STREAMS shall then switch on the
ramp closure signs.
Austroads 2012
— 20 —
The main findings can be summarised as follows:

 The data sets required for most of the functional requirements (24 out 26) are already
available through the SCATS ITS Port.
 About half of the functional requirements in Table 4.1 (12 out of 26) have been implemented
 For those functional requirements that have not been implemented in STREAMS (14 out of
26), priority rankings were provided based on the feedback from jurisdictions. The ranking
values are the average values of the rankings supplied by individual jurisdictions. This
priority ranking is useful for the on-going development and usage of the SCATS/STREAMS
interface.
 RMS would investigate the following requirements not currently supported with SCATS data
through the ITS Port.
— STREAMS shall display current SCATS user such as an operator or a system that
placed site locks and trims, to ensure they are not left around inadvertently (functional
requirement 12(a)).
— STREAMS shall query and display the Action List for SCATS sites, i.e., show current
Action List(s) by the scheduler and/or variation routines (functional requirement 14).
— STREAMS shall provide the online calculation of arterial NPI based on cycle-by-cycle
SCATS signal timings, flow and occupancy (or equivalent density indicators), link
length and speed limit for a through movement (functional requirement 22).
— STREAMS shall be advised of any changes in SCATS site configurations (functional
requirement 23 (b)).
Further, the number of message types provided by the ITS Port may need to be further increased
to meet the needs from users.
Austroads 2012
— 21 —
5 CONCLUSIONS
Austroads Project NS1724 successfully developed a set of functional requirements for the interface
between SCATS and STREAMS through the SCATS ITS Port. RMS further clarified the licensing
requirements in using the data from the ITS Port and a SCATS development kit. A third party
software/firmware developer will be able to deal with both its client road agency and RMS on
matters that involve both SCATS and the data through the ITS Port.
Jurisdictions that have commissioned both products provided substantial input for the development
of 26 functional requirements (Section 4). A summary of the main findings is as follows:
 The data sets required for most of those functional requirements (24 out 26) are already
available through the SCATS ITS Port.
 About half of the functional requirements in Table 4.1 (12 out of 26) have been implemented
 For those functional requirements that have not been implemented in STREAMS (14 out of
26), priority rankings were provided based on the feedback from jurisdictions. The ranking
values are the average values of the rankings supplied by individual jurisdictions. This
priority ranking is useful for the on-going development and usage of the SCATS/STREAMS
interface.
 RMS would investigate the following requirements not currently supported with SCATS data
through the ITS Port:
— STREAMS shall display current SCATS user such as an operator or a system that
placed site locks and trims, to ensure they are not left around inadvertently (functional
requirement 12(a)).
— STREAMS shall query and display the Action List for SCATS sites, i.e. show the
current Action List(s) by the scheduler and/or variation routines (functional requirement
14).
— STREAMS shall provide the online calculation of arterial (NPI) based on cycle-by-cycle
SCATS signal timings, flow and occupancy (or equivalent density indicators), link
length and speed limit for a through movement (functional requirement 22).
— STREAMS shall be advised of any changes in SCATS site configurations (functional
requirement 23 (b)).
Further, the number of message types provided by the ITS Port may need to be further increased
to meet the needs from users.
Austroads 2012
— 22 —
REFERENCES
Beacon Technology 2009, ITS SCATS data collector use case model survey, version 0.1, Main Roads WA,
Perth, WA.
Beacon Technology 2010, ITS SCATS use case model survey travel time model, version 0.1, Main Roads
WA, Perth, WA.
Joint Committee on the NTCIP 2009, The NTCIP guide: National Transportation Communications for ITS
th
Protocol, version v04, AASHTO, ITE & NEMA, Washington, DC, viewed 12 April 2012,
<http://www.ntcip.org/library/documents/pdf/9001v0406r.pdf>.
Luk, JYK, Karl, C, Su, M & Bennett, P 2006, ‘Real-time estimation of travel times on arterial roads in
nd
Melbourne’, ARRB conference, 22 , 2006, Canberra, ACT, ARRB Group Ltd, Vermont South, Vic, 14
pp.
Roads and Traffic Authority 2009, SCATS intelligent transport systems interface overview, SCATS6-TN-028,
Issue A, 4 February 2009, RTA, Sydney, NSW.
Roads and Maritime Services 2012, Sydney Coordinated Adaptive Traffic System (SCATS), Sydney, NSW,
th
viewed 12 April 2012, http://www.scats.com.au/index.html.
Serco 2012, A global leader in transport, Serco, North Sydney, NSW, viewed 12 December 2012,
<http://www.serco-ap.com.au/our-services/sectors/transport/>.
th
Transmax 2010, STREAMS ITS integration, Transmax Pty Ltd, Brisbane, Qld, viewed 12 April 2012,
http://www.transmax.com.au/images/stories/pdf_files/brochures/web/3.STREAMS_ITS_Integration.pdf
VicRoads 2010, Managed freeways: freeway ramp signal handbook, VicRoads, Kew, Vic.
VicRoads 2011, SCATS and STREAMS integration software requirement specification, version 2.0,
VicRoads, Kew, Vic.
Austroads 2012
— 23 —
APPENDIX A LIST OF ABBREVIATIONS

Abbreviation Full name or explanation
ANTTS Automatic Network Travel Time System
API Application programming interface
ATTM ARRB Travel Time Model
BO Block out
C2C Centre to centre
CCTV Closed circuit television
CL Cycle length
CMS Changeable message signs
EVP Emergency vehicle pre-emption
GUI Graphical user interface
IP Internet Protocol
ITS Intelligent transport systems
LP Link plan
NPI National performance indicators
NTCIP National Transportation Communications for Intelligent Transportation System Protocol
OF On flash
PLC Programmable logic controller
RPC Route pre-emption control
SCATS Sydney Coordinated Adaptive Traffic System
SCATS SM SCATS system monitoring message (data)
SCATS DS SCATS Degree of saturation
SP Split plan
STREAMS An integrated intelligent transport system used in Queensland
TCP/IP Transmission Control Protocol/Internet Protocol
TMC Traffic management centre
TRAFF Controller software supplied by RMS
VMS Variable message signs
VR Variation routing
VSL Variable speed limits
Austroads 2012
— 24 —
APPENDIX B PRIORITY RANKINGS FROM

JURISDICTIONS
Table B.1: Priority ranking of not implemented functional requirements of SCATS/STREAMS interface through
the SCATS ITS port

Priority of Implementation
Functional
No. 1 – Low priority; 2 – Medium priority; 3 – High priority
requirements Availability Comments Implementation
Average Vic
DPTI MRWA TAMS TMR
value Roads
STREAMS shall Marriage data is
query and display available in both
2 current Subsystem Available the Site Status Not implemented 2 2 3 1 2
marriage status and Subsystem
graphically. messages.
STREAMS shall
display the current
SCATS sites
operation modes on
the map including
alarm types where
applicable, such as Available in the
4 but not limited to: Available Site Status Not implemented 2 1 3 1 3 3
(a) operation modes message.
such as: Masterlink,
Fexilink, Isolated,etc.
(b) major alarm type
such as: ST, DZ, etc.
(c) minor alarm.
STREAMS shall
display multiple
SCATS graphics for
items on the map
such as: Available in the
5 (a) time pie chart Available Site Status Not implemented 2 2 3 1 2 3
message.
(b) signal group
(c) active phase (e.g.
phase A, B, C, D,
etc.).
STREAMS shall be
able to query and
display current cycle
time of multiple Provided in the
SCATS sites on the Site Status and
6 Available Not implemented 2 2 2 1 2 1
graphical map Subsystem
interface with messages.
customisable colour
code representation
of time range.
STREAMS shall
query and display the
Provided in the
current link plan (LP)
7 Available Subsystem Not implemented 2 2 2 1 2 2
of multiple SCATS
message.
sites on the map
interface.
Austroads 2012
— 25 —

Functional
Average Vic
DPTI MRWA TAMS TMR
value Roads
STREAMS shall draw
An ad hoc route
and/or select multiple
pre-emption plan
SCATS sites on the
can be created
8 map to create Available Not implemented 2 3 2 1 2 2
and run, but
predefined routes,
cannot be saved
e.g. for route
via the ITS Port.
pre-emption.
STREAMS shall
display current
SCATS site status Alarm
graphically with a information is
total number of each available in the
occurrence, for Alarm and Site
example, status is Status
Black Out (BO) messages.
and/or on flash (OF)
with a total number.
Information from
the Alarm and
STREAMS shall
Route
query and display
Pre-emption
selected routes (such
messages can
10 as from a pre-emption Available Not implemented 2 2 3 2 1 1
be correlated to
list) to check for
determine which
alarms in graphical
sites in a
map format.
pre-emption plan
have alarms.
STREAMS shall
display current
SCATS site locks and
trims and the user
who placed them, to
ensure they are not Supported in the
left around Available Locks and Trims Not implemented 2 1 2 2 3 3
inadvertently, for message.
12
example:
(a) locks and trims
such as
CL + SP + LP + dwell
(b) current user such
Not
as an operator or Not implemented 2 1 2 2 2 2
available
system.
STREAMS shall
display and show
Provided in the
status of predefined
Route
13 plans for route Available Not implemented 2 2 3 2 2 1
Pre-emption
pre-emption with
message.
details such as sites,
phase, and time.
Austroads 2012
— 26 —

Functional
Average Vic
DPTI MRWA TAMS TMR
value Roads
STREAMS shall
query and display the
Action List for SCATS
sites, i.e. show Action SCATS issue,
List(s) currently in Not
14 will be resolved Not implemented 2
actions by: available
in future.
(a) scheduler
(b) Variation Routing
(VR1, VR2, etc.).
STREAMS shall
display SCATS usual
and unusual
congestion
graphically in colour
modes including
details such as: Can be provided
(a) duration in if Congestion
minutes Server is
purchased.
(b) direction of
congestion
(c) a number of top
occurrence sites as
defined by user (e.g.
top 20).
STREAMS shall
provide online
calculation of arterial
NPI based on cycle-
by-cycle signal Implemented in
Not
22 timings, flow and See Section 2.3. STREAMS using 2
available
occupancy (or STREAMS data
equivalent density
indicators), link length
and speed limit for a
through movement.
Lx and pcintgraff
(a) STREAMS shall
files can be
conduct automated
Available provided, but Not implemented
data migration from
data migration 3 3 3 3 2 2
SCATS such as
tools are not
coordinates, site data,
23 provided on the
etc.
ITS Port.
(b) STREAMS shall
know the changes in Not Not implemented
3 3 3 3 2 3
SCATS site available but critical
configurations.
Austroads 2012
— 27 —
INFORMATION RETRIEVAL
Austroads, 2012, SCATS and STREAMS Interface through the SCATS ITS
Port, Sydney, A4, pp. 30. AP-T224-12
Keywords:
SCATS, STREAMS, SCATS ITS Port, functional requirements, interface, traffic

control, system.
Abstract:
This report documented current activities amongst road agencies in Australia

on the SCATS/STREAMS interface through the SCATS Intelligent Transport
System (ITS) Port, and identified a set of 26 functional requirements for this
interface to guide the development of applications that makes use of the data
through this ITS Port. The RMS licensing requirements in using the data from
the ITS Port and the SCATS development kit were also clarified. A third party
software/firmware developer will be able to deal with both its client road agency
and RMS on matters that involve the use of both SCATS and the data through
the ITS Port. The functional requirements compiled in this report show the
roadmap for the on-going development and application of the
SCATS/STREAMS interface. When all of the proposed requirements are
implemented in both systems, a powerful ITS platform will be available to road
agencies to improve the productivity and reliability of the road network in
moving people and goods.

SCATS and STREAM Interface Through The SCATS ITS Port

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SCATS and STREAM Interface Through The SCATS ITS Port

Uploaded by

Copyright:

Available Formats

AP-T224-12

AUSTROADS TECHNICAL REPORT

SCATS and STREAM Interface through the

Published December 2012

© Austroads Ltd 2012

SCATS and STREAMS Interface through the SCATS ITS PORT

Austroads Project No. NT1724

Austroads Publication No. AP–T224-12

Published by Austroads Ltd

APPENDIX B PRIORITY RANKINGS FROM JURISDICTIONS ..................................... 25

This report provides the following information:

2 RELEVANT EXPERIENCE ON SCATS/STREAMS

2.1 DPTI SCATS/STREAMS Integration

Source: Supplied by DPTI SA.

Source: Supplied by DPTI SA.

Source: Supplied by DPTI SA.

Figure 2.3: Display of SCATS control actions in STREAMS

2.2 VicRoads SCATS/STREAMS Interface Development

Source: Supplied by VicRoads.

2.3 MRWA on Using the SCATS ITS Port

2.4 TMR on STREAMS Integration with Another Traffic Control

 over-height vehicle detected southbound

2.5 Dialogue with Transmax

The following issues were discussed at the meeting:

3 THE ITS PORT IN SCATS

3.3 Available Message Types from the ITS Port

Table 3.1: Message types supported by the SCATS ITS Port

No. Message type Version Region Availability

3.3.1 Message Type 1: Action List

See also message type 15: incident plan in Section 3.3.15.

3.3.2 Message Type 2: Alarms

See also message type 24: site status in Section 3.3.24.

3.3.3 Message Type 3: ANTTS

3.3.4 Message Type 4: Congestion

3.3.5 Message Type 5: Controller Details

3.3.6 Message Type 6: Date and Time

3.3.7 Message Type 7: Detector Count

3.3.8 Message Type 8: Dwell

3.3.9 Message Type 9: Error

3.3.10 Message Type 10: Event Log

3.3.11 Message Type 11: Extended Controller Details

See also message type 5: controller details in Section 3.3.5.

3.3.12 Message Type 12: Extended Region Details

See also message type 19: region details in Section 3.3.19.

3.3.13 Message Type 13: File

3.3.14 Message Type 14: Green Window

3.3.15 Message Type 15: Incident Plan

See also message type 1: Action List in Section 3.3.1.

3.3.16 Message Type 16: Licence Validation

3.3.17 Message Type 17: Locks and Trims

3.3.18 Message Type 18: Ramp Metering System

3.3.19 Message Type 19: Region Details

 list of sites and their subsystem numbers.

3.3.20 Message Type 20: Route Pre-emption

3.3.21 Message Type 21: Server Registration

3.3.22 Message Type 22: Site Graphics

 corner island dimensions

See also message type 23: site layout in Section 3.3.23.

3.3.23 Message Type 23: Site Layout

See also message type 22: site graphics in Section 3.3.22.

3.3.24 Message Type 24: Site Status

3.3.25 Message Type 25: Strategic Monitor

3.3.26 Message Type 26: System and Site Notes