Primary Contacts The Parties will keep and maintain current at all times a primary point of contact for this contract. The primary contacts for this this Contract are as follows:
Secondary Contact Name Please identify the individual who will be secondarily responsible for all TIPS matters and inquiries for the duration of the contract.
Cost Containment The Benefit Fund Trustees are directed to explore all reasonable methods of cost containment to minimize the Employer contribution obligations under the contract. In the event Medicare becomes secondary in the application of the retiree benefit plan, the Trustees will take immediate and remedial action to protect the financial integrity of the Plan.
ROLE OF THE PRIMARY AND SECONDARY CONTACTS 5.01 Primary and Secondary Contact(s). The Resident, in executing this Agreement, is required to identify a “Primary Contact” and a “Secondary Contact”. It is strongly recommended that these contacts are parents or legal guardians of the Resident. The Primary Contact serves as the individual that is contacted by the Manager if concerns or problems arise with the Resident, as detailed in section 5.02 below. If the Primary Contact is not available, the Secondary Contact will be contacted.
Emergency Contact CONTRACTOR shall have a responsible person available at, or reasonably near, the Project/Service on a twenty-four (24) hour basis, seven (7) days a week, who may be contacted in emergencies and in cases where immediate action must be taken to handle any problem that might arise. CONTRACTOR shall submit to the COUNTY’s Project Manager, the phone numbers and names of personnel designated to be contacted in cases of emergencies. This list shall contain the name of their supervisors responsible for work pertaining to this Agreement.
Emergency Contacts Contractor shall provide County with a list of names and telephone numbers at which Contractor’s representative, alternate, superintendent, and other key personnel can be reached during non-working hours in the case of an emergency.
Network Maintenance and Management 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result.
38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center.
38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed.
38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties.
38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events.
38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time.
38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below.
38.7.1 AT&T TENNESSEE Disaster Recovery Plan
38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases.
38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate.
38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.
Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity
1.1.02 Identify at least one individual to act as the program contact in the following areas:
1. Immunization Program Manager;
Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:
Patch Management All workstations, laptops and other systems that process and/or 20 store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or 21 transmits on behalf of COUNTY must have critical security patches applied, with system reboot if 22 necessary. There must be a documented patch management process which determines installation 23 timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable 24 patches must be installed within thirty (30) calendar or business days of vendor release. Applications 25 and systems that cannot be patched due to operational reasons must have compensatory controls 26 implemented to minimize risk, where possible.
