Government Code Claim Requirement No suit for money or damages may be brought against the City until a written claim therefor has been presented to and rejected by the City in conformity with the provisions of San Francisco Administrative Code Chapter 10 and California Government Code Section 900, et seq. Nothing set forth in this Agreement shall operate to toll, waive or excuse Contractor’s compliance with the California Government Code Claim requirements set forth in San Francisco Administrative Code Chapter 10 and California Government Code Section 900, et seq.
Depositions Depositions should not be taken if a less complicated or more cost effective procedure will obtain the desired information.
4.2.1 The Firm should evaluate the need for each deposition and should only pursue such depositions when necessitated by the unique circumstances of the specific matter. The Firm should evaluate the need for transcription of the deposition; however, a copy of any transcript obtained should be provided to Citizens in a timely manner and uploaded into Acuity.
4.2.2 The Firm shall consult with Citizens prior to initiating any deposition, if not already approved through the case plan. The Firm shall make its recommendations concerning the depositions it expects to take in the Initial
4.2.3 It is the responsibility of the Firm to ensure that all witnesses testifying on behalf of Citizens are sufficiently prepared for each and every deposition. In the event a Corporate Representative is required for deposition, the Firm shall immediately notify Citizens and cooperate with Citizens in the designation and preparation of such witness for deposition.
4.2.4 In the event that a notice for deposition requires production of any documents held by Citizens, the Firm shall immediately notify Citizens and comply with Citizens’ policies regarding records production.
Emergency Escalation initiated by ICANN Upon reaching 10% of the Emergency thresholds as described in Section 6 of this Specification, ICANN’s emergency operations will initiate an Emergency Escalation with the relevant Registry Operator. An Emergency Escalation consists of the following minimum elements: electronic (i.e., email or SMS) and/or voice contact notification to the Registry Operator’s emergency operations department with detailed information concerning the issue being escalated, including evidence of monitoring failures, cooperative trouble-‐shooting of the monitoring failure between ICANN staff and the Registry Operator, and the commitment to begin the process of rectifying issues with either the monitoring service or the service being monitoring.
Emergency Escalation Escalation is strictly for purposes of notifying and investigating possible or potential issues in relation to monitored services. The initiation of any escalation and the subsequent cooperative investigations do not in themselves imply that a monitored service has failed its performance requirements. Escalations shall be carried out between ICANN and Registry Operators, Registrars and Registry Operator, and Registrars and ICANN. Registry Operators and ICANN must provide said emergency operations departments. Current contacts must be maintained between ICANN and Registry Operators and published to Registrars, where relevant to their role in escalations, prior to any processing of an Emergency Escalation by all related parties, and kept current at all times.
Post-Observation Conference 1. The post- observation conference between the evaluator and teacher will be held no later than ten (10) days after the formal observation.
2. The purpose of the post-observation conference is to review the evaluator’s and teacher’s evidence related to the scoring criteria during the observation, and to discuss the teacher’s performance.
3. If there is an area of concern, the evaluator will identify specific concerns for the applicable criteria and provide possible solutions to remedy the concern in writing.
Production of Witnesses; Records; Cooperation (a) After the Effective Time, each Party shall use its commercially reasonable efforts to make available to the other Party, upon written request, the former, current and future directors, officers, employees, other personnel and agents of the members of its respective Group as witnesses and any books, records or other documents within its control or which it otherwise has the ability to make available without undue burden, to the extent that any such Person (giving consideration to business demands of such directors, officers, employees, other personnel and agents) or books, records or other documents may reasonably be required in connection with any Action in which the requesting Party (or member of its Group) may from time to time be involved, regardless of whether such Action is a matter with respect to which indemnification may be sought hereunder. The requesting Party shall bear all costs and expenses in connection therewith.
(b) If an Indemnifying Party chooses to defend or to seek to compromise or settle any Third-Party Claim, the other Party shall make available to such Indemnifying Party, upon written request, the former, current and future directors, officers, employees, other personnel and agents of the members of its respective Group as witnesses and any books, records or other documents within its control or which it otherwise has the ability to make available without undue burden, to the extent that any such Person (giving consideration to business demands of such directors, officers, employees, other personnel and agents) or books, records or other documents may reasonably be required in connection with such defense, settlement or compromise, or such prosecution, evaluation or pursuit, as the case may be, and shall otherwise cooperate in such defense, settlement or compromise, or such prosecution, evaluation or pursuit, as the case may be.
(c) Without limiting the foregoing, the Parties shall cooperate and consult to the extent reasonably necessary with respect to any Actions.
(d) Without limiting any provision of this Section 6.7, each of the Parties agrees to cooperate, and to cause each member of its respective Group to cooperate, with each other in the defense of any infringement or similar claim with respect any Intellectual Property and shall not claim to acknowledge, or permit any member of its respective Group to claim to acknowledge, the validity or infringing use of any Intellectual Property of a third Person in a manner that would hamper or undermine the defense of such infringement or similar claim.
(e) The obligation of the Parties to provide witnesses pursuant to this Section 6.7 is intended to be interpreted in a manner so as to facilitate cooperation and shall include the obligation to provide as witnesses inventors and other officers without regard to whether the witness or the employer of the witness could assert a possible business conflict (subject to the exception set forth in the first sentence of Section 6.7(a)).
Pre-Observation Conference The pre-observation conference shall be held prior to the first formal observation. The teacher and evaluator will mutually agree when to conference. The purpose of the pre- observation conference is to discuss the employee’s goals, establish a date for the formal observation, and to discuss such matters as the professional activities to be observed, their content, objectives, strategies, and possible observable evidence to meet the scoring criteria.
Office of Inspector General Investigative Findings Expert Review In accordance with Senate Bill 799, Acts 2021, 87th Leg., R.S., if Texas Government Code, Section 531.102(m-1)(2) is applicable to this Contract, Contractor affirms that it possesses the necessary occupational licenses and experience.
Stipulated Penalties Review Notwithstanding any provision of Title 42 of the United States Code or Title 42 of the Code of Federal Regulations, the only issues in a proceeding for Stipulated Penalties under this CIA shall be: (a) whether Good Shepherd was in full and timely compliance with the obligations of this CIA for which OIG demands payment; and (b) the period of noncompliance. Good Shepherd shall have the burden of proving its full and timely compliance and the steps taken to cure the noncompliance, if any. OIG shall not have the right to appeal to the DAB an adverse ALJ decision related to Stipulated Penalties. If the ALJ agrees with OIG with regard to a finding of a breach of this CIA and orders Good Shepherd to pay Stipulated Penalties, such Stipulated Penalties shall become due and payable 20 days after the ALJ issues such a decision unless Good Shepherd requests review of the ALJ decision by the DAB. If the ALJ decision is properly appealed to the DAB and the DAB upholds the determination of OIG, the Stipulated Penalties shall become due and payable 20 days after the DAB issues its decision.
Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-‐level domain name, or (B) block those second-‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.
6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-‐level domain names identified by ICANN and set forth at <xxxx://xxxxxxxx.xxxxx.xxx/en/announcements-‐and-‐ media/announcement-‐2-‐17nov13-‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1.
6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-‐OARC) <xxxxx://xxx.xxx-‐xxxx.xxx/xxxx/xxxx/xxxx>.
6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released.
6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-‐ new-‐gtld-‐annex-‐1-‐07oct13-‐en.pdf>.
