Description

Ballarat Health Services is seeking suitably qualified building contractors from the Department of Treasury and Finance Construction Supplier Register for the supply of services to convert the existing Dialysis Unit into a Nocturnal Dialysis Unit.

The associated building works are required to assist with the change of use requirements from a BCA class 5 to a BCA class 9a building.

Tenderers shall be pre-qualified tenderers from the Department of Treasury and Finance's Construction Supplier Register.

All works are required to be conducted after hours. Small scale demolition works

Building works associated with fire compartment compliance

Installation of an Australian Standard compliant wet fire sprinkler system Construction of wall partitions

Coordination of services trades

All works to be done out of hours between the hours of 2030 to 0600 weekdays or all day Sunday.

Commissioning of all new systems and the provision of all required paper work to the Registered Building Surveyor for the purpose of the buildings change of use.

Project Report -A

1 PROJECT INFORMATION

2 GANTT CHART
Gantt Chart.
This chart represents the original baseline plan for the project. The shaded column between weeks 6 & 7 is the current date.

3 VARIANCE ANALYSIS (COST IN THOUSANDS)
The table contains the Planned Value (PV), Earned Value (EV), and Actual Cost (AC) values. Calculate Schedule Variance (SV%) and Cost Variance (CV%) using formulas given in Australian Standards

4 ESTIMATE AT COMPLETION
EAC.
The estimate at completion (EAC) is the expected total cost of the completing all work expressed as the sum of the actual costs to date and the estimate to complete (see PMBOK 2013 p224 Table 7-1).

5. Cost summary.
Summarise the impact of the costs on the project and whether there is a need to redefine the risks

6. FORECAST COMPLETION DATE
Forecast Completion Date
A Forecast Completion Date is derived from the Schedule Performance Index (SPI) and forecasts the end date of the project (see AS 4817-2006 pp.13-15 section 2.3.2). State whether re-baselining is required and the impact.

7. MILESTONE REPORT
Milestones are an event on a schedule which marks the completion of a key activity

Event Report.
Major events that the stakeholders should be made aware of are reported here (see risk management procedures 8.3.5 in Managing PRINCE2

Part -B Project Controls Report

1. PROJECT INFORMATION

2. CONTROLLABLE CATEGORIES

Controllable Categories.
Managing PRINCE2 page 92 identifies that the following management products are used to establish and maintain the project's controls for issues, changes and configuration management. The lists of controllable categories consist of deliverables, configuration items, project status accounts, daily logs, and issue items. The PMBOK Guide deals with control in each of the Knowledge Area chapters (4-13) according to the summary that is contained in section 3.6 Monitoring and Controlling Process Group.
Break each category down further according to the advice contained in Managing PRINCE2 chapter 9 and the PMBOK Guide chapter 4.4-4.5 and each section in the PMBOK Guide that deals with control in chapters 5 to 13, i.e. 5.6 Control Scope, 6.7 Control Schedule, Control Cost, etc. ...
Identify what those category items are for the project in the table below. Adjust by adding extra rows or columns the table as required to show the items in each of the category.

3.Configuration Procedural Outputs.
Managing PRINCE2 page 94 identifies that there are typically five core activities that manage deliverables, configuration management, planning, identification, control, status accounting, verification and audit. Additional information about configuration items can be found in the indexes of PRINCE2, the PMBOK, and Kerzner in section 11.33.
Identify the procedural outputs for those procedures where each category item corresponds to your table in section 2 above. You may wish to write a short answer as a paragraph to explain what is required, rather than list each item. Adjust by adding extra rows or columns or merging cells in the table as required to show the items in each of the categories.

4. EVENT DRIVEN CONTROLS
Event Driven Controls are control mechanisms that are assigned to control items as a consequence of events that occur within a project. The management of the events are governed by taking inputs, applying tools and techniques and generating or updating outputs. Each knowledge area in the PMBOK identifies a specific set of controls, some of which may be event driven.
Identify the inputs, tools and techniques and outputs that apply to each event driven controllable category item that you have identified in table 2 above. Provide a short explanation of how your event driven control will affect the item.

1.1 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.
1.2 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.
1.3 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.

Configuration
2.1 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.
2.2 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.
2.3 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.

3. Status Accounts
3.1 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.
3.2 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.
3.3 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.

4. Logs
4.1 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.
4.2 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.

4.3 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.

5. Issues

5.1 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.

5.2 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.

5.3 Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable.

Attachment:- Project Status and Control Reports.rar