Well, welcome and thank you for standing by.
At this time all participants are in a listen only mode.
During the question and answer session please press star 1 on your touch tone phone to ask a question.
Now I'd like to turn the meeting over to Ms. Jennifer Symoun.
Thank you, hello, everybody and welcome to the talking Operations web conference.
I'm going to be giving you a brief introduction to the web conferencing environment before turning the session over to Eddie Curtis who we're very pleased to have as our moderator today for talking Operations seminar.
Please be advised today's seminar is being recorded.
Today's seminar will last approximately an hour had and 45 minutes with 70 minutes allocated for the presenters and final 30 minutes for audience question and answer.
During the presentation if you think of a question you can type it moo the smaller text box underneath in the chat area , on the left side of your screen.
Please indicate who your question is directed towards, unless your question is intended for all presenters and please make sure you're typing in the thin text box and not the large white area.
Please also make sure you send your question to everybody.
Presenters will not be able to answer your questions during their presentations but Eddie will use the questions typed moo the chat box for the question and answer session in the last 30 minutes of the seminar.
A file containing the audio and visual portion of the seminar will be posted to the national transportation Operations coalitions website within the next week.
I will type that address ma the chat box shortly.
We encourage you to direct others in your office who may have not been able to attend the seminar to access the recording.
The PowerPoint presentations used during the seminar will also be available on the website.
However, you can can also download the presentations right now from the box in the lower left corner of your screen and there are instructions above that on how to download the presentations and you can save them directly to your computer.
I'd now like to introduce Eddie Curtis, the moderator of Today's Webcast.
Eddie is the Manager of the arterial Management and traffic signaling timing program within the federal highway administration Office of Operations
and is also a member of the federal highway administration Resource center Operations technical service team.
He is the pray merry contact for the deployment within the federal highway administration and has conducted several workshops throughout the nation to promote adaptive control technology and specifically ACSLight.
He served as project Manager for the 2007 traffic signal report card and is managing the development of the signal timing manual due out in May and several research
projects focused on improving traffic signal Operations.
He joins federal highway administration in February of 2006 and previously worked for the City of Los Angeles and traffic Operations and research.
He is a registered professional engineer in California and Louisiana.
So now, I'll turn things over to Eddie to start off Today's seminar.
Eddie, I'll bring up your presentation and you can begin when you're ready.
Okay, thank you, Jennifer.
I'd like to welcome everybody to the ACS Light Webcast today.
We have three great speakers lined up that I think are going to give you some very comprehensive information about ACS Light, and I encourage you to type questions into the chat box, should you have any and certainly,
take our contact information down and definitely give us any questions additional information you'd like to obtain about ACS Light.
I'm going to start off today and introduce all three of the speakers, and as Jennifer said I am the first speaker actually.
And I'll go through their bios and then move into my presentation which will pretty much give you on overview of traffic signal Operations and how adaptive systems fit into traditional Operations, per se.
And then we'll have Dr. Shelby go into development and the functionality of ACS Light, and Kirk Houserer will kind of sum everything up and give an overview of his experience with ACS Light.
Tyler, Texas was the first agency to fall on the sword I guess and decide to deploy ACS Light which is up until recently was really just a research project, so we're really happy that Tyler, Texas was able to take that leap
and get us going.
Okay, so let's look on our, I'll go over the biographies of our two other speakers.
After me will be Dr. Steve Shelby.
Dr. Shelby is a research project Managers with Siemens working out of Tucson, Arizona.
He's a leading expert in the design and development of adaptive traffic signal control systems.
He is essentially a designer and sole software development for ACS Light.
In the prior days of the University of Arizona he helped develop the road of adaptive system which is funded by the federal highway administration
and he's also worked on a lot of other projects including transit priority systems in Salt Lake City in Houston and developing communication software for advanced traffic Management systems, deployed nationwide
and he's also doing research on surrogate measures for intersection safety.
Kirk Houserer, our third speaker is a graduate of Texas A & M University and he has 20 years of experience in public works 10 of which has been spent in traffic and transportation.
He is the city traffic engineer for the City of Tyler, Texas and he's current Board member for the Texas chapter of ITE.
Mr. Houseer is married with two kids, his son is studying electrical engineering at Rice University and his daughter was just accepted into the Texas Academy of Math and Science.
Sounds like she's a a future engineer.
Okay I'm going to start off my presentation and when you start talking about improving the technology of traffic signal systems, I think you first have to ask a couple of questions.
What are the objectives and the purpose of traffic signals?
If you're going to improve the technology, how will you help these signals achieve their purpose? And I think the purpose of traffic signals can be polarized into these four statements
and these actually came out of a document that was put together by the federal highway administration Office of safety, and these are pretty consistent of w what you'll see in the MUTCD in terms of warrants.
I think of particular interest to me is the last one, and that's to maximize the capacity of each intersection approach and then probably the second one too, minimizing vehicles and pedestrians,
I think these are two purposes that adaptive systems can help achieve, and since we ask that question, what's the purpose of traffic signals and what are the objectives, you have to consider how are we achieving these objectives today.
If we were to use the traffic signal report card as a barometer for that we probably would conclude that we're not doing that great with an overall score of a " D" in 2007 which is up slightly from a D- in thousand 5.
In the realm of adaptive systems, I would say that we probably could help improve two areas of the signal report card and I would say that those would be the Management of our signal systems overall
and because when you deploy an adaptive system, you basically have to move or you're committing to move from a reactive posture to more of a pro active posture, and then what goes along with that is the section on traffic monitoring
and data collection, which was Section 5, and by deploying an adaptive system or an advanced signal system of almost any type, it gives you the ability to collect a higher resolution of data and to monitor and interact with the system.
So, in all of these areas, Management, we certainly had a D-and in traffic monitoring and data collection, overall, respondents to the survey scored themselves an F,
so these are definitely two areas where we can apply some effort to make improvements.
When you ask the question, well what agencies are having the greatest difficulty? Who is producing the scores that we're seeing? And primarily, we found that agencies that have 50
or fewer traffic signals tend to struggle the most in terms of operating and maintaining their traffic signal systems.
And in respect with ACS Light, the system designed and we found that there's some 20,000 close up systems deployed throughout the United States, and a large portion of those systems are deployed in municipalities that have 50
or fewer traffic signals so it's an optimal technology for a small agency but you can see that the scores actually the group that did the best was the agencies with 450-1,000 signals
and we saw that's a combination of having the right balance of resources in terms of your engineering expertise in house and the size of the system.
The systems tend not to be too large, when you get into that range.
The next question you are going to ask yourself is how is your signal system performing? Can you justify the need to improve your signal system?
And when we start talking about performance you have to consider that there is really no standard of performance for traffic signals.
Traffic signals operate in a variety of different ways.
We've got everything from electrical mechanical signals that are still out and not only are they operating, a lot of them are still being maintained and on the same token, you've got very advanced systems like,
we'll say adaptive systems for instance.
You've got Scats, scoot, and a high level of performance in some of these systems so how do you have that dichotomy of performance throughout the nation? So how do you compare r those?
Frequently, we see that agencies are using the phone comment to gauge how their systems performing and typically, we'll see before and after studies, before and after we do signal retimings
and then the other question in terms of performance is how do you report information about performance if you don't really have the ability to collect that data?
What could you do with performance information if you had it readily available to you? I think one of the things you could do is certainly you could report that information to identify needs for improvement.
If you could show that your objective was to perform at level A, and you're currently performing at level C, then you've identified a gap that immediates to be filled
and you could somehow justify the types of improvements that would be necessary to go from level C to level A, and then you could also compare different facilities.
It's difficult to compare different facilities without performance information so how do you compare a facility in say downtown Atlanta to one in suburban Georgia somewhere?
And I'm hinging on the performance measures for a lot of reasons.
One of the big ones is that traffic signals have to compete for resources with virtually every other type of capital improvement project whether it's filling potholes, building
and repairing bridges which is probably growing in necessity right now, and resurfacing projects, and virtually every other type whether it's water, conservation, or whatever it may be,
all of these typically have to compete in a public works setting for funding, so how do you compete for effectively to obtain funds for traffic signal Operations?
One area that I think we haven't looked at the too closely and we probably should look at more closely is safety.
For some reason, safety and certainly in the federal highway administration, our Office of Safety, my perception is that they're much well better funded than the Office of Operations,
and one of the reasons is you can always justify things based on safety, and in 2002 that's when this data came from, we saw that there were roughly close to or just over 1.
2 million crashes at signaled intersections with over 460 of those resulting in either injury or fatality, so if we can somehow connect traffic signal Operations with safety,
then that opens up another avenue of funding that we can use to deploy traffic signal systems, or improve their Operations, and there's certainly a connection between Operations and safety.
In fact many of the measures that are implemented to improve safety also compliment operational measures that can also reduce congestion.
There are a couple of documents that I'll show you in just a second but what they've done is identified signal timing measures that reduce crashes,
and these are also quite closely related to some of the things that adaptive systems help to improve.
We have studies that have shown that by providing progression, you can can actually reduce the number of rear end crashes, side swipes, and in some cases, even right angle crashes, and to improve progression,
we're talking usually about providing interconnect, time base coordination , if you don't have communications between them and in a lot of cases we see centrally managed systems
and systems that are really trying to improve the optimization of offsets.
That's something that adaptive systems and certainly ACS Light will do.
Also we're talking about optimization of signal timing, optimizing our phases and then there's also things like modifying clearance intervals and providing green extensions ,
and these are pretty much say that you need to have detection at your intersection, and once you have the detection and you've got the interconnect and you want the ability to do some optimization, that's where adaptive systems come in.
There were two issue briefs that were issued late last year.
I think around November, by the Office of Safety and both of these are available, if you send me an e-mail or you were to go to our safety website, you'd see these two issue briefs that you could download
and they go over the potential counter measures to reduce crashes at intersections and it shows you pretty clearly what those signal timing counter measures are.
But why it's important and why am I bringing up safety?
I think it's because most of the people in the traffic signal Operations assume it, we've been singing the same song for a long time.
These are pieces from the ITE journal and they go back moo 1975 and basically you see that we're talking about reducing fuel consumption and reducing delays and for some reason,
this just hasn't got the engine started in a lot of our stakeholders that can provide the funding to improve a lot of signal systems,
so I think we need to find now ways new story toss tell to justify how we obtain funding for signal systems.
Traffic signal control logic really hasn't changed much in the last probably 50 years, and that kind of goes in line with what I'm saying about funding.
I consider traffic signal control evolution to really follow two tracks.
First track I would say is really what's happening at the local intersection level and that's the domain of our vendor s, the guys that make the signal Controllers, the interconnect, all that business,
and then the other track I would say has been mostly the public sector track, and this was where you've got public agencies like the Fed call Highway Administration
and your University transportation centers that are developing ways to improve traffic signals, and for a long time, the private vendors that make the Controllers and the public sector really haven't had much of a connection.
I think with the kind of ACS Light coming on the scene it's probably the first time we've really had a real relationship between the public sector and our vendors to agree on a technology to improve traffic signal Operations,
and I'll go through some of the motivation for that in a few minutes.
Let's talk about the benefits of adaptive signal timing.
We found that adaptive signal timing, a variety of studies, that adaptive signal timing is more responsive to traffic conditions, improvements to reduce delays and we've certainly seen a reduction in the offset of saturated conditions.
And a lot of cases reduces or eliminates the need to retime traffic signals, and we've estimated that the cost to retime a signal system is about 1800-$3500 per intersection, there abouts,
and we've seen improvements over time in day plans and I'll go into that in a second and certainly they give you the ability to do some data collection, archiving, and give you an avenue to measure some of your performance.
Now let's talk about our signal timing design.
Signal timing is typically designed for three peak periods.
Most agencies that I've visited, I usually see no less than three signal timing plans, a.m., midday, p.m., and a lot of times your midday plan is what's used for the off peak.
What I'm showing here is if you follow that kind of the white line, it would show the capacity that's introduced by each signal plan, so this would be your a.m. plan, over here would be your midday and then this would be your p.m. plan.
And what happens is these plans are designed based on current conditions, which would be represented by the light black line, and then as traffic conditions change,
that's represented by the dark black line so you you could can see here that we've basically designed our timing for our 15 minute peaks, for our a.m., midday, and p.m. time periods,
and then whether it would be six months from the time this design was donor whether it's three years or six years, whatever the case may be,
those traffic patterns have changed significantly enough to where we're not meeting the capacity demands of that intersection, and what happens is you get delay, you get standing cues, you get over saturation,
and what do adaptive systems provide you? How can they help you solve this problem?
Well adaptive systems would actually compensate for this change in demand by adjusting your split to offset and cycle length if necessary,
and then another thing about our signal timing plan is we build delay into our plans in a lot of cases.
We could see in this plan, this a.m. plan is coming in at about 5:00 in the morning, and our traffic really doesn't get heavy until about 6:30-7:00, so realistically, we didn't have to implement this plan until probably 6:30.
So we've actually built some delay into this a.m. plan and it actually happens in the p.m. too, by when we implement these timing plans.
And that's another avenue that adaptive introduces in how to reduce the delays in signal timing plans.
Our signal timing plans are typically designed using this process.
There's a trigger event.
We go out and identify intersections, we collect our before data, surveys, get our turning movement counts, design our timing, and then we go out and begin to evaluate it.
Well how efficient is that process? Well here is a little calculation that I did, and when you collect 15 minute,
or utilizing your peak 15 minute data always throughout everything else except for my peak 15 minute data when I designed a timing plan and I'd do that, say I'm going to design four plans and do that for the a.m., midday, p.m.
and off peak so those plans run for three hours a peak, it's 15 hours per day, five days a week, I'm not going to do anything for the weekend and you either run 52 weeks a year and if we go with best practice,
that means we're going to re time every three years.
So roughly, these four timing plans will run for a total of 11, 720 hours, and when you consider the data that you've collected, to design those plans you've actually got a representative sample of about .
0085% of the number of hours that that plan will actually run.
So, kind of going back to the previous slide on how we design timing, we can see why we have so many periods of inefficiency in a timing plan.
So how does adaptive small timing do anything to help that? Well a typical timing plan is implemented and we see about a 25% improvement in the delay and travel time for that intersection,
and what happens is the traffic patterns change over a period of say two to five years and that timing plan becomes less effective.
With an adaptive system what you're doing is you're able to compensate for those changes in demand, so you're able to prolong the effectiveness of signal timing.
I've heard a lot of people say that adaptive systems improve signal timing over time of day and I would probably say that's not very accurate
or I'd tend to say they prolong the effectiveness because you probably should come up with the same timing solution at the time you implement a timing plan is what an adaptive system would come up with, so if you do a retiming today,
and implement an adaptive system within that probably first six months, you probably would see no improvement, but over the long term, say five years, you should see no reduction in the effectiveness of that timing plan.
So where have adaptive systems been deployed? Over the last Oh, about 20-25 years we've seen about 25 systems pop-up throughout the country.
The largest market share of adaptive systems is held by SCATS right now and that was an adaptive system developed in Sidney, Australia.
The second most common system would be SCOOT, and now actually with ACS Light coming on, we're probably, we have more deployment than any of the other systems.
In terms of the number of intersections, there are about 272000 traffic signals estimated throughout the United States, and only less than 1% of that or about 2005 signals are able to
or installed with any type of adaptive technology so that's less than 1% of all of the traffic signals in the United States have any adaptive ability.
So the question is, why is that? If the benefits are so compelling and we're going to get all of these great gains in terms of travel time and prolonging the effect of the signal timing, why aren't there more systems?
Well the primary reason for that is that these systems, some of them cost incredible amounts of money to deploy, and not only do they Costa Lt. To get on the ground, there's extensive calibration and monitoring that's required,
the detectors are crucial in a system so if you don't have a good system to maintain traffic detectors, you're not going to get good performance out of an adaptive system and then there's significant communications overhead.
A lot of cases you need more technical staffing because the systems have traffic models that run in the background and you need people that are familiar with those, and almost every adaptive system should have a disclaimer that says,
" Will not operate in over saturated conditions".
So what happens when you deploy an adaptive system?
In a typical system, I think these are four variables, cost performance, proactive Management and data, what type of data is the system providing you and a typical system,
you get pretty small performance because you don't really monitor a lot and then our proactive Management requirement is pretty low because we're just going to retime and follow best practice and retime every three to five years
and as a result of that, I don't require a lot of data.
The system is not providing a lot so I don't collect much.
With an adaptive system, you're cost for deployment and Operations will certainly go up, but you also see an improvement in your performance
and you're going to be required to do a certain level of proactive managing because now your communications and detection systems become critical.
But you're also responding to traffic conditions as they change which gives you a greater level of performance which you can report.
So what were the goals for ACS Light? Well primarily we wanted to lower the cost of getting into the adaptive market
and that meant that you needed to be able to utilize a lot of the existing infrastructure because that's where a lot of the costs are in deploying some of the more what will be considered fully adaptive systems.
We wanted to provide improvements over typical time of daytiming and have connectivity to a TMC, although we do provide for that and we wanted to promote the use of NTC/IP.
Kind of going back to my graph earlier, the cost, we have significantly reduced the cost to get into an adaptive system.
We feel we haven't had a real good evaluation against the SCA T or a SCOOT system.
We've got a lot of interest against people doing that and we haven't gone" yet but we do think they probably perform relative to these other systems probably at the same or maybe a better level,
and you are going to be required to do some level of proactive Management meaning you will have to actively maintain your communications and detection systems,
and you will get a high resolution of data from your system that you can report in terms of performance.
To develop ACS Light, federal highway administration formed a public partnership, Siemens ITS headed up the actual development of the software, Purdue and University of Arizona helped out in that effort and then on the deployment side,
on our signal control manufacturers, our Controller manufacturers included Econo Light eagle which is now owned by seem ebbs, Mcane and Peak, Siemens.
The integration site, there were four integration sites, each corresponds to one of the manufacturers, and what these integration sites were were basically a test of the ACS Light software with that Controller manufacturers firmwear.
And it just so happens that while we were doing this test which was actually out in the field, we collected evaluation data, so we do have some before and after data in times of travel time
and delay reductions an then we Tyler Texas who was the first deployment site for ACS Light.
In terms of benefits, and reductions to travel tim, delay and fuel consumption using the TTI method, for calculating unit cost, our first deployment was in Gahanna, Ohio, that was an Econo Light test site
and we saw a benefit cost annualized benefit of $88, 408.
The second test site was Houston, Texas, it was an Eagle site and we saw an annual cost savings of $57 7,000, Braydenton was the Peak system site, and we saw $75 7,000 annual benefit there,
and then the last test site was an integration with McCain systems and that annual benefit was estimated at $327 thousand.
How do you explain the differences in these figures?
I think it comes down to a variety of things I think as we rolled out ACS Light, I Think it actually improved over time , and they learned lessons, so as you go from left to right it kind of shows that progression of deployment
or integration test, and then there's also some factors in terms of when was the system retimed last? And if you re timed probably within a year, and you deploy ACS Light,
you probably shouldn't see a huge improvement but what you would see is if you were to do a long term study I think you would see significant gains over a long period of time.
Okay, and that's pretty much it for my presentation.
I don't think I saw any questions come through the chat box.
If you do have a question, feel free to type it in there and we'll try to address those at the end of all three presentations.
And at this point, I'm going to turn it over to Dr.
Steve Shelby, who will talk about the development and functionality of ACS Light.
All right, thank you for the introduction.
I guess this is something that I'd like to do in these presentations is a little before and after survey, give everyone a chance here to get on the little chat window and maybe reveal your position as to whether you're a skeptic
or a believer, or on the fence line about adaptive control.
And then maybe we'll see where we stand afterwards.
There are a number of skeptics out there so that's perfectly fine.
I'll just move on here.
So this is kind of my, I can't quite see all of the slides because that poll is coming up but this is kind of the one slide version of the talk.
We've got, this is one intersection under adaptive control on the left and normal control on the right.
It's not normal traffic conditions on the right for whatever reason, there's a surge in that north bound left turn traffic if you look where that arrow is, you can see, I have a little pointer here,
you can see left turns spill out of the left turn bay and off the end of the screen here, and for whatever reason, traffic diversion due to accidents or construction or special events, that's going on and then the adaptive control.
This is if you look at the time stamp ps, I don't know if you have a 21 inch screen with high resolution like I do, but it uses the same times, this intersection has just been running under adaptive control for about a half an hour,
and so that's nutshell version.
The rest of the slides have four items I want to talk about.
Eddie kind of already talked about motivation and goals so I will probably go quickly over that.
I just kind of wanted to set a little context as I talk about the system components and by that, I mean, it's like processor and the hardware boxes were interconnecting to make the system, signals, and so fourth,
but in talking about the goals first I think it gives a better understanding of why the system is designed the way it is.
We already have ACS.
There's lots of adaptive control systems as Eddie mentioned we could have roads, scoot, SCATS, Eutopia motion, UTC, generations 1, 2, & 3, why do we have ACS Light, and so I think in talking about the goal, we'll establish what's that ,
give a better appreciation for the value-added of those goals and meeting those goals in the system.
And we'll talk about how it makes adjustments and finally the performance results.
Just quickly on the project, it's about a five year project.
We worked about 18 months on building the prototype and then it may be an idle year there before we got started integrating with each of the vendors over here, and then doing field tests with each and it was headed by Siemens.
I had a prominent role in the algorithm and all of the development, but there were others at Siemens.
Of course we had University advisory input and the valuation and ITT was the vendor reporting the simulation at the time.
Try to go quickly through this and this is taking you back to 1999 which is about when ACS Light was conceived and at that time, FHWA had spent money and developed five prototype s for adaptive control under the tracks program,
that the realtime traffic adaptive control systems which now we refer to as the ACS program.
So people weren't exactly lines up to buy it like we would have liked, and so the idea here is the traffic is a problem, if we went out and retimed all of our signals or at least the 75% they say need to be retimed,
we would say a 13 % delay or about a half a billion hours of delay a year.
And that's just that's the timing.
The thing about adaptive timing is it's not just poor timing for your typical daily or weekly traffic flows, and you have snow conditions, vehicles depart out of the cues in different manners.
When you have instructions, short-term and long term, that affects traffic flows and traffic diverts to other routes and signals encounter traffic that wasn't expected when the timing plans were created.
Same thing when crashes happen.
People divert.
Lanes get blocked, people change lanes so it's nice to consider that when we think about the slice of the pie that adaptive control is shooting at.
It's a little bit bigger than just that 13%.
Of course, you mentioned we've got self-assessments that say it's not doing the greatest job.
Polling meaning for political issues, the traffic is becoming a top concern among the people out there.
In 1999, the case was after all RT tracks development that according to ITS deployment database, we're still in the adaptive deployments in the U.S, So this document here, what have we learned about ITS was put out about that time
and that information about an ITE conference where a round table discussion with various engineers was, that forum was used to discuss why, why not use adaptive controlling and of course,
the same thing hat comes out of the traffic signal report card is that there's just deficiency of resources, and adaptive control didn't necessarily address that.
There's also uncertainty in the benefits and that stems from a number of reasons such as, now, is this timing, would this timing really be better than my timing.
Sure it's better than that other guys timing but would it be better than my timing? Comments like that come out and there's some I'ms the data just isn't available and there are a couple cases where it just hasn't performed so well.
Some of the systems out there don't have a graphical user interface.
Some require for a single arterial full time technician to monitor them and sometimes it's necessary to bring in experts or to calibrate certain parameters, so just moving on.
The goals of ACS Light, in a nutshell, it's just to just to build the deployable system but it's addressing all of those issues is what it would take to do that, and so Light is all about lower costs, by leveraging infrastructure,
bringing adaptive control to the close loop market which there wasn't really an adaptive control solution available for that market which is 90% of the systems out there.
For the last 20 years if you bought a field master, you got traffic responsive included in the box there, like most of the vendors that we talked with said maybe 3% of their customers actually use that,
and I guess one way to say that is it's maybe a bit of an art.
Of course another important goal is we need to meet performance expectations or valuation expectations is a better way to say it.
So here is the system architecture.
We've got an ACS Light box with communications and this is an arterial photo of Lafayette, Indiana, there was a simulation model put together by Purdue University, and this has seven Controllers, all talking to an ACS Light box
and again the AC S Light processor can either be deployed as a field master, we did that in three out of the four field tests or a central server, a windows workstation.
The user interface is not your typical front panel where you just punch in a few numbers.
It's a little more rich in display of data and so we have a web interface.
The web-based, it's relatively easy to configure.
Hit the upload button and most of the data comes, is uploaded into the system, maybe 90% of the data.
There are systems out there that would require you to enter that same information redundantly into your whatever you have in your signal, you have to put in your system, and then there's the problem of keeping the two synchronized
and making sure whatever changes you make in the field end up in the system as well.
And we simplified things by making, eliminating the need for calibration with some design there and just sticking to known facts and not requiring that you estimate things like how many people are going to turn right?
At a given approach , which is something that just changes by time of day.
On the communications front, a primary concern is cost of communications and the RT Tracks systems for considerable bandwidth, trenching for fiber optic cable is expensive.
If you have it, we can support an EPIP communication, but it designed to be bandwidth efficient and run on serial.
It uses NTP/IP.
And it will pull second by second.
This is a design consideration triggered by complaints about sensitivity to communications.
If the system has to get to, the essential system has to talk to a Controller every second to tell it to force off this phase, then if there are intermittent communications, that becomes an issue,
really executing the plan that your algorithm solved for, aside from that if you have peer to peer systems, these distributed systems have to talk to all adjacent smalls every second to say,
to get the information of how many vehicles are departing from upstream intersections every second, and if you miss your per second data polls every once in awhile then that affect the your arrival predictions and your queue estimates
and that affects your decisions and there comes a point when flakey communications results in pretty degraded or non-beneficial performance.
So we're pulling once a minute, which allows us to operate a lower bandwidth and if communications are a little flaky, we miss a pull or two, we have 60 seconds to ask a couple more times and get that information from the Controller.
So it's relatively relatively insensitive to communication errors but if there's horrible mun indication, no system will be able to deal with that, with that disclaimer out there.
Controllers, what we're looking at here is a NEMA Controller from Siemens.
It's an N50 Controller is what we use for the Siemens deployment.
Reduce costs of the system, there's just one ACS Light processor.
Some of the distributed systems with require a 2070 which is a little bit more expensive unit than the NEMA Controllers, or with a VME cage which allows you to add additional processors and these in particular,
some of the distributed systems, adaptive systems require several thousand dollar processor to be inserted in every Controller at every intersection so that cost is eliminated.
There's still a immediate to upgrade to NTC/IP capable firmwear with ACSLight support, which is a minor communications addition, but it's still the same firmwear that you had before, so there's no cost to retraining it.
Some systems require switching out to a specific Controller or a specific firmwear.
Looking at detectors, you design the needs of ACS Light to match, what's traditional.
And I think the traditional layout, actually the control layout would be stop line detection on all of the minor movements.
Sometimes there's no semi -- there's no detection on the through approach but often there's advanced detection, if you run free in the middle of the night there's usually advanced detection
or maybe stop line detection but in many cases a few detectors would have to be added at the stop line.
Certainly can't make intelligent decisions without information, so we do require the detection.
We're looking for detection in places you typically already have it.
Many systems required on exit lanes and in locations you wouldn't normally have it so there would be that added cost, even if you have detectors there would be that added cost to upgrade the certain systems.
Some systems are sensitive to the precise dimensions of your detector have to be 4.5 meters, you've used four foot loops, you've used video detection that ranges 70-100 foot detection zones in some cases, and of course,
if you're looking at like a volume count per cycle, you're going to get maybe one per cycle on a 100 foot long detection zone and enter 20 for a 4 foot loop, so the algorithm in ACS Light are designed for flexibility there.
We do allow all of the detectors to be tied together on an approach, on a given movement, and that said, it's preferable to have individual lane by lane detection and that gives better performance,
especially a read on the saturation so that's what the detectors look like.
A little less cost because we're looking for what you typically have and we're a little more flexible.
Moving on to the logic, it's not second by second.
It's not where every intersection is running without an explicit cycle.
It's based on timing plans.
We change the timing plans every five to 10 minutes.
This would be similar to having a dedicated engineer standing on every corner watching the traffic and making minor tweaks to the coordination parameters.
We adjust the splits, the offsets, currently we do not adjust the cycling.
So add-ins are scheduled by time of day, as they normally are.
The engineer picks the cycle length, and reason for that and this has met some resistance, but we held to our position, from a do not harm philosophy and the reason behind that is some of the adaptive systems used to adjust cycle lengths.
Simple heuristics because that's what it takes to get it in realtime and they don't get cycle lengths as good as you might find with an off line optimization all opt it any algorithm so there's a paper out there about cycles
and I'd be happy to share that with anyone that's interested but right now, we only adjust the cycle length for certain reasons
and I think that is reflected in the performance that if you use a very simple heuristic to adjust the cycle length, there are times when it actually does degrade the performance from a good existing timing.
So this was a fail safe feature I'm not going to talk about that.
Adjusting the splits, again here is our example.
This is State route 26 and U.S. 52 in Lafayette, Indiana.
This was that seven intersection arterial we saw an aerial shot of before, and there's a stop line, these little blue rectangles, this is dual ring, eight phase intersection and I'll just call your attention to this,
I guess it's Phase III here is the northbound left turn, if you can, I'm not sure everyone can see that.
There's a little tool bar over here but I don't think we have any zoom option.
Looks like I've got some John Madden type stuff if I want to , but --
No, there's not.
If people want to try to make their screen full screen they can do it on their own but there's really no zoom options.
Okay.
So the first issue is a measured demand, and we're pulling once a minute.
This is the phase data we get.
What you're looking at here is each road there's kind of clusters of two roads that's one for each ring and this is the last several cycles for the signal.
You can see for every second had a green, yellow, or red shaded section of that timeline which indicates which phase is active.
You can sort of see the variability in the duration of some of the phases.
You can see for instance here left turn phase has got skipped.
So we're getting data once a minute, but it's second by second resolution data and same thing for detectors, we pull once a minute but we've got second by second volume and occupancy, I think these red bars indicate volume
and the blue are occupancy.
Then, we sort of over lay those.
If you tell me that you've got 10 vehicles with cycle, I really can't tell you if you're saturated or not or how to adjust your timing but if you look at, for example, occupancy during just green intervals,
then you get a pretty clear indication of whether you're Using that green time completely or not at all.
And so this is how we measure demand.
It's not just occupancy although that's where we started.
It's not just occupancy but that's the simplest concept to keep in mind here.
And we average together multiple cycles that requires a minimum of three cycles or five minutes worth of data to make a decision to have reasonably stable demand estimates.
Here is another screen shot from ACSLight where we've got a table hereof phases 1-8 and corresponding the degree of of saturation.
This is equivalent to a volume to capacity ratio although as I said we might have 100 foot detection zone and the volume might be 1 or 0, so this is equivalent
and I'd argue it's what we're calculating is better than calling capacity ratio s, but here we have, for instance, this is Phase I, 55% utilized or saturated.
This was Phase III and that's that northbound left turn with an enormous queue, so green is not saturated, red is saturated or congested, and yellow sort of borderline .
My slides got moved.
This is just the same, a different representation that gives a ring diagram sort of view.
We can see Phase III is congested, Phase IV is borderline, so maybe we should reach across the barrier and take some time from the main street phases one or two, so the idea of the algorithm, this is, so let's back up
and the idea is to balance the degree of saturation across all phases so I could take some time and not utilized by one of these phases , give that time to Phase III, and in addition to that,
if there's adequate time for everybody to not be congested, and then if there's extra time available, we can allocate that from a biasing option,
you can can allocate that to phases we typically allocate that to the the coordinated phases to give a larger green window for better progression.
So, this was the before picture after we balance here is the after picture and now we've reduced saturation from 100% to 76% and we've increased the load here on some of the other phases and if I back up a little bit here again,
they aren't , they are just on the cusp of congestion, but they aren't really congested so you can't really tell between this phase , these phases which have not had time taken away from them
and these approaches over here with adaptive that have had time taken away, the cues are essentially the same.
But there's no left turn queue and an enormous delay for that approach there.
So that's a split adjustment.
Looking at offsets, this is a platoon of vehicles approaching this little bar here is a detector about 250 feet upstream from the stop line .
The slides seem to be having a mind of their own here, sorry about that.
Again, we're matching up volume and occupancy information, so this is a 70 second cycle length and here is the timeline and this is I can call this a green profile and this full height green bar indicates that over the last five cycles,
100% of the time the light has been green for this phase on this approach, 100% of the time.
This indicates that there is probably one cycle where the Controller didn't yield to the side streets.
There's no demand on side streets so it was green the whole cycle and over here you can see maybe half of the time there was some early return to green due to the side street phases gapping out.
And we're taking volume and occupancy information and averaging it together over multiple cycles to get, to see where platoons are showing up.
Here is a little bit easier to digest an example where these blue blips are the vehicles showing up, this is 18 2nd timeline, and they' reshowing up early
and they're having to wait a few seconds for the green light so the obvious thing to do would be to shift the offset earlier in the cycle, shift that green window so people arrived to a green light and have no stopping.
Of course that's easy to do, on one way streets but if you've got two way or a crossing arterial that's four way, you've got to consider arrivals to the pairs in each direction which may not come up together,
if you got different scenarios, you've got outbound approaches also, if you change the offset at one intersection you're going to effect the time that that platoon departs
and arrives to the green at the downstream intersection so ACSLight considers all inbound and outbound directions and basically makes an incremental adjustment.
This is configurable.
Here we're looking at -4 to plus 4 or keep it the same, that's the adjustment we're considering for the offset, and when you make those small adjustments that avoids any disruptive transition.
So that's how the offset adjustment works.
Again, we have four field evaluations as Eddie mentioned, I'll tell you about Houston, which was the Siemens site.
This is an arterial, here is Houston and then this is heavily trafficked arterial and there's some environmentally protected areas so everybody has to sort of pick a path around that, it's a heavily trafficked area
and you can see we had less delay in stops, 7% less fuel, with the Texas transportation institute's model, it was a benefit, an annual benefit of 57 7,000.
I think that was based on fuel costing about somewhere in the $2 range for gas at that point in time.
Didn't calculate pollution but I think it would roughly be equivalent to fuel savings.
This is arterial travel time.
Red is the four, ACSLight, yellow was after so there was reduction there as well.
That's field testing from pierce County talking to one of the engineers there, I believe the timings here were only 13 months old from what I was told.
They had ongoing development of housing development was being populated at that point in time right along that arterial.
So the question field studies and those were independently conducted field studies, it was Saber Wayne & Associates ran pro vehicles with GPS units and all of that data is available from Eddie Curtis or myself.
Purdue went into the simulation environment and they did just hundreds of scenarios, a.m., p.m., off peak scenarios and this is just one screen shot of what they were comparing to and when they turned on ACS Light
and what the delay was with ACS Light and I'll just summarize with these four rows of findings, first they started with optimized timing,
and they simulated for somewhere between 1-3 hours depending on the specific tests they were doing and in this test, they kept the volumes, turning proportions and departure rates
and all of those parameters fixed over the whole simulation time period, and used the optimized timing and then they turned on ACSLight starting with that optimized timing and you can say there were multiple simulation runs, more
or less there was no significant harm done to those optimized settings and I would attribute that largely to not trying to adjust the cycling using a simple back of the envelope equation.
It is not the say it was solved for.
If it was a significant change, it would appear as blue or red in bold so they started with the, to evaluate offsets they tweeked them a little bit from optimal and turned on ACS Light to see how ACSLight did
and they found better offsets than non-optimal offsets.
Similarly with splits, one of the things they did here to make the bad splits is they took all of the green time on the side streets and stripped them down to minimums and then handed it to the main street and then turned on ACSLight
and offsets were not allowed, and our progression biasing because was not developed at that point in time, so we had kind of mixed results.
And there's a number of reasons for that and one is you didn't have this progression biasing technique which really improves progression
and other thing is the delay in travel time is not the whole story so we took all of the time away from the side streets and here is the number of phase failures, we had 40 phase failures on this particular intersection,
and that's a cart sitting at the queue when the light turns green that didn't get out of the queue when it turned red.
I think that correlates pretty highly with phone calls so that's a good performance measures in a lot of peoples book so what ACS Light did when we turned it on is it took that time away from the coordinated phase
and gave it back to the side streets.
When you take all of that abundant time and huge dream windows away from the coordinated phases, that does disrupt your progression a little bit.
So that was another factor.
We are also looking only at occupancy on green at that particular time.
And there is shortcomings there and we had only 36 foot detectors.
They were timed even during saturated flow where the spacing between vehicles is more than 36 feet.
And so it can appear that one approach is not being fully utilized during its green when it really is, so the adjustments made on that don't work out so we've adjusted the logic and I think that's drastically improved performance.
Another test was to instead of keeping the volume static at these optimized values, changed the volumes around, allowed them to fluctuate a little more or I think this was probably that surge case on one of the intersections,
and that was beneficial.
So aside from those algorithms we're going to look at cycle time adjustment.
It's difficult to do a light cycle time adjustment but there are cases such as Braydenton, Florida we were doing a field test there and during our field evaluation one day we had to throw our data away for that day,
there was a fatality accident that completely shut down the freeway and I think it was seven lanes of traffic during the a.m. peak.
All dumped out on to arterial so we adjusted the splits to give more time to the arterial but that was really a drop in the bucket an that was a time where jumping to a higher cycle length was a much better thing to do, unquestionable.
So that would probably be a cup in the bucket in that case, but I think the most valuable aspect that will come out of the next phase of work, which will come out of the next few years will be looking at detectors
and doing some diagnostic s that we seen before.
So minor enhancements will be forthcoming.
I just found this the other day, ripped it off from a colleagues slide, I thought that was interesting.
So do feel free to contact us.
This is my contact information.
There's a prior NTOC webinar that's archived earlier during the project which gives a slightly different look at this project, more research.
You've got some overview papers, FHWA has a couple of websites with an FAQ.
At that point, that's all I have to offer, so I'll turn it over to Kirk Houser, to talk about his deployment.
Yes, I'm Kirk Houser, I'm the traffic warden near for the City of Tyler, Texas and I'm going to give you a sort of the Tyler experience with ACS Light,
and tell you a little bit about some of the possible things in doing this kind of a project, and hopefully help give some guidance to somebody who is thinking about ACS Light and maybe wants to know what they should do next.
A little background on Tyler.
We are in East Texas.
We are a City of about 100 thousand, and we are sort of located out in sort of the middle of know where by ourselves.
We're not part of a bigger major metropolitan area so we're sort of a regional shopping hub and employment area.
In this past year, the city did a big comprehensive plan update and we asked the citizens of Tyler what they thought the number one problem or various problems in the city were and their number one issue was traffic congestion.
So we formed a special traffic congestion and transportation committee as part of our comp plan update, and one of the things that came out of the committee was looking at some arterial improvements
and also some identified adaptive control and other smart signal technologies as maybe something that could help us out.
This was the corridor that we chose to deploy on, this is U.S. 69, South Broadway, and it's a collection of, it's one arterial here and Tyler is on kind of a hub-and-spoke.
Our streets are really not on much of a grid once you get outside of the old part of town.
Our side streets are fairly irregularly spaced.
There's also creek corridors in here, we're very forested and not very hilly but we're not as flat as what you would think Texas is normally and so there's a lot of terrain to deal with
and developers tend to build subdivisions with little streets and they didn't like building bridges and crossing creeks and that sort of thing, so we don't have a lot of good connectivity.
This, the traffic infrastructure on this corridor was 16 intersections, you see it's kind of in a little grid.
Closed loop master and we had an existing hard wire copper 1200 communication and our detection was a mixture of loops and video detection at the stop bar with little to no set back detection at all.
We felt there was a need to do better than what was just standard procedure.
We went on all of our signals in town on a three year cycle.
We have a concern over traffic delay, and we felt that on certain corridors, our signal timing was updated fairly frequently but really not fast enough to keep pace with the high growth.
In general, the corridor that we're looking at the flow traveled pretty smoothly at peak times, but during the middle of the day, the side streets really picked up and there's a lot of variation in it due to the commercial nature.
Some days a lot of folks go out and try to run errands during the day and some days they don't and we also felt that our traditional timing plans were weak on weekends, and the holidays.
When we the sat down and looked at ACS Light, we knew we wanted to upgrade our communication speed.
We were implementing on 16 intersections which is pretty large for ACS Light, and we decided to go with a spread spectrum radios at the time.
We also upgraded our signal Controllers mostly to be compatible with NTC/IP, and to take advantage of speed increase.
We needed to add the set back detection as Steve has described, and for that we chose a radar, this little schematic over here is an example from the construction plans of our side fire radar set ups,
and then of course we had to get the upgrade signal control software to include an ACS Light module.
We begin turning everything on in August of '07, and communication problems delayed the real kind of working until October.
We have a conflict between the set back detection and the radio communication systems both of which use 900 megahertz
and we found it very difficult to find hot patterns where the two sets of instrumentation were not talking over each other.
What we sort of discovered in really working with our comp system and getting it where it was working pretty well that it was the system was making offset adjustments fairly well but it was a less successful,
I mean sorry it was doing really well for splits but it was handling offset adjustment very well.
A part of the situation there is it's collecting data back from all of the set back detection and the stop bar detection and all of this data is coming back to the central.
It makes some decisions about timing plan changes and it sends out these data changes in the form of dummy plans that it tells all of the Controllers so it does a download to the Controllers
and then what happens then is it's also simultaneously trying to collect all of this data back from accounts and it was just too much going on there and a lot of retries and lots of issues there.
I want to kind of talk about some of the lessons that we've learned in this project, mostly with consultants and vendors.
Be sure to select consultants and vendors that actually have some experience with ACSlat and adaptive control.
One thing we did as we were implementing I would describe to vendors or consultants this is what I want to do and this is what I need, and they would say, well, we'll use this because that should work,
and the truth of the matter is they really weren't sure themselves because nobody has ever really done it before.
Avoid piecemealing, to expedite our project we sort of split it into several segments.
New Controllers and new communication system, some set back detection, and software integration were all separate pieces of the puzzle, and when all these pieces came together, that's where we had some problems that could be avoided,
so I'm just suggesting that if you do this type of a project, you need to coordinate the leadership and everybody needs to be on Board and make sure that everything stays compatible.
Manage your expectations.
The citizens in Tyler say that traffic congestion is the number one problem.
We formed that special committee.
Adaptive control was presented as the technology we wanted to pursue, but there was quite a bit of media coverage and hype over our comp plan because it was the most aggressive
and Allen compassing comprehensive plan update that we've ever taken on and our level of public input that we went out and sought was pretty unprecedented for our community so there's a lot of media attention and soon,
what happened is we got a lot of media coverage on our signal system and before long, people thought it was going to be some sort of magical silver bullet that would solve all problems and magically make all of the cars go away somehow.
Something else to think about is deadlines and stealth.
I put the picture back up here about showing one of our set back detectors looks like.
The set back detection was done with a construction project and it probably was the easiest construction project dealing with a single contractor we've ever had in Tyler and it went in very smoothly, did everything on time, under budget,
everything went great, but the problem there was that they got the units in so quickly that drew a lot of attention.
These things are sort of hard to miss out on the corridor and people saw all of this stuff going up so everyone kept calling and saying what's going on, what is going on? And then when they figured out what it was for,
it was like when will it be ready, when will it be ready and one thing that you need to factor into a future project is allowing some time for integrating and programming the ACS Light model.
Which just brings me to Montgomery Scott here who always grossly inflated his estimates and is suggesting that that's kind of what you need to do when you're dealing with a City Hall and the media,
give yourself lots of fudge factor there for when you think you're actually going to get this up and working.
There's also some manpower issues to consider.
ACS Light system gathers up a large quantity of data and this data is all useful, and the more time you spend with somebody watching that central computer, there's more things that you can learn about the corridor
and plus of course when you deploy more technology in the field that's more things to take care of.
Part of our problems with our communication system where it's both systems are 900 megahertz we basically had to take a technician and put him in the field where he just tweaks the radios almost non-stop to get the system really up
and running to where it was in October.
So what's next for Tyler? We do intend upon expanding ACS Light along the East and West of Loop 323.
The Loop around Tyler is completely at grade facility.
We don't have a flee way here.
We just have traffic signals.
We intend to put in some sort of set back detection that will be a little more stealthy.
That is we can put it in and it doesn't Garner quite as much attention as the set back detection that we used with the radar.
We intend to use a comp system that's hard wire or probably fiber optic and we're not really going to make a huge announcement about this project in the media or in the public until pretty much it's already up and already operating.
And with that, I'm pretty much done.
Okay, I would like to thank Steve and Kirk for great presentations.
Kirk, thank you for being very candid about your system.
I mean it's one of the things that we need is to have some real hard data about what it takes to deploy these systems and I think that's what a lot of the people that are kind of sitting on the fence,
that's the kind of information they immediate to see.
Certainly as you pointed out these are not, there had no silver bullet to take care of all of your traffic problems and you certainly need to probably get help when you're thinking about deploying communications
and detection systems because these are the eyes and ears of the system and if those aren't working effectively, then your system isn't going to work either.
What I'm going to do right now is go ahead and start going over some of the questions and I'm going to start with the first ones that were posed, if anyone has additional questions that they would like to type into the chat box,
I'd be glad to address those.
I'll start with the first question, and it's from I guess Gannett Consulting and their question is, do all four vendors offer the ACS Light processor?
I don't know, is that Steve, do you want to take that one or I could answer that if you don't want to.
Yeah, I'll let you answer that.
{LAUGHTER}.
Okay.
Um, the processor is for the field test, there was a field computer that was used, and probably I would say that that processor is available to vendors, it's just the speck for the computer and it could,
I think eventually what we'll have is ACS Light will be integrated into the field master and that will eliminate the need for an external processor.
I think that's a long term vision before in the meantime, it will be a field hardening computer.
Kirk, what are you guys using in Tyler?
We have ACS Light on a desktop computer running the web application.
It's a dedicated standalone machine, back at our central shop, and it talks to our communications system across our city network.
Down at that corridor, next to one of the intersections we have a fire station and that fire station is on our city internet and so that's where we tie into our system there.
Thanks and that's a good point.
ACSLight can run out in the field along with your field master, using a field hardening computer or it can operate from a central location as Kirk just said as you have the communications down to the local intersection
and I'm just going to add that the ACS Light software is, it can be licensed by all four of the vendors.
Each of the vendors was given a license to distribute ACS Light at the conclusion of the research project.
The next question is from ODOT, and it's: What are the NT Practice frac IP objects needed for ACS Light to work? And I'll ask that, I'll pass that to you, Steve.
Okay, we've designed, well, there's a number of standard N TC/IP objects and there's a standard signal Controller MIB or Management Information Base that describes what a standard Controller should have like for each phase,
minimum greens and that, but much of the data comes in that.
No one has something that just adheres perfectly to that standard, and there's always additional proprietary objects for every Controller but we upload a portion of the data, phasing data, coordination parameters and such,
so those are kind of standard upload items, but looking at what was available for status across all of the four vendors we looked at,
the lowest common denominator among what was available was just not adequate to make adaptive decisions so we defined sort of large block of data r for phasing data
and a large block for detector data which gives that second by second information and it's compressed in a bandwidth efficient format so we can go over 9600 baud, so these are two objects
and we have a MIB that specifies what goes into those.
And I don't believe that NEMA committee has adopted those additional objects into the standard as of yet, but hopefully that will happen.
At some point in the future.
Okay so the next question is it's two part question.
The first part is: How efficiently does adaptive systems work during rush hour if the intersections are at capacity?
I would say once it reaches capacity, it's basically going to look like it did before with fixed timing where ACS Light, I don't think there's any, at capacity, the timing isn't going to solve that problem,
but the shoulder leading up to and coming down from capacity is where there are benefits, so right as you approach the capacity, maybe one approach is slightly over saturated and another is not,
and so it can kind of shave off the prolong the onset, not prolong but postpone the onset a little bit of of that congestion and maybe get out of it a little earlier because when you're coming out of it maybe one of the intersections,
one of the approaches comes out of saturation earlier than competing approach, and so it can really had indicate to take advantage of that.
So we can sort of shave off the shoulders on that peak but not when there's too many cars, single timing solutions are not necessarily going to solve that problem.
Okay, the next, the second part of that question was how do the adaptive systems work and grid networks with spacing at 330 or 660 feet, with high pedestrian volume, high turn volumes, and how is it, hats another question, Oh,
so I'll answer that one.
In general, adaptive systems I don't think are really designed to work in grid networks and certainly ACSLight is not intended for grid networks.
It's more of an arterial system, so in a tight grid, certainly we're talking about a tight grid at 330 or 660 feet spacing, ACSLight would not be the application that you would choose for that type of facility.
I think in many of the studies, I think Scoot has shown some improvements under grid systems but ACSLight is really designed for arterial systems.
And the third part of the question is how does adaptive compare to responsive, I'm assuming meaning traffic responsive systems? Steve do you want to take that one?
Sure.
I think adaptive you've got software that's trying to search a number of options and evaluate and find the best option using measures whereas traffic responsive is if we were trying to balance the degree of saturation
and traffic responses, you're trying to guest it mate that what volume or occupancy threshold are we becoming saturated enough that we want to jump to a higher cycle length, or and that's a little, it's a bit of an art
and just like signal timing itself, the parameters that go into traffic responses, they age as well.
So it's hard to, traffic responsive is hard to quantify how well it's going to do.
It's a function of the configuration in many respects but one look at it from our field data, I don't know if you had all of the numbers from each of the four sites I think we showed cost of benefit ratios but in Gahanna, Ohio,
we were asked to instead of using our offset algorithm to reduce the number of detectors to just a few detectors in each direction and use a 1970's style traffic response instead.
And by doing that I think that you change the offsets, it's great for one direction but not so great for the other direction, and that particular site we didn't have the greatest performance
and I think that was due to using a different offset algorithm.
There isn't, you can be effective with traffic responsive and you can also be in effective.
It can go into transition more often than you'd like which will disrupt benefits, so it's just a bit of an art I guess is the way to say it.
Right.
And I'll add to that that traffic responsive is probably the most widely available, under utilized feature in field masters.
Almost virtually every field master has the ability to do traffic responses and almost nobody uses it and I think it's probably due to some of the complexity or the perception that there's some complexity to set it up.
And then the next question is asking about explain the algorithms used to determine a shift in offset or split is needed and how is it calculated? In the interest of time, I am going to suggest that we,
if you want to know more about the algorithm that we send, send us an e-mail and we can e-mail you the paper that Steve presented during TRB, because I think that question, we only have about five minutes left
and I think it will take at least five minutes to discuss that.
So I do have, the person the person that ask question I have your e-mail address and I'll send that to you.
If anybody else wants that then send me an e-mail and we'll get that information to you as well.
There's another question, and this is an important one.
Kirk, how much did your system cost per intersection and where did the funding come from, and then I'm going to go ahead and add the next question so that and it's why did you choose this detection instead of video?
The entire project for South Broadway at first corridor was around when you added all of the pieces together about $ 500 thousand and that roughly equates out to about $31 thousand an intersection.
The money we just, it came from general fund as it's just a special project.
We have a special fund that we set aside to do just special projects with, and all of the various departments in the city just sort of make their pitch as to why they should get a piece of that special money, so that's how we funded it.
It was all funded by the city.
There weren't any grants or State money involved in any of it.
Right.
And on side fire detection, mostly chose it over video for its ease of set up and just seemed very reliable when we tested it.
We've had some issues with video detection, always needing to go out and play with it quite a bit, and we've just seen really good results out of our side fire radar.
The downside I said in our presentation is that the units themselves are not very attractive.
And the public has kind of noticed that and complained just a little bit.
Okay, and I'll add-on the cost.
We've estimated the cost of ACSLight to be comparable to and we're just talking about an upgrade, if you've already had all of the detectors and the communications, you're not doing any of those types of infrastructure upgrades,
just the software, firmwear upgrades and integration cost are pretty typical of what you'd see for retiming projects so we're talking somewhere around $3500 per intersection.
Okay, the next question is from Dale and he wants to know how does ACSLight implement the pro freeing bias.
I think that's a quick one.
I'll let Steve answer that.
Okay, well I guess the quick answer is if you select which phases you want biased and that's I guess an easy way, this is not exactly how it works but an easy way to think about it is maybe if all movements can,
if we can rebalance the degree of saturation such that there's mow more than about 85% saturated, then any time left over would go to those equally balanced among those phases that are selected for biasing
and that's usually only the main street phases but if you have crossing arterials, you could select through movements, two through movements on the main street and two on the side street.
Okay, and the next question comes from Alla Banja with Arcadis, and they want to know what are the additional feature s in the full version of adaptive control systems that are not available in ACSLight?
I guess I could answer that one.
I think in most adaptive systems, normally you'll see, that's kind of a hard question to answer.
Primarily I would say that most of the adaptive systems use second by second communications and they're updating almost every cycle and a lot of cases,
it's limited by the user to prevent changes from happening because all of the transition s tend reverse the benefits that you'll see.
ACSLight does not have a traffic model that runs in the background.
I think it's the Scoot system that uses Transit 7 F or something of that that's running in the background to make a lot of the timing decisions,
so ACSLight uses fairly intuitive algorithms I think that they don't do a lot of rigorous calculations to come up with or modeling to come up with the decisions that it makes.
It's very intuitive.
I think it works a lot like a human would at an intersection.
It's just tweaking offsets and splits.
Okay the next question is from Gannet again and it says: Can can the ACSLight software processor run more than one integrated signal system? I'll pass that to you, Steve.
Right now, they're not like if you had two closed loop systems we would operate them independently, so they wouldn't necessarily share data at this point in time.
That's something we would like to get to, but at this point in time we've just gotten off the ground and we're focused on those 90% of closed loop systems out there that aren't necessarily one large grid.
I'm not sure if that answered the question but that's what I would offer.
Feel free to contact me for more detail.
I think in Tyler, for our second corridor, the question that we're tossing back and fourth is whether
or not we are going to bring in a second computer with another ACSLight instance running on that second computer for the other corridor for our West Loop,
or if we're going to have it on one computer just running two separate instances of the software and I don't know if that decision has been made yet.
I'm leaning towards two computers.
Okay.
Jennifer, can you put up the slide with our contact information? I think it's like the third?
Sure.
Third slide in my presentation?
Sure, I'll do that now.
Um the next question SR the ACSLight MIBS on the NTC/IP website and that's easy.
No, they are not.
With that MIB be available, Steve, on request?
I've provided it to a couple of people.
It's a moving target in a sense that I hate to jump on and have everybody jump on a prematurely on a standard when there will probably be changes in the next phase of the research to address some lessons learned.
Yeah, I would be willing to share that if individuals want to contact me.
I've seen a tendency to immediately standardize support for something that is not matured to the point of a proven standard, but is just a first draft cut which is what this was, and it's certainly effective
and it's interesting to look at.
I think it's got room to grow so I haven't distributed it widely.
The next two questions are fairly related.
How does the system work during pre-emption, and what does it do about transit priority.
I'll give both of those to you, Steve.
It basically goes into the stand by mode because you might have a phase that gets omitted, you might have a, you know, if it's a case that there's no phase demand
and the phase gets skipped then we recognize that as no demand in that cycle but if it's during pre-emption, if a phase gets omitted, that's not representative of the full demand that might have traveled through,
had it been allowed to Max out or force off and so we don't consider that data and sort of we just kind of stand by until it comes out of preemption.
Reports from Ohio, a couple of the field tests had emergency vehicle preemption going on and one of them in particular had a school that would have an enormous preemption to unload all buses at the end p of the day,
and ACSLight would after the preemption was over would sort of help it to recover a little bit faster but it's not that second by second realtime response.
Okay.
Thank you.
I think that's the last question that I saw.
One thing that I wanted to add and it's something you mentioned, Steve and it's that there were some simulation tools developed to test ACSLight,
so there is an NTC/IP run time extension that allows it to communicate with the ACS Light software so they're able to test a lot of scenarios, I think it was Purdue University that actually did the testing , with Corsem,
and I've actually suggested to some audiences that they would consider doing a simulation prior to deployment, but if you're going to hire a consultant to do simulation exercise, you don't have the ability to do-it-yourself in house,
then you probably will spend more doing the simulation than it will cost you to deploy ACS Light but it's certainly a consideration if you had the expertise and the ability to do that.
And I think there was another point I wanted to make.
I'd like to add --
Okay.
FHWA is also, and this isn't Eddie's office but another division is for a product demonstration showcase which would probably happen in Houston, Texas,
And the idea there is to invite agency representatives to attend like a full day seminar where you'd have a morning of a little bit more elaborate presentations than this and then afternoon of going to field sites
and looking at the equipment, and discussing the equipment and deployment issues and watching it in action.
So that, if you would be interested that sort of attending that sort of showcase, this program is designed for emerging research that they're trying to transfer to practice that's been relatively successful, then give me an e-mail
or contact Eddie Curtis and we can get you the information P as it becomes available.
All right and I have actually have a question for Kirk.
Okay.
My question, I almost would like to get a personality profile run on you, Kirk, because granted, you did ACSLight as part of a kind of a larger signal system upgrade that you did with all of the detection
and the communications that you put in.
Right.
But the question is why, there were other adaptive systems, what was kind of your reasoning behind going with AC SLight? Because I didn't, obviously I didn't market ACSLight to you,
it was a decision that you came up with on your own so what was kind of the motivation behind that?
I guess it had to do with that it was the newest technology and that it was sort of, it was sort of marketed as being simpler to rollout than something like Scoot.
I originally contacted Siemens talking about adaptive control to ask them things about the other systems and SCATS and things like that so the original conversations I had with them was about Scoot.
Okay.
And then we just sort of migrated towards ACSLight because the research was wrapping up and it looked like it could a achieve similar results for a little bit less implementation cost.
Okay.
Thanks.
And one other thing I'll add and I think you made this point , Kirk, was that in a lot of the adaptive systems when you're looking for expertise in terms of what communication systems or how do you want to set up your detection,
with 25 systems throughout the United States in the last 20 years, there's such a small pool of professionals that are actually familiar with this and actually do have expertise.
Certainly the federal highway wants to support this effort and we do have people on the Operations technical service team that can provide assistance to you in terms of you need to make decisions about detection,
devices whether it be where to place it, and definitely communication systems too.
We've got a lot of expertise in that area so you have any questions or even if you want more information about ACS Light, certainly feel free to contact us.
It doesn't cost you anything to get our services and we get into the area where you asking us for things that consultant s should be doing, we will certainly direct you to a consultant at that point.
I just wanted to make that point.
I don't see any other questions.
I'd like to thank Jennifer, Steve, and Kirk, for their participation, and hopefully, we'll maybe do this again in the future.
And again, if anyone has any questions or wants additional information, feel free to send us an e-mail and I have been doing a host of ACS workshops throughout the country and we pretty much do those on a request,
and we usually do about half a day and really get into the details of the system.
So, thanks.
Well, and thank you, everybody.
Before we close out I just wanted to bring up a few slides about the national transportation operation coalition.
This slide just lists the member organizations.
If you go to the website it's www.pointdNtalk talks.Com and find out more about these organizations and I will type that address in again.
It's up earlier in the slides.
Or in the chat area, I'm sorry.
The N-talk website contains information about upcoming Webcasts so you can go and register and I think we have one coming up in May about new MUTCD regulations so you can register for that one from there
and it also contains a Webcast archive page with the slides and recordings of the previous talking Operations Webcasts and will have the slide s and the recordings from Today's presentation up in a few days.
There's also two discussion forums, one focusing high level on strategic issues an the other on ITS deployment and lessons learned.
And then finally, you can also sign up on the site to receive the N-talk newsletter by e-mail twice monthly.
And that's it.
That concludes the Webcast for today.
So thank you to the the presenters and to Eddie for moderating, and everybody have a great rest of the day.
Okay, thank you.
Thanks.
Goodbye.
(end)