Service Management Effective support of in-scope services is a result of maintaining consistent service levels. The following sections provide relevant details on service availability, monitoring of in-scope services and related components.
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
Performance Management 17.1 The Contractor will appoint a suitable Account Manager to liaise with the Authority’s Strategic Contract Manager. Any/all changes to the terms and conditions of the Agreement will be agreed in writing between the Authority’s Strategic Contract Manager and the Contractor’s appointed representative.
17.2 The Contractor will ensure that there will be dedicated resources to enable the smooth running of the Framework Agreement and a clear plan of contacts at various levels within the Contractor's organisation. Framework Public Bodies may look to migrate to this Framework Agreement as and when their current contractual arrangements expire. The Contractor will where necessary assign additional personnel to this Framework Agreement to ensure agreed service levels are maintained and to ensure a consistent level of service is delivered to all Framework Public Bodies.
17.3 In addition to annual meetings with the Authority's Strategic Contract Manager, the Contractor is expected to develop relationships with nominated individuals within each of the Framework Public Bodies to ensure that the level of service provided on a local basis is satisfactory. Where specific problems are identified locally, the Contractor will attempt to resolve such problems with the nominated individual within that organisation. The Authority's Strategic Contract Manager will liaise (or meet as appropriate) regularly with the Framework Public Bodies' Contract Manager, and where common problems are identified, it will be the responsibility of the Contractor to liaise with the Authority's Strategic Contract Manager to agree a satisfactory course of action. Where the Contractor becomes aware of a trend that would have a negative effect on one or more of the Framework Public Bodies, they should immediately notify the Authority's Strategic Contract Manager to discuss corrective action.
17.4 Regular meetings, frequency to be advised by Framework Public Body, will be held between the Framework Public Bodies' Contract Manager and the Contractor's representative to review the performance of their Call-Off Contract(s) under this Framework Agreement against the agreed service levels as measured through Key Performance Indicators (KPIs). Reports will be provided by the Contractor to the Framework Public Bodies' Contract Manager at least 14 days prior to the these meetings.
17.5 Performance review meetings will also be held annually, between the Authority's Strategic Contract Manager and the Contractor's representative to review the performance of the Framework Agreement against the agreed service levels as measured through Key Performance Indicators. A summary of the quarterly reports will be provided by the Contractor at least 14 days prior to these meetings.
17.6 The Authority will gather the outputs from contract management to review under the areas detailed in the table below. Provision of management reports 90% to be submitted within 10 working days of the month end Report any incident affecting the delivery of the Service(s) to the Framework Public Body 100% to be reported in writing to FPB within 24 hours of the incident being reported by telephone/email Prompt payment of sub-contractors and/or consortia members (if applicable). Maximum of 30 from receipt of payment from Framework Public Bodies, 10 days target 100% within 30 days
STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.
Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:
Verizon Operations Support Systems Verizon systems for pre- ordering, ordering, provisioning, maintenance and repair, and billing.
Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System.
4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System.
4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA.
4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code.
4.1.5 The Power Producer shall commission the Project within SCOD.
4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer.
4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.
Emergency Mode Operation Plan Contractor must establish a documented plan to enable continuation of critical business processes and protection of the security of electronic County PHI or PI in the event of an emergency. Emergency means any circumstance or situation that causes normal computer operations to become unavailable for use in performing the work required under this Agreement for more than twenty-four (24) hours.
Quality Management System Supplier hereby undertakes, warrants and confirms, and will ensue same for its subcontractors, to remain certified in accordance with ISO 9001 standard or equivalent. At any time during the term of this Agreement, the Supplier shall, if so instructed by ISR, provide evidence of such certifications. In any event, Supplier must notify ISR, in writing, in the event said certification is suspended and/or canceled and/or not continued.
Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.
9.2.2 ECI shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from ECI’s Customers.
9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA.
9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.
