Is it possible to use PDL if not using 800xA-Batch?
For an upcoming project we are investigating to make use of PDL logging. However, in this project 800xA-Batch is not part of the configuration. The process which needs to be handled can be regarded as a sort of batch-process, but we believe the customer has good reasons to not use 800xA-batch. The production will be handled in AC800 controllers, part of an 800xA-system
The goal is to log all steps during producing a product batch, for reporting and data mining purposes
OPC AE from AC 800M is stored in 800xA by the Event Storage service (default capacity is 10.000 events per category, but can be extended into 50.000 events, or perhaps a little bit more if you can accept slower event lists).
An IM can be used to extend this event storage into 12 million events; Oracle based storage allowing some SQL application to read / process them.
If Batch is used, the IM Batch PDL message log will automatically be populated as batch equipment and batches are changing states. With no Batch and IM servers you are left with the relatively speaking small storage of Event Storage. Storage will be shared with other objects emitting events on the same categories. A process upset with large amounts of process events may cause your home cooked batch events to wrap prematurely.
Maybe a labdata log might be able to store what you need?
A Calculation can be created and set detect the "batch" upon some OPC DA property changing value, read a number of additional inputs (batch data) and finally store them into a lablog with some suitable storage parameter.
I doubt you can store strings though.
No, PDL is part of Batch Management. The production data log is where the batch manager stores changes to procedure parameters, related events etc. All of this data can be stored somewhere else - eg, Event Logs, Basic History, Reports etc.
Ive had several years experience with the Batch Manager, and it is absolutely not required on plants where the S88 procedures are simple and do not vary very much between products. Even small changes to procedures are more easily handled in the controller rather than in the Batch Manager. In simple plants, the BM becomes little more than an expensive and overcomplicated recipe storage server.
IMHO, if you dont have a BM, then you dont need an IM. Basic History is perfectly capable of storing long term data. in practical terms, the history is limited only by the amount of disk space you have available. All the reporting functions are available with Data Direct, which does not need the IM for Excel Based reporting.
The BM and IM are really only required when you have more complicated S88 requirements. Eg Pharmaceuticals etc.
A simple and effective alternative is "ProBase" - a library of solutions for Food and Beverage. This library includes recipe based CIP procedures where recipes can be stored in an MS access database. The same principle can be used to store product recipes. Even if you dont use ProBase, it might be worthwhile to look at a demo of the package to get some ideas about how you can build an S88 compliant control system without the Batch Manager.
You can contact me off forum if you need to know more.