ASTRID and INGRID User Guide
Contents
1. Reason 2 Current occupancy 96 3 Smoothed occupancy 46 4 Dispersed occupancy 46 131 Detector DET Sat flow Reason 1 Cur2 Sm3 Dp4 Detector Detail Calculation of saturation flow Reason 2 Current saturation flow veh h 3 Smoothed saturation flow veh h 4 Dispersed saturation flow veh h I32 Detector DET Sat time Reason 1 Cur2 Sm3 Dp4 Detector Detail Calculation of saturation time Reason 2 Current saturation time s 3 Smoothed saturation time s 4 Dispersed saturation time s I33 Detector DET Cur up marker Detector Detail Current up marker none I34 Detector DET Cur down marker Detector Detail Current down marker none I35 Detector DET Cur flags Up 1 2 Down 3 4 Result 5 Detector Detail Issue 30 Page 50 ASTRID and INGRID User Guide 7 3 36 7 3 37 7 3 38 px 7 3 40 Description Parameters I36 Message Format Type Class Description Parameters I37 Message Format Type Class Description Parameters I38 Message Format Type Class Description Parameters I39 Message Format Type Class Description Parameters I40 Message Format Type Class HS16940_V32 doc 666 HS 16940 000 Current flags 1 Up flow flag 2 Up occupancy flag 3 Down flow flag 4 Down occupancy flag 5 Result no flag M current up flag N current down flag reference up flag reference down flag 136 Det2. The data will include a header indicating the meaning of each column Some of these descriptions are abbreviated Files extracted from ASTRID will be stored on the TMC from where they may be transferred to a PC using drag and drop techniques The extracted files will be found in the shared directory ASTRID OUT on the TMC of either an Alpha based UTC System or A PC SCOOT System HS16940_V32 doc Issue 30 Page 31 ASTRID and INGRID User Guide 666 HS 16940 000 File Edit View Favorites Tools Help Bak O F Ph res M d F 4 4 On Line Help Each screen contains an on line help facility To access the help facility select the help button In the event of a conflict between the on line help text and this document The on line help text should be followed In the event that features are found in the ASTRID interface that are not included in this document on line help should be consulted HS16940_V32 doc Issue 30 Page 32 ASTRID and INGRID User Guide 666 HS 16940 000 9 ASTRID ADVANCED OPERATION 5 1 Introduction ASTRID version 3 4 is designed to accept data from a variety of sources Provided this data is presented in an acceptable format the ASTRID data base will store and display such data The Transport Research Laboratory document ASTRID design change note ADCN 97 2 refers see 1 3 8 The ASTRID software is designed to accept command line instructions to set up the input and display of new data types This proced
3. 3 5 Summary of Data Types code level message param units description flow link M02 ps veh h Flow stops link M02 D I veh h Stops del link M02 p7 veh Delay cong link M02 p10 Congestion dsat link MOS p5 Saturation hflwc link M45 p5 veh h Historic cycle flow hfiwg link M45 p veh h Historic green flow hlenc link M45 p6 S Historic cycle length hleng link M45 ps S Historic green length rflow det M29 D I veh h Det flow rocc det M29 p Det occ slen stg M17 p5 S Stage length The parameters p5 p6 etc represent the parameters in a SCOOT message HS16940_V32 doc Issue 30 Page 13 ASTRID and INGRID User Guide 666 HS 16940 000 4 4 1 4 2 4 3 4 3 1 ASTRID USER INTERFACE Introduction The ASTRID user interface has been specially developed to provide an advanced user friendly method of extracting and displaying graphical information from the ASTRID data base This interface is only available on STC systems ASTRID displays are based on colour graphs different colours being used to display the various parameters The ASTRID interface is designed for operators with a good working knowledge of STC UTC systems SCOOT and basic traffic engineering Set up Before ASTRID can be used information must be passed from the UTC system to the ASTRID data base To enable ASTRID for the whole system the following commands should be entered MESS M02 N gt ASTRID MESS MOS N gt ASTRID MESS M17 N gt ASTRID
4. Converted F10 data 1 Period s 2 Saturation flow veh h I44 Detector DET Ref 1 Sat flow 2 Detector Detail Reference data 1 Index 2 Saturation flow veh h 145 Detector DET Ref 1 2 3 Flow 4 Occ 5 Detector Detail Reference data 1 Hour Issue 30 Page 52 ASTRID and INGRID User Guide 7 3 46 7 3 47 7 3 48 7 3 49 7 3 50 146 Message Format Type Class Description Parameters 147 Message Format Type Class Description Parameters 148 Message Format Type Class Description Parameters 149 Message Format Type Class Description Parameters I50 Message Format Type Class Description Parameters HS16940_V32 doc 666 HS 16940 000 2 Minute 3 Index 4 Flow veh h 5 Occupancy 146 Detector lt DET gt Ref 1 2 3 Sat flow 4 Detector Detail Reference data 1 Hour 2 Minute 3 Index 4 Saturation flow veh h 147 Detector DET Fault 1 Empty 2 Full 3 Good 4 Detector Detail Fault detectors 1 Fault 2 Empty ivl 3 Full ivl 4 Good ivl 148 Detector DET Detector faulty 1 full empty ivls Detector Detail Detector is faulty 1 Number of full 20 or empty 0 intervals I49 Detector DET Detector OK Detector Detail Detector is OK none I50 Area Area All detectors set faulty Area Detail All detectors set faulty none Issue 30 Page 53 ASTRID and INGRID User Guide 666
5. This screen allows the LPU factor used by SCOOT to be changed This allows flow rates and vehicle content to be taken into consideration The LPU factor is used to determine counts A SCOOT detector may be calibrated to calculate approximate vehicle counts after a survey is performed The survey is carried out by measuring the number of LPUs at a SCOOT detector over the same period that vehicles that cross the detector are counted An LPU conversion factor is calculated on this basis For more information consult the following commands in the UTC Operator Handbook SSSU ASLD and LLCF If no data is entered in this screen the LPU factor will be taken as 17 HS16940_V32 doc Issue 30 Page 26 ASTRID and INGRID User Guide 666 HS 16940 000 EI assignteueenversionfaeters LC N04131E 11 4 Link name N04131G 12 4 T N04131H 17 0 N041311 LPU to vehicle count conversion factor N04131Z i NO4141A NO4141B NO4141C NOH HE NOH HF NO041 44C N04144D N10124E N10311A N10311C 4 Speed This screen allows link length and cruise speed to be entered From this information speed is derived If no data is entered no speed data will be displayed Link Speed Information NO4131E Link name NO4131G T N04131H N04131Z il NO4141A NER N04141B Cruise time along link s N04141C P NO4141E NO4141F NO4144C N04144D N10124E N103114A N10311C HS 16940 V32 doc Issue 30 Page 27 ASTRID and INGRID Use
6. Total Stops 3 Total Delay 4 Congestion 5 SAT HS16940_V32 doc Issue 30 Page 17 ASTRID and INGRID User Guide 6 7 Stage Length Vehicle Delay Site Type Node 1 2 3 4 5 6 7 Total Flow Total Stops Total Delay Congestion SAT Stage Length Vehicle Delay Site Type Stage 1 Stage Length Site Type Link 1 2 3 4 5 6 7 8 9 10 41 Total Flow Total Stops Total Delay Congestion SAT Vehicle Delay Speed Journey Time Congestion Index Vehicle Occupancy LPUFactor Site type Route 1 2 3 4 5 6 HS16940 V32 doc Total Flow Total Stops Total Delay Congestion SAT Vehicle Delay 666 HS 16940 000 Issue 30 Page 18 ASTRID and INGRID User Guide 4 3 4 Site Type Det 1 Det Flow 2 Det Occ Site Type Group 1 CP Total Entries 2 CP Exits 3 CP Occupancy Site Type Car Park 1 CP Total Entries 2 CP Exits 3 CP Occupancy Site Type Cnt 1 Total Flow 666 HS 16940 000 1 asmposy LI Site Type Node 7 Data type Backup Bac Pro Bac Bac 1 type Site N01121 N01131 N01211 N01221 N01222 N01231 N01232 NO1241 N01311 N01321 Weekdays _ Mo zl Tu we c Th B rr Bl sa _ Su Times Dates lt gt 00 24 Start EE 1 Feb 1998 lt gt 00 07 lt gt 07 10 EU 10 16 41 Feb 1998 lt gt 16 19 lt gt 19 24 options Graph Type Extract Figure 4 A
7. the configuration program will automatically create an INGRID region for each SCOOT region and include such upstream and downstream detector information as can be derived from the SCOOT database You can choose to use this data as a starting point or delete the regions and create your own data from scratch The following diagram shows the configuration dialog f ingrid configuration 1 0 efti Incident Regions Incident Detectors All detectors available RSX mmm MEE 4 N04131E1 N07421B1 N04131G1 N07411F1 EF N04131H1 N04131I1 N06232B1 N04141A1 N04141B1 NO4141C1 NO4141E1 N04141F1 N04144C1 N04144D1 N10124E1 N10311A1 N10311C1 N10311F1 N10311H1 Downstream detectors N1031171 N07371E1 N10321B1 N10321D1 N10321E1 N1033141 N10331B1 Upstream detectors N07421E1 N10331E1 N10341CI IF N10341D1 Cancel Add Region Delete Region Figure 7 INGRID Configuration dialog To create a region click on Add Region The following dialog will be displayed requesting a region name This can be any text string up to 25 characters The region will be added to region list HS16940_V32 doc Issue 30 Page 40 ASTRID and INGRID User Guide 666 HS 16940 000 ndanegionbislos popup E7 Selection Been 6 4 M To set up the upstream and downstream detector information select the region from the region list The incident detectors list will now sho
8. Description Parameters DO Message Format Type Class Description Parameters HS16940_V32 doc 666 HS 16940 000 5 Number of algorithms 125 Detector lt DET gt Affected down det 1 Alg 2 Detector Detail Affected down detector 1 Detector 2 Algorithm 126 Detector DET Affected up det 1 Alg 2 Detector Detail Affected up detector 1 Detector 2 Algorithm 127 Detector DET Add 1 Case 2 Dur 3 Sev 4 Alg 5 Conf 6 Detector Detail Add incident 1 Add 2 Case 3 Duration 4 Severity 5 Algorithm 6 Confidence 128 Detector lt DET gt Affected det 1 Alg 2 Detector Detail Affected detector 1 Affected detector 2 Algorithm 129 Detector DET Flow Detector Detail Calculation of flow 1 Reason 2 Current flow veh h 3 Smoothed flow veh h 4 Dispersed flow veh h Reason 1 Cur 2 Sm3 Dp 4 Issue 30 Page 49 ASTRID and INGRID User Guide 666 HS 16940 000 7 3 30 130 Message Format Type Class Description Parameters 7 3 31 131 Message Format Type Class Description Parameters 7 3 32 132 Message Format Type Class Description Parameters 7 3 33 133 Message Format Type Class Description Parameters 7 3 34 134 Message Format Type Class Description Parameters 7 3 35 135 Message Format Type Class HS 16940 V32 doc 130 Detector DET Occupancy Reason 1 Cur2 Sm3 Dp4 Detector Detail Calculation of occupancy
9. Message Format Type Class Description Parameters I22 Message Format Type Class Description Parameters I23 Message Format Type Class Description Parameters I24 Message Format Type Class Description Parameters HS16940_V32 doc 666 HS 16940 000 Area Logging Keep alive INGRID none 120 Detector lt DET gt W138 1 Up 2 Repeated Down 4 Repeated Incident Detector Logging Incident detected 1 Incident detector 2 Up detector affected 3 repeated 4 Down detector affected 5 repeated 121 Detector lt DET gt W139 1 Incident clearing Detector Logging Incident clearing 1 Incident detector 122 Detector DET W140 1 Incident cleared Detector Logging Incident cleared 1 Incident detector 123 Detector DET Severity 1 2 Aff 3 Detector Detail Calculation of severity 1 Severity 2 Severity text 3 Number of affected detectors 124 Detector DET Confidence 1 2 Dur 3 Aff 4 Algs 5 Detector Detail Calculation of confidence 1 Confidence 2 Confidence text 3 Duration min 4 Number of affected detectors Issue 30 Page 48 ASTRID and INGRID User Guide 7 3 25 7 3 26 7 3 27 7 3 28 7 3 29 125 Message Format Type Class Description Parameters 126 Message Format Type Class Description Parameters 127 Message Format Type Class Description Parameters 128 Message Format Type Class
10. SA uu EE 17 Stage Lenbth EE 17 Total Delay teo e tere 17 Total Flow eese eene 17 Total Stops ede ed tpe teen 17 Vehicle Delage 17 Site Type Car park CP OGCCUpatiCys ito EE EE 19 Site Type Cat Park iii oues eee 19 ed SE Ee sies 19 CP Total Entries etre 19 SIR AAI EE EE EG 19 Site Type Det AE NEER HO 19 Det AAR EE EE 19 Det OE Ee Rete IRE 19 Site Type Group 19 die ei RR EE ET 19 HS 16940 V32 doc 666 HS 16940 000 CP OCCUPANCY eege EES VERE Eseg RE Ek se ERGE SEG 19 CP Total Entries inen Ds EDE ee GE Gis 19 Site Type Link esse esse ee ee Re Re 18 CORng SEOn ee GE RE ESE eR 18 Congestion Index seeen 18 Journey E EE 18 LPU ie GE ME OE ein 18 Queue at Start of Green 18 yu E 18 Speed in qun ME 18 Total Delay erroe itr obere Eege 18 Total Blow esee oho rele 18 Total StOps nieder EE 18 Vehicle Delay AE EE ER RE 18 Vehicle Occupancy 18 Site Type Node enne Ree RERO RS 18 Congestion idrar sees ee ee ee Re Re 18 Queue at Start of Green 18 SAT E 18 stapel ens aoc tens EO PUES 18 Total Delay s a seges seges reperit ror teretes 18 Total Blow AR OE EE OE EE 18 Total Stops C s 18 Vehicle Delay tie ina EE RR 18 Site Type Region iese esse esse ee se ke Re ee 17 Congestlon ER RA Ren 17 Queue at Start of Green 18 SA EO 17 Stage Lensth annee AE aei eersiet 18 Total Delay EE 17 Total BLOW d 17 Total MODE rere Hei eee eee a
11. When a day is selected the day button changes to a depressed state Times Window This window selects the time range to be displayed Only one selection can be made When a time range is selected the range button changes to a depressed state HS16940 V32 doc Issue 30 Page 21 ASTRID and INGRID User Guide 666 HS 16940 000 4 3 9 4 3 10 Dates The dates windows are controlled by the graph types selection With some selections the dates windows are not available Start The dates start window allows start dates to be selected Selection is made by moving the slider from left to right The top slider selects days The middle slider selects months The lower slider selects years The selected date is displayed above the sliders End The dates end window allows end dates to be selected Selection is made by moving the slider from left to right The top slider selects days The middle slider selects months The lower slider selects years The selected date is displayed above the sliders p Asmpboispy Tr ifo Veekd a ime Site Type Dates Start 1 Feb 1998 Display Options Data Collection Advanced Display Grid Routes Messages Colours Holidays Graphs Graph type End LPU Factors 1 Feb 1998 Profile 7 Speeds Scale type Variable OK Help iem d ASTRID Display Options selected Options The display Options window is sub divided into pull down w
12. a bb A A 1 5 Issue State and Amendment cccccccsssssssscccccssscsssscccccccccesscssccecccccccssssscecccceccssssscesccceecsssssccccsees 2 BASIC DESCRIPTIONS sisi es OE ee Eua EG DES E ECKE E Ge Ge ER 6 3 ASTRID DATA BASE sesse esse nito tcn ee ttai th ub dad gu dk We Ewe gu co Y i N N Ka ev nde 7 3 1 sources of Data v M er 3 2 Database Organisation eeesssesessoesesosesesosesesosesssocssssosssssesessoessssoesesosesesosesesosesesosesssosssssesssssessse 7 3 3 Basic Data rp LO 3 4 Derived rico seide esse dese dee ee de de deed ed so ed Ge doe oie eo sed Gee Ges eg de ed ees de gees LA 3 5 Summary of Data TYDES esse esse sesse ee see Ge Ge AA Ge Ge AA ee ee ee ee see see ss LO 4 ASTRID USER INTERFAGE se ses ns ee ee we is CM Se es di Ge We GR 14 4 1 Jedi Deg E EE EE EE EE GS 4 2 KI ONE 4 3 ASTRID Display Control Window ee eeee eese Ge eerte enses Ge sse ee ee see ees sees 14 4 4 On Line DIE E 5 ASTRID ADVANCED OPERATION essens nasien ees ie ie ee ee ie ee ie ee ae 33 5 1 Hcet a 5 2 il TE IE OE N EE EE OE EE Pn 5 3 cid M S Iz 6 INGRID ec 38 6 1 TE aie Te GE OE N OO 6 2 INGRID Data EE OE EE EE ME 6 3 INGRID Configuration eese ee ee GE AE Ge Ge AG Ge ae ee sees see OD 6 4 INGRID
13. is converted into an appropriate format ASTRID can also process data from sources other than SCOOT ASTRID was originally developed at the University of Southampton for the Transport and Road Research Laboratory as an off line version running on an IBM compatible PC ASTRID has been further developed into an on line version as part of the DRIVE 2 projects HERMES and SCOPE ROMANSE and received funding from DIM division Department of Transport This version has been operating successfully in Southampton and London since 1993 ASTRID is a database designed to collect information from a SCOOT traffic control system or other source of time varying traffic data and to store it in a database for later retrieval and analysis The name ASTRID means Automatic SCOOT Traffic Information Database The on line version of ASTRID runs on a computer operating under the Open VMS operating system In the past ASTRID has required a separate machine for its operation Feasibility studies showed that it was possible to run ASTRID in the same machine as a UTC system and ASTRID has now been issued to allow this to be used in practice ASTRID is covered in sections 3 to 5 INGRID The INGRID INteGRated Incident Detection system was developed to automatically detect incidents in urban areas The systems uses information from SCOOT and the ASTRID database of traffic conditions INGRID runs in real time on an OpenVMS UTC system or A PC SCOOT UTC system The
14. message ASTC ASTRID Configuration seng LSTM List SCOOT messages inc INGRID Configuration NODT Transfer Node to a new region Accept Clear ACCT Action CAST by Cycle Time XACC Cancel Action CAST by Cycle Time ASTRID Display Site Type Site Weekdays Dates Cnt D01121 E Mo Start D01122 1 Feb 1998 Data type DO1231 Cl Tu D01232 Vehicle Flow D01311 m we D01312 E Th Graph type D02111 F Backup D02112 B rr 1 Feb 1998 D02211 E sa D02212 D03111 I Su Variable ECH options L View Print Extract Close Help B Figure 1 ASTRID Display Control Window Scale type The control window in divided into a number of pull down and selection windows buttons Some of the main windows lead to other selection windows ASTRID displays are selected using these windows and displayed using the View button 4 3 2 Site Type The Site Type pull down window is used to select the basic display Changing the site type may also change options available in other windows When a site type is selected the available sites are automatically shown in the Site window HS16940_V32 doc Issue 30 Page 15 ASTRID and INGRID User Guide 666 HS 16940 000 ASTRID Display Site Weekdays Times Dates Node Mo 00 24 Start N01121 1 Feb 1998 Sage N01131 E Tu lt gt 07 19 Link N01211 Det N01221 Brute N01222 Ej Th lt gt 07 10 NO1231 Si N01232
15. set to fixed Enter an expected maximum value for the data in this field You can specify different Y scales for different site levels e g 100 N 200 AR 1000 The levels are as used in the Define data sets to extract from SCOOT messages window In the example the Y scale is 200 for Node level 1000 for Area and Region levels and 100 for all other site levels 5 Data Units for display Enter a text string to display on the Y axis 6 Use LPU Factor HS16940_V32 doc Issue 30 Page 36 ASTRID and INGRID User Guide 666 HS 16940 000 Select Yes if the data is in LPUs and you wish to convert the LPUs to vehicles The conversion factor specified on the LPU factor screen will be used or 17 if no conversion factor is defined for the site HS16940_V32 doc Issue 30 Page 37 ASTRID and INGRID User Guide 666 HS 16940 000 6 6 1 INGRID Introduction Congestion is a problem in urban areas Vehicles are delayed pollution increases and drives become frustrated As traffic levels continually rise congestion becomes an ever increasing part of urban life Traffic incidents often cause or exacerbate congestion A traffic incident could be an accident a broken down vehicle or a slow moving lorry If such incidents could be detected action could be quickly taken to stop the congestion spreading around the network Automatic traffic signal control systems such as SCOOT try to optimise traffic signals to minimise delays to d
16. 00 2000 veh h rocc Det Occ 0 100000 100 slen Stage Length 1 000000 100 s cpin CP Entries 1 000000 500 veh h cpout CP Exits 1 000000 500 veh h cpocc CP Occupancy 1 000000 500 veh vdel Vehicle Delay 0 100000 60 s speed Speed 1 000000 60 km h jtime Journey Time 0 100000 120 s cidx Congestion Index 0 000000 10 vocc Vehicle Occupancy 1 000000 2000 ms veh Ipuf Lpu Factor 0 000000 30 Ipu veh Cancel 666 HS 16940 000 Data name stops Full Data Name for display Factor to multiply data to convert to data units Y scale for one or more site levels Data units for display Use LPU Factor No E Remove The list on the left shows the existing data types To add or modify an entry enter values for each of the fields on the right The fields have the following meanings 1 Data Name This is the data that you want to display These data names are defined on the messages configuration window There are also some built in derived data types that ASTRID supports 2 Full Data Name This is the name of the data type that is displayed on the graph and on the Data Type option menu on the main ASTRID window Put required oe 99 where spaces are 3 Factor to Multiply Data to Convert to Data Units This figure can be a fractional value 4 Y Scale for One or more Site Levels This is the value that is used for Y scale on graphs when the scale type is
17. 1 20 vflow F01 57 lt gt 0 0 300 AVE AGV 12 1 20 Multiplier qclr M11 5 5 0 0 300 AVE LNART 1 1 20 Data parameter Fault Parameter Period parameter Maximum valid period AVE add up normally Collect for these site levels Divisor Smoothing Factor Rejection data name optional Rejection sample size Rejection std deviation Rejection smoothing factor Cancel Remove The list on the left shows the existing data categories Selection of an entry expands that entry into the fields on the right HS16940_V32 doc Issue 30 Page 33 ASTRID and INGRID User Guide 666 HS 16940 000 The fields have the following meaning 1 Data Name This field contains the name of the category The name should contain no more than 6 alphabetical characters 2 Message Number This is the SCOOT message from which data is to be extracted 3 Data Parameter This field contains the data parameter to be extracted from the SCOOT message It should be noted that the first parameter containing data is No 5 4 Fault Parameter This field contains the data parameter 5 Fault Parameter Test From this screen select the appropriate comparison to apply to the fault parameter which if true indicates that the data is faulty 6 Interval Parameter If non zero this value specifies the message parameter from which the period for the data can be extracted The value in the message must be in seconds If this v
18. 3 1 Default 0 INKE A INGRID Keep flag This is the INGRID keep flag This parameter should be left at 1 Values for CHAN are 0 to 1 Default 1 INSO 3 A INGRID Severity Ranges There are 4 INGRID severity ranges INSO INS1 INS2 and INS3 The severity of an incident is determined from the number of detectors affected by the incident The INSO to INS3 values set the ranges to convert the number of affected detectors to a severity Values for CHAN are 1 20 Defaults are INSO 1 INS1 3 INS2 6 INS3 9 INSE A INGRID Severity Filter Values for CHAN are 1 5 INGRID will not report an incident unless the severity is greater or equal to the Severity Filter value The severity is determined by the number of upstream and downstream detectors which are affected by the incident Values for CHAN are 1 5 Default 0 INGRID Messages The various messages which may be output from INGRID are explained below Each explanation comprises the following Format The format shows the layout of the message in terms of its SCN and parameters Type The Type of the message is the level at which it can be selected i e area or detector Class The class of the message is a classification into user logging or detail User messages are intended for the user logging messages are intended for recording in a log file and detail messages are intended to give information at a detailed level less likely to be of interest to the user Descr
19. 95 ASTRID version 3 3 user guide ASTRID design change note ADCN 95 2 ASTRID version 3 4 external interface ASTRID design change note ADCN 97 2 INGRID V1 5 User Guide Design Change Note IDCN 99 4 Definitions For all definitions and abbreviations used in this and related UTC documentation see 666 KE 16066 000 UTC Glossary of terms HS16940_V32 doc Issue 30 Page 4 ASTRID and INGRID User Guide 1 5 666 HS 16940 000 Issue State and Amendment Issues 01 00 to 16 00 Issue 17 00A Issue 17 00B Issue 17 00 Issue 18 00 Issue 19 00 Issue 20 00 Issue 21 Issue 22 Issue 23 Issues 24 to 27 Issue 28 Issue 29 Issue 30 HS16940_V32 doc Not issued First draft Updated after review First issue Not Issued Not Issued Addition of export file header formats Issue number updated to reflect software version Not issued Details of INGRID V1 6 added Not issued Updated for PC SCOOT Not issued Issue update only no other changes Issue 30 Page 5 ASTRID and INGRID User Guide 666 HS 16940 000 2 2 1 2 2 BASIC DESCRIPTIONS ASTRID The SCOOT Urban Traffic Control system optimises signal timings in a network to minimise stops and delay Data used by the SCOOT model in the optimisation process such as delays flows and congestion are available to traffic engineers through the ASTRID database system which automatically collects stores and processes traffic information for display or analysis If the data
20. ASTRID and INGRID User Guide 666 HS 16940 000 Siemens Mobility Traffic Solutions Sopers Lane POOLE Dorset BHI7 7ER SYSTEM PROJECT PRODUCT STC UTC SYSTEM ASTRID and INGRID User Guide This is an unpublished work the copyright in which vests in Siemens plc All rights reserved The information contained herein is the property of Siemens plc and is supplied without liability for errors or omissions No part may be reproduced or used except as authorised by contract or other written permission The copyright and the foregoing restriction on reproduction and use extend to all the media in which this information may be embodied HS16940_V32 doc Issue 30 Page i ASTRID and INGRID User Guide 666 HS 16940 000 ISSUE STATE Note Source of documents is shown under Type as below 1 Paper 2 VAX 3 Microfilm 4 CALTEXT Disc 5 DECmate Disc 6 Paper Insert 7 MAC Disc 8 LIFESPAN 9 SUN 10 Other add note The document comprises the following components Current Pages Issue Type Part ID File ID All 30 10 666 HS 16940 000 HS16940 doc Note 10 document stored under AMW HS16940_V32 doc Issue 30 Page ii ASTRID and INGRID User Guide 666 HS 16940 000 CONTENTS 1 INTRODUGTIOM esse eis Ge sin ie si ei ne ei ne n ei oi 4 1 1 ad GE 1 2 COPE RE EE N EE KEER ELKE HE EE EE EE AE N Ne 1 3 Related doeuments s sesse ESEG SG EG SG GV GN aa aaa an gae NF G Nga Nn aae NN YEN Ge N EN NEN NEN GE Ge EN VEN NEN 1 4 Definitions ee
21. Car Park N01241 N01311 N01321 Cl su 19 24 variable c Er m options View Print Extract Close Help Figure 2 ASTRID Display Site Type Node selected T we lt gt 00 07 End Group n Fr gt 10 16 1 Feb 1998 Cl sa lt gt 16 19 Cnt P type The following site types are available 1 Area 2 Region 3 Node 4 Stage 5 Link 6 Det Detector 7 Route 8 Group car parks 9 Car Park 10 Cnt count HS16940_V32 doc Issue 30 Page 16 ASTRID and INGRID User Guide 666 HS 16940 000 1 1 1 7 asmposay LI Site Type Site Weekdays Times Dates Node NOTITI T Mo X 00 24 Start N01121 1 Feb 1998 N01131 Cl Tu lt gt 07 19 N01211 Flow N01221 Stops N01222 zl Th 07 10 N01231 N01232 Data type T we lt gt 00 07 End Delay E Fr 10 16 41 Feb 1998 Congestion EH Cl sa lt gt 16 19 Sat N01311 Stage Length N01321 Ej su lt gt 19 24 Vehicle Delay FB Options Queue Clear Time View Print Extract Close Help Figure 3 ASTRID Display Data Type for Site type Node selected 4 3 3 Data Type Each site type has a number of associated data types Data types are dependent on site type Site Type Area 1 Total Flow 2 Total Stops 3 Total Delay 4 Congestion 5 SAT 6 Stage Length 7 CP Total Entries 8 CP Total Exits 9 CP Occupancy 10 Vehicle Delay Site Type Region 1 Total Flow 2
22. HS 16940 000 7 4 INGRID UTC Set Up Incidents detected by INGRID are reported to UTC System users by means of event driven messages A CAST should be set up to initialise the messages A suggested set of messages which may be sent to ALLUSERS is given below ESS I01 ESS 118 ESS 102 N ESS I03 N ESS I04 N ESS I07 N ESS I08 N ESS I09 N ESS I10 N ESS I15 N S m EE Xm SEES HS16940 V32 doc Issue 30 Page 54 ASTRID and INGRID User Guide Jo SaturatON esse see ee ee ee ee Pipe s Pp ASTRID Messages iese ee ee ee ASTRID Set p aeos reiner teret ttes ASTRID version BA sesse esse ese ee ee ke Back dei ME RE EN Basic data DES esse ee ee Ke Ge eks Ee eke EG Congestion essere nennen Historic flow parameters ccccceeeeeeeees Saturation esse esse ee ee Re ee eene CO S Congestion index eese cruise Spee Derived data epes loer depron redare opaan ae SEAE Ene Eaa Detector flow nexa Detector OCCUPANCY see ee DIM division Gie EE GE einen Gee ee Ee ed Display Colours eee Display Grid ER HERO N ER Extract Button File Ai RE OE ER EE File Types Bae files eite hee Graph Type ies ritade danae tiders ENE Be BERE ee Bae ER EE ie Graphs dut nte EE UNA Data ER EES Data Units for display HS 16940 V32 doc 33 666 HS 16940 000 LE EE AE ER
23. MESS M29 N gt ASTRID MESS M45 N gt ASTRID MESS K01 C00000 gt ASTRID MESS FOl D00000 gt ASTRID To ensure that the information to the ASTRID database is not accidentally halted it is recommended that these commands are put into a CAST and the CAST run by time table command each morning Once these commands have been entered the system will require a few hours data collection before ASTRID can be used Note that if ASTRID is required to run on a reduced set of the UTC system then the SCNs above should be altered accordingly For example if required for one region only modify the SCNs from N to RxxN etc where xx is the required region identification ASTRID Display Control Window General The ASTRID display control window can be opened in two ways 1 By selecting SCOOT in the UTC Session window followed by SCOOT Specials and then ASTRID Display 2 Entering ASTD in the UTC Command Entry window HS16940 V32 doc Issue 30 Page 14 ASTRID and INGRID User Guide 666 HS 16940 000 SIEMENS UTC Session User SIEMENS Access Level 16 Terminal T01094 SCOOT CarParks ITMC Manager Hew f SCOO Start SCOOT control XSCO Cancel SCOOT control Parameters P File Displays P CASTS gt OVRB X07410 XFLT E00000 Validation P LSTS scoor Specials ASTD ASTRID Display MESS Start SCOOT Message INGRID messages Enter a UTC command XMES Stop SCOOT
24. N IG 36 Full Data Name 36 Use LPU Factor ss set se SEE ee SE Gee Ee GE qwe 36 Y Scale for One or more Site Levels 36 HERMES and SCOPE ROMANSE 6 hic 13 KIWE cesa hele ke ee AAA 13 Historic cycle length ees esse ese ee ee 13 Historic green length sesse esse ese ee ee 13 lle AE EE EE 13 ES eee dtes 13 Holidays iue EE EE SCOPE PH 28 INGRID ii EE Ge E 6 38 INGRID Configuration seen 39 INGRID Data Base esse esse ee 39 INGRID Operation eene 41 licum 9 Journey time eeeeseeeeeeeeeeeeneeee nee nennen 12 SE dc E 9 IR AE EE ME H Q 9 end te ER GEE GE E 9 start TIME sies See SE Gee Gee GE Gee bone eet daceve 9 AGE RE ME EE 9 il en EO EE EE OE EK 8 link length iet t tet 27 L pu EC TE 13 LPU Factors C Ee 26 EE EE OE ON HE 11 13 MOB as iet A Ge irons 11 13 lu 13 MOON IINE e 13 MAS EN 11 13 Messages ei ete iere 7 Collect for These Site Levels 34 Data Name ER GEE cos GE EEN 34 Data Parameter ees esse ee ee ee 34 Data value cuenten err 7 bo e EE EE N EE 7 luto ES 35 End time ee 7 Fault indicator arreire 7 Fault Parameter 34 Fault Parameter Test 34 How Data is Combined 34 Interval Parameter esee 34 Maximum Valid Interval 34 Message Number 34 Mes
25. Operation eee ee Ge eren esee GE ens esee snss sesso ss esos en osse snss see sessesesseseseesssseeees A 7 INGRID VERSION 1 6 sesse sede ds se N Ka ni cuu kk oiu N Lu iu ditioni chau ad iik uv 42 7 1 Introduction 2 ses SE GE N EG N EN GE NO Ee Ge GR N N ee Eee regen ione Se e 7 2 User le Ui de OE EE ED 7 3 INGRID Messages M 44 7 4 INGRID UTC S t Up eene eee enero ooa eere eee e DE Ya eene eene ioa aerea dee nene aep ranae eese e ed oe pasarte A HS16940 V32 doc Issue 30 Page iii ASTRID and INGRID User Guide 666 HS 16940 000 1 1 1 1 2 1 3 1 3 1 1 3 2 1 3 3 1 3 4 1 3 5 1 3 6 1 3 7 1 3 8 1 3 9 1 4 INTRODUCTION Purpose This document describes the user interfaces for ASTRID and INGRID Scope The document covers the configuration and display facilities for both ASTRID and INGRID Related documents Note In the references below the characters xxx substitute for the 3 digit number which uniquely identifies a particular UTC System i e the customer variant for these documents 666 UH 16940 000 Systems Requirement Specification for an STC UTC System 666 UH 16940 xxx Customer Requirements Specification 666 HB 16940 000 Operators Handbook for an STC UTC System 666 HE 16940 000 System Handbook for an STC UTC System 666 HA 16940 000 Hardware Handbook for an STC UTC System 666 HD 16940 000 Data Preparation Handbook for an STC UTC System PR TT 103
26. STRID Display Graph Type selected The graph type pull down window selects the data to be displayed There are up to 8 selections depending on the site type selected This window also controls the HS16940_V32 doc Issue 30 Page 19 ASTRID and INGRID User Guide 666 HS 16940 000 start and end date windows Depending on the graph type selected you may also need to choose settings for one of the following 1 Weekdays 2 Times 3 Start and End times The basic graph types are described in sections 3 2 4 3 2 8 and below 1 Backup This graph type displays historic information at medium resolution 15 minutes 2 Bac Pro This graph type displays historic information at medium resolution and profile information for the same period 3 Bac Bac This graph type displays historic information at medium resolution for two defined dates The two dates are selected in the dates start and end windows 4 Profile This graph type displays profile information The profiles contain data for each weekday The data stored includes a minimum maximum and smoothed average of the values from the backup data for the previous year The profiles are updated every day 5 Max min This graph type displays maximum and minimum figures as well as a mean 6 Stdev This graph type displays standard deviation about a mean 7 Trend This graph type displays trends derived from long term low resolution data The trend data contain hi
27. These data types are collected directly from messages and are stored in the ASTRID database ASTRID is not restricted to recording these data types any information which can be taken from a message can be stored in the database provided ASTRID is configured to do so 3 3 2 Flow The M02 message gives SCOOT flow It is measured in lpu h and differs from actual flow in several respects e Because it is measured in lpu h it should strictly be converted to vehicles with a link dependent and possibly time dependent conversion factor e It is subject to the maximum queue flow which is measured but which is modelled as exceeding the maximum queue is not included HS16940_V32 doc Issue 30 Page 10 ASTRID and INGRID User Guide 666 HS 16940 000 3 3 3 3 3 4 3 3 5 3 3 6 3 3 7 3 3 8 e The modelled flow is retained from a previous cycle if the SCOOT detector is seen as congested This is essential for the correct operation of the SCOOT optimisers in congested conditions but does mean that the flow values obtained do not necessarily reflect the street in the circumstances The FO1 message gives a flow value based on count detector input Stops The M02 message gives SCOOT stops which represent the number of stops on the link as modelled by SCOOT It is measured in lpu h and is output by ASTRID in veh h Delay The M02 message gives SCOOT delay which represents the delay on the link as modelled by SCOOT The value is in Ipus
28. This parameter is not suitable for use by the SCOOT model or optimisers but is used by the INGRID incident detection system and can be used wherever a value for flow is required which is not influenced by the SCOOT model HS16940_V32 doc Issue 30 Page 11 ASTRID and INGRID User Guide 666 HS 16940 000 3 3 9 3 3 10 3 4 3 4 1 3 4 2 3 4 3 3 4 4 3 4 5 Detector occupancy The detector occupancy is a value for the occupancy of a detector calculated by taking the total number of quarter seconds for which the detector is on as a percentage of the whole period Stage length The stage length is the SCOOT stage length as derived from the M17 message This is the length of stage as demanded by SCOOT and does not take account of the occurrence or not on street of demand Dependent stages Derived Data Types Introduction These data types are not stored in the ASTRID database but are derived from data stored there by straightforward calculations The user can access and display these data types in the same way as the basic data types Vehicle delay The vehicle delay or delay per vehicle is obtained by dividing the delay by the flow giving a value in seconds and eliminating the dependence on lpu factors This is SCOOT s estimate of the delay suffered by a vehicle on the link Journey time The journey time is obtained by adding the vehicle delay to the cruise time It gives SCOOT s estimate of the time for an average
29. adow Display Printer Graph background Bottom Shadow Display Printer Ticks lettering Foreground EIER Main title Foreground EIE lid Border Highlight DEEG Printer Graph 1 User defined NEI Graph 2 User defined co PIETER Printer Graph 3 User defined co WEIEN Printer Graph 4 User defined Graph 5 Printer 1 User defined Graph 6 User defined Printer User defined WHIEH Printer Black co HEEN Printer Printer 1 TITER LLL BHEHHHEBBEHHE User defined User defined co DOEN Printer OK Default Cancel EE E BE CETTE PESUE EE EE user defined e ao user defined on SC DETE SE L The Display and Printer Colour buttons allow the colour of the selected area to be changed The display immediately below shows the colour picker available on an Alpha based UTC System whereas the lower one shows that available on a PC SCOOT system HS16940_V32 doc Issue 30 Page 24 ASTRID and INGRID User Guide 666 HS 16940 000 Display Option Picker Mixer Spectrum Lighter Interp Title Scratch Pad Reset Cancel The Display and Printer Colour buttons allow the colour of the selected area to be changed This window allows a large range of colours to be created HS16940_V32 doc Issue 30 Page 25 ASTRID and INGRID User Guide 666 HS 16940 000 gt lt Colour Mixer ixi 195 Red 92 Green 158 p 3 LPU Factor
30. alue is zero then the period is taken from the time of the last message 7 Maximum Valid Interval This is the maximum value allowed for the period If a message has a greater period than the value then the data is discarded 8 How Data is Combined One of the methods is selected from the pull down screen e AVE is used where the SCOOT message data value already has the correct dimensions for storage For example flow in the M02 message has dimensions of vehicles time and the required storage in ASTRID is also in dimensions of vehicles time ACC is used where the SCOOT message data value needs to be divided by dimensions of time for storage For example Det Flow in the M29 message has dimensions of vehicles but the required storage in ASTRID has dimensions of vehicles time so ACC is used to cause the data value to be divided by the period to give dimensions of vehicles time e WAVE is similar to AVE but each point is weighted by the period MAX takes the maximum of the data points rather than the sum MIN takes the minimum of the data points rather than the sum 9 Collect for These Site Levels Specifies which site levels to collect data from Enter a character for each site level The characters to use for each site level are as follows HS16940 V32 doc Issue 30 Page 34 ASTRID and INGRID User Guide 666 HS 16940 000 5 3 e A Area level e R Region level e N Node level e S Stage level e L Link level
31. and can be thought of as the average queue length on the link throughout the period It is stored in ASTRID to a resolution of 0 1 vehicles and is output in vehicles Congestion The M02 message gives raw congestion unprocessed by SCOOT The term congestion in SCOOT is based on the concept of a congested interval this is a period of 4 seconds for which the detector or any one of the detectors on the link is covered The raw congestion is the total length of these congested intervals as a proportion of the length of the period it has not been processed by the SCOOT model It is stored in ASTRID to a resolution of 1 and is output in percent Saturation The MOS message gives the degree of saturation of a link as modelled by SCOOT It is output by ASTRID in percent Historic flow parameters The M45 message produces 4 parameters which are stored by ASTRID and can be fed back into SCOOT They enable SCOOT to produce a default profile when detectors are faulty and can be used instead of the default split and default offset values The four values are Historic cyclic flow Historic green flow Historic cycle length and Historic green length Detector flow The detector flow is a value for flow calculated by counting the number of transitions of the detector state from off to on For detectors covering only one lane it should give an accurate flow count for other detectors it will give an underestimate depending on the amount of masking
32. been flagged as faulty by INGRID The output also shows if adetector has been configured for use by INGRID and ifINGRID has detected an incident at this detector INFE A INGRID Faulty Empty Limit The INGRID Faulty Empty Limit is the time in minutes after which INGRID will flag a detector as faulty when the detector output contains all zeros Values for CHAN are 5 to 100 Default 10 INFF A INGRID Faulty Full Limit The INGRID Faulty Full Limit is the time in minutes after which INGRID will flag a detector as faulty when the detector output is all ones Values for CHAN are 5 to 100 Default 10 INFG A INGRID Faulty Good Limit The INGRID Faulty Good Limit is the time in minutes after which INGRID will clear a detector fault when the detector output is neither all zeros or all ones Values for CHAN are 5 to 100 Default 10 INFR A INGRID Reporting Frequency Normally INGRID will re report an incident every minute whilst it is present This behaviour may be modified with this parameter The INGRID Reporting Frequency is the time in minutes after which INGRID will re report an incident if it is still present 0 has the same meaning as 1 Note If the incident status changes e g the confidence level changes then the incident will always be re reported Values for CHAN are 0 to 99 HS16940 V32 doc Issue 30 Page 43 ASTRID and INGRID User Guide 666 HS 16940 000 7 2 9 7 2 10 7 2 11 7 3 7
33. contain data in the same format the differences are in the dates for which the data is relevant A dayfile contains the latest incomplete day being processed which will normally be the current day The bacfile itself contains the same data but for previous dates usually containing all of the current month Bacfiles are archived at the start of each month the archived bacfiles are more difficult to access but still exist in the database Each record contains the following information 1 Date 2 Weekday 3 Start time 4 End time plus the following for each data type 5 Mean 6 Valid sample size Sc 7 Fault sample size 9 HS 16940 V32 doc Issue 30 Page 9 ASTRID and INGRID User Guide 666 HS 16940 000 3 2 9 Trend files The trend files contain aggregated data for previous days There are 7 different aggregation periods as identified by the start and end times e g 1 00 00 to 24 00 2 00 00 to 07 00 3 07 00 to 10 00 4 10 00 to 16 00 5 16 00 to 19 00 6 19 00 to 24 00 7 07 00 to 19 00 This ensures that the trend files are relatively small These periods cannot be changed 3 2 10 Profiles A site has a profile for each day of the week each record in the profile contains the following information 1 Weekday 2 Start time 3 End time plus the following for each data type 4 Mean 5 Standard deviation stdev 6 Sample size count 3 3 Basic Data Types 3 3 1 Introduction
34. doc Issue 30 Page 8 ASTRID and INGRID User Guide 666 HS 16940 000 3 2 6 3 2 7 3 2 8 Keys A record is referenced with the following keys although not all file types contain all these keys 1 Date the day month and year of the date for which the record contains data Typically the date is represented externally as yyyymmdd so that for example 1 9 9 5 0 1 2 6 represents 26 January 1995 The reason for using this formula is that it allows dates to be sorted conveniently 2 Weekday the day of the week Monday to Sunday Externally the weekdays are represented by the first two letters of their name so that MO represents Monday etc 3 The start time of the data period Times are represented externally as hh mm using the 24 hour clock so that for example half past seven at night is represented as 19 30 4 The end time of the data period This is represented in the same way as the start time The end time of a period can extend to midnight which is then represented as 24 00 Items 1 Data All the data for one site corresponding to that date and time The actual format of the data in the files is not described here as the files are not accessible directly by the user instead data can be retrieved from the database by using the View command and is displayed in the form of a graph Back Files and Day Files These files contain detailed information at the normal aggregation level of 15 minutes They all
35. e D Detector level e T Route level e G Group equivalent to UTC sub area e C Car park e V Count detector 10 Multiplier The data will be multiplied by this figure 11 Divisor The data will be divided by this figure 12 Smoothing Factor 96 The smoothing factor is expressed as a percentage and is used when up dating the profile 13 Rejection Data Name optional This is an optional field If specified the rejection data name must be derived from the same SCOOT message as the data set that is being defined all remaining fields must be filled in 14 Rejection Sample Std Deviation and Smoothing Factor Data is rejected if the Rejection Data has a sample size of at least Rejection sample size and the data is more than Rejection Standard Deviation 100 standard deviation away from the mean If the data is rejected Rejection smoothing factor is used instead of Smoothing Factor Data is smoothed as follows New value smoothing factor 100 old value 100 smoothing factor 100 Graphs This window allows the user to define new data types for display HS16940 V32 doc Issue 30 Page 35 ASTRID and INGRID User Guide EL fine graphdata 0 flow Flow 1 000000 2000 N 4000 AR 20000 veh h LPUFAC stops Stops 1 000000 2000 N 4000 AR 20000 veh h LPUFAC del Delay 0 100000 30 N 60 AR 300 veh LPUFAC cong Congestion 1 000000 100 N 200 AR 1000 dsat Sat 1 000000 100 N 200 AR 1000 rflow Det Flow 4 0000
36. e normally cyclic or at 5 minute resolution and M08 and M29 messages are cyclic Data at their resolution are stored for a few days at most as the storage requirements are very large This resolution of data can be appropriate for analysing incidents or other effects on the network The raw files are stored at this resolution Data are stored at medium resolution for the longer term The time resolution of 15 minutes is a compromise between detail of information and storage requirements The profiles are stored at this resolution Data at low resolution are divided into a few time periods per day covering peak and off peak periods as a whole Because the storage requirements are so much less data can be stored for years at this resolution The trend files are stored at this resolution 3 2 4 File types The files are organised as four separate file types which contain data at different resolutions and for different periods 1 Raw files contain raw data for the last few days only at high resolution 2 Profiles files contain average data per weekday at a medium resolution 3 Trend files contain data per day at low resolution 4 Bac files contain data per day at medium resolution 3 2 5 Records Each file contains records each of which contains the data for one period of time For example a profile file contains records for one site each record in the file would contain one 15 minute period of data for the one site HS16940_V32
37. ector DET Ref values Flow 1 Occ 2 Detector Detail Reference values 1 Flow veh h 2 Occupancy 46 I37 Detector DET Ref up marker Detector Detail Reference up marker none I38 Detector DET Ref down marker Detector Detail Reference down marker none I39 Detector DET Ref flags Up 1 2 Down 34 Result 5 Detector Detail Reference flags 1 Up flow flag 2 Up occupancy flag 3 Down flow flag 4 Down occupancy flag 5 Result I40 Detector DET Period 1 s Flow 2 veh Occ 3 qs Detector Detail Issue 30 Page 51 ASTRID and INGRID User Guide 666 HS 16940 000 Description Parameters 7 3 41 141 Message Format Type Class Description Parameters 7 3 42 142 Message Format Type Class Description Parameters 7 3 43 143 Message Format Type Class Description Parameters 7 3 44 144 Message Format Type Class Description Parameters 7 3 45 145 Message Format Type Class Description Parameters HS16940_V32 doc Raw M29 data 1 Period s 2 Flow veh 3 Occupancy 1 4 s 141 Detector DET Period 1 s Flow 2 veh h Occ 3 Detector Detail Converted M29 data Period s 2 Flow veh h 3 Occupancy 46 142 Detector DET Period 1 Sat flow 2 T2 3 Fault 4 Detector Detail Raw F10 data 1 Period s 2 Saturation flow veh h 3 t2 s 4 Fault code 02OK 143 Detector DET Period 1 Sat flow 2 Detector Detail
38. ed incident refers to a real incident happening on street 6 2 INGRID Data Base Information on the layout of the SCOOT detectors must be entered into the database before INGRID can operate This consists of defining upstream and downstream links for each detector to be monitored To illustrate this the following figure shows a sample SCOOT layout B G H F C E L on A D d Figure 6 Sample SCOOT layout 6 3 INGRID Configuration Information on the layout of detectors around the SCOOT network must be supplied to INGRID such that it can operate correctly In particular for each detector the detectors on the upstream and downstream links must be set up When setting up the detector layout information detectors are grouped into regions These regions may or may not be the same as SCOOT Regions You can choose to group the detectors anyway you wish As a guide a region should contain detectors which are in the same geographical area To function effectively HS16940 V32 doc Issue 30 Page 39 ASTRID and INGRID User Guide 666 HS 16940 000 INGRID requires information on which detectors lie on a downstream from other detectors By making each region as large as possible this increases the number of connections between detectors and makes INGRID more effective The current limitation is that INGRID is limited to 25 regions with up to 50 detectors in each region Initially when INGRID configuration is run and no data has been entered
39. es 17 Vehicle Delai 18 Site type Route io geeignete Ee 18 Site Type Route COng SEOD eie ERREUR 18 Queue at Start of Green 19 SARTRE RIEN RII 18 Total Delay etit tror toten 18 Total e 18 Total StOps T 18 Vehicle Delay EE le een ER EE eg 18 Site Type Stage 18 Stage EE 18 Site WINdOW cece eesceeeseeeseeeeeeeeeeeseseeesteeensaes 21 len oe UDIN GE Ee 13 Speed RE Ee GE DE ee 12 27 ETA EE OE EE HERE 7 Stage ii RE EE EN 12 EE EE RE ET 13 Times Window eese 21 Transport and Road Research Laboratory 6 Trend Ke AE EE ee RE 10 University of Southampton ss 6 Vehicle delay sse 12 Vehicle occupancy sinciera rie 13 View Button EE 29 Ed ee EE unen 15 Issue 30 Page 56 ASTRID and INGRID User Guide 666 HS 16940 000 Weekdays Window 21 HS16940_V32 doc Issue 30 Page 57
40. escription What the parameter is for Values The allowable values for CHAN Default The default value if no CHAN is entered INAL A INGRID Alpha Changing the value of the INGRID Alpha parameter varies the incident detection sensitivity using the current method which looks for significant changes in traffic activity over a short time period Smaller values of the Alpha parameter will make incident detection more likely Values for CHAN are 0 to 10000 Default 200 INBE A INGRID Beta Changing the value of the INGRID Beta parameter varies the incident detection sensitivity using the historic method which looks for significant differences between the current network activity and the typical network activity for this time and day as retrieved from the ASTRID profiles Smaller values of the Beta parameter will make incident detection more likely Values for CHAN are 0 to 10000 HS16940_V32 doc Issue 30 Page 42 ASTRID and INGRID User Guide 666 HS 16940 000 7 2 3 7 24 7 2 5 7 2 6 7 2 1 7 2 8 Default 200 INCO A INGRID Confidence Filter INGRID calculates a confidence value which is based on the length of time for which the incident has been detected Incidents will not be reported unless the calculated confidence value is greater than that of the Confidence filter Values for CHAN are 1 5 Default 0 INDF D INGRID Detector Fault Status The output from a VALU INDF command shows whether a detector has
41. indows and one OK button 1 Display Grid This button displays or removes a grid pattern from the graphs 2 Display Colours This pull down window allows ASTRID colours to be selected HS16940_V32 doc Issue 30 Page 22 ASTRID and INGRID User Guide 666 HS 16940 000 EI seleeAsTRID colours i Surround Background Display Printer Top Shadow Display Pri Graph background Bottom Shadow Display Printer Ticks lettering Foreground om MEIER Printer Main title Foreground Border Dates Start 1 Feb 1338 Highlight co IO O Printer End 1 Feb 1338 Profile Graph 1 User defined MOER Scale Ph 2 User defined DEE Lui variable Graph 3 User defined Co PITTE Printer Graph 4 User defined Graph 5 User defined Printer Graph 6 User defined EI Printer Graph 7 User defined co DISSE Printer Other 1 Black oe DIETER Printer Other 2 User defined Printer Other 3 Printer sums User defined mm DEJEN E Ce D et o D s eo m Help ASTRID Display Options Display Colours selected Each of the 16 major colour areas has a pull down window that allows detailed colour area selection This window allows selection of predefined colours or a facility to create user defined colours HS16940_V32 doc Issue 30 Page 23 ASTRID and INGRID User Guide 666 HS 16940 000 EI SeleetAsTRID colours LJ7 Grid Top Sh
42. iption A general description of the message Parameters The parameters are number from 1 I01 Message Format I01 AREA AREA INGRID 1 functioning 2 Type Area Class User HS16940 V32 doc Issue 30 Page 44 ASTRID and INGRID User Guide 7 3 2 7 3 3 7 3 4 7 3 5 7 3 6 7 3 1 Description Parameters 102 Message Format Type Class Description Parameters 103 Message Format Type Class Description Parameters 104 Message Format Type Class Description Parameters 105 Message Format Type Class Description Parameters 106 Message Format Type Class Description Parameters 107 Message Format Type Class Description Parameters HS16940_V32 doc 666 HS 16940 000 INGRID functioning 1 Version 2 INGRID time and date Detector lt DET gt Incident Detector User Incident none 103 Detector lt DET gt Incident CLEARING Detector User Incident clearing none 104 Detector lt DET gt Incident CLEARED Detector User Incident cleared none 105 Detector DET Confidence 1 2 Cur 3 Ref 4 Detector User Confidence 1 Confidence level 1 to 4 2 Confidence text 3 Current 4 Reference 106 Severity 1 2 Detector User Severity 1 Severity level 1 to 4 2 Severity text I07 Detector DET 1 of a2 Detector User Confidence and severi
43. m 51 Incident N0123181 RST Mildly confident of a moderate incident Duration 05 minutes Affected down N01221B1 Affected up Incident N06311E1 RSP Mildly confident of a moderate incident Duration 05 minutes Affected down NO6314C1 Affected up HS16940_V32 doc Issue 30 Page 41 ASTRID and INGRID User Guide 666 HS 16940 000 7 7 1 7 2 7 2 1 1 2 2 INGRID Version 1 6 Introduction INGRID version 1 5 was developed by TRL as part of the COSMOS project The output of this and later versions of INGRID has been found to be more suitable for use with STC s COMET Systems than earlier ones The output is in the form of event driven messages similar to SCOOT messages see 7 3 A number of CHAN parameters may be used to influence the sensitivity of incident detection and the freguency of message output Incident detection is performed using the current and reference methods previously described see 6 1 The facilities described in the section are only available if the UTC System has been configured accordingly by STC User Parameters The user may use the UTC CHAN command to set the sensitivity and other parameters of INGRID The value of any parameter may be seen at any time by using the VALU command With the exception of the detector status all INGRID commands are area level ones This section lists the available parameters in alphabetical order With each parameter are a number of pieces of information D
44. nslator has been set up Such printers often end in post to help identify them The options button opens the print options screen under normal conditions this screen will not be required HS16940_V32 doc Issue 30 Page 29 ASTRID and INGRID User Guide 666 HS 16940 000 Print Dialog_popup Number of Copies o Page Range From To Cancel Orientation lt gt Default lt gt Portrait lt gt Landscape Options Print Format Printer PostScript R HP890C Help HP890C POST TO1001 TO1004 UCX LPD OUEUE Print After now The above Print Dialog popup shows the print dialogue screen which would be seen on an Alpha based UTC system On a PC SCOOT system a pop up menu will show a list of available printers from which the required one may be selected 4 3 13 Extract Button The extract button allows the data compiled to produce a graph to be exported to another machine The format in which this data is exported can also selected The name of the file to be exported is entered in the section box and the export format selected from the format selection box When the OK button is selected the file is stored under the given name HS16940_V32 doc Issue 30 Page 30 ASTRID and INGRID User Guide 666 HS 16940 000 EI Csenge T Filter Files H DBF HELLO DBF NO1111A DEF NETSERVER LOG UCX FTPSERVER LOG Astrid txt Lotus 123 123 dBase Ill dbf dBase IV dbf Selection
45. pes 1 An area represents a whole cell Because data can be collected for more than one cell there may be more than one area 2 A region is a SCOOT region or an equivalent for a non SCOOT data source 3 Anode is a SCOOT node or an equivalent for a non SCOOT data source 4 A stage is a SCOOT stage or an equivalent for a non SCOOT data source HS16940_V32 doc Issue 30 Page 7 ASTRID and INGRID User Guide 666 HS 16940 000 5 A link is a SCOOT link or an equivalent for a non SCOOT data source 6 A detector is a SCOOT detector or an equivalent for a non SCOOT data source 7 A route is a set of links which has been defined to ASTRID by the user A route may consist of links representing a particular route through the network or it may be a set of disconnected links which the user wishes to consider together 8 A group is sub area or equivalent group of equipment 9 Acar park is a single car park It may have a number of in and out counts 10 A ent is a count taken directly from a count source not derived by the use of conversion factors 3 2 3 Resolution The time resolution of data except the trend periods can be configured as part of the initial installation of ASTRID The values given here are typical values Data are stored at one of three types of resolution 1 2 3 Data entering ASTRID are at high resolution The exact resolution depends on the message being processed but M02 messages ar
46. r Guide 666 HS 16940 000 5 Routes This screen allows routes to be constructed from a list of links EI Route Configuration LJ Routes Links in this route Available links bee n ele nk in remove from route add to route 01ROUTE2 01ROUTE3 NOS5111C NO4131E OTROUTE4 NO5131A NO4131G OTROUTES NO5121C NO4131H OTROUTEG N05911B NO41311 01ROUTE NO4131Z 01ROUTES NO4141A 01ROUTES NO4141B 01ROUTE10 N04141C N04141E NO4141F NO4 44C NO4 44D N10124E 6 Holidays This screen enables dates to be entered Information gathered on these dates will not be used in producing the profiles HS16940_V32 doc Issue 30 Page 28 ASTRID and INGRID User Guide 666 HS 16940 000 meiayssene Holidays currently defined 4 3 11 4 3 12 01 Jan 1995 02 Jan 1995 14 Apr 1995 17 Apr 1995 08 May 1995 29 May 1995 28 Aug 1995 25 Dec 1995 Enter the date for a holiday to add or select a date from the list to remove LY OK Cancel Add Remove L 7 Messages See Advanced Graphics section 5 8 Graphs See Advanced Graphics section 5 View Button This button displays the selected graph Print Button This button opens the Print Dialog popup screen This screen allows the number of copies print format and the printer to be selected All configured system printers should be shown You should select a printer that either supports Postscript directly or a printer for which a Postscript tra
47. rivers Although such systems work well in normal traffic flow as a network becomes congested the ability to minimise delays is reduced To improve this situation two systems have been developed ASTRID and INGRID ASTRID is a database that monitors a traffic network and provides detailed information to a network operator about historic traffic conditions The INGRID system has been developed to detect traffic incidents using information from adaptive urban traffic control systems such as SCOOT Once an incident has been detected information on the location and severity of the incident can be passed to the traffic operator In the future information on an incident could lead to automatic remedial action being carried out by the traffic control system INGRID uses two types of algorithm to detect traffic incidents One examines current traffic data for sudden changes in detector flow and detector occupancy NO reference data is required for this algorithm To detect an incident information from connected detectors must satisfy the following conditions Detector upstream of incident i e has a queue over it occupancy greater than smoothed value calculated over recent minutes e flow less than smoothed value calculated over recent minutes Detector downstream of incident i e traffic flow less as cannot pass incident occupancy less than smoothed value calculated over recent minutes e flow less than smoothed value calculated over recent minute
48. s The second type of algorithm uses ASTRID to provide historical reference data This reference data is compared with current data obtained from SCOOT This algorithm also requires data from connected detectors For an incident to be detected the following conditions must be satisfied Detector upstream of incident i e has a queue over it occupancy greater than historical average e flow less than historical average Detector downstream of incident i e traffic flow less as cannot pass incident occupancy greater than historical average HS16940 V32 doc Issue 30 Page 38 ASTRID and INGRID User Guide 666 HS 16940 000 e flow less than historical average Both algorithms minimise the possibility that normal fluctuations in traffic flow could cause false detection of an incident by ensuring that each item e g detector flow is a considerable distance from the average before an incident is indicated By varying this distance the sensitivity of each algorithm can be altered The best results are obtained when traffic information is available for each traffic signal cycle Once an incident is detected it is important to determine whether the incident will have any effect on the surrounding network As the number of detectors affected b the incident increases and the duration of the incident rises the greater the severity of the incident A similar calculation is made to determine the confidence that the INGRID system has that the detect
49. sage type eese 7 Multiplier 2i eee here EE be EE Ee Ge AE 35 Rejection Data Name optional 35 Rejection Sample sees 35 SI T R 7 Smoothing Factor seen 35 Smoothing Factor Op 35 Issue 30 Page 55 ASTRID and INGRID User Guide Start me 7 Std Deviation trei eite eerte en 35 node PEE nennen ener enne rennen 7 on line helps EE ER nee he Hen 32 Open AE ete toes eres ete EE dee 6 Options i EE OR OE es 22 Et Eeer EE IEEE 6 Print B tton eee tt eet Ve Ee Ke 29 Le sees ses es ee ee Ge enne enne 10 de GEE EE OE 8 Iu CO RE 7 Resolution tct eet etae 8 high resolution eene 8 low resolution intet 8 medium resolution RA 8 iv i E E RE E R E 13 TOCC is css ees boss sags e RE EE says orgs SR gees OGE Ge HH 13 SS E ES 8 YE MEE AE 28 scale YDE EES EE eg mens 21 Fixed EE eoe ten 21 Specified uus EER 21 Variable 21 Qi 7 Site n 15 nw I 16 Car Park 16 Crt count eee SEE DE GE Ee ideis 16 Det Detector ee 16 Group car Dark 16 bu c 16 Node inen ih eee ree ede IN 16 lo cepai CDa Ere aeanoea EERE 16 RR RE EE EE M 16 MEER OE ER 16 Site Type Areas uc ESE DR EG EE EG EG LEE 17 CCOBIPESLIOD iioc EE EE EE 17 CP Occupancy Ee deett eerie e Eed 17 CP Total Entries sesse sesse ee ee ee 17 CP Total Exits eines 17 Queue at Start of Green 17
50. storic data but is stored over longer intervals 8 Trend This graph type is the same as Trend above but allows single days to be displayed HS16940 V32 doc Issue 30 Page 20 ASTRID and INGRID User Guide 666 HS 16940 000 4 3 5 4 3 6 4 3 7 4 3 8 strip isplay LI Site Type Site Weekdays Dates Node NOTIT E Mo Start N01121 1 Feb 1998 NO1131 T Tu N01211 Flow N01221 N01222 B Th Graph type N01231 N01232 Fr N01241 B Sa m N01311 i ype Fixed N01321 Osu Variable Options Specified view Extract Close Help Figure 5 ASTRID Display Scale Type selected Data type We End 1 Feb 1998 Profile SE Scale Type There are three scale types The Y axis is varied in each case 1 Fixed The Y axis is set by the value selected in the graphs window of the options pull down window 2 Variable The Y axis is selected by ASTRID to best fit the graph 3 Specified The Y axis value can be entered with this selection Site Window The site window displays sites for which data is available The sites displayed are dictated by the Site Type window To select a site scroll until the required site is visible and then select A single click will select the site a double click will select and view the site When selected a site will change to reverse video Weekdays Window This window selects the days to be displayed Any combination between 1 and 7 can be selected
51. system must have SCOOT ASTRID and INGRID installed for it to operate INGRID is covered in section 6 HS16940_V32 doc Issue 30 Page 6 ASTRID and INGRID User Guide 666 HS 16940 000 3 3 1 3 1 2 3 2 3 4 1 3 2 2 ASTRID DATA BASE Sources of Data Cells ASTRID is designed primarily to receive data from SCOOT traffic control systems but data can also be received from other sources Each source of data is referred to as a cell which often refers to a specific SCOOT computer but can equally well mean an independent source of data A cell is given a name consisting of 2 digits Messages Each cell supplies a stream of messages that contain the data required to be stored in the database The messages for ASTRID are in an amended format from the standard SCOOT messages but contain the same information The following information is required for each message to be processed by ASTRID 1 Date 2 Start time 3 End time 4 Message type 5 Site 6 Data value 7 Fault indicator A message can contain more than one data value Database Organisation Configuration The parameters which specify to ASTRID what data types to collect by default and at what resolution are set up by STC during the installation of ASTRID Configuration of other data types is described in section 4 Site The ASTRID database is organised by site which means the location for which the data is collected Sites are one of several ty
52. tion flow veh h Issue 30 Page 46 ASTRID and INGRID User Guide 666 HS 16940 000 7 3 14 114 Message Format Type Class Description Parameters 7 3 15 115 Message Format Type Class Description Parameters 7 3 16 116 Message Format Type Class Description Parameters 7 3 17 I17 Message Format Type Class Description Parameters 7 3 18 I18 Message Format Type Class Description Parameters 7 3 19 I19 Message Format HS16940_V32 doc 114 Detector DET Sat time Cur 1 Sm2 Dp3 Ref 4 Detector User Saturation time 1 Current saturation time s 2 Smoothed saturation time s 3 Dispersed saturation time s 4 Reference saturation time s 115 Detector DET Detector User Separator none 116 Region REG Cur 1 Repeated Region User Current flags 1 Flag for one detector no flag M current up flag N current down flag 2 repeated 117 Region REG Ref 1 Repeated Region User Reference flags 1 Flag for one detector no flag reference up flag gt reference down flag 2 repeated I18 Area Area Startup INGRID Area Logging Startup INGRID none I19 Area Area Keep alive INGRID Issue 30 Page 47 ASTRID and INGRID User Guide 7 3 20 7 3 21 7 3 22 7 3 23 7 3 24 Type Class Description Parameters I20 Message Format Type Class Description Parameters I21
53. ty 1 Confidence text Issue 30 Page 45 ASTRID and INGRID User Guide 7 3 8 7 3 9 7 3 10 7 3 11 7 3 12 7 3 13 108 Message Format Type Class Description Parameters 109 Message Format Type Class Description Parameters I10 Message Format Type Class Description Parameters I11 Message Format Type Class Description Parameters I12 Message Format Type Class Description Parameters I13 Message Format Type Class Description Parameters HS16940_V32 doc 666 HS 16940 000 2 Severity text 108 Detector DET Duration 1 minutes Detector User Duration 1 Duration of incident min 109 Detector DET Affected up 1 repeated Detector User List of affected up detectors 1 An affected up detector 2 repeated 110 Detector DET Affected down 1 repeated Detector User List of affected down detectors 1 An affected down detector 2 repeated I11 Detector DET Affected Up 1 Down 2 Detector User Number of affected up and down detectors 1 Number of affected up detectors 2 Number of affected down detectors 112 Detector DET Near 1 Detector User Location of incident 1 Description of location I13 Detector DET Sat flow Cur 1 Sm2 Dp3 Ref4 Detector User Saturation flow Current saturation flow veh h 2 Smoothed saturation flow veh h 3 Dispersed saturation flow veh h 4 Reference satura
54. ure is involved and time consuming STC have incorporated into their ASTRID interface a more user friendly method of configuring new data types This interface also allows users to customise the standard interface and displays The following screens are intended for use by more experienced operators 5 2 Messages This screen allows the user to define new data categories to be extracted from SCOOT style messages The screen can be found in the options pull down screen messages button Note for all new messages for storage a suitable graph must also be generated to allow for display Define data sets to extract from SCOOT messages Bl stops M02 6 11 20 5 0 AVE ARNTL 1 1 20 flow 5 200 10 Data name del M02 7 11 0 5 0 AVE ARNTL 1 1 20 flow 5 200 10 flow M02 8 11 gt 0 5 0 AVE ARNTL 1 1 20 flow 5 200 10 Message Number cong M02 9 11 gt 0 5 0 AVE ARNTL 1 9 20 flow 5 200 10 dsat M08 5 5 0 0 300 WAVE ARNTL 1 1 20 xsat M08 5 5 0 0 300 MAX ARNTL 1 1 20 nsat M08 5 5 0 0 300 MIN ARNTL 1 1 20 slen M17 5 0 none 0 300 AVE ARNS 1 1 20 Fault test rflow M29 6 0 none 5 0 ACC D 900 1 20 rocc M29 7 0 none 5 0 ACC D 250 1 20 rocc 1 980 0 cpin K01 5 10 lt gt 0 0 300 AVE AGC 12 1 20 cpout KO1 6 10 0 0 300 AVE AGC 12 1 20 cpocc KO1 7 10 lt gt 0 0 300 AVE AGC 1 1 20 hflwc M45 5 5 0 0 300 ACC L 3600 17 20 Accumulation method hlenc M45 6 6 0 0 300 AVEL 1 1 20 hflwg M45 7 8 0 0 300 ACCL 3600 17 20 hleng M45 8 8 0 0 300 AVEL 1
55. vehicle to travel the link The cruise time can be entered in the ASTRID database as part of the installation process but is not automatically updated from the SCOOT value Speed This is derived from the link length the cruise time and the vehicle delay as follows s 3 6 D where 5 is the speed km h l is the link length m t is the cruise time on the link s d is the vehicle delay on the link s Congestion index This is derived from the vehicle delay and the link cruise time as follows HS16940_V32 doc Issue 30 Page 12 ASTRID and INGRID User Guide 666 HS 16940 000 t d c t where C is the congestion index t is the cruise time on the link s d is the vehicle delay on the link s The congestion index is a dimensionless measure of the delay on the link such that no delay gives a congestion index of 1 if the delay is equal to the cruise time the congestion index is 2 and so on with higher values of congestion index indicating greater levels of delay In SCOOT terminology it is a measure of delay rather than congestion but the term congestion index is used in a wider context 3 4 6 Vehicle occupancy This is derived by dividing the detector occupancy by the detector flow to give the average occupancy of a vehicle It is output in milliseconds per vehicle ms veh 3 4 7 Lpu factor An estimate of the Ipu factor is derived from the vehicle occupancy It is output in Ipus per vehicle Ipu veh
56. w the detectors entered for this region To add a detector to this list locate the detector in the list of available detectors on the right select it and click the left pointing arrow button alongside the incident detector list To remove a detector from the list select the detector in the incident list and click the right pointing arrow button For each detector in the incident detector list you can define up to three upstream and three downstream detectors Select the detector you want to add upstream and downstream detectors to The upstream and downstream detector lists will now show the existing configuration To add an upstream or downstream detector locate the detector in the list of available detectors and click the right pointing arrow alongside the list to add To remove a detector select the detector from the upstream or downstream list and click the left pointing arrow Once you have finished making changes click OK to save the changes and exit In order for INGRID to use the new data it must be restarted A dialog will be displayed asking if you want to do this If you click no INGRID will only start to use the new configuration when the system is next restarted Click Cancel to quit without saving changes INGRID Operation For INGRID to detect incidents INGRID Messages must be selected from the SCOOT Specials menu The following figure shows a sample screen displaying two incidents detected by INGRID INGRID Messages B
Download Pdf Manuals
Related Search