Electronic Data Exchange Services Sample Clauses

Electronic Data Exchange Services. 1.1.1. Coordinate with PG&E to maintain VCE's Community Choice Aggregation Program ("Program") within PG&E's territory including meetings and calls as needed to ensure timely set up, data transfer, and billing services. 1.1.2. Maintain electronic interfaces and communication protocols with PG&E to exchange a full set of EDI files (including 810, 814, 820, 867, and 997) and interval and load data files (Items 16 and 17). Unless otherwise determined, data from PG&E will be received by SMUD which will process and apply VCE rates and then generate EDI transaction files to be sent back to PG&E for billing and enrollment services. 1.1.3. Process CCASRs from/to PG&E which specify the changes to a customer's choice of service for customer enrollment, or customer initiated returns to bundled utility service (814 Electronic Data Interchange Files). Changes will be reflected in the CRM. 1.1.4. Obtain customer usage data from PG&E's Enterprise Secure File Transfer server to timely bill each customer according to PG&E requirements (867 Electronic Data Interchange Files). SMUD will work with PG&E to maintain protocols required to transfer said customer usage data. 1.1.5. Maintain and communicate the amount to be billed by PG&E for services provided by VCE (810 Electronic Data Interchange Files). SMUD will maintain a rate table of VCE rates and apply applicable rate tariffs to calculate the amount to be billed by PG&E for services provided by VCE. SMUD will work with PG&E to maintain the transactions required to transfer the billing amounts to PG&E via the 810 EDI files and requirements specified by PG&E. 1.1.6. Receive and maintain data related to payment transactions toward Program charges from PG&E after payment is received by PG&E from VCE customers (820 Electronic Data Interchange Files, and/or daily payment files). SMUD will work with PG&E to maintain the transactions required to transfer the payment transactions toward CCE charges from PG&E after payment is received from customers. SMUD will store this payment data as required by VCE. 1.1.7. Conduct integration testing and data validation with PG&E.
Sample 1
AutoNDA by SimpleDocs
Electronic Data Exchange Services a. Process CCA Service Requests (CCASRs) from/to PG&E which specify the changes to a customer’s choice of services such as enrollment in CCA programs, customer initiated returns to bundled utility service or customer initiated returns to direct access service (814 Electronic Data Interchange Files). b. Obtain all customer usage data from PG&E’s Metered Data Management Agent (MDMA) server to allow for timely billing (according to PG&E requirements) of each customer (867 Electronic Data Interchange Files). c. Maintain and communicate the amount to be billed by PG&E for services provided by PCEA (810 Electronic Data Interchange Files). d. Receive and maintain all data related to payment transactions toward CCA charges from PG&E after payment is received by PG&E from customers (820 Electronic Data Interchange Files). e. Process CCASRs with PG&E when customer status changes. f. Participate in the Customer Data Acquisition Program (CDA) beta testing for SmartMeter data sharing as PCE’s Data Manager.
Sample 1
Electronic Data Exchange Services. This Section details the obligations and responsibilities of the Parties regarding Electronic Data Exchange Services, such as file handling. Except where a responsibility is identified as a “P” responsibility for CoreLogic in the matrix below, Supplier shall be responsible for the associated activities. Supplier will: 1.2.1.1 Execute and support the inbound and outbound file transmission process, including performing any programming support to automate the file transmission processes on appropriate platforms. P 1.2.1.2 Test and remediate any issues identified for any programs created to automate the file transmission process for specific files prior to implementing into the production environment. P 1.2.1.3 Attend business unit and customer planning and design meetings to determine the file transmission setup requirements. P 1.2.1.4 Perform daily and after hours support for file transmission issues, including researching missing files, trouble-shooting connectivity issues and after receipt of the information required for Supplier to complete the request, resending files upon CoreLogic customer or business unit request and supporting changes in connectivity setup as initiated by CoreLogic customers. P 1.2.1.5 Report on transmission issues and implement process changes to reduce errors/failures. P 1.2.1.6 Provide scripting support for business unit reports and notifications. P 1.2.1.7 Install and configure Third Party Software for Windows and Unix platforms that will be used in automated transmissions. P 1.2.1.8 Coordinate with internal CoreLogic teams for file transmissions that are configured to monitor for server space and file cleanup. P 1.2.1.9 Work directly with CoreLogic customers during business hours to configure and maintain file transmissions. P CORELOGIC AND DELL CONFIDENTIAL Supplement A Page 104 1.1 INTRODUCTION
Sample 1
Electronic Data Exchange Services i. Process CCA Service Requests (CCASRs) from or to PG&E which specify the changes to a customer’s choice of services such as enrollment in CCA programs, customer initiated returns to bundled utility service, or customer initiated returns to direct access service (814 Electronic Data Interchange Files). ii. Return customers to PG&E bundled service in accordance with City’s late payment policy. iii. Obtain all customer usage data from PG&E’s Metered Data Management Agent (MDMA) server to allow for timely billing (according to PG&E requirements) of each customer (867 Electronic Data Interchange Files). iv. Ensure timely billing (according to PG&E requirements) of each customer (867 Electronic Data Interchange Files). v. Maintain and communicate the amount to be billed by PG&E for services provided by City (810 Electronic Data Interchange Files). vi. Receive and maintain all data related to payment transactions toward CCA charges from PG&E after payment is received by PG&E from customers (820 Electronic Data Interchange Files). vii. Process CCASRs with PG&E when customer status changes.
Sample 1

Related to Electronic Data Exchange Services

  • Electronic Data 7.1.1 The parties recognize that Contract Documents, including drawings, specifications and three-dimensional modeling (such as Building Information Models) and other Work Product may be transmitted among Owner, Design-Builder and others in electronic media as an alternative to paper hard copies (collectively “Electronic Data”).

  • Electronic Data Interchange If both Parties elect to facilitate business activities hereunder by electronically sending and receiving data in agreed formats (also referred to as Electronic Data Interchange or “EDI”) in substitution for conventional paper-based documents, the terms and conditions of this Agreement shall apply to such EDI activities.

  • Electronic Data Interchange (EDI This standard establishes the data contents of the Invoice Transaction Set (810) for use within the context of an EDI environment. This transaction set can be used for invoicing via the AN for catalog and non-catalog goods and services.

  • Electronic Devices No electronic devices that may hinder job performance or safety (especially cell phones), may be carried on employees’ person, or be used by employees during working hours.

  • ELECTRONIC WORKFLOW SYSTEM OGS reserves the right to incorporate an electronic workflow system that may include elements of the Authorized User RFQ process. OGS reserves the right to post Authorized User Contract usage of Centralized Contracts. For Lot 4 only, when provided for in the RFQ and resultant Authorized User Agreement, the Authorized Users may reimburse travel expenses. All rules and regulations associated with this travel can be found at xxxx://xxx.xxxxx.xx.xx/agencies/travel/travel.htm. In no case will any travel reimbursement be charged that exceeds these rates. All travel will be paid only as specified within the Authorized User Agreement and must be billed with the associated services on the same Invoice with receipts attached. The Contractor shall receive prior approval from the Authorized User for any travel that occurs during the term of an Authorized User Agreement. Parking fees and/or parking tickets shall not be paid by an Authorized User. Unless otherwise specified in writing by the Authorized User, a vehicle will not be provided by Authorized User to the Contractor for travel. Therefore, the Contractor will be responsible for ensuring that the Contractor has access to an appropriate vehicle (e.g., personal vehicle or rental vehicle) or common carrier with which to carry out any necessary travel. For the Contractor to obtain reimbursement for the use of a rental vehicle, such use must be justified as the most cost- effective mode of transportation under the circumstances (including consideration of the most effective use of time). The Contractor is responsible for keeping adequate records to substantiate any claims for travel reimbursement. All services provided under the resultant Authorized User Agreement must be performed within CONUS. There are no BONDS for this Contract. However, an Authorized User may require in an RFQ a performance, payment or Bid bond, or negotiable irrevocable letter of credit or other form of security for the faithful performance for the resultant Authorized User Agreement. Pursuant to New York State Executive Law Article 15-A and Parts 140-145 of Title 5 of the New York Codes, Rules and Regulations (“NYCRR”), the New York State Office of General Services (“OGS”) is required to promote opportunities for the maximum feasible participation of New York State-certified Minority- and Women-owned Business Enterprises (“MWBEs”) and the employment of minority group members and women in the performance of OGS contracts.

  • Electronic Road Show The Company has made available a Bona Fide Electronic Road Show in compliance with Rule 433(d)(8)(ii) of the Securities Act Regulations such that no filing of any “road show” (as defined in Rule 433(h) of the Securities Act Regulations) is required in connection with the Offering.

  • Electronic Documents We may make periodic statements, disclosures, notices, and other documents available to you electronically, and, subject to any delivery and receipt verification procedures required by law, you agree to receive such documents electronically and to check the statements for accuracy. If you believe any such statement contains incorrect information, you must follow the procedures set forth in the Related Agreement(s).

  • ELECTRONIC SUBMISSIONS Concessionaire must have the capacity to send and receive electronic submissions and communications as a pre-condition and continuing requirement of this Agreement. For purposes of this Agreement, “Electronic Submissions” shall only include the transmission of documents by email. Concessionaire shall comply with the following terms and conditions: A. Concessionaire shall electronically submit all reports, including, but not limited to, Monthly Reports and Annual Reports as described in Paragraphs 12 and 13, by email to: XxxxxxxxXxxxxx@xxx.xx.xxx. Failure on the part of Concessionaire to submit reports electronically shall be a material breach of this Agreement, subject to Suspension of Operations and/or Termination in accordance with the terms and conditions set forth in Paragraphs 9 and 10. B. Concessionaire shall maintain and monitor on a daily basis an active email address, designated for this Agreement and report any change to the email address during any Term of this Agreement. Failure on the part of Concessionaire to maintain and monitor the active email address, designated for this Agreement, shall be a material breach of this Agreement, subject to Suspension of Operations and/or Termination in accordance with the terms and conditions set forth in Paragraphs 9 and 10.

  • Electronic Access Access by the Customer to certain systems, applications or products of Bank shall be governed by this Agreement and the terms and conditions set forth in Annex A Electronic Access.

  • Picnic Day 49.1 The Parties agree that Building Industry Picnic Day will continue to apply during the life of this Agreement in accordance with the following: (a) The first Monday in December of each year shall be the building industry picnic day, except in Mildura. The second Monday in December shall be the building industry picnic day within an area of 25 kilometres from Mildura. (b) All Employees shall, as far as practicable, be given and shall take this day as Picnic Day without deduction of pay. (c) Any Employee required to work on this day shall be paid at the rate of double time and a half; provided that an Employee who attends for work as required on this day shall be paid for not less than four hours work. (d) The Employer may require from an Employee evidence of their attendance at the picnic and the production of the butt of a ticket issued for the picnic shall be sufficient evidence of such attendance. Where such evidence is requested by the Employer payment need not be made unless the evidence is produced. This requirement only applies so long as all Employees remain eligible to obtain a ticket for Picnic Day regardless of whether or not they are a Union member.

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