Page 1 of 1
Anyone using custom acquisition server for Empower 3?
Posted: Mon Mar 18, 2019 3:38 pm
by LabSysAdmin
Anyone is doing data acquisition using its own custom computers instead of Waters LAC/E32 in an Empower 3 environment?
Re: Anyone using custom acquisition server for Empower 3?
Posted: Tue Mar 19, 2019 2:00 pm
by DR
Yes. Many people do this. You need a decent PC w/ a mid-tower sized case if you want/need to accommodate BUS-LAC/E, (whatever has replaced) Equinox, and/or secondary NIC cards. From there, it is mostly a matter of getting permissions and such setup properly in the OS.
Re: Anyone using custom acquisition server for Empower 3?
Posted: Wed Mar 20, 2019 4:22 pm
by LabSysAdmin
Yes. Many people do this. You need a decent PC w/ a mid-tower sized case if you want/need to accommodate BUS-LAC/E, (whatever has replaced) Equinox, and/or secondary NIC cards. From there, it is mostly a matter of getting permissions and such setup properly in the OS.
How do you do the qualification on those custom acquisition servers?
New Waters LAC/e32 (config #16) don't have Raid1 anymore and we can't modify them since they are qualified by Waters and Waters won't let us add a second SSD with Raid1. Custom PC would be sooo cheaper for us and more secured than new Waters machine.
**EDITED for spelling error
Re: Anyone using custom acquisition server for Empower 3?
Posted: Wed Mar 20, 2019 9:26 pm
by Magpie
If you want to execute an identical process that Waters does for their LAC/E boxes you can go through the Self-Directed Qualifications Services training so you can execute yourself (in addition to the training fee, you'll need to pay something for each LAC/E qualification; I think when we asked it was something in the $X,000 for the training and $XXX for each individual LAC/E qualification).
http://www.waters.com/webassets/cms/lib ... 4869en.pdf
But in the end its up to your QA/regulatory group to decide what is a sufficiently qualified LAC/E.
Re: Anyone using custom acquisition server for Empower 3?
Posted: Thu Mar 21, 2019 5:54 pm
by DR
The core elements involve establishing that the LAC/E communicates with the instrumentation and server, going through the checksum file to make sure none of the installed software has been modified and that no needed files are missing, then making sure that both the traditional and apex track integration algorithms are working properly by processing Waters provided sample sets with their PMs and bringing the results up with their report methods.
There are internal and external calibration data sets in both an Apex Track and a traditional project, so you end up with 4 result sets that get compared to Waters provided guides.
Anything above and beyond that will be a function of your QA/QC/IT preferences.