Integration of Computerized Maintenance and GIS
Barbara Schmitz
GIS Global Technology Leader
CH2M HILL
P.O. Box 492478
Redding, California 96049
Abstract
Significant investment is required for capturing, storing, and manipulating large
quantities of utility asset information. Two of the most data intensive programs
include maintenance management systems (MMS) and geographic information
systems (GIS). Often, each of these programs is developed independently of the
other but often contain duplicate information for asset inventories. Many
organizations are looking for ways to integrate these systems to improve efficiency
of resources and data collection processes, and reduce data redundancy and
maintenance requirements. Early determination of integration options and
methodologies will result in significant increases in efficiency. This paper discusses
the major phases of an asset inventory project and important actions that need to be
considered. These actions include strategic information planning; software
acquisition, integration, and implementation; and training and support. This paper
presents lessons learned from all phases of asset data management activities and
highlights recommendations for successful integration of MMS and GIS. Most critical
to successful implementation is the need to understand in detail the business
processes and operational and management needs of the client.
Introsuction
As more organizations try to meet the continual demand to do more with fewer
resources, integration of information systems is becoming more critical. Significant
investment is required for capturing, storing, and manipulating large quantities of
utility asset information. Two of the most data intensive programs include
maintenance management systems (MMS) and geographic information systems
(GIS). Organizations often already have one or the other or both systems in place to
some degree. Often, each of these programs is developed independently of the other
but often contain duplicate information for asset inventories. Many organizations are
looking for ways to integrate these systems to achieve greater efficiency of resources,
improved data collection processes, and reduced data redundancy and maintenance
requirements.
Government agencies are moving toward integrating CMMS and GIS for several
reasons, but two of the primary drivers are GASB-34 and CMOM. The Government
Accounting Standards Board (GASB), in Statement No. 34 – Management’s
Discussion and Analysis for State and Local Governments (GASB-34) – requires state
and local governments to inventory their assets and report the value of those assets.
Assets reported in more than one database, often named differently in different
databases, complicate this process.
CMOM – Capacity, Management, Operation and Maintenance Program – is an EPA
regulatory program associated with the National Pollutant Discharge Elimination
System (NPDES). CMOM standards specify that each permittee must properly
manage, operate, and maintain all parts of their collection system, provide adequate
capacity to convey base flows and peak flows, mitigate impact of sanitary sewer
overflows, and notify parties exposed to pollutants associated with an overflow
event. Each permittee is also required to prepare a CMOM program summary and
make it available to the public. The tools that address CMOM include hydraulic
modeling, predictive modeling, decision analysis, field inspections, GIS, and master
planning. Again, data can typically be stored in two locations and can be difficult to
combine for use.
Significant investment is required for capturing, storing, and manipulating large
quantities of utility asset information. By determining integration options and
methodologies for pursuing integration at the onset, significant efficiencies can be
realized. Integration can be done at any time; however, the sooner in the life cycle of
a project that integration is initiated, the sooner savings can be realized. Following
are the major phases of implementing an integrated CMMS and GIS:
-
Strategic information planning
-
Software acquisition
-
Integration
-
Implementation
-
Training and ongoing support
Each integration project may have unique aspects, but each typically requires similar
strategies.
