scats 6.9.1 release review smug, march 2013 sydney

40
SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

Upload: evangeline-townsend

Post on 18-Dec-2015

234 views

Category:

Documents


10 download

TRANSCRIPT

Page 1: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

SCATS 6.9.1 Release Review

SMUG, March 2013Sydney

Page 2: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

2SMUG 2013

SCATS 6.9.1 Release Review

This presentation describes the new featuresintroduced in

SCATS 6.9.1 Commercial Release.

Page 3: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

3SMUG 2013

SCATS 6.9.1 Release Scope

• 22 new features• 19 enhancements• 24 major issues resolved

In operation at TMC since January 2012 – V6.9.1.1

Commercial release prepared in November 2012 – V6.9.1.11

SCATS 6.9.1 Release Summary

Page 4: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

4SMUG 2013

SCATS 6.9.1: What’s new

The major changes in this version are:• Support for Windows® 7 and Windows® Server

2008 R2.• Support for virtual environments and network

dongles to allow for automatic failover or disaster recovery plans.

• An increase in the number of MSS, RSF and XSF flags from 16 to 32.

• The ability to lock and trim all flags, except MSS flags.

Page 5: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

5SMUG 2013

SCATS 6.9.1: What’s new – cont’d

The major changes in this version are:• Better support and monitoring of secret walks.• Improved controller fault management.• New variation routines for resetting the state and

implementing a logical AND between tests.• Ability to import the SCATS host licence name and

licence details from the licence file into the two configuration programs

Page 6: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

6SMUG 2013

SCATS 6.9.1: New Features - 1

Time Gain Changes• The rule introduced in v6.6.3.2 that time gain could only

be accepted from phases that were allowed to gap has been removed!

• A sanity test is now applied to time gain at the end of each phase that fixes TG build-up observed in Master-Isolated mode and skipping of the stretch phase.

• Time can now be gained from skipped phases when a dwell is applied.

Page 7: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

7SMUG 2013

SCATS 6.9.1: New Features - 2

Walk monitoring – includes secret walks• An RPS request is now sent to all controllers every

second to get the demanded walks and the active walks.

• Site diagnostic monitor (IDM) files now show when a walk ended rather than when a walk termination request was sent.

• The capture of the intersection status when an SC, LC or IH alarm is generated will also show secret walks (eg More… in Access).

Page 8: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

8SMUG 2013

SCATS 6.9.1: New Features - 3

ST alarm (NXP) review• The failure of a controller to answer an NXP/CLP message

within 8 seconds now generates Fallback instead of an ST alarm.

• An ST is generated only when no messages at all are received for 8 seconds.

• Generate an ST alarm if NXP reply is 16 seconds late – TS mode

• The processing of the Special Facilities for an intersection (Y-, Z-, Z+, Z1-6, XSF, RSF) are now done for intersections that are not communicating as they could be used by Variation Routines.

Page 9: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

9SMUG 2013

SCATS 6.9.1: New Features - 4

Improved controller fault log management• SCATS can now detect a deadlock when a controller

fault log is being automatically retrieved. The fault is logged and SCATS will retry after 60 seconds which allows RAM/IMAP changes to be saved.

• The controller log can now be saved to the SCATS log file when a controller has a WD alarm.

• The AL/ command in SCATS Terminal now resets the flag that allows an RLE fault (Read Log Entry) to be logged.

Page 10: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

10SMUG 2013

SCATS 6.9.1: New Features - 5

Variation Routines• New variation routine to AND (VR18), implemented.

When "test" routines follow each other, there is an implied AND between the routines.

When an OR is used (VR19), as in A OR B AND C, you get A or (B AND C).

If you want (A OR B) AND C you must use VR18 for the AND. VR18 also allows (A OR B) AND (C OR D)

• VR83 (Test an SA for congestion) now compares the user supplied DS against the DS from the SI, not the split plan vote DS.

Page 11: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

11SMUG 2013

SCATS 6.9.1: New Features - 6

Variation Routines• A variation routine (VR10) has been added to reset the

variation routine state to true

• It is now recommended that you use VR10 instead of VR19 (the OR routine) if you need to reset the state.

• The Variation Routine Usage dialogue now includes the stop routine (VR0) and longer descriptions.

Page 12: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

12SMUG 2013

SCATS 6.9.1: New Features - 7

Variation Routines• All the variation routines

are now shown in the Variation Routine Monitor dialogue with an icon and description. The icon identifies the type of variation routine or whether it has been skipped, bypassed or is unknown. A shortcut menu provides a legend for the meaning of the icons.

Page 13: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

13SMUG 2013

SCATS 6.9.1: New Features - 8

SCATS Flags• All flags except MSS can be locked or trimmed to an ON

state or an OFF state. • Each flag is managed separately.

• A trim cannot be applied if the flag is locked.

• SF and XSF locks no longer require a split plan lock to be applied (i.e. no PL=0#! Needed)

• SF and XSF trims clear on a split plan change.

Page 14: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

14SMUG 2013

SCATS 6.9.1: SCATS Flags - 1

Flag Types• SF Special Facilities: Y-, Z+, Z-

No Change• XSF Extra Special facilities

Increased from 16 to 32 including Flexilink plans, VC6.1

• MSS Miscellaneous StatusIncreased from 16 to 32 including Flexilink plans,

VC6.1• Z Z1 to Z6

No Change• RSF Remote Special facilities

Increased from 16 to 32, any controller

Page 15: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

15SMUG 2013

SCATS 6.9.1: SCATS Flags - 2

• Indication of a trim or a lock in Access

No flag locks or trims

At least one flag is trimmed, no locks

At least one flag islocked, there can be trims

Page 16: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

16SMUG 2013

SCATS 6.9.1: SCATS Flags - 3

• The Special Facilities form Shows current state of all flags Indicates the presence of locks and trims

At least one lock,there can be trims

At least one trim,no locks

No locks or trims

Page 17: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

17SMUG 2013

SCATS 6.9.1: SCATS Flags - 4

• Opening a Flag Selector form Click a button for the desired flags Can open multiple selection forms

Page 18: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

18SMUG 2013

SCATS 6.9.1: SCATS Flags - 5

• The Flags Selector form Shows the current state of the flags of that type Shows locks and trims Apply trims ON or OFF Apply locks ON or OFF Remove a lock or trim Show the Locks and

Trims form

Page 19: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

19SMUG 2013

• The Flags Selector form Applying a lock or trim

• Select the state› Click the ON or OFF button

• Select the type› No Lock for trim› Permanent or timed

for a lock

• Click Apply

Removing a lock or trim• Locks and trims are shown

in the top section• Select the lock or trim

to be removed› Click the button with the

lock or trim icon

• Click Apply

SCATS 6.9.1: SCATS Flags - 6

Trimmed ONLocked OFF

Page 20: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

20SMUG 2013

SCATS 6.9.1: SCATS Flags - 7

• Displaying details of locks and trims Click the “Locks and Trims…” button on the Special Facilities form

or the Flags Selector form to display the Locks and Dwells form.

Shows if flag stateis ON or OFF

Page 21: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

21SMUG 2013

SCATS 6.9.1: New Features - 9

• Network intersection IP addresses are now persistent, * indicates inactive

Page 22: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

22SMUG 2013

SCATS 6.9.1: New Features - 10

• IP address of GUI client is always displayed in Workstation list

Page 23: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

23SMUG 2013

SCATS 6.9.1: New Features - 11

• Ability to monitor ISS stretch phase bias in Access

• Form isrearranged!

Page 24: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

24SMUG 2013

SCATS 6.9.1: New Features - 12

• Short-cuts defined for SI/SA/LK configuration forms to show their monitor forms, and vice versa

Page 25: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

25SMUG 2013

SCATS 6.9.1: New Features - 13

Region request log message• message format is modified to include unknown site request

as specified below,"region request at CM from SENDER_IPADDR for Site SITEID

replied with (REGNAME at REG_IPADDR:REG_NETPORT)"

or

"region request at CM from SENDER_IPADDR for Unknown site

SITEID"

Page 26: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

26SMUG 2013

SCATS 6.9.1: New Features - 14

Allow master subsystem to rotate (correcting offset errors)

• Early study results Increased number of rotations while Reduced CL modifications Applies between 2 to 10 subsystems

Page 27: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

27SMUG 2013

SCATS 6.9.1: New Features - 15

Force controller clock update even if site is on fallback• New Region option RK=RC or IK=RC• A new Reset Clock button to force a clock update

• Good for customers who do not use Flexilink

Page 28: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

28SMUG 2013

SCATS 6.9.1: More features

• VE alarms can be cleared – validation retry is reattempted.

• The change of a controller's dimmed lamp state is now logged

The current state is also logged at midnight.

• The Fallback panel in SCATS Access is no longer set by an intersection on fallback that's a member of a subsystem that's on fallback.

Additionally, intersections that are members of a subsystem that is on fallback are no longer included in the fallback summary display

Page 29: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

29SMUG 2013

SCATS 6.9.1: More features

• Number of dwell stores has been increased from 4 to 30

• Number of simultaneous IDM collections increased from 30 to 64

• Limit for daily average volume (AV) increased from 32767 to 65535

• Copy contents of Location field into the Remarks field by double clicking on the remarks field in SCATS Access Route Plan

editor

Page 30: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

30SMUG 2013

SCATS 6.9.1: Issues addressed - 1

• Reported lamp faults are now displayed in System Status Summary

Page 31: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

31SMUG 2013

SCATS 6.9.1: Issues addressed - 2

• Copying an intersection’s data with the "Use" button now works

Page 32: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

32SMUG 2013

SCATS 6.9.1: Issues addressed - 3

• Menu shortcuts (Ctrl+C, Ctrl+X, Ctrl+V, etc.) were not enabled as specified so it was not working all the time

Page 33: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

33SMUG 2013

SCATS 6.9.1: Issues addressed - 4

• Buffer overflow reported by VicRoads when there CM crashed

• Region crash during sending region status message last intersection in the defined slots has an LF loop count loses its

value and crashes

• Region crash when logging an FTP lock

• Region crash when saving Variation Routine 5 in SCATS Access before nominating an MSS bit

Page 34: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

34SMUG 2013

SCATS 6.9.1: Issues addressed - 5

• TG calculations (bug fix) No time gain is obtained from skipped phases when a dwell is

applied Master Isolated - TG wrongly builds up from a number of cycles

• SI phase time not being set to zero when being skipped

• Any intersection with > 4 split plans and 7 phase (TCS 2861)

The details in Access not shown correctly – first 10 – 15 sec Reported as incorrect Hurry call operation and showing locks/trims

that are not applicable

Page 35: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

35SMUG 2013

SCATS 6.9.1: Issues addressed - 6

• Variation routine monitor The on-entry and on-exit values displayed is wrong for VR98 (Skip

next entry on FALSE) and VR99 (Skip next entry on TRUE)

• VR15 (the count routine) does not clear the SCATS flags if the count type is changed

• Skip checkbox missing for VR99 (Skip next entry on TRUE)

Page 36: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

36SMUG 2013

SCATS 6.9.1: Issues addressed - 7

• Actual link mode is shown and updated in Time/Distance diagram

• Flexilink data dialogue validation check for an invalid pulse time highlights incorrect field

• SCATS Log Log includes parked alarms and events if a site (s) is specified in the

filter

• Alarm Analyser Machine re-start reported as crash on Windows Server 2008 R2

Page 37: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

37SMUG 2013

SCATS 6.9.1: Release available

• SCATS 6.9.1 Release is available and recommended to deploy.

• Release notes must be reviewed prior to installation.

• User Manuals are up to date.

• HASP Device drivers are updated.

• Need a new licence – contact SCATS Help!

Page 38: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

38SMUG 2013

SCATS 6.9.1: Known issues

• SCATS Flags (child dialogues) not updated when monitored site changed

• Communications status not updated in 'Controller communications' dialogue

• Invalid input to Local (or Controller) Times would yield a deadlock in SCATS Access

Page 39: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

39SMUG 2013

SCATS 6.9.1: Known issues

• DO NOT USE – RK=LS!

• 16 plans – do not overload variation routines

• New Access ( > 6.8.3.0) with old region (6.5.0.2 and 6.8.3.0), increase number of plans in Site Edit destroys the slot data – site configuration is lost

Page 40: SCATS 6.9.1 Release Review SMUG, March 2013 Sydney

40SMUG 2013

SCATS 6.9.2: Next step

• Maintenance Release 6.9.2 is now compiled.

• Objective of SCATS 6.9.2 is to provide a maintenance release addressing outstanding defects and change requests.

• Scope to resolve all outstanding major defects for greater system stability and reliability.

• A few enhancements are in consideration.