217x Filetype DOCX File size 0.29 MB Source: arena.gov.au
1. KNOWLEDGE SHARING PLAN [Drafting note: The Applicant should refer to the Knowledge Sharing Plan Guidance document provided on the application page of the ARENA website for further information on how to populate the Knowledge Sharing Plan template. This Knowledge Sharing Plan template is indicative of the requirements that ARENA would expect in the Knowledge Sharing Plan that is submitted by Applicants. Applicants are encouraged to adapt the provided Knowledge Sharing Plan template as relevant to the proposed Project noting not all deliverables or data fields may be relevant to your Project. The Applicant should refer to the HyGATE Initiative Funding Announcement for further information on Knowledge Sharing Plan requirements specific to the HyGATE Initiative. The information contained within the reports must be suitable for public dissemination and written in a manner that is suitable for the prescribed audience. The Applicant may like to include additional Knowledge Sharing deliverables or reports that include information that is confidential in nature for ARENA use only, which should be clearly specified as ‘Recipient Confidential Information.] 1.1 Knowledge sharing context Under the ARENA Act, ARENA’s mandate is to promote the sharing of information and knowledge about renewable energy technologies, with the objective of accelerating the development and growth of Australia’s renewable energy sector. 1.2 Knowledge sharing objectives [Drafting Note: Briefly describe the main concepts, questions or issues that the project is aiming to answer or resolve in the context of technology commercialisation.] 1.3 Knowledge sharing stakeholders/target audiences [Drafting Note: Briefly describe the main groups of stakeholders or target audiences that are potentially interested in the KS Objectives listed above, and the outcome of the project in general.] 1.4 Knowledge Sharing Deliverables [Drafting note: The table under item (a) applies where the Project relates to a study, and the table under item (b) applies where the Project relates to demonstration and deployment. ARENA will assist the Recipient in identifying which table applies to the Project.] ARENA may make requests from Projects (and portfolios of Projects) for particular topics to be covered either through lessons learnt reports (where applicable) or ad hoc reports, as required. Where ARENA has not made a specific request, topics are to be relevant and/or topical and have an appreciation for the key audiences. For the avoidance of doubt, business development and marketing material is not considered to be Knowledge Sharing Deliverables. HyGATE – Knowledge Sharing Plan 1 All deliverables are to be prepared to a standard acceptable to ARENA and where relevant, reflect ARENA’s Report Writing Tips & Guidelines which will be provided by ARENA to the Recipient or can be found on ARENA’s website. (a)Studies module No. Deliverable title Purpose Frequency When? Accessibility (Public or Content and delivery Recipient Confidential Information) (clause Error: Reference source not found) 1. ARENA 15-minute Efficient qualitative and quantitative Quarterly From Commencement Date Recipient Confidential ARENA to provide link to Project survey data gathering. Anonymised data is to 3 months following the Information survey each quarter. used internally for ARENA’s Final Milestone Date quarterly portfolio updates 2. Seminar/webinar/ Share Project information with other Minimum one per From Commencement Date Public Recipient to provide workshop participation ARENA funded Projects and key year, as agreed to the Final Milestone Date documentation (i.e. slides, stakeholders with ARENA. word document, pdf etc) to ARENA following attendance, to contain sufficient information to be read as a standalone document. 3. Final public study Share findings with the market. This Once only Final Milestone Date Public Report must comply with the report should include the extent to which ARENA Report Writing Tips the Project has contributed to and Guidelines, including building and strengthening linkages the minimum content. between Australian and German industry and research institutions, Public report to be published and how it has enabled the on a public platform exchange of skills and expertise to determined by ARENA. support the development of the Any sensitive information industry. (information not for public release) can be included as a confidential addendum for ARENA (as Recipient Confidential Information). 4. Ad hoc reports, Capture information not yet known No more than As required Agreed at time of Format and topic to be products, and activities three per year request agreed at the time of request. (b)Demonstration and deployment module HyGATE – Knowledge Sharing Plan 2 No. Deliverable title Purpose Frequency When? Accessibility Content and delivery (Public or Recipient Confidential Information) 1. ARENA 15-minute Efficient qualitative and Quarterly From Commencement Date Recipient Confidential ARENA to provide a link to the survey Project survey quantitative data gathering. to 12 months following the Information each quarter. ARENA may use this Final Milestone Date information in anonymised portfolio analysis and reporting. 2. Project Webpage To establish a high quality Established once, Within 3 months of Public Dedicated official Project webpage, project webpage that serves as then updated Commencement Date hosted on the Recipient’s website. It a central source of accurate, regularly must be engaging, clear and easy to reliable, and up-to-date navigate for a wide range of information about the project for stakeholders. The webpage should a wide variety of stakeholders. provide information including, at a minimum, the information described here in section . 3. Lessons learnt reports To share key lessons from the Frequency to be From Commencement Date Public Report must comply with the ARENA Project and implications for confirmed based [or the later of the Report Writing Tips and Guidelines, industry. This should include the on Milestones, but Commencement Date or including the minimum content. extent to which the Project has no less than every Financial Close] to the Final contributed to building and 6 months. Milestone Date Public report to be published on ARENA strengthening linkages between Knowledge Bank, and/or on a public Australian and German industry platform determined by ARENA. and research institutions, and Any sensitive information (information how it has enabled the not for public release) can be included exchange of skills and expertise as a confidential addendum for ARENA to support the development of (as Recipient Confidential Information). the industry. 4. Technology and Market To document and disseminate Once TBC Public Delivered as a professional and detailed Report the plans for the project and the report, typically less than 50 pages in market context within which it length, that clearly presents all the has been developed. This information suggested here in section . should provide a valuable and credible confirmation of the The report will be accompanied by a current state of play for key Financial Model spreadsheet as stakeholders. A Financial Model specified in section . will accompany the report. Report must comply with the ARENA Report Writing Tips and Guidelines, including the minimum content. Public report to be published on ARENA Knowledge Bank, and/or on a public platform determined by ARENA. Any sensitive information (information not for public release) to be included as a confidential addendum for ARENA only (rather than separate report). 5. Construction and To document and disseminate Once Draft version due at least 1 Public Delivered as a professional and detailed Commissioning Report an overview of the construction week prior to the relevant report, typically less than 50 pages in process, and in particular the Draft Briefing Workshop length, that clearly presents all the method and results of the (KS9) information suggested here in section . commissioning process. An updated version of the Financial The report will be accompanied by an HyGATE – Knowledge Sharing Plan 3 Model will accompany the updated version of the Financial Model Final due at one (1) month that is due at KS3. report. following Commissioning Report must comply with the ARENA Report Writing Tips and Guidelines, (c) Data collection This Project will use the ARENA data specification as set out in section 1.7. 1.5 Knowledge sharing third parties (a)Knowledge Sharing Agent ARENA may engage a suitably qualified consultant to act as an ARENA Knowledge Sharing Agent. ARENA reserves the right to engage a Knowledge Sharing Agent at any time. 1.6 Contents of Knowledge Sharing Deliverables 1.6.1. Project Webpage The webpage should be clear, professional and engaging. It should contain a project description and up to date information on project status with contact details for any community consultations, public queries or complaints handling. The webpage must contain an acknowledgement of ARENA funding for the project, a standard disclaimer about the website contents not being ARENA’s, and a link to the ARENA project webpage. This webpage design should use effective search engine optimisation techniques to ensure stakeholders can easily find it on the internet. It should also be promoted appropriately to the project’s stakeholders. The webpage should provide a clear and engaging graphical presentation of the operation of the project at a simplified systems-level, for typical operating scenarios. All project datasets defined as Public in section 1.7 should be available for download from the webpage. A project fact sheet should be downloadable from the webpage that includes detailed public information such as: (a)project timeline (e.g. date of commencement of construction, scheduled completion date vs. actual completion date, etc.); (d)technical and performance data; (e)key contractors; (f) key equipment suppliers; (g)total Project cost; and (h)summary of debt, equity and grant providers. HyGATE – Knowledge Sharing Plan 4
no reviews yet
Please Login to review.