Early Returns on Synergi Pipeline Overpressurization
Synergi Pipeline Overpressurization is the DNV Pipeline Product Group’s first multi-tenant cloud web application. Designed to help pipeline planners and engineers characterize the criticality of regulator stations from a hydraulic standpoint, the first round of private previews for the Synergi Pipeline Overpressurization application was a huge success. In this blog post, Corey Rice walks us through some of the feedback received from our previewers. Corey, who is based in our Mechanicsburg, Pennsylvania office, is a Principal Technical Support Engineer for DNV’s Pipeline Solutions Portfolio.
Synergi Pipeline Overpressurization Private Preview Activity
Last year I posted on Critical Regulator Station Failure, introducing the Pipeline Product Group’s first multi-tenant cloud web application, Synergi Pipeline Overpressurization. That post ended with a few questions for all of you that were geared towards assisting us refine and improve the application. In what I hope was not a reflection of the enthusiasm for this application, zero comments have been left. It’s not too late! You can still go back and leave some feedback, but in the meantime I’ve compiled some of the feedback we’ve received from our first round of private previewers that I’m sharing today.
“Already being asked for the results to use in prioritizing over pressure mitigation actions”
The private preview participants unanimously concluded that the application is helpful for prioritizing regulator stations. More specifically, this included both efforts geared just towards installing overpressure mitigation measures at older stations and also for more standard station replacement programs. When stations are all of a similar age, the results of the overpressure analysis can contribute to more strategic replacement decisions. For users of the Synergi Pipeline regulator station risk model, the overpressure analysis results are vital for generating the most accurate results for total risk.
“Not sure there is one [ideal metric for categorizing regulator stations]; that probably depends on the system”
That old joke about asking five engineers how to do something and receiving six different answers applies here. While each private previewer appreciated having the application return a single metric because it simplifies understanding, they had something different to say about how to define that metric. One put it very simply – “number of customers over pressured”:
Another appreciated the application’s existing scoring system:
Not surprisingly, there were calls to allow the user to define the formula used to determine the scoring value for stations.
“Distribution Engineering, System Planning, Operations, PSMS, and other departments benefit from the results”
All of the private previewers agreed that a variety of departments within the utility would benefit from results generated by the application, citing many of the same groups. Standards, or “Codes & Standards,” was also noted as a beneficiary. PSMS stands for Pipeline Safety Management System, which would include Distribution Integrity Management Program (DIMP) activities.
“Frequency to run the overpressurization application is once or twice a year”
All of the private previewers initially thought that, in practice, this application would be run annually. That thinking did not change very much by the end of the preview period, with most concluding that they expected to run it one to two times per year, with occasional ad-hoc analyses as needed. One of the things I was wondering going into this first preview was – would the blazing speed of the analysis proportionally affect the desired frequency to run it. So far, it seems like there is no relationship between the two.
“Impressed with the speed at which this cloud-based application can perform the analysis”
When we first broached the subject of a public cloud platform a few years ago, it was met with varying degrees of skepticism. But the feedback from our private previewers was unanimously positive regarding the Overpressurization Analysis application. Frequently cited was the speed at which system-wide analyses are completed.
Private previewers also appreciated that patches/fixes could be delivered quickly. Not that we had to issue a LOT of these during the private preview, but there were a few. Once the patch was complete all I had to do was contact the user to let him know of its existence. The next time he logged in to the application in his browser, the reported issue was gone.
Private Preview Benefits
See what you’re missing out on by not participating in the private preview? Our participants are provided with their own private space (“tenant”) and only users from that company can access the applications. The preview also provides a means for you offer direct input into the development of these applications. If you’re interested in participating in future previews, contact me or your DNV sales manager. The next application that will be made available for private preview in a few months is Outage Analysis. I’ll have more on this application later in the year.