Release burndown predictions and project planning with TFS/Urban Turtle

Edit Subject

This is a general question for any POs out there using TFS/Urban Turtle :-) Help!

Does anyone have any suggestions as to how to meet these requirements from TFS using the Visual Studio Scrum v1.0 template (and Urban Turtle too if that helps).
Or alternatively, how have you achieved your requirements for project planning? Do they match the requirements below?

1.As a product owner I want to view a release burndown (in Story Points) so I can give a predicted end date to my project based on current estimates.
Acceptance Criteria:
The burndown is based on the current team’s average velocity over the course of the project.
The burndown goes from today’s date down until the predicted end of the project.
The burndown takes the total story points estimated for the project, and reduces them by the velocity for each sprint.
Tasks and bugs (estimated in hours) are not included in this.
The burndown shows the amount of work remaining at each sprint and an ideal trend line.

1.1 Ideally:
As a PO I can modify the planned future capacity of the team in my release plan to account for known periods of leave and this should reflect in my velocity and therefore my end date predictions.

2. As a product owner I want the ability to create and see the high level project plan at a Theme and/or Epic level with expected number of sprints required to finish each Theme/Epic so I can plan project milestones for the team to aim towards.
Acceptance Criteria:
Amount of work for each theme/epic is based on the current story point estimates for that theme/epic.
I can assign user stories(or PBIs) to these Themes/Epics
The velocity for each sprint is based on the team’s current average velocity over the course of the project.
I can change the order that Themes/Epics are planned to be developed in
I can de-scope certain Themes