Systems Architecture and The Problem with GIS
The cost savings in this functionality alone have not been grasped by the industry. Corporations will
likely implement more than three tiers – especially with regard to the application layer. For instance, if
the network resides on one layer, another layer may contain component applications which allow
upstream or downstream tracing of the network. These component applications for tracing can be shared
by Outage Analysis and Feeder Analysis -- without having to hard-wire the tracing component into each
different application.
The data layer, within three tier architecture, is a data warehouse, or it can be multiple databases. One
of the problems of integrating databases has been the proprietary nature of each of thes ystems. Vendor
agreement on shared, common access has given rise to different standards. Open Database Connectivityy
(ODBC) is one of the most agreed upon standards. Communication between the application layer and the
data layer will occur through technology such as ODBC (or Active X). A major change in systems design
will occur when vendors and developers take a data-centric view of information, rather than an
application/project view. The former assumes the data will be used by a variety of applications rather
than hard-coded into a specific design. AM/FM/GISs applications have generally been developed with a
graphic-centric view, rather than with a data-centric view
In the future, systems as we know them today will be thrown together, at will, by a variety of users (of
different ability), into applications we could never have imagined, and in a fraction of the time it took
them to be built the first time. It is very possible that the users who are currently familiar with the
Windows environment could excel in application development over those who come out of a more
traditional programming background. For the first time in history, market share has determined a stable
platform for developers and users upon which to rely. Through these design concepts users will be
enabled rather than stranded. But until then, the corporation will have all three tiers of systems with
which to deal.
(Please note: no references on Three Tier Technology have been provided, however, there is a wealth of
literature available on the subject.)
The Evolution of AM/FM/GIS Technology
Over the years, we have moved from isolated monolithic systems to “islands of automation,” and from
“islands of automation” to modular interconnected systems - with the later being the newest and least
implemented of thes ystems. There are certain benefits to having such a wide choice ofs ystems: the
ability to select best of breed, independence of particular vendors, scalability, and evolutionary change.
At the same time each company takes on the burden of managing the integration of unique solutions.
Traditional AM/FM/GIS systems do not quite fit the three tier architecture. These older systems are
monolithic and proprietary, or they are “islands of automation”; many of the newer systems are still two-tier,
but great attempts are being made to break out of the limitations these solutions offer. (This is a
reminder that the problems expressed here are not unique to AM/FM/GIS – take a look at SCADA - take
a look at Customer Information Systems) Many AM/FM/GISs use specialized tools and unique database
formats. The functionality provided is tied to unique user interfaces and other technical limitations that
limit the universal distribution of geographical data and analyses throughout the organization. The
systems which are customized installations leave little chance of upgrades when the underlying
technology changes. In fact, the utility can be assured that the code will have to be rewritten with the next
release. Figure 2. provides a general diagram of the components within an AM/FM/GIS. Following the
diagram is a description of each of those components and where they are in their evolutionary stage.
Figure2. Ageneral view depicting thecomponent pieces of an AMIFIWGIS
Components of an AM/FM/GIS
Graphic User Interface (GUI): First generation PCs did not have the performance to manage very large
graphical data sets and only recently have the machines had the power to drive the Windows bit mapped
display at a speed that comes close to direct vector graphics. As a result GIS systems have developed
their own user interface that often is embedded in their first generation version of Windows. Standards in
this area are still evolving.
The next generation of user interface integration from Microsoft, OleDB, will allow users to build
composite drawings and models created in different applications, while still allowing each component to
be edited. This type of capability will drive AM/FMGIS vendors to full support of standard user
interfaces. Buyers have to be careful when investigating new systems as not all “Windows compliant”
offerings will support either ActiveX or OleDB.
Tools/Commands: Most AM/FM/GISs are tool-boxes. Except for the vendors which focus solely on the
AM/FM industry, few vendors offer turnkey solutions which do not require a degree of customization. In
any case, it is often the tools or the commands which differentiate one product from another, Tools or
command functionality consists of data import and export, raster-to-vector conversion, cartographic
layout and design, spatial analysis, data and feature query, database links, etc.
While base functionality is similar between systems, as tool-sets they are all unique and proprietary.
However, it is in their full functionality that systems have competitive advantage. Again, AM/FM/GISs
are not unique in their proprietary offerings. Tool sets cannot be made available for operation on other
databases or applications unless that tool’s methods can be shared through compliance to a mutual
standards. If you are looking for a long-term solution, do not select on functionality alone.
In the future, the tool sets will be shared as a common and adopted method in the application layer of the
corporation. One AM/FM/GIS company is developing component-based tool sets. These tool sets act as
large objects, which will in turn, interact with other objects. These component-based tool-sets will allow
applications to be developed in a shorter period of time.
Language: The programming language used within the AM/FM/GIS is most often proprietary. Often, the
vendor creates their own language because the standard languages do not provide adequate access to
graphical features. These languages are usually far simpler than standard programming languages which
make them easy to learn. However, before the languages can be learned, the developer must have a clear
understanding of the underlying technology of AM/FM/GIS and what affect tools and commands have on
the AM/FMfGIS database. In this regard, it is very difficult to bring in a programmer from elsewhere in
the corporation without providing considerable training. Some vendors utilize languages which mimic
more standard languages. In this case, the new user only need learn the underlying technology.
Utilities tend to push the limits of GIS technology when building Ah4/FM/GIS systems. The utility
operating environment requires a robust programming environment -- where production-quality systems
can be built. Only a few vendors have taken a step toward this level of quality. But, to date, vendors have
not been pushed to implement robustness in their code or debugging tools. Interoperabilit y (Active X) at
the application level will reduce the issues of having to code interfaces between systems; it will also
ensure a degree of quality – as earning the “WIN ’95” logo does not come easily.
