Priority 2 definition

Priority 2. Individuals who are: Age 60 and over in need of the following medically related trips: • Need for life sustaining medical care such as dialysis, chemotherapy, radiation treatment • Multi-system failure or conditions requiring immediate medical supervision/care, e.g. diabetes, heart disease, Chronic Obstructive Pulmonary Disease (COPD) • Surgery or non-elective (immediate need) procedure
Priority 2 means streets that are designated as collectors and bus routes within the City’s street system which carry most of the inter-arterial vehicular and bus traffic. These streets are typically 10 metres in width;
Priority 2 is defined in Appendix A, Section 3.4.

Examples of Priority 2 in a sentence

  • Note: For Priority 1 and Priority 2 level Incidents, Clients must call into HSP Support line using one of the numbers listed on our Support Portal to speak directly with an Engineer.

  • The content of the customer’s APPP / website will be created in HTML format and will conform to the World Wide web Consortium XHTML 1.0 Transitional (W3C) and are WCAG Priority 2 AA compliant.

  • A Priority 1 call is deemed by our support staff to be an Urgent or High Priority call, Priority 2 is classified as a Medium Priority and Priority 3 is deemed to be a Low Priority.

  • A Cribl LogStream Enterprise license comprises the following features: Support and Maintenance Support and maintenance is supplied by Confluent on the following terms: Availability: 24 x 7 Initial Response Time: Priority 1: within 1 hour, Priority 2: within 4 hours, Priority 3: within 1 business day, Priority 4: within 2 business days.

  • Our response time guidelines are as follows: Priority 1: 1 - 4 hours Priority 2: 1 - 8 hours Priority 3: 1 - 24 hours Call Priorities In an effort to assign our resources to incoming calls as effectively as possible, we have identified three types of call priorities, 1, 2 and 3.


More Definitions of Priority 2

Priority 2 or “P2”) means an Incident that results in a partial loss of Product functionality, operation or performance, such that use or processing can proceed in a restricted fashion but performance is significantly reduced and/or operation of the Product or any portion thereof is considered severely limited and no workaround to provide the affected functionality is possible or cannot be implemented in time to minimize the impact on Saint Luke’s and Facility business. P2 Incidents may include one or more of the following characteristics: (i) severely degraded performance, (ii) loss of Product base functionality to multiple rooms including loss of Integrations (ADT/locating/wireless), or (iii) some important functionality is unavailable, yet the Product continues to operate in a restricted fashion.
Priority 2 means an Error that affects performance of the Software and prohibits Licensee's use of the Software.
Priority 2 refers to a condition that is necessary to repair but is not yet critical. Such conditions require correction to preclude deterioration, potential loss of function or service, or associated damage or higher costs if further deferred. “Priority 3” refers to a condition that is recommended to repair. Such repairs will reduce long-term maintenance or repair costs, will improve the functions of a Facility, and will support improved court operations.
Priority 2. Fault shall mean any condition that materially impairs one or more functions that the Licensed Software is specified to perform, but that does not involve a Priority 1 condition. Nonexclusive examples include database information corruption for a small group of students, a single school, or incorrect writing of non-critical fields. Priority 2 conditions are less severe than Priority 1 conditions.
Priority 2 means that while the Software is Operational, (i) functional limitations or restrictions have materially impacted Licensee’s operations, (ii) non-essential functions were disabled in production, or (iii) essential non-production functions were disabled.
Priority 2. Means a severe outage rendering a server or a database malfunction resulting in the partial failure of the software and causing the Licensed Program to be partially inoperable, impacting a limited subset of users, endpoints or devices. In some cases, the users may have a Workaround by using the redundant configuration if implemented. Response Time is within (1) hour of opening ticket. Supplier Resolution Time is within Sixteen (16) hours of opening ticket.
Priority 2. The problem has high visibility and impacts on the way Customer does business. The service is disrupted but not halted. The system performance may be degraded and some functions may not operate correctly.