My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council Work Session - 08/03/1998
Ramsey
>
Public
>
Agendas
>
Council Work Session
>
1998
>
Agenda - Council Work Session - 08/03/1998
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/27/2025 3:38:54 PM
Creation date
8/22/2006 12:56:58 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council Work Session
Document Date
08/03/1998
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
49
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
<br />,. <br /> <br />The process is designed to be iterative; what is being tried today will undoubtedly be <br />improved upon the next time around. As the process is continually improved and refined, <br />some indicators will be dropped and others will be added. Some definitions will need to <br />be reworked and some indicators won't provide the instght that the TAC members had <br />hoped for. <br /> <br />This project is first and foremost about quality -- determining a process that any local <br />government can use to show it is dedicated to giving citizens the best service as <br />efficiently as possible. As the Consortium work evolves, a process will be developed that <br />will allow jurisdictions to not only compare their own performance from one period to <br />the next, but to also compare themselves with other local governments. <br /> <br />During the two-year effort, we will rely on three major data sources: <br /> <br />. Local government records (both existing records and modifications to current records) <br />. Customer surveys <br />. Trained observer ratings <br /> <br />Although to date the Consortium's work has focused primarily on traditional data <br />collection based on government records, we are also in the formative stages of developing <br />a uniform customer survey . We anticipate that trained observers will be used to gather <br />data further along in the process. <br /> <br />Basically, each Technical Advisory Committee is looking at a wide variety of indicators. <br /> <br />. Input Indicators-- The amount of resources used for a specific program. <br />Examples include data like the number of dollars expended for EMS <br />services or the amount of employee time spent on police investigations. <br /> <br />. Output Indicators-- The amount of completed activity or effort that has <br />been accomplished. Examples include the number of investigations <br />completed, the number of library books borrowed, the number of <br />calls answered, the number of road miles repaired. <br /> <br />. Outcome Indicators-- An outcome is an event, occurrence, or condition <br />that occurs outside the program itself and involves a result that is of direct <br />importance to customers and the public. An outcome indicator measures <br />the amount and/or frequency of such occurrences. There are two types of <br />outcome indicators: . <br /> <br />Intermediate Outcomes-- Those that are expected to lead to the <br />ends desired, but by themselves are not "ends." Examples include <br />response times to police, fire, or complaint calls. <br />
The URL can be used to link to this page
Your browser does not support the video tag.