*Form last 3 to 4 years we have been selling and proposing Citect Scada with DNPr driver in Pharmaceutical Companies as a 21CFR compiled Solution. We are using the back-filling feature of DNPr driver with Citect Scada. To use this feature we configure Event Type trends in Citect Scada so that DNPr slave device can back fill data into Citect Trend.
*But the major two disadvantages which we have observed is;
1. When the Slave device is not in communication with Citect Scada ,Citect is showing graphs in trend screen. We can not justify this to our customers.
2. If my slave deice power fails and it took one hour to get powered up then Citect Event type trend will show graph for that duration when Device itself is powered of. This is really a big issue.
3. Now one more example is that my slave device became faulty due to some reason and it has the last value 25 transferred to Citect. Now after one week customers procure a new device and replace the faulty device and communication will be established with Citect. New device has the first reading 30 transferred to Citect. So Citect event type trends will show graphs between 25 to 30. That means my Citect Trend will show a graph of the last one week where the device itself is not working. Again we or even customers can not justify this scenario to their authorities.
Guest
|
Idea business value
We have enough orders and enough inquiries but we are stuck with this limitations of Citect Scada Event type trend. |
|
| Idea priority | 5 – Critical to my company |
