Here is a list of the typical yearly software tasks that I have been involved in....

Before the run:

1)  Initializing the DB timeline.
Sometime in the winter, Jerome sends out an email to the softcoord hypernews list informing us of the timestamps that should be used to initialize the 'sim' and 'ofl' flavors in the DB for in the upcoming run.  Typically they are 20121210 (December 12 00:00:00) for 'sim' and 20121220 (December 20 00:00:00) for 'ofl' for the given year.
Documentation for the BEMC is here: https://drupal.star.bnl.gov/STAR/subsys/bemc/database/yearly-timestamp-initialization
For the EEMC, the procedure for uploading the tables is here: https://drupal.star.bnl.gov/STAR/subsys/eemc/calibrations/uploading-eemc-pedestal-status-and-gain-calibrations-db
The ideal tables should be used to initialize the 'sim' flavor, and for the 'ofl' flavor a set of good ped/status tables from the previous year can be used (these will be updated when we start taking data, so they're not too important at this point).  The latest gain tables for the Towers and Mapmt are from 2008 and 2006, and those can be found on RCF here: /star/u/stevens4/runList2013/

At the beginning of the run:

1)  Soon after the run starts, preliminary status and pedestal tables for the BEMC should be generated from one of the early runs and uploaded to the DB, so that there are reasonable values in the DB for FastOffline production.  When updating the database during the run, we typically upload them with a timestamp 1 second after the most recent timestamp in the DB (i.e. 20121220 000001, etc).  That way, when the final tables are generated after the run, they will replace the preliminary tables. 
Preliminary BEMC documentation: https://drupal.star.bnl.gov/STAR/blog/aohlson/2013/aug/21/draft-bemc-statusped-tables
EEMC documentation: https://drupal.star.bnl.gov/STAR/subsys/eemc/calibrations/calculating-eemc-pedestal-and-status-tables

2)  Update offline QA reference plots. 
The BEMC plots that we are responsible for are currently: bsmdeClNum, bsmdeEta, bsmdpClNum, bsmdpPhi, EmcCat4_Point_Energy, EmcCat4_Point_Eta, EmcCat4_Point_Phi, EmcCat4_Sigma_Eta, EmcCat4_Sigma_Phi, _Point_Flag.  The histograms must be updated for each of the types of triggers (the first two letters of each histogram name), which vary depending on the run, but can include: MB, HT, JP, CL, XX
Documentation here: https://drupal.star.bnl.gov/STAR/comp/qa/offline/currentqadocs/configuring-autoqa-subsystems

During the run:

1)  If any major changes occur in the BEMC, or if there's a change in the species that we're running, it would be good to update the status/ped tables in the DB (1 second after the previous tables) and to update the offline QA reference histograms (as above). 

2)  Keep an eye on the detector QA, respond to problems reported by offline QA shifters (they may email you directly, or Gene will email you), etc. 

After the run, before production:

1)  Generate the final BEMC status/ped tables for the entire run and upload to the DB (with the proper timestamps). 
Preliminary documentation: https://drupal.star.bnl.gov/STAR/blog/aohlson/2013/aug/21/draft-bemc-statusped-tables

After the run:

1)  Generate the final EEMC status/ped tables for the entire run and upload to the DB (with the proper timestamps). 
Documentation here: https://drupal.star.bnl.gov/STAR/subsys/eemc/calibrations/producing-adc-distributions-emcs-raw-daq-files
https://drupal.star.bnl.gov/STAR/subsys/eemc/calibrations/calculating-eemc-pedestal-and-status-tables 
https://drupal.star.bnl.gov/STAR/subsys/eemc/calibrations/uploading-eemc-pedestal-status-and-gain-calibrations-db