Prioritization. All reported incidents receive a priority number based on the impact and urgency of the service interruption. Impact is determined based on the number of people/departments/buildings that are affected by the interruption or outage. Life-Safety issues are taken into consideration for assessing and assigning priorities. Urgency is based on the acceptable delay to restore the service. Urgency can be critical or high and is determined based on the nature of the service outage. UNM IT may prioritize incoming incident requests as P1 or P2 priority if it meets one or more of the following criteria: Significant number of people affected; The level to which work is impaired for individuals; Academic and Administrative Calendar deadlines; Significant impact on the delivery of instruction; Significant risk to safety, law, rule, or policy compliance.
Prioritization. All Services will be implemented and/or facilitated (as applicable) on a schedule, and in a prioritized manner, as we determine reasonable and necessary. Exact commencement / start dates may vary or deviate from the dates we state to you depending on the Services being provided and the extent to which prerequisites (if any), such as transition or onboarding activities, must be completed.
Prioritization. The HB shall prioritize households in Housing Need in the following order:
Prioritization. Unless otherwise stated in a SOW, all Services will be performed on a schedule, and in a prioritized manner, as determined by XXXX.
Prioritization. Prioritization of delivered constructs for transformation, prioritization of existing events for genetic crossing, and prioritization of existing events for plant assay.
Prioritization. All Services will be performed on a schedule, and in a prioritized manner, as we determine reasonable and necessary.
Prioritization. The Database Services group will prioritize incoming incident requests as “urgent” priority if it meets any one of the following criteria: • Number of departments or people affected. • Academic and Administrative Calendar deadlines. • Impact on the delivery of instruction. • Risk to safety, law, rule, or policy compliance.
Prioritization. ICE retains sole discretion in determining how it will manage its limited resources and meet its mission requirements. To ensure resources are managed effectively, ICE requires the AGENCY to also manage its resources dedicated to 287(g) authority under the MOA. To that end, the following list reflects the categories of aliens that are a priority for arrest and detention with the highest priority being Level 1 criminal aliens. Resources should be prioritized to the following levels: Level 1 – Aliens who have been convicted of or arrested for major drug offenses and/or violent offenses such as murder, manslaughter, rape, robbery, and kidnapping; Level 2 – Aliens who have been convicted of or arrested for minor drug offenses and/or mainly property offenses such as burglary, larceny, fraud, and money laundering; and Level 3 – Aliens who have been convicted of or arrested for other offenses. Training: The 287(g) training program, the Immigration Authority Delegation Program (IADP), will be taught by ICE instructors and tailored to the immigration functions to be performed. ICE Office of Training and Development xxxx xxxxxxx examinations during the IADP. The AGENCY nominee must pass each examination with a minimum score of 70 percent to receive certification. If the AGENCY nominee fails to attain a 70 percent rating on an examination, the AGENCY nominee will have one opportunity to remediate the testing material and re-take a similar examination. During the entire duration of the IADP, the AGENCY nominee will be offered a maximum of one remediation examination. Failure to achieve a 70 percent on any two examinations(inclusive of any remediation examination), will result in the disqualification of the AGENCY nominee and their discharge from the IADP. Training will include, among other topics: (i) discussion of the terms and limitations of this MOA; (ii) the scope of immigration officer authority; (iii) relevant immigration law; (iv) the ICE Use of Force Policy; (v) civil rights laws; (vi) the U.S. Department of Justice “Guidance Regarding the Use Of Race By Federal Law Enforcement Agencies,” dated June 2003; (vii) public outreach and complaint procedures; (viii) liability issues; (ix) cross-cultural issues; and (x) the obligation under Federal law and the Vienna Convention on Consular Relations to make proper notification upon the arrest or detention of a foreign national. Approximately one year after the participating AGENCY personnel are trained and certified, ...
Prioritization. An Issue shall be categorized as "Severity 3" if the issue will result in the State limiting Entity and/or Supplier use of or access to components/features of the associated functionality. Typical characteristics of Severity 3 issues are situations that would have adverse effect on the rollout, adoption and training of the functionality. Examples include, but are not limited to: - Procurement transactions can be completed but access to the component/feature will cause transaction errors. - Processing transactions produces system on-screen messages that are inaccurate or are not understandable. - Workarounds are not available to permit use a specific component/feature of the functionality. - Workarounds are sufficiently complicated that functionality component/feature access has to be limited Entity procurement staff. - Supplier use will result in significant number of support calls. Measurement: Issue "Time to Repair" will be measured from the time the State reports the issue as Severity 3 to the point in time the Contractor provides either a resolution or workaround to the State for verification and acceptance. In the case where the resolution or workaround is determined by the State to be unacceptable the tracking of the "Time to Repair" will recommence at the time the State reports the unacceptability. In the case of a workaround, the State may accept the workaround as a short-term solution, allowing the functionality to move to Production, but still need the issue resolved at a lower Severity. In these circumstances, the State will consider the associated Severity 3 issue resolved and the Contractor will establish a new issue at the State determined Severity for management and tracking. The "Mean Time to Repair" for the reporting month will be measured by assessing the elapsed time in business days (expressed as a decimal number, to two positions after the decimal point, that reflects the hours and minutes) of all resolved Severity 3 UAT issues to determine the statistical mean. Measurement Period Data Source Collection Frequency SL Formula SL Measure GYR State Reporting Month Issue Management System Per Issue Mean Time to Repair (Severity 3 Issues) = (Total elapsed business days for all resolved Severity 3 Issues) divided by (Total number of all resolved Severity 3 Issues) <= 20 days > 20 days and <= 40 days > 40 days Project Implementation Service Level Agreement: UAT Environment Availability eProcurement Solution UAT Environment is available to Stat...
Prioritization. This section intentionally left blank. 7 Maintenance and Service Changes This section intentionally left blank.
