IMAC Sample Clauses

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 xxxxxxxxxx xxxx (xx xxxxx xxxxxxx xxxx) as defined by the United Stated Federal Communications Commission (FCC).
Sample 1Sample 2
AutoNDA by SimpleDocs
IMAC. 15.1 The Immunisation Advisory Centre (IMAC) was established in 1997 as part of the University of Auckland.
Sample 1
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 xxxxxxxxxx xxxx (xx xxxxx xxxxxxx xxxx) 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. Proactive Problem Management analyses Incident Records, and uses data collected by other IT Service Management processes to identify trends or significant Problems. 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 Requireme...
Sample 1
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...
Sample 1
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 ...
Sample 1

Related to IMAC

  • Data Integrity Contractor shall implement policies and procedures reasonably intended to ensure that Protected Health Information and Personally Identifiable Information in its possession is complete, accurate, and current, to the extent necessary for the Contractor’s intended purposes, and has not been altered or destroyed in an unauthorized manner.

  • Verizon OSS Services Access to Verizon Operations Support Systems functions. The term “Verizon OSS Services” includes, but is not limited to: (a) Verizon’s provision of Z-Tel Usage Information to Z-Tel pursuant to Section 8.1.3 below; and, (b) “Verizon OSS Information”, as defined in Section 8.1.4 below.

  • Out-of-Network Services We Cover the services of Non-Participating Providers. See the Schedule of Benefits section of this Contract for the Non-Participating Provider services that are Covered. In any case where benefits are limited to a certain number of days or visits, such limits apply in the aggregate to in-network and out-of-network services.

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

  • Network Etiquette You are expected to abide by the generally accepted rules of network etiquette. These include but are not limited to the following:

  • Systems Review The Construction Administrator will conduct reviews of proposed roof, structural, mechanical, electrical, plumbing, conveyance, sprinkler, telecommunications, and life safety systems, and will consider initial cost, availability, impact on the overall program, comfort and convenience, long-term maintenance and operating costs, and impacts on schedule.

  • Data Input Control It will be possible to retrospectively examine and establish whether and by whom Personal Data have been entered, modified or removed from SAP data processing systems. Measures: • SAP only allows authorized personnel to access Personal Data as required in the course of their duty. • SAP has implemented a logging system for input, modification and deletion, or blocking of Personal Data by SAP or its subprocessors within the Cloud Service to the extent technically possible.

  • Supplier Staff The Supplier Staff shall at all times during the Contract Period; obey all lawful instructions and reasonable directions of the Customer; apply all due skill, care, diligence and shall be appropriately experienced, qualified and trained to supply the Services in accordance with this Contract; and shall respond to any enquiries from the Product Owner relating to the Services within the timescales agreed by the Parties (where applicable) and in any event as soon as is reasonably practicable. The Supplier acknowledges and agrees that the continuity of the Key Personnel is paramount to the success of the Project and shall ensure that Key Personnel are assigned to the Project on a full-time basis and are not removed from the Services or assigned to any other Supplier or third party projects during the Contract Period (unless otherwise Approved by the Customer). The Customer may also require the Supplier to remove and/or replace any Key Personnel that the Customer acting reasonably considers in any respect unsatisfactory. The Customer shall not be liable for the cost of removing or replacing any Key Personnel. The Customer may, by written notice to the Supplier, refuse to admit onto, or withdraw permission to remain on, the Customer’s Premises any member of the Supplier Staff or any person employed or engaged by any member of the Supplier Staff whom the Customer believes represents a security risk or does not have the required levels of training and expertise or whose admission or continued presence would, in the reasonable opinion of the Customer, be undesirable. Supplier Staff engaged within the boundaries of the Customer’s Premises shall comply with such rules, regulations and requirements as may be in force from time to time for the conduct of personnel when at or within the boundaries of those Customer’s Premises.

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

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