My WebLink
|
Help
|
About
|
Sign Out
Home
Reso 1997-136 to 140
CityHall
>
City Clerk
>
City Council
>
Resolutions
>
1997
>
Reso 1997-136 to 140
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/14/2022 5:17:51 PM
Creation date
7/14/2022 5:12:22 PM
Metadata
Fields
Template:
CM City Clerk-City Council
CM City Clerk-City Council - Document Type
Resolution
Document Date (6)
12/31/1997
Retention
PERM
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
60
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Mr. Steve Fitzsimons Page 4 November 5, 1996 <br />specific time periods and locations). The name we propose for this module is <br />"Traffic Database," which supersedes "COUNTS." <br />Traffic Database is the common link between different signal systems; in this <br />project, Traffic Database is the common link between Type 170, Econolite and <br />Traconex systems. The input data translation need is only between CT Net and <br />Traffic Database, Econolite Zone Master IV and Traffic Database, and <br />TraconeVMAQS and Traffic Database. Output translation need is from the signal <br />settings editor and each of these systems. It is this commonality of Traffic <br />Database that will allow TIS to access three different systems from one computer, <br />at least for input and analysis and monitoring. Control, however, will always reside <br />in the signal system software, not TIS. This means that the signal settings editor of <br />TIS will translate TIS edited output to CT Net, Econolite Zone Master IV/I'MS, or <br />Traconet. It is then the function of CT Net, Econolite Zone Master IV/I'MS or <br />Traconet to download the edited signal settings to the field masters and intersection <br />controllers. <br />2. Modelling and Timing Plan Generation Module: <br />The data generated in the Data Acquisition and Compiling Module are then <br />translated into input for Synchro (which can then be directly linked to produce <br />TRANSYT 7F and PASSER 2 input data). Also, in this module are databases with <br />files of stored system configuration information as well as editors for development <br />of new system configurations as other systems are added to the central system <br />monitor. There is a difference between developing a standard system input file for <br />TRANSYT 7F and this module. This module also provides for a means of defining <br />a new system in terms of which loops are related to specific movements at an <br />intersection and links in a TRANSYT 7F model (and also, as seen in Figure 1, is an <br />input to the data extraction and compiling program in Traffic Database). <br />The translation program takes the Traffic Database information and assigns it to the <br />input fields in the Synchro software. Once Synchro input data are complete, the <br />model can be nun for timing analysis, and when desired, new timing plan <br />generation. Timing plan generation takes the "controller settings" output from <br />TRANSYT 7F or "Pin Settings" from PASSER and converts those outputs into the <br />specific format needed by the signal system software. This output is then capable <br />of being directly downloaded via the central signal system software, or first, <br />manually edited and checked prior to downloading. <br />
The URL can be used to link to this page
Your browser does not support the video tag.