Since Verizon has now modified Sample Clauses

Since Verizon has now modified its electronic ordering system to include a method for ***CLEC Acronym TXT*** to provide the certification required by this section, ***CLEC Acronym TXT*** shall use such method, as updated from time to time, to provide such certification [, so long as such method is no more onerous than providing certification by letter].
AutoNDA by SimpleDocs

Related to Since Verizon has now modified

  • Geographic Area and Sector Specific Allowances, Conditions and Exceptions The following allowances and conditions shall apply where relevant. Where the Employer does work which falls under the following headings, the Employer agrees to pay and observe the relevant respective conditions and/or exceptions set out below in each case.

  • FULLY BARGAINED PROVISIONS This Agreement represents and incorporates the complete and final understanding and settlement by the parties on all bargainable issues which were or could have been the subject of negotiations. During the term of this Agreement, neither party will be required to negotiate with respect to any such matter, whether or not covered by this Agreement, and whether or not within the knowledge or contemplation of either or both of the parties at the time they negotiated or signed this Agreement.

  • Amendments - Changes/Extra Work The Subrecipient shall make no changes to this Contract without the County’s written consent. In the event that there are new or unforeseen requirements, the County has the discretion with the Subrecipient’s concurrence, to make changes at any time without changing the scope or price of the Contract.‌ If County-initiated changes or changes in laws or government regulations affect price, the Subrecipient’s ability to deliver services, or the project schedule, the Subrecipient will give County written notice no later ten (10) days from the date the law or regulation went into effect or the date the change was proposed and Subrecipient was notified of the change. Such changes shall be agreed to in writing and incorporated into a Contract amendment. Said amendment shall be issued by the County-assigned Contract Administrator, shall require the mutual consent of all Parties, and may be subject to approval by the County Board of Supervisors. Nothing herein shall prohibit the Subrecipient from proceeding with the work as originally set forth or as previously amended in this Contract.

  • Volunteer Firefighting Leave Leave without pay will be granted when an employee who is a volunteer firefighter is called to duty to respond to a fire, natural disaster or medical emergency.

  • Changes in Equipment, Systems, Etc USBFS reserves the right to make changes from time to time, as it deems advisable, relating to its systems, programs, rules, operating schedules and equipment, so long as such changes do not adversely affect the services provided to the Trust under this Agreement.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.

  • Transfer and Seniority Outside the Bargaining Unit (a) It is understood that an employee shall not be transferred by the Hospital to a position outside the bargaining unit without his consent except in the case of temporary assignments not exceeding six (6) months. Such employees on temporary assignments shall remain members of the bargaining unit. (b) An employee who is transferred to a position outside the bargaining unit shall not, subject to (c) below, accumulate seniority. In the event the employee is returned by the Hospital to a position in the bargaining unit within twenty-four (24) months of the transfer he or she shall be credited with the seniority held at the time of transfer and resume accumulation from the date of his or her return to the bargaining unit. An employee not returned to the bargaining unit within 24 months shall forfeit bargaining unit seniority. (c) In the event an employee transferred out of the bargaining unit under (b) above is returned to the bargaining unit within a period of six (6) calendar months, he shall accumulate seniority during the period of time outside the bargaining unit."

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

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