API 1130 Requirements

Computational Pipeline Monitoring (CPM) Selection Criteria as identified in the API 1130 second edition November 2002, section 4.2, Selection Criteria.
(Each attribute is supported by Leak Track 2000 unless otherwise noted)

  1. Possess accurate commodity release alarming.
  2. Possess high sensitivity to commodity release.
  3. Allow for timely detection of commodity release.
  4. Require minimal software configuration and tuning.
  5. Perform its CPM functions with existing sensors and instruments (or does not require additional requirements or instrumentation).
  6. Be minimally impacted by communication outages or data failures.
  7. Accommodates complex operating conditions.
  8. Be available during transients.
  9. Be configurable to complex pipeline networks.
  10. Perform an imbalance calculation on meters at one instant in time.
  11. Possess dynamic alarm thresholds.
  12. Possess dynamic liquid pack constants.
  13. Accommodate commodity blending.
  14. Account for heat transfer.
  15. Provide the pipeline system's real-time pressure profile.
  16. Accommodate intermittent or permanent slack line conditions (avoiding alarms and not totally disabling all segments of the pipeline during event).
  17. Accommodate all types of liquids.
  18. Identify leak location with appropriate mile post locations or nearest station.
  19. Have the ability to display pressure history versus time for each line pressure location along a pipeline.
  20. Provide for automatic and manual data substitution during periods of data non-availability (e.g., communication outage, measurement failure, maintenance, etc.).
  21. Provide composite indication of data attributes associated with supporting field inputs and calculated data.
  22. Minimize the number of alarms by requiring supporting and preferably independent, commodity release confirmation.
  23. Identify the leak rate.
  24. Accommodate commodity measurement and inventory compensation for various correction factors (temperature, pressure, density, meter factor).
  25. Provide batch tracking with interface location, be able to compute bulk modulus and perform inventory compensation.
  26. Perform calculations quickly using data immediately as it becomes available.
  27. Validate commodity release alarms using redundant analysis within the same method as well as redundant analysis between methods.
  28. Accommodate pump start-ups/shutdowns, valves opening/closing, and other normal operational functions without generating alarms.
  29. Account for effects of drag reducing additive.
  30. Offer efficient field and Control Center support.
  31. Contain a leak probability analyzer to weigh all of the components of a leak (linepack loss, pressure/flow deviation, meter shortage) to assist a pipeline controller in making a leak declaration.
  32. Possess ability to allow alarms to be integrated into the pipeline controller's alarm processing.
  33. Possess audit trails of CPM actions taken by pipeline controllers and allow saving of historical data.
  34. Have the ability to return to normal detectability limits rapidly after data or computer service is restored or after an unscheduled interruption.
  35. Have the ability to provide various types of warnings and alarms for example warnings or alarms on data failure or unusual operating conditions that indicate the cause is not a commodity release.
  36. Provide an alarm under all operating conditions and will not be disabled or turned off automatically regardless of circumstance.
  37. Have the ability to automatically self test without effecting performance while test is underway.1

1 - Does not support a self test function but data is validated as it is processed.

Image