Incident Category and Priority Response and Resolution Targets Sample Clauses

Incident Category and Priority Response and Resolution Targets. A. Company shall comply with the priority levels provided below when Incidents are reported by Authority. These levels, as determined by Authority, are measured according to the business impacts of each problem. Software Support activity prioritization, response and resolution expectations are based on impact and urgency. Company must provide Authority with a single point of contact for the Company Service Desk, as well as an updated escalation matrix which details contact information. The escalation must be maintained, and changes sent to the Authority Vice President of Information Technology Services. This information should include physical address, phone, email, any other available means of contact type. Category Description High The damage caused by the Incident increases rapidly. Work that cannot be completed by staff is highly time sensitive. A minor Incident can be prevented from becoming a Major Incident by acting immediately. Customers are not able to be processed. A large number of customers are affected and/or acutely disadvantaged in some way. The financial impact of the Incident is likely to exceed $10,000. The damage to the reputation of the Airport is likely to be high. Medium The damage caused by the incident increases considerably over time. A moderate number of staff are affected and/or not able to do their job properly. A moderate number of customers are affected and/or inconvenienced in some way. The financial impact of the Incident is likely to exceed $1,000 but will not be more than $10,000. The damage to the reputation of the Airport is likely to be moderate. Low A minimal number of staff are affected and/or able to deliver an acceptable service but this requires extra effort. A minimal number of customers are affected and/or inconvenienced but not in a significant way. The financial impact of the Incident is likely to be less than $1,000. The damage to the reputation of the Airport is likely to be minimal.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Incident Category and Priority Response and Resolution Targets

  • Patent Filing Responsibilities and Costs 1. The invention and patent rights herein apply to any patent application or patents covering an invention made under this Agreement. Each Party is responsible for its own costs of obtaining and maintaining patents covering sole inventions of its employees. The Parties may agree otherwise, upon the reporting of any invention (sole or joint) or in any license granted.

  • Collocation Transfer of Responsibility Without Working Circuits The Collocation is not serving any End User Customers and does not have active service terminations (e.g., Interconnection trunks or UNE Loops) or 2) Collocation Transfer of Responsibility With Working Circuits – The Collocation has active service terminations, such as Interconnection trunks or is serving End User Customers.

  • FACILITY RESPONSIBILITIES (1) The Facility will retain responsibility for the care of its clients and will maintain administrative and professional supervision of students insofar as their presence and program assignments affect the operation of the Facility and its care, direct and indirect, of its clients. No provision of this MOU shall prevent any Facility client from requesting not to be a teaching client or prevent any member of the Facility’s staff from designating any client as a non-teaching client.

  • Customer Responsibilities Customer shall:

  • Requester and Approved User Responsibilities The Requester agrees through the submission of the DAR that the PI named has reviewed and understands the principles for responsible research use and data management of the genomic datasets as defined in the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. The Requester and Approved Users further acknowledge that they are responsible for ensuring that all uses of the data are consistent with national, tribal, and state laws and regulations, as appropriate, as well as relevant institutional policies and procedures for managing sensitive genomic and phenotypic data. The Requester certifies that the PI is in good standing (i.e., no known sanctions) with the institution, relevant funding agencies, and regulatory agencies and is eligible to conduct independent research (i.e., is not a postdoctoral fellow, student, or trainee). The Requester and any Approved Users may use the dataset(s) only in accordance with the parameters described on the study page and in the 1 If contractor services are to be utilized, PI requesting the data must provide a brief description of the services that the contractor will perform for the PI (e.g., data cleaning services) in the research use statement of the DAR. Additionally, the Key Personnel section of the DAR must include the name of the contractor’s employee(s) who will conduct the work. These requirements apply whether the contractor carries out the work at the PI’s facility or at the contractor’s facility. In addition, the PI is expected to include in any contract agreement requirements to ensure that any of the contractor’s employees who have access to the data adhere to the NIH GDS Policy, this Data Use Certification Agreement, and the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. Note that any scientific collaborators, including contractors, who are not at the Requester must submit their own DAR. Addendum to this Agreement for the appropriate research use, as well as any limitations on such use, of the dataset(s), as described in the DAR, and as required by law. Through the submission of this DAR, the Requester and Approved Users acknowledge receiving and reviewing a copy of the Addendum which includes Data Use Limitation(s) for each dataset requested. The Requester and Approved Users agree to comply with the terms listed in the Addendum. Through submission of the DAR, the PI and Requester agree to submit a Project Renewal or Project Close-out prior to the expiration date of the one (1) year data access period. The PI also agrees to submit an annual Progress Update prior to the one (1) year anniversary2 of the project, as described under Research Use Reporting (Term 10) below. By approving and submitting the attached DAR, the Institutional Signing Official provides assurance that relevant institutional policies and applicable local, state, tribal, and federal laws and regulations, as applicable, have been followed, including IRB approval, if required. Approved Users may be required to have IRB approval if they have access to personal identifying information for research participants in the original study at their institution, or through their collaborators. The Institutional Signing Official also assures, through the approval of the DAR, that other institutional departments with relevant authorities (e.g., those overseeing human subjects research, information technology, technology transfer) have reviewed the relevant sections of the NIH GDS Policy and the associated procedures and are in agreement with the principles defined. The Requester acknowledges that controlled-access datasets subject to the NIH GDS Policy may be updated to exclude or include additional information. Unless otherwise indicated, all statements herein are presumed to be true and applicable to the access and use of all versions of these datasets.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Specific Responsibilities In addition to its overall responsibility for monitoring and providing a forum to discuss and coordinate the Parties’ activities under this Agreement, the JSC shall in particular:

  • Connecting Transmission Owner’s Scope of Work and Responsibilities The Connecting Transmission Owner will design, construct, own, operate and maintain all Connecting Transmission Owner’s Interconnection Facilities, except as otherwise stated above and in the Project Specific Specifications. The Connecting Transmission Owner will complete all engineering reviews, field verifications and witness testing, etc. in accordance with the ESBs and the Project Specific Specifications. Connecting Transmission Owner shall provide the revenue metering CT/PT units and meter socket enclosure. The Connecting Transmission Owner shall:  provide, run, and wire both ends of the color-coded cable for the revenue metering instrument transformer secondary wiring;  perform all terminations; and  supply and install the meter. The revenue meter may require a communications link to the RTU. The Connecting Transmission Owner will specify and run those communications cables. The Connecting Transmission Owner shall complete all wiring, testing and commissioning of the RTU.

  • User Responsibilities i. Users are required to follow good security practices in the selection and use of passwords;

  • Reactive Power and Primary Frequency Response 9.6.1 Power Factor Design Criteria

Time is Money Join Law Insider Premium to draft better contracts faster.