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).
Defense of the Underlying Proceeding (a) Indemnitee shall notify the Company promptly in writing upon being served with any summons, citation, subpoena, complaint, indictment, request or other document relating to any Proceeding which may result in the right to indemnification or the advance of Expenses hereunder and shall include with such notice a description of the nature of the Proceeding and a summary of the facts underlying the Proceeding. The failure to give any such notice shall not disqualify Indemnitee from the right, or otherwise affect in any manner any right of Indemnitee, to indemnification or the advance of Expenses under this Agreement unless the Company’s ability to defend in such Proceeding or to obtain proceeds under any insurance policy is materially and adversely prejudiced thereby, and then only to the extent the Company is thereby actually so prejudiced.
(b) Subject to the provisions of the last sentence of this Section 13(b) and of Section 13(c) below, the Company shall have the right to defend Indemnitee in any Proceeding which may give rise to indemnification hereunder; provided, however, that the Company shall notify Indemnitee of any such decision to defend within 15 calendar days following receipt of notice of any such Proceeding under Section 13(a) above. The Company shall not, without the prior written consent of Indemnitee, which shall not be unreasonably withheld or delayed, consent to the entry of any judgment against Indemnitee or enter into any settlement or compromise which (i) includes an admission of fault of Indemnitee, (ii) does not include, as an unconditional term thereof, the full release of Indemnitee from all liability in respect of such Proceeding, which release shall be in form and substance reasonably satisfactory to Indemnitee, or (iii) would impose any Expense, judgment, fine, penalty or limitation on Indemnitee. This Section 13(b) shall not apply to a Proceeding brought by Indemnitee under Section 12 of this Agreement.
(c) Notwithstanding the provisions of Section 13(b) above, if in a Proceeding to which Indemnitee is a party by reason of Indemnitee’s Corporate Status, (i) Indemnitee reasonably concludes, based upon an opinion of counsel approved by the Company, which approval shall not be unreasonably withheld or delayed, that Indemnitee may have separate defenses or counterclaims to assert with respect to any issue which may not be consistent with other defendants in such Proceeding, (ii) Indemnitee reasonably concludes, based upon an opinion of counsel approved by the Company, which approval shall not be unreasonably withheld or delayed, that an actual or apparent conflict of interest or potential conflict of interest exists between Indemnitee and the Company, or (iii) if the Company fails to assume the defense of such Proceeding in a timely manner, Indemnitee shall be entitled to be represented by separate legal counsel of Indemnitee’s choice, subject to the prior approval of the Company, which approval shall not be unreasonably withheld or delayed, at the expense of the Company. In addition, if the Company fails to comply with any of its obligations under this Agreement or in the event that the Company or any other person takes any action to declare this Agreement void or unenforceable, or institutes any Proceeding to deny or to recover from Indemnitee the benefits intended to be provided to Indemnitee hereunder, Indemnitee shall have the right to retain counsel of Indemnitee’s choice, subject to the prior approval of the Company, which approval shall not be unreasonably withheld or delayed, at the expense of the Company (subject to Section 12(d) of this Agreement), to represent Indemnitee in connection with any such matter.
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.
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.
Insolvency; Voluntary Proceedings The Company or any Material Subsidiary (i) ceases or fails to be solvent, or generally fails to pay, or admits in writing its inability to pay, its debts as they become due, subject to applicable grace periods, if any, whether at stated maturity or otherwise; (ii) voluntarily ceases to conduct its business in the ordinary course; (iii) commences any Insolvency Proceeding with respect to itself; or (iv) takes any action to effectuate or authorize any of the foregoing; or
Assistance in Litigation or Administrative Proceedings Covered Entity shall provide written notice to Business Associate if litigation or administrative proceeding is commenced against Covered Entity, its directors, officers, or employees, based on a claimed violation by Business Associate of HIPAA, the HIPAA Rules or other laws relating to security and privacy or PHI. Upon receipt of such notice and to the extent requested by Covered Entity, Business Associate shall, and shall cause its employees, Subcontractors, or agents assisting Business Associate in the performance of its obligations under the Contract to, assist Covered Entity in the defense of such litigation or proceedings. Business Associate shall, and shall cause its employees, Subcontractor’s and agents to, provide assistance, to Covered Entity, which may include testifying as a witness at such proceedings. Business Associate or any of its employees, Subcontractors or agents shall not be required to provide such assistance if Business Associate is a named adverse party.
Notification of Compromise or Potential Compromise The compromise or potential compromise of Confidential Information must be reported to the DSHS Contact designated on the contract within one (1) business day of discovery. Contractor must also take actions to mitigate the risk of loss and comply with any notification or other requirements imposed by law or DSHS.
Administrative Proceedings With a view to administering in a consistent, impartial, and reasonable manner all measures of general application affecting matters covered by this Agreement, each Party shall ensure, in its administrative proceedings applying measures to particular persons, goods, or services of the other Party in specific cases, that: (a) wherever possible, persons of the other Party that are directly affected by a proceeding are provided with reasonable notice, in accordance with the Party's procedures, when a proceeding is initiated, including a description of the nature of the proceeding, a statement of the legal authority under which the proceeding is initiated, and a general description of any issues in controversy; (b) such persons are afforded a reasonable opportunity to present facts and arguments in support of their positions prior to any final administrative action, when time, the nature of the proceeding, and the public interest permit; and (c) its procedures are in accordance with its law.
Appeals Process The Participants acknowledge that, pursuant to local ordinances, regulations, and rules, each Participant has its own procedures by which matters relating to the calculation, assessment, and collection of business license taxes may be appealed. With respect to Impositions subject to this Agreement, however, each Participant has enacted a local ordinance by which appeals relating to such Impositions are excluded from the otherwise applicable local ordinance. Each Participant agrees that the appeals process described in this Section shall apply to all appeals relating to Impositions subject to this Agreement. Each Participant hereby consents to the adoption of the appeals process described in this Section; specifically declares its intention that such appeals process shall be deemed an exception to its otherwise applicable local ordinances, regulations, and rules; and agrees that it has or will approve such appeals process by appropriate local action.
(a) There is hereby created a board for purposes of hearing appeals pursuant to this Section (the “Appeals Board”). The Appeals Board shall contain three members. The President of the Association, the Executive Director of the Association, and the President of the South Carolina Business Licensing Officials Association (“BLOA”) shall each serve ex officio as members of the Appeals Board, with terms of office coterminous with their terms as officers of the Association or BLOA, as appropriate. The President of the Association, or in his or her absence the Executive Director of the Association, shall serve as chair at meetings of the Appeals Board.
(b) With respect to the calculation, assessment, and collection of Impositions, the following appeals process, as required by Section 6-1-410, shall apply.
(1) If a taxpayer fails or refuses to pay an Imposition by the date on which such Imposition is due, the LRS Business License Official may serve notice of assessment of the Imposition due on the taxpayer by mail or personal service. Within thirty days after the date of postmark or personal service, a taxpayer may request, in writing with reasons stated, an adjustment of the assessment. An informal conference between the LRS Business License Official and the taxpayer must be held within fifteen days of the receipt of the request, at which time the taxpayer may present any information or documents in support of the requested adjustment. Within five days after the conference, the LRS Business License Official shall issue a notice of final assessment and serve the taxpayer by mail or personal service with the notice and provide a form for any further appeal of the assessment by the taxpayer.
(2) Within thirty days after the date of postmark or personal service, the taxpayer may appeal the notice of final assessment by filing a completed appeal form with the LRS Business License Official, by mail or personal service, and by paying to LRS in protest at least eighty percent of the business license tax based on the final assessment. The appeal must be heard and determined by the Appeals Board. The Appeals Board shall provide the taxpayer with written notice of the hearing and with any rules of evidence or procedure prescribed by the Appeals Board. The hearing must be held within thirty days after receipt of the appeal form unless continued to another date by agreement of the parties. A hearing by the Appeals Board must be held at a regular or specially called meeting of the Appeals Board. At the appeals hearing, the taxpayer and LRS have the right to be represented by counsel, to present testimony and evidence, and to cross-examine witnesses. The hearing must be recorded and must be transcribed at the expense of the party so requesting. The Appeals Board shall decide the assessment by majority vote. The Appeals Board shall issue a written decision explaining the basis for the decision with findings of fact and conclusions and shall inform the taxpayer of the right to request a contested case hearing before the Administrative Law Court. The written decision must be filed with the LRS Business License Official and served on the taxpayer by mail or personal service. The decision is the final decision of LRS on the assessment.
(3) Within thirty days after the date of postmark or personal service of LRS’s written decision on the assessment, a taxpayer may appeal the decision to the Administrative Law Court in accordance with the rules of the Administrative Law Court.
DUE PROCESS PROCEEDINGS CONTRACTOR shall fully participate in special education due process proceedings including mediations and hearings, as requested by XXX. Participation further includes the willingness to make CONTRACTOR’s staff available for witness preparation and testimony as is necessary to facilitate a due process hearing. CONTRACTOR shall also fully participate in the investigation and provision of documentation related to any complaint filed with the State of California, the Office of Civil Rights, or any other state and/or federal governmental body or agency. Full participation shall include, but in no way be limited to, cooperating with LEA representatives to provide complete answers raised by any investigator and/or the immediate provision of any and all documentation that pertains to the operation of CONTRACTOR’s program and/or the implementation of a particular student’s IEP/Individual and Family Service Plan (“IFSP”).
