Leverage EpochSync with Smallworld Construction View
Recently, a power utility client approached us with a business problem concerning viewing their proposed work across the enterprise. They were already using EpochSync to replicate their as-built Smallworld data to an ArcGIS SDE database, but they had wished to get their proposed Design Manager Construction View data into ArcGIS as well. This would allow all of their proposed work to be made available using ESRI’s WebAppbuilder, already being used with the as-built EpochSync’ed Smallworld data. This presented a challenge, how can EpochSync work against multiple Smallworld alternatives in the same datasets without the churn of syncing and maintaining all as-built data in an ESRI database twice?
Well, with a bit of creative thinking, we had our solution. The client created a supplementary ArcGIS SDE database for the Construction View data, using ArcCatalog to export the schema from their as-built database and replicate it in their Construction View database. That was EpochSync’s target, and we only wanted the inserts and updates in the Construction View alternatives to make it into this database, so…
…we assisted the client in customizing EpochSync to provide a “Construction View” mode. When using this mode, every time EpochSync runs against the Construction View alternatives, it deletes all existing records in the table(s) being synced and re-populates the table from scratch, but ONLY populating the table with the records that have been inserted or updated in the Construction View alternatives (as derived using Smallworld’s built-in difference stream functionality). The solution is relatively simple, prevents double-syncing, and best of all does away with any difficulties arising from the vagaries of Smallworld’s Construction View alternative management.
With this solution in-place, the client can view both their Smallworld as-built assets and proposed work at the same time, across the enterprise, via ESRI’s WebAppbuilder and other ESRI tools.