GIS has become the foundation of our organization’s asset management program. Many of our business systems rely on our GIS services for authoritative spatial data and map services. Other business systems (SunGard ERP, Cityworks CMMS, and legacy WinCan CCTV inspection system) contain critical non-spatial data that must be linked to spatial asset information. In this presentation I’ll share how we are using FME Server to “blend” spatial and non-spatial data together for the ArcGIS Server map services that power our Geocortex applications, our Cityworks CMMS, and our new ITpipes CCTV inspection system.
4. What is
“Enterprise
Data”?
• Non-spatial tabular data
• Often part of Commercial Off-The-
Shelf (COTS) software
• Computerized Maintenance
Management Systems (CMMS)
• Enterprise Resource Planning (ERP)
systems
• CCTV or other inspection systems
• Stored in an enterprise DBMS
• Oracle
• Microsoft SQL Server
• IBM DB2
• SAP
• Microsoft Access**
• Frequently involves lots of related
tables
14. Identification Formats Change
Structure Type
Old GIS ID
Format CCTV ID Format GIS ID Format
Manhole 75A1 M 12 75A1M12 75A1-M12
Cleanout 9E7 CO10 9E7CO10 13B7-CO10
Junction Structure 47C3 JS5 47C3JS5 47C3-JS5
Rodding Inlet 101E7 R 22 101E7R22 101E7-RI22
Pressure Relief 47D6 P 6 47D6P6 47D6-PR6
Wye 13B5 W 5.3 13B5W5.3 13B5-W5.3
20. Cross-Database
joins
• May not be common
primary/foreign key columns
• May not be optimally
indexed
• Datatypes may not match
(casting is slow)
• May mix DBMS platforms
• MS Sql Server
• Oracle
• IBM DB2
• Sybase
• MS Access
21. Enterprise
database table
joins
• 1:Many relationships
may need aggregation
• May not be optimally
indexed for joins
• Data may not be
consistent
• May be deeply nested
Table1
idPK
blahblahblah
yadayadayada
Table2
idPK
blahblahblah
yadayadayada
fk_idFK
1:M
Table3
idPK
blahblahblah
yadayadayada
fk_idFK
1:M
22. Geocortex
supports joining
to Enterprise
databases, but…
• Still subject to the “pain
points”
• poor performance
• data inconsistencies
• aggregation
• Users must “drill down”
through relationships to
get to the joined data
(e.g.: extra clicks)
• Doesn’t support nested
table joins and 1:Many
relationships
23.
24. “Blend” the
Enterprise data
into the GIS
features
1. Add extra fields to
relevant geodatabase
feature classes
2. Use FME Server to
write the enterprise
data into those fields
3. Profit! J
25.
26.
27. “Blend” the
Enterprise and
GIS data into a
non-versioned
“Publish”
geodatabase
1. Duplicate the geodatabase
schema to new “Publish”
geodatabase
2. Add extra fields to relevant
geodatabase feature classes
3. Use FME Server to
truncate/repopulate the
geodatabase with the
“blended” data
4. Profit! J