Conclusions and agreement Sample Clauses

Conclusions and agreement. St Helens Council and St Helens CCG have worked together to put arrangements in place for hospital discharge in response to the COVID-19 pandemic with St Helens Council acting as the lead commissioner. This has included securing capacity within the care homes sector, identifying hospital discharge cases along with commissioning care and reviewing service provision in line with national guidance. This has proved effective in allowing uninterrupted flow between hospital and community settings within the system. This variation provides evidence of agreement between the partners of the approach to support for hospital discharge in 2020/21 including the funding flows. Funding for COVID-19 is accounted outside of the S75 Agreement. SCHEDULE 6 Variation – Repayment of Contributions SCHEDULE 6
AutoNDA by SimpleDocs

Related to Conclusions and agreement

  • Conclusion of the Agreement 1. All offers made by the Freight Forwarder are non-binding.

  • Covenants and Agreements Each Grantor hereby covenants and agrees that:

  • Application and Agreement a) Application to the plan is voluntary. A faculty member who wishes to be considered for an early retirement incentive shall do so in keeping with the procedures and dates described in the Employer's annual "letter of interest" sent to eligible employees. Such application would then be considered a standing application for the following twelve-month period. Applications must be submitted annually in response to the Employer's "letter of interest". The Union shall be advised in writing of all applications made by faculty members.

  • Conflict Between this Amendment and the Agreement This Amendment shall be deemed to revise the terms and provisions of the Agreement to the extent necessary to give effect to the terms and provisions of this Amendment. In the event of a conflict between the terms and provisions of this Amendment and the terms and provisions of the Agreement this Amendment shall govern, provided, however, that the fact that a term or provision appears in this Amendment but not in the Agreement, or in the Agreement but not in this Amendment, shall not be interpreted as, or deemed grounds for finding, a conflict for purposes of this Section 4.1.

  • Conclusions and Recommendations The demonstration and evaluation process provided an opportunity to test community specific tools with a range of end users from the memory institution domain and to gain greater insight into both the current and future evolution of the SHAMAN prototypes for preservation, access and re-use. Xxxx et al. (2000) in their user evaluation study of the Alexandria Digital Library which incorporated the evaluation of a Web prototype by earth scientists, information specialists and educators raised four key questions in relation to their findings that SHAMAN may be well advised to consider, they are paraphrased here with our conclusions from the investigations. What have we learned about our target organizations and potential users?  Memory institutions are most definitely not a homogenised group; their needs and requirements differ greatly across the domain.  Representatives of the archives community are agreed on the benefits of SHAMAN‟s authenticity validation function.  The representatives of government information services remained unconvinced as to the need or benefit of grid technologies or distributed ingest while librarians saw the value of grid access as an asset of the framework. What have we learned about the evaluation approach for digital preservation?  Within the limits of the exercise, in terms of time-frame and resources, the approach adopted has generated useful information for the further development of demonstrators and for the development of the SHAMAN framework overall. What have we learned about the SHAMAN ISP1 demonstrator?  Respondents to the evaluation questionnaires and the focus groups indicate that, overall, the presentation of the demonstrator worked effectively and that, in general, participants in the demonstration and evaluation events were able to understand the intentions of the demonstration and to apply the ideas presented to their own context. What have we learned about the applicability of the SHAMAN framework to memory institutions?  Respondents to the questionnaires and participants in the focus groups readily identified the value of the SHAMAN framework to their own operations. The majority had not yet established a long-term digital preservation policy, but recognized the need. Generally, the concepts of distributed ingest and grid operations found favour.  Virtually all practitioners in the focus groups, however, drew attention to need of a lower level demonstration that would be closer to their everyday preservation troubles, especially for digital preservation to be applied to non-textual materials, such as film, photographs and sound archives. In addition to the criteria suggested by Xxxx et al., we can add a further project-related question: What have we learned that has implications for the training and dissemination phase of the Project?  It was not part of the remit of the demonstration and evaluation specifically to discover information of relevance to the training and dissemination function. However, a number of factors will affect the efficacy of any training programme in particular. o First, no common understanding of digital preservation can be assumed of the potential target audiences for training. Consequently, it is likely that self-paced learning materials will be most effective in presenting the SHAMAN framework. o Secondly, the aims of SHAMAN as a project must be conveyed clearly: specifically, that it is a kind of „proof-of-concept‟ project and is not intended to deliver a package of programs capable of being implemented by institutions. o Thirdly, it needs to be emphasised that the SHAMAN framework is not limited to text documents; it can be applied to materials of all kinds. However, the demonstrations relate to bodies of material that were actually available for use. o Fourthly, the existing presentation materials are capable of being adapted for use in training activities. o Finally, the target audiences will appreciate the possibility of online access to the demonstrator, which will need to have very great ease of access in order that people with diverse backgrounds are able to use it with equal facility. We believe that, overall, WP14 has met its aims and objectives in this demonstration and evaluation of ISP1. Valuable lessons have been learnt by all parties involved, which will be transferred to the evaluation of ISP2 in the coming months.

  • REPRESENTATIONS, WARRANTIES, AND AGREEMENTS Section 6.01.

  • Representations, Warranties and Agreements to Survive All representations, warranties and agreements contained in this Agreement or in certificates of officers of the Company or any of its subsidiaries submitted pursuant hereto, shall remain operative and in full force and effect regardless of (i) any investigation made by or on behalf of any Underwriter or its Affiliates or selling agents, any person controlling any Underwriter, its officers or directors or any person controlling the Company and (ii) delivery of and payment for the Securities.

  • Acknowledgement and Agreement By execution below, the Transferor expressly acknowledges and consents to the pledge of the 2022-1 SUBI Certificate and the 2022-1 SUBI and the assignment of all rights and obligations of the Transferor related thereto by the Transferee to the Indenture Trustee pursuant to the Indenture for the benefit of the Noteholders. In addition, the Transferor hereby acknowledges and agrees that for so long as the Notes are Outstanding, the Indenture Trustee will have the right to exercise all powers, privileges and claims of the Transferee under this Agreement.

  • Modifications and Add-ons Subject to the licensing of the required development rights under separate agreement, Provider shall be entitled to develop Modifications and Add-ons for the Software and shall be permitted to Use Modifications and Add- Ons with the Software in accordance with the license grant to the Software set forth in Section 3.1 herein. Provider shall promptly notify SAP if and when Provider is planning to develop Modifications or Add-ons to the Software. The notification provided by Provider shall include a high level description of the intended functionality and of the timeframe planned for such development. In addition, any Modifications or Add-ons must not i) unreasonably impair, degrade or reduce the performance or security of the Software; ii) enable the bypassing or circumventing of SAP license restrictions and/or provide users with access to the Software to which such users are not directly licensed; and/or iii) permit mass data or metadata extraction from an SAP software to a non-SAP software for the purpose of replacing the Software as the data’s system of record. With regards to the aforementioned item iii), Provider shall refer any Customer requiring such information to SAP.

  • GENERAL PROVISIONS AND RECITALS 12 1. The parties agree that the terms used, but not otherwise defined in the Common Terms and

Time is Money Join Law Insider Premium to draft better contracts faster.