Monday, June 17, 2019

What Happened to the Beulah Traffic Signals over this past Weekend--What is Happening Right Now?

This weekend in Beulah--the traffic signals on 9-Mile Road in front of Navy Federal Credit Union's two eastern-most entrances were way out of sync.

Something was definitely wrong--as the traffic began to stack up on 9-Mile Road going East and West---even though there were no cars going into or out of NFCU.  I was out running errands on Saturday and Sunday and knew, immediately, that something was wrong.

"Why is traffic stopped at 10:30AM on a Saturday??"

Drivers were getting frustrated---several went around cars waiting at the light and drove through the red lights.

So I immediately fired off emails to see if we could get this fixed ASAP.

And staff deserves credit for immediately engaging and working toward the solution right away.  Here are the emails:


"David [Forte],

This weekend the lights on 9-mile road at NFCU way and security place were WAY out of whack.  This created a nightmare for those of us going back and forth with our lives in and out of Beulah.  There would be long delays at both lights----long and unnecessary----even though there was zero traffic coming into and going out of NFCU.  It was ridiculous.  Can someone please look into this and see what went sideways with the timing this weekend—and can we please look at getting this fixed?  Thanks!

R/

Jeff Bergosh
Escambia Board of County Commissioners,
District 1
221 Palafox Place Suite 400
Pensacola, FL 32502
850-595-4910 office
850-377-2209 Voicemail
@jeffbergosh"

To which I received the following responses:

"Will report this immediately.


Thanks."



"Kelli/Eric,


Please see the below email from Commissioner Bergosh re: the two traffic signals on 9 Mile Road and Navy Federal (Navy Federal Way and Heritage Oaks), and direct/respond accordingly. 

Please, also, advise as to the resolution(s).

Thanks."

This afternoon I received an email describing what caused the signal timing issue, and also the resolution:

"All:

On Friday Ingram Signalizations’ directional bore crew begain installation of the new signal conduit to service the intersection of Heriatage Oaks and 9-Mile Road. Currently the entire intersection is operating using temporary loops. As work progressed from the installation of the water and sewer, through the roadway pavement several splices and temporary connections were made. During the directional boring the crew inadvertantly hit the homerun (the main connection for the loops beneath the roadway. The crews did not recognize that they had damaged the loops and the signal went into the default mode and operated on the timing. There is not much impact or change during the day, however it became very noticable during the evening hours and thus the compalints were received.

Ingram was on-site this morning troubleshooting the issue. They discovered the damage and tried to make repairs however, they were onable to locate one end. They pulled new cabling and have completed re-wiring of the intersection and it is back in actuation mode. Ingram also reviewed the Navy Federal Intersection and all loops and cameras were functioning properly."

I'm told the technicians are still working the issue as of right now....as the first fix hasn't solved the problem...

"Mr. Bergosh:

My staff just reported that the signal seems to be lagging again. We have contacted Ingram Signalization and they will go back out and see what is happening.

Sincerely,

Michael Lenga
Project Administrator
Radiation Safety Officer
Stantec
8130 Pittman Ave."






No comments:

Post a Comment

Abusive, profane, and/or off-topic posts will not be allowed. Unprovoked ad-hominem attacks will not be tolerated. All posts are subject to moderation, posts that violate these policies, spam, posts containing off-color language, and any other inappropriate comments or content, as determined by the blog administrator, will remain in moderation and may not be added on the site. This site is not my campaign site, but in an abundance of caution I will offer the below disclaimer.