Title: Regional Municipality of Peel
1Regional Municipality of Peel
Growing Your Hansen System
2gt one million population
gt6,000 km (3600 mi.) of water main
gt300,000 households
gt3000 km (1800 mi) sanitary sewer
gt 25,000 hydrants
gt400 km (240 mi.) of road
gt40 pumping stations
gt100 bridges
Region of Peel winner of the 2002 Hansen Power
User award in Canada
3Hansen and Peel-when it all began
- Need Implement an electronic system for cradle
to grave tracking of all - information relating to Public Works
infrastructure assets - (Hansen system purchased in late 1990s-Currently
using version 7.6.1 and - testing version 7.7 )
- Results Groups of existing systems communicating
with Hansen as the source - of all asset inventory
- Bonus Hansen able to provide functionalities
beyond asset inventory - Service Contract
- Customer Service module and Knowledge base
- Fleet/Materials/Supplies management
- Work Order
- Work Notice
4Current Data Flow Diagram for AIMS (Hansen)
Customer Service Data
Asset Spatial Data
As Built Asset Data
Water Model
AutoMail
MailAuditor
AIMS (Hansen)
Infracarta
GIS
AIMS Reporting
Financial Data
IPFS
Batch Header
AIMS Payroll and GL Interface
PSoft
5What are we using it for ?
- Hansen and Geo Media applications are the front
end user systems of choice to manage Public Works
infrastructure assets at Peel - The information in the Hansen database is used to
support - benchmarking initiatives
- performance standards
- preventative maintenance programs for assets
- asset valuation
- budget planning for capital assets
- customer service management
6Customer Service Request
Roadways
Asset valuation
Efficient
Pumping stations
Asset planning
Work Order
Assets
Water mains
Functions
Parts/Materials module
Customer Service Corporate Reporting Asset
Management Financial Management
Sanitary Sewers
Activity cost development
Improved
Budget planning
Permit module
Vehicles
Service contract management
Equipment
Benchmarking
Street furniture
Inspection module
Preventative maintenance
System Connections
Asset Inventory/Work Order/Interfaces
General ledger Payroll
Planning models
GIS
IPFS
7Newly Implemented Initiatives
- Bringing info to field staff
- Population of road infrastructure data and street
furniture (ongoing) - Comprehensive training programs/schedules on
Hansen and peripheral systems for staff - Service Contract module for tracking managed
competition - Enhancement of the Knowledge Base in Service
Request
8Planned Initiatives
- GIS-Hansen bi-directional
- Expand info to the field
- Create means to allow corporate employees to
access information in Hansen - Interface between CCTV inspection data and Hansen
asset data - Link remaining assets to capital financial
planning system - Provide web access to public for on-line permit
application - Complete implementation of Roadway module
9Successes
- Linkages to other systems streamlines and speeds
up the flow of - information between departments and reduces paper
processing. - Strong partnership with IT and Hansen
Technologies - Infracarta (GIS-Hansen interface)
- Interface link to batch info from Hansen to
corporate finance systems - Auto-mail link between Hansen and e-mail
- Hansen assets linked to financial capital
planning system - Example
10Fleet Services Information Flow
Fuel System (linked to asset in Hansen)
Internal Customer
Interfaced (batch) to PSoft GL
PM schedule request (auto-generated)
Auto Mail (Internal customer notification)
Fleet Service request (demand generated)
Auto generated
Data entry generated
Hansen PM Work Order
Associated to asset in Hansen
Interfaced (batch) to PSoft general ledger
Interfaced (batch) to PSoft payroll
11Challenges
- Corporate support
- Client support
- Data compilation and quality assurance
- Resource planning
12Expected resource changes in implementing complex
e-information systems
benchmarking
performance
Greater demand for info outcomes-New system
customer service
planning
More manual data entry/collection- resources
required
More IT resources?
Old systems-less outcomes required
More information analysis resources?
Wireless, live links-less manual data entry
resources required
13Lessons Learned
- Before a system is implemented
- Senior Management and CORPORATE support
- Information flow mapping
- Data is KEYcreate a team to assemble and qualify
data - Identify training needs
- Plan for resources
- Develop a strategy with timelines
- Create an implementation team with a coordinating
leader
14Lessons Learned
- During and after a system is implemented
- Data is KEY ensure ongoing data collection
processes in place - Establish forums for
- End users
- Policy makers
- Planners
- Identify training
- Plan for resources