Hon. Nigel Hallett requests a breakdown of fixed asset purchases in the 2005-06 Annual Report, specifically differentiating between metropolitan and regional Western Australia. The Treasurer's response provides a breakdown but notes limitations due to statewide projects.

AnsweredQoN 4450Legislative Council
Asked
20 March 2007
Portfolio
Treasurer

QuestionView source ↗

The Annual Report on State Finances for the year 2005-06, published in September 2006, contains at page 16 a table numbered six entitled ‘Purchase of Fixed Assets’, and I ask -
(1) Would the Treasurer please provide a breakdown of figures illustrated in the table for -
(a) the metropolitan area; and
(b) Regional Western Australia?

AnswerView source ↗

Answered
1 May 2007
Responded by
Parliamentary Secretary representing the Treasurer
Response time
42 days
(b) Regional Western Australia?
The figures provided in Attachment A outline the split of capital works projects (i.e. purchase of fixed assets, some expensed capital items and Keystart Housing) between Metropolitan and Regional Western Australia for the 2005-06 expected out-turn, as at the 2006-07 Mid-year Review. It is important to note that a significant proportion of the capital works program cannot be allocated to a specific region or electorate as many projects relate to Statewide initiatives or large infrastructure, such as roads, pipelines or energy transmission lines, that straddle electoral/regional boundaries. These cashflows are categorised in the 'not?attributed' column. [see tabled paper no]
It is important to note that a significant proportion of the capital works program cannot be allocated to a specific region or electorate as many projects relate to Statewide initiatives or large infrastructure, such as roads, pipelines or energy transmission lines, that straddle electoral/regional boundaries. These cashflows are categorised in the 'not?attributed' column. [see tabled paper no]

Explore WA Government Data

Search the full archive in the free dashboard, or query programmatically via API.

Explore more