Exception Process Sample Clauses

Exception Process. A Participating Agency which does not fully meet the standards set forth in this Section XV may submit a proposed plan to share Data to the Data Governing Board during the process of coming into full compliance with the stated requirements.
AutoNDA by SimpleDocs
Exception Process. If a Prescription Drug, including contraceptives, is not on Our Formulary, You, Your designee or Your prescribing Health Care Professional may request a Formulary exception for a clinically- appropriate Prescription Drug in writing, electronically or telephonically. The request should include a statement from Your prescribing Health Care Professional that all Formulary drugs will be or have been ineffective, would not be as effective as the non-Formulary drug, or would have adverse effects. If coverage is approved, the costs will count toward the Out-of-Pocket Maximum. If coverage is denied under Our standard or expedited Formulary exception process, You are entitled to an external appeal as outlined in the Complaints, Appeals and External Review section of this Policy. Visit Our website at xxx.xxxxxxx.xxx or call 0-000-XXXXX-00 to find out more about this process. For contraceptives only, We will defer to Your Provider’s recommendation of Medical Necessity and will provide the contraceptive service or FDA approved item without cost sharing upon request. Coverage and benefits for Covered Prescription Drugs and Supplies and Covered OTC Drugs are subject to the following limitations in addition to all other provisions and exclusions in this Contract.
Exception Process. For any potential Tax Equity Investment presented by GEV IA under this Agreement that does not satisfy all of the Tax Equity Investment Requirements, GEV IA and Parent agree to discuss such potential investment in good faith and consider any exceptions that could be made by Parent on a case-by-case basis. Any exception to the Tax Equity Investment Requirements in respect of a Tax Equity Investment will require the written approval of Parent, in its sole discretion, prior to the Parent Investor entering into any Tax Equity Transaction Documents or the execution of any term sheet or the like in relation thereto. GEV IA will provide Parent with written notice, as promptly as reasonably practicable, and in no event less than fifteen (15) Business Days’ prior to the date that GEV IA requests that such term sheet be issued, or the Tax Equity Investment Transaction Documents in respect of such potential Tax Equity Investment be entered into (including all information and underwriting materials related to such proposed exception), for Parent to consider whether to grant any such exception in its sole discretion. If such an exception is granted by Parent for a Tax Equity Investment in accordance with this Section 3.03, such Tax Equity Investment will be deemed to comply with the Tax Equity Investment Requirements if the Tax Equity Investment satisfies all requirements and conditions to the granting of the exception.
Exception Process. If Franchisee proposes to purchase materials or supplies not theretofore approved by Pretzel Time as meeting its specifications, or from a supplier or distributor not previously approved by Pretzel Time, Franchisee shall first notify Pretzel Time and request Pretzel Time's approval using the special exception form provided to Franchisee in its Operations Manual, and pay any reasonable fees that Pretzel Time designates therefor. Further, Franchisee agrees to use all forms specified and developed by Pretzel Time for requesting any exceptions in products or suppliers. Pretzel Time may require submission of sufficient information and samples to determine whether such materials, supplies or suppliers meet its specifications as well as financial information regarding the supplier. Pretzel Time will advise Franchisee within a reasonable time whether such materials or supplies meet its specifications. Pretzel Time does not maintain a formal criteria for approving materials, supplies or suppliers. All approvals, disapprovals and revocations of approval of suppliers will be communicated to Franchisee, in writing, and shall be in the sole discretion of Pretzel Time. Franchisee must comply with the following conditions in order to seek a substitution for a Pretzel Time approved Product: (1) Franchisee shall submit a written request to Pretzel Time for approval of a non-approved supplier or product; (2) Franchisee and supplier shall demonstrate to Pretzel Time's reasonable satisfaction that it is able to supply the commodity which meets Pretzel Time's specifications to Franchisee; and (3) The supplier shall demonstrate to Pretzel Time's reasonable satisfaction that the supplier is of good standing in the business community with respect to its financial soundness and the reliability of its product and service and shall request in writing to Pretzel Time to be named an approved supplier.
Exception Process. In rare circumstances, exceptions to this policy are permitted if the DTI Chief Security Officer (CSO) has signed off in writing. Related ISO 27002:2013 clause(s): 7.2.3, 7.3.1 Failure to comply with the policy is a serious matter, whether through intentional act or negligence, and is grounds for discipline up to and including dismissal based on the just cause standard set forth by Merit Rules, or collective bargaining agreement, whichever is applicable to the subject employee. Exempt employees are subject to appropriate discipline without recourse, except as provided by law. While DTI has no authority to discipline employees or other parties of other State Organizations in the Legislative or Judicial branches of government, it shall take the appropriate steps to ensure any misconduct is appropriately addressed.
Exception Process. In the case of patients who need a drug that does not appear in the PDL or in the FMU, the insurance companies, mental health organizations and health service providers must utilize the process described herein for the approval of the drugs. This procedure shall consider the particular merits of each case, which may include: 1. Contraindication to the drug(s) that appear in the PDL. 2. History record of adverse reaction to the drug(s) that appear in the PDL. 3. Therapeutical failure with regard to all the alternatives available in the PDL. 4. Non-existence of a therapeutical alternative in the PDL.
Exception Process. In the case of patients who need a drug that is not included in the FDC, healthcare service providers and, as applicable, insurance companies must use the process described below to obtain approval of the drug by exception. This procedure will consider the particular merits of each case, which may include: a. Contraindication to the drug(s) included in the FDC; b. History of a clinically significant adverse reaction to the drug(s) included in the FDC; c. Evidence of therapeutic failure of all alternatives available in the FDC; and/or d. Lack of a therapeutic alternative in the FDC. This exception process requires a clinical justification that is duly documented by the service provider with the clinical reasons justifying the use of a non-formulary drug, which will be evaluated on a case-by-case basis by a clinical team at the insurance company(ies) contracted by ASES.
AutoNDA by SimpleDocs

Related to Exception Process

  • Selection Process The Mortgage Loans were selected from among the outstanding one- to four-family mortgage loans in the Seller's portfolio at the related Closing Date as to which the representations and warranties set forth in Subsection 9.02 could be made and such selection was not made in a manner so as to affect adversely the interests of the Purchaser;

  • Escalation Process If Customer believes in good faith that Customer has not received quality or timely assistance in response to a support request or that Customer urgently need to communicate important support related business issues to Service Provider’s management, Customer may escalate the support request by contacting Service Provider and requesting that the support request be escalated to work with Customer to develop an action plan.

  • Application Process The employees wishing to enter into a job share arrangement will apply in writing to the Employer and forward a copy to the Union outlining the proposed commencement date of the job share, how the hours and days of work will be shared and how communication and continuity of work will be maintained. The Employer shall communicate a decision on a job share request in writing to the applicants. Applications to Job Sharing shall not be unreasonably denied.

  • Evaluation Process ‌ A. The immediate supervisor will meet with an employee at the start of their review period to discuss performance expectations. The employee will receive copies of their performance expectations as well as notification of any modifications made during the review period. Employee work performance will be evaluated during probationary, trial service and transition review periods and at least annually thereafter. Notification will be given to a probationary or trial service employee whose work performance is determined to be unsatisfactory. B. The supervisor will discuss the evaluation with the employee. The employee will have the opportunity to provide feedback on the evaluation. The discussion may include such topics as: 1. Reviewing the employee’s performance; 2. Identifying ways the employee may improve their performance; 3. Updating the employee’s position description, if necessary; 4. Identifying performance goals and expectations for the next appraisal period; and 5. Identifying employee training and development needs. C. The performance evaluation process will include, but not be limited to, a written performance evaluation on forms used by the Employer, the employee’s signature acknowledging receipt of the forms, and any comments by the employee. A copy of the performance evaluation will be provided to the employee at the time of the review. A copy of the final performance evaluation, including any employee or reviewer comments, will be provided to the employee. The original performance evaluation forms, including the employee’s comments, will be maintained in the employee’s personnel file. D. If an employee disagrees with their performance evaluation, the employee has the right to attach a rebuttal. E. The performance evaluation process is subject to the grievance procedure in Article 30. The specific content of a performance evaluation is not subject to the grievance procedure. F. Performance evaluations will not be used to initiate personnel actions such as transfer, promotion, or discipline.

  • Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-­‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-­‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

  • Consultation Process (a) Unless the expedited process in clause 3.4 applies, the Operator must follow the process set out below for consulting on a proposal to amend this agreement. (b) The notice to be published under clause 3.2(b)(ii) must invite Members and other interested persons to submit written comments on the proposal to the Operator on or before a date specified in the notice (which must be at least 20 Business Days after the date of the notice). (c) If the Operator considers it appropriate having regard to issues raised in submissions, it may undertake further consultation on specified issues or alternative proposals, and the notice and minimum time periods in paragraph (b) apply to that further consultation. (d) The Operator must publish its decision on the proposal on its website within 20 Business Days after the closing date for submissions under paragraph (b) or (d) as applicable. The decision must: (i) summarise any comments received on the proposal; (ii) set out the proposed amendment to be made (if any); (iii) if the proposed amendment is materially different from the original proposal, describe how and why the proposal has been revised; (iv) if the decision is to make a proposed amendment then specify the day on which the amendment is to take effect; and (v) if the decision is against making any proposed amendment, state that the proposal has been rejected and give reasons for the rejection. (e) At least 15 Business Days before the day on which any amendment is to take effect, or an earlier date fixed by this agreement in any particular case, the Operator must: (i) notify all Members and the AER of the amendment; and (ii) publish the amendment and the amended Exchange Agreement on its website. (f) In determining whether or not to make an amendment under this provision, the Operator must take into account all relevant and material comments that it receives by the closing date for comments and may take into account any comments it receives after that date.

  • Arbitration Process Any arbitration will be conducted pursuant to the applicable rules (the “Arbitration Rules”) of the American Arbitration Association, as modified herein, to the extent such modifications are not prohibited by the Arbitration Rules. The arbitration will be conducted in Indianapolis, Indiana. The parties will select a single arbitrator, but in the event that the parties are unable to agree, the arbitrator will be appointed pursuant to the Arbitration Rules. The arbitrator will be a practicing attorney with significant expertise in litigating and/or presiding over cases involving the substantive legal areas involved in the dispute. The parties to the arbitration will not request, and the arbitrator will not order, that any discovery be taken or provided, including depositions, interrogatories or document requests, except to the extent the amount in controversy exceeds $50,000. The arbitration will be concluded within three months of the date the arbitrator is appointed. The arbitrator’s findings, reasoning, decision, and award will be stated in writing and based upon applicable law. Judgment on the arbitration award may be entered in any court having jurisdiction. In the event that the arbitration results in an award which imposes an injunction or contains a monetary award in excess of $100,000, the award will be reviewable on appeal initiated by filing notice of appeal with the AAA office within 30 days of the award, governed by the AAA Optional Appellate Arbitration Rules and conducted by a panel of three new arbitrators, ruling by majority, under the procedure for appointment from the national roster of arbitrators. Unless the applicable Arbitration Rules require otherwise, arbitration fees and costs will be shared equally by the claimant(s) and respondent(s), respectively, in any arbitration proceeding. Should the AAA be unavailable, unable or unwilling to accept and administer the arbitration of any claim under these arbitration provisions as written, the parties will agree on a substitute arbitration organization, such as JAMS, that will enforce the arbitration provisions as written. Because this Agreement memorializes a transaction in interstate commerce, the Federal Arbitration Act governs the interpretation and enforcement of these arbitration provisions. More information about arbitration, including the Arbitration Rules, is available at xxx.xxx.xxx or by calling 0-000-000-0000.

  • TRANSACTION PROCESS The RFQ for this Lot will contain a deliverable-based Statement of Work (SOW). The RFQ will include, but is not limited to: Authorized User timeframes; system integration requirements; and other risks that may affect the cost to the Authorized User. All responses to RFQs must include detailed price information, including but not limited to: hours required per title, cost per hour etc. Travel, lodging and per diem costs must be itemized in the total quote and may not exceed the rates in the NYS OSC Travel Policy. More information can be found at xxxx://xxx.xxx.xxxxx.xx.xx/agencies/travel/travel.htm. All costs must be itemized and included in the Contractor’s quote.

  • Complaints Process The School shall establish and adhere to a process for resolving public complaints which shall include an opportunity for complainants to be heard. The final administrative appeal shall be heard by the School's Governing Board, except where the complaint pertains to a possible violation of any law or term under this Contract. The complaints process shall be readily accessible from the School’s website, as described in Section 11.4.1.

  • Sick Leave Verification Process a. The new school district shall provide the employee with the necessary verification form at the time the employee receives confirmation of employment in the school district. b. An employee must initiate the sick leave verification process and forward the necessary verification forms to the previous school district(s) within ninety (90) days of commencing employment with the new school district. c. The previous school district(s) shall make every reasonable effort to retrieve and verify the sick leave credits which the employee seeks to port.

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