There are several processes we need to work out:
- Process for modifying recharge formula
- An example is base charge for tiny clusters - probably not justified
- ways to encourage 'good' behaviour
- baseline the document and put it under change control sounds about right
- Process for buying from new vendors and novel hardware. Relationship to Lance's alternate vendor search?
- do we need an annual vendor review process, once we have the first new ones?
- if the (then) current set of vendors seems fine, carry on for a year? Review pricing and products, perhaps with an eye to how the products fit into the technology plan and resource allocations
- need some description for how to optimise full cost of ownership, not just price tag out the door of Fry's
- Process for keeping CD informed of upcoming purchases, and setting priorities if needed to resolve bottlenecks.
- SCSC could maintain a document of purchase projections. Checked on some schedule, but modifiable whenever new knowledge comes in
- how should CD organise itself to receive this information, and feed back to the SCSC any issues for installing it?
- the SCSC should be consulted on prioritising, if necessary
- Process for evaluating licences and deciding who pays
- how to consider new licences that might be of general interest. Trial periods?
- Process for CD to consult directorates on resource changes affecting scientific computing.
- we are affected by more than the unix/storage teams. eg the tech coordinator teams; Boris's efforts on corraling power and cooling.
- we need input during any horse trading phase in Ops. Hopefully impact statements could be provided on how any changes affect sci comp and we can respond to that to Sandy et al
- Process for getting SCSC input into the Operations Directorate Agenda and the Operations Directorate Strategic Business Plan
- Annual reviews of CD Scientific Computing and M&S expenditures
- Process for technical design reviews (see Fry's question above)
- Process for CD to consult about projects within the Unix/storage team. There's a list of projects...
- How do we handle SLAs?
- We also need to document this list as part of an SCSC "execution plan". We should also think about standing reports and metrics to the SCSC.