All Pipes is a program and data set aiming to create one common schema across ten municipalities. Extensive FME Workbench and Server work aids York Region as they transform and standardize water/wastewater data into one integrated system. This helps York Region to better plan and prepare for the future as a better government.

1. All Pipes Portal:
A Collaborative
Initiative
Jennifer Chung
Andrew Turvey
Neil Hellas

2. About Us
York Region
GIS Technologist
York Region
GIS Technologist
Spatial DNA
Enterprise Solutions
Architect
Jennifer Chung Andrew Turvey Neil Hellas

3. All Pipes Program
All Pipes is a collaborative initiative between York
Region and its nine Area Municipalities to
maintain a single common schema and
water/wastewater utility dataset among partners.

4. Connecting our World:
One pipe at a time!

5. All Pipes
Structure

6. Continuous
Improvement
In September 2015 York
Region decided to
enhance their current
FME portal
architecture.

7. Solution

8. Project Objectives
• Removed ESRI Data Reviewer services
– Replaced QA/QC checks with FME tools
• Increased email notifications
• Integrate loading & viewer capabilities
• Increased reporting functionalities
• Reduce number of workspaces

9. Solution
The goal was to create
a custom workflow to
allow Geocortex to
upload data to FME
Server, and for FME
Server to generate
reports visible on
Geocortex

10. Old
Process
New
Process

11. Timeline
2
weeks
8
weeks
6
weeks

12. Technical
Approach
• Integrate with
Geocortex
• QA/QC Data
• Transform to
common schema
• Limit workspace
editing
• Increase
communications to
user

13. Integration of data and components
User

14. User interface
• Form items are FME
service parameters
• Active Directory
permissions
• Leverage
fmedataupload
service

15. Data Exchange Portal

16. Old process – lots to maintain

17. New process – less to maintain
Configuration separated from functionality

18. Master Workspace
Step 1:
Transform the
feature class and
attribute names
Do some “sanity” QC
Step 2:
Business rules QC
Conform attribute
values
Step 3:
Write the data to the
common database
Step 4:
Topology checks
Launched by web
interface
Calls other FME
services to complete
process
Status table updates
and email notification
to user/admin

19. Step 1 - Schema Mappers
Feature class
names Attribute names

20. Step 2 – QC - Business Rules
Should we test?
Check configuration
Test! Record error Check results

21. Step 2 – QC – Business Rules
Configure which errors can be ignored

22. Step 3 and 4 – Upload

23. A User perspective!

24. All Pipes Portal FME Configuration
• Each Municipality has checks tailored to its unique
data
• Changes and enhancements are easy to manage
without recreating the entire workflow
CSV GISFME

25. Configuration and Efficient management
• Standardizes Data into All Pipes Schema
• Value mapping is done in CSV files; no external software
Concrete Pipe = CPConcrete Pipe = CP

35. Lessons Learned
• Guest token user
• Strict data rules
• Happier users 
• Objectives met

36. Future
Application

37. Thank you!
All Pipes
allpipes@york.ca
Spatial DNA
neil.hellas@spatialdna.com