Knowledge Sharing. Once per quarter (or more frequently in the event of material errors with respect to any of the Services or KPIs) BNY Mellon shall, upon Voya’s request, meet with Voya to: (1) assist Voya subject matter experts in understanding the performance of the Services, including any Changes implemented since the last meeting; and (2) answer Voya’s reasonable questions regarding the Systems and the Services; provided, however, that following the second anniversary of the Effective Date, such knowledge sharing meetings shall, upon Voya’s request, occur no more frequently than one time per rolling 12-month period.
Knowledge Sharing. 7.1 The Recipient must:
(a) in consultation with ARENA, implement and comply with the Knowledge Sharing Plan; and
(b) ensure the delivery of the Knowledge Sharing Deliverables, as set out at item 4 (Knowledge Sharing Plan) of Schedule 1 (The Project).
7.2 It is the Recipient’s responsibility to ensure that any Project documentation or information (including any Knowledge Sharing Deliverables) prepared for public release do not contain any Recipient Confidential Information.
7.3 The Recipient must categorise the documentation and information it provides to ARENA pursuant to the Knowledge Sharing Plan as follows:
(a) public: information that may be shared freely within ARENA, with industry participants, and with the public in general; and
Knowledge Sharing. Except as provided otherwise in an Engagement Schedule, with respect to all Services provided under Engagement Schedules hereunder, including Termination Assistance Services, Vendor will, upon the reasonable request of Prudential and with prior written notice, meet with representatives of Prudential (as designated by the Prudential Project Manager) in order to provide (a) the most recent Business Requirements Document to include Change Requests and the most current floor procedures and (b) notify Prudential of any anticipated problems with respect to the Systems or Services of which Vendor is aware, together with a proposed plan to avoid or resolve such problems.
Knowledge Sharing. On a mutually agreed schedule, Service Provider, Novation, VHA and UHC will provide information to each other to understand how Service Provider provides the Services and how Novation, VHA and UHC (or any of their designees) use the Services so that each may better fulfill its obligations under this Agreement.
Knowledge Sharing. 3.1 The Recipient must:
(a) in consultation with ARENA, implement and comply with the Knowledge Sharing Plan;
(b) ensure the delivery of the Knowledge Sharing Deliverables; and
(c) as reasonably required by ARENA, participate in relevant meetings, conferences, seminars, workshops, surveys and interviews, deliver presentations and provide briefings to the ARENA Board and ARENA staff and other relevant industry forums on Activity progress and achievement of the Outcomes.
3.2 It is the Recipient’s responsibility to ensure that any Activity documentation or information (including any reports) prepared for public release does not contain any Recipient Confidential Information.
3.3 The Recipient must categorise the documentation and information it provides to ARENA pursuant to the Knowledge Sharing Plan as follows:
(a) public unrestricted: information that may be shared freely within ARENA, with industry participants, and with the public in general;
(b) public restricted: information that may be shared freely within ARENA, with industry participants, and with the public in general, subject to any reasonable restrictions specified in the Knowledge Sharing Plan; and
(c) Recipient Confidential Information: information that may be shared in accordance with clause 18.
Knowledge Sharing. (a) Project Operator must provide the Knowledge Sharing Deliverables to the Commonwealth in accordance with Schedule 4 (“Knowledge sharing plan”).
(b) If Project Operator receives funding for the Project from the Australian Renewable Energy Agency or another Commonwealth Entity, then the Commonwealth will act reasonably in agreeing any amendments to the Knowledge Sharing Deliverables to align with any equivalent obligation on Project Operator to provide knowledge sharing deliverables to those Government Authorities.
(c) Project Operator must, acting reasonably and in good faith, categorise the Knowledge Sharing Deliverables it provides to the Commonwealth pursuant to this clause 13 as follows:
(i) public information: information that may be shared freely within the Commonwealth, with industry participants and with the public in general; or
(ii) confidential information: information that may only be shared in accordance with paragraph (d) or clause 31 (“Confidentiality”).
(d) The Commonwealth may disclose information received pursuant to this clause 13 that is marked by Project Operator as ‘confidential information’ to the public on an aggregated and anonymised basis.
(e) Where Project Operator submits a Knowledge Sharing Deliverable to the Commonwealth, the Commonwealth (acting reasonably) will notify Project Operator within a reasonable period of receipt of the Knowledge Sharing Deliverable as to whether or not it approves the Knowledge Sharing Deliverable for the purposes of this agreement. Without limitation, it will be unreasonable for the Commonwealth to reject that Knowledge Sharing Deliverable where it complies with the Knowledge Sharing Plan and this agreement.
(f) Where the Commonwealth notifies Project Operator under paragraph (e) that it does not approve the Knowledge Sharing Deliverable, the Commonwealth must, at the same time, notify Project Operator of such further information or updates to the deliverable that the Commonwealth reasonably considers are required in order for the deliverable to meet the requirements of this agreement and/or the Knowledge Sharing Plan and a reasonable timeframe within which Project Operator must resubmit that Knowledge Sharing Deliverable. Where Project Operator fails to resubmit that further information or updated Knowledge Sharing Deliverable within that timeframe or the updated Knowledge Sharing Deliverable is not approved for the purposes of this agreement, that failure will be deemed to be a failure to comp...
Knowledge Sharing. (a) The Recipient must:
(i) in consultation with ARENA, implement and comply with the Knowledge Sharing Plan;
(ii) use its best endeavours to achieve the objectives specified in the Knowledge Sharing Plan;
(iii) in consultation with ARENA, undertake the Knowledge Sharing Activities;
(iv) ensure that the Knowledge Sharing Activities are disseminated as widely as possible;
(i) ensure that the Knowledge Sharing Activities are suitably resourced and coordinated and that they are implemented to the standard required by the Knowledge Sharing Plan;
(v) provide the Knowledge Sharing Deliverables to ARENA in accordance with the Knowledge Sharing Plan;
(vi) ensure that Knowledge Sharing Deliverables and Project Lessons Learnt are properly captured, securely stored, and reported to ARENA in accordance with the Knowledge Sharing Plan;
(vii) be reasonably available to answer any queries relating to the Project raised by ARENA; and
(viii) at the reasonable request of ARENA, participate in relevant meetings, conferences, seminars, workshops, surveys and interviews, deliver presentations and provide briefings to the ARENA Board and ARENA staff and other relevant industry forums on the progress of the Project.
Knowledge Sharing. 3.1 The Recipient must:
(a) in consultation with ARENA, implement and comply with the Knowledge Sharing Plan; and
(b) as reasonably required by ARENA, participate in relevant meetings, conferences, seminars, workshops, surveys and interviews, deliver presentations and provide briefings to the ARENA Board and ARENA staff and other relevant industry forums on Activity progress and achievement of the Outcomes.
3.2 It is the Recipient’s responsibility to ensure that any Activity documentation or information (including any reports) prepared for public release do not contain any Recipient Confidential Information.
Knowledge Sharing. Complete a post event survey.
Knowledge Sharing. HPES will: (A) explain and review the procedures set forth in the Policies and Procedures Manuals with HPI at least once every quarter; (B) upon HPI’s request, assist HPI subject matter experts (as designated by HPI) in understanding the performance of the Services, including attending meetings with HPI or, subject to the confidentiality obligations set forth in Article 20, its designee to the extent necessary for such designee to provide products and services to HPI; and (C) provide such training and documentation as HPI may request from time to time to enable HPI to understand and operate the Systems used to provide the Services and to understand and provide the Services after expiration or termination of this Agreement.
