Reporting Tools. OPAS Incident Management and Change Management, Atrium CMDB. Will be measured using an Incident RCA based measurement approach. Exceptions: - No single LAN availability device could cause an SLA miss, unless that single device is unavailable for more than 4 hours. Supplemental definition of terms: To determine the impact and duration to service availability, the following process is adhered. True impact and duration are determined by analyzing the MIM communications, AIR & RCA. With that extracted start & end times (Excluding any scheduled maintenance downtime) a CI unavailability record is created on the parent incident management record to reflect & report the service impact duration. Low Volume Eligible: No Threshold parameters: ***% of the time, ***% of Data Center LAN Systems will be available. SLA Metrics and parameters: (field names in OPAS) Supporting CompanyIncident Assigned Date/TimeIncident PriorityIncident IDIncident Resolved Date/TimeProduct Category Tier 1 Product Category Tier 2Product Category Tier 3CI Unavailability Scheduled Actual Start Date/TimeCI Unavailability Scheduled Actual End Date/TimeCI Unavailability Unscheduled Actual Start Date/TimeCI Unavailability Unscheduled Actual End Date/TimeRelated Change to Incident RecordExcluded from SLA Reporting
Reporting Tools. Fry to review additional Web [****] tools such as [****] for support on the Site. -------------------------------------------------------------------------------- 1-800-FLOWERS, Inc. Page 12 of 18 Confidential 536615.1-XXXXXX-6/17/99 12:35:15 PM **** Represents material which has been redacted and filed separately with the Commission pursuant to a request for confidential treatment under Rule 406 of the Securities Act of 1933, as amended.
Reporting Tools. 1. Vendor agrees to provide online electronic access to all purchasing data relating to the Products that are purchased by each MMCAP Participating Facility to the MMCAP Office and MMCAP Participating Facilities. Vendor will provide a system for reporting each individual MMCAP Participating Facility’s purchases, as well as be capable of running reports on select groups of facilities. Users must be able to manipulate the data to build reports based on each MMCAP Participating Facility’s individual needs/requirements directly through the system or through the ability to transfer data into spreadsheets in a Microsoft Office compatible format.
Reporting Tools. OPAS Incident Exceptions: This does not include any communication outside the Supplier Service Management process. Any Communication suspension as agreed by Dell and CoreLogic. Supplemental definition of terms: Measures the percentage of Critical Incidents where communication to established stakeholders is distributed within 5 minutes of the 30-minute target during the duration of the Critical Incident NOTE: Measurement of KM will be through an agreed-upon process and timestamp within the OPAS system or email transmission mechanism Low Volume Eligible: None Threshold parameters: ***% of all Critical Incident Communications sent no later than *** of the *** target. SLA Metrics and parameters: (field names in OPAS) Supporting CompanyIncident Assigned Date/TimeIncident PriorityIncident IDIncident Resolved Date/TimeProduct Category Tier 1 Product Category Tier 2CMDB Urgency CI Unavailability Scheduled Actual Start Date/TimeCI Unavailability Scheduled Actual End Date/TimeCI Unavailability Unscheduled Actual Start Date/TimeCI Unavailability Unscheduled Actual End Date/TimeRelated Change to Incident RecordExcluded from SLA Reporting
Reporting Tools. OPAS Exceptions: Any other purchase requests that are not RU based or through an approved project. Circuits are excluded, but circuit hardware is not.CoreLogic cancellations of a PO request. Supplemental definition of terms: For the RU based purchase requests, the request types include:Physical Server Install - (All Platform/Types)Server Storage RequestServer Request - Hosted For approved project based purchase requests, request types are irrelevant. Reference the methodology below. Low Volume Eligible: Yes, provided that if any single purchase request is not completed within ***, then this Low Volume exception shall not apply. Threshold parameters: ***% of purchase orders created in the target timeframe: *** (***) regardless of vendor or hardware type Note: *** = 1 business day SLA Metrics and parameters:(field names in OPAS) Supporting CompanyRequest Summary NameRequest Approval Date/TimeRequest Assigned Date/TimeRequest Completed Date/TimeExcluded in SLA Reporting CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.
Reporting Tools. OPAS Service Requests Exceptions: - Any hold in approval processes or change request initiated by CoreLogic- Supplier's failure to meet this Service Level in respect of any hardware-related Incidents shall be excused to the extent that such failure is caused by any Supplier third party provider's failure to perform, or delay in performing, any repair or replacement actions required to be performed by such third party provider in connection with the resolution of any such Incident; provided, that (i) Supplier uses commercially reasonable efforts to cause such third party providers to perform within the required time frame and (ii) to the extent documented in Supplier's Root Cause Analysis- Pending Time based on allowed Pending Event Supplemental definition of terms: Measures the time taken between processing of approved request(s) Low Volume Eligible: No Threshold parameters: ***% of requests completed within ***; ***% completed within *** SLA Metrics and parameters:(field names in OPAS) Supporting CompanyRequest Summary NameRequest Approval Date/TimeRequest Assigned Date/TimeRequest Completed Date/TimePending TimeExcluded in SLA Reporting Logical description of the SLA calculation: Report CriteriaSupporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”Request Summary Name = Firewall Request or IP Assignment Request Closed Date/Time is within the reporting periodExcluded in SLA Reporting <> Yes Calculations Request SLA = Request Completed Date/Time - Request Approval Date/Time- Total Pending Time ***% - Service Level Achievement (within ***)= (Number of successfully completed requests within ***/Total number of requests in the measurement period) * 100% ***% - Service Level Achievement (within ***)= (Number of successfully completed requests within ***/Total number of requests in the measurement period) * 100%
Reporting Tools a. Vendor must provide online electronic access to all MMCAP participating facilities. Upon request, Vendor will provide access to related Member to obtain purchasing data.
Reporting Tools. 1. Wholesaler agrees to provide online electronic access to all purchasing data relating to the Products that are purchased by each MMCAP Participating Facility to MMCAP and MMCAP Participating Facilities. Wholesaler will provide a system for reporting each individual MMCAP Participating Facility’s purchases, as well as be capable of running reports on select groups of facilities. Users must be able to manipulate the data to build reports based on each MMCAP Participating Facility’s individual needs/requirements directly through the system or through the ability to transfer data into spreadsheets in a Microsoft Office compatible format.
Reporting Tools. 6.6.5.1 The solution must have the ability to perform a full analysis of the relationships between the DARD field boundary and ineligible area polygons with the OSNI® large scale vector mapping and provide an audit trail for future reference.
Reporting Tools. 1. Wholesaler agrees to provide online electronic access to all purchasing data relating to the Products that are purchased by each MMCAP Infuse Participating Facility to MMCAP Infuse and MMCAP Infuse Participating Facilities. Wholesaler will provide a system for reporting each individual MMCAP Infuse Participating Facility’s purchases, as well as be capable of running reports on select groups of facilities. Users must be able to manipulate the data to build reports based on each MMCAP Infuse Participating Facility’s individual needs/requirements directly through the system or through the ability to transfer data into spreadsheets in a Microsoft Office compatible format.
