Service Request Reporting Sample Clauses

The Service Request Reporting clause establishes the requirements and procedures for documenting and communicating requests for services under the agreement. Typically, it outlines how service requests should be submitted, the information that must be included, and the timelines for acknowledgment or response by the service provider. This clause ensures that both parties have a clear, standardized process for handling service needs, reducing misunderstandings and facilitating efficient service delivery.
Service Request Reporting. Service Provider’s responsibilities include: 1. Provide a monthly report on use of the knowledge base to fulfil Service Requests. 2. Provide a monthly report, or more frequently as required by DIR, including: 2.1. Progress toward fulfillment and the status of all Service Requests. 2.2. Committed fulfillment timeframes, anticipated completion times, and status. 2.3. Ownership and activities toward fulfillment for all open Service Requests. 2.4. Changes in Service Request status throughout the Service Request lifecycle. 2.5. Categories of Service Requests, by DIR Customer. 3. Provide a monthly report on Service Provider and other Service Component Provider(s) staff activities on Service Requests. 4. Provide a monthly report on outstanding and aging Service Requests and the trends thereof. 5. Provide reports on all requesting mediums to show demand, forecasts on demand, trends, product health, spend, problem areas, and backlogs. 6. Provide reports on the effectiveness of the Request for Solution process, including: time- to-solution, time-to-respond, accuracy of proposals, accuracy of forecast and captured compared to canceled.
View SourceView Similar (3)
Service Request Reporting. Service Provider responsibilities include: 1. Provide a monthly report on use of the knowledge base to fulfil Service Requests. 2. Provide a monthly report, or more frequently as required by DIR, including: 2.1. Progress toward fulfillment and the status of all Service Requests. 2.2. Committed fulfillment timeframes, anticipated completion times, and status. 2.3. Ownership and activities toward fulfillment for all open Service Requests. 2.4. Changes in Service Request status throughout the Service Request life cycle. 2.5. Categories of Service Requests, by DIR Customer. 3. Provide a monthly report on Service Provider and DCS Service Providers staff activities on Service Requests. 4. Provide a monthly report on outstanding and aging Service Requests and the trends thereof. 5. Provide reports on all requesting mediums to show demand, forecasts on demand, trends, product health, spend, problem areas, and backlogs. 6. Provide reports on the effectiveness of the Request for Solution process, including: time- to-solution, time-to-respond, accuracy of proposals, accuracy of forecast and captured compared to canceled.
View SourceView Similar (2)
Service Request Reporting. ‌ Contractor will: Produce monthly, or on demand, reports and data extracts on the service request data. Provide a mechanism whereby JWA is able to run and print these reports independently if so desired by the County if available.
View SourceView Similar (2)
Service Request Reporting. Contractor shall provide periodic reporting on the performance and practice of Service Request Management, including:  Report on use and effectiveness of the knowledge base to fulfil Service Requests.  Reports on all requesting mediums to show demand, forecasts on demand, trends, product health, spend, problem areas, and backlogs.  Reports on the effectiveness of the Service Request process, including (but not limited to): Committed fulfilment timeframes, anticipated completion times, and status; Ownership and activities toward fulfilment for all open requests; Changes in requests status throughout the Service Request life cycle; Volumes and categories of requests; Outstanding and aging requests, and the trends thereof.  Reports on the effectiveness of the Request for Solution process, including (but not limited to): time-to-solution, time-to-respond, accuracy of proposals, accuracy of forecast and comparing captured to cancelled requests.
View Source

Related to Service Request Reporting

  • Monthly Reporting Within twenty (20) calendar days following the end of each calendar month, Registry Operator shall deliver to ICANN reports in the format set forth in Specification 3 attached hereto (“Specification 3”).

  • Progress Reporting a) RECIPIENT must satisfactorily demonstrate the timely use of funds by submitting payment requests and progress reports to ECOLOGY. ECOLOGY reserves the right to amend or terminate this Agreement if the RECIPIENT does not document timely use of funds. b) RECIPIENT must submit a progress report with each payment request. Payment requests will not be processed without a progress report. ECOLOGY will define the elements and frequency of progress reports. c) RECIPIENT shall use ECOLOGY’s provided progress report format. d) Quarterly progress reports will cover the periods from January 1 through March 31, April 1 through June 30, July 1 through September 30, and October 1 through December 31. Reports shall be submitted within thirty (30) days after the end of the quarter being reported. e) RECIPIENT must submit within thirty (30) days of the expiration date of the project, unless an extension has been approved by ECOLOGY, all financial, performance, and other reports required by the Agreement and funding program guidelines. RECIPIENT shall use the ECOLOGY provided closeout report format.

  • Diversity Reporting Upon request, the Contractor will report to the Department its spend with business enterprises certified by the OSD. These reports must include the time period covered, the name and Federal Employer Identification Number of each business enterprise utilized during the period, commodities and contractual services provided by the business enterprise, and the amount paid to the business enterprise on behalf of each agency purchasing under the Contract.

  • Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.

  • Incident Reporting Transfer Agent will use commercially reasonable efforts to promptly furnish to Fund information that Transfer Agent has regarding the general circumstances and extent of such unauthorized access to the Fund Data.