Problem Management System Sample Clauses

Problem Management System. The Service Provider will utilize the Problem Management System, including the Known Error Database / Knowledge Database, provided by MSI and integrate such with their Problem Management processes. Service Provider responsibilities include:
AutoNDA by SimpleDocs
Problem Management System. Service Provider’s responsibilities include: 1. Implement an automated Problem Management System and Known Error Database, including the integration of applicable Software, Equipment, communications, and databases. 1.1. Provide access to the Problem Management System, including the Known Error Database, to other Service Component Provider(s), DIR, DIR Customers, and authorized Third Party Vendors, which access shall include all appropriate and required licenses and/or interfaces. 2. Integrate with Service Provider’s other systems, including Incident Management, Configuration Management, Service Level Management, Change Management and Release Management. 3. Enable data exchange between the Problem Management Systems and the problem management systems of other Service Component Provider(s) and designated Third Party Vendors, as directed by DIR. 4. Limit access to the Problem Management Systems to the agreed levels (e.g. by DIR Customer) for the type of Authorized Users who require access to the systems. 5. Provide Service Provider personnel, other Service Component Provider(s) personnel, DIR, DIR Customers and authorized Third Party Vendors with appropriate training in using the Problem Management System and Known Error Database. 6. Grant DIR access to the database(s) of the Problem Management System, including the Known Error Database, and allow DIR and DIR Customer to monitor and view on an ongoing basis. 7. The Problem Management System shall include at a minimum the following: 7.1. Functionality to manage information for each Problem submitted to, and originating from, Service Provider. 7.2. A sophisticated set of problem resolution, diagnostic, and tracking Software and Equipment to enable the automation of monitoring, detection, and to facilitate the resolution of Problems. 7.3. The ability to electronically link or associate Problems with records associated with related Incidents, Changes, Releases, and Configuration Items or components. 7.4. A Known Error Database / Knowledge Database, used to capture, store, and retrieve information and solutions. This knowledge database will enable the sharing of the following: 7.4.1. Policies and procedures for resolving or circumventing errors. 7.4.2. Best practices for resolving or circumventing errors. 7.4.3. Methods to Resolve Problems among DCS Service Provider personnel, Third Party Vendors, and Authorized Users. 7.4.4. References for Configuration Items for Resolving or circumventing errors. 7.4.5. Contain ...
Problem Management System. Service Provider’s responsibilities include: 1. Implement an automated Problem Management System and Known Error Database, including the integration of applicable Software, Equipment, communications, and databases. 1.1. Provide access to the Problem Management System, including the Known Error Database, to other Service Component Provider(s), DIR, DIR Customers, and authorized Third Party Vendors, which access shall include all appropriate and required licenses and/or interfaces. 2. Integrate with Service Provider’s other systems, including Incident Management, Configuration Management, Service Level Management, Change Management and Release Management. 3. Enable data exchange between the Problem Management Systems and the problem management systems of other Service Component Provider(s) and designated Third Party Vendors, as directed by DIR. 4. Limit access to the Problem Management Systems to the agreed levels (e.g. by DIR Customer) for the type of Authorized Users who require access to the systems. 5. Provide Service Provider personnel, other Service Component Provider(s) personnel, DIR, DIR Customers and authorized Third Party Vendors with appropriate training in using the Problem Management System and Known Error Database. 6. Grant DIR access to the database(s) of the Problem Management System, including the Known Error Database, and allow DIR and DIR Customer to monitor and view on an ongoing basis. 7. The Problem Management System shall include at a minimum the following: 7.1. Functionality to manage information for each Problem submitted to, and originating from, Service Provider.

Related to Problem Management System

  • 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.

  • 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.

  • PERFORMANCE MANAGEMENT SYSTEM 6.1 The Performance Plan (Annexure A) to this Agreement sets out – 6.1.1 The standards and procedures for evaluating the Employee’s performance; and 6.1.2 The intervals for the evaluation of the Employee’s performance. 6.2 Despite the establishment of agreed intervals for evaluation, the Employer may in addition review the Employee’s performance at any stage while the contract of employment remains in force; 6.3 Personal growth and development needs identified during any performance review discussion must be documented in a Personal Development Plan as well as the actions agreed to and implementation must take place within set time frames; 6.4 The Employee’s performance will be measured in terms of contributions to the goals and strategies set out in the Employer’s Integrated Development Plan (IDP) as described in 6.6 – 6.12 below; 6.5 The Employee will submit quarterly performance reports (SDBIP) and a comprehensive annual performance report at least one week prior to the performance assessment meetings to the Evaluation Panel Chairperson for distribution to the panel members for preparation purposes; 6.6 Assessment of the achievement of results as outlined in the performance plan: 6.6.1 Each KPI or group of KPIs shall be assessed according to the extent to which the specified standards or performance targets have been met and with due regard to ad-hoc tasks that had to be performed under the KPI, and the score of the employer will be given to and explained to the Employee during the assessment interview. 6.6.2 A rating on the five-point scale shall be provided for each KPI or group of KPIs which will then be multiplied by the weighting to calculate the final score; 6.6.3 The Employee will submit his self-evaluation to the Employer prior to the formal assessment; 6.6.4 In the instance where the employee could not perform due to reasons outside the control of the employer and employee, the KPI will not be considered during the evaluation. The employee should provide sufficient evidence in such instances; and 6.6.5 An overall score will be calculated based on the total of the individual scores calculated above.

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;

  • Financial Management System Subrecipient shall establish and maintain a sound financial management system, based upon generally accepted accounting principles. Contractor’s system shall provide fiscal control and accounting procedures that will include the following: i. Information pertaining to tuition rates, payments, and educational assistance payments; and

  • 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:

  • Project Management Plan 3.2.1 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, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

  • Account Management 15.1 The Contractor is required to provide a dedicated Strategic Account Manager who will be the main point of contact for the Authority. The Strategic Account Manager will:  Attend quarterly, or as otherwise agreed, review meetings with the Authority, in person at the Authority’s premises or other locations as determined by the Authority  Attend regular catch-up meetings with the Authority, in person or by telephone/videoconference  Resolve any on-going operational issues which have not been resolved by the Contractor or Account Manager(s) and therefore require escalation  Ensure that the costs involved in delivering the Framework are as low as possible, whilst always meeting the required standards of service and quality. 15.2 The Contractor is also required to provide a dedicated Account Manager for every Framework Public Body using the Framework, if required by the Framework Public Body. The service to be provided will be agreed with each Framework Public Body and may include:  regular review meetings, which may be in person at the Framework Public Bodies’ premises, by video-conference, webinar or telephone  Regular catch-up meetings/telephone calls to discuss current and on-going issues  Work with the Framework Public Bodies Contract Manager to resolve any on-going operational issues  Work with the Framework Public Body ’s Contract Manager to pro-actively introduce initiatives to:  Create efficiencies in processes  Improve the environmental performance of the contract. 15.3 It is expected that end users will contact the Contractor in the first instance to resolve any operational issues. The Account Manager will act as a point of escalation to be contacted either by end users or by the Framework Public Body’s Contract Manager should there be issues that the Contractor needs to resolve. 15.4 Further details of the roles and responsibilities of the Contractor, Authority and Framework Public Bodies are provided in Schedule 4 – Management Arrangements

  • Change Management BellSouth provides a collaborative process for change management of the electronic interfaces through the Change Control Process (CCP). Guidelines for this process are set forth in the CCP document as amended from time to time during this Agreement. The CCP document may be accessed via the Internet at xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC 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 CSTC 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 CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC 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 CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!