Laserfiche WebLink
APPENDIX <br /> LONG RANGE SYSTEMS PLANNING <br /> <br /> The need for an information systems plan was identified by the 1990 and 1991 audits. In 1991, a <br /> plan was prepared internally by the County's data processing department. This plan was not accepted <br /> by the County Council and asole-source contract was given to an independent contractor to develop a <br /> systems plan for the County. <br /> A "Long-Range Strategic Information Systems Plan" (Plan) was prepazed for the County in April <br /> 1992. The content of this plan is similaz to the plan prepazed for the County of Maui. The Plan does <br /> not include all of the analyses necessary for the County of Hawaii to adequately plan its information <br /> systems. The systems plan should include the following (see Exhibit I): <br /> • Business Model -The purpose of a systems plan is to ensure that the administration allocates <br /> system resources and establishes priorities based upon countywide needs. This analysis identifies <br /> the organizational mission, objectives, and critical success factors for the County administration. <br /> Information systems development efforts should be tied to the County's strategic plans and <br /> objectives. Systems must deliver information where it is needed. Therefore, systems <br /> development planning must include planning for all areas of the County Administration. <br /> The County's Plan does not identify the objectives and critical success factors for the County <br /> Administration. <br /> • Function Model -For information systems to support the needs of the County, a common <br /> understanding of the County's processes must be developed. The function model defines the <br /> administration's processes and how they relate to one another. By linking these processes to the <br /> objectives and critical success factors, the most important processes can be identified. By linking <br /> processes to organizational units, redundant business activities can be identified, and the <br /> interaction between organizational units can be determined. <br /> The function model is not the same as an organizational model. Organizational boundaries are <br /> eliminated and only the functions of the County aze identified. The function model describes the <br /> activities performed, whereas an organizational model describes one way of organizing human <br /> resources to perform those actions. <br /> Because activities performed by the County aze shown only once in the function model, the data <br /> and systems to support these activities will only be created once. Redundant data and systems <br /> can be avoided and the systems supporting a function model will be much more stable than <br /> systems built according to an organization chart. This stability derives from the fact that what an <br /> organization does changes much less than how it is organized. Because the Function Model <br /> identifies how the County administration operates, it is the foundation for building future <br /> information systems. <br /> The County's Plan does not provide a function model for the County. <br /> -16- <br /> <br />