Text Substitution on File Read Some process historians very usefully record data for some status variables as text such as ON or OFF, OPEN or CLOSED instead of as integers. Laboratory data similarly can contain text such as PASS, FAIL. CVE 2.8.0 and earlier treat text fields as invalid data.
We regret to have to raise the purchase price of our CVE product by approximately 9% due to inflation. This is the first price increase for CVE in many years and will apply from 1 February 2023. TAP subscriptions will be affected at next renewal. The rise may be avoided
We’ve introduced this Blog to enable better two-way communication between you and us and to reduce the number of emails we send to subscribers to hopefully just three per month. You can contribute blog entries too by sending them to anyone in PPCL or to firstname.lastname@example.org or Enquiries@ppcl.com as emails
Protected: How to replicate a successful computer pilot application from one process site to many others?
There is no excerpt because this is a protected post.
Why you must use CVE for Alarm and Process Performance Monitoring and on-going Adjustment of Alarm Limits to maintain top performance
This three-way relationship between Operating Objectives, Operating Envelope, and Process Capability is why you must use CVE for alarm performance monitoring.
When we start exploring data in CVE, there are often some variables that are single-valued, that is, all of the data has been reported as the same value.
Our purely visual method, when properly set up, allows process-knowledgeable end-users to see at a (long) glance a comparison across hundreds of variable.