Core Functions Sample Clauses
The "Core Functions" clause defines the essential services or activities that a party is obligated to perform under the agreement. It typically outlines the main responsibilities, deliverables, or operational tasks that are central to the contract's purpose, such as providing technical support, maintaining software, or delivering specific products. By clearly specifying these key duties, the clause ensures both parties understand the fundamental expectations and helps prevent disputes over what constitutes satisfactory performance.
POPULAR SAMPLE Copied 1 times
Core Functions. Core Functions are critical to the successful operation of AONB Partnerships and Conservation Boards. Within core functions it is to be expected that staffing and associated overheads should merit particular protection. As set out in the Defra grant offer letter the grant offer includes a maximum contribution to core funding of 75% and is conditional on AONB Partnerships securing match funding of a further 25% of core funding from other sources (the respective figures for Conservation Boards are 80% and 20%). It is hoped and expected that Local Authority partner contributions to all Core Functions continue at a minimum of 25% (20%), or even at the same levels that have previously been invested. If Local Authority partners contribute more, then the “surplus” Defra funding may be used for other AONB work. Similarly non local authority partners may contribute and if external funding can be used to support core functions then this could also release money for other activity. In exceptional circumstances there may be core function items which merit special funding arrangements where Defra funding could be applied at 100%. Core Functions are defined in the defra MoA and as such provide guidance on minimum standards to allow successful operation of an AONB unit and the delivery of the AONB Management Plan.
Core Functions. Any portion of the Licensed Product that implements any of the Core Functions shall include all of the characteristics set forth in Sections 1 through 3 of these Robustness Rules. Such portions shall be implemented in a “Hardened Execution Environment” meaning they shall:
4.2.1 Comply with Section 1 above by employing Hardware-enforced mechanisms, where such enforcement is rooted in a Hardware Root of Trust, that (a) protect Decrypted HDCP Content, Device Secret Keys and values identified as Confidentiality Required in Appendix A to the HDCP Specification, where such values are also identified under Core Functions, against unauthorized exposure (such as encrypting Decrypted HDCP Content on any User-Accessible Bus, encrypting Decrypted HDCP Content, Device Secret Keys and such Confidentiality Required values in system memory, isolating memory in which Decrypted HDCP Content, Device Secret Keys or such Confidentiality Required values reside through access controls, using Device Secret Keys and such Confidentiality Required values only inside a secure processor, and embedding Device Secret Keys in silicon circuitry or firmware that is protected from being read, to the level specified in Section 4.3), and (b) effectively and uniquely associate the RSA private key, that is applicable to the HDCP 2.0 Presentation Device or function used to receive and decrypt HDCP Content in HDCP 2.0
4.2.2 Comply with Sections 1 through 3 of these Robustness Rules by protecting against unauthorized modifications of portions of the Licensed Product implementing Core Functions by checking integrity or otherwise ensuring integrity of such portions through the implementation of Hardware-enforced mechanisms, where such enforcement is rooted in a Hardware Root of Trust. Such mechanisms shall include a Secure Load of such portions and shall be designed such that unauthorized modifications made at any time will be expected to result in a failure of the implementation to perform the Core Functions and attempts to remove, replace, or reprogram Hardware elements of a Presentation Device or Repeater in a way that would compromise the content protection requirements of the HDCP Specification Rev 2.0 and the Compliance Rules in Licensed Products would pose a serious risk of rendering the Licensed Product unable to receive, decrypt or decode HDCP Content. By way of example, checking a signature on updateable firmware within a secure boot loader may be appropriate for this means.
Core Functions. 9.1.1 VAEF provides a range of services that are available to the local voluntary and community sector on an ongoing basis. They are detailed as follows:
Core Functions. Any portion of the Licensed Product that implements any of the Core Functions shall include all of the characteristics set forth in Sections 1 through 3 of these Robustness Rules. Such portions shall be implemented in a “Hardened Execution Environment” meaning they shall:
Core Functions. The Monitor will perform four core functions:
10.1 open and maintain an account for the receipt of payments from Western Union via the clerk of the Court and for the payment and accounting for all Monitor expenses;
10.2 assemble and direct a staff of personnel that the Monitor deems reasonably necessary to assist in the proper discharge of the Monitor’s duties;
10.3 determine whether Western Union is in compliance with the terms of the Agreement and this Monitor Engagement Letter and submit an Implementation Plan; progress reports for each six-month period beginning after the Monitor submits the Implementation Plan, and in each six-month period thereafter until the end of the forty-first month after the Agreement is fully executed, or until this Engagement is terminated early as provided in the Agreement; and a final evaluation in a Final Report; and
10.4 include in each report a detailed financial accounting of all of the Monitor’s activities and expenses to date and of all Western Union expenses beginning August 1, 2009 that the Monitor has determined were made to implement the Recommendations or to enhance the Program, as described in Paragraph 23.1.2 of the Agreement.
Core Functions. 1. The Core Functions of the Hosted Service are defined as following
a) Users’ ability to join an event, take part in a livestream, take part in a conference, watch a VOD recording (Stage).
b) Users’ ability to create or update events, manage event attendees, change session states (Backstage & Stage event management).
c) API Consumers’ ability to authenticate, create & update events, create & update sessions, create & update attendees (public API).
Core Functions. In providing the Core Services at Heywood, the Contractor shall carry out the core functions described in the sections below in response to requests by DWP Users. The Authority shall be responsible for the authorising signatories on the completed form templates where appropriate. The Contractor shall take these authorising signatories at face value and in good faith. The Contractor shall provide required inventory form templates in Microsoft Office to the Authority for non-FARIO enabled sites. The Authority shall make these form templates available on the DWP Intranet.
Core Functions. The “core functions” comprise the low-level actions, which will be carried out by the Contractor in response to requests made by individual file store Users.
Core Functions. 4.1 The duties of the Board are set out in section 43 of the Care Act and in Chapter 14 of the Care Act Statutory Guidance, issued under s78 of the Care Act 2014.
4.2 As fundamental core duties the Board is required to: ❒ Publish a Strategic Business Plan for each financial year detailing how it will meet its main objective and what Members will do to achieve this ❒ Publish an Annual Report detailing what the Board has done during the year to achieve its objectives and to implement its Strategic Plan ❒ Conduct any Safeguarding Adults Reviews in accordance with s44 of the Care Act 2014 and report on the findings of such reviews in the Annual Report.
Core Functions. (a) Librarians and Archivists are accountable for the operation and management of the University Libraries and Archives, and as such have primary responsibility for planning and directing the Libraries’ and Archives’ budgets, staff, facilities and technological infrastructure.
(b) Librarians and Archivists, while working in co-operation and partnership with all staff in the Library and Archives, have a lead role as mentors, problem-solvers and decision-makers within their Departments and Units.
(c) In the list of functions which follows, while portions of many of them could be carried out by others, the complete scope of any of the numbered functions will not be carried out by persons who are not Professional Librarians:
i. initiating and leading the implementation and evaluation of the Libraries’ programs and services;
ii. planning Library information systems and electronic services development;
iii. providing specialized reference assistance and research consultation, and setting standards for the provision of the Libraries’ reference and research services;
iv. designing curricula and delivering instruction to meet the information literacy and lifelong learning needs of the Queen’s community; v. developing, assessing and ensuring the preservation of the Libraries’ collections;