Problems Archiving Data with Chemstation ECM

[ksmith]

The way we have established our file structure with Chemstation ECM, we are having a hard time archiving study specific data as required by the GLP regulations. We have established our structure as:
Business
Group
Client
Compound -
Apparently, when we run multiple, overnight sequences, all data is sent to a common data file, so our analysts have found it easiest to archive the entire compound directory at the end of the study, rather than taking the time to segregate the data by study. When archiving the entire compound file, it includes the method and sequence information (along with information from other incomplete studies). Where a compound folder may contain the information for as many as 10 different studies, it will need to be archived 10 times - thats a lot of storage space.

Need ideas on alternate approaches, etiher in folder/file structure, quick queries, macros, etc. We would like to limit the study specific data archive to include only the method, sequence and data for a specific study (including all associated runs for that study). Agilent has suggested a pretty expensive fix, I believe there are other great ideas to try first.

Thanks, Kirk

[varossf]

If I understand correctly you have defined a default LCDF for storing the data into ECM, correct?
And you have not allowed users the select an other LCDF prior to running a sequence, correct?

And each sequence contains runs from 1 project per time, or do you run samples from multiple projects in 1 sequence. With the latter it would be difficult to pull the data apart in different LCDF structures.

How is your system set-up, multiple workstations on ECM?

One solution could be to swap to OpenLAB CDS EZChrom, which works project oriented and allows you to store data per project in the correct LCDF structure.
Another solution could be to augment the ECM system with openLAB BPM and create workflows to sort the CHemStation data according to their project.

you can always drop me an email