Out with the “If it Ain’t Broke, Don’t Fix it” Approach. In with Remote Monitoring.

Mar 26, 2018 | Blogs, Software, Technology | 0 comments

Often by the time you’re aware of a problem, it’s too late, and disaster has already struck. You’re forced to pick up the pieces—downtime, reduced productivity and lost data.

When your PC goes down, IT comes to the rescue. That’s a reactive approach. In many cases, IT can predict when your PC will fail, based on remote monitoring and diagnostics.

Wouldn’t it be nice if there were a way to fix mass spectrometer issues before they snowballed into an instrument failure? This is where LC-MS remote monitoring comes in.

Mass spec remote monitoring allows your team to observe the current health your system efficiently—from anywhere, at any time.  That means fewer surprises and maximized uptime.

Your SCIEX LC-MS systems are compatible with StatusScope® Remote Monitoring service.  If you have a service or support contract, you just need to have it turned on by your SCIEX service professional. Enabling the StatusScope service will also require some help from your IT department. 

A Case for StatusScope Remote Monitoring
While most IT teams are familiar with the benefits of remote monitoring, network security and stability are their highest priority. Check out the following FAQ’s to help you explain the StatusScope service to your IT department, and address their concerns.

Question: How can I convince my IT team that StatusScope Remote Monitoring is secure?
Answer: The StatusScope Remote Monitoring is unidirectional. This means all communication is initiated from inside your firewall.  All communication is outbound-only, through port 443 with end-to-end encryption.

Only instrument operating parameters are monitored. Proprietary data is safe and not transmitted.

Question: What about encryption standards?
Answer: All SSL communication supports only strong encryption standards (TLS 1.2 only) with no downgrade negotiation

StatusScope Remote Monitoring only supports Transport Layer Security (TLS 1.2), with no downgrade negotiation. Thus, you can be confident that all your instrument operating parameters are within a highly secure environment.

Question: I need to be sure my research data is secure. How do I ensure it won’t get leaked?
Answer: Only instrument operating parameters are monitored. Proprietary data is safe. SCIEX does not collect or retain any analytic or assay information from connected devices.

Question: How do I know SCIEX is a reliable cloud provider?
Answer: StatusScope Remote Monitoring is built on the Axeda Machine Cloud platform from PTC Corp, an industry leader in IoT. PTC has Tier 1 data centers in global locations and is ISO 27001 certified. SCIEX is not running its own cloud; all data transactions happen in the PTC cloud.

Question:  I like the idea of mass spec remote monitoring services, but how do I convince my IT team to take on the project?
Answer: Your IT Team can implement the StatusScope Remote Monitoring Services with little effort. IT only needs to facilitate outbound HTTPS traffic. There is no need to open any new ports. A small number of external IP addresses need to be whitelisted for the StatusScope service to work.

Question: With all the data my research generates, how do I know StatusScope Remote Monitoring will not fill up our bandwidth?
Answer: StatusScope requires low bandwidth, similar to someone performing occasional web browsing.

ProteinPilot phosphopeptide library and DIA-NN

I have prepared a spectral library for a phosphopeptide enriched sample and I am generating my SWATH samples from similarly enriched samples. The problem is that when I use DIA-NN for the retention time alignment and quant, it doesn’t recognise the terminology of the spectral library annotated by ProteinPilot. DIA-NN recognises Unimod:21 for phosphorylation, but PP uses phospho(Tyr) etc. Other than changing the data dictionary to get around the mismatch, anyone have any suggestions for how I might resolve this? Thank you, Roz

Sequential processing of multiple data-files in ProteinPilot

I would like to use ProteinPilot 5.0.2 to process data-sets containing 16 wiff files acquired from fractionated peptides on a 6600 TripleTOF. A Precision T7910 workstation struggles to process four files in parallel and I would like to be able to queue sequential processing of individual files overnight. I currently use the ‘LC ‘ tab to load and process individual data-files but this leads to parallel processing. Is it possible to generate 16 .group files sequentially?

Posted by


Submit a Comment