Laserfiche WebLink
ADMINISTRATOR JENNINGS DISCUSSED HOLDING A PUBLIC HEARING ON A <br />CHANGE OF FRANCHISE OWNERSHIP AT HOLIDAY VILLAGE MOBILE PARK. THE FRAN- <br />CHISE OWNERS WISH TO CHANGE OWNERSHIP TO THE PRESENT HOMEOWNERS IN THE <br />PARK, HE DID NOT FEEL THIS WOULD BE A CONTROVERSIAL MATTER, AND THE POARD <br />AGREED IT COULD BE HANDLED AT A REGULAR MEETING. <br />ADMINISTRATOR .JENNINGS NEXT INFORMED THE BOARD THAT GENERAL <br />DEVELOPMENT COMPANY WISHES TO AMEND THEIR FRANCHISE BY CHANGING THE FORMULr <br />FOR SETTING CONNECTION CHARGES, HE FELT THIS ALSO WOULD BE A FAIRLY ROU- <br />TINE MATTER AS THE CHANGE DOES NOT AFFECT EXISTING CUSTOMERS, ONLY PRESENT <br />LOT OWNERS, <br />AFTER SOME DISCUSSION, THE BOARD AGREED TO SCHEDULE BOTH PUBLIC <br />HEARINGS FOR THE REGULAR MEETING OF SEPTEMBER 21ST, <br />ON MOTION BY COMMISSIONER SCHMUCKER, SECONDED BY COMMISSIONER <br />SIEBERT, THE BOARD UNANIMOUSLY APPROVED RETROACTIVE OUT -OF -COUNTY TRAVEL <br />FOR THE ADMINISTRATOR, COMMISSIONER Loy., COORDINATOR THOMAS AND .JACK <br />FLINT TO MEET WITH THE DOT IN FORT LAUDERDALE ON AUGUST 9, 1977. <br />COMMISSIONER SCHMUCKER READ TO THE BOARD AN ARTICLE FROM THE <br />STATE & COUNTY ADMINISTRATOR, ,JULY., 1977, ABOUT THE ADVANTAGES OF A COM- <br />PUTER SERVICE AS OPPOSTED TO AN IN-HOUSE PROGRAM, THE ARTICLE SET FORTH <br />SOME OF THE DISADVANTAGES OF THE IN-HOUSE SYSTEM AS FOLLOWS; <br />" • High turnover in programming, <br />analysis, and/or software <br />management positions. <br />• A large number of programmers <br />or analysts with less than three years` <br />experience implementing govern- <br />ment applications. <br />• Computing personnel with little <br />experience in government ap- <br />plications, unable to communicate <br />effectively with users, and oriented <br />mainly to computing technology <br />rather than solving the problems of <br />government. <br />• Non-existent or inappropriate <br />standards Ind procedures for <br />training, documentation, and <br />programming. <br />• Inability to meet implementation <br />budgets or schedules. <br />• Little or no new systems devel- <br />opment; programmers/analysts <br />concentrated in maintenance and <br />operations. <br />• Software support overly con- <br />centrated on the needs of a few <br />users; no master planning or <br />priority setting mechanism. <br />78 <br />Boa 30 PAGE 366 <br />J <br />