My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Minutes 03/30/1999
Portsmouth-City-Clerk
>
Minutes
>
1990s
>
Year 1999
>
Minutes 03/30/1999
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/30/2001 2:52:38 PM
Creation date
7/30/2001 2:48:57 PM
Metadata
Fields
Template:
City Council
City Council - Type
Adopted Minutes
City Council - Date
3/30/1999
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
11
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
March 30, 1999 <br /> <br />These recommended rate increases will be used to continue addressing replacement of <br />Portsmouth's aging water and sewer infrastructure and to fund preventative <br />maintenance and routine replacements. This upgrading of infrastructure is part of five- <br />year, $25 million renewal and replacement plan of the Department of Public Utilities and <br />is necessary to ensure the quality and safety of our drinking water in a system where <br />almost half of the system is more than 40 years old. <br /> <br />Stormwater Management <br /> <br />The stormwater fee increase will be used toward repair of our aging storm drainage <br />infrastructure throughout the city, as well as development of a Lake Management <br />Program for dredging of lakes and ponds that serve as filters or holding areas for <br />nutrients and sediments. This program is part of mandated federal and state programs <br />that include the Clean Water Act, the Chesapeake Bay Program, and the Tributaries <br />Strategies Program. As a waterfront city with an extended shoreline, Portsmouth has a <br />vested interest in maintaining clean waterways, regardless of mandates, as an <br />economic, esthetic and recreational asset. [Figure 6--Rate Comparison] <br /> <br />Figure 6: Stormwater Rate Comparison <br /> <br />Chesapeake Norfolk Virginia Beach Portsmouth (proposed) <br /> <br />1.75 5.52 3.68 3.30 <br /> <br />These rate increases will help with our backlog, as will the other appropriations <br />mentioned above. Unfortunately, backlog will be with us for some time and will take a <br />steady and dedicated approach to eliminate. We plan to stay the course. <br /> <br />INVESTMENT IN CITY EMPLOYEES <br /> <br />I have said before and I will repeat here: employees are our most important asset. We <br />are primarily a service organization, providing human contact with our customers on a <br />daily basis in a wide range of services, from police and fire protection to recreational <br />programs and road maintenance, from libraries and museums to health care and social <br />services. <br /> <br />For the City of Portsmouth to succeed in meeting and exceeding our customer needs, <br />we must have employees who are carefully selected, well trained, highly motivated, and <br />fairly compensated. For many months we have been working on a new pay plan that <br />must be stable, clear, equitable, predictable, flexible, simple and objective. We have <br />determined that our wages should be competitive in a market made up of the Hampton <br />Roads cities of Chesapeake, Hampton, Newport News, Norfolk, Suffolk and Virginia <br />Beach. We have spent considerable time and effort studying that marketplace. <br /> <br />We are engaged in a multi-year process to ensure that employees are fairly <br />compensated. This process has involved an unprecedented amount of employee <br />communication and involvement on an ongoing basis. We have taken considerable <br />pains to keep employees informed of principles and issues involved in revising the pay <br />plan and in seeking their input and guidance as we proceed. Our goal is nothing less <br />than for our employees to consider this to be their pay plan, and not just management's. <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.