Industry platforms, move by move.
Regulators read policy admin, claims, core banking and EHR systems closely, so every change has to appear in the change log. We stick to the vendor's upgrade path and keep the examiner's evidence up to date as we go.
- AVEVA PI data to cloud analytics on Databricks or Fabricmodernization · delivered
- Duck Creek on-premises to Duck Creek OnDemandmigration · delivered
- Epic integrations, FHIR APIs and TEFCA connectivityimplementation · delivered
- Guidewire InsuranceSuite self-managed to Guidewire Cloudmigration · delivered
- Murex MX.3 upgrades and the move to MXSaaSupgrade · delivered
- Nasdaq Calypso upgrade to V19upgrade · delivered
AVEVA PI data to cloud analytics on Databricks or Fabric
Told without the client's name or anything that could identify them.
A chemical manufacturer's data scientists kept asking for direct connections into plant historians, and cloud teams copied PI data with scripts that broke whenever a tag was renamed. Every site named tags differently, and a PI subscription renewal was coming without a clear list of the components analytics needed. We read interface logs, buffering settings and archive gaps by site and fixed the collection problems first, then agreed a tag naming and asset hierarchy standard with process engineers. Data now leaves the plant outbound through a DMZ PI replica and lands in Delta tables under Unity Catalog with asset context attached.
what the client got- Nothing in the cloud connects into the control networkPI data reaches the cloud through an outbound feed from a DMZ replica. No inbound firewall rules to the control network were needed.
- Tags follow one naming and asset standardProcess engineers agreed a tag naming and asset hierarchy standard, starting with the units and equipment analysts ask about most, so cross-site analysis no longer starts in a spreadsheet.
- Collection gaps are fixed at the sourceInterface, buffering and stale tag problems were fixed site by site before analytics leaned on the data. Otherwise they'd have turned up later as flat lines on someone's chart.
All 10 in industry platforms
Read any of them and you get the story, the before-and-after architecture, the plan phase by phase and the results.
AVEVA PI data to cloud analytics on Databricks or Fabric
Getting AVEVA PI System data into Databricks or Microsoft Fabric with asset context, outbound-only paths out of the plant and tag names people understand.
read the case studyDuck Creek on-premises to Duck Creek OnDemand
We move self-hosted Duck Creek Policy, Billing and Claims onto Duck Creek OnDemand and keep the product and rating content, integrations and data intact.
read the case studyEpic integrations, FHIR APIs and TEFCA connectivity
Building and governing the HL7 and FHIR integrations, SMART on FHIR apps and TEFCA exchange around Epic, with an interface catalog and scope reviews.
read the case studyGuidewire InsuranceSuite self-managed to Guidewire Cloud
Moving self-managed PolicyCenter, BillingCenter and ClaimCenter to Guidewire Cloud without carrying every Gosu customization and integration along.
read the case studyMurex MX.3 upgrades and the move to MXSaaS
Planning the next Murex MX.3 upgrade, or a move to MXSaaS, with automated regression on trades, valuations and accounting and the datamart reports traced.
read the case studyNasdaq Calypso upgrade to V19
Upgrading Nasdaq Calypso to V19, with server consolidation, properties moved to the database, the WebUI and deployment changes tested on your own trades.
read the case studyOracle Utilities CC&B 2.x to the 25.x release line
Taking Oracle Utilities CC&B from 2.6, 2.7, 2.8 or 2.9 to 25.4 on a tested upgrade path, with custom algorithms checked and bill cycles compared.
read the case studySAP IS-U to S/4HANA Utilities
Taking SAP IS-U from ECC 6.0 to S/4HANA Utilities ahead of 2027, and proving billing variants, device data and FI-CA in parallel billing first.
read the case studyTemenos core banking upgrades and Temenos SaaS
Upgrading Temenos Transact (formerly T24), or moving to Temenos SaaS, with local developments traced, retired or rebuilt, and regression automated.
read the case study
TriZetto Facets upgrades and CMS-0057-F interoperability APIs
Keeping TriZetto Facets current while we build the Provider Access, Payer-to-Payer and Prior Authorization APIs that CMS-0057-F requires by January 2027.
read the case studyNot sure which one fits?
Send us what you run and what's due. An engineer reads it and tells you where we'd start.
start an assessment →Risks that keep coming up
One risk from each of these moves, and the case study that shows how we handled it when it hit.
-
Opening a path into OT ↗
A design that needs inbound firewall rules to the control network will stall with the OT team, and it should. All feeds run outbound from the DMZ or CONNECT.
-
Manuscript drift ↗
Years of state-specific manuscript edits rarely match documentation. Comparing rated premium on real policies before and after the move is the only reliable check.
-
Over-broad FHIR scopes ↗
Apps approved with more scopes than they need expose patient data that was never in scope for their use case. We review every scope against the app's job.
-
Rebuilding every customization ↗
Moving all Gosu code as-is recreates the upgrade problem in the cloud. Each item needs a keep, replace or drop decision before build starts.
-
Manual regression filling the window ↗
With spreadsheet regression, only so many test cycles fit before go-live. Automation is usually what turns two cycles into several.
-
Topology assumptions breaking ↗
Server consolidation changes what runs where. Monitoring, failover and engine sizing built for the old layout need rework.
Platforms and services across these moves
Ordered by how often they appear in this area's case studies.
01Should we use AVEVA CONNECT or build our own feed from PI?
It depends on your licence, how many sites you have and whether you want AVEVA to run the cloud side. CONNECT with Delta Sharing suits Databricks users. A DMZ replica with your own outbound feed gives more control. We cost both against your sites.
02Do we lose our custom products when moving to OnDemand?
No. Product and rating content moves across as it is. Custom extensions and integrations are another matter, because they're built and deployed differently on OnDemand. We go through each before the migration so nothing disappears unexpectedly.
03Do we need to do anything for TEFCA if Epic is our QHIN connection?
Usually, yes. You still decide which exchange purposes to support, how requests get answered, and how consent and patient matching work. We go through those settings and the workflows behind them with your team.
04How long does a move to Guidewire Cloud take?
It depends on how many products and lines of business you run, how much Gosu code and how many integrations you carry, and how much history you convert. We give an estimate after the customization and integration inventory, not before.
05Should we upgrade ourselves or move to MXSaaS?
It depends on your hosting and regulatory constraints, how many interfaces need to change and how much in-house MX.3 operations staff you want to keep. We lay both options out against your own estate.
More case studies by area
The same approach, applied to other parts of the estate.
773df8f5 - 01AVEVA: AVEVA and Databricks forge strategic collaboration (3 Apr 2024)aveva.com ↗
- 02AVEVA: AVEVA PI System (components, subscription licensing)aveva.com ↗
- 03Microsoft Learn: What is Real-Time Intelligence in Microsoft Fabric?learn.microsoft.com ↗
- 04Databricks: Agent Bricks at Data + AI Summit 2026databricks.com ↗
- 05Duck Creek: Policy, Rating, Billing and Claims; Duck Creek OnDemand and Cloud Deliveryduckcreek.com ↗
- 06Duck Creek: Duck Creek acquires Send (7 Jul 2026)duckcreek.com ↗
- 07ASTP/ONC: Trusted Exchange Framework and Common Agreement (TEFCA)healthit.gov ↗
- 08The Sequoia Project (RCE): Designated QHINsrce.sequoiaproject.org ↗
Facing one of these moves?
Tell us what you're on now and where you need to be. We'll come back with how we'd run the move.
- The platform and the version you're on
- Where you need to get to, and by when
- What's custom: rules, plugins, integrations
- Any audit finding or deadline driving it