Responsibilities of Edam Entity and Caiso
Responsibilities of Edam Entity and Caiso Sample Clauses
Related to Responsibilities of Edam Entity and Caiso
Responsibilities of Customer 5.1 To the extent that the Supplier requires access to the Customer Site to perform the Services, the Customer shall provide such access during Normal Business Hours and to provide a suitable work environment to enable the Supplier to perform such Services subject to the Supplier complying with such internal policies and procedures of the Customer (including those relating to security and health and safety) as may be notified to the Supplier in writing from time to time. 5.2 The Customer shall co-operate with the Supplier in all matters relating to the Services and shall appoint a minimum of two Representatives (“Customer Representatives”), who shall have authority to commit the Customer on all matters relating to the relevant Service. 5.3 The Customer agrees and acknowledges the terms of the applicable Licence Agreements and the terms of the CSP Agreement shall form part of this Agreement. For the avoidance of doubt, in the event the applicable Licence Agreements, and/or the CSP Agreement is not applicable to the Services being received or delivered by the Supplier to the Customer under this Agreement, such agreements shall not apply. 5.4 Customer shall: (a) adhere to the Fair Usage Policy; (b) ensure it has suitable licences in place for any third party software required (which is not issued by the Supplier) to allow the Supplier and its subcontractors full use in relation to the Services provided; (c) co-operate with the Supplier in all matters relating to the Services as reasonably requested by the Supplier; (d) adhere to the dates scheduled for provision of Services by the Supplier to the Customer as stated in the applicable Statement of Work or otherwise agreed between the Parties in writing. In the event the Customer wishes to reschedule or cancel the dates for the provision of Services, liquidated damages (“Liquidated Damages”) will become payable from the Customer to the Supplier on the following basis: (i) if dates are changed or cancelled at the Customer’s request more than fourteen (14) days before the scheduled start date no Liquidated Damages are payable; (ii) if dates are changed or cancelled between seven (7) days and fourteen
RESPONSIBILITIES OF CITY City or its representative shall issue all communications to Contractor. City has the authority to request changes in the work in accordance with the terms of this Agreement and with the terms in Exhibit A – Scope of Work. City has the authority to stop work or to suspend any work.
Responsibilities of Business Associate Business Associate agrees:
RESPONSIBILITIES OF PARTIES A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The CLEC-1 will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BellSouth shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BellSouth shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BellSouth’s reasonable control. BellSouth will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BellSouth will issue line-based calling cards only in the name of CLEC-1. BellSouth will not issue line-based calling cards in the name of CLEC-1’s individual end users. In the event that CLEC-1 wants to include calling card numbers assigned by the CLEC-1 in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the CLEC-1 has identified the billing number as one which should not be billed for collect or third number calls, or both. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to CLEC-1 by BellSouth will be in accordance with the methods and practices regularly adopted and applied by BellSouth to its own operations during the term of this Agreement, including such revisions as may be made from time to time by BellSouth. 2. CLEC-1 shall furnish all relevant information required by BellSouth for the provision of XXX Hosting, CATS and NICS. 3. Applicable compensation amounts will be billed by BellSouth to CLEC-1 on a monthly basis in arrears. Amounts due from one Party to the other (excluding adjustments) are payable within thirty (30) days of receipt of the billing statement. 4. CLEC-1 must have its own unique XXX code. Requests for establishment of XXX status where BellSouth is the selected Centralized Message Distribution System (CMDS) interfacing host, require written notification from CLEC-1 to the BellSouth XXX Hosting coordinator at least eight (8) weeks prior to the proposed effective date. The proposed effective date will be mutually agreed upon between the Parties with consideration given to time necessary for the completion of required Telcordia (formerly BellCore) functions. XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of CLEC-1 and will coordinate all associated conversion activities. 5. BellSouth will receive messages from CLEC-1 that are to be processed by BellSouth, another LEC or CLEC in the BellSouth region or a LEC outside the BellSouth region. 6. BellSouth will perform invoice sequence checking, standard EMI format editing, and balancing of message data with the EMI trailer record counts on all data received from CLEC-1. 7. All data received from CLEC-1 that is to be processed or billed by another LEC or CLEC within the BellSouth region will be distributed to that LEC or CLEC in accordance with the agreement(s) which may be in effect between BellSouth and the involved LEC or CLEC. 8. All data received from CLEC-1 that is to be placed on the CMDS network for distribution outside the BellSouth region will be handled in accordance with the agreement(s) which may be in effect between BellSouth and its connecting contractor (currently Telcordia (formerly BellCore)). 9. BellSouth will receive messages from the CMDS network that are destined to be processed by CLEC-1 and will forward them to CLEC-1 on a daily basis. 10. Transmission of message data between BellSouth and CLEC-1 will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and CLEC-1 will be formatted in accordance with accepted industry standards for EMI formatted records and packed between appropriate EMI header and trailer records, also in accordance with accepted industry standards. 12. CLEC-1 will ensure that the recorded message detail necessary to recreate files provided to BellSouth will be maintained for back-up purposes for a period of three (3) calendar months beyond the related message dates. 13. Should it become necessary for CLEC-1 to send data to BellSouth more than sixty (60) days past the message date(s), CLEC-1 will notify BellSouth in advance of the transmission of the data. If there will be impacts outside the BellSouth region, BellSouth will work with its connecting contractor and CLEC-1 to notify all affected Parties. 14. In the event that data to be exchanged between the two Parties should become lost or destroyed, both Parties will work together to determine the source of the problem. Once the cause of the problem has been jointly determined and the responsible Party (BellSouth or CLEC-1) identified and agreed to, the company responsible for creating the data (BellSouth or CLEC-1) will make every effort to have the affected data restored and retransmitted. If the data cannot be retrieved, the responsible Party will be liable to the other Party for any resulting lost revenue. Lost revenue may be a combination of revenues that could not be billed to the end users and associated access revenues. Both Parties will work together to estimate the revenue amount based upon historical data through a method mutually agreed upon. The resulting estimated revenue loss will be paid by the responsible Party to the other Party within three (3) calendar months of the date of problem resolution, or as mutually agreed upon by the Parties. 15. Should an error be detected by the EMI format edits performed by BellSouth on data received from CLEC-1, the entire pack containing the affected data will not be processed by BellSouth. BellSouth will notify CLEC-1 of the error condition. CLEC-1 will correct the error(s) and will resend the entire pack to BellSouth for processing. In the event that an out-of-sequence condition occurs on subsequent packs, CLEC-1 will resend these packs to BellSouth after the pack containing the error has been successfully reprocessed by BellSouth. 16. In association with message distribution service, BellSouth will provide CLEC-1 with associated intercompany settlements reports (CATS and NICS) as appropriate. 17. In no case shall either Party be liable to the other for any direct or consequential damages incurred as a result of the obligations set out in this agreement.
