System Unavailability definition

System Unavailability. As measured within the Managed Care Plan’s information systemsspan of control, when a system user does not get the complete, correct full-screen response to an input command within three (3) minutes after depressing the “enter” or other function key.
System Unavailability. As measured within the Contractor’s information systems Span of Control, when a system user does not get the complete, correct full-screen response to an input command within three (3) minutes after depressing the “Enter” or other function key.
System Unavailability. As measured within the CONTRACTOR’s information systems span of control, when a system user does not get the complete, correct full-screen response to an input command within three (3) minutes after depressing the “Enter” or other function key. TCA – Tennessee Code Annotated. TENNCARE – TENNCARE shall have the same meaning as “State.” TennCare CHOICES in Long-Term Care (CHOICES) – A program in which long-term care services for elders and/or persons with physical disabilities are integrated into TennCare’s managed care delivery system.

Examples of System Unavailability in a sentence

  • System Unavailability — As measured within the Health Plan’s information systems Span of Control, when a system user does not get the complete, correct full-screen response to an input command within three (3) minutes after depressing the “Enter” or other function key.

  • System Unavailability – As measured within the CONTRACTOR’s information systems span of control, when a system user does not get the complete, correct full-screen response to an input command within three (3) minutes after depressing the “Enter” or other function key.

  • Unscheduled System Unavailability to all other Contractor System functions caused by systems and telecommunications technologies within the Contractor’s Span of Control shall be resolved, and the restoration of services implemented, within four (4) hours of the official declaration of System Unavailability.

  • Unscheduled System unavailability caused by the failure of systems and telecommunications technologies within the Health Plan’s Span of Control will be resolved, and the restoration of services implemented, within forty-eight (48) hours of the official declaration of System Unavailability.

  • The Health Plan shall ensure that critical systems functions available to Enrollees and providers, functions that if unavailable would have an immediate detrimental impact on Enrollees and providers, are available twenty-four (24) hours a day, seven (7) days a week, except during periods of scheduled System Unavailability agreed upon by the Agency and the Health Plan.

  • Unscheduled System Unavailability of ECM functions caused by the failure of systems and technologies within the Contractor’s Span of Control will be resolved, and the restoration of services implemented, within sixty (60) minutes of the official declaration of System Unavailability, if unavailability occurs during normal business hours; or within sixty (60) minutes of the start of the next Business Day, if unavailability occurs outside business hours.

  • System Unavailability Notification within two (2) hours Notification to SLP, of any non-scheduled system unavailability within two (2) hours of incident occurrence.

  • The Health Plan shall provide to appropriate Agency staff information on System Unavailability events, as well as status updates on problem resolution.

  • Unless otherwise agreed to in advance by the Agency as part of the activities described in this Section, scheduled System Unavailability to perform System maintenance, repair and/or upgrade activities shall not take place during hours that could compromise or prevent critical business operations.

  • Unavailability of Dedicated Equipment due to Customer's information content or application programming, acts of Customer or its agents, or events of Force Majeure shall not be deemed System Unavailability for the purpose of this Commitment.


More Definitions of System Unavailability

System Unavailability has the meaning specified in Paragraph 7.2 (Service Credits) of this SLA.
System Unavailability. Failure of the system to provide a designated user access based on service level agreements or software/hardware problems within the contractors span of control.
System Unavailability. As measured within the Contractor’s Information SystemsSpan of Control, when a system user does not get the complete, correct full-screen response to an input command within three (3) minutes after depressing the “Enter” or any other function key. Term or Contract Term: The duration of time that this Contract is in effect. Termination Date of the Contract: The dated designated by ASES as the date that Contracted Services shall end. Third Party: Any person, institution, corporation, insurance company, public, private, or governmental entity who is or may be liable in contract, tort, or otherwise by law or equity to pay all or part of the medical cost of injury, disease, or disability of an Enrollee. Third Party Liability (“TPL”): Legal responsibility of any Third Party to pay for health care services. Time and Distance Standards: A standardized measure of mileage and travel time for Enrollees in Urban and non-Urban Areas to access Network Pharmacies as specified in Section 7.2.1.

Related to System Unavailability

  • Unavailability (or “Unavailable”) the Flexibility Services, in accordance with the Service Requirements, are not Available to be delivered to the Company; “Utilisation Instruction” an instruction by the Company to the Provider to deliver Flexibility Services;

  • System Availability means, with respect to any particular calendar month, the ratio obtained by subtracting Unscheduled Downtime during such month from the Total Monthly Time, and thereafter dividing the difference so obtained by the Total Monthly Time. Represented algebraically, System Availability for any particular calendar month is determined as follows:

  • Service Availability The total number of minutes in a calendar quarter that the Tyler Software is capable of receiving, processing, and responding to requests, excluding maintenance windows, Client Error Incidents and Force Majeure.