COUNTY’S CONTRACT TRANSITION PROCESS Sample Clauses

COUNTY’S CONTRACT TRANSITION PROCESS. CONTRACTOR agrees to provide all information deemed necessary by the County for use in subsequent procurement cycles.
Sample 1Sample 2Sample 3See All (8)
AutoNDA by SimpleDocs
COUNTY’S CONTRACT TRANSITION PROCESS. CONTRACTOR agrees to provide all information deemed necessary by the County for use in subsequent procurement cycles. Santa Xxxxx County Social Services Agency A. Contract Goal: B. Situation
Sample 1
COUNTY’S CONTRACT TRANSITION PROCESS. CONTRACTOR agrees to provide all information deemed necessary by the County for use in subsequent procurement cycles. Agency: City of Milpitas
Sample 1
COUNTY’S CONTRACT TRANSITION PROCESS. CONTRACTOR agrees to provide all information deemed necessary by the County for use in subsequent procurement cycles. Santa Xxxxx County Social Services Agency‌ Social Services Agency (SSA)* $ 91,650 100% 1 Other Funding Sources: 0% Total Funding Resources** $ 91,650 100% 1 Firm Commitment-Already have an agreement or letter confirming funding 2 Anticipated Renewal of Existing Funding-Continuation of current year funding 3 Anticipated Resource-Projection of previous fees or donations 4 Application Pending-Application has been submitted, no confirmation at this time 5 Pre-Application-Not yet submitted and expect funding * The SSA line in FY 00-00 Xxxxxx, Xxxxxx "X" should equal the Grand Total of Column "B" in the Budget Detail. ** The Total Funding Resources in Column "B" should equal the Grand Total of Column "D" in the Budget Detail. Contract between the County of Santa Xxxxx and Bay Area Legal Aid Contract # SBC-OIR-BALA-IOLR-CLI-FY20 Immigrant Case Management, Legal Representation, and Intervention Services - Direct Legal Assistance A Staff Name and Job Title B Annual Salary C % Time Allocated to Contract D Number of Months E Salary Allocated to Contract * Xxxx Xxxxxxxx, Managing Attorney $ 110,507.00 9.6% 6 $ 5,304.34 Xxxxxx Xxxxxxxxx, DV & Family Law Attorney $ 75,407.00 24.0% 6 $ 9,048.84 Xxxxxxx Xxxxxxx, Immigration Attorney $ 81,725.00 24.0% 6 $ 9,807.00 Mélody Saint-Saëns, Immigration Regional Counsel $ 100,503.00 14.4% 6 $ 7,246.27 Xxxxxx Del-Pan, Director of Pro Xxxx $ 113,510.00 20.0% 6 $ 11,351.00 Pro Xxxx Coordinator, to be hired $ 49,680.00 17.3% 6 $ 4,284.90 Legal Advice Line $ 71,119.00 9.5% 6 $ 3,378.15 Xxxxxx Xxxxxxx, Office Manager $ 72,404.00 14.3% 6 $ 5,176.89 *Total Salary Allocated to this Contract should equal the Salaries line in Contract Amount, Column "B" of the Budget Detail. Contract between the County of Santa Xxxxx and Bay Area Legal Aid Contract # SBC-OIR-BALA-IOLR-CLI-FY20 Immigrant Case Management, Legal Representation, and Intervention Services - A B Direct Costs * C D Salaries $ 55,597.50 $ 55,597.50 Payroll Taxes $ 4,575.50 $ 4,575.50 Employee Benefits $ 9,601.50 $ 9,601.50 Communication Expense $ 2,240.50 $ 2,240.50 Equipment $ 1,005.50 $ 1,005.50 Insurance $ 719.50 $ 719.50 Office Supplies $ 931.00 $ 931.00 Rent $ 7,509.50 $ 7,509.50 Travel $ 566.00 $ 566.00 Other(Postage, Printing, and Deliveries $ 564.00 $ 564.00 Indirect Costs *** (maximum 15% of budget or federally approved indirect rate) Administrative Overhead...
Sample 1
COUNTY’S CONTRACT TRANSITION PROCESS. CONTRACTOR agrees to provide all information deemed necessary by the County for use in subsequent procurement cycles. I. PROGRAM OVERVIEW A. The intent of the COUNTY is to partner with CONTRACTOR to ensure coordinated service delivery and adhere to the intent of the COUNTY to establish The Welcoming Center (CENTER) as a receiving, assessment and intake facility where children and youth who either have been removed from their family home, court-ordered for placement, are experiencing a loss of placement or are returning from placement may stay. CONTRACTOR shall transform, operate and manage the facility located at 0000 Xxxx Xxxxxx in San Xxxx as the CENTER. Once identified, CONTRACTOR shall present the proposed location and the facility to the COUNTY for inspection and prior approval. B. The CENTER shall be operational for 24-hours a day, 7-days a week and shall hold children and youth for up to 23 hours and 59 minutes, while a more permanent placement is located. The CENTER is expected to serve an average of four children and youth, including siblings, per day. The CENTER shall serve the actual number of children and youth admitted at any given time of the day, regardless if the number is lower or higher than the average number. C. The CENTER must be able to accommodate at least two infants using two separate cribs, two toddlers, and seven children and adolescents. The CENTER must have a designated common area that must be divided into two smaller activity areas. One area shall be set up with activities and toys geared toward infants, toddlers and young children, while the other area shall have activities, including games and books, for older children and teens. The CENTER must maintain a home-like setting to make each child feel as comfortable as possible during the time of disruption. It must be maintained with accessories, such as but not limited to toys, games, healthy snacks, entertainment media, space to play including a nearby park, and individual rooms for those who want some quiet space. The Center must also have communication equipment and enhanced security measures to ensure safety of clients and staff. D. All behavioral health services shall be provided pursuant to Exhibit C: BHSD Scope of Work. This is the same scope of work attached to the separate contract between the CONTRACTOR and Behavioral Health Services Department (BHSD) also for the same program. In the event of a conflict between the provisions herein and Exhibit C, including any sub...
Sample 1
COUNTY’S CONTRACT TRANSITION PROCESS. CONTRACTOR agrees to provide all information deemed necessary by the County for use in subsequent procurement cycles. PROGRAM : Commercial Sexual Exploitation of Children (CSEC) CONTRACTOR : Community Solutions
Sample 1
COUNTY’S CONTRACT TRANSITION PROCESS. CONTRACTOR agrees to provide all information deemed necessary by the County for use in subsequent procurement cycles. Santa Xxxxx County Social Services Agency # Staff Name and Job Title Activities Staff Person Will Perform Education, Experience, and Qualifications Language and Cultural Competence 1 Xxxx Xxxxxxxx, IPV Advocacy and Housing Programs Manager Responsible for development and implementation of Self-Sufficiency Programs. Oversees Self-Sufficiency Coordinator. Provides training, mentoring, and evaluation for project staff. Develops partnerships for external self-sufficiency programming providers. Almost 30 years experience in managing housing programs including Director for South County Housing where responsibilities included oversight of the day to day administration of 32 subsidized housing developments, 4 commercial sites, 3 homeowner associations, 2 mobile home parks. Ensured developments were in compliance with local, state, federal and housing program regulations. Secured the financial stability of properties by accurate preparation of budgets and monitoring revenue/expenses. Properly monitored the facilities by assuring implementation of preventive and capital improvement schedules. Fostered positive tenant and community relations. Prepared complex reports to funding agencies and boards as required; Supervised a team of 30 staff property management, maintenance and administrative staff. Key member to a nationwide 10- member committee for NeighborWorks America. Committee created a "Measures and Outcomes" reference book for affordable housing professionals, providing residents services to multi-family portfolios. Xxxx is fluent in English and Spanish, and is bi- cultural. She is trained in cross-cultural competence, demonstrates an awareness and respect for the beliefs, practices, traditions, religions, history, languages, and physical abilities of the individuals we serve. We view sexual orientation as a positive form of diversity that is desired in a multicultural setting. Community Solutions has a policy on language access.
Sample 1
AutoNDA by SimpleDocs
COUNTY’S CONTRACT TRANSITION PROCESS. CONTRACTOR agrees to provide all information deemed necessary by the County for use in subsequent procurement cycles. Santa Xxxxx County Social Services Agency 2 A. Dhoraje, Manager of Support Services Oversees Support Services programs (support group program, aligned children's services, permanent supportive housing services, and long-term self- sufficiency case management). This includes design, implementation, and evaluation of program goals and supervision of Support Services staff. Masters in Counseling Psychology. 8 years experience at NDSDV with Support Groups and the shelter. Has completed the 40-hour Domestic Violence Training mandated by the State. Domestic Violence Peer Counselor certified; includes cultural competency and responsiveness training. Xx. Xxxxxxx speaks Hindi and Marathi and has a bicultural background. Santa Xxxxx County Social Services Agency A. Contract Goal: B. Situation
Sample 1

Related to COUNTY’S CONTRACT TRANSITION PROCESS

  • Contract Transition Upon Contract expiration or termination, the Contractor shall ensure a seamless transfer of Contract responsibilities with any subsequent Contractor necessary to transition the Products and services of the Contract. The incumbent Contractor assumes all expenses related to the contract transition.

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

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

  • Seniority Verification Process i. The new school district shall provide the employee with the necessary verification form at the time the employee achieves continuing contract status. ii. The employee must initiate the seniority verification process and forward the necessary verification forms to the previous school district(s) within ninety (90) days of receiving a continuing appointment in the new school district. iii. The previous school district(s) shall make every reasonable effort to retrieve and verify the seniority credits which the employee seeks to port.

  • Contract Task Order A- E shall be assigned work via a task order by COUNTY which shall subsequently be referred to as the “Contract Task Order” (hereinafter “CTO”). A CTO for each project shall be developed by A-E in conjunction with COUNTY Project Management staff. The County Project Manager shall manage all A-E’s work including monitoring the CTO work schedule, quality of deliverables, review of invoiced amounts, adherence to set budget, and internal review of submittal packages. A-E shall follow all requirements as outlined in the CTO; this general Scope of Work, the project specific Scope Statement, and the Architect-Engineer Guide (Rev July 2018). The CTO shall include a detailed Scope Statement, describing tasks to be performed with a specific list of deliverables for each task, schedule of work and cost to complete the work. The schedule of work shall allow enough time for meetings with County Management staff to review the work progress, provide technical and policy direction, resolve problems and ensure adherence to the work completion schedule. The CTO shall include a cover sheet provided by County Project Management staff with the appropriate signature blocks and contract information. Once both Parties agree, and all Parties have signed the CTO, County Management staff shall provide A-E with a Notice to Proceed (NTP) to begin work. A-E shall submit all plans, reports and other documents produced under the CTO to the assigned County Project Manager within the timeframe indicated in the CTO or as directed by County Project Management staff.

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

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

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

  • Modifications and Updates to the Wire Center List and Subsequent Transition Periods 5.4.6.1 In the event AT&T identifies additional wire centers that meet the criteria set forth in Sections 5.4.2.1 or 5.4.2.2 above, but that were not included in the Master List of Unimpaired Wire Centers or AT&T’s List of Unimpaired Wire Centers, AT&T shall include such additional wire centers in a CNL. Each such list of additional wire centers shall be considered a Subsequent Wire Center List. AT&T will follow any limitations on the frequency with which it may issue such lists and notification procedures set forth in applicable Commission orders. 5.4.6.2 TWTC shall have thirty (30) business days to dispute the additional wire centers listed on AT&T’s CNL. Absent such dispute, effective thirty (30) business days after the date of a AT&T CNL providing a Subsequent Wire Center List, AT&T shall not be required to provide DS1 and DS3 Dedicated Transport, as applicable, in such additional wire center(s), except pursuant to the self-certification process as set forth in Section 1.9.1 of this Attachment. 5.4.6.3 For purposes of Section 5.4.6.1 above, AT&T shall make available DS1 and DS3 Dedicated Transport that were in service for TWTC in a wire center on the Subsequent Wire Center List as of the thirtieth (30th) business day after the date of AT&T’s CNL identifying the Subsequent Wire Center List (Subsequent Embedded Base) until one hundred eighty (180) days after the thirtieth (30th) business day Version: 4Q06 Standard ICA 11/30/06 from the date of AT&T’s CNL identifying the Subsequent Wire Center List (Subsequent Transition Period). 5.4.6.4 The rates set forth in Exhibit B shall apply to the Subsequent Embedded Base during the Subsequent Transition Period. 5.4.6.5 No later than one hundred eighty (180) days from AT&T’s CNL identifying the Subsequent Wire Center List, TWTC shall submit an LSR(s) or spreadsheet(s) as applicable, identifying the Subsequent Embedded Base of circuits to be disconnected or converted to other AT&T services. 5.4.6.5.1 In the case of disconnection, the applicable disconnect charges set forth in this Agreement shall apply. 5.4.6.5.2 If TWTC chooses to convert DS1 and/or DS3 Dedicated Transport to special access circuits in existence as of the Effective Date of this Agreement, AT&T will include such DS1 and/or DS3 Dedicated Transport within TWTC’s total special access circuits, and apply any discounts to which TWTC is entitled from the transition period of 3/11/2006 to the conversion date. Conversions will be subject to the switch-as-is charge set forth in Exhibit A to this Attachment 2. 5.4.6.5.3 AT&T shall not impose disconnect or nonrecurring installation charges when transitioning the Subsequent Embedded Base of DS1 and DS3 Dedicated Transport in existence as of the Effective Date of this Agreement. 5.4.6.6 If TWTC fails to submit the LSR(s) or spreadsheet(s) for all of its Subsequent Embedded Base by one hundred eighty (180) days after the date of AT&T’s CNL identifying the Subsequent Wire Center List, AT&T will identify TWTC’s remaining Subsequent Embedded Base, if any, and will transition such circuits to the equivalent tariffed AT&T service(s), or in the case of Georgia, to the equivalent 271 service(s) set forth in Exhibit 1. In the states of Florida, Kentucky, Mississippi and South Carolina, those circuits identified and transitioned by AT&T shall be subject to the applicable disconnect charges as set forth in this Agreement and the full nonrecurring charges for installation of the equivalent tariffed AT&T service as set forth in AT&T’s tariffs. In the states of Alabama, Georgia, North Carolina and Tennessee, those circuits identified and transitioned by AT&T shall be subject to the applicable switch-as-is rates set forth in Exhibit A of Attachment

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

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