CIM 3.23 - November 5, 2021

Posted about 1 month ago by Wendy Acoin

W
Wendy Acoin Admin

ENHANCEMENTS

  • Added the new field – “leak/rupture” failure mode (prediction calculation) for all corrosion anomalies. This can be viewed in the Integrity Compliance - Add Anomalies screen.
    • The calculation uses the reported flaw length, MOP or evaluation pressure provided by the user, and the CVN toughness attribute assigned.  No flaw interaction is considered; however, the calculation uses the original log-secant model for through wall flaws & the Folias Factor provided for modified ASME B31G calculations.
  • Dig Number field is now directly editable in the Dig Management grid / list of digs.
  • Dent w/ Metal Loss features now ingest both the Dent Depth & Metal Loss Depth values when available in the ILI tally.
  • Added CIS Report comments & tooltip to Close Interval Survey Analysis Report.
  • Display the following additional fields in the Scoop Report:
    • NHD Waterway
    • Foreign Line Crossings
    • Maximum Rupture & Flow Rate - Counts
  • Added new Integrity Compliance conditions to support NEW CIM implementations:
    • Dent with Gouge, Top Half of Pipe HCA 
    • Dent with Gouge, Top Half of Pipe NON-HCA 
    • Remaining Strength / Corrosion, Burst Pressure / MOP <= 1.46 HCA 
    • Remaining Strength / Corrosion, Burst Pressure / MOP <= 1.46 NON-HCA 
    • Dent with Corrosion, 12.5% NWT HCA 
    • Dent with Corrosion, 12.5% NWT NON-HCA 
    • Metal Loss in casings where an evaluation shows 1% corrosion growth HCA/NON-HCA
    • Dent @ Foreign Line Crossing HCA/NON-HCA
  • Changed references to KAPA, RSTRENG, PR3-805 to a more generic term: "Effective Area"
  • User can no longer download Maintenance Pigging Template from Upload Data screen
  • Introduced the ability to run a "risk-only" analysis in Integrity Compliance without selecting a Condition (available for Private Preview Groups only)
  • Improved the Threat Monitoring Bulk edit functionality to allow the user select multiple anomalies from the Threat Monitoring Grid which will enable the “Bulk Edit” button at the top right hand of the screen. Once selected, the user can change the following fields: 
    • Action
    • Work Order Number
    • Repair Date (manually entered)
    • Repair Type
    • Deration Start Date
    • Deration Rescinded Date
    • Field Repair Note
  • Added "Lowest Remaining Life" to Dig Details grid based on the anomaly with the least remaining life in the dig
  • Removed "Delete Date" fields in Integrity Compliance
  • Added Dig Note column to Dig Feature Worklist report
  • Added new filters in Condition Mgt. screen
  • Added when a dig is deleted, system should also delete any related "Nearby Anomalies" that have been added
  • Changed delete analysis from soft delete to hard-delete
  • Changed "State" field in Assessment Planning to "State / Province", add provinces to lookup table
  • Improved error handling if the user enters an invalid SMYS value in Integrity Compliance

BUG FIXES

  • Fixed a bug where Hydro Assessment Start Date, End Date & Type do not save properly the first time the user clicks Save
  • Fixed a bug causing Dig Plan attachments to fail to load when the filename contains a "#" symbol
  • Fixed an error in Threat Monitoring maps when latitude/longitude values are null
  • Fixed a bug where selections on the Risk tab in integrity compliance can unexpectedly persist when creating / editing another analysis
  • Fixed an issue where the Action Name filter in the Assign Action screen may not work correctly
  • Fixed an issue when filtering Anomaly Type = "All" in Assign Action screen
  • Fixed an error when trying to drill-through on "The Scoop" report
  • Fixed an issue where inactivating condition 8000 in Condition Mgt. caused the Add Anomalies screen to break
  • Fixed an error when attempting to approve a Dig Plan associated with an Analysis that was un-submitted
  • Fixed a bug where field found anomalies would link to an analysis and dig but not associate that analysis with the dig record
  • Fixed a bug where the count of attachments in Threat Monitoring may not be correct in some cases

0 Votes


0 Comments

Login or Sign up to post a comment