TRESA Costs and cost recovery

[Davsarper]

Goal Title

What will this work achieve? An agreed and formal process to recharge ATI projects being served by TRESA.

Description

Beyond establising the process it includes executing quarterly rechargers accoding by the information on TREs kept by the SA

Definition of Done

When will this be considered as succesfully completed?

• First part when the process is in place
• Then is an ongoing task

-> Consider breaking into two, one with an end and one recurring

Details

• RACI
  • Accountable team or person: RPM
  • Responsible team or person: REG
  • Informed and consulted people:
• Estimated effort FTE: 0.1 for recurring

Resourcing

August

• RPM: 0.05

Task and issue breakdown

Breakdown in specific tasks of maximum a month duration, tasks and issues may be added as necessary
Issues may span across repositories when necessary

• https://github.com/alan-turing-institute/tps-project-management/issues/223

Checklist

• This Story have been agreed with project members, it tackles prioritised work
  • If not: Label as ForPrioritisation so it discussed in the next monthly meeting, do not set a status
• I have filled in the Team Accountabe field
• I have included this Story in the agreed upon Milestone, set status as Planned
  • If not: set status as Backlog, to be Planned via weekly meetings or async discussions
• The work to be done is likely to span over a month
• I have broken down the work in monthly issues and added them above
• I have labeled this issue according to its main project: SATRE, TRESA, CORE DSH (ELA) or other (please agree and create a new label if necessary)
• I have stimated the total effort and added it in the body (under Details) but left the issue field blank

Reporting

1 November 4 December

SHM subscription (prod4) run out funds, partly due to an considerable increase in use.
This use is normal and acceptable given the new team need to learn and test.

After reviewing the budget and being prepared to absorb the cost the credit request was approved without RPM supervision, upong investigation it turns out the request and all previous requests have been submitted for Core coverage and aproved.

Therefore, no TRESA infrastructure costs have made it to the research budget.

Dummy environment were created for Dec DSGs to get used to using DSH, this is a good idea but should not come from the DSH budget again. We had conversations about new subscriptions for the TRESA team to test things and practice, there would be budget for some. This should not be done directly in the prod one.

Agreed with TRESA to hold a post DSG meeting this year and a strategic one early next, to see what the area will need, what to ask for and why. Basically to prepare a proposal.

[Davsarper]

@jemrobinson & REG (probably @edwardchalstrey1 ) what effort from you do you think this would take? Considering you are not Accountable but do contribute to it and are Responsible.
I would think your work for this story is actually already part of what you do for #27

[jemrobinson]

I think developing these processes might be quite a bit of work, but producing a report of costs will be very little effort once this is set up (probably too little to capture in FTE terms).

[Davsarper]

You are right, have split this in set up here #55

[martintoreilly]

Martin has not yet got a new TRESA finance project code set up due to finance focussing on the reforecast and overall REG budget reconciliation. he will chase w/c 11 Dec 2023

[Davsarper]

While capacity is stretched with the new year we have to clarify recharges process and prepare for the announcement in May's catch up

[Davsarper]

In May would really like to make this a priority and move it forward

[Davsarper]

Quoting myself "In May June would really like to make this a priority and move it forward"

[Davsarper]

This I cannot focus on while doing Community work, the change in priority was agreed during last monthly. DO clarify with Finance though where cost have ended up.