Solving fundamental issues when integrating WAM (Works & Asset Management) Systems with GIS

Abstract
It is a now recognised and accepted that there are substantial business benefits of using Geographical Information Systems for the design and documentation of utility and telecommunication networks. Asset management packages with full work management, scheduling and dispatch capabilities have been equally successful when deployed within the operational part of the same organisation. The division of these two applications into disparate systems is more a result of development history than of user requirement.

An examination of the scope and functionality of these systems show there are additional and far reaching benefits that can be gained by the integration of these complimentary packages. There are however potential conflicts that may occur due to the way in which these systems manipulate and manage essentially the same data.

This paper will show that if a conceptual framework is first established that properly positions design systems with works and asset management systems; the development of key operational applications that meet end user requirements and provide real business benefits can be achieved. Practical production examples are given.

Introduction
Utility and telecommunication companies worldwide are facing increasing pressures to operate in a more productive and cost effective way. As global deregulation in these industries becomes more widespread so the pressure of competition increases. In this competitive environment, utility and telecommunication companies are trying to reorganise, restructure, downsize and outsource in an effort to streamline their business.

The business process consists of a complex range of inter-related tasks with no single one determining the success or failure of the business. Similarly there is no single IT solution on which an organisation’s business can depend. Historically IT solutions have been procured by different departments with unique objectives, schedules and budget constraints. Business Process Reengineering however is changing the IT focus from producing systems which support individual tasks towards an integrated solution approach.

The key to utility and telecommunication company’s success are its assets - its network and customers. The smooth and efficient running of a organisation’s network provides the goods and services that the company’s customers demand. This paper examines the role of GIS and Work and Asset Management (WAM) within the organisation. These systems are fundamental to the success of business process re-engineering upon which these companies are embarking.

The first part of the paper provides an overview of GIS and WAM, examining the scope and functionality of these systems. The following section focuses on the business benefits to be found by integrating these complementary products. A section then considers the problems that may be encountered due to the inherent conceptual differences between the packages. Finally, case studies highlight benefits that are being achieved in production today

GIS: Work and asset management
Utility and telecommunication companies typically have a number of existing legacy systems. These systems manage separate islands of data and fulfil very specific business tasks supporting many of the customer and engineering needs of the business. Examples of these are network management systems, GIS, customer information systems, billing systems and WAM systems. By looking at the data and services each system provides, areas of overlap can be identified. Overlapping areas of the business results in costs being incurred, such as data duplication and data concurrency resulting in a lack of data integrity and operating inefficiency. The following outlines the scope of GIS and WAM systems.

GIS enables the effective planning, design and maintenance of an organisation’s network assets with the ability to graphically visualise and spatially analyse the network. It does this by providing a realistic model of objects forming ‘background’ and ‘foreground’ data.