Top Banner
Smallworld to GreGG FME Server Automation Ted Norcott GIS Specialist FortisBC Mark Sedgwick GIS Consultant Fujitsu
23

Smallworld to GreGG - FME Server Automation

Jul 16, 2015

Download

Technology

Safe Software
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Smallworld to GreGG - FME Server Automation

Smallworld to GreGGFME Server AutomationTed NorcottGIS SpecialistFortisBC

Mark SedgwickGIS ConsultantFujitsu

Page 2: Smallworld to GreGG - FME Server Automation

Business Requirement to Automate Process

Smallworld 4.1 to 4.3 Upgrade

FME Server 2014

SBS Plug-in

Let’s Automate!!

Page 3: Smallworld to GreGG - FME Server Automation

Smallworld GreGG

SmallworldGIS

GreGGNetwork Analysis

FMEServer

Page 4: Smallworld to GreGG - FME Server Automation

Before….

Page 5: Smallworld to GreGG - FME Server Automation

Key Elements…

Spatial Context configuration(only get the data you need)

Logical Field Configuration(use “rich” data-model of Smallworlod to provide key information)

Page 6: Smallworld to GreGG - FME Server Automation

After….1 workspace for Export

Page 7: Smallworld to GreGG - FME Server Automation

….

GIS FME

Entire DBFor each object

All SystemBoundaries

“Hope” System

Entire DBFor each object

All SystemBoundaries

2 Original Workspaces- “what” gets translated

Page 8: Smallworld to GreGG - FME Server Automation

New Workspace using Spatial Datum- “what area” gets exported

"gas_distribution.gd_system.network_extentwhere network_id = '$(NAM)'"

Page 9: Smallworld to GreGG - FME Server Automation

Hope area

GIS FME

New Workspace using Spatial Datum- “what area” gets exported

Page 10: Smallworld to GreGG - FME Server Automation

GreGG Data Requirements355 Third Ave (17 fields in total)

X,Y X,Y

Page 11: Smallworld to GreGG - FME Server Automation

Tracing to Connected Main(1)

Page 12: Smallworld to GreGG - FME Server Automation

Tracing to Connected Main(2)

Page 13: Smallworld to GreGG - FME Server Automation

Key Element: a “Pseudo Field”

programming logic for a named field within the FME Workspace

(ie.)

gd_metergd_service_point_connection_location_fields

Page 14: Smallworld to GreGG - FME Server Automation

Single Pseudo Field in FME…returns 17 GIS fields from 3 different objects

Magik> gd_meter.gd_service_point_connection_location_fields

"XC|1271908.133|YC|453151.208|XP|1271945.286|YP|453269.155|GISXP|1271945286.000|GISYP|453269155.000|SCENARIO||WO|1458|CIVIC|65367|DIR_SUF||NAME|KAWKAWA LAKE|PCODE|V0X 1L0|POD|619458|PREFIX||PREMISE_ID|619458|SUFFIX|Road|TOWN|Hope|UNIT|108""

Page 15: Smallworld to GreGG - FME Server Automation

List to allow multiple field returns

Page 16: Smallworld to GreGG - FME Server Automation

Automating (simplifying)the original workspaces…

Exporting:

Spatial Datum (replaced 2 workspaces)

Pseudo Fields (replaced 5 workspaces)

Page 17: Smallworld to GreGG - FME Server Automation

GreGG Smallworld

SmallworldGIS

GreGGNetwork Analysis

FMEServer

Page 18: Smallworld to GreGG - FME Server Automation

Pressure values going back into Smallworld

Automatically removes existing points before inserting newly calculated points.

Page 19: Smallworld to GreGG - FME Server Automation

Import… 1 workspace

Page 20: Smallworld to GreGG - FME Server Automation

Pressure values going back into Smallworld

Page 21: Smallworld to GreGG - FME Server Automation

Pressure Load Point values going back into Smallworld

Page 22: Smallworld to GreGG - FME Server Automation

Benefits and Conclusion

Automated self-serve process on demand

Removal of repetitive semi-manual process

More up-to-date data

Two way connection

Greater usage of FME Server Software

Page 23: Smallworld to GreGG - FME Server Automation

Thank You!

Questions?

For more information:

Ted Norcott [email protected]

FortisBC Energy Inc