Infrastructure Management (IM) |
| Site Navigation :: Home>Estate Maintenance>0.10 Templates |
Estate Maintenance Templates
|
Template |
Use |
|
Infrastructure Appraisal |
||
Template for developing a Base IA Maintenance Plan |
||
Used to ask customers to document their known maintenance issues in preparation for a Desktop Appraisal. |
||
Statement of Work template for engagement of contractors to conduct Physical Infrastructure Appraisals. |
||
Bid Development |
||
CSIR template to be used for bidding of maintenance projects stemming from IA. |
||
CSIR for bidding for minor new works where the new works component is less than <$250k |
||
Provides guidance on how to complete a CSIR Minor New Works |
||
Provides guidance on the Estate risk assessment process. |
||
Program Brief |
||
Template for a project brief prepared by DS and provided to CMS detailing the project delivery restrictions, resources and/or risks. |
||
Project Brief template for describing projects prior to transition to the "Program Brief" process. |
||
Summary of estate and other activities occurring in the region that may affect scheduling the program of works. |
||
The baseline handover and takeover requirements for each project in the program. |
||
The baseline requirements for management and provision of information relating to each project in the program. |
||
Procurement |
||
Program Facilities Acquisition Template used to identify the procurement strategy for each project in the FACOPS program. |
||
Program Tender Plan template used to identify evaluation criteria and weightings in the evaluation of project tenders. |
||
Program Management |
||
Raised by the region and updated on a monthly basis. Used in the monthly review of program. Forwarded to National Office DEO prior to each regions quarterly review. |
||
Template for requesting >50% variation in project allocation or changes to CMS Management Fees, Reactive Maintenance or Contractual Commitment budgets. To be submitted to DEO for ASEP approval. |
||
Used in accordance with Business Rule 72 Non DSG Works (Devolved Projects). Commitment to transfer funds from the projects sponsors group to DSG. |
||
Sent to DEO to request an Emergency Allocation of funds for a unforeseen event such as a fire/cyclone/storm. |
||
Project Delivery |
||
Used in regions where project management is still a DS controlled function. Used to detail the scope of a project. |
||
Used to request and document approval of the environmental impact and management requirements for all risk managed works projects. |
||
Handover plan is an attachment to the project scope. It defines the requirements for handover and takeover of the project, and is included in the tender documentation. |
||
This site selection provides the user with a comprehensive checklist of points to consider when selecting a site. |
||
Tender Evaluation Board Report Template |
||
The Start up template is a guide for CMS to develop their own Contract Start-up checklist/procedure and to record data in the project file on DEMS |
||
Checklist to be use by project managers to ensure that all requirements are met during the handover from the sub-contractor. |
||
Certificate that may be presented to the new user of a facility, informing them of the DLP and who they should contact when problems are found. |
||
This checklist is issued to the user of a facility to assist them in the conduct of a thorough check of their new facility. Assists those who don't have a construction background to identify issues during the Defect Liability Period. |
||
When a project changes the use or user of a structure, the DS Project Officer submits this form to their regional information manager so that they may update DEMS. |
||
This form is completed as soon as a capital project is completed (ie. an asset is completed or enhanced) so that the AUC value can be transferred to the Fixed Asset Register. |
||
Ensures all project AUC balances in ROMAN have been transferred to the Fixed Asset Register and changes the project status in ROMAN to closed. |
||
Post Project Evaluation is to assess the level of success of a project in meeting its objectives and to identify opportunities for process improvement. |
||
FACOPS Finance |
||
ROMAN Project Creation Template (V5) (intranet only) |
Sent to DEO detailing the operating/capital breakdown of a projects allocation, so that the project may be created on ROMAN. |
|
Section 49 Month End Return (intranet only) |
Used to report WPNI at the end of each month. |
|
Raised by the region and forwarded to DBSM on completion of a project. Used to transfer the capital component of completed works from Assets Under Construction to the Assets in Use register. |
||
Raised by the region and forwarded to DEO. Used to close the project in ROMAN |
||
Purchase Order Request for projects that are to be delivered during the current financial year or that will span more than one financial year, where Financial Management and Accounting Regulation 10 applies. (Commitment of funds from future budgets) |
||
Approval to Dispose of a Defence Asset (intranet only) |
IAW DRB47 Pt 2. This form ensures the appropriate delegations are sought prior to the disposal of any Defence Infrastructure Asset (not land). Includes demolition. |
|
ROMAN Notification of Demolition / Write off (intranet only) |
Used to notify DEO finance to change an 'asset in use' to 'disposed' in the Asset Register. |
|
Contracts are to be documented on the Interim Defence Contract Register when the PO amount is >$90,909. This optional form assists project staff with data entry into the IDCR in accordance with Senate Order 192. Exclusions are listed ion the Defence Procurement Policy Manual at page 5.8.7 |
||
|
||