-
- Posts: 14
- Joined: Thu Feb 03, 2011 4:22 pm
Advertisement
Mass Spec SOP
Discussions about GC and other "gas phase" separation techniques.
3 posts
Page 1 of 1
Can someone recommend things that a GC-MS standard operating procedure should have? I need to write an SOP, but I am very new to the MSD. I would like to have enough detail for a reasonable person to operate the system. For example, what are good parameters for the system when not in use (stand-by mode)? Which items should be immediately available to the user and which are ok to say "see the manual"? How often should the source be cleaned? I know this is a very general question, but does anyone have any tips for a rookie like myself? What common mistakes should I be avoiding?
-
- Posts: 517
- Joined: Thu Jul 14, 2016 12:08 pm
You can find plenty of examples on the internet.
Write it in the sense that a person with the knowlegde your institute defines as 'common' can run a sample from start to finish. I would try to avoid the line 'check the manual'.
A good practice is to let users run a system suitability test (SST) before operation. This is a standard solution that users inject and evaluate based on your criteria: for instance peak X need a S/N of 5, or the separation between peak X and Y needs to be <60%. If the test doesn't pass, the users should contact an advanced user before running.
- Source cleaning: typically 2 times / year.
Write it in the sense that a person with the knowlegde your institute defines as 'common' can run a sample from start to finish. I would try to avoid the line 'check the manual'.
A good practice is to let users run a system suitability test (SST) before operation. This is a standard solution that users inject and evaluate based on your criteria: for instance peak X need a S/N of 5, or the separation between peak X and Y needs to be <60%. If the test doesn't pass, the users should contact an advanced user before running.
- Source cleaning: typically 2 times / year.
-
- Posts: 326
- Joined: Wed Oct 02, 2013 12:20 pm
Hello
1. SOP should contain all needed information to operate instrument - for example: how to switch it on (order), how to tune it, how to set up method etc.
2.All maintenance procedure (done by operator) should be in separate document. And all should be written whith sense. For example ion source should be cleaned as needed (not every 6 month) because its state (contamination) depends on your samples/std etc.
Regards
Tomasz Kubowicz
1. SOP should contain all needed information to operate instrument - for example: how to switch it on (order), how to tune it, how to set up method etc.
2.All maintenance procedure (done by operator) should be in separate document. And all should be written whith sense. For example ion source should be cleaned as needed (not every 6 month) because its state (contamination) depends on your samples/std etc.
Regards
Tomasz Kubowicz
3 posts
Page 1 of 1
Who is online
In total there are 31 users online :: 2 registered, 0 hidden and 29 guests (based on users active over the past 5 minutes)
Most users ever online was 4374 on Fri Oct 03, 2025 12:41 am
Users browsing this forum: Bing [Bot], Semrush [Bot] and 29 guests
Most users ever online was 4374 on Fri Oct 03, 2025 12:41 am
Users browsing this forum: Bing [Bot], Semrush [Bot] and 29 guests
Latest Blog Posts from Separation Science
Separation Science offers free learning from the experts covering methods, applications, webinars, eSeminars, videos, tutorials for users of liquid chromatography, gas chromatography, mass spectrometry, sample preparation and related analytical techniques.
Subscribe to our eNewsletter with daily, weekly or monthly updates: Food & Beverage, Environmental, (Bio)Pharmaceutical, Bioclinical, Liquid Chromatography, Gas Chromatography and Mass Spectrometry.
- Follow us on Twitter: @Sep_Science
- Follow us on Linkedin: Separation Science
