Technical Resolution Guidance Chart Sample Clauses

Technical Resolution Guidance Chart. The technical resolution guidance chart below highlights the options provided within Contractor’s Software Support & Maintenance agreement and the Professional Services agreement. Description *
AutoNDA by SimpleDocs

Related to Technical Resolution Guidance Chart

  • Informal Resolution Outcomes a. When a complainant approaches an administrative officer and alleges harassment by another BCTF member, the following shall apply:

  • UDP DNS resolution RTT Refers to the RTT of the sequence of two packets, the UDP DNS query and the corresponding UDP DNS response. If the RTT is 5 times greater than the time specified in the relevant SLR, the RTT will be considered undefined.

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

  • Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.

  • TECHNICAL GUIDANCE LETTERS In the sole discretion of the System Agency, and in conformance with federal and state law, the System Agency may issue instructions, clarifications, or interpretations as may be required during work performance in the form of a Technical Guidance Letter (TGL). A TGL must be in writing, and may be delivered by regular mail, electronic mail, or facsimile transmission. Any TGL issued by the System Agency will be incorporated into the Contract by reference for all purposes when it is issued.

  • Informal Resolution Process It is the declared objective of the University and the Union to encourage the prompt resolution of potential causes for dismissal in the interest of maintaining harmony within the campus environment. Whenever practicable, before a formal recommendation for dismissal is initiated, every effort should be made to resolve or remediate the problem. Unless the individual concerned requests otherwise, the following efforts to resolve the problem will be undertaken in all cases where the issue is the individual’s performance and may be undertaken at the University’s discretion in other instances. The Department Personnel Committee, the Department Chair or Head, the individual concerned, and his or her union representatives may review the matter and explore a mutually acceptable resolution of the matter. The Xxxxxxx and/or appropriate Xxxx may, upon request of the Department Personnel Committee, the Department Chair or Head, the individual concerned, or the union representatives, join in the discussions about resolving the matter. Informal attempts at resolution shall not extend beyond thirty days without the written agreement of the individual concerned and the Xxxxxxx.

  • Problem Resolution The parties will endeavour to resolve any problems identified with the operation of this Agreement as they arise.

  • Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.

  • Issue Resolution Procedures As soon as possible after any occupational health and safety issue has been reported, the company’s or management representative and elected safety representative must meet to try to resolve the issue. The resolution of the issue must take into account those of the following factors that are relevant: o Whether the hazard or risk can be isolated o The number and location of employees affected o Whether appropriate temporary measures are possible or desirable o Whether environmental monitoring is desirable o The time that may elapse before the hazard or risk is permanently corrected o Who is responsible for performing work and overseeing the removal of the hazard or risk. As soon as possible after the resolution of an issue, details of the agreement must be brought to the attention of affected employees in an appropriate manner. Should the matter not be resolved, the issue shall be dealt with in line with Clause 20 of the VBIA “Safety Disputes Resolution Procedure”.

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

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