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
Agenda
ArcFM 8 Water Product
implementation options project strategies
Pre-release program
An editing framework for As-Built water systems A extensible system for the development of complex enterprise solutions
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
Scalability
1 user to enterprise deployment
Software components
custom features, 8.0 desktop for editing and network analysis tools
Documentation Samples
database and tools
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
Coverages
Implementation Options
Use ArcInfo 8 and migrate data to simple features in a GeoDatabase
ArcInfo 8
Coverages
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)
Build applications
Project Strategies
Project Strategies
To minimize risk and reduce development effort
adopt the core ArcFM model
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 8
ArcInfo 8
Combined model
water wastewater and storm water
Devices
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?
Lines
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
Facilities
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
Structures
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
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
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 ...
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
Modeling a subsystem
Domains
Describe the legal values of a field type
used to ensure attribute integrity
Domains
Range domains
water distribution mains can have a pressure between 40 and 100 psi
Subtypes
Different types of features or objects in an object class
same attributes and behavior can have different default values and domains for each field
Default Values
Establish default values based upon object class, field, and subtype triplet
e.g., (Main, Pressure, PVC) = 80 psi
Relationships
An association between objects
feature to object, feature to feature, etc.
Relationships
Composite Composite relationship, relationship, Pole Pole to to Transformer Transformer
Geometric Networks
Topological relationship between feature classes Used to model network systems Topology:
based upon geometric coincidence always live
Geometric Networks
Valve Meter Lateral DistMain TransMain
Geometric Network
Connectivity Rules
Help you maintain a valid network Connectivity rules include
edge-junction rules
cardinality
edge-edge rules
permissible junction types default junction type
Devices
Object
Device
Pump
Motor
StandByPower
Aerator
ChemicalInjector
WarehouseDevice
Generator
AlternatePower
WarehouseMeter
WarehouseHydrant
WarehouseValve
Lines
Based on complex edges Topology auto maintained Examples include
PressurizedMains GravityMains LateralLines
PressurizedMain ComplexEdgeFeature
NetworkLine
WaterLine
MainLine
LateralLine
GravityMain
Facilities
Basic connectors for water networks Participate in the transmission and control of water in the network Based upon simple junctions Examples include
SimpleJunctionFeature
Facility
Fitting
Hydrant
Valve
SamplingStation
Meter
Structures
Represent complex network structures Based on complex junctions Relationships with multiple devices Examples include
ComplexJunctionFeature
Structure
PumpStation
StorageFacility
TreatmentPlant
ProductionWell
EnclosedStorageFacility
StorageBasin
Miscellaneous Features
Simple spatial features that are associated with the water network
do not participate in the network
Feature
WaterFeature
ScadaSensor
UndergroundEnclosure
SpatialOperationsRecord
LineProtector
Vault
ValveVault
MeterBox
Casings
CathodicProtection
ThrustProtection
Cathodic Protection
A comprehensive CP subsystem Used on large transmission systems Options for simple anode / rectifier devices included in LineProtector class
SimpleJunction
SimpleEdge
CathodicProtectionDevice
CathodicProtectionWire
GroundBed
Anode
Rectifier
CPTestStation
CPReferenceCell
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
JunctionFeature
* EdgeFeature
SimpleJunction
ComplexJunction
SimpleEdge
ComplexEdge
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
Generate stub-code
ESRI supplied wizard (VC++ only)
Appropriate for
storing class variables (C++ static variables) custom validation custom property inspectors class level behavior
FeatureDataset
Object
ObjectClass
ObjectClassExtension
Feature
FeatureClass
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
ArcFM Water