Problem identification includes the description of a traffic safety problem and documentation of data to support the problem. The problem identification cannot be more than 5,000 characters, (approximately a page and a half). Information contained in charts, graphs, tables, etc. does not count towards the 5,000 characters and can be attached on Attachments page.
Note: You may cut and paste data from another system or software program and enter it into eGrants.
Note: Any additional problem identification (over the 5000 characters) that is attached on the Attachments page will not be reviewed and scored by the RFP review teams.
The problem identification description should be a clear, concise, and accurate description of the problem. A strong problem identification description accurately defines the nature and magnitude of the specific problem or problems. Causes of fatalities, injuries, crashes and property damage, site location (city, county, roadway section, statewide), and target population data are important information to problem identification.
The problem identification process involves obtaining and analyzing historical motor vehicle traffic crash data that is relevant to the problem and proposed project to determine the who, what, when, where, how, and why of an existing problem. Accurate and factual information helps create a strong problem statement. Other pertinent data, such as safety belt use, may be included or substituted for crash data. Sufficient data that is both local and as current as possible must be provided to justify the traffic safety problem. The data source and date of the data and information should always be cited.
Examples of problem identification statements:
• Bicycle helmet usage in Hazard County among children ages 8 to 14 decreased from 79% in 2010 to 68% in 2011.
• Adult seat belt usage in Gotham City is only 67% compared to the statewide rate of 90.4%.
• Restraint use for children ages 5-9 decreased from 78% in 2010 to 70.5% in 2011.
Potential data sources include:
• local law enforcement agencies
• hospital and emergency room reports
• Department of Public Safety (DPS)
• State or local surveys or assessments (for example, TTI Safety Belt Survey)
The proposed solution should briefly (5,000 characters maximum) describe the scope of work and activities that will be performed to address the stated traffic safety problem or problems. This may include methods, countermeasures, and strategies that could reduce problem severity or eliminate the problem or increase traffic law compliance. The proposed solution may also detail the “who-what-when-where-how” in order to assist in project evaluation.
Note: Don’t forget to save your work! Click on the Save button.
Note: You can always come back and make changes to a page before the proposal is submitted. Resave the page after any changes have been made.
Note: If you use the spell check, make sure that you re-save the page (if the page has previously been saved).
Objective Statements, including Performance Measures, Targets, and Activities briefly indicate the specific purpose of the project and will provide guidance to determine efficiency and effectiveness of the project, serving as measures of project progress. These activities are necessary to carry out a successful project and will be entered on the “Objectives, PI&E, Performance Measures and Activities” page.
Note: If a Public Information and Educational activity (PI&E) is part of the proposed project, a PI&E objective statement is required.
The proposal must clearly demonstrate proven methods for measuring and evaluating project success. Proposers are to indicate how their organization plans to evaluate the project(s) to prove project success.