|
What Can OPC Time Monitor Do for You ?
The number of potential applications for the OPC Time Monitor is wide and varied.
On this page we have provided a list of common applications to help you think about how the OPC Time Monitor can help you in your process improvement efforts
OPC Data Consolidation/Funneling
Does your OPC client application limit you to the number of OPC server connections it can make?
Do you worry that new OPC clients installed on your plant network will connect to your OPC servers and request data at
rates that you know will overwhelm the device network?
Do you have OPC servers that have long, cryptic, non-meaningful tagnames?
The OPC Time Monitor takes care of solving all these problems and as a bonus gives you valuable business information.
Maintenance Management
Intelligent Maintenance Management decisions depend on knowing:
- How long machine has been in use
- How long an abnormal condition has existed
- How often abnormal conditions occur
- How long the abnormal condition lasts on average
How do you calculate this data now ? Now off-the-shelf OPC server that talks to machine control systems gives you that data automatically.
OPC Time Monitor answers all of the above Maintenance Management questions and provides the data via OPC to your CMMS system or any other system.
Machine Utilization, Uptime & Asset Management
Everyone knows that capital equipment is a big investment and wants to get the most out of it. The control systems that run
your machines know whether the machine is running or not and a lot more about the condition and operating conditions - all valuable information if presented properly.
OPC Time Monitor, without programming, helps you to aggregate and summarize information about machine operating
states and conditions and present it to any application of your choice for logging, presentation, reporting, and management.
The data provided by OPC Time Monitor can then be fed into your favorite HMI/SCADA, Maintenance Management, or Asset Management application using the open OPC DA standard.
Information possible includes:
- Machine Uptime and/or Downtime (total, max, and average times using the condition aggregates)
- Machine setup times (total, max single setup, average setup using the condition aggregates)
- Setup counts (i.e. # of setups) (using CycleCount aggregate)
- Part Production Counts (using CycleCount aggregate)
- Time spent making different product types - setup monitoring items - one per product type - that monitor an OPC item
that specifies the current part being made - OPC Time Monitor, with its aggregates, can then easily generate for you the Total, Max, and Average time spent making each part type using it's condition aggregates)
Regulatory Compliance Monitoring
Using the OPC Time Monitor's ability to specify a "condition" based on a range of values and its ability to specify condition
that would imply loss of communications to the field device (OPC Quality conditions), the OPC Time Monitor can then
monitor your field instruments through your OPC Data Access servers and generate notification events to your HMI application or other regulatory monitoring applications. Information possible includes:
By using the OPC Time monitor to handle detecting out-of-compliance conditions, you free yourself from writing custom
scripting or other decision making logic in your monitoring application or in field devices. Because the OPC Time Monitor
can simultaneously report information and events to multiple client applications, your choices for monitoring and notification are extensive.
When teamed with our
OPC Data Logger application, powerful monitoring and logging applications can be built without any programming.
Quality Variable Monitoring
Use the OPC Time Monitor's ability to specify a "condition" based on a range of values to setup your control limits on
process variables. The OPC Time Monitor will then provide, without programming, information about
Tool & Die Utilization
Do you have problems with wasted tooling because tools are changed after some arbitrary number of uses that may not
reflect actual runtime ? Or are tools to be changed every 100 usages but in reality get changed early "just because its
convenient and no one is really counting cycles"? Are there conditions that you know dramatically reduce tool lifetime ?
Wouldn't it be nice to be able to automatically know if those conditions have existed, how many times, and for how long ?
The OPC Time Monitor can save you money by making it easy for you to monitor actual usage times and cycle counts and
display them for operators in the machine user interface or provide events/data to your maintenance management applications.
You could setup key values available from the machine controller that tell whether or not the machine is running, machine
speed, temperature, etc and the OPC Time Monitor will then provide information about
|