Page History

...

Pre Expedition Activities

...

• Ensure your computing equipment powers up and successfully connects to ship and shore networks.
• Cross-over with off-going staff regarding credential changes. Confirm your shipboard passwords and access: Oracle non-privileged and DBA accounts (test and production); ship and shore password safes; credentials for the storage network and email; credentials for build and dev resources, including software distribution credentials for the application servers.
• All personnel have responsibilities to ensure expedition data is returned to the shore warehouse. Review and confirm: data is backed up and ready for transport, we are clear to prepare the database for the new expedition.
• Prepare the database system for the new expedition. See BOX checklist, detail, rationale.
  • Moratorium enforcements.
    • Expunge the previous expedition's database content. Note that some information may need to be retained from the previous expedition--for example play cores for JR Academies and Schools of Rock. As-needed confirm with the staff scientist.
    • Clean out archived files on all logger systems. Confirm with off-going and on-coming Physical Properties, Paleomagnetics, and Imaging staff what has been done.
• Prepare the rig management system for the new expedition. See BOX checklist, detail, rationale.
  • Ensure the Operations Manager has access to the OPS user interface.
  • Ensure the Drillers have access to the DRILLER user interface.
  • Ensure the Collector utility is pumping iRIS data into Oracle.
• Manage laboratory accounts for scientists and techs. This includes: creating or enabling accounts for oncoming scientists and staff; and removing accounts for off-going scientists. Sometimes intervention is required with Auther permissions.
• Cross-over with off-going developers. What happened? What changed? What’s changing? What worked? What didn’t? Where can we improve?
  • Read the prior expedition reports, thoroughly.
  • Review change management records from the previous expedition. 
  • Confirm that you have access to (current) source code for recently changed product.
  • Spot-check routinely used services to ensure they are functioning: sampling programs, LIMS reports, MUT uploaders, web pages, Confluence support pages. SQL Developer access, LIME data editor.
• The labs are being made ready for expedition use. What is changing? What needs improvement? Anything not working that requires your knowledge and support? Prioritize, advertise.
• Attend introductory meetings including required safety and/or training meeting sessions. 
• Assist with loading/unloading freight and other tasks as directed by the Lab Officer or Assistant Lab Officer. 
• Provide courier services as-needed. If data was brought out, load it. If digital media were brought out, deliver it to those who requested it.
• You have expertise in software and code. Help others leverage that expertise.

...