Exciting changes in the TIP database now allow you to select multiple Programmers in Advanced Search, the Fund Source Line Items report and the Amendment Reports. Use the standard Shift or CTRL keys to make your selections. Multi-select capabilities will be added to additional fields later this summer. Please direct any suggestions for particular fields or reports where you would benefit from this feature to Kama Dobbs (email@example.com or 312-386-8710).
Some changes were also made to Work Types, primarily to allow CMAP to classify projects as maintenance, modernization or expansion to assist with analysis of the TIP and how projects meet the goals of GO TO 2040. These changes resulted in the addition of new types, particularly for bicycle, pedestrian and transit related work, and the removal of other types. For example, E-BIKE has been split into three work types: E-BIKENEW (new facilities – expansion), E-BIKEIMP (modernization of existing facilities, which could include filling of gaps), and E-BIKEMAINT (maintenance of existing facilities).
Work types that have been removed from the drop-down list can remain on existing projects, however if you're making other changes to a project with one of the eliminated work types, we would appreciate you updating the project by deleting the old type and adding a new type. Eliminated types include: A-FNC, A-OPT, and A-SKIDT (replaced with A-OTH); D-VEH; E-BIKE (replaced with E-BIKENEW, E-BIKEIMP, E-BIKEMAINT); E-PED (replaced with E-PEDNEW, E-PEDIMP, E-PEDMAINT); H-IRS (use H-PATCH or H-RS), T-RELOC; T-EXP and T-IMP (replaced with T-NEWSVC, T-IMPSVC); U-COM, U-POW, and U-SIGS (replaced with U-CPSIMP and U-CPSMAINT); V-MAINT and V-STOR (replaced with V-MAINSTOR); X-RELOC (replaced with X-MOD) and; Z-Museum. New types include: E-BIKEPARK (Bicycle Parking); E-MODE (Travel Demand Management); E-SRTS (for SRTS projects that are not bike/ped); H-RL (Road Diets/Remove Lanes); J-FUEL (Alternative Fuel Vehicles) and; J-RETRO (Engine Retrofits).
A full list of active work types can be found on the Programmer Resources web page. If you would like a list of your projects that currently include eliminated work types, contact Kama Dobbs (firstname.lastname@example.org or 312-386-8710).
The ability to run an "All Projects" style report for a select list of TIP IDs was also added. Select "All Projects Report" from the left-side menu. You can enter a series of TIP ID's in the form on the left – one TIP ID per line, with no commas, semi-colons or other characters, or you can use the filters on the right. Select your sort order for either style of report in the center of the page. As a reminder, the All Projects Report includes only line items that are in the active years (currently 2012 – 2015) of the TIP. Pending TIP changes are not included.
Finally, validation rules were put in place to remind you to enter a total project cost that equals or exceeds the sum of all line items in the TIP. All new projects entered in the TIP must have a total cost. Changes to existing projects will be subject to the validation rule, so you must update total cost when making any change to a project. Remember that total cost should include the cost of all phases, even if those phases are not included in the TIP, or were completed in the past. The total cost field is used to analyze the total investment in transportation in the region.
UPCOMING EVENTS & DEADLINES
Transportation Committee Meeting (4/27/12)
MPO Policy Committee Meeting (6/14/12)
TIP Change Deadline: August IDOT letting (5/30/12)
Transportation Committee Meeting (6/15/12)
TIP Changes for Conformity (7/13/12)
TIP Change Deadline: September IDOT letting (7/18/12)
ITEP Call for Projects
The Illinois Department of Transportation (IDOT) announced it is seeking proposals for the 2012 Illinois Transportation Enhancement Program (ITEP). Approximately $50 million is available for projects. The application form and guidelines are available at www.dot.il.gov/opp/itep.html. Completed applications must be submitted online by May 29, 2012.
Data Entry Reminder – Project Location and Descriptions
Please remember to take care with project location and work descriptions. "Various at various" should not be used to describe a project location. For projects that include various locations, please enter "Various" in the Location field and include some descriptive text, such as "Pavement patching throughout the region" in the Other Project Location Information field. Also, please do not repeat facility information in the Other Project Location Information field.
If you are making a change to a project and receive a "Project violates fiscal constraint for <fund source> in <year>" error, you must resolve the constraint violation before your project changes can be saved. The fund source with the violation may not be the source/year you are trying to change or may not be one that you program, however if your project includes a line item with that source/year, you cannot change your project. When determining if constraint will be violated, the database includes approved projects and pending changes from all programmers. There are several steps you can take to resolve constraint issues.
To determine the scope of the issue, view the fiscal constraint report for "projects in the approved TIP, plus proposed TIP Changes" for the fund source listed in the error message (see this video for help with reports). Look at your balance for the year listed in the error message to determine the balance of funds available for programming in that year. A negative balance indicates that before you can program any additional funds, you must first remove funds in the amount of the negative balance. Negative balances are the result of funding allocations being reduced or other adjustments to the programming marks.
To determine what projects currently include line items for the fund source and year, view the Fund Source Line Items Report for that source and year (see this video for help with reports). If the fund source is constrained "regionwide" (BRR, for example), you should include all programmers in the report. Select "not awarded" projects and "Include TIP changes". From this report you can determine what changes can be made to other projects to resolve the constraint violation.
If you are making a change to an existing change record, it is possible for the database to double count line items because of the way change records are saved. The recommended procedure to eliminate the possibility of double-counting is to delete the existing change record (make sure you have a record of what the changes were, especially if you were not the programmer that made those changes) and then enter a new change for the project that includes prior changes and any new changes you are making. For help with the change form, see this video.
If you are not the programmer of the fund source that has violated constraint or you have questions about the allocations or adjustments shown in the fiscal constraint report, please contact Russell Pietrowiak (email@example.com or 312-386-8798) for assistance.
Projects that include Not Exempt or Exempt Tested work types must undergo conformity analysis. The next analysis period will begin in July. All changes to existing projects and any new projects with Not Exempt or Exempt Tested work types must be submitted by July 13 to be included in the analysis. Any projects requiring conformity and targeting lettings in November 2012, January 2013 or March 2013 must be conformed at this time. CMAP will be coordinating with programmers in the coming weeks regarding projects that include these work types. Questions regarding conformity should be directed to Leroy Kos (firstname.lastname@example.org or 312-386-8780).