IntroducingArcFM 8 Water

IntroducingArcFM 8 Water

The ESRI Solution forWater, Wastewater, and

Stormwater Management

The ESRI Solution forWater, Wastewater, and

Stormwater Management

Presentation GoalsPresentation 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

It’s not as hard as you might think!

• 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

It’s not as hard as you might think!

AgendaAgenda

• ArcFM 8 Water Product– implementation options– project strategies

• Water Data Model– ArcInfo 8 GeoDatabase– customization

• Pre-release program

• ArcFM 8 Water Product– implementation options– project strategies

• Water Data Model– ArcInfo 8 GeoDatabase– customization

• Pre-release program

The ArcFM 8 Water ProductThe ArcFM 8 Water Product

What is ArcFM Water?What is ArcFM Water?• An off-the-shelf utility solution

– Water– Wastewater– Stormwater

• An editing framework for As-Built watersystems

• A extensible system for the developmentof complex enterprise solutions

• An off-the-shelf utility solution– Water– Wastewater– Stormwater

• An editing framework for As-Built watersystems

• A extensible system for the developmentof complex enterprise solutions

What is ArcFM Water?What is ArcFM Water?• ArcFM Water focuses on the as-built,

operations, and analysis stages of thefacilities lifecycle

• ArcFM Water focuses on the as-built,operations, and analysis stages of thefacilities lifecycle

DesignAnalysis

Operations

ConstructionAs-Built

text

ArcFM WaterArcFM Water• A product extension built on ArcInfo 8

and ArcSDE 8• A product extension built on ArcInfo 8

and ArcSDE 8

ArcInfo 8

ArcSDE 8

ArcFM 8

ArcInfo 8 ProvidesArcInfo 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 coverage editing support

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

languages

• Sophisticated end-user applications forfacilities management

• Comprehensive editing environment– CAD tools– advanced symbology and labeling– direct editing of data in a variety of formats

• includes coverage editing support

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

languages

ArcSDE 8 ProvidesArcSDE 8 Provides

• Scalability– 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

• Scalability– 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 ProductArcFM 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

• Provides a generic facilities managementsolution

• 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 ProvidesWhat 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

• 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 BenefitsArcFM Water Benefits

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

• Common framework for third party toolsand applications– reduced customization

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

• Common framework for third party toolsand applications– reduced customization

Water Model BenefitsWater Model Benefits• Efficient systems analysis, design and

development• Reduced data conversion / migration effort• Promotes sharing of product enhancements

and third party products

• Efficient systems analysis, design anddevelopment

• Reduced data conversion / migration effort• Promotes sharing of product enhancements

and third party products

ArcFM Water 8 DeliverablesArcFM Water 8 Deliverables• Standard data model

– features, properties, etc. in UML• Software components

– custom features, 8.0 desktop for editing andnetwork analysis tools

• Documentation• Samples

– database and tools

• 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 DemoArcFM Water Demo

Demo IntroductionDemo 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

• 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 OptionsImplementation Options

Implementation OptionsImplementation Options• Use ArcInfo 8 and keep data in

coverages• Use ArcInfo 8 and keep data in

coverages

Coverages

ArcInfo 8

Implementation OptionsImplementation Options• Use ArcInfo 8 and migrate data to simple

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

features in a GeoDatabase

ArcInfo 8

Coverages ArcSDE 8

Implementation OptionsImplementation Options• Use ArcInfo 8 / ArcFM 8 and migrate data

to custom features• Use ArcInfo 8 / ArcFM 8 and migrate data

to custom features

ArcInfo 8

ArcSDE 8

ArcFM 8

Implementation StepsImplementation 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?

• 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 StepsImplementation 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

• 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 StrategiesProject Strategies

Project StrategiesProject 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.

• To minimize risk and reduce developmenteffort– 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 StrategiesProject 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

• Critical success factors for enterprisesolutions development– budget and plan for adoption of new

technology– consider procuring outside assistance for

initial design and setup• accelerate project implementation, reduce risk

Project StrategiesProject 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 owncomponents from scratch

• ArcInfo 8 architecture introducesadditional 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 owncomponents from scratch

ArcFM Solutions ModelArcFM Solutions Model

ArcFM Solutions ModelArcFM Solutions Model

• ESRI teams with business partners toprovide customized solutions– business domain experts– component developers– systems integrators

• Built to be the COTS tool of choice forutility enterprise solutions

• ESRI teams with business partners toprovide customized solutions– business domain experts– component developers– systems integrators

• Built to be the COTS tool of choice forutility enterprise solutions

ArcFM Solutions ModelArcFM Solutions Model

ArcInfo 8

ArcFM

8Config

CustomTools,ThirdParty

Products

ESRI Product Development

Solution

ArcFM Development ConsortiumArcFM 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 andsystems integrators

• ArcFM Water is an ESRI product• Development Consortium includes

– Water - ESRI– Electric and Gas - Miner and Miner– Telecom - Telcordia

• A new marketplace for developers andsystems integrators

ArcFM Data ModelArcFM Data Model

Data Model GoalsData 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

• Essential set of classes for waterfacilities management

• Adoptable for production use withminimal configuration

• Focus on As-Built editing and mapping• Easy to customize

ArcFM Data ModelArcFM 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

• 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 SubsystemsWater Model Subsystems

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

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

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

• Represents equipment and other componentsthat 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 arein an active network– asset tracking

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

• Represents equipment and other componentsthat 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 arein an active network– asset tracking

LinesLinesLaterals, gravity mains, pressure mains,interconnect lines, tunnels ...

• Used for representing pipes and other entitiesthat are used for transmission of water andwastewater

• Modeled as a linear chain of connectednetwork elements

• Network connectivity auto maintained

Laterals, gravity mains, pressure mains,interconnect lines, tunnels ...

• Used for representing pipes and other entitiesthat are used for transmission of water andwastewater

• Modeled as a linear chain of connectednetwork elements

• Network connectivity auto maintained

FacilitiesFacilitiesValves, 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 thathave network connectivity

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 thathave network connectivity

StructuresStructuresPump stations, storage facilities, treatmentplants, 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

Pump stations, storage facilities, treatmentplants, 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 FeaturesMiscellaneous Features

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

• Simple spatial entities that are found inthe water network

• Do not participate in the network– no network connectivity

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

• Simple spatial entities that are found inthe water network

• Do not participate in the network– no network connectivity

Cathodic ProtectionCathodic ProtectionGround 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

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 GeoDatabaseArcInfo 8 GeoDatabase

ArcInfo 8 GeoDatabaseArcInfo 8 GeoDatabase

• A new geographic data model• Stored in an RDBMS• Features with behavior• Topological relationships

• A new geographic data model• Stored in an RDBMS• Features with behavior• Topological relationships

Object ClassesObject 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

• 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 ClassesObject Classes

A row storesan Object

TypeOID Inlet Size . . .518 Axial 24

PUMP

A table storesan ObjectClass

Feature ClassesFeature Classes

• Object classes which store spatialobjects (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

• Object classes which store spatialobjects (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 ClassesFeature Classes

Feature(row)

ShapeOID524 X,Y,Z,M, ...

LATERALTypeDomestic

. . .

. . .

FeatureClass (table)

• X, Y• Z, M (optional)• Integer coordinate storage• Separate coordinate domain for X, Y, Z, M values

Feature GeometryFeature GeometryPoints Multipoints PolygonsLines

Segments

Beziercurve

Line Circulararc

3 Rings(closed paths)

2 Paths

1 Poly1 Line

Feature DatasetsFeature Datasets• Container for feature classes

– shared spatial reference• Analogous to a coverage

– less restrictive• May also contain

– relationship classes– geometric networks

• Modeling a subsystem

• Container for feature classes– shared spatial reference

• Analogous to a coverage– less restrictive

• May also contain– relationship classes– geometric networks

• Modeling a subsystem

DomainsDomains• 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

• 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

DomainsDomains• Range domains

– water distribution mains can have apressure between 40 and 100 psi

• Coded value domains– water distribution mains can have a

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 adiameter of 10, 24 or 36 inches

SubtypesSubtypes• 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

• Different types of features or objects in anobject 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 ValuesDefault Values• Establish default values based upon

object class, field, and subtype triplet– e.g., (Main, “Pressure”, “PVC”) = 80 psi

• Enable default initialization of objectsonce subtype is selected– ArcMap property inspectors

• Establish default values based uponobject class, field, and subtype triplet– e.g., (Main, “Pressure”, “PVC”) = 80 psi

• Enable default initialization of objectsonce subtype is selected– ArcMap property inspectors

RelationshipsRelationships• 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, moveto follow, custom…)

• 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, moveto follow, custom…)

RelationshipsRelationshipsComposite relationship, Pole to TransformerComposite relationship, Pole to Transformer

Select a pole and move itSelect a pole and move it …the transformer follows…the transformer follows

Geometric NetworksGeometric Networks

• Topological relationship between featureclasses

• Used to model network systems• Topology:

– based upon geometric coincidence– always live

• Feature classes in the same dataset

• Topological relationship between featureclasses

• Used to model network systems• Topology:

– based upon geometric coincidence– always live

• Feature classes in the same dataset

Geometric NetworksGeometric Networks

DistMain

Meter

TransMain

Lateral

Valve

Network Feature ClassesNetwork Feature Classes

Geometric NetworkGeometric Network

Network Feature ClassesNetwork Feature Classes• Network features live in a geometric

network• Directly support network analysis• Types:

– simple junction– simple edge– complex junction– complex edge

• Network features live in a geometricnetwork

• Directly support network analysis• Types:

– simple junction– simple edge– complex junction– complex edge

Connectivity RulesConnectivity Rules• Help you maintain a valid network• Connectivity rules include

– edge-junction rules• cardinality

– edge-edge rules• permissible junction types• default junction type

• Help you maintain a valid network• Connectivity rules include

– edge-junction rules• cardinality

– edge-edge rules• permissible junction types• default junction type

ArcFM Data ModelArcFM Data Model

DevicesDevices

• Aspatial objects• Associated with structures and facilities• Aspatial objects• Associated with structures and facilities

ChemicalInjectorAeratorMotorPump

Device

Object

Generator

StandByPower

AlternatePower

WarehouseDevice

WarehouseHydrantWarehouseMeter WarehouseValve

LinesLines

• Based on complex edges• Topology auto maintained• Examples include

– PressurizedMains– GravityMains– LateralLines

• Based on complex edges• Topology auto maintained• Examples include

– PressurizedMains– GravityMains– LateralLines

MainLine

PressurizedMain GravityMain

LateralLine

WaterLine

ComplexEdgeFeature

NetworkLine

FacilitiesFacilities• 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

• 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 Valve SamplingStationHydrant Meter

Facility

SimpleJunctionFeature

Fitting

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

– pumping stations– split manholes– storage basins

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

– pumping stations– split manholes– storage basins

Structure

TreatmentPlantPumpStation ProductionWellStorageFacility

EnclosedStorageFacility StorageBasin

ComplexJunctionFeature

Miscellaneous FeaturesMiscellaneous Features• Simple spatial features that are

associated with the water network– do not participate in the network

• Simple spatial features that areassociated with the water network– do not participate in the network

WaterFeature

ScadaSensor LineProtector

Casings CathodicProtectionMeterBoxValveVault

UndergroundEnclosure

Vault

Feature

ThrustProtection

SpatialOperationsRecord

Cathodic ProtectionCathodic Protection

• A comprehensive CP subsystem• Used on large transmission systems• Options for simple anode / rectifier

devices includedin LineProtector class

• A comprehensive CP subsystem• Used on large transmission systems• Options for simple anode / rectifier

devices includedin LineProtector class

CathodicProtectionWire

SimpleEdge

CathodicProtectionDevice

Anode Rectifier CPTestStation

SimpleJunction

GroundBed CPReferenceCell

Data ModelData 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

• 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 WaterCustomizing ArcFM Water

Customizing Existing Object ClassesCustomizing 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 inany GeoDatabase

• Edit the behavior of an object class– set subtypes, domains, relationships, etc.

• 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 inany GeoDatabase

• Edit the behavior of an object class– set subtypes, domains, relationships, etc.

Modeling Additional BehaviorModeling Additional Behavior

• System can usually be customizedwithout creating custom objects

• If it is necessary to create additionalcustom 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

• System can usually be customizedwithout creating custom objects

• If it is necessary to create additionalcustom 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 ObjectsProgramming Custom Objects

• Custom objects requires programming inCOM-compliant language– only VC++ or Delphi (don’t ask about VB)– custom object classes can use VB or VJ++

• CASE tools make it easier

• Custom objects requires programming inCOM-compliant language– only VC++ or Delphi (don’t ask about VB)– custom object classes can use VB or VJ++

• CASE tools make it easier

ESRI Provides Vanilla ObjectsESRI Provides Vanilla ObjectsesriCoreRow.1esriCoreObject.1esriCoreFeature.1esriCoreSimpleJunctionFeature.1esriCoreComplexJunctionFeature.1esriCoreSimpleEdgeFeature.1esriCoreComplexEdgeFeature.1

Feature

NetworkFeature

JunctionFeature EdgeFeature

SimpleJunction ComplexJunction SimpleEdge ComplexEdge

Object

Row

2..* *

Custom ObjectsCustom Objects

• Developers create custom objects andintricate data schemas

• No difference between ESRI supplied anddeveloper-supplied custom objects– merely support required interfaces– augments with new interfaces

• Developers create custom objects andintricate data schemas

• No difference between ESRI supplied anddeveloper-supplied custom objects– merely support required interfaces– augments with new interfaces

Custom ObjectsCustom 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

• 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 ProcessCreation 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

• 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 ExtensionsObject 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

• 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 ExtensionsObject Class ExtensionsWorkspace Dataset

GeoDataset

FeatureDataset

ObjectClass

FeatureClass

Object

Feature

GeometricNetwork

ObjectClassExtension

Object Class ExtensionsObject 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

• 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 ProgramPre-Release Program

Pre-Release ProgramPre-Release Program

• Pre-release package will be available fordownload on the ArcFM Web Page

• Submit application for the program• Limited number will be selected after UC

• Pre-release package will be available fordownload on the ArcFM Web Page

• Submit application for the program• Limited number will be selected after UC

Pre-Release ProgramPre-Release Program• Subscription includes

– pre-release software– documentation– scheduled release– technical support

• Channel between customers anddevelopment

• Subscription ends with general release

• Subscription includes– pre-release software– documentation– scheduled release– technical support

• Channel between customers anddevelopment

• Subscription ends with general release

Feedback We’d LikeFeedback We’d 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

• Things you have a hard time figuring outbased 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 InfoFor Further Info

For Further InfoFor Further Info

• Relevant ArcInfo 8 sessions:– GeoDatabase Design using CASE– Using ArcCatalog to Define and Manage the

GeoDatabase– Programming Custom Objects with ArcInfo 8

• Relevant ArcInfo 8 sessions:– GeoDatabase Design using CASE– Using ArcCatalog to Define and Manage the

GeoDatabase– Programming Custom Objects with ArcInfo 8

For Further InfoFor Further Info• Literature

– David Taylor. Object Technology: AManager’s Guide. 2nd Ed., Addison-Wesley,1997.

– David Chappell. Understanding ActiveX andOLE: A Guide for Developers and Managers.Microsoft Press, 1996.

– Bertrand Meyer. Object-Oriented SoftwareConstruction. Prentice Hall, 1997.

• Literature– David Taylor. Object Technology: A

Manager’s Guide. 2nd Ed., Addison-Wesley,1997.

– David Chappell. Understanding ActiveX andOLE: A Guide for Developers and Managers.Microsoft Press, 1996.

– Bertrand Meyer. Object-Oriented SoftwareConstruction. Prentice Hall, 1997.

ArcFM WaterArcFM Water

A force multiplier of unprecedented scale