Sie sind auf Seite 1von 86

Introducing ArcFM 8 Water

The ESRI Solution for Water, Wastewater, and Stormwater Management

Presentation Goals
To help you to understand
the ArcFM Water Product your options for implementing an ArcFM solution how to implement your ArcFM solution
strategies water model overview customization overview

Its not as hard as you might think!

ArcFM 8 Water Product
implementation options project strategies

Water Data Model

ArcInfo 8 GeoDatabase customization

Pre-release program

The ArcFM 8 Water Product

What is ArcFM Water?

An off-the-shelf utility solution
Water Wastewater Stormwater

An editing framework for As-Built water systems A extensible system for the development of complex enterprise solutions

What is ArcFM Water?

ArcFM Water focuses on the as-built, operations, and analysis stages of the facilities lifecycle
Analysis Design Operations

Construction As-Built

ArcFM Water
A product extension built on ArcInfo 8 and ArcSDE 8
ArcFM 8

ArcInfo 8

ArcSDE 8

ArcInfo 8 Provides
Sophisticated end-user applications for facilities management Comprehensive editing environment
CAD tools advanced symbology and labeling direct editing of data in a variety of formats
includes includes coverage coverage editing editing support support

Map production / map layout environment Industry-leading development tools and languages

ArcSDE 8 Provides
1 user to enterprise deployment

Relational database storage technology

Single database for all data

Long transactions and versioning

multiple users, reconciliation of design and as-built changes

ArcFM Water Product

Provides a generic facilities management solution Establishes a water model standard Documented, supported product from ESRI Reviewed and built with input from many users and business partners Provides a customizable framework for enterprise-level solutions

What ArcFM 8 Provides

Utility functionality in a core GIS platform Easy customization environments
ArcCatalog, CASE, VB

Core ArcFM solution can be extended

data model components tools user interface

ArcFM Water Benefits

Component technology
large-scale component reuse lower lifecycle costs shorter implementation timeframes

Common framework for third party tools and applications

reduced customization

Water Model Benefits

Efficient systems analysis, design and development Reduced data conversion / migration effort Promotes sharing of product enhancements and third party products

ArcFM Water 8 Deliverables

Standard data model
features, properties, etc. in UML

Software components
custom features, 8.0 desktop for editing and network analysis tools

Documentation Samples
database and tools

ArcFM Water Demo

Demo Introduction
A simple implementation example Core tools and user interface Coverage data migrated to MS Access and ArcSDE 8 Migration process is really easy
Once you know how to do it Plan on a couple iterations to get things right

Implementation Options

Implementation Options
Use ArcInfo 8 and keep data in coverages
ArcInfo 8


Implementation Options
Use ArcInfo 8 and migrate data to simple features in a GeoDatabase
ArcInfo 8


ArcSDE 8

Implementation Options
Use ArcInfo 8 / ArcFM 8 and migrate data to custom features
ArcFM 8

ArcInfo 8

ArcSDE 8

Implementation Steps
Plan your data migration path Define additional functionality / data requirements Determine if the ArcFM Water model meets your needs
can you configure what you need? do you need to create custom features?

Implementation Steps
Build target database schema
configure (smaller - ArcCatalog) customize (larger - UML, schema wizard)

Migrate / convert data

use ESRI tools to migrate to simple features use ESRI tools to migrate to custom / ArcFM features

Build applications

Project Strategies

Project Strategies
To minimize risk and reduce development effort
adopt the core ArcFM model

Model can be configured for your needs

add and relabel properties establish domains specify relationships configure symbology, labels, etc.

Project Strategies
Critical success factors for enterprise solutions development
budget and plan for adoption of new technology consider procuring outside assistance for initial design and setup
accelerate project implementation, reduce risk

Project Strategies
ArcInfo 8 architecture introduces additional protocols to ArcFM projects
augmenting is easy (classes and properties) removing classes is allowed removing properties is not allowed it will be more difficult to leverage future product enhancements if you build your own components from scratch

ArcFM Solutions Model

ArcFM Solutions Model

ESRI teams with business partners to provide customized solutions
business domain experts component developers systems integrators

Built to be the COTS tool of choice for utility enterprise solutions

ArcFM Solutions Model

Custom Tools, Third Party Products

ArcFM 8

ArcInfo 8

ESRI Product Development

ArcFM Development Consortium

ArcFM Water is an ESRI product Development Consortium includes
Water - ESRI Electric and Gas - Miner and Miner Telecom - Telcordia

A new marketplace for developers and systems integrators

ArcFM Data Model

Data Model Goals

Essential set of classes for water facilities management Adoptable for production use with minimal configuration Focus on As-Built editing and mapping Easy to customize

ArcFM Data Model

ArcInfo 8 extension
custom feature classes relationships, validation rules, etc. custom network analysis tools editing automation

Combined model
water wastewater and storm water

Water Model Subsystems

Model is broken into several subsystems
Devices Lines Facilities and Structures Miscellaneous Features Cathodic Protection

Pumps, motors, aerators, warehouse valves, warehouse meters, chemical injectors, generators ...

Represents equipment and other components that are found in other containing entities (e.g., pump station) Modeled as non-spatial entities
why non-spatial?

May be associated with other entities that are in an active network

asset tracking

Laterals, gravity mains, pressure mains, interconnect lines, tunnels ... Used for representing pipes and other entities that are used for transmission of water and wastewater Modeled as a linear chain of connected network elements Network connectivity auto maintained

Valves, fittings, manholes, hydrants, meters, sampling stations, clearwells ...

Basic connectors for water networks Participate in the transmission and control of water in the network
often used to connect Lines

Modeled as point / polygon entities that have network connectivity

Pump stations, storage facilities, treatment plants, storage basins ...

Larger entities that contain other entities Modeled as complex entities that maintain network connectivity
may have inbound and outbound connections

Relationships with multiple Devices

Miscellaneous Features
Vaults, leaks, casements, scada sensors, thrust protection, cathodic protection ...

Simple spatial entities that are found in the water network Do not participate in the network
no network connectivity

Cathodic Protection
Ground beds, anodes, rectifiers, test stations, reference cells

A comprehensive CP subsystem Used on large transmission systems

pressure mains

Simple anode / rectifier devices included in miscellaneous features

for simpler modeling requirements

ArcInfo 8 GeoDatabase

ArcInfo 8 GeoDatabase
A new geographic data model Stored in an RDBMS Features with behavior Topological relationships

Object Classes
Stores objects and their properties Non-spatial (e.g., parcel owners) Objects have unique system identifiers Like objects grouped into an object class Objects in an object class have the same
properties - stored in the table as attributes behavior - implemented as a component

Object Classes
A table stores an ObjectClass Type Axial Inlet Size 24 ...

PUMP A row stores an Object OID 518

Feature Classes
Object classes which store spatial objects (i.e., features) Features are objects with required shape Store spatial objects with the same
properties - stored in the table as attributes behavior - implemented as a component

Feature Classes
FeatureClass (table) LATERAL OID Feature (row) 524 Shape Type ... ... X,Y,Z,M, ... Domestic

Feature Geometry
Points Multipoints Lines Polygons

1 Line

1 Poly

X, Y
Z, M (optional) Integer coordinate storage Separate coordinate domain for X, Y, Z, M values
2 Paths 3 Rings (closed paths) Segments Line Circular arc

Bezier curve

Feature Datasets
Container for feature classes
shared spatial reference

Analogous to a coverage
less restrictive

May also contain

relationship classes geometric networks

Modeling a subsystem

Describe the legal values of a field type
used to ensure attribute integrity

Can be shared among classes Uniquely named Types of domains

range: mains can be 40 to 100 psi coded value: mains have diameter of 10, 24 or 36 inches

Range domains
water distribution mains can have a pressure between 40 and 100 psi

Coded value domains

water distribution mains can have a diameter of 10, 24 or 36 inches

Different types of features or objects in an object class
same attributes and behavior can have different default values and domains for each field

Example: in a feature class which stores Mains

steel mains can be 0 to 150 psi PVC mains can be 0 to 100 psi both are subtypes of the Mains feature class

Default Values
Establish default values based upon object class, field, and subtype triplet
e.g., (Main, Pressure, PVC) = 80 psi

Enable default initialization of objects once subtype is selected

ArcMap property inspectors

An association between objects
feature to object, feature to feature, etc.

Stored in a relationship class Related objects can message each other

origin to destination, destination to origin, both, neither can trigger behavior (cascade delete, move to follow, custom)

Composite Composite relationship, relationship, Pole Pole to to Transformer Transformer

Select Select a a pole pole and and move move it it

the the transformer transformer follows follows

Geometric Networks
Topological relationship between feature classes Used to model network systems Topology:
based upon geometric coincidence always live

Feature classes in the same dataset

Geometric Networks
Valve Meter Lateral DistMain TransMain

Geometric Network

Network Feature Classes

Network Feature Classes

Network features live in a geometric network Directly support network analysis Types:
simple junction simple edge complex junction complex edge

Connectivity Rules
Help you maintain a valid network Connectivity rules include
edge-junction rules

edge-edge rules
permissible junction types default junction type

ArcFM Data Model














Aspatial objects Associated with structures and facilities

Based on complex edges Topology auto maintained Examples include
PressurizedMains GravityMains LateralLines
PressurizedMain ComplexEdgeFeature






Basic connectors for water networks Participate in the transmission and control of water in the network Based upon simple junctions Examples include

Valves Fittings Meters







Represent complex network structures Based on complex junctions Relationships with multiple devices Examples include

pumping stations split manholes storage basins








Miscellaneous Features
Simple spatial features that are associated with the water network
do not participate in the network












Cathodic Protection
A comprehensive CP subsystem Used on large transmission systems Options for simple anode / rectifier devices included in LineProtector class









Data Model
Models available in pre-release package
analysis formal UML detailed design

Implemented as COM components Many possibilities for configuration and customization of the model

Customizing ArcFM Water

Customizing Existing Object Classes

Define a new feature class (object class)
add attribute fields, set geometry type, spatial reference, etc.

Import an object class

import template from another object class in any GeoDatabase

Edit the behavior of an object class

set subtypes, domains, relationships, etc.

Modeling Additional Behavior

System can usually be customized without creating custom objects If it is necessary to create additional custom behavior on the object
nearly any COM compliant language can be used: C++, VB, Delphi CASE tools and ESRI Code Generation and Schema Wizards make this a lot easier

Programming Custom Objects

Custom objects requires programming in COM-compliant language
only VC++ or Delphi (dont ask about VB) custom object classes can use VB or VJ++

CASE tools make it easier

ESRI Provides Vanilla Objects

esriCoreRow.1 esriCoreObject.1 esriCoreFeature.1 esriCoreSimpleJunctionFeature.1 esriCoreComplexJunctionFeature.1 esriCoreSimpleEdgeFeature.1 esriCoreComplexEdgeFeature.1 Row Object Feature NetworkFeature 2..*


* EdgeFeature





Custom Objects
Developers create custom objects and intricate data schemas No difference between ESRI supplied and developer-supplied custom objects
merely support required interfaces augments with new interfaces

Custom Objects
What you will need
UML and MS Repository aware CASE tool
Visio Professional or Enterprise

Visual C++ or Delphi GeoDatabase data model diagram ArcCatalog OO programming skills and knowledge of COM

Creation Process
Create the object model
3rd party CASE tool

Export to the Microsoft Repository

3rd party CASE tool UML export wizard

Generate stub-code
ESRI supplied wizard (VC++ only)

Implement custom behavior

you program into the stubs

Create the GeoDatabase schema

Object Class Extensions

Non-spatial table-centric customization Extension of the object class
not a subclassing of an object

Appropriate for
storing class variables (C++ static variables) custom validation custom property inspectors class level behavior

Object Class Extensions

Workspace Dataset GeometricNetwork GeoDataset







Object Class Extensions

Completely optional
GeoDatabase tests when appropriate

Implementable in VB (no aggregation) Large collection of specified interfaces

almost all are optional GeoDatabase tests when appropriate

One class extension per object class

Pre-Release Program

Pre-Release Program
Pre-release package will be available for download on the ArcFM Web Page Submit application for the program Limited number will be selected after UC

Pre-Release Program
Subscription includes
pre-release software documentation scheduled release technical support

Channel between customers and development Subscription ends with general release

Feedback Wed Like

Things you have a hard time figuring out based on documentation and examples Tips and Tricks that you develop Things that are complex to do the way the software has been designed Ideas for new tools Specific functionality requirements, business scenarios

For Further Info

For Further Info

Relevant ArcInfo 8 sessions:
GeoDatabase Design using CASE Using ArcCatalog to Define and Manage the GeoDatabase Programming Custom Objects with ArcInfo 8

For Further Info

David Taylor. Object Technology: A Managers Guide. 2nd Ed., Addison-Wesley, 1997. David Chappell. Understanding ActiveX and OLE: A Guide for Developers and Managers. Microsoft Press, 1996. Bertrand Meyer. Object-Oriented Software Construction. Prentice Hall, 1997.

ArcFM Water

A force multiplier of unprecedented scale