Defence Support Group

Infrastructure Management (IM)
Menu

MinisterNavyArmyAir ForceDepartment

Davis Langdon Certification Services Davis Langdon Certification Services


Version No: 1.4
Issue Date: Aug 09
Review Date: Jul 10
Project Review Group (PRG)

Technical Authority: DGIAD
Subject Matter Expert: DCC & EDIAD

Purpose, Responsibilities and Membership

1. A key element of successful delivery of projects is the establishment and function of the Project Review Group (PRG). The PRG has a collective management responsibility and will be established for all major capital facilities projects. The purpose of the PRG is to provide guidance to the Project Director and a forum for senior level liaison with input to the project by sponsors, users and senior Defence management.

2. The typical membership of the PRG will include:

  • chair—Director General Infrastructure Asset Development (DGIAD) - or alternatively the Executive Director, Infrastructure Asset Development (EDIAD);
  • secretary—the Project Manager / Contract Administrator;
  • member—the sponsor(s) or their representative(s);
  • member—an IAD Director and Project Director;
  • member—each user's representative (Unit Commander or equivalent); and
  • member—Defence Support Operations Division's Regional Manager(s) or representative(s).

3. Other stakeholders’ representatives may be invited to contribute specialist knowledge to the PRG and may include:

  • Defence's Design Consultant(s);
  • Defence's Construction Contractor(s);
  • other specialist consultants or contractors; and
  • representation from other areas within Defence with an interest in the project.

4. The PRG is appointed by the DGIAD with membership being endorsed by the Defence Infrastructure Sub-Committee (DISC) through approval of the Detailed Business Case (DBC). The DGIAD is the authority for changes in the composition of the PRG.

5. The PRG should be established after project approval has been obtained and if required, the Public Works Committee (PWC) enquiry process has been completed.

6. The Project Director should propose the formation of the PRG and recommend its membership, role, objectives to DGIAD for inclusion in the project’s DBC. The DBC will be submitted to the DISC for endorsement, noting that the PRG's objectives, responsibilities and membership may change as the project evolves and progresses through design to delivery (construction).

7. The Chairman of the PRG is normally DGIAD, however DGIAD may delegate this responsibility to EDIAD, or to an IAD Director or Project Director depending on the complexity, sensitivity or phase of the project.

8. The PRG is responsible to and reports to DGIAD. The group: 

  • provides a forum for reviewing and making recommendations on key project issues;
  • provides guidance in relation to overall project planning, intermediate objectives and priorities on behalf of the project sponsor and other stakeholders;
  • provides strategic information and assistance to the Project Director in delivering the project;
  • reviews progress achieved and monitors risk to key performance parameters, such as against budget and schedule and relevant legislative matters; and
  • where end user, sponsor, Infrastructure Division and Defence Support Operations Division or Departmental expectations deviate from those approved by the DISC within the DBC, particularly in relation to capability outcomes, provides a forum for recommending changes from the approved DBC to DGIAD. (In some circumstances, if the capability and/or budgetary impact is significant, DGIAD may refer the matter to the DISC for direction.)

9. Where projects are the subject of a PWC enquiry, the PRG has additional responsibilities, which include:

  • reviewing progress on any recommendations made by the PWC in their report to Parliament as part of a progress report to DGIAD in May each year (for inclusion in an annual omnibus submission to the PWC in June/July);
  • referring any significant changes to the proposed scope or budget to DGIAD for referral to the PWC, as required by the PWC’s guidelines (note: ‘significant changes’ are major additions to the project expected to cost more than 10% of the project budget and which were not included in the evidence submitted to the PWC, or a proposed increase of greater than 10% to the approved project budget): and
  • overseeing the preparation of a project post-implementation report for the consideration and endorsement by DGIAD at the completion of the construction. This report will provide the basis for DGIAD to report to the Department of Finance and Deregulation and the PWC on the key outcomes and lessons learned during the project. (Further details of the post-implementation report are in Annex A.)

10. In carrying out its role, the PRG is to:

  • meet as required, typically once per quarter, noting that meetings may be required more often during the early stages of a complex project;
  • conduct meetings in accordance with a written agenda, and produce formal minutes of the meeting which will be stored in accordance with Defence archive policy clearly recording key considerations and recommendations regarding the delivery of the project; and
  • provide a forum for resolving conflicts/disagreements between Defence stakeholders and record decisions and recommendations in writing.

11. In additional to standard meeting agenda items such as the acceptance of previous meeting minutes, presentation of key project reports addressing key financial management aspects of the project (budget issues, forecast and actual expenditure, contract administration and asset rollouts), project schedule and other key project performance indicators, each PRG meeting agenda will include the following standing items: 

  • compliance with National Code of Practice for the Construction Industry;
  • compliance with the requirements of the Office of the Federal Safety Commissioner;
  • new business items; and
  • for those projects which have been the subject of PWC enquiries:
    • progress on recommendations made by the PWC;
    • significant proposed changes to approved project scope and budget; and
    • post –implementation report.

top

Home Welcome Contact Us Site Map Glossary