Project Management Plan Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan and
PERFORMANCE MANAGEMENT SYSTEM 5.1 The Employee agrees to participate in the performance management system that the Employer adopted for the employees of the Employer; 5.2 The Employee accepts that the purpose of the performance management system will be to provide a comprehensive system with specific performance standards to assist the employees and service providers to perform to the standards required; 5.3 The Employer must consult the Employee about the specific performance standards and targets that will be included in the performance management system applicable to the Employee; 5.4 The Employee undertakes to actively focus on the promotion and implementation of the key performance indicators (including special projects relevant to the employee’s responsibilities) within the local government framework; 5.5 The criteria upon which the performance of the Employee shall be assessed shall consist of two components, Operational Performance and Competencies both of which shall be contained in the Performance Agreement; 5.6 The Employee’s assessment will be based on his performance in terms of the outputs/outcomes (performance indicators) identified as per attached Performance Plan, which are linked to the KPAs, and will constitute 80% of the overall assessment result as per the weightings agreed to between the Employer and Employee; 5.7 The Competencies will make up the other 20% of the Employee’s assessment score. The Competencies are spilt into two groups, leading competencies (indicated in blue on the graph below) that drive strategic intent and direction and core competencies (indicated in green on the graph below), which drive the execution of the leading competencies. Strategic direc on and leadership People management Program and project management Financial management Change leadership Governance leadersip Moral competence Planning and organising Analysis and innova on Knowledge and informa on management Communica on Results and quality focus
International Olympic Committee; International Red Cross and Red Crescent Movement As instructed from time to time by ICANN, the names (including their IDN variants, where applicable) relating to the International Olympic Committee, International Red Cross and Red Crescent Movement listed at xxxx://xxx.xxxxx.xxx/en/resources/registries/reserved shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Additional International Olympic Committee, International Red Cross and Red Crescent Movement names (including their IDN variants) may be added to the list upon ten (10) calendar days notice from ICANN to Registry Operator. Such names may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
Patch Management All workstations, laptops and other systems that process and/or 20 store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or 21 transmits on behalf of COUNTY must have critical security patches applied, with system reboot if 22 necessary. There must be a documented patch management process which determines installation 23 timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable 24 patches must be installed within thirty (30) calendar or business days of vendor release. Applications 25 and systems that cannot be patched due to operational reasons must have compensatory controls 26 implemented to minimize risk, where possible.