| 051108 IMACS F/2 Mosaic kickoff |
UserPreferences |
| Magellan Telescopes | FrontPage | RecentChanges | TitleIndex | WordIndex | SiteNavigation | HelpContents | moin.sf.net |
November 8, 2005, 10 AM OCIW Conference Room
Attending: Alan Dressler, Ian Thompson, Pat McCarthy, Greg Burley, Tyson Hare, Alan Uomoto
AGENDA
The following personnel assignments were agreed upon:
Principal investigator: Alan Dressler
Project scientist: Ian Thompson
Project engineer: Tyson Hare
Project manager: Alan Uomoto
After discussion about whether or not this should be an F/2-only project, the name became IMACS F/2 Mosaic Camera (but most thought that F/4 would remain an option if necessary).
A spreadsheet (BudgetImacsDewar2_051007.xls) was presented showing the dollar amounts listed in the proposal to the Magellan Council (August 2005, Dressler, Thompson, McCarthy, & Uomoto). No administrative support or contingency was included in this budget; Uomoto will add numbers before presenting it, and the MOU draft, to the Council.
It was noted that the E2V price quote will be in USD so exchange rate fluctuations will not be a problem or advantage.
Uomoto suggested a 10% be added for unanticipated overruns but others argued that the fixed costs were high and that a better number would be a flat $50,000K for contingency.
Uomoto reported that an account number will be created after Carnegie receives a signed MOU from the Magellan partners. The project can purchase things from the OCIW advance account but salaries must be reported directly to the project account. Uomoto asked people to track their time starting now.
Tyson Hare is not in the original budget for the project. We anticipate needing about 3 months of Tyson's time to build a new drawing package (checking for internal and external consistency) and for new design work on the focus mechanism.
Alan Bagish is not in the original budget but will be needed to design and implement the focus controller system. We will budget for one month of Alan Bagish's time.
A simple Gantt chart (example presented) with progress bars will be used for Council reports.
A task list maintained in a WBS by Uomoto will be used for internal project tracking.
A Technical Requirements Document is maintained by the project scientist. Hardware, software, operations, and performance requirements are tablulated, along with the scientific, operational, and/or cost drivers. Recording why certain requirements exist gives confidence when someone proposes relaxing them.
Requirements changes are announced immediately to project personnel, observatory management, and the observatory instrument scientist.
Uomoto will maintain a separate WBS for tasks. These were presented at today's meeting:
Thursday, December 8, 2005?