• Ninety-seven percent of these cities have a citywide plan to address Y2K issues, and for three out of four, that plan was developed by in-house staff rather than by consultants or by other agencies.

 
• All of the cities have designated an individual who is responsible for achieving Y2K compliance; in more than half (53 percent) of the cities, that individual is assigned to the information technology or management information systems agency within city government.

 
• Asked to identify the number one priority for Y2K compliance, the cities named, in order of frequency: emergency response, management information systems, general government administration, the police department, utilities, and taxation and finance.

 
• Asked how many of their computer applications would have to be repaired or replaced, 38 percent of the cities said 10 or fewer, 33 percent said between 11 and 50, 11 percent said between 51 and 100, and another 11 percent reported more than 100. One percent reported that no computer applications need repair or replacement.

 
• All but seven (97 percent) of the survey cities have completed more than half of their computer system assessments, and well over one-third have completed all of them; 79 percent have completed more than half of their system repairs or replacements; and 54 percent have completed more than half of their system testing.

 
• Well over half (54 percent) of the cities have inventoried all of their equipment containing embedded chips, and just under half are relying on in-house staff to resolve the embedded chip issue.

 
• More than two-thirds of the cities are planning to conduct a citywide Y2K test, and four percent of these already have conducted it. 

 
• Forty-four percent of the cities have developed a contingency plan for Y2K "snafues" on January 1, 2000.

 
• Information on funds spent on Y2K compliance prior to FY98 was provided by 168 cities; their spending ranged from $500 to $19 million and, for the group, totaled $90.8 million. Funds for Y2K compliance have been budgeted for FY99 by 139 of the cities; their spending ranged from $1,000 to $32.2 million and, for the group, totaled $164 million. Funds for Y2K compliance have been budgeted for FY00 by 70 of the cities; their spending ranges from $1,000 to $19.9 million and totals $57 million.

 

• For the 136 cities able to estimate their total cost for compliance, the range was $2,000 to $59 million, and the total for the group was $296 million. Of the 200 survey cities which know how they will pay for their Y2K compliance plans, all but one will rely primarily on local general funds.

 
• Asked to identify the system which has given them the most difficulty with Y2K compliance, most cities named, in order of frequency: embedded chips, financial management or accounting systems, utilities, old computer systems, outside vendors or agencies (over which they have no control), public safety, and individual personal computers (PCs).

Because computers have been designed only to recognize a change in the last two digits of any given year, many are incapable of accurately recognizing the year 2000 without modifications in hardware and/or software. If left unchanged, for example, they will recognize the year 2000 as 1900 or 1980, depending on the computer. Worse, embedded chips - devices in sophisticated equipment that control both the date and an important process, such as securing a jail door or activating a power grid - require far more than just reprogramming a computer; they require reprogramming hundreds, even thousands, of microprocessors. With only a year left before the new millennium, these problems, if not addressed, may very well cause many vital government computer systems to fail or become incapacitated.

The survey asked each city:

• whether it had a plan to address Y2K issues and, if yes, how the plan was developed;

 
• who had in-house responsibility for achieving/coordinating Y2K compliance, and to what department the responsible individual was assigned;

 
• the number one priority (e.g., emergency response, traffic management, utilities) for the Y2K compliance efforts;

 
• the number of computer applications identified as needing repair or replacement;

 
• the percentage of system assessment, system repair or replacement, and system testing that has been completed;

 
• whether all equipment containing embedded chips had been inventoried;

 
• who was working to resolve the embedded chip issue (e.g., in-house staff, private consultants, original vendors);

 
• whether a Y2K test was being planned and, if so, when;

 
• whether a contingency plan for Y2K "snafues" on January 1, 2000 had been developed;

 
• how much money had been budgeted for Y2K compliance;

 
• the primary sources of funding for Y2K compliance (e.g., general funds, state grants, federal grants, private sector); and

 
• the system for which Y2K compliance has been most difficult. 

• Ninety-seven percent (211) of the survey cities have a citywide plan to address Y2K issues.

 
• In three-fourths (163) of these cities the plan was developed by in-house staff. In 18 percent (40) of the cities it was developed by private consultants. In two cities it was developed by a regional development agency; in another two it was developed by a state agency.

• All of the survey cities have designated an individual who is responsible for achieving Y2K compliance. In 53 percent (115) of the cities that individual is assigned to the information technology or management information systems agency. In 27 percent (58) that person is in finance or administration. In four percent (eight) of the cities the individual is in the general services department. Among the other offices identified which most frequently house the individual responsible for Y2K compliance are those of the city clerk/ administrative services (five cities) and the city manager (three cities).

• Emergency response was identified by 19 percent (42) of the cities as the number one priority for the city's Y2K compliance efforts. This was followed by management information systems, identified by 17 percent (38) of the cities; general government administration, by 16 percent (34) of the cities; the police department, by 11 percent (25) of the cities; utilities, by 11 percent (23) of the cities; taxation and finance, by 10 percent (21) of the cities; and water and waste treatment, by eight percent (18) of the cities. Other priorities listed are fire services (by seven cities), health and human services (by five cities), roads and traffic management (by two cities), and telecommunications (by one city).

• Thirty-eight percent (83) of the survey cities report that they have identified between one and 10 computer applications as needing repair or replacement. Thirty-four percent (71) of the survey cities said that between 11 and 50 computer applications needed repair or replacement. Eleven percent (24) of the cities said between 51 and 100 applications needed repair or replacement. Another 11 percent (23) said more than 100 needed repair or replacement. Three cities say no applications need repair or replacement.

• The survey cities estimated the percentage of system assessment, system repair or replacement, and system testing that had been completed. The following table contains these estimates.

• Fifty-four percent (118) of the cities report that they have inventoried all of the equipment containing embedded chips; 38 percent (83 cities) say they have not inventoried such equipment; and eight percent (17 cities) did not know whether the equipment has been inventoried.

 
• In 66 percent (138) of the cities, in-house staff is being relied upon to resolve the embedded chip issue. Forty-three percent (90) of the cities are relying on their original vendors. Twenty-two percent (46) of the cities are relying on private consultants. Two cities are relying on a state agency. Many cities identified more than one resource in their responses to this question.

• More than two-thirds (147) of the cities said they were planning to conduct a citywide Y2K test. Four percent (six) of these said the test has already been conducted, between October 1997 and December 1998. Nineteen percent (42) of the cities are not planning a test; officials in 13 percent (27) of the cities did not know if a test had been planned.

 
• Eighty-one of the survey cities said a test will be conducted during 1999. For these, 12 percent plan it for January, six percent for February, 15 percent for March, 11 percent for April, 11 percent for May, 19 percent for June, 11 percent for July, two percent for August, 10 percent for September, two percent for October. None plan to test later than October. 

 
• Seventy-three of the cities do not yet know when a test will be conducted. 

• Forty-four percent (95) of the cities have developed a contingency plan for January 1, 2000 Y2K "snafues;" 51 percent (111 cities) have not. Officials in five percent (10) of the cities did not know if a contingency plan had been developed.

• Information on funds spent for Y2K compliance prior to FY98 was provided by 168 of the survey cities. Of these, eight percent (13) spent less than $10,000; 55 percent (92) spent between $10,000 and $99,999; 24 percent (41) spent between $100,000 and $999,999; and 13 percent (22) spent over $1 million. The amount spent by the cities ranged from $500 to $19 million. For the 168 cities, spending totaled $90.8 million.

• Funds for Y2K compliance were budgeted for FY99 by 139 of the cities. Four percent (six) of these spent less than $10,000; 35 percent (48) spent between $10,000 and $99,999; 45 percent (63) spent between $100,000 and $999,999; and 16 percent (22) spent more than $1 million. The amount budgeted by the cities ranges from $1,000 to $32,200,000, and totals $164.3 million for all 139.

 
• Of the 70 cities which have budgeted funds for FY00, six percent (four) have budgeted less than $10,000; 47 percent (33) have budgeted between $10,000 and $99,999; 39 percent (27) have budgeted between $100,000 and $999,999; and nine percent (six) have budgeted more than $1 million. The amount budgeted for the cities ranges from $1,000 to $19,914,440, and totals $57.4 million for all 70.

 
• Of the 136 cities able to estimate their total cost for Y2K compliance, two percent (three) said it would be below $10,000; 15 percent (21) said it would be between $10,000 and $99,999; 61 percent (83) said it would be between $100,000 and $999,999; and 21 percent (29) said it would be more than $1 million. The estimated total cost for city compliance ranges from $2,000 to $59,000,000; for the 
• 136 cities it totals $296 million.

 
• Of the 200 survey cities which know how they will pay for their Y2K compliance plans, all but one will rely primarily on local general funds. One city plans to use federal funds. Seven cities do not yet know how they will fund the cost of Y2K compliance.

• In response to an open-ended question, the survey cities identified the system which has given them the most difficulty with Y2K compliance. Their responses: 
 
* embedded chips - by 35 cities;

* financial management or accounting systems - by 22 cities;

* utilities - by 18 cities;

* old computer systems - by 18 cities;

* outside vendors or agencies (over which they have no control) - by 17 cities;

* public safety - by 16 cities;

* individual personal computers (PCs) - by 12 cities;

* 911 emergency response - by nine cities;

* payroll and human resource systems - by 10 cities;

* revenue collections - by nine cities;

* telephone and communication systems - by eight cities;

* permitting systems - by three cities;

* traffic signals - by three cities; and

* utility billing - by three cities.

Addison, IL: We are in the process of obtaining compliance letters from all vendors of electronic equipment. We have found only six items so far. One has been replaced already. Three more will be replaced shortly. The final two may not require any attention. We have an ongoing scheduled replacement program for all of our equipment. It appears to have resolved a lot of our potential problems. Organizations that have not kept up with technology are the ones who are going to experience the bulk of the Y2K problems. Those that have may not experience any problems. Our vendors have indicated that some clocks can be reprogrammed to 1972 as a quick fix until the item can be replaced. Apparently 1972 and the year 2000 have the same calendar. Based on what we have seen in our organization, we are not too concerned.
 

Alhambra, CA: During the staff's initial Y2K assessment, it was determined that the City's entire data and network systems needed to be reviewed; solutions in one area necessitated upgrades in the existing computer network. A thorough review of hardware, applications and data networks, in all city departments, has been undertaken. This review will identify what applications exist in the organization, their size, complexity, and components. A city-wide list of critical information systems issues is nearly complete.

Ann Arbor, MI: Except for embedded chips, we have inventoried all of our systems and developed an action plan which includes hiring a consultant to serve as project manager. The individual who is presently performing this function cannot continue to do so effectively as he is the director of a major city department. We have included the development of contingency plans and communicating them to our citizens as part of the comprehensive plan.
 

Athens, GA: We are currently in the last phase of remediation and will soon be in the last phases of testing. The next stop is to finalize contingency plans and develop an action plan for using contingencies should they become necessary.
 

Atlantic City, NJ: Total replacement of mainframe operating system and application software is planned for 1999. PCs and networks are routinely upgraded, and few have problems. The principal embedded chip processor problem is in the traffic control system. A decision is pending regarding need vs. the cost of certification. 

Attleboro, MA: We have basically approached it the way we would approach a natural disaster. The significant characteristic is that we have decided not to form a "team" as a lot of the literature has suggested. We have instead decided that Y2K compliance is the responsibility of each department manager. We have tried to emphasize that this is not just about computers, and it is not just for the "computer people." Once we get that message across, the rest of the process is largely one of vendor management. The area that concerns us the most is processes where we have data that is shared or interfaces directly with data from other non-city entities.
 

Austin, TX: The City of Austin does not expect any major interruptions of service that would affect public health, safety or welfare due to Y2K issues. We expect to be prepared for Y2K by third quarter of 1999. 

Baldwin Park, CA: The City will conduct a Y2K audit and send letters to all the vendors for their equipment or system Y2K certification. We will start at the police department, then public works and City internal systems. We expect to be Y2K ready by the third quarter of 1999.
 

Bayamon, PR: We are ready. Servers (Unix) are Y2K compliant. We are working on Oracle financial and payroll (BBX) Y2K compliance. PCs were verified through a technical program, and the result of that verification was communicated to each department director. We don't know if other equipment (cars, elevators, switchboard, etc.) is Y2K compliant. We hope to complete Y2K compliance by June 1999. 
 

Bayonne, NJ: Bayonne is just completing its assessment phase of our Y2K project. A standing technology committee has been established with representatives of all city departments and agencies participating. Remediation of Y2K problems commenced in December 1998. All systems will be tested for compliance in January and February 1999.

Beaumont, TX: All but public safety software has been replaced or updated to be brought into compliance. Our vendor is trying to get public safety compliant. City staff are helping to identify the problems and should achieve total compliance by June 1999. 
 

Bellevue, NE: All networked PCs, including servers, will have new/upgraded operating systems. All hardware will be replaced or upgraded. Applications will be upgraded or replaced. All data processing Y2K compliance is scheduled for completion by mid-March 1999. 
 

Belleville Township, NJ: We plan to hire a consultant to assess, test and remediate PCs and servers in January 1999. Due diligence letters will be mailed to major vendors in January 1999. We will Introduce a new network and standardize with compliant software. We will create a contingency plan June 1999.
 

Bethlehem, PA: The City had identified all areas affected both inside and outside, and what is in compliance and what still needs to be done to achieve compliance. 

Biloxi, MS: The City's written Y2K plan was delivered December 18, 1998 and included replacement of the existing mainframe system with Y2K compliant Windows NT servers. The consultant expects implementation of Y2K plan by March 1999. 
 

Boise, ID: Accounting Systems are 90 percent complete and will be finished by August of 1999. All City network operating systems are Y2K compliant now. Plans and implementation steps for remediating all City PCs are in place and will be complete by August of 1999. Specialized and individual desktop software problems are unknown at this time. Embedded chip assessment is 90 percent complete. Each department is responsible for this.
 

Bolingbrook, IL: The Village is in the process of developing a more formal Y2K plan. The Village has assessed and contacted vendors for all MIS systems, including hardware and software; the telephone system, including pagers and cellular phones; and miscellaneous finance department MIS equipment systems. Ninety-eight percent of these are in compliance. The systems that are not in compliance are non-critical contingency plans, critical vendors, and embedded chips will be addressed in the formal plan. 
 

Boston, MA: The City of Boston has designed a comprehensive Year 2000 Plan. As part of the plan we have established an Executive Level Year 2000 Oversight Committee consisting of the Chief Operating Officer, the Chief Financial Officer and the Director of the Management and Information Services Department. The Oversight Committee works with the Mayor's Cabinet Chiefs to monitor and ensure the progress of each City Department. Each department head is responsible for the results of the effort in the department. As a supplement, we are organizing function-specific task forces to work cross-institutionally in the following sectors: public safety, facilities, finance/banking, public awareness, information technology and utilities. We have prioritized our mission critical systems and are re-coding, testing and replacing some of these systems. 

Approximately 70 percent of the core applications managed by the Management and Information Services Department have been re-coded to be Year 2000 ready. We are evaluating embedded processors and our external dependencies, with particular emphasis on the public safety departments. We are in the process of interviewing consultants to assist us with our embedded processor evaluation.

Some departments are still inventorying their hardware, software and external dependencies. We expect that these inventories will be completed by January 31, 1999. We have begun preliminary work on contingency plans, meeting with the Boston Emergency Management Agency, Boston Emergency Medical Services, some of the public safety departments, and some state agencies. We have also planned an emergency response exercise for the fall of 1999.

The City's target date for Year 2000 compliance in all computer systems, computer-controlled systems and external dependencies is July 1, 1999. Additionally, the City has identified and appropriated resources for the remediation of Year 2000 items through both the Operations Budget and the Capital Budget as items have been identified. A streamlined procurement process has been identified to expedite replacement hardware and software components necessary for remediation. A centralized Year 2000 fund that will be accessed by individual departments and managed by the Oversight Committee is currently being established.
 

Bowie, MD: The City of Bowie has purchased new hardware and software in all information system areas. A new main system has compliant software in all but one application, and this application has been scheduled for replacement. Personal computers will all be compliant with a software change, and this change is scheduled for the middle of 1999. Our main efforts now are directed to vendors and service providers not controlled by the City.
 

Bremerton, WA: We operate a centralized information system function. Most of our software was developed using UNIX and Informix and has been fixed by the vendor already. We maintain B & O Tax and Utility Billing systems and they need minor work for compliance. We are in the process of replacing our old police records systems. We do not anticipate major problems with PC environments. We anticipate some problems with power and are preparing citywide plans to mitigate the effects of serious power disruption.

Bryan, TX: Currently the internal Y2K Task Force is receiving divisional reports. All testing is to be completed and issues resolved, if possible by June 30, 1999. Contingency Plans are to be completed by each department and ready for implementation by August 31, 1999. Two public forums are scheduled for June and October of 1999.

Buffalo Grove, IL: We feel we are compliant but we continue to look for potential problems.
 

Camarillo, CA: The Year 2000 is of major concern. The City of Camarillo is actively evaluating and updating all of its mission critical systems and services for the Year 2000. To this end the City of Camarillo is in the process of replacing and or updating both hardware and software platforms, with an expected completion date of June 30, 1999.

Carol Stream, IL: We have prepared a Y2K readiness plan and inventory of deficient and compliant systems. The Village does not heavily rely upon automated systems triggered by a date with year format. Based on our initial inventory, very few Village operated systems will be impacted by Y2K. We hope to be able to test compliance efforts, especially as they relate to dependencies with other agencies or organizations, by June 1, 1999.
 

Cerritos, CA: The City's Y2K plan was approved by the City Council on September 10, 1998. Most City operating software is Y2K compliant, with parks & recreation software modifications in progress. Upcoming efforts will focus upon identification of embedded chips and securing letters of cooperation/compliance.
 

Charleston, WV: We have identified all suspect areas and are addressing them individually, internally and through vendors. Testing has begun - so far so good. Major upgrades are needed within the parking system. We are working on that presently.

Cheyenne, WY: We expect to be Y2K ready, except for the water and sewer utility, by May 1999. The police should be Y2K ready by that date also. The water and sewer utility is unsure of the compliance date.
 

Chicago, IL: In November 1996 the City began its work on the Y2K project with a preliminary assessment of the city's mainframe system. In February 1997 the City initiated a Y2K Awareness Campaign and the development of an internal user group. All of the City commissioners (department heads) were briefed on the Year 2000 problem and their roles in helping to address it. Representatives of each department were assigned to the user group to serve as points of communication and accountability.

The City's Year 2000 effort is divided into four primary categories: 1) Information Technology, 2) Embedded Systems; 3) Business Partners; 4) Business Continuity Planning.

Information Technology - The information technology element of the Y2K project encompasses the mainframe, network and PC components of the systems serving the various City departments and agencies. Thirty-five of the City's 42 departments have applications that reside in the mainframe environment. At this time, all mainframe applications have been assessed for Year 2000 compliance. The preliminary mainframe assessment was completed in late 1996. In January 1997, the City completed an initial determination regarding the disposition of affected systems, and slated many of the Y2K-compromised systems to be replaced with new technology rather than renovated. The City expects the replacement, installation and follow-up activities for those mission critical systems to be completed in the second quarter of 1999. The City began remediation and follow-up work to be completed by the second quarter of 1999. The City began remediation activities for mission critical applications which was not replaced in the fall of 1997 and expects the remediation and follow-up work to be completed by the second quarter of 1999. The City expects renovation or replacement of applications which are not mission critical to be completed by the third quarter of 1999.

The distributed computing environment, or network, is comprised of approximately 10,000 PCs, midrange servers and communications devices. The City completed the assessment of the distributed network in May 1998. All PCs, servers, communication devices and printers were inventoried and assessed for compliance. Additionally, server software was inventoried and assessed. Replacement or remediation of non-compliant components began in the fourth quarter of the 1998 and continues through the first quarter of 1999.

Embedded Systems - The scope of the City's Y2K effort for embedded systems includes operational systems for the City government's primary buildings, vehicles, water purification and distribution, transportation infrastructure, emergency services and other services. The City is retaining a consulting firm to manage and implement the remediation of the City's embedded systems. The City expects this consultant to begin work in December 1998. The city has conducted a preliminary inventory of the embedded systems. The City expects the inventory to be completed by the end of the first quarter of 1999 and the City expects repairs of embedded systems to be completed by the third quarter of 1999.

Business Partners and Vendors - The city is also working to mitigate the risk of Y2K problems arising from dealings with its business partners and vendors. The City is investigating the Y2K compliance of its critical vendors and suppliers in order to reduce the risk of disruptions in the City's supply chain. The City has begun this investigation which will continue into the second quarter of 1999 and beyond, if necessary. The City has retained outside counsel to coordinate this effort and any follow-up efforts that may be necessary.

Moreover, the City plans to communicate with public and private enterprises in order to study societal issues beyond direct responsibility of the City. Examples of those entities which may be involved include banks, real estate concerns, utilities and transportation authorities. Additionally, a cross-agency task force has been established to share information, techniques and status across various levels of non-city government and public agencies.

Business Continuity Planning - In October 1998 the City began a business continuity planning process to identify and assess the Y2K contingency risks that may affect each of the City's departments. Through this process, which is being managed by the Year 2000 Project Management Office, the City will be able to develop plans intended to make it possible for the city's departments to continue their operations even if Y2K problems arise. The process will identify and assess internal and external Y2K risks from computer-related technologies and from supply chain relationships, prioritize those risks and develop plans to mitigate those risks. The business continuity planning process will continue throughout the life of the Y2K Project, however, the City expects the principal work of the process to be completed by July 1999.

Finally, the City has devoted and will continue to devote significant resources to addressing the Y2K problem, and has allocated funds that it believes are appropriate under the circumstances.
 

Chino, CA: During the final quarter of 1998 the City performed a comprehensive assessment of all potential Y2K problems. In January 1999, the City is replacing finance management information hardware and bringing finance software into compliance. This will be performed by outside consultants. By July 1999 all other systems will have been upgraded or replaced. These are more minor in nature than the finance system.

Cicero, IL: The personal computers owned by the Town of Cicero are currently being tested for Year 2000 compliance. If any PC fails the testing phase, the hardware will be scheduled for replacement in 1998-1999 time frame. A similar effort is underway relative to PC software utilized by the Town's PC users. The main computer system, an IBM AS400, has just recently been upgraded to a Y2K operating system. In addition, all software currently running on the AS400 is being tested for Year 2000 compliance. No major problems have been encountered nor are anticipated. Concurrent with the ongoing testing will be the implementation of newly acquired software to upgrade and to add new functionality to the Town's billing system. This should all be completed by December 1999.
 

Claremont, CA: The Year 2000 City Wide Task force was created in mid-1998. A detailed identification of all affected equipment and software was conducted. Each piece of equipment and software was classified into Year 2000 compliant, not compliant and unknown. All non- compliant items have been scheduled to be repaired or updated by mid 1999. Unknown items are now being tested or classified for a further determination. The final status is anticipated to be done by Spring 1999.
 

Clovis, NM: The City of Clovis has finished the assessment of all of its computer systems. We feel we are approximately 90 percent compliant. The systems that comprise the 10 percent are the finance, emergency preparedness and telephone systems. The finance system is scheduled to be completed by April 1, 1999. The emergency preparedness systems does not have a completion date as yet. The telephone system is scheduled to be completed by February 1999.

College Station, TX: Our City has done it's best to identify and fix Y2K problems. We have contacted vendors, we are in the process of testing, and we are optimistic that we have covered all systems for our critical services. Just like everyone else, we will only see the final test in January 2000.
 

Columbia, SC: We are about 80 percent complete with our older systems. These will be completed by April 1999. This includes testing of each system. Our emergency response system is being replaced before July 1999. We have some stand-alone PCs that will be replaced in the 99-00 budget, but this are not critical to our operation as they are only office automation-type stations. Our traffic light control system is not compliant, but it works with the day of the week so the department has determined they will roll the date back, and the system will work fine. The water and sewer plants have been verified.
 

Columbus, GA: We are in good shape for Y2K. We purchased a new mainframe system in 1996 with new operating software and it was compliant when purchased. We have been working on correcting our systems developed in-house since the early 90's. All new development since 1994 has been Y2K compliant. Our financial and human resource/payroll systems are packages and have been compliant since July 1998. Our property tax system is also a package and the new Y2K version will be implemented in March 1999. Our court tracking applications and police applications were developed in house and are 50 percent complete for Y2K compliance. We have 12 personal computer networks and all are Y2K compliant. Ninety-five percent of our personal computer inventory is Y2K compliant and the other five percent will be replaced in the FY-2000 budget. 
 

Concord, NH: The majority of our systems were upgraded prior to FY99 when we replaced our financial system, office products software and wide area network. We have recently completed a preliminary survey of remaining systems and are receiving status reports from vendors. Tests of systems are being conducted and others scheduled. Contingency plans will be developed accordingly.
 

Corvallis, OR: Some of the software and hardware upgrades which will make us Y2K compliant were planned anyway as hardware and software age. We have completed our assessment and the City's major systems have been certified Y2K compliant. We do not plan to test all systems but will rely on testing done by other cities. We expect to be Y2K ready by June 30, 1999. The FY 99-00 budget primarily includes funding for contingencies to respond to unforeseeable difficulties.
 

Covina, CA: The City is taking all necessary steps to bring all information technology-related software and hardware Y2K readiness. This included the acquiring of a new financial system to purchase upgrades to existing software. 
 

Culver City, CA: We recognized that our information technology infrastructure was outdated, and had significant Y2K issues. We decided to replace our entire infrastructure. 
 

Daly City, CA: We are finishing a city-wide inventory of systems. Main and desk-top computers will be compliant by the first quarter of 1999. All testing will be complete by the second quarter of 1999.

Davenport, IA: Our date fields are stored correctly in all databases. Operating systems have been upgraded to the latest version for UNIX systems. PCs are being worked on now, updating BIO chip and Windows 95 & NT operating systems. The final report will be delivered by the consultant in mid-December 1999. 
 

Davis, CA: The systems we are replacing are obsolete and needed to be replaced regardless of Y2K. The bulk of our systems are vendor certified. We are identifying embedded chip systems and developing contingency plans ("work-arounds").
 

Daytona Beach, FL: New application software has been purchased from Creative Computer Solutions in Pleasanton, CA and implementation of the conversion has begun and will be completed before October 1999. New public safety software has been purchased from Lucent Technologies of Lyle, IL and the conversion and training will begin in January 1999 and be completed before October 1999. New mainframe equipment, DEC Alpha has been purchased and just installed to run the new application software. Three-hundred ninety-one personal computers were leased to upgrade the computers being placed on a new citywide computer network installed in May 1998. 
 

Des Moines, IA: Application conversion is 99 percent complete. Desktop replacements are 80 percent complete. Major system review and correction testing are 80 percent complete. Embedded system assessment is 50 percent complete. All system tests and other activities are due for completion by July 1, 1999. Our contingency plan is due July 1, 1999. 
 

Detroit, MI: To address Year 2000 problems the City has been actively assessing, preparing and executing a Y2K readiness plan. Each City department or agency is conducting a business assessment and developing contingency plans to minimize areas that may affect service continuity.

The City has committed human and financial resources to implement the City's Year 2000 compliance system. To date, the city has spent over $4 million on its year 2000 compliance program. To implement the program the City has assembled a team of information systems professionals, business analysts and users, and managers. This team has performed the following Y2K tasks: 1) promoted awareness of Y2K issues to all City departments and agencies; 2) assessed and created inventories of hardware, software, operating systems, and EDI interfaces with the City's own systems, as well as with business partners; 3) developed and implemented plans to solve Year 2000 issues; 4) submitted biweekly status reports and analysis of Year 2000 progress to executive management; 5) initiated Year 2000 corrections and modifications; 6) instituted quality assurance validation and testing; and 7) implemented Year 2000 ready systems.
 

Dothan, AL: We have completed our assessment, purchased our replacement software and hardware, and are in final stages of installation and testing. We should be complete by June 1999 at the latest. 
 

Elizabeth, NJ: Major systems are compliant now; hardware is systematically assessed and replaced.

Elk Grove Village, IL: Some municipal applications were unable to process transactions correctly due to only using a two-digit year. In addition, the bios utilized in many microcomputers (PCs) were not compliant. The Village has tested its systems and is replacing those items found to be non-compliant. The original focus was upon mission critical applications. With those resolved, non-critical but necessary functions are being updated. The largest concern is the mission critical readiness of suppliers, including public utilities.
 

Elmira, NY: Critical applications - public safety and integrated financials - are year 2000 compliant. Patches to Compaq hardware & windows NT software must be applied when available. PCs and local application need to be assessed for appropriate remediation. The project is currently active and we expect to be confident of compliance in the second quarter of 1999. 
 

Elyria, OH: The main hardware systems (two AS/400 & one Hp 3000) have been updated to be Y2K ready. Y2K applications have been purchased for utility billing and financial issues. They have been tested and are in use. Modifications to these applications have been made and are currently being tested. Modifications are scheduled to be phased in during the last quarter of 1998 and the first quarter of 1999.

Traffic lights, communications, water treatment, and waste water treatment have run tests and are Y2K ready, and their vendors have certified as Y2K ready. Police, city jail and fire service systems have been tested and vendors have certified as Y2K ready. Local private utilities have been contacted and are Y2K ready or are scheduled to be Y2K ready. We are continuing to attend seminars to learn of other testing that may be required, or of what other problems may exist.
 

Enid, OK: The City has tested its mainframe computer, file servers and individual PC hardware. We have identified computers that will need to be replaced and operating systems that will require an upgrade. We are still exploring some custom software applications for Y2K compliance. We have completed an initial inventory of embedded chips and plan on auditing various departments. The next major step is to meet with local utility providers and major suppliers to determine the status of their Y2K compliance. We believe that we will have the City's overall exposure assessed by mid-February. We will then spend the rest of the second quarter of 1999 developing strategies and testing scenarios.

Everett, MA: We have tested and identified peripheral devices which need updating. We have just completed the installation of a LAN which is Y2K compliant. We have just awarded a software contract that will make all of our municipal functions Y2K compliant and will be on-line by March/April. All new construction in the city is being certified by the appropriate vendors to be Y2K compliant.

Fairfield, OH: We are currently reviewing all systems and subsystems for compliance. We are then going to maintain a file and description of all results for public perusal. We expect to have all systems either upgraded or replaced by September 1, 1999. 
 

Farmington Hills, MI: The inventory is completed, system assessment is almost completed, priorities have been established, testing is being implemented along with replacement of known problems. The first quarter of 1999 priority is communicating our status to the public and increasing the public awareness of our residents. The media will make or break this issue.
 

Findlay, OH: We are 95 percent done, expect to be complete in April 1999.

Flint, MI: A strategic implementation plan has been developed and is in the process of being implemented by in-house information services staff together with consultants hired on an as needed basis.
 

Fontana, CA: Financial systems assessment is almost completed, some areas have been verified compliant by vendors. Telecommunications & embedded systems are in the inventory and assessment phase. Most of our systems have been replaced or are contracted to be replaced by Y2K compliant systems in 1999. 
 

Fort Wayne, IN: The Y2K project was initiated in 1993 with the Technology Application System Replacement Project. A large majority of systems are Y2K compliant from vendor remediation of applications, which are scheduled to be compliant at end of the first quarter of 1999. 
 

Frederick, MD: Inventory and assessment are complete. The remediation strategy is complete. Prioritization is complete. Most testing will be done by third party software vendors.
 

Freeport, NY: Our network equipment is less than two years old and Y2K compliant. All other suspected equipment has been inventoried and a Y2K plan has been developed.
 

Gainesville, FL: We are essentially completed, although two minor systems (fleet and legislative tracking) won't be on-line until April or May 1999, due to continuing possible PC-related failures. 
 

Galveston, TX: We are in the process of converting from NCR to Windows NT with Y2K compatible software. All systems will be on NT by December 1999. 
 

Garden City, MI: We are concentrating on the assessment of City-owned equipment and secondarily on the key vendors that supply goods and services to the City.

Grand Forks, ND: As of December 31, 1998, we believe we will be compliant by July 1, 1999. At this time we are moving into emergency management planning for the community and into community awareness.

Grand Prairie, TX: The mainframe running two applications (financial management and human resources/payroll) is 100 percent compliant. The AS/400 is compliant. The customer service system is 80 percent complete. The hardware within our PCs are 100 percent compliant. The PC software will be compliant by October 31, 1999. The LAN/WAN network is 20 percent compliant and will be completed by February 25, 1999. 
 

Grand Rapids, MI: The City of Grand Rapids completed a Y2K assessment in January 1997. 

The City identified computer systems which were and were not Y2K compliant. The non-compliant systems were prioritized and work began on ensuring Y2K compliance within existing financial resources. The City's implementation will be completed by April 1999. Full testing has begun and will be completed by September 1999. The City of Grand Rapids has empowered each operating department to evaluate and remedy any and all systems within their jurisdictions which are not Y2K compliant. Staff meets on a regular basis to discuss this singular topic and this subject is discussed weekly by the City Manager and his executive team. The City of Grand Rapids is very proactive in addressing the Y2K issue.
 

Great Falls, MT: A Y2K Task Force has been established and is actively working on the issues. There are two pieces of Y2K: internal systems and the impact on providing services to the community. Our committee is concentrating on developing contingency plans if services to the community are impacted by Y2K. The Internal systems are being left up to the individual departments and the Information Services Department for computers. The committee did however, raise awareness in the departments on dealing with the issues. 

Our contingency plan is being developed in three tiers: Tier 1 assumes the power outage is minor and no additional City funds will be needed. Tier 2 assumes a moderate outage and our plan of contingency would require using funds from the existing budget. Tier 3 assumes a serious power outage and our contingency plans require additional appropriations.
 

Greenfield, WI: The City is in the process of replacing the non-compliant software with a package. The package has been purchased and is being phased into production. The expected completion date is October 1999.

Greensboro, NC: Most of our critical computer systems, such as finance, human resources, police case management, utility billing, etc. were developed and are supported in-house using City staff. We surveyed those systems in 1996 and made the decision to modify storage of all dates to include century. Actual work on upgrading the systems started in 1997. We have completed and implemented the entire financial system and the building permitting and inspections systems. From January through June of 1999 we will be upgrading the human resources, police and utility billing systems. Our target date for a citywide computer system test will be in July of 1999.

The embedded chip issue is much more uncertain for us because the Y2K issue was largely considered a MIS issue until last year. We've done little to estimate our exposure for control systems that may contain the embedded chip issue. We are currently negotiating with an engineering consulting firm to examine all City control systems for Y2K compliance.
 

Greenville, MS: We are upgrading and replacing old PCs. We are in the process of replacing our mid-size NCR System with a Unisys NT server. All of our applications will also be replaced on the new system. This includes general ledger, cash receipts, utility billing, utility route, budgeting, budget preparations, grant administration, purchasing, bid administration, accounts payable, human resources, payroll, GeoBase, fixed assets, accounts receivables, work orders, project management, fleet maintenance, inventory, permit, inspections and privilege license.
 

Greenville, SC: We feel comfortable that our computer operations will be compliant ahead of schedule. We are now assessing other systems with embedded chips. We are less sure about them.

Hamilton, OH: Our consultant firm (RMI) is currently completing inventory and assessment. 
 

Hampton, VA: Ninety percent of our computer systems have been replaced or are scheduled to be replaced by the end of March. We are currently performing an inventory of embedded chips, which will be completed by January 1. We expect to be Y2K ready by June 1. 
 

Harrisburg, PA: Harrisburg has understood and recognized the Y2K issue for some time, and work is well along in addressing it. All city agencies have done their inventory. Repair or replacement plans for each compliance need were prepared and are being implemented. Most corrections have been made. In some instances, replacing PCs is the solution, although in most instances they need replacement anyway. Overall supervision of plan implementation is handled by the City's Bureau of Data Processing in the Department of Administration, where full-time programmers have been hired to perform such tasks. 
 

Hayward, CA: The City's mainframe applications (general ledger, utility billing, budget, etc.) are estimated to be 80 percent compliant. Only payroll remains, and it will be upgraded in fiscal year 1998-99. Other major areas such as public safety, library, and public works are well along in the inventory process. Programs will be upgraded as necessary in 1999. Contingency planning will be completed in 1999. 
 

Henderson, NV: We have been working on our major systems since 1997 either fixing or replacing. We began looking at the embedded chip issues in the second quarter of 1998. We are scheduled to have all critical software systems Y2K ready by June 30, 1999. We are also planning on having checked critical embedded chips by June 30, 1999. We plan to have our contingency plan in place by June 30, 1999. After that date we will be looking at fixing any problems that arose from testing of critical systems and if not then looking at less critical systems. The key is to start with your critical systems first defined as those that could impact public safety, delivery of essential services (water especially), etc. After that work, we will work on less critical systems and make sure we have our contingency plan in place as soon as possible. We are on schedule for June 30, 1999 to implement our plan.
 

Hendersonville, TN: We are in the process of going through all systems and receiving verification from vendors that we can't test....We expect to have a clear understanding of our condition by March 31,1999.
 

Highland Park, IL: The City of Highland Park began its Year 2000 project in September 1998. The initial phase has been an inventory of all electronic equipment and software. The assessment was completed by the end of December 1998. Through the first quarter of 1999, the City will repair and replace any equipment or software that is not Y2K compatible. By April 1999, the City will test all of its operating systems. We are planning a testing procedure to make us comfortable with our ability to operate on critical dates, such as September 9, 1999. By August 1999, an emergency management program on Year 2000 issues will have been conducted to insure infrastructure and mental preparedness. Highland Park intends to be in full compliance to the best of our knowledge and abilities by December 31, 1999. 
 

Hillsboro, OR: We will be replacing our current Unix OS with SCO Unix which will fix the Y2K issue with Unix. We use all Microsoft products and we are following Microsoft's guides for addressing Y2K issues with any of their products.
 

Hilo, HI: We began working on Y2K in 1997. Due to the large variety of systems and applications in use by the county government (2,000 employees), we are in various stages of Y2K work . Some systems and applications have been upgraded and tested while others are in progress.
 

Huntington, WV: We are currently assessing our needs for a new computer which we plan to have on order after the first of the year. We are also assessing a new payroll package which we also plan to purchase with the new computer. All of our accounting software is already Y2K compliant. We will begin testing our in-house programs as soon as we have the new computer in place.

Huntsville, AL: The City is on schedule to complete this effort by June 1999. A city (community)-wide contingency plan for Y2K will also be developed starting in January 1999. 
 

Hurst, TX: The City organized a Y2K committee in late 1996. Plans were developed for assessing, testing, replacing or repairing. The assessment is complete. Replacement or other remediation is not yet complete, but all systems have been addressed. August 1, 1999 is the target date for 100 percent compliancy on all major systems. Most systems will be rededicated by the end of the first quarter of 1999.

Irondequoit, NY: The Town of Irondequoit replaces computer hardware every three years. By the year 2000, our oldest equipment would have been purchased in 1997. So far, approximately 50 percent of our hardware systems have been tested for Y2K compliance. Of those systems, all are Y2K compliant. Most of our hardware will automatically adjust for the Year 2000. Approximately 10-15 percent of our hardware will have to be manually set for the date change. The Town should be prepared for Y2K adjustments by March 1999.
 

Irvine, CA: The City has been running on obsolete equipment and we are in the process of replacing all of the mainframe equipment with client server. This replacement makes it impossible to divide out what are Y2K costs and what are basic technology upgrades. We have a complete assessment and are actively working on Y2K compliance in conjunction with upgrading the City to state-of-the-art technology. The City has a strategic technology plan which takes us through 2003, however our Y2K compliance will be completed by mid 1999.
 

Jefferson City, MO: Payroll is complete; the rest is to be worked on.

Kettering, OH: We feel that we are already well prepared. We started a year ago examining systems and most of our computer systems are less than three years old. We are mostly concerned about embedded chips and have a committee looking at this. We should be Y2K ready by June.

Kansas City, MO: We have 1) Y2K departmental coordinators and monthly meetings, 2) a Y2K oversight committee, and 3) Y2K integrated into our FY2000 budget, and are currently forming a Kansas City metro area Y2K group under MARC. 
 

Key West, FL: The City of Key West is currently undertaking the following actions as they relate to Y2K compliance:

1. Evaluating all computer hardware and software;

2. Evaluating, on the level of individual City departments, all electronic equipment;

3. Establishing a contingency plan for potential system failures;

4. Examining all City contracts and bids for vendor Year 2000 compliance;

5. Working with community institutions, including the Chamber of Commerce and other public utilities, by sharing Year 2000 compliance information.

La Crosse, WI: With the exception of less than a dozen areas, the City of La Crosse as far as we can tell will be Y2K ready. Hardware and all major operating equipment have been successfully tested. Equipment that is not compliant is slated for replacement. We hope to be ready by June 30, 1999. 
 

Lafayette, IN: We have identified two software packages that are not Y2K compliant. The estimated time for manufacturers' fixes is too far into 1999, so the City of Lafayette chose to replace those two software packages and the hardware running the software. Both replacements are fully tested and certified Y2K compliant. Installation of one package will begin before the end of the year and be completed by October 1999; the other will begin and end in the first quarter of 1999.
 

Laguna Niguel, CA: 

City Computer Network Infrastructure:

The City has completed an inventory of computers and software within its computer network infrastructure and has determined that 41 out of 66 computers are not fully Y2K compliant. Also, the inventory of software identified many applications that have not yet been determined to be compliant. In regards to the non-compliant computer issue, the City has budgeted $37,500 to replace 15 to 20 of the older PCs in FY 98-99 and had anticipated that the balance would be replaced through an appropriation in FY 99-00. The City has budgeted $10,000 for computer software and supplies which is available for upgrading the Corel Suite 7 Professional programs to Corel 8 at an estimated cost of $5,000. The cost of the initial Y2K assessment and the cost to apply patches or upgrades to equipment being retained and purchased is estimated at $45,000. 

With the increasing demand by companies to replace older computers in the upcoming calendar year, the City may need to reschedule the purchase of computers to occur in the early part of 1999 as it may become difficult to get computers later in the year. This would allow the City to be compliant by the end of June, 1999.

Other City Issues:

Phone system - The City's current phone system has been determined to be non-compliant and bids have been received to replace existing PBX equipment.

Accounting system - compliant.

Payroll system - compliant.

In-house Complaint Management system - compliant.

Facility & Registration system - have received software upgrade from vendor

Critical Business Partners:

The City is a contract city and relies on private vendors and other governmental agencies (Orange County Sheriff, Orange County Fire Authority) to provide critical public safety services to its residents. The City is continuing to monitor the progress of all critical business partners to ensure that they are actively involved in addressing Y2K issues.
 

Lakeland, FL: Major Applications Software: The City has corrected code and replaced or acquired all applications software needed for Y2K compliance. The purchase of replacement large application packages represents our largest Y2K compliance costs to date. All mission critical legacy systems which we will continue in use beyond the year 2000 have been remediated and tested.

Vendor Compliance: Letters have been sent to all critical vendors and trading partners identified by City departments seeking compliance statements or intentions. Responses have been mixed and very vague in some instances.

Embedded technology in process control systems has been the most challenging area to prove compliance, but most critical systems are "vouchsafed" or under remediation at this time. Because of the ubiquitous nature of embedded technology, there is uncertainty that all such chips will be identified, tested, and replaced if necessary.

Each department has been placed on notice to develop contingency plans for each automated system, service or supply source, or process control system which cannot be proven to be Y2K compliant by July 1, 1999.
 

Lake Oswego, OR: Major tasks have been identified and due dates established. The hardware and software inventory has been completed. Each individual PC will be tested prior to February 1, 1999. Office automation software (word processing, spreadsheets, etc.) is believed to be Y2K compliant; this will be verified by testing. Vendors for all the City's databases have been contacted; systems which are not compliant are either being upgraded or replaced. The City's most critical system is its financial system, which runs on our county's mainframe; it's not compliant and is being replaced by the county. It will be operational by December 1999. Validation and testing will be accomplished throughout 1999, with the largest and most critical systems being tested first.
 

Laredo, TX: The City of Laredo prepared an action plan and began implementation on December 1, 1998. We have been working with the Y2K problem since July 1997 and plan to have full implementation by the end of March 1999. This plan was prepared by city staff in an effort to address the challenges of the Y2K problem and as such take action to avoid and mitigate the effects of Y2K.

It was initially anticipated that full compliance would be achieved by December 1998, but due to the complexity of Y2K issues it was decided to delay our completion date to March 1999.

A detailed inventory and assessment of personal computers and critical systems was initiated; which included elevators, security systems, environmental controls metering systems and embedded logic. The results indicate that a minimum number of installed embedded systems have a microprocessor, very few are date-sensitive and those that do have date logic already process new millennium dates correctly. Corrective measures are well underway and contingency planning is in place for those systems that need remediation. Inventory assessment of business applications and vendor supplied software was also initiated. The business applications programs and computer systems are year 2000 compliant. The City of Laredo is committed to provide uninterrupted service prior to, during and after the new millennium.
 

Lauderhill, FL: The City is replacing hardware and software to gain functional improvements as well as address Y2K. Hardware replacement is almost complete, with some older personal computers to be tested and replaced as required. Software replacement is about 50 percent complete. The scheduled completion date for conversion and Y2K readiness is October 1999. Embedded chips testing is not complete and a date has not yet been set.
 

Leominster, MA: Y2K issues have been addressed on a department level so far. IN FY99, a Y2K committee with outside consultants will identify remaining issues and plan for full Y2K compliance no later than the fall of 1999. Key systems -- financial, collection, tax and assessing - are Y2K updated at this time. Full testing for compliance of these will be done by June 30, 1999, with remaining systems to follow. 
 

Lincoln Park, MI: The assessment will be completed by January 31, 1999. At that time a budget will be presented to the Mayor and Council. It is our intent to repair and/or replace all equipment by July 31, 1999.

Livonia, MI: We started working on Y2K three years ago by upgrading our tax systems. This past year we upgraded all of our financial systems. We are now working on permits. The public safety area has lagged behind the City Hall. They recently have completed their inventory process and have upgraded several of their systems. Outstanding issues are digital radio systems, CAD, and records keeping. All of these systems are scheduled for upgrades and testing by June of 1999. We have upgraded our generators this year as part of our contingency planning. Detailed contingency plans are just now being made and will be completed by late spring of 1999.
 

Lynn, MA: The City has received compliance letters from all third party vendors. The City has also upgraded its hardware to be Y2K compliant and is currently working with a consultant to make sure that the network environment is sufficient to accommodate the demands of the Y2K conversion.
 

Madison, WI: The City has broken the Y2K project down into three broad categories:

1. The traditional computer systems for which information services has responsibility. These are the mission critical applications. Over the past few years, the City replaced both of its mainframes with a wide area network of servers and PCs and, in so doing, attempted to insure that all software which was written in-house or purchased was year 2000 compliant. In spite of that, there is a project team which will be doing quality assurance testing. In addition, we will be testing the network infrastructure including PCs, servers, and the telecommunications equipment which runs the wide area network.

2. Software which may have been developed by individual City agencies which are smaller, stand-alone, and non-mission critical. We are assisting these agencies in identifying and remediating any problem areas.

3. Embedded chips in other types of equipment, e.g., elevators, building security systems, etc. We are working with each agency to inventory, assess and remediate where necessary.

Manhattan, KS: We are hiring a consultant in January of 1999 to assist the Y2K Committee. We have begun a Y2K inventory. All software is Y2K compliant.

Martinez, CA: Most systems have been checked and have been updated or are being updated. PCs over two years old will be checked and if not Y2K compliant will be replaced, or BIOS upgraded. All programs are being converted or replaced. The HVAC program is being upgraded. Phone and voice mail have been upgraded. The water system is Y2K compliant.
 

Minot, ND: The City of Minot has an in-house committee reviewing all aspects of Y2K. We feel that we are ahead of schedule and expect to be ready for year 2000 by September 1999.

Miami, FL: Applications are being modified one system at a time. The system is tested; parallels are performed where possible; the code is moved to production. The entire production environment will be tested simulating Y2K rollover when a new mainframe is installed. Conversion is scheduled for completion in July 1999. 
 

Minneapolis, MN: Departmental Y2K projects are proceeding across all city operations and are being coordinated through a city-wide Y2K program office. The overall priority is to identify, fix, and test all "life and safety" related systems and to complete this effort by October 1, 1999. 

Minnetonka, MN: The City staff has been working since April 1998 to ensure that all City systems are year 2000 compliant, and the City is well on its way to reaching its compliance goals. We expect the year 2000 project to be an on-going process, and many testing and upgrades to systems have already been accomplished. The City of Minnetonka is committed to continuing its excellent service to our residents, and we expect all of our systems to be compliant by June 1999.
 

Missoula, MT: All applications are now Y2K compliant; known bugs are identified; hardware is Y2K compliant. We are building a priority readiness plan to address the effect of outside influences, and a department by department contingency plan is in the works. It is due in the first quarter of 1999. 

Mt. Lebanon, PA: We expect to be done by July 1, 1999. We have gone through the inventory, assessment, and repair/replace/remove phases. The changes so far seem to be working. Rigorous testing begins in January.

Murray, UT: The Murray City Corporation started Year 2000 awareness, assessment and review efforts in late 1995. We have identified the impacted areas and prioritized areas of remediation according to scope and severity of impact. We have been actively engaged in on-going assessment, remediation, testing, and implementation efforts ever since. Murray City is making every conscious effort and diligently pursuing every avenue for Year 2000 compliance that is feasible. We believe Murray City will substantially achieve most definitions of Y2K compliance by our goal date of September 30, 1999.

The greatest percentage of risk has been addressed and remediated by software renovation or replacement and hardware replacement. The remaining elements of unknown quantity and cost are embedded devices or chips. Through the assessment activities completed thus far, we believe this risk is small in numbers of affected devices. However, the effect of non-compliant devices not yet found is unknown both in cost and scope of impact.

Murray City is also upgrading electrical, water and sewer control and distribution systems to be Year 2000 compliant.
 

Nacogdoches, TX: The City of Nacogdoches is making every reasonable effort to protect the integrity of its information systems and to bring all systems into compliance for Year 2000. Due to staff time constraints, the City engaged a technology firm to assist in the assessment of its information systems. The City has completed an inventory of its computer systems, including hardware, operating systems, software applications, and interfaces. Replacement of non-compliant hardware has been completed. Police and fire emergency services, and water distribution systems have been replaced and/or updated. In conjunction with the City's application software vendor, all software upgrades are scheduled for completion by the summer of 1999. Barring interruptions from second party suppliers of services, which are beyond the control of the City of Nacogdoches, there should be no interruption of municipal services.
 

Napa, CA: The City has almost completed the upgrading of all in-house programs, which includes almost all of our operating systems (payroll, accounts payable, labor distribution, recreation sign-ups, etc.). We have some embedded chips out there that we are researching, and we have a traffic control system that we think we might have to replace because it's too old to fix. We've replaced most of our PCs and the mainframe (AS400 RISC). Now we only fear the unknown.

Newport News, VA: Embedded Chips - We are in the process of taking an inventory of all mission critical systems that may contain an embedded chip which are located in our city owned buildings. We have also looked at embedded chips in vehicles and other equipment and at this time have no evidence that our vehicles will encounter Y2K problems.

Norristown, PA: New financial software and trash software has been purchased and should be installed in the first quarter 1999. Our consultant has replaced network software with that which is 2000 compliant; tickets are compliant; property tax should be compliant shortly; payroll is compliant.
 

North Las Vegas, NV: We are currently 1) installing a new city-wide switched gig-ethernet network utilizing a fiber networked backbone to 100 Mbps at desktop; 2) replacing 250 of 450 PCs, with the balance planned to be changed during the first quarter of FY 2000; 3) replacing finance, human resources and payroll software with Oracle products (Oracle database is the City's new standard.); 4) undertaking Unisys hardware upgrade and conversion of selected customized software; and 5) replacing the City Clerk's record management system, water utility billing, water operations management systems, GPS and AutoCADD systems. The network installation is due to complete in December 1998. Finance, human resources and payroll software integration are due to be complete in June 1999. RFP's for the City Clerk's record management system, water utility billing, and water operations management systems are due to be released by February 1999. Detention, court and police systems are being worked on by their respective departments; selection and implementation schedules are not available.
 

North Miami, FL: We plan to be ready June 1, 1999. The City has reviewed PCs and software and is making corrections where needed. 
 

North Providence, RI: Software supplier and operating system providers have developed solutions to Y2K already. Custom programs must be adapted to our application. Most applications on the main frame are with a single source provider. Minimum programs are patching, and dumping is done. The Town's application provider has already installed Y2K compliant upgrades which are functioning in other communities.

Novato, CA: The plan is developed and implementation is underway. We will be Y2K ready by September 1, 1999.
 

Ogden, UT: From an MIS standpoint, we are replacing non-compliant mainframe hardware and software. Installation will be completed in the second quarter of 1999. PCs have been tested and programmed with a fix. Embedded chips are the unknown now - we will be hiring a Y2K project manager in the next 45 days for inventory and planning. 

Omaha, NE: Assessment is complete, and on-going implementation is to be completed by NLT June 30, 1999. Testing starts in March, to be completed in July 1999. We are making special preparations for problem solving in January 2000. 
 

Pawtucket, RI: We are done with major items in the assessment stage, but only 25 percent done with awareness and look forward to testing and re-assessment. We have appointed a Y2K Coordinator who is chairing a Y2K Task Force with members from each department. A Y2K plan is in the draft stage and continually being updated. 
 

Pembroke Pines, FL: 

Awareness Stage: The City of Pembroke Pines has actively worked on the Year 2000 problem for the past two years. We have implemented software design tools that have significantly reduced the efforts required for conversions. Adequate funding for the project has been provided. 

Assessment Stage : The City has identified all of its systems. Those systems and equipment that are critical to conducting operations have been given priority. The resources and costs to make them Year 2000 compliant have been identified.

Remediation Stage: This stage deals primarily with the technical issues of converting existing systems when switching to compliant systems. The following systems are in this stage: central cashiering, payroll, utility billing and accounting.

Validation/Testing Stage: This includes the development of test data and test scripts, the running of test scripts and the review of test results. If the testing results show anomalies, the tested areas have been corrected and retested. Although minor problems will undoubtedly remain, the City expects to resolve all of its critical year 2000 problems before January 1, 2000.
 

Petaluma, CA: We are currently completing an inventory of systems and equipment, and planning repair or replacement of all problems. We will test systems identified as critical and will prepare a contingency plan. 
 

Philadelphia, PA: As of December, 1998, Philadelphia determined readiness for 95 percent of its critical applications, mainframe and operating system. All systems will be tested for compliance by July 1999. Business risk assessment was completed in December 1998 and contingency planning/testing will be completed by July 1999. Vendor suppliers contingency and recovery will be tested by September1999. 
 

Plano, TX:

Summary of Year 2000 Plan: All equipment, systems and programs purchased September 1, 1997 or later were required to be Year 2000 compliant. These items are being tested when received by the user departments. All equipment, systems and programs purchased prior to September 1, 1997 were inventoried. These items were tested for Year 2000 compliance, or a letter was sent to the manufacturer asking them to certify their product's Year 2000 compliance. Items that failed the test or did not receive manufacturer certification were assigned a compliance date. These items are monitored on a monthly basis. If the compliance date is exceeded, this triggers further action. Compliance will be reported monthly.

Summary of Readiness: Listed below is a summary of the City's current Year 2000 compliance status. The City's goal is to have all systems with known Year 2000 issues compliant prior to July 1999. Following this summary are notes that add relevant information to the raw numbers presented below.
 

Radios - About half of the remaining items will be compliant with the next release of software. The rest will be compliant if mobile data terminals are replaced by laptops.

Finance - The unknown systems are credit card systems. Year 2000 compliance will be required of credit card providers in renewal negotiations.

Plantation, FL: We are in good shape - 75 percent done.
 

Plymouth, MN: Information systems have been inventoried. We are developing a contingency plan for business operations and beginning work on community emergency management issues. We plan a test of contingency plans in June 1999. 
 

Pocatello, ID: The City of Pocatello began this process in 1990. All software that was written or purchased for the City was determined to be Y2K compliant. Whenever an old system was modified, the century was added to the date field. All hardware and software has been tested and either replaced or updated if not Y2K compliant. We still have approximately 20 PCs that are not compliant. They will all be replaced in the next few months. The City should be fully compliant by mid-1999.
 

Portsmouth, VA: The City of Portsmouth began implementing a Y2K compliance plan in 1997. Conversion work has been underway since this time. At the present time more than 70 percent of the conversion has been completed. The City is targeting completion of Y2K compliance work by September 1999. 

Provo, UT: Provo City's Y2K compliance plan is being executed, and is staying on schedule so far. We are currently compliant in human resources, payroll, and police records and dispatch. The only other major computer systems not yet compliant are the Utility Billing Customer Information System and the Financial System. The Utility Billing System is currently engaged in implementation of a new product. Completion is expected in April1999. The Financial System is currently being upgraded to the version level that is compliant. Completion is expected in February. Preliminary tests of the power distribution system show it to be in compliance, but more testing is coming. The designing of tests for water distribution and water reclamation are currently in process. Renovations of PC applications will take place during the months of February through April. Some PCs will need replacing, but this will mostly take place through normal attrition. Completion of all work to accomplish Y2K compliance should be complete during August of 1999.
 

Redding, CA: The City of Redding has undergone a pretty good assessment of services and looked at the impacts of Y2K. We are in the process of correcting the application code and replacing code and hardware that do not meet specifications. All vital services - electric, water, sewer, solid waste and public safety - have been reviewed. We feel we will be in good shape for the year 2000. 
 

Renton, WA: We have assessed all our major systems and have implementation plans to replace systems or bring them into compliance. We have decided to wait on other less critical systems until after January 1, 2000. We are currently surveying for embedded chips and analyzing outside vendors' compliance efforts.
 

Rochester Hills, MI: The City of Rochester Hills is actively working to ensure that the City's facilities, systems and equipment will be Year 2000 ready or operational on January 1, 2000 and thereafter. The City administration has established a Year 2000 Readiness Steering Committee and the City is currently undergoing departmental inventory and assessment to identify each and every City service or process that utilizes or depends, directly or indirectly, on electronic components. For each item in the inventory assessment, the City intends to develop a risk analysis and to create and implement action and contingencies plans. 

Concurrent with these internal efforts to achieve Year 2000 readiness, the City is also making appropriate inquiries and will undertake appropriate measures to determine whether the City's vendors, suppliers and contractors will likewise be Year 2000 ready. Clearly, this is a complicated and arduous problem and process, but the City is actively engaged in addressing Year 2000 readiness issues. 
 

Rockford, IL: The City of Rockford began its Year 2000 (Y2K) compliance project in1992 when it was informed by Unisys Corporation that the CTOS operating system on its Unisys servers and workstations was no longer supported by Unisys and would not operate after December 31, 1999. In 1993, the City began replacing 63 CTOS workstations. In 1996, the City purchased two Unisys NT servers and began migrating users from the CTOS network to the NT Network. When this migration is completed in March of 1999, the CTOS network will be shut down and the NT network and workstations will be Y2K compliant. The City's mainframe applications have been Y2K compliant since 1992 and required minor modifications for input and display. These modifications were completed in 1998 by our software vendor, Pentamation, and by our in-house staff. In 1999, the City will replace 40 Mobile Data Terminals (MDT's) in police squad cars that are not Y2K compliant. The City will also be upgrading software and hardware for the City heating and air conditioning system, the gas dispensing system, and the security system by March 1999. The City is continuing to investigate other equipment to identify other potential problems, but it presently does not appear that Y2K will adversely impact its ability to operate beyond January 1, 2000. 
 

Rosemead, CA: Since the City of Rosemead contracts with a number of private and public agencies for municipal services, we have to rely on their assurances that they are in Y2K compliance. The City's computers will be in compliance by June 1999. We are considering contracting with the accounting firm that prepares our annual financial report to perform a Y2K compliance audit. Since Y2K compliance will be part of the annual audit, this will assist us in meeting that goal. 
 

Salem, MA: Salem has hired a private consultant to test our PCs and office automation software for compatibility. We have contacted Datapoint and have been assured that our model 5400 Datapoint will rollover and retain the date after a re-boot, which requires updating our system kernel. We do not have to worry about database conversions because Salem had the foresight in 1985 to insist on a four-digit year. We have some key-in's for dates that must be expanded to a four position field, as well as sorts on years. We are only going to address statistical reports and programs at this time. Salem is in the process of purchasing a new computer system (both new hardware and municipal software) within the next three months. Our police, fire, electric and public services departments are handling their own Y2K issues, and all are compliant. We expect to be Y2K compliant no later than March of 1999.
 

Salem, OR: We are systematically evaluating our hardware and software, replacing or revising as appropriate, developing contingency plans for priority services, and eventually testing high priority systems for Y2K compliance. We will be ready. 
 

San Bernardino, CA: We had to replace public safety software (75 percent complete) and water utility billing software (40 percent complete). Both projects are underway at this time. Other minor software problems found during tests have been corrected in-house. A committee of major departments was formed in November 1998 to address the operations and infrastructure issues such as elevators, traffic lights, sprinkler timers, etc. The same committee is responsible for assisting departments in the creation of contingency plans. The committee is chaired by the Fire Department's Disaster Preparedness Coordinator. 
 

San Bruno, CA: We have begun to create priorities and a program to assure the provision of essential services. We expect to be compliant within our jurisdiction. Like many others, however, we depend on an array of third party service providers.
 

San Leandro, CA: An inventory of all known systems has been completed. A Y2K team is being assembled to confirm the inventory and begin testing. Primary systems will be tested in the first and second quarters of 1999 with assistance of consultants. Most software is supported by vendors including law enforcement. Y2K fixes for public safety have yet to be distributed by the vendor (Tiburon). The date of compliance will depend on testing results and vendor provided updates.
 

San Ramon, CA: All relevant hardware and software has been inventoried and is in the process of being researched and analyzed for compliance. We expect to have a fully inventoried Y2K database containing Y2K compliance information and links to associated sites on the worldwide web. Little is expected to happen in researching embedded chip systems.
 

Santa Ana, CA: In regards to Y2K compliance, our City Council has approved an Information Systems Strategic Plan which will effectively address those internal systems requiring new programs or program modifications. Efforts are currently underway, as part of the plan, to assure that our payroll system, municipal services billing system, and financial system will all be operational on January 1, 2000. Currently, all Y2K-related projects are on schedule with estimated completion dates ranging from June to October 1999. The City of Santa Ana is committed to ensuring the integrity of our systems and the role they play in providing a secure environment for our community. Therefore, to prove that the problem is solved, we have devised test cases to prove computational and date accuracy. Additionally, we will run parallel systems in the months leading up to January 1, 2000. We anticipate no interruptions in essential public services including police, fire, water, sanitation and refuse collection as a result of any changes or modifications to our systems for the year 2000. 
 

Santa Barbara, CA: The City developed a plan in 1998 to assess, correct and test. The assessment phase is complete and the departments are evaluating and testing identified items that are Y2K related. The critical City systems in water and wastewater treatment are tentatively considered Y2K compliant and final testing will commence in early 1999. The City in-house applications have been evaluated and are considered ready. No major problems are foreseen for City of Santa Barbara systems. 
 

Santa Clara, CA: The City of Santa Clara realizes the importance of Y2K readiness and has committed staff and resources in preparation. The City is upgrading or replacing mission critical systems that affect the health and safety of the community. We are completing systems assessment and are in the process of, or have already, replaced non-Y2K compliant systems.
 

Santa Clarita, CA: Regarding information systems, the City is about 95 percent compliant. In regard to other potential Y2K issues, the City is actively investigating possible systems which may experience failure. We plan to be fully compliant by June 1999.

Santa Fe, NM: We anticipate full compliance by mid-1999. We are currently working on establishing a citywide contingency plan. We are heavily reliant on the utility companies to provide us service. Our biggest concern is the possibility that utilities may not be able to provide service. At this point, the utilities can not and will not guarantee service. We need some assurance, from them, that service will or will not be delivered so that we can focus on contingency plans and educating the public on what to expect on January 1, 2000.
 

Schaumburg, IL: Our hardware systems are approximately 85 percent compliant; our software systems are about 80 percent compliant. The plan is doing inventory vendor-wide and we expect to be ready by the fall of 1999. Compliance issues are still being worked on as they pertain to mission critical suppliers and vendors. 
 

Schenectady, NY: We are just starting Citywide analysis of the problems. The Finance Office has purchased some software and will be purchasing more software to fix Y2K bugs in our operating system and our software package. No installation or testing has been done to date.
 

Scottsdale, AZ: The City has inventoried and assigned risk factors to all inventoried items. The mission critical items are being addressed for compliance. Contingency plans will be in place and tested as a backup regardless of compliance.
 

Seaside, CA: We are currently gathering data to write a formal plan. Hardware testing is complete, and new hardware has been purchased. The plan will be completed and the budget approved for FY 99-00. Outside vendors are working on solutions for third party software.
 

Seattle, WA: The City identified 27 of its most critical applications that support vital city services. Of these tier one systems, 11 have been confirmed compliant with the vast majority of the remaining applications scheduled for final Y2K testing in the first quarter of 1999. Remediation has included installing vendor supplied patches, full date expansions, and the use of windowing techniques. The replacement for the city's financial management system is scheduled to go into full production October 1999. The project is currently on schedule and on budget. The City's emergency vehicle dispatch capability has recently been confirmed compliant by an end to end test. An end to end test for the city's energy management system is scheduled for the first quarter of 1999. The City's water purification system is new and was specified to be Y2K compliant. Department heads are required to submit certifications of compliance to the CTO for critical applications by June 1999. 
 

Shaker Heights, OH: Requests for proposals are being developed for replacement of three software systems. We expect completion in two weeks. We currently are contacting vendors to obtain compliance information.
 

Sheboygan, WI: The City has contracted for revisions to the mainframe systems using the windowing technique. The revisions have been completed and testing will be conducted in the first quarter of 1999. The City is reviewing all PCs for Y2K software and hardware compliance; this will be completed in early 1999. A task force is reviewing the various other equipment and is attempting to receive verification from the equipment vendors by mid-1999.
 

Shelton, CT: Third party vendors are required to certify Y2K readiness. No unusual problems are evident at this time. Failure to certify may result in loss of business by the affected vendor. 
 

Sierra Vista, AZ: We have tested all computer applications for Y2K compliance. Because we are working within our fiscal year, we will know by July if we have done our homework. 
 

Simi Valley, CA: In 1997, the City initiated an aggressive Y2K remediation program. Three major areas were identified where vital citizen services or critical operations of City departments would be impacted: computer hardware and software (i.e., PCs, networking, mainframe systems); services provided by outside agencies (i.e., banking, insurance providers, utility companies); and embedded systems (water delivery, sanitation plant infrastructure, traffic signals). All departments are represented on a Y2K Compliance Committee for information and coordination efforts. After testing, those systems that are not Y2K compliant will be recommended for upgrade or replacement during the budget process. The City is also coordinating formation of a multi-agency community Y2K task force, represented by various public agencies and utility companies.
 

Sioux City, IA: The City of Sioux City has been engaged in Year 2000 (Y2K) activities for nearly two years. The City's critical and/or largest systems (such as water, purchasing, finance, administrative services, and public safety) are being prepared for Y2K compliance. For example, one of the City's software vendors, whose products are used throughout the City, is providing a Y2K upgrade of the financial, parks and recreation, administrative services, public works, community development, purchasing, and maintenance software packages; this was installed at the end of November 1998. The City continues to work diligently to assure the smooth transition into the 21st century. 
 

South San Francisco, CA: We believe we are ready now, but will continue to test and review all systems.

Stockton, CA: The City of Stockton Management Information Services Department is working with all City departments to assure Year 2000 compliance. Vendors of hardware, software, and embedded chips are being contacted to attain statements of vendor compliance. A database of all identified systems is being compiled according to compliance, non-compliance, or unknown compliance. A compliant product is one that has been certified by the vendor to be ready and has been so tested by the City. Special attention is being paid to Stockton's Police Department, Fire Department, Municipal Utilities District, and Public Works Department to assure public safety and well being.

Stages identified by the City include awareness, assessment, remediation, testing, and implementation. The first stage has been completed and assessment and remediation of non-compliant products and a continued effort to identify systems is now the focus of the City's Year 2000 effort. Of the 150 products defined, 70 percent are currently compliant. Individual departments are responsible for reporting all non-City standard products to the MIS department. The individual departments then assess the compliance of the products and determine action needed to remediate those problems. A Year 2000 Project Manager has been assigned and a Year 2000 Coordinator has been added to the staff. The City is expected to be fully compliant, with contingency plans for critical systems, by December 1999.
 

Suffolk, VA: In our plan, we have implemented and have in production our mission critical tax and financial applications. The E-911 emergency dispatching and public safety records management applications were recently replaced with federal grant funding making them Y2K ready. Our City plans to be fully Y2K ready in the fourth quarter of 1999.
 

Tampa, FL: The City has been aggressively repairing or replacing host-based systems since 1996. Host-based systems and infrastructure is scheduled to be totally compliant by August 1999. The embedded systems review is being conducted by an internal audit with results anticipated to be manageable. The Year 2000 reality facilitated funding for replacement of obsolete systems. 
 

Texarkana, TX: We are finishing up our assessment. Most of our computers are relatively new and are already compliant. We should be finished by June 1999.

Tamarac, FL: The City of Tamarac is in substantial Y2K compliance pending the latest fixes and patches to the operating systems and applications. Over 60 PCs remain to be replaced in the first quarter of the 1999 and telemetry systems will be upgraded by the end of 1999. 
 

Topeka, KS: We are halfway through an 18 month program and are 60 percent complete with the Y2K issues identified to date. We plan to be completed by September of 1999. 
 

Tucson, AZ: We expect to be Y2K ready by mid-1999. We will contract with an independent risk assessor to give us a better idea of our progress.
 

Tupelo, MS: The City's main computer software has been made Y2K compliant and is tested using current dates. The next step is to process Y2K dates and validate the results. Some City departments will have to replace department servers and software. Some desktop PCs will be replaced. This is budgeted in the current budget to be done no later than September 30, 1999. Each department is checking equipment such as traffic signals, power substations, etc. Most of our equipment is not computer controlled. We are a TVA city. The TVA has assessed all of its equipment and found that 10 percent has to be repaired or replaced. They are 30 percent through the 10 percent. We are counting on TVA for power. If we receive the power, our system can distribute to our citizens. We have backup water tanks and ground water if there is a problem with the water district. We have had some tests already to test computer software and equipment. 
 

Tuscaloosa, AL: The City of Tuscaloosa started considering the Y2K problem in the early 1990's and started formally replacing/upgrading systems in 1995. The mainframe computers were eliminated in 1995, and microcomputer-based client/server computer systems replaced them.
 

The inventory and replacement of mission critical management information systems was the main focus of the Y2K efforts. Embedded chip systems have been considered since 1997; a citywide inventory was completed in 1998, and all existing problem areas were identified. Departments are working with manufacturers to determine which systems are Y2K compliant, and what to do to upgrade and replace non-compliant systems. The City expects to be Y2K compliant on mission critical management information systems by April, 1999. Embedded chip systems will continue to be evaluated and replaced if necessary until November, 1999. 

All of this said, because of the insidious nature of the problem, no organization can guarantee complete year 2000 compliance. Much of the City's efforts rely on manufacturers of software and process control computers to be correct in their assessment that their products are Y2K compliant. Plus there is always the possibility of a non-compliant program or system being overlooked due to inadequate inventory control, the lack of realization that it involves a computer, or simple human error. Consequently, no one should rely on the steps the City has taken without keeping these caveats in mind.
 

Union, NY: By September 1999, our IBM AS/400 will be upgraded with Y2K compliant software, tested and ready for use. Individual software products will be tested as time allows. 
 

Ventura, CA: The City has completed the diagnostic stage and is proceeding to prioritization.
 

Victoria, TX: The City of Victoria has completed a Y2K risk assessment, and converted or planned to replace all software. Desktop computers and embedded systems equipment have been inventoried. We are now prioritizing that equipment according to critical applications. Equipment will be tested and fixed or replaced if possible. Contingency plans are being developed for all applications.
 

Waltham, MA: The City of Waltham has been working since 1996 to get the systems under its control compliant with year 2000 issues. A strategic plan has been developed to ensure that the risks associated with the Year 2000 date change are identified and effectively managed. 

A year 2000 team meets monthly to discuss all aspects of the strategic plan. Mayor William F. Stanley has fully supported the team's efforts by giving any remedial steps and testing needed to ensure Year 2000 compliance the highest priority. Since the year 2000 team recognizes the problem affects not only computer systems, it is working with other departments to help identify and manage possible exposure from other sources. The Year 2000 team understands it is impossible to foresee all the various Year 2000 impacts on the City's operations. The team received invaluable assistance from the State Division of Local Services.
 

Waterloo, IA: We are currently 100 percent complete with our system assessment, about 70 percent complete on system repair or replacement, and 15 percent complete on system testing. We are not sure of the date that we will be Y2K ready. 
 

Watsonville, CA: We have been working on assessment and remediation since January, 1998. We are replacing outright a number of key systems (financial, payroll, utility billing, etc). Our methodology has been to work with the various departments and an identified coordinator from each to assess and remediate problems. Many of our systems are provided by outside vendors and we are turning to them for identification and resolution of potential Y2K problems.
 

West Valley City, UT: Having the resource of an in-house MIS staff and management support, planning and actual testing/renovation work has been going on for a number of years. We are about 80 percent critical system-ready now; the remainder of work involves minor software patches now being written by vendors. If year 2000 began today, we would have minor problems, but should be functional. We plan to be completely compliant by the fall of 1999.

Weymouth, MA: The Town of Weymouth had several audits last year - one an audit of the Data Processing Department. The recommendation from these audits was to replace all financial software, install a Town Wide Area Network (WAN) and form an Information Systems Steering Committee. This was all done. Simultaneously, we had a GIS Needs Assessment & Analysis by an outside consultant. The GIS Committee hired a consultant to do the network study. The Information Systems Committee hired a consultant to evaluate and recommend new financial software. The IS staff, consistent with Committee recommendations, will be upgrading all the PCs and hardware in town. The financial staff developed a project plan and the IS Committee followed this for time lines. In conjunction with implementation of a GIS system, new desktop equipment, new financial software and networks, we should be Year 2000 ready by the Year 2000. All departments are being made aware of Y2K, checking into the other areas presently, and hoping to be completed by June 30, 1999.
 

Wilmington, NC: All computer hardware and software has been inventoried, and remediation is on schedule for full compliance by September 1999. An inventory of embedded chips is being prepared; generally compliance is considered reasonably achievable by September 1999. Contingency planning is also underway.
 

Wilson, NC: We have made a lot of progress in changing to new software to replace major applications such as general ledger, payroll, purchasing and warehousing, cash receipts, and utility billing. We have made some progress in identifying other systems that have embedded chips that may malfunction. We are in the process of determining most critical systems and communicating with vendors regarding potential problems and solutions. Still left are testing and developing contingency plans. 
 

Winston-Salem, NC: All departments have been inventoried to determine the impact of the century change. A database has been established to track the progress made by internal efforts and external vendor commitments. The citywide area network will be compliant by July, 1999. Most larger applications systems are already Year 2000 compliant or in the process of final testing, including the financial accounting system, utility billing system, computer aided dispatch, and budget. A dedicated Year 2000 test environment has been established for testing mainframe software applications. All major computer application systems in the city are scheduled to be Year 2000 compliant by July 1999. City departments are working with vendors to determine all date-sensitive hardware, software, and equipment. Contingency plans are being developed by each department to handle the possible failure of systems. 
 

Youngstown, OH: The City of Youngstown began by replacing all system hardware and operating systems that were non-compliant. That is completed as of now. Each application system has been evaluated and modifications and testing have begun. Full tests should be done by summer of 1999.

Of the 220 cities providing information for this report, one percent (three) have a population below 30,000; 36 percent (80) have a population between 30,000 and 49,000; 35 percent (78) have a population between 50,000 and 99,999; 19 percent (42) have a population between 100,000 and 249,999; five percent (10) have a population between 250,000 and 499,999; and three percent (seven) have a population above 500,000. The survey cities are: