<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Folks,<div class=""><br class=""></div><div class="">As discussed at the most recent CLAS Collaboration meeting, it seems that there will</div><div class="">be changes to how collaborators will select their service work for the upcoming year.</div><div class="">One of the new developments is that lists of tasks will be posted and collaborators will</div><div class="">be required to select some predefined fraction of their service load from these lists.</div><div class=""><br class=""></div><div class="">To this end, I have prepared a list of CALCOM-related tasks to put on this list of</div><div class="">service tasks (other tasks will be added for areas like reconstruction, common tools,</div><div class="">slow controls, etc). However, my focus is on CALCOM tasks.</div><div class=""><br class=""></div><div class="">As the service enrollment period is coming up soon, we need to finalize our list</div><div class="">to make sure that it is complete so that we can get the manpower that we require.</div><div class="">I ask the subsystem folks to look at the attached task list and to let me know what</div><div class="">is missing. Also remember that we require 0.25 FTE/member for service work and </div><div class="">our collaborators sign up for tasks once per year during the service work signup</div><div class="">period. I have therefore structured each line in the table as a task for one person to </div><div class="">commit to for the next year.</div><div class=""><br class=""></div><div class="">If I have under- or overestimated the manpower needed for a given task, let me know or</div><div class="">if I have omitted any subsystem CALCOM-related tasks, I would like for folks to tell me.</div><div class="">Also, I have not included service tasks associated with expert phone carriers, but I</div><div class="">am interested to know what your needs are in this area and a task list for hardware-related</div><div class="">work can be created.</div><div class=""><br class=""></div><div class="">I would like to finalize this list by Aug. 15 to be able to post the list in time for the</div><div class="">upcoming service work period. I have put a contact person for each task, so for</div><div class="">now these are the folks who should represent their subsystems. I will be speaking</div><div class="">to these folks in the upcoming weeks to finalize our list.</div><div class=""><br class=""></div><div class="">If you have any questions, please let me know.</div><div class=""><br class=""></div><div class="">Regards,</div><div class="">Daniel</div><div class=""><div class="">
<div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class="Apple-interchange-newline">***********************************************************************************<br class="">* *<br class="">* Dr. Daniel S. Carman <a href="mailto:carman@jlab.org" class="">e-mail : carman@jlab.org</a> * <br class="">* Staff Scientist office : (757)-269-5586 *<br class="">* Jefferson Laboratory web: <a href="http://userweb.jlab.org/~carman" class="">http://userweb.jlab.org/~carman</a> * <br class="">* *<br class="">***********************************************************************************</div><br class="Apple-interchange-newline" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class="Apple-interchange-newline">
</div>
</div></body></html>