Hallazgos & Recomendaciones
13 hallazgos
F1:
We found that there are five parts to the system/project. Each part is complete to various degrees. Some parts are in productive use today. When viewed as a whole, the effort to replace and enhance the property tax assessment system was approximately 60% complete when work was stopped. The five parts and their completion status are as follows: 1) Legacy X1 System - Complete and in production - The County's production legacy system (X1) for Property Appraisal, Billing and Tax Collection. This system incorporates all the business rules and workflow that support the activities for processing of Secured and Unsecured tax rolls of the Offices of the Assessor, Treasurer-Tax Collector and Auditor-Controller. The basic screen design of the existing system was to be used as the basis in the next stage of development of the system described in #4-5 below. We reviewed the design of the legacy system during our assessment. It is a menu driven character-based system that the Assessor's staff uses in conducting the day to day business of the office. The Assessor and the Assessor's office manager convinced us that the business processes as designed in the legacy system were adequate and efficient for the Assessor's function. The replacement efforts were focused only on the Assessor's part of the application (i.e. not the Billing, and Tax Collection portions). 2) Comparative Sales System - Complete and in production - There is a PC based system using a Microsoft (MS) Access database that supports a comparative sales analysis data base and stores digital photographs of each parcel. We observed this system in use in the Assessor's office during our assessment. 3) Data Base Design - Complete - There is a database design for a complete countywide Property Tax system. The design we reviewed supports all aspects of the Property Tax assessment function and appears to meet standards for a County of Nevada Assessor Software Development Assessment Carrera MAXIMUS normalized relational database. This database design forms the basis for a new system design for a replacement system. The database design is documented in a technical diagram called an Entity-Relationship-Diagram (ERD). 4) Replacement Comparative Sales System - Partially complete (~90%) - There is a system that is intended to replace the MS Access comparative sales system described in #3 above. The system incorporates the digital photograph elements from the MS Access System and adds digitized plot plans and parcel maps to the data base. The system is written in Visual Basic (VB) and is designed to run on an MS SQL database using an Internet browser to view parcel data. A considerable amount of design and development work has been completed on the replacement system. We were able to view a prototype version of the new system in the Assessors office. This portion of the overall project is approximately 90% complete. While it is intended to complement the business functions presently provided by the X1 system, it has value by itself as a more powerful Comparative Sales application. The technology used for this application is intended to function in the same way as the Internet using an Internet browser such as Netscape or Internet Explorer. Outstanding tasks include the creation of system documentation and final testing/debugging. 5) Replacement of Existing X1 Assessor System - Minimally complete (~0%) - The Assessor's plan was to re-program the screens and database (from the X1) into the new VB/MS SQL software platform (from item #4 above) and normalized database (from item #3 above). This would result in all of the Assessors applications being combined and using the same "Browser" technology. Included in the Assessor's design was consideration for the support of other County departments. The current system includes a database that is an extract of the Assessor's production database (on the X1) which other departments access for their own use. The Assessor's design included an interface that would continue to provide the extracted Assessor database on the X1 for other departments to use in exactly the same manner as the existing system. Creating new interfaces to any new systems introduced by other departments would be much easier with the new relational database design. As a follow-on effort to the replacement of the X1 system, the Assessor described future plans to offer access to limited amounts of property data to the public via the Internet. Public access through the Internet was not part of this project, however the development and design work that was in progress is an essential element in order to complete the public access piece sometime in the future.
F2:
The conceptual design and features of the Assessor's new system are better than those found in any commercial off-the-shelf California Property Tax system available in the market today. There are presently very few commercial off-the-shelf (COTS) products for Property Tax Assessment in California. A few vendors have claimed to have development efforts underway for new products, but to our knowledge, none of them has signed contracts County of Nevada with a county at this time. The Assessor confirmed, and we agree, that the existing system contains features and functions not present in the few COTS systems available. In addition, none of those products includes support for digital photographs and area plots as envisioned by the Assessor's design.
F3:
We found that the Assessor had valid reasons for originally proceeding with this project. The Assessor described to us the reasons that he believes that this development project was necessary. First, the legacy Property Tax system is based on data base management software called "UniVerse". While this data base management system has served the County well, the current release level is outdated. Furthermore, the legacy property tax database design is outdated and makes the integration and sharing of data difficult. Second, the County's computer system (the X1) is outdated. The hardware is experiencing capacity problems and is difficult and relatively expensive to maintain compared to newer equipment. At the time that the Assessor embarked on the path to replace the Property Tax application, no plans were in place to replace this hardware. Third, the legacy system on the X1 uses a product for screen design and presentation management named Total On-line Applications Development System (TOADS). The version of TOADS in use at the County is several releases behind and does not support modern development tools and systems features such as a graphical user interface (GUI). While there are known advantages and disadvantages to a GUI interface, it is generally accepted that the advantages, e.g. ease of use and reduced training, outweigh the disadvantages, e.g. intense data entry efficiency. In other words, applications that require intense data entry are most efficient in a character-based mode.
F4:
There are changes in hardware and software planned in the County that should be considered in conjunction with continuing development of the Property Tax system. The County's IS Director has described plans to upgrade the County's X1 system. The planned system, a Data General Aviion server is a state of the art mid-range computer that will place the county in a position to take advantage of current software technology. The new Data General system is scheduled for installation by spring of 2001. The County also plans to upgrade the UniVerse database software. The new version of UniVerse supports a wide range of current development tools and software languages (including Visual Basic or VB). According to the documentation on the new version of UniVerse, it will support any normalized database design. With this new functionality in the UniVerse product, the normalized database designed by the Assessor to run on an MS SQL Server database might work equally well in the new UniVerse, as might the new software written in VB. This means that completing the Assessor's project as County of Nevada begun would not be in conflict with future direction currently planned by the County and could even be merged at some future date if desired. Also, completing the Assessor's project would create an opportunity for the Tax Collector and Auditor to migrate their legacy systems to the same platform, if this was deemed desirable after reviewing the effectiveness of the Assessor's new system. The County's future plans for the TOADS screen management system are unclear at this time. Given the legacy Property Tax system's reliance on TOADS, clear direction in this area is needed. It is important to note that TOADS and UniVerse are critical components in many other County systems. These include: Financial Accounting, Fixed Assets, Budgeting, Fleet Management, Planning, Building Inspection, Criminal Justice Case Management, Jail Management, Computer Aided Dispatch, Collections, Board of Supervisor's Document Indexing, Time Accounting, Cashiering, Court Calendar, Probation, and Purchasing. 2.2 Project Management Methodology
F5:
We found that the Project Management methodology used by the Assessor was much more informal than we would reasonably expect to find on a project of this type. At a minimum, the project management methodology would be expected to track time (labor hours), cost, and deliverables during the life of the project, and forecast the schedule and cost to complete. The application of a methodology to a project must be included in the cost estimates. Overhead cost for the project increases as the project management methodology becomes more formal, however, project risk increases as the formality of the methodology decreases. There were two major reasons given for the informal approach to project management. First, was the wide variety of work being performed. The current Assessor, Mr. Green, was using the same resource(s) to perform in-house maintenance on business systems, day-to-day support of the office LAN, and for new development work. He assigned top priority for work being performed by the temporary employee to the day-to-day network administration and desktop PC support functions. Consequently, development work on the new system became difficult to forecast as it could be (and was) interrupted anytime there was an issue effecting the department's information technology and its operation. The second reason for the informal approach was that the development team was very small and worked in close proximity to Mr. Green. From Mr. Green's perspective, this close working arrangement reduced the need for more formal project management methodology. However, it also led to confusion and misunderstanding outside of the Assessor's Office as to the nature and status of the system, progress on new development and Mr. Green's plans for the future. County of Nevada Project Plan 2.3
F6:
indicated: "We found no formal documentation of a project plan associated with this project". The Carrera-Maximus report also indicates that little system software documentation exists due to a system development process being used by the Assessor called "Rapid Prototyping" or "Iterative Development". This has resulted in little or no documentation of the new software being produced to date. The County Administrator supported these findings by Carrera-Maximus in his introductory report accompanying the assessment report presented to the Board on September 12, 2000. 3. In his response to the Grand Jury Interim Report the Assessor stated that since he "took office in November 1998, less than $200,000 has been spent for computer equipment and application programs in the Assessor's Office." The Grand Jury examined all payroll records and invoices paid for computer hardware, studies, software, and computer related expenses. Between November 15, 1998, and December 31, 1999, the following amount were spent: Paid to temporary employees $139,210 Employees share of FICA (7.65%) 10,650 Total employee cost $149,860 Paid to outside vendors $195,119 TOTAL COMPUTER EXPENSE $344,979 Partially agree. The Board has no independent knowledge of the results of the Grand Jury's review of payroll records and invoices. Ward/other/grndjury/gj9900-IR6-Assessor The Board does agree with the Grand Jury that at least $300,000 has been spent to date on the development of the Assessor's computer system. Although the exact amount actually spent towards developing the computer system can not be determined due to financial accounting system limitations, the County Administrator, in the introduction to the Carrera-Maximus report, estimates that the project has cost at least $300,000. 4. There is a question as to who will own the Assessor's proposed computer system upon its completion. There is no formal County procedure regarding ownership of intellectual property. Disagree with the first sentence. The Board believes that all intellectual property developed to date in conjunction with the Assessor's new computer system, as well as other related systems and components either developed by the Assessor, contract employees of the Assessor, or Assessor Department employees, is the property of Nevada County. Any future system development of the Assessor's proposed computer system, either done by staff or by professional service contract, will specifically provide for legal protection of county intellectual property. Partially agree with the second sentence. Clause Twenty One in the Miscellaneous section of the county standard professional services contract form clearly specifies that all intellectual property concerning or relating to contracted work projects or services are owned by the county without exception. The Board also hereby directs the County Administrator and County Counsel to develop a formal policy regarding ownership of intellectual property by county employees and provide a
F7:
The Assessor was using a methodology known as "Rapid Prototyping" or "Iterative Development". This software development technique is highly interactive (typically between the designer and a knowledgeable user) and can be quite adequate for focused projects attempting to introduce new technology. At the same time this methodology does not County of Nevada Assessor Software Development Assessment Carrera XIMUS produce any significant documentation because the designer is constantly trying new things, showing them to the user, and incorporating the user's feedback. At some point, the designer must stop the iterations and document the work produced. That point is usually after all prototyping is complete. Prior to that point, the prototype itself serves as the documentation. This can easily get out of hand if the project is very large or if there are very many people involved in the effort. In the Assessor's case this was a small focused effort involving very few people. Therefore, the fact that there is no formal documentation at this point does not surprise or concern us. While we are not concerned at the level of documentation at this point in time, we did hear staff's concerns about the impact upon staff time taken up by the project using this development approach. Our assessment was limited, so we did not make any effort to verify or determine the level of staff time that was needed to support the development effort. Based upon our observations of the system's development status, we believe that the most intense period of interaction between the office staff and any software developer is over. However, we have included a specific recommendation that would address this issue should a new contract to finish the project be negotiated. When performing iterative development, some technical aspects of the system are frequently "stubbed-out." This means that the code to provide that functionality is not really there. This is often the case when one is trying to develop a new user interface, which is what we observed that the Assessor was doing. This allows the developer to focus on one aspect of the system at a time without having solved all of the technical problems of the finished system. Clearly, all such "stubbed-out" portions of the code would have to be completed before the system would be usable. While we did not examine the code directly, discovering that portions of the system had been "stubbed- out" would not have changed our conclusions given the development approach the Assessor was following. As can be seen from our diagram (Appendix A), the introduction of new technology into the Assessor's system was being accomplished in an evolutionary rather than revolutionary manner. This approach has produced successful results in the Assessor's office for many years. Initially, the Assessor's office developed and maintained a Paradox database application running on a DOS PC to perform comparative sales analysis using data extracted from the X1 system. This system was moved off the Paradox system in the mid-1990's to the emerging Microsoft office suite. The replacement system used the MS Access Database as an initial deployment with the intention of eventually moving to a more robust database platform. At the time this was considered an upgrade in technology which moved the comparative sales application onto a relational database with a Graphical User Interface (GUI), namely Windows. In 1995 digital photographs were introduced to the office which could be stored on a shared server computer and viewed with stand-alone viewer software. The Assessor County of Nevada Assessor Software Development Assessment estimates that this modification generated a saving of $22,000 a year in Polaroid film costs. Integration of the digital photographs into the Access database improved productivity of the Assessor's staff and lowered document management costs (of the pictures). The MS Access database product suite used includes some database design tools that the Assessor and the developer (a temporary County employee in the Assessor's Office) used to restructure the data for all of the Assessor's data residing back on the X1. The design we observed was a highly normalized relational data base design. A highly normalized relational design for a database has several well-established benefits in terms of total cost of ownership. The term "total cost of ownership" (TCO) refers to taking a comprehensive view of all aspects of costs, both initial and on going. Use of a relational database helps to create what is called an "open-system." An open-system assures that other County department's data needs from the Property Tax system could be met without requiring them to be on the same platform. Generally, this would apply even if they decide to purchase a different off-the-shelf system (provided those systems are "open" as well). However, for many (mostly technical) reasons, we caution the County about using MS Access as a database platform for long-term strategic use in the County (see section 2.6 for additional TCO aspects). The Assessor is well aware of the known limitations in MS Access. Initially, MS Access was being used as an application prototyping and production tool and to aid in the re- design of the new Property Tax database. However, the intended prototype turned out to have immediate payback in terms of productive use by the Assessor's office. As a result of this value, the prototype containing comparable sales and digital photos was placed in production and is in use today. The Assessor described to us his intent to develop and implement the new database using MS SQL Server. MS SQL Server is Microsoft's premier database product and is presently one of the industry leaders for strategic enterprise database platforms. The new system design that the Assessor is currently introducing, includes a new way of structuring data called "compound data architecture" and new development methodology called "Object-Oriented Development" (OOD) in a "Thin Client" environment. Compound data architecture allows computer systems to collect, store and present much more than just the text-based information which most users are familiar. Things such as pictures, video/voice recordings and drawings can be stored and manipulated with much the same ease as simple text by the user. But for the developer, it requires significant new skills and the use of new and different practices. In order to understand the significance of Thin-Client software, consider an older form of software architecture (but more modern than that employed on the X1) that is very popular today called Client/Server. In this approach, the software is divided into two different parts called the Client and the Server (or Client/Server software). The Server portion controls the database and maintains its integrity. The Client portion controls the County of Nevada Assessor Software Development Assessment arrera presentation of the information to the user. This has usually resulted in development of two separate sets of programs, one running on a database-server computer and one set running on each user's workstation. This results in each user having to have a copy of the client portion of the application and introduces significant system management challenges. While it was initially thought by the industry that Client/Server systems would be less expensive to develop, operate and maintain than traditional "mainframe" or "legacy" systems, experience has proven otherwise. Studies have been published by well know research firms like The Gartner Group showing that Client/Server systems are up to 5 times as expensive as mainframe systems. Because of this huge difference another approach had to be found. The latest means to develop software that attempts to address this issue is called Thin- Client application development. Thin-Client applications require very little software to be loaded on the user's workstation, preferably nothing more than an Internet web browser (which is frequently already present). Thin-Client applications are very new and require additional tools and skills over and above the move to Object-Oriented Development. In particular, the use of automated testing tools is highly recommended. The Assessor is developing the new system using this Thin-Client approach. During the course of our assessment we have heard this referred to as "Browser" software. We did not find the expected use of any automated testing included in the Assessor's plan.
F8:
The staff resources being used to develop the new system were also being used to maintain the old system. This seems to have caused considerable confusion about what was being done, progress being made, and cost of the effort. As a result of this practice, development on the new system would proceed only when everything else (technology wise) in the Department was working well. This is frequently the way a small staff is managed especially if there are no external deadlines for the new development like Y2K. The disadvantage is the protracted nature of the development time and the lack of a visible schedule for completion. This appears to be the way the Assessor's Office was run for a number of years preceding the term of the current Assessor. With the recent move in the County to consolidate IT resources into a centralized department, a more focused effort to complete this project is needed. This will help to limit cost and allow better tracking of project status and deliverables. Change Management Policies and Practices
F9:
We found no formal change management policies or practices in use in the Assessor's Office. We checked with the County's IS department (in order to consider
F10:
The development tools being used to support this project consisted of industry standard off-the-shelf products. Proper use of these products places the County in the industry mainstream and has already produced concrete benefits. Use of standard off-the-shelf products for systems development presents a minimum risk to the organization of being out of step with industry standards. The Assessor was using Visual Basic, MS SQL Server, AutoCAD, Windows NT and MS Office for the project. These are all mainstream products. In addition, a single company, Microsoft, supports all but AutoCAD. Having a single vendor for all or most of the supporting products can enhance support opportunities and make interaction and integration of system components less problematic. The benefits of the system developed using modern tools and techniques include lower total cost of ownership (TCO) because of the following aspects: Increased labor pool of qualified programmers – use of current technology increases the available pool of trained resources. > Normalized relational databases are easier to maintain and require less complex code structure through the use of SQL (Structured Query Language). > Object-Oriented programs enjoy a high potential for re-use if carefully constructed. > Use of automated testing improves reliability for all systems, which improves County productivity. In addition, specifically concerning the Assessor's project: County of Nevada Assessor Software Development Assessment arrera лахіmus The Assessor's Office has already witnessed improved productivity with the limited functions deployed so far. However, these were just prototype systems. Finishing the project could help consolidate those gains and add additional document management tools that should further enhance productivity. > The project allows the County to have concrete information upon which to base future directions for technology upgrades. The County may be able to recoup some portion of its development costs through data subscription services or even licensing the software to other counties or licensing the system to a vendor.
F11:
The development, test and production environments are not well defined. It is a common practice in these types of projects to set up multiple server computers where each computer supports either the development, test or production environment. This approach helps assure that the developers, testers and users operate in a known and stable environment. This way, a problem encountered while testing a change to the system will not affect the systems operation in production. In the Assessor's case, the system was under development and the development team was small. This small configuration reduces the importance of multiple environments. However, formalizing a separation before the system enters production would be essential. 2.7 Other Relevant Issues Two other relevant issues surfaced during the course of our assessment. The two issues were Communications and Funding. Discussions of those two issues are included in this section. Communications In Section 2.2 of this report, we identified that there was "confusion and misunderstanding outside of the Assessor's office as to the nature and status of the system, progress on new development and Mr. Green's plans for the future." This breakdown in communications between the parties and the ensuing need for the public to have a level of understanding of how funds were being spent, caused the project to be halted. At the point that the project was halted, design documentation was not complete and may now be partially lost. These actions may have cost implications in the future if, or when, the project is resumed. More important, it became clear to us that effective communications and mutual trust must be rebuilt between the parties for the future good of the County, the County of Nevada Assessor Software Development Assessment success of the IS Strategic Planning process and the successful completion of this project. Funding Plans
F12:
At the time that the contract was presented to the Board by the Assessor (December 1999), the Assessor had a reasoned approach in mind for funding the project. The Assessor's Office had not adequately communicated this plan to the County Administrator's Office and had not followed up on several administrative and/or procedural steps necessary to put the plan in motion.
F13:
Some of the assumptions used to create the December 1999 funding plan are no longer valid, requiring modification to the plan if the project is to proceed at any level. At the request of the County Board of Supervisors, we were asked to review and report on the plans the Assessor had to fund this project. We were also asked to review those plans with the Budget and Auditor's offices and report our findings. The following five sections of this report cover this issue. The changes in circumstances that have occurred over time have been factored into our
Recomendaciones adicionales
14
No vinculadas a hallazgos específicos.
R1:
business partner of the temporary male employee (as identified in the Interim Report). In his public response to the Grand Jury report he stated that "the male worker was never a 'business partner' not did the Assessor state that he was". Clearly, the Assessor has given conflicting statements. The Grand Jury has a copy of the fictitious business name statement files with the County Recorder by the Assessor, stating that the Assessor and the male employee were indeed partners. Neither agree nor disagree with the first three sentences. The Board has no knowledge of the Assessor's testimony to the Grand Jury. Partially agree with the fourth sentence. According to the Assessor, he did have a prior business relationship with the temporary male employee referenced in the report, but the fictitious business name statement referenced by the Grand Jury identifying this business relationship as a partnership was never published. The Assessor also responded to the Grand Jury that a subsequent statement was published identifying the business as a sole proprietorship. The Grand Jury Interim Report on the Assessor's Office recommends that before any
R2:
more funds are spent on the computer system the Assessor provide the County Information Systems Department with documentation of his proposed system. To date this has not occurred. Agree. The county Information Systems Department has no record of receiving any documentation from the Assessor regarding his proposed new computer system. The Assessor indicated in his response to this Finding that he previously provided extant documentation of the proposed system. In his May 24, 2000 response to the Grand Jury, he indicates he will comply, but that it is "inappropriate and unnecessary" since the proposed computer system is a rewrite of the current computer system and the county Information Systems Department already has "complete documentation". The Assessment of Software Development in the Assessors Office report, dated August 30, 2000, prepared at Board direction by Carrera-Maximus, indicated in 2.2 Project Management Methodology. Finding 5, that "...the Project Management methodology used by the Assessor was much more informal than we would reasonably expect to find on a project of this type".
R3:
In his response to the Grand Jury Interim Report the Assessor stated that since he "took office in November 1998, less than $200,000 has been spent for computer equipment and application programs in the Assessor's Office." The Grand Jury examined all payroll records and invoices paid for computer hardware, studies, software, and computer related expenses. Between November 15, 1998, and December 31, 1999, the following amount were spent: Paid to temporary employees $139,210 Employees share of FICA (7.65%) 10,650 Total employee cost $149,860 Paid to outside vendors $195,119 TOTAL COMPUTER EXPENSE $344,979 Partially agree. The Board has no independent knowledge of the results of the Grand Jury's review of payroll records and invoices. Ward/other/grndjury/gj9900-IR6-Assessor The Board does agree with the Grand Jury that at least $300,000 has been spent to date on the development of the Assessor's computer system. Although the exact amount actually spent towards developing the computer system can not be determined due to financial accounting system limitations, the County Administrator, in the introduction to the Carrera-Maximus report, estimates that the project has cost at least $300,000.
R4:
There is a question as to who will own the Assessor's proposed computer system upon its completion. There is no formal County procedure regarding ownership of intellectual property. Disagree with the first sentence. The Board believes that all intellectual property developed to date in conjunction with the Assessor's new computer system, as well as other related systems and components either developed by the Assessor, contract employees of the Assessor, or Assessor Department employees, is the property of Nevada County. Any future system development of the Assessor's proposed computer system, either done by staff or by professional service contract, will specifically provide for legal protection of county intellectual property. Partially agree with the second sentence. Clause Twenty One in the Miscellaneous section of the county standard professional services contract form clearly specifies that all intellectual property concerning or relating to contracted work projects or services are owned by the county without exception. The Board also hereby directs the County Administrator and County Counsel to develop a formal policy regarding ownership of intellectual property by county employees and provide a recommendation to the Board by January 31, 2001 (See response to Recommendation No. 2).
R5:
The Assessor's response to the Interim Grand Jury Report, filed April 17, 2000, failed to meet the requirements of California's Penal Code Section §933.05. Agree. The Assessor, in his April 17, 2000 response to the Grand Jury did not specifically indicate if he agreed, disagreed, or partially agreed with each Finding. A reading of his responses to each
R6:
Recommendation for a Service Level Agreement: Staff agrees that service level agreements are prudent when contracting for outside professional support services. However, the County's standard arrangement for IS support to departments requiring enhanced maintenance and support services is to provide dedicated staff which take daily task direction from the departments. In exchange, the department executes a Memorandum of Understanding (MOU) with IS. This arrangement provides more flexibility and support to departments than a service level agreement. The IS Department currently has executed MOU's with other departments and offices, including those headed by elected officials. Attachment A September 12, 2000 Moving the Discussion to the Higher County "Picture" This section includes staff reflections on issues outside the scope of the consultants' work, which nonetheless are related to decisions about what to do now. They include:
R7:
etc.) in the past is not acceptable for future work on this project. There are resources available in the County to help meet this need. The support and maintenance of the Assessor's Office systems (LAN, X1, PC hetwork, etc.)
R8:
can and are being serviced by the County's IS Department. The servicing of these systems should remain completely separate from any development of the software project. The County's method for Attachment A September 12, 2000 handling this service is codified in a standard MOU which should be executed between IS and the user department or office. The Assessor has not yet signed an MOU. Significant changes in the County's leadership, planning and funding of IS resources since the
R9:
Assessor began his project are available. If entered into as a willing partnership, these resources can provide immediate and long-term benefits for both the Assessor's Office and the County. Cooperatively working with other County departments and in conformance with Board-directed policy will benefit the Assessor and his staff and the County "family" as a whole. In turn, a relationship of mutual respect, communication and collaboration benefits the taxpayers. Near-term funding opportunities to address finishing the 10% of the CSS rewrite may be
R10:
realistic enough to accomplish without additional General Fund support once a project plan and costs are determined. Examples of possible funding scenarios include getting State approval for redirection of some SLP funds and/or use of unspent current year appropriations in the Assessor's approved Clearly more information on costs is necessary before definitively allowing a funding budget. recommendation based on the range of possibilities. The County has a responsibility and an opportunity to help influence long-term funding for the
R11:
Property Tax Administration Program. Devotion of resources to this effort could synergistically benefit much more than the Assessor's Office and its software development project. Although there is no written policy on this issue, it is generally assumed that the law protects
R12:
County ownership of all intellectual property developed by regular and temporary employees using County resources. In the future, the consultants recommend that the County contractually cement intellectual property rights about ownership of the software (code) or any other products developed under this project if/when there is a decision to continue work on this project. At the workshop, additional concepts such as "derivative works" and protection from licensing fees were introduced. It is noted that the County's standard Professional Services Agreement does include a general clause pertaining to County ownership of intellectual property. However, given the industry, closer attention and expansion of that clause may be prudent for software development agreements executed by the County in the future. There may be entrepreneurial opportunities for the County as a result of completing the CSS
R13:
and/or participating in further development on this project. However, these opportunities should be addressed as "value added" and separate business decisions requiring information, analysis and a reasoned approach, in contrast to having them drive decisions to move forward. The issue of the former temporary employee(s) and any future role in the project must be
R14:
addressed. It was raised to a high level of public visibility and controversy by the documented concerns of Assessor's Office staff, questions from the Board during the December 14, 1999 meeting, and the Grand Jury's Interim and Final Reports. The employee is also described in the consultants' report as the "original developer." Given the lack of documentation and project plans, the consultants' recommendation that the County first determine whether the original developer is interested in completing future work is not unreasonable from a business perspective. There is no guarantee that future work with the original developer will take less time and will therefore cost less in the long run, but it is a logical step. However, it may not be politically feasible unless the project is assured of strong and independent project management (also critical from a perspective of performance and compensation) and specific parameters for the contractor with regard to offsite development and staff interaction. According to Attachment A September 12, 2000 County Counsel, a well-defined scope of work in a Professional Services Agreement will also address the Board's previous concerns about the appropriateness of shifting work from a temporary employee to a contract. Finally, any contract with the original developer that may appear before the Board in the future to provide for work on this project will be completely different than the contract presented in December 1999. The County clearly has the plan for what would be needed to contractually proceed with this project. Staff Recommendations-- General Based on the discussions in this comprehensive report, it appears to be in the County's best interest to try to move ahead with completion of the CSS rewrite as recommended by the consultants ( of the Carrera-MAXIMUS report) with these important exceptions.