This week we officially released Cognitive Integrity Management 3.0, (“CIM 3.0”), which was developed under the product codename Polaris. The product team has been working tirelessly with SME’s from our participating pipeline operators during our private preview to ensure the solution applies horizontally across most operators. Starting at the end of May, each week these SME’s provided us operational data from their existing systems, assisted to validate CIM features, and confirmed the accuracy of the results. The ultimate objective of these operators was to evaluate CIM 3.0 for use within their organization. This ranged from replacing relatively manual processes based on Microsoft Excel to more significant on-premise legacy database solutions.
To provide some context around the outcomes from the private preview, at the kick-off back in May, we expected a huge list of gaps. Fortunately, we left the meeting with only one showstopper and a few minor updates well within the planned scope of this sprint. Since then, these operators have been working within the solution using their own data. It’s extremely encouraging to us that one of these operators has already moved into production with the CIM 3.0 solution. You can read about it here. We’re working on a few specific requirements for the other operators and expect that they will move to production in the next few months.
Where do we go from here? As a SaaS company, it’s kind of anti-climactic to officially tie a version to a release, as there will likely be new features released as soon as next week. For example, we have completed 100+ user stories (individual solution features) to date and have a backlog of new user stories the team is aggressively working on. That’s the business of being a SaaS company. For us, GA versions really signify the overall impact the cumulation of work to date has to the business operations of our customers. We believe this release will significantly improve the following for our customers:
- Pit to pit alignment - it continues to evolve and has now been trained on over 45,000 miles of pipe. It’s very good according to SME’s at operators and will continue to evolve and improve.
- Operators are sharing with us their “in the ditch” data from digs previously identified by the solution. So far, we’re batting 1000 and anxiously waiting for any false positives so we can further evolve the algorithms. Further, we are testing an API to allow operators to push their field data into the solution automatically.
- 29 of 44 CFR 192 & 195 regulatory conditions are now active in the solution. The remaining conditions are dependent on specific data we have not yet been able to get from most operators.
- Initial capabilities to ingest recent and historical repair data are being tested so operators can filter to only include injurious anomalies that have not yet been repaired.
- A PODS API is being developed with operators using the PODS database standard to allow them to push pipe properties into the solution.
- We are constantly iterating and releasing reports as prioritized by operator SME’s with standard unity plots, dig sheets, PHMSA annual reporting (including Parts F & G), and dashboards slated to be released soon.
In addition to wrapping up our private preview and tagging this release, we are actively working on nine other pilot programs utilizing both CIM 2.0 and 3.0. This has provided further validation to the significance of this release as operators are able to load their historical ILI tally sheets, repair data, pipeline hierarchy, and pipe properties within a short period of time. They can then, literally, hit a button to analyze 100% of the data to check all CFR 192 & 195 conditions, identify anomalies that are growing quickly, and report across their entire pipeline system. (i.e. how many anomalies are growing at 20% near a girth weld with coating type of FBE?)
Finally, we’d like to thank those operators who are on this journey with us. The experience has truly been invaluable both for the progression of the CIM 3.0 release and the growth of OneBridge. We believe the input we are receiving from the SME’s at these operators is critical to driving each iteration and evolution of the solution and is the only way we will ultimately fulfill our mission of predicting pipeline failures. We feel fortunate to play a part in helping support the mandate of sharing community knowledge towards this goal.
If you are interested in joining us or learning more, please reach out to firstname.lastname@example.org. We think you will be surprised by the sophistication and impact Cognitive Integrity Management could have on your organization.