Issue Management Clause Samples

Issue Management. 11.1. Any issues in relation to this ISA must be reported to the designated contacts (or successors to the role) listed in ▇▇▇▇▇ ▇. 11.2. If it is not possible to resolve an issue within 10 working days or the issue may have a negative impact on either the VOA or the Billing Authority, it will be escalated to the respective contacts in the overarching ISP.

Issue Management. Use of personal information

Issue Management. 8.1. Any issues must be reported to the designated contacts (or successors to the role) listed 8.2. If it is not possible to resolve an issue within 10 working days and/or the issue may potentially have a negative impact on either the VOA or the Billing Authority, it will be escalated to the respective senior management teams. 8.3. The senior management teams will be briefed on the issue including what steps have been taken to resolve the issue and any remaining barriers. They will agree any further action which could include contingency arrangements and negotiating agreed solutions.

Issue Management. The recording and reporting of events that have happened and will have an adverse effect on a Plan, from a delivery point of view (i.e. impacting the delivery of the Plan to budget, schedule or quality needs) or from a benefits realization point of view (i.e. impacting the proposed realization of benefits post-implementation).

Issue Management. 7.1. The Parties will make every reasonable effort to agree on the interpretation and application of this MOU. 7.2. To the extent practical, the Integrated Management Committee will resolve any differences in opinion and are committed to resolving differences in a timely manner. 1 By completing the EA within 300 days of acceptance of the Proponent’s EIS, the Agency will also be in compliance with the 365-day legislated timeline as per CEAA, 2012.

Issue Management. Governance committees address two types of decisions: a. Issue resolution b. Strategic DCS program decisions as per the roles and responsibilities matrix Issues may be escalated DCS Customer issues or enterprise issues identified by DIR, DCS Customers, or Service Providers. Issues are escalated following the escalation process described below. Strategic decisions may be identified by DIR, DCS Customers, or Service Providers. Both decision types are treated the same by the committees c. All DCS Customers have an opportunity to see the issue d. DIR performs triage and routes unresolved issues to appropriate committees e. All DCS Customers have an opportunity to document their perspective f. Agency committee members will review positions/perspectives in order to represent their partner agencies in the meeting

Issue Management. 9.01 The City will notify the Licensee of any matters relating to the use of the MROW or the use or operation of the Vehicles or any other nuisance that must be addressed by the Licensee. Without limiting the generality of the foregoing, the following are nuisances for the purposes of this Agreement: (a) Permitting a Vehicle to remain parked in one location for more than 72 hours; (b) Permitting a Vehicle to remain improperly parked; (c) Permitting a Vehicle to be locked to anything other than a City bicycle rack; and (d) Failure to remove a Vehicle in accordance with Article 11.00 or Article 14.00. 9.02 In the event of notification pursuant to Clause 9.01, the Licensee shall address issues identified by the City within the following timelines: (a) Within four (4) hours of receipt of a notice; (b) Notices received after 4pm MST shall be deemed to have been received at 8am the next day. 9.03 In the event that the Licensee fails to address the issue or nuisance in accordance with the timelines in Clause 9.02 the City may, without notice, rectify the issue and deduct the cost of City work activities associated with such rectification from the Security Deposit on a cost recovery basis. If the cost of rectification exceeds the Security Deposit, the City may invoice the Licensee for its costs incurred in such rectification.

Issue Management. Response time SLA Application technical support Root cause analysis Manage IBM PMR process Escalation through IBM channels Application user questions Supported hours 09:00-17:00 (GMT) 07:00-19:00 (GMT) 07:00-19:00 (GMT) Supported days Monday to Friday Monday to Sunday Monday to Sunday Web portal Email Onboarding review Telephone Monthly status reporting Quarterly service review Annual application audit Application monitoring IBM issue/patch notifications Best-practice tips & techniques Application housekeeping Software patching Transition of new application Consulting days included 0 12 24 Included in tier Excluded from tier

Issue Management. The Service Provider shall: (A) promptly identify all Issues that come to its attention, whether raised by its own Personnel, by Other Service Providers or by TfL, as a result of or in connection with Testing and/or during the operation of the Enforcement Infrastructure Service; (B) immediately classify any Issue arising (whether raised by TfL or the Service Provider) as one of the categories set out in clause 40.4; (C) promptly notify TfL of the Issue and the Service Provider’s proposed classification of the Issue in accordance with any timing requirements set out in the Specification; and (D) promptly notify any relevant Other Service Provider of any Issue which may affect that Other Service Provider’s Systems, or of any defects or problems arising from, that Other Service Provider’s System. In the case of an Issue which may affect the Core Service Provider’s Systems or defects in, or problems arising from, such Systems, such notification shall be made via the helpdesk facility provided by the Core Service Provider, where available, and in all other instances by notifying such employee of the Core Service Provider as TfL may notify to the Service Provider from time to time.