Responsibilities of Consultant a. Consultant, as an independent contractor to Client, shall perform the Scope of Work (Exhibit A) in accordance with, and subject to, the other provisions of this Agreement. b. The Scope of Work shall be performed in accordance with all applicable federal, state, and local rules and regulations including, but not limited to, the requirements of the Storage Tank and Spill Prevention Act (Act 32 of 1989, as amended) and Pa. Code, Title 25, Chapter 245, established under the Land Recycling and Environmental Remediation Standards Act (Act 2 of 1995) and Pa. Code, Chapter 250 (Administration of Land Recycling Program). c. Consultant shall perform the Scope of Work for an amount not to exceed the Base Contract Price (“BCP”) of $[insert BCP] plus any Cost Adders, Optional Milestones and/or Unit Costs, subject to all other provisions of this Agreement. d. Consultant shall participate in periodic site meetings with the Client and PAUSTIF for site status updates. Consultant will be provided no less than ten (10) days written notice of the date, time, and location of the meeting by the Client/PAUSTIF through their third party administrator.
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 THE UNIVERSITY The UNIVERSITY shall designate in writing a faculty member to coordinate with a designee of the FIELDWORK SITE.
Responsibilities of Both Parties 6.1 The CLEC providing the circuit between CLEC’s office and SBC-12STATE’s office shall make such circuits available for use in connection with the DA services covered herein. When the total traffic exceeds the capability of the existing circuits, additional circuits will be provided by the CLEC. 6.2 Where applicable, if additional ADAX cards and ASN Routers (with sync and token ring cards) are necessary, they will be provided by SBC-12STATE, and CLEC will reimburse SBC-12STATE for the cost, plus Engineering, Furnish and Installation.
RESPONSIBILITIES OF PARTIES A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER 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 MPOWER. BellSouth will not issue line-based calling cards in the name of MPOWER’s individual end users. In the event that MPOWER wants to include calling card numbers assigned by the MPOWER 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 MPOWER has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER 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. MPOWER 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 MPOWER 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. MPOWER 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 MPOWER 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. BellSouth will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER 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 MPOWER.
Responsibilities of the Parties 1.5.1 The Parties shall perform all obligations of this Agreement in accordance with all Applicable Laws and Regulations, Operating Requirements, and
Responsibilities of Client a. Client shall exclusively retain the services of Consultant to perform the Scope of Work, in accordance with, and subject to, the other provisions of this Agreement. b. Client shall provide access for Consultant and its subcontractors to the Site, and shall enter into access agreements with other third party property owners, as necessary for Consultant to complete the performance of the Scope of Work. c. Client shall, as necessary to complete the Scope of Work: (i) cooperate and assist Consultant with the preparation and submittal, to PADEP, PAUSTIF, local governing authorities and others, of all information and documents including, without limitation, correspondence, notices, reports, data submittals, restrictive covenants, engineering and institutional controls, and the like; and (ii) implement and maintain any engineering or institutional controls. d. Client shall transmit to Consultant copies of all documentation, correspondence, reports, and the like, sent or received by Client, regarding the Scope of Work at the Site. e. Client shall make a good faith effort to minimize any and all interference with the progress of the Scope of Work if the Site is remodeled or otherwise modified. Client shall also make a good faith effort to place this condition on third parties that are not a party to this Agreement including, but not limited to, current owners, future owners, current operators, future operators, current lessees and future lessees.