I featured NLEX or the North Luzon Expressway and SCTEX or the Subic-Clark-Tarlac Expressway last year. This time, it is best to feature SLEX or the South Luzon Expressway.
SLEX was mentioned in ITS topic I posted early last year which discussed on how their ETC system reduced queueing in tollbooths.
Good thing, I was able to get the SLEX toll rates! So here it is:
Entry Point Class 1 Class 2 Class 3
Nichols 78.00 155.00 233
C-5 78.00 155.00 233.00
Bicutan 48.00 95.00 143.00
Sucat 30.00 59.00 89.00
Alabang 13.00 25.00 38.00
Filinvest 12.00 24.00 35.00
Susana Hts. 9.00 18.00 27.00
San Pedro 8.00 16.00 24.00
Southwoods 5.00 10.00 15.00
Carmona 4.00 7.00 11.00
Mamplasan 2.00 4.00 5.00
It took almost a year for me before finally having an idea to post about SLEX. I do not have much to say about SLEX since I rarely (because I live in the north) pass through this transport infrastructure. Only last Saturday when I together with churchmates went to Enchanted Kingdom was I able to take SLEX photos and had the *eureka moment to post something about SLEX. That one time chance to see SLEX again after several years still did not give me much ideas to write here. Anyway, the traffic was generally okay during that time maybe because it is a Saturday.
I would rather pass on the question to you dear reader, what can you say about SLEX? ;)
Monday, February 1
Lessons Learned: Monitoring Highway Congestion and Reliability Using Archived Traffic Detector Data by Turner, Margiotta and Lomax
Technical reports, research studies, and publications about transportation engineering fill my list of must-be-read-now notes. There is so much to learn and take note from all the written articles. If you ask WHY on earth would I read these boring stuff? My answer is because I need to for my NEW thesis topic. Apart from this main reason is that I love transportation engineering, I like doing research in this field, I enjoy everything that goes with it. (possing with two hands up! =)
Anyway, so much for intros.. I came upon these Lessons Learned: Monitoring Highway Congestion and Reliability Using Archived Traffic Detector Data by Shawn Turner, Rich Margiotta, and Tim Lomax. This FHWA report gives important insights on three general areas: analytical methods, data quality, and institutional issues. The following texts were directly taken from the report. Here are the top 10 lessons:
Analytical Methods
1) Don't wait for a "silver bullet."
The lesson learned is that transportation agencies should not wait idly for a “silver bullet” dataset or collection technique. More often, change in transportation is evolutionary rather than revolutionary, and agencies may find that what seemed like an ideal data source also has problems. Of course, agencies must become comfortable with available data resources and their features and limitations. In a limited number of instances, available data may be so poor as to not be considered for performance monitoring. Data of such poor quality should be obvious to even the casual observer.
2) Travel time modelling and estimation will always be necessary.
The lesson learned is that travel time modeling and estimation techniques will always be necessary (even with widespread availability of collected link travel times), particularly in a performance-based planning process. One of the challenges will be to ensure that estimation techniques produce roughly compatible travel time estimates as those from direct measurement.
3) Visualize the data, pictures are cool!
The lesson learned is that simple charts and graphics are more easily interpreted by this diverse audience than complex data tables and lengthy text descriptions. Data collectors and analysts may be adept at interpreting complex technical data because that is their primary job function; however, other non-technical audiences may only be able to devote 30 to 60 seconds to understanding key report elements.
4) Whatever affects traffic should be part of tperformance monitoring.
The lesson learned is that, to be effective, performance monitoring must also gather information on activities and events that can affect system performance. Examples include:
• System usage;
• Traffic incidents;
• Work zones;
• Severe or inclement weather;
• Special events;
• Economic conditions; and,
• Data quality.
Data Quality
5) Use can improve quality.
The lesson learned is that, in these instances, the agency or workgroup collecting data should be encouraged to use the data to improve their own agency functions or decision-making.
6) Support for operations can be built with quality archives.
The lesson learned here is that data
collected and archived while managing the transportation system can be easily reformulated to demonstrate the benefits of operations and management activities. However, the reuse of operations data for analytical purposes requires at least two things: 1) foresight to develop information systems that support real-time traffic management activities as well as historical analyses; and 2) commitment to collect and maintain quality data that can be used to demonstrate the benefits of operations... ...Archived operations data can help to “level the playing field”.
7) The devil is in the details.
The lesson learned is that the devil is in the details; that is, there are several seemingly minor data management practices that could have significant consequences when using archived data for performance monitoring.
Institutional Issues
8) Find and fix the barriers that hinder performance monitoring.
Some of the barriers to the development of archived data systems are similar to those experienced in further developing ransportation operations and management functions:
• Lack of financial resources for building and maintaining systems;
• Professional capacity to manage and analyze large data archives and warehouses;
• Widely ranging costs and benefits of implementation; and
• Uncertainty about data quality.
It will be vitally important to identify and remove these and other barriers to performance monitoring.
9) Performance monitoring may be a "killer app" for archived data.
Current trends and anecdotal evidence indicate that more traffic managers have taken an interest in developing and maintaining data archives. There appear to be at least two applications that
provide tangible benefits to traffic managers:
• Performance monitoring – helps traffic managers preserve or expand funding for operations; and
• Detector status/health reporting – helps traffic managers diagnose and troubleshoot extensive data collection systems.
Of these two applications, performance monitoring appears to be the most compelling application that is likely to strengthen traffic managers’ interest in developing data archiving systems.
10) Local knowledge contributes to national interpretation.
The lesson learned is that capturing local knowledge is desirable for interpreting system performance at a national level. State and local agencies are likely to be more familiar with highways in their jurisdiction and significant activities or events that have affected system performance. Some State and local agencies may be monitoring performance using other methods or techniques that could confirm or differ from national congestion monitoring results.
Because of their experience with local issues, State and local agency staff may also serve as a “reality check” for data collected in national congestion monitoring. However, this capture of local knowledge is currently, at best, an informal process that involves sporadic communication with State and local agencies.
**Note that this FHWA report can be downloaded in their website.
Anyway, so much for intros.. I came upon these Lessons Learned: Monitoring Highway Congestion and Reliability Using Archived Traffic Detector Data by Shawn Turner, Rich Margiotta, and Tim Lomax. This FHWA report gives important insights on three general areas: analytical methods, data quality, and institutional issues. The following texts were directly taken from the report. Here are the top 10 lessons:
Analytical Methods
1) Don't wait for a "silver bullet."
The lesson learned is that transportation agencies should not wait idly for a “silver bullet” dataset or collection technique. More often, change in transportation is evolutionary rather than revolutionary, and agencies may find that what seemed like an ideal data source also has problems. Of course, agencies must become comfortable with available data resources and their features and limitations. In a limited number of instances, available data may be so poor as to not be considered for performance monitoring. Data of such poor quality should be obvious to even the casual observer.
2) Travel time modelling and estimation will always be necessary.
The lesson learned is that travel time modeling and estimation techniques will always be necessary (even with widespread availability of collected link travel times), particularly in a performance-based planning process. One of the challenges will be to ensure that estimation techniques produce roughly compatible travel time estimates as those from direct measurement.
3) Visualize the data, pictures are cool!
The lesson learned is that simple charts and graphics are more easily interpreted by this diverse audience than complex data tables and lengthy text descriptions. Data collectors and analysts may be adept at interpreting complex technical data because that is their primary job function; however, other non-technical audiences may only be able to devote 30 to 60 seconds to understanding key report elements.
4) Whatever affects traffic should be part of tperformance monitoring.
The lesson learned is that, to be effective, performance monitoring must also gather information on activities and events that can affect system performance. Examples include:
• System usage;
• Traffic incidents;
• Work zones;
• Severe or inclement weather;
• Special events;
• Economic conditions; and,
• Data quality.
Data Quality
5) Use can improve quality.
The lesson learned is that, in these instances, the agency or workgroup collecting data should be encouraged to use the data to improve their own agency functions or decision-making.
6) Support for operations can be built with quality archives.
The lesson learned here is that data
collected and archived while managing the transportation system can be easily reformulated to demonstrate the benefits of operations and management activities. However, the reuse of operations data for analytical purposes requires at least two things: 1) foresight to develop information systems that support real-time traffic management activities as well as historical analyses; and 2) commitment to collect and maintain quality data that can be used to demonstrate the benefits of operations... ...Archived operations data can help to “level the playing field”.
7) The devil is in the details.
The lesson learned is that the devil is in the details; that is, there are several seemingly minor data management practices that could have significant consequences when using archived data for performance monitoring.
Institutional Issues
8) Find and fix the barriers that hinder performance monitoring.
Some of the barriers to the development of archived data systems are similar to those experienced in further developing ransportation operations and management functions:
• Lack of financial resources for building and maintaining systems;
• Professional capacity to manage and analyze large data archives and warehouses;
• Widely ranging costs and benefits of implementation; and
• Uncertainty about data quality.
It will be vitally important to identify and remove these and other barriers to performance monitoring.
9) Performance monitoring may be a "killer app" for archived data.
Current trends and anecdotal evidence indicate that more traffic managers have taken an interest in developing and maintaining data archives. There appear to be at least two applications that
provide tangible benefits to traffic managers:
• Performance monitoring – helps traffic managers preserve or expand funding for operations; and
• Detector status/health reporting – helps traffic managers diagnose and troubleshoot extensive data collection systems.
Of these two applications, performance monitoring appears to be the most compelling application that is likely to strengthen traffic managers’ interest in developing data archiving systems.
10) Local knowledge contributes to national interpretation.
The lesson learned is that capturing local knowledge is desirable for interpreting system performance at a national level. State and local agencies are likely to be more familiar with highways in their jurisdiction and significant activities or events that have affected system performance. Some State and local agencies may be monitoring performance using other methods or techniques that could confirm or differ from national congestion monitoring results.
Because of their experience with local issues, State and local agency staff may also serve as a “reality check” for data collected in national congestion monitoring. However, this capture of local knowledge is currently, at best, an informal process that involves sporadic communication with State and local agencies.
**Note that this FHWA report can be downloaded in their website.
Subscribe to:
Posts (Atom)