• Created by Unknown User (crowder), last modified on Aug 01, 2018

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Standard Operating Procedure – Logging Technician


V.374 | February 2018 / Original March 2014

I. PRE EXPEDITION


  • Complete mandated training for sea going staff within required time frame, see your supervisor for detail.
  • Attend Pre-cruise meeting if available
  • Assist in preparing up-coming expedition, duty as assigned by shore base supervisor(s)
  • You are responsible to learn, understand, and operate all instruments, including software applications, outlined in this SOP. This could include contacting vendor to attend instrumentation training classes, scheduling in house training, reading manuals, and any other process in order to complete this goal.
  • You are expected to learn, understand, and perform all the tasks outlined in this SOP.


II. PORT CALL - Start of an Expedition


  • Find your room and bunk assignment, drop your luggage off either in the F-deck Conference room or your room.
  • Go to the curator/logging office and begin cross over with the offgoing technician. Read the lab report from the previous Expedition and discuss any changes in equipment status or procedures.
  • Attend introductory meeting or any other safety or training meetings.
  • Assist with loading/unloading of cores, freight and other tasks as directed by the Lab Officer (LO) or Assistant Lab Officer (ALO).
  • Unpack all oncoming freight and distribute them accordingly
  • Collect and remove all trash from your lab.


III. SITE PREPARATION - Prior to arrival on site and core on deck

  • Ensure you are aware of the logging plan.
  • Coordinate with the EPM to determine who should be on the email distribution list for the data transfer alerts. The logging scientists may need to be included in the list to ensure data is accessible as soon as it is available.I don't know how helpful it is for the logging scientists if they receive several code-like emails about which file is ready and have already been transferred. In previous expeditions, there was even an apparent interest only in the processed data in order to avoid confusion with the raw data. Furthermore, the raw and processed data have to be placed in an accessible folder in Uservol anyway, and the logging tech has to send out an email to all interested scientists once this is done.Keith: I believe the transfer-auto-emails only trigger when the files go to Lamont, not Lamont to the ship. I just tell them the location of the Yellowstone drive. They usually occupy the Logging machine anyway, so they can check for the data if they want. Provide a list of recipients to the Marine Computer Specialists (MCSs) with instructions to update the distribution list.
  • Introduce the logging scientists to their workstations and the software and resources available.
  • Coordinate with logging scientist and engineer about any site survey data that needs to be plotted (e.g., seismic profiles and legacy wireline geophysical data).
  • Set-up a project in Petrel and/or Techlog. Get the final site or shotpoint coordinate from the logging scientist and update with the final site fix from the underway technician or operations superintendent. Load any site-survey or legacy data.
  • During the hole preparation for logging, establish communication with LDEO-BRG to update them on the logging plan.


IV. During Logging and Coring Operations


  • Primary duties are assisting as needed in the core lab. For details on Core lab responsibilities refer to the Core lab SOP.
  • In between primary duties in the core laboratory, plotIs this a task the tech does or should the scientists do? Is this routine? Is there a guide for this process?Both. But because Petrel requires a steep learning curve and the scientists are often busy with generating data and writing reports, I, as the logging tech, have been doing the manual job of updating the plots. In the end, it's the scientists who do the interpretation anyway.Keith: I usually don't provide a plot of the data. I do plot it for my own practice and to understand the data structures. I focus on providing detailed info about the files: e.g. main vs. down passes, a list of tool acronymns, the link to the ships logging tools webpage, etc.) I think its useful when correlators or phys. Props want to use th data. in Petrel, Techlog or both any core data relevant to core-log-seismic integration: PWL/C, GRA, MS, NGR, etc. Consult the logging scientist or co-chief as to what other data they want to plot.
  • During the rigging-up process, be available to provide overview of the logging operation or answer questions to any scientist who is interested.
  • Work closely with the logging engineer, keeping track of all information relevant to plotting the data (e.g., depth of drill string, estimates of water depth, etc.). If possible, monitor the logging operation in order to have a better understanding of the data being collected, which is significant when interfacing with logging scientist later.
  • After the logging operation, coordinate with the logging engineer about the transfer of data to LDEO-BRG. Retrieve relevant data from logging engineer on a flash drive or other media device. Ensure this data is not corrupted before transfer protocol.
  • Copy the raw data into the JR2Lamont Folder on the Yellowstone transfer drive. This can be done by the Schlumberger Engineer to ensure timely transfer of the data. Establish whose task this will beI have been receiving the raw data from Kerry so I can copy them to Yellowstone, Uservol and data1 and immediately right away email the logging scientists about where the files are located.Keith: Clay will often copy the data to Yellowstone. He prefers to keep the raw files separate, but will give them to anyone who asks for them. Clay just asks don't post the raw to Uservol, since they are similar data with different depth scales.. If there are any problems with data transfers, you can check the logging email account for any emails regarding the problem, talk to the logging engineer, or email Cristina Broglia (chris@ldeo.colombia.edu).
  • Copy the raw files in the 'data1' folder for backup purposes. Inform the logging scientists and EPM about the availability of the raw (and later, the processed) data. Double check with the Marine Computer Specialist (MCS) that the data transfer is operating correctly. Find solutions to any problems that arise.
  • Monitor your email and/or the Yellowstone:\Lamont2JR folder for the incoming processed data. Copy the files in data1 and/or other working folders for logging in that expedition. Inform the scientists about the availability of the data.
  • Backup files in an external hard drive dedicated for logging operations. Do not leave these often large files in the network folderWhich network folder is this?Any. Before, I tried to back-up in the share folder, but it almost filled up the drive, so the MCS had to transfer the files into an external drive. That's when I asked for USB drives for the logging techs to back-up project files. This old external drive is kept in the drawer of the port-side logging workstation.Keith: I save the logging files and exclude the seismics. The times when scientists are interested in seismics, they usually bring their own migrated data and/or depth models. These have often been "proprietary".. Ideally, we should keep the files on the external hard drive as long as possible, so they're available to answer questions, provide examples (for non-classified seismics and out-of-moratorium data), etc. As the drives may contain proprietary/classified information as well as moratorium data from recent expeditions, make sure to keep the external drive in a secured place.
  • Work with the logging scientist to open and display the raw data. UsingIs this routinely done? Does it plot nicely? Would you do it with the processed data as well?I routinely do it, especially for the raw data, so that the scientists can immediately have an idea of the logging profiles and start their general interpretation. Before, I also re-plot the processed data, but recently, I only do so upon the scientists request. Petrel is an analytical software and even their developers admit that it doesn't output the nicest graphic….but it does the job of conveying the data for interpretation, especially in relating the core and log data to the seismic profileI have never printed anything on the large paper plotter. the plotter in the user room, print a copy of the wireline log and, if available, post it on the whiteboard near the NGR for scientists to have an initial overview of the result. Copy the plot file into the relevant folder in data1.


V. During Transits


  • Continue processing cores through the lab as described above.
  • Core lab duties as described before apply here.
  • Continue helping the scientists in plotting the data or, if needed, in the core-log-seismic integration process.


VI. During Expedition


  • All staff are expected to perform shipboard duties as assigned by the Laboratory Officer as priority over other projects.
  • All staff are expected to report to work 5 minutes prior to the shift change time to cross-over with the off-going staff. You should be "ready to work" when you come on shift.
  • All staff are expected to have their breakfast prior to coming on shift, have their dinner (supper) after shift ends and they are relieved by the oncoming staff. Lunch is the only meal eaten during the shift.
  • Although break time onboard is scheduled at 3am, 9am, 3pm, and 9pm, due to our responsibilities, all staff are expected to adjust their break time according to "core-on-deck" schedules. A 15 minutes break time is reasonable. Note that when core flow is high enough, breaks may need to be cut short.
  • All staff on shift are expected to be available for the entire 12 hours. You must respond to a call or a page. If you will be working in an area where no speaker or phone available, it is recommended that you notify ALO or your fellow staff with your whereabouts.
  • All staff are expected to follow safety regulations at all time. All staff are also expected to observe the scientists' behavior and if they are not following safety rules, either correct it or inform the ALO.
  • Wearing headphones with music during shift is highly discouraged due to safety reasons.


VII. END OF EXPEDITION ACTIVITIES


  • Write the End-of-Expedition Technical Report and give a copy to the Lab Officer.
  • Make sure all raw and processed logging data are copied to the data1 folder before the MCSs cut off network folder access. All non-essential data should be erased from the hard disks of all the computers.
  • Get rid of all printed log plots from the laboratory for data security.
  • Pack up equipment being returned for repairs and give the Assistant Lab Officer the following information: IODP inventory number, value, weight, serial number, model number, vendor's name and country of manufacture.
  • Give the Lab Officer a list for port purchases if any.
  • Clean the lab and assigned area following the cleaning instruction listed by the LO/ALO. Bring all the trash to the incinerator. Glass and sharps get disposed of in port call.


VIII. PORT CALL – Off Going


  • Find the oncoming Technical Staff for your lab and perform crossover. Make available a copy of your tech report for crossover. Make sure the on-coming staff is aware of any changes made to the lab, procedures, current equipment status, and port purchases if necessary.
  • Attend the port call meeting.
  • Unload off going airfreight and frozen shipment, or any freight as required. Load on-coming freight if time permits.
  • You must check into the hotel appointed by IODP travel as soon as possible after departing the ship and must remain checked in until released from official duty which is based on departure time for the ideal "trip." This is because it may be necessary to contact you in order to find out some key piece of information, so please remain reachable that first day, if only by leaving messages with the front desk.


Created by Seth Frank on Exp. 354
Updated by Seth Frank on Exp. 359
Updated by Zenon Mateo on Exp. 371T (17 July 2017)
Updated by Lisa Crowder and Zenon Mateo on 374 (16 Feb 2018) Reviewed by Trevor Williams

  • No labels