Data Transmission Control Except as necessary for the provision of the Cloud Services in accordance with the Agreement, Personal Data must not be read, copied, modified or removed without authorization during transfer. Where data carriers are physically transported, adequate measures are implemented at SAP to provide the agreed-upon service levels (for example, encryption and lead-lined containers). Measures: • Personal Data in transfer over SAP internal networks is protected according to SAP Security Policy. • When data is transferred between SAP and its customers, the protection measures for the transferred Personal Data are mutually agreed upon and made part of the relevant agreement. This applies to both physical and network based data transfer. In any case, the Customer assumes responsibility for any data transfer once it is outside of SAP-controlled systems (e.g. data being transmitted outside the firewall of the SAP Data Center).
Conversion of Live Telephone Exchange Service to Analog 2W Loops The following coordination procedures shall apply to “live” cutovers of VERIZON Customers who are converting their Telephone Exchange Services to SPRINT Telephone Exchange Services provisioned over Analog 2W unbundled Local Loops (“Analog 2W Loops”) to be provided by VERIZON to SPRINT.
Transmission and Routing of Exchange Access Traffic PURSUANT TO 251(c)(2) 13 5.1 Scope of Traffic 13 5.2 Trunk Group Architecture and Traffic Routing 13 5.3 Logical Trunk Groups 13 5.4 End Office Access 13 ARTICLE VI MEET-POINT BILLING ARRANGEMENTS 14 6.1 Meet-Point Billing Services 14 6.2 Data Format and Data Transfer 14 6.3 Errors or Loss of Access Usage Data 15 6.4 Payment 15 6.5 Additional Limitation of Liability Applicable to Meet-Point Billing Arrangements 16 ARTICLE VII BLV/BLVI TRAFFIC 16
Transmission and Routing of Telephone Exchange Service Traffic PURSUANT TO SECTION 251(c)(2) ............................... 14 4.1
Data Transmission The procedures for transmitting load obligation data to PJM for DS Supplier’s DS Load shall be as set forth by PJM.
Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.
Loop Transmission Types 3.1 Subject to the conditions set forth in Section 1 of this Attachment, Verizon shall allow CBB to access Loops unbundled from local switching and local transport, in accordance with this Section 3 and the rates and charges provided in the Pricing Attachment. Verizon shall allow CBB access to Loops in accordance with, but only to extent required by, Applicable Law. The available Loop types are as set forth below:
SUBMISSION OF THE MONTHLY MI REPORT 4.1 The completed MI Report shall be completed electronically and returned to the Authority by uploading the electronic MI Report computer file to MISO in accordance with the instructions provided in MISO.
Traditional IRA-to-Xxxx XXX Conversions If you convert to a Xxxx XXX, the amount of the conversion from your Traditional IRA to your Xxxx XXX will be treated as a distribution for income tax purposes, and is includible in your gross income (except for any nondeductible contributions). Although the conversion amount generally is included in income, the 10 percent early distribution penalty tax will not apply to conversions from a Traditional IRA to a Xxxx XXX, regardless of whether you qualify for any exceptions to the 10 percent penalty tax. If you are required to take a required minimum distribution for the year, you must remove your required minimum distribution before converting your Traditional IRA.
Developer and Connecting Transmission Owner Notice Developer and Connecting Transmission Owner shall each notify the other Party, first orally and then in writing, of the release of any Hazardous Substances, any asbestos or lead abatement activities, or any type of remediation activities related to the Large Generating Facility or the Attachment Facilities, each of which may reasonably be expected to affect the other Party. The notifying Party shall: (i) provide the notice as soon as practicable, provided such Party makes a good faith effort to provide the notice no later than twenty-four hours after such Party becomes aware of the occurrence; and (ii) promptly furnish to the other Party copies of any publicly available reports filed with any Governmental Authorities addressing such events.
