diff --git a/docs/operations/taking-data.md b/docs/operations/taking-data.md
index e5970e16de1ab533fdaaee365d06bddc400b898c..5405695c9930f55b54c64eeb738da6872315ce96 100644
--- a/docs/operations/taking-data.md
+++ b/docs/operations/taking-data.md
@@ -1,29 +1,32 @@
 # Taking calibration scans & data
 
+The scans and the analyses of the scans need to follow a specific naming convention: 
+
+`<sbit-rate-scan|gbt-phase-scan|latency-scan|dac-scan>-<in|out>-[<comment>-]-<data+revision>`
+
+Meaningfull scans that are supposed to be stored for future reference are to be stored in the path `/gemdata/data/` with the above naming convention.
+
 ## Taking an S-bit rate scan at P5
 
 ### Starting the S-bit rate scan
 
-To take a threshold scan, first connect to [RCMS](http://cmsrc-gem.cms:20000/rcms/gui/servlet/FMPilotServlet), then create a miniDAQ session or attach to a running session.
+To take a threshold scan, first connect to [RCMS](http://cmsrc-gem.cms:20000/rcms/gui/servlet/FMPilotServlet), then create a miniDAQ3 session or attach to a running session.
 
-From the RCMS interface, click on "Connect".
+From the RCMS interface, click on "Connect" and then "Configure".
 
 Open the [xDAQ](http://srv-s2g18-33-01.cms:20100/urn:xdaq-application:service=calibration) calibration suite. In case the calibration suite page was already opened before you clicked on "Connect" in RCMS, reload the page manually.
 
-From the dropdown menu, select the calibration type "S-bit ARM DAC scan", then  set the number of iterations in the "Iterations" text box to 6 and leave all the other parameters to their default values. Click on "Apply settings".
-
-Go back to the RCMS interface, then follow these steps:
-1. click on "Configure" and wait for all the subsystems to be in _Configured_ state;
-2. click on "Start" and wait for the status of all subsystems to be _Running_;
-3. click on "Stop".
-
-Go back to the calibration suite in xDAQ, then click on "Run".
+From the dropdown menu, select the calibration type "S-bit ARM DAC scan", then  set the number of iterations in the "Iterations" text box to 6 and leave all the other parameters to their default values. Click on "Apply settings" and then "Run".
 
 While the scan is ongoing, from any p5 GEM DAQ machine check that the output files are being written in `/gemdata/runs/minidaq/sBitRateScan`.
 
 ### Analyzing the S-bit scan
 
-!!! todo
+To analyze an S-bit scan locate first the output in `/gemdata/runs/minidaq/sBitRateScan`. If these data are meant to be saved for later reference or analysis, copy the directory in the path `/gemdata/data/` with the naming convention:
+
+`<sbit-rate-scan-in-[<comment>]-<data+revision>`
+
+At these point analyze the scan using the command `gemos analyze sbit` from the terminal of `gem-locdaq02`: the path of the input file and output directory need to be specified, as well as the options for the plotting and allowed rate for the thresholds settings. 
 
 ## Taking a CSC-EMTF-GEM join run on the integration setup in building 904