Loading...
2001-03-12 SP SPECIAL TOWN BOARD MEETING MARCH 12, 2001 MTG. #11 RES. 121-1225:30 P.M. TOWN BOARD MEMBERS PRESENT SUPERVISOR DENNIS BROWER COUNCILMAN JAMES MARTIN COUNCILMAN THEODORE TURNER COUNCILMAN DANIEL STEC COUNCILMAN TIM BREWER TOWN DEPARTMENT HEADS HIGHWAY SUPERINTENDENT RICK MISSIT A DIRECTOR OF INFORMATION TECHNOLOGY BOB KEENAN DIRECTOR OF BUILDING AND CODES CHUCK RICE LANDFILL SUPERINTENDENT JIM COUGHLIN TOWN ASSESSOR HELEN OTTE Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. PLEDGE OF ALLEGIANCE LED BY COUNCILMAN TIM BREWER DISCUSSIONS GOVERN STATUS UPDATE AND REVIEW Director Keenan-Gave a presentation to the Town Board on the history of the Govern Software. Search started in 1999 when the Community Development software for building permits and inspections was not Y2K compliant, also looking for a product that would be integrated to be used by more than one office. November of 1999 the Town signed an agreement with Govern software which included software for the wastewater and water department including billing, the Clerk's office the accounts receivable package, Community Development called land management and the Assessors Office. First step was conversion of core data, which is the parcel information, noted right from the start there were difficulties in the conversion especially with the owner's names. First Department to go on line was the water/waster water department and utility billing and after that Community Development. All the named departments use the software on a daily basis except Assessor's Office, which updates the core information when deeds are fild. The Assessor's Office uses RPS for their base work. Noted Warren County is very interested in how our data and the format of our data are received by them, they will use said data to produce tax bills for the school and town. Noted at present Warren County is using RPS version three, concerned about data coming from RPS four and also they do not like the format from the Govern system. Noted the County is trying to convert to RPS four not sure if they will have problems with the AS400 they have told us that they want to hold off until October to convert all the other towns in the County to the RPS four. Spoke about the new tax map numbers for the Town, Warren County has to implement that change, noted there will be a public meeting in April on the tax map number changes. Govern Issues: Not satisfied with the initial layout of the screens, not liking the number of screens to do data entry, some performance issues, speed, records locking, we have found that the users are frustrated with the software, thre have been on going problems, especially the Clerk's office with the way some of the transactions are occurring the information that they are getting out of it. Noted that there have been a number of problems in creating reports from the software that the County wanted. At this point what I feel should happen that we try to work with the County to move to the RPS version four software. Noted that the Town will be moving to a Microsoft SQL server we will increase the performance of the data base, we will not have the record locking issues and a better backup of the system. Govern 7.0 software has been released, which will allow us to customize screens. Issues with Clerk's Dept. is the breaking out of penalties between various districts, we got a decision from the State Comptrollers office noted that it is not an issue with the State Comptrollers Office, also noting that the Clerk is still not satisfied with it. COUNCILMAN BREWER-Questioned if we would be dumping Govern and get RPS? DIRECTOR KEENAN-Noted we would not be dumping either, we would be moving to the next version of RPS which is what the County wants us to do, we would stay with Govern software for the Departments that we have it in at this point. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs. Infobases built before v3.1 have unreliable record IDs.