Project Terms. 1.1 This Agreement sets forth the duties and responsibilities of the Owner and the Designer with respect to the Project. Designer shall provide the services for the Project in accordance with this Agreement.
1.1.1 The scope of the Project is as follows:
Project Terms. 1. TCS expects Client to ensure availability and cooperation of all concerned stakeholders including Client Subject Matter Experts (SMEs), interfacing system owners and 3rd party vendors for business process discussions, process finalization, data collection and harmonization, deliverables sign-off, user acceptance testing and sign-off for Go-Live. TCS expects all relevant and required documents will be made available to it in reasonable timeframe.
2. TCS has considered Client office at <Client Location> as the base location for this engagement on onsite. Client will provide necessary and adequate infrastructure to enable TCS to fulfil its commitment for the assignment. This will be applicable for each onsite TCS Consultant associated with the project and will be arranged for and provided at no cost to TCS. The infrastructure will include office space, computers/terminals and software, computer consumables and communication facilities.
3. Environments provisioned by TCS will be multi-tenant environments allowing sharing of infrastructure and services.
4. Service delivery provisioned by TCS will be shared services allowing sharing of services.
5. The Scheduled downtime for business systems will be eight (8) hours per month.
6. Any organizational changes in the client organization having impact on the on-going services (locations, structure, policies, salary), will be discussed with TCS from the point of view of deployment, and if required will be estimated and proposed separately.
7. Interfacing system owners will be available for providing test data, testing, validating results and ensuring their system availability as applicable.
8. Client will ensure that response to reviews and sign-off of documents happens within <<five>> working days to minimize delays.
9. Any request for change in data provided by Client that has already been uploaded in Production environment will be chargeable
10. Application authorization, role assignment, and employee access matrix shall be agreed and signed-off as part of BRD and UAT. For providing application support, TCS Service Delivery team shall have the required access and authorization. TCS shall not be responsible for any impact due to authorization, roles and access provided to client users TCS will adhere to following Service Levels post 3 months of Go Live. TCS shall measure the Service Levels for initial 3 months for benchmarking, however the Service Levels will not be applicable for the same period.
Project Terms. Xxxxx will…
Project Terms. Service Assumptions & Customer Dependencies In addition to any other responsibilities or assumptions described in this Agreement, the Customer Dependencies are as follows and the Customer recognises that if it fails to comply with the following dependencies, Vodafone is relieved from performing or delivering the Service and may choose to suspend or terminate this Agreement: 1. Customer shall perform and complete the responsibilities and assumptions set out in the Customer Prerequisites section prior to the Service Commencement Date. 2. Customer is solely responsible for implementing a process to ensure that if Customer’s IT Team detects Vodafone’s activities under the Service, such detection will be escalated to Customer’s senior management, or such other knowledgeable Customer personnel, who can intervene prior to such activity being reported outside of Customer’s organisation (e.g. to law enforcement) or, if such activity is reported outside of Customer’s organisation, Customer will promptly clarify that Vodafone was acting with Customer’s full knowledge and consent. 3. Decisions to be made by the Customer must be made promptly and without delay. 4. Customer shall be responsible for delivering all communications internal to Customer regarding the Service, including communications intended to inform Customer employees and personnel about the Service, any impact it may have on Customer employees and personnel, and any training necessary to impacted Customer employees and personnel. 5. Customer must be aware of and acknowledge the risks associated with the Service and must have taken the necessary pre-testing steps (e.g. data backup, internal communications etc.) to help minimize these risks. 6. Customer shall provide an accurate and complete list of email addresses together with names and department/roles of the Targeted Employees in a timely manner, and such other information as may be reasonably required and notified by Vodafone, and shall immediately notify Vodafone if it learns that any information previously provided to Vodafone is materially inaccurate or incomplete. 7. Customer will consent to and authorize Vodafone to access the Customer Property and perform the Service as described in this Agreement. 8. Customer is solely responsible for obtaining any such consents (including copyright for websites to be cloned as part of the Service), permissions or licenses or providing such notices (including from third-parties and Customer employees) necessary...
Project Terms. Tyler will…
Project Terms. Customer Dependencies In addition to any other responsibilities or assumptions described in this Agreement, the Customer Dependencies are as follows and the Customer recognises that if it fails to comply with the following dependencies, Vodafone is relieved from performing or delivering the Service and may choose to suspend or terminate this Agreement: • Customer Property, systems, materials. o the Customer is solely responsible for ensuring the availability of the Customer personnel and resources for the duration of the Service and as necessary for Vodafone’s performance of the Service, including (unless otherwise agreed in writing to form part of Vodafone’s scope) the timely provision of information, access to systems, delivery of systems and logs, "out of band" communications systems, forensic imaging, data restoration, and backup of Customer systems. o if Vodafone is required to use Customer tools during an engagement, the Customer is responsible for enabling Vodafone to have appropriate access to Customer-owned tools, including any necessary licenses. o to the extent applicable, the Customer is responsible for ensuring that the Customer tools to be used as part of the Service are sufficient and appropriate to meet the Customer’s security requirements. o the Customer will make any decisions required of it promptly and without delay and Vodafone shall be entitled to rely on all such decisions and approvals. o the Customer shall provide necessary support (including, for example, providing invite letters where necessary) for obtaining any required visas and/or travel authorisations; • Hardware and software. o if Vodafone and Customer determine that the installation of hardware and software will be necessary to gain additional visibility into Customer systems and networks, Vodafone will install servers on and/or will set up capacity in Vodafone or its vendor's cloud-based environment and connect to Customer’s network in order to collect endpoint, network and log data, and will provide Customer with the hardware and software components required to be installed on Customer’s network and endpoint devices. Customer will: ▪ obtain any certificates (or modify any certificates) required to enable installation of the devices or software on any network, device or endpoint; ▪ perform testing on each of its classes of devices to determine and/or confirm that the software agents do not affect reliability or availability of the devices include consent; and ▪ install th...
Project Terms. The “Intake Cycle” and “Project Term” for an Eligible BMP Activity are as follows: April 3, 2023 – January 31, 2024 April 3, 2023 – January 31, 2026 February 1, 2024 – January 31, 2025 February 1, 2024 – January 31, 2027 February 1, 2025-January 31, 2026 February 1, 2025-January 31, 2028.
Project Terms. (a) Each Core Participant is bound by the terms of the Core Participants Agreement in the conduct of this Project.
(b) Each Supporting Participant is bound by the terms of its Supporting Participants Agreement in the conduct of this Project.
(c) Without limitation to clauses 1.3(a) and 1.3(b), the CPA Clauses listed in the table below are adopted and incorporated into this Agreement as clauses of this Agreement, applicable to all Project Parties, with any necessary changes having been made:
1 Definitions and interpretation 10 Specified Personnel 11 Assets 15 Projects 16 Centre IP 17 Utilisation of Centre IP 18 Confidentiality 19 Indemnities 20 Insurance 21 Publications 22 Notices and other communications 23 Public announcements 29 Dispute resolution 30 Use of Party’s name and CRC Branding
Project Terms. As a condition of this grant and recipient of grant funds, Grantee-Contractor Urban Water Works will agree to and abide by the terms of the Memorandum of Agreement between the City of Portland Environmental Services and Portland Public Schools governing the approval, construction, and maintenance of stormwater management facilities constructed as retrofits to existing development on Portland Public Schools property. Urban Water Works will design, obtain permits for, and construct the project as described in this grant agreement. Urban Water Works will notify BES in writing within 5 business days of any changes to the design or function of the facility that results from circumstances that arise during construction, and will not implement any changes that decrease the utility of the project for stormwater management purposes without first obtaining the City’s written agreement. Urban Water Works will ensure that all volunteers sign a “Volunteer’s Agreement, Waiver of Liability, and Volunteer Injury Release Form” prior to engaging in any activities related to the project. Urban Water Works will develop and submit to BES and Portland Public Schools an Operations and Maintenance Plan (O&M) that is consistent with the O&M requirements specified in the BES Stormwater Management Manual. Urban Water Works will perform routine maintenance as described in the O&M plan through September 2010. Urban Water Works will annually submit a copy of a site Stormwater Operations and Maintenance Activities list, updated to provide information about activities that occurred over the previous year for 5 years following construction. In addition, submit a short written report summarizing any problems related to the stormwater management facilities, and changes made to address those problems. This updated O&M Activities list and report shall be submitted by August 30th of the year following execution of this agreement, and every year thereafter for 5 years (including August 30th, 2010). Urban Water Works will supply the following documentation to BES within 60 days of completion of the project: A revised final budget including all activities, materials, and labor, including in-kind contributions of material, services and labor; final project drawings (“As-Builts”) and any additional documents as required by BES or EPA.
Project Terms. As your partners, we are fully committed to the timely completion and quality delivery of each project element outlined as part of the scope. With that in mind, we believe in providing transparency on our process, payment terms and client-side expectations up front. We do this so that we can be the most efficient and effective with our collective time and project budgets in order to create the most value we can. The following section outlines details and terms of our project process. PROJECT PHASES Each project phase is limited to a total of 2 rounds, unless otherwise noted. We find that this format encourages more collaboration in the early stage of each phase and enables the exploration of all ideas. With more participation and strategic discussion up front, we are able to streamline the executional phases to deliver more speed and accuracy. Any additional rounds requested by the client, and not due to errors on SPARK’s side, will result in additional fees: • Round 1: Initial Concept, Design or Strategy Presentations, Client provides collective team feedback • Round 2: Refined Presentation, final collective feedback received from Client • Final approval: Final approval received from Client, final document(s) sent to Client upon receipt of payment PROJECT TIMING A formal project timeline will be provided to the client upon contract approval and start of the project. Ideal turnaround times for feedback are outlined below but specific deadlines will be outlined in the project timeline. Any shifts to the timeline expectations (due to early or late feedback, holidays, scheduling conflicts, etc.) will result in a shift of the overall project timeline to accommodate for changes: • Round 1 feedback: 3 business days • Round 2 feedback: 2 business days • Final approval: 1 business day CHANGE IN SCOPE/DELIVERABLES Specific deliverables have been identified as part of the recommended project scope. Once deliverables have been approved, any changes or additions to the scope will require additional cost approval and payment prior to completion. In these cases, a formal estimate will always be provided to the client. TRAVEL All travel and accommodation fees associated with any phase of the project will be billed to the client separately after securing prior approval for the expenditures. No travel and accommodation fees in excess of the per diem limits in section 112.061, Florida Statutes, shall be reimbursed. This includes but is not limited to flights, hotel accommod...
