NEW FEATURES
- Added over 20 new Integrity Compliance conditions to support new customer IMP requirements, particularly around gas pipelines.
- Added support for a new pressure calculation: Raju-Newman used to support new conditions around crack and crack-like feature.
- Added support for integration with GIS systems which use alphanumeric IDs.
ENHANCEMENTS & BUG FIXES
- Added the “Actual Anomaly Description” field to Threat Monitoring edit screen
- Improved the behavior of the Master Joint report when there are is no master joint data for the selected system
- Moved many reports out of “Preview” and into other report groups in the report module
- Report lists now sort alphabetically rather than by DB sort order field
- Added support for ingesting DOT Class Code values from ILI for use in Integrity Compliance analysis
- Added Coupon Vendor, Injection Vendor & Samples Vendor templates in Upload Data
- Added the Internal/External field to Feature Dig Sheet report
- Dig compliance date is now populated automatically based on the earliest anomaly due date
- Changed projected anomaly failure date / remaining life to calculate down to the specific day rather than rounding to a whole number of years
- Fixed an issue when a condition is removed from a default template in Condition Management it could get re-added automatically by the next CIM upgrade
- Fixed an issue where the D/S odometer value was cut off when producing Feature Dig Sheet in PDF format
- Fixed several issues which could result in failed Repair Template load jobs
- Fixed some issues related to repair template formatting
- Fixed an issue where the Feature Counts report could report double the actual number of girth welds
- Change growth conditions & projected growth dates to be based specifically on Modified B31G rather than the max of B31G & B31GMod (now more consistent with direction of other pressure conditions)
- Fixed an issue where the “Create Default Analysis” button in Assessment Planning Vendor Reports grid could become enabled before vendor report loading & data migration are complete
- Fixed an issue where Dents with Metal Loss which are also on the Long Seam can display “Is Long Seam = N” in Integrity Compliance
- Fixed an issue where Field Found repair records were being inserted as “System Generated = Y” rather than “System Generated = N”
- During Data Migration stage, if there are no Joint Numbers provided, generate one based on CIM’s internal IDs to support adding field anomalies by Joint ID
- Fixed an issue where Integrity Compliance conditions that are de-selected can be re-selected again after saving the analysis
- Fixed an issue where the Route Sequence field could display incorrectly in the Pipeline Data grid
- System will no longer automatically set an anomaly repaired date when an End Date is specified on the corresponding Dig
- Improved error handling when attempting to load an ILI vendor report into a system without a diameter value
- Fixed an issue where certain values in Integrity Compliance Attributes could display an excessive number of decimal places of precision after conversion
- Fixed an error when viewing the “Map” tab in Integrity Compliance Assign Action when the ILI data contains no lat/long data
Comments
0 comments
Please sign in to leave a comment.