IMAC Clause Samples

IMAC. Install, Move, Add, and Change – A modification of service, tracked through the Service Request Process. Incident - An unplanned interruption to an IT service or reduction in the quality of an IT service. Failure of an IT Service that has not yet impacted service is also an Incident, for example failure of one disk from a mirror set. Incident Management - the process for dealing with all Incidents; this can include failures, questions or queries reported by the users (usually via a telephone call to the Service Desk), by technical staff, or automatically detected and reported by Event monitoring tools. interLATA – A call between two different LATAs. This is a call outside your local calling area and constitutes this call to be defined as Long Distance (LD). interstate – A call between two different states. The majority of time, this is an interLATA call. intraLATA – A call within the same LATA. This is a call within your local calling area. intrastate – A call within the same state. This can be an intraLATA or an interLATA call based on FCC defined LATAs within the state. IT Service - A Service provided to one or more Customers, by an IT Service Provider. An IT Service is based on the use of Information Technology and supports the Customer's Business Process. An IT Service is made up from a combination of people, and technology and should be defined in a Service Level Agreement. LATA - Local Transport and Access Area which is a contiguous ▇▇▇▇▇▇▇▇▇▇ ▇▇▇▇ (▇▇ ▇▇▇▇▇ ▇▇▇▇▇▇▇ ▇▇▇▇) as defined by the United Stated Federal Communications Commission (FCC).
View SourceView Similar (2)
IMAC. Install, Move, Add, and Change – A modification of service, tracked through the Service Request Process. Incident - An unplanned interruption to an IT service or reduction in the quality of an IT service. Failure of an IT Service that has not yet impacted service is also an Incident, for example failure of one disk from a mirror set. Incident Management - the process for dealing with all Incidents; this can include failures, questions or queries reported by the users (usually via a telephone call to the Service Desk), by technical staff, or automatically detected and reported by Event monitoring tools. interLATA – A call between two different LATAs. This is a call outside your local calling area and constitutes this call to be defined as Long Distance (LD). interstate – A call between two different states. The majority of time, this is an interLATA call. intraLATA – A call within the same LATA. This is a call within your local calling area. intrastate – A call within the same state. This can be an intraLATA or an interLATA call based on FCC defined LATAs within the state. IT Service - A Service provided to one or more Customers, by an IT Service Provider. An IT Service is based on the use of Information Technology and supports the Customer's Business Process. An IT Service is made up from a combination of people, and technology and should be defined in a Service Level Agreement. LATA - Local Transport and Access Area which is a contiguous ▇▇▇▇▇▇▇▇▇▇ ▇▇▇▇ (▇▇ ▇▇▇▇▇ ▇▇▇▇▇▇▇ ▇▇▇▇) as defined by the United Stated Federal Communications Commission (FCC). Local call – An outbound intraLATA call. Long Distance (LD) call – An outbound interLATA calls. Priority Code - A simple code assigned to Incidents, Problems and Known Errors, indicating the seriousness of their effect on the quality of IT service. Problem - A cause of one or more Incidents. The cause is not usually known at the time a Problem Record is created. Problem Management - To manage the lifecycle of all Problems. The primary objectives of Problem Management are to prevent Incidents from happening, and to minimize the impact of Incidents that cannot be prevented. Repair Time - Repair Time is a measurement of the amount of time it takes to restore Service for a given Incident. Service Design - An activity or process that identifies Requirements and then defines a solution that is able to meet these Requirements. Service Request - A Customer request to move, add, or change a supported Configuration Item ...
View Source
IMAC. (1‐5 devices per request) This SLR applies to all County Locations Elapsed time Less than or equal to two (2) Business Days of request or per mutually agreed‐upon schedule 98% Transaction Range Amount of Failures that Cause SLR Miss 0‐20 >1 = 2 Failures cause a miss 21‐50 >2 = 3 Failures cause a miss Monthly measurement with fifty‐one (51) or more Transactions will follow the normal percentage calculation. Monthly Monthly 100 x ((TE ‐ FE)/TE) Where: TE = Total number of IMACs FE = Total number of IMACs that the Supplier failed to successfully complete within the Performance Target County‐provided Service Management System (currently Ramp‐Up Period ends as of the earlier of (1) County’s Approval of Written Acknowledgement of Converged Network Services Readiness2, or (2) March 17, 2019.* * As to Voice Communications Services, the Ramp‐Up Period ends as of the earlier of (1) County’s Approval of Written Acknowledgement of Voice Communication Services Readiness, or (2) September 1, 2019. 3% 3% 3% SLR 27 IMAC (6‐10 devices per request) This SLR applies to all County Locations Elapsed time Less than or equal to three (3) Business Days of request or per mutually agreed‐upon schedule 99% Transaction Range Amount of Failures that Cause SLR Miss 0‐25 >1 = 2 Failures cause a miss 26‐50 >2 = 3 Failures cause a miss 51‐75 >3 = 4 Failures cause a miss 76‐100 >4 = 5 Failures cause a miss Monthly measurement with one hundred one (101) or more Transactions will follow the normal percentage calculation. Monthly Monthly 100 x ((TE ‐ FE)/TE) Where: TE = Total number of IMACs FE = Total number of IMACs that the Supplier failed to successfully complete within the Performance Target County‐provided Service Management System (currently Ramp‐Up Period ends as of the earlier of (1) County’s Approval of Written Acknowledgement of Converged Network Services Readiness2, or (2) March 17, 2019.* * As to Voice Communications Services, the Ramp‐Up Period ends as of the earlier of (1) County’s Approval of Written Acknowledgement of Voice Communication Services Readiness, or (2) September 1, 2019. 2% 2% 2% SLR 28 IMAC (11‐20 devices per request) This SLR applies to all County Locations Elapsed time Less than or equal to five (5) Business Days of request or per mutually agreed‐upon schedule 99% Transaction Range Amount of Failures that Cause SLR Miss 0‐25 >1 = 2 Failures cause a miss Monthly Monthly 100 x ((TE ‐ FE)/TE) Where: TE = Total number of IMACs FE = Total number of IMACs that County...
View Source
IMAC. Figure 5 A reordering Network Assume that the edge router remarks some packets within a certain flow (the numbers in the figure represents packets’ relative positioning to previously forwarded packets that do not intervene in the presentation of this example), in this case packets 2 and 3 are upgraded (shown in a bold and underlined font after being upgraded in the figure). Depending on the scheduling scheme and the state of the various service queues in downstream nodes, packets 2 and 3 (since they are upgraded to a better service class) can arrive at the destination before packets 0 and 1. For example, one scenario is that the first downstream node could schedule packets 2 and 3 before packet 1 since they are of higher service class, and the next downstream node could schedule packets 2 and 3 before packet 0. In order to maintain the ordering criteria within a flow, nodes could decide to maintain a per-flow state that keeps track of packet sequence numbers and queue out of order packets until they are back in order. This solution is not desirable, since it would not scale when the number of flows becomes large; it would require keeping state information for every flow [71,72]. iMac iMac Figure 6 A non-reordering Network The proposed solution is to force each node to maintain packet ordering as follows. Use a special indicator in each packets’ header (e.g. one of the DSCP bits) to tell a downstream node that a packet has been upgraded to a higher class (from CLASS-2 to CLASS-1 for example). Once the downstream node detects a packet with the special indicator set, it would queue the upgraded packet in its original class of service (CLASS-2), reset the special indicator, and add a token in the higher class (CLASS-1) to represent the upgraded packet. Once the scheduler decides that the token packet needs to be forwarded, it would forward instead the head-of-line packet from the lower class (CLASS-2) and set the special indicator in that packet. The idea is similar to the 400 meters relay, where each runner runs 100 meters and relays a baton to the next runner. Figure 6 depicts an example of the proposed solution which contrasts the previous example. As shown in the figure, when packets 2 and 3 (after being upgraded at the edge router) are received in the first downstream node, they are placed back in their original class of service queue, and tokens represent their arrivals as upgraded packets in the higher service class. If packet 0 was forwarded before it ...
View Source
IMAC. 15.1 The Immunisation Advisory Centre (IMAC) was established in 1997 as part of the University of Auckland. 15.2 IMAC leads and supports activities to provide: (a) independent, factual information based on international and New Zealand scientific research regarding vaccine-preventable diseases and the benefits and risks of immunisation (b) information and training for health professionals (c) national immunisation coordination (d) policy advice and research into many aspects of vaccines and vaccine-preventable diseases.
View Source
IMAC. (1-5 devices per request) This SLR applies to all County Locations Elapsed time Less than or equal to two (2) Business Days of request or per mutually agreed-upon schedule 98% Transaction Range Amount of Failures that Cause SLR Miss 0-20 >1 = 2 Failures cause a miss 21-50 >2 = 3 Failures cause a miss Monthly measurement with fifty-one (51) or more Transactions will follow the normal percentage calculation. Monthly Monthly 100 x ((TE - FE)/TE) Where: TE = Total number of IMACs FE = Total number of IMACs that the Supplier failed to successfully complete within the Performance Target County-provided Service Management System (currently Ramp-Up Period ends as of the earlier of (1) County’s Approval of Written Acknowledgement of Converged Network Services Readiness2, or (2) March 17, 2019.* * As to Voice Communications Services, the Ramp-Up Period ends as of the earlier of (1) County’s Approval of Written Acknowledgement of Voice Communication Services Readiness, or (2) September 1, 2019. 3% 3% 3%
View Source

Related to IMAC

  • Data Integrity Policies and procedures to ensure the confidentiality, integrity, and availability of Customer Data or Professional Services Data and protect it from disclosure, improper alteration, or destruction.

  • Verizon OSS Services 8.2.1 Upon request by PNG, Verizon shall provide to PNG Verizon OSS Services. Such Verizon OSS Services will be provided in accordance with, but only to the extent required by, Applicable Law. 8.2.2 Subject to the requirements of Applicable Law, Verizon Operations Support Systems, Verizon Operations Support Systems functions, Verizon OSS Facilities, Verizon OSS Information, and the Verizon OSS Services that will be offered by Verizon, shall be as determined by Verizon. Subject to the requirements of Applicable Law, Verizon shall have the right to change Verizon Operations Support Systems, Verizon Operations Support Systems functions, Verizon OSS Facilities, Verizon OSS Information, and the Verizon OSS Services, from time-to-time, without the consent of PNG. 8.2.3 To the extent required by Applicable Law, in providing Verizon OSS Services to PNG, Verizon will comply with Verizon’s applicable OSS Change Management Guidelines, as such Guidelines are modified from time-to-time, including, but not limited to, the provisions of the Guidelines related to furnishing notice of changes in Verizon OSS Services. Verizon’s OSS Change Management Guidelines will be set out on a Verizon website.

  • Telemedicine Services This plan covers clinically appropriate telemedicine services when the service is provided via remote access through an on-line service or other interactive audio and video telecommunications system in accordance with R.I. General Law § 27-81-1. Clinically appropriate telemedicine services may be obtained from a network provider, and from our designated telemedicine service provider. When you seek telemedicine services from our designated telemedicine service provider, the amount you pay is listed in the Summary of Medical Benefits. When you receive a covered healthcare service from a network provider via remote access, the amount you pay depends on the covered healthcare service you receive, as indicated in the Summary of Medical Benefits. For information about telemedicine services, our designated telemedicine service provider, and how to access telemedicine services, please visit our website or contact our Customer Service Department.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central ▇▇▇▇▇▇ Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Data Integrity Control Personal Data will remain intact, complete and current during processing activities.