Project Specific Assumptions Sample Clauses

The Project Specific Assumptions clause defines the particular conditions, expectations, or circumstances that are presumed to be true for the successful execution of a specific project. This clause typically lists assumptions about resources, timelines, client responsibilities, or external factors that may impact project delivery. For example, it may state that certain permits will be obtained by a set date or that client-provided data will be accurate and complete. By clearly outlining these assumptions, the clause helps prevent misunderstandings and disputes by ensuring all parties are aware of the foundational premises upon which the project plan is based.
Project Specific Assumptions. Client understands and agrees that, in connection with the delivery of ThreatZero Services, Cylance will need access and use the Software on Client’s behalf and that such access and use may result in access, use and manipulation of Client systems, network and infrastructure, and that Cylance may operate the Software, retrieve data or otherwise connect with Client’s network on Client’s behalf to implement and tune the Software per Client instruction and as agreed by the parties in order to perform ThreatZero Services.
Project Specific Assumptions. Clark County determines that because this is a repair project that they will not require a SEPA checklist.
Project Specific Assumptions. The estimated duration and associated fees presented in this SOW are based on the following assumptions. Should any element(s) of these be lacking during execution of the Services, additional time, associated fees, and expenses may be required. 1. This Statement of Work constrains activities to an approximate 10-week duration. 2. Azure scaffolding and governance is sufficiently mature to support the objectives and design approach as enumerated herein. 3. This engagement does not include development tool licenses (i.e., Visual Studio), database, third-party product and application server licenses. 4. If applicable, any onsite skills transfer that takes place during this project will not replace the manufacturer’s formal system implementation and administration classes. 5. Insight has no obligation to mount, affix, or otherwise fasten any cable, hardware, or other product to any building or structure (inside or outside), and Insight has no obligation to run cable above, under, behind, or through any ceiling, floor, or wall of any building or structure. If such services are requested by Client, such services may be performed by Insight only to the extent permitted by applicable law and will be subject to a Change Request for additional services. 6. Each party agrees that personnel will not be asked to perform, nor volunteer to perform, engineering and/or consulting tasks that lie outside the skill sets and experience of personnel. Personnel have the right to decline a service request if the request falls outside their scope of experience and expertise. a. Electrical or cabling services b. Formal user training
Project Specific Assumptions. The estimated duration and associated fees presented in this SOW are based on the following assumptions. Should any element(s) of these be lacking during execution of the Services, additional time, associated fees, and expenses may be required. 1. Project estimates assume the following: a. Content moderation of videos ingested by the target solution is the responsibility of the ▇▇▇▇▇▇ ▇. Videos to be encoded and analyzed by the target solution will be pulled using an automated method from a secured location in the vendors environment c. Workshop session dates and calendar invitations for attendees will be confirmed prior to start of engagement d. This SOW assumes Client has Azure tenant and all related licenses established with any funding related to the engagement in place 2 weeks prior to the engagement e. Client’s current infrastructure is healthy and meets the minimal requirements for the engagement f. Unsupported hardware and software will be the responsibility of Client g. Installation or configuration of any Client-related applications are out of scope of this engagement except where specifically called out as in scope h. Existing network connectivity is sufficient to support engagement activities and to support Client security requirements i. Client’s Azure cloud scaffolding is sufficiently configured and mature to support the SOW objectives j. Any infrastructure software tools, services, and licenses required to execute project will be arranged by Client excluding any tools provided by Insight in tools section k. User communication and training on any end user readiness / post engagement steps will be handled by Client IT team l. Any delays in approval or availability of systems and access will impact the estimated timelines and may result in a change order m. Any change in the assumptions as detailed under this SOW may impact the overall timelines may result in a change order n. Data received from Client will be timely and accurate 2. This engagement does not include development tool licenses (i.e., Visual Studio), database, third party product and application server licenses. 3. If applicable, any onsite skills transfer that takes place during this project will not replace the manufacturer’s formal system implementation and administration classes. 4. Insight has no obligation to mount, affix, or otherwise fasten any cable, hardware, or other product to any building or structure (inside or outside), and Insight has no obligation to run cable abov...
Project Specific Assumptions. The functional scope of this project is detailed in the document, “Solution Overview.” • The Project Timeline and Implementation strategy are specified in the project schedule and the staffing matrix. • The proposal includes on-site training (train-the-trainers) and Open Academy (virtual platform) is available at no additional cost. • The provisioning configuration services, were estimated assuming that three (3) platforms will be configured including network electronics, video and phone. The City must provide the documentation and specifications. Such information is relevant to determine the configuration of the Software and the modules that need to be used for the integration with the platforms. Open developed the project timeline assuming the required documentation would be available three (3) weeks prior to the project start date. The Parties agree that the Customer will provide this information as it becomes available. The Customer also acknowledges Open has requested the City provide the sandbox platform connections at the beginning of the first month of the project and the acceptance platforms at the beginning of the fifth month of the project. The City will provide the sandbox platform as it becomes available. If the information, sandbox environments or acceptance platforms are not available to Open in the abovementioned timeframes, once the information, sandbox environments or acceptance platforms are available, Open will evaluate any impact to the project and inform the Customer within ten (10) business days. In such event, Open will initiate a change request in accordance with Section 6 of the MPSA for discussion and mutual agreement by the Parties. Nevertheless, Open will make best efforts to mitigate any impact to the project. • One month after the project starts, all the definitions corresponding to the Broadband platforms must be closed and delivered to the Open project team. • Open has assumed typical scenarios for the system configuration and professional services estimation. • It’s estimated one thousand and seven hundred (1,700) hours for reports • Two thousand (2.000) hours are estimated to address regulatory requirements. • From the contract approval and the go-live process, Open has included the services described in the support and maintenance agreement. After go-live, the City must sign a new agreement. • For deliverable signoff, the responsible party for deliverables will inform the approval party that it’s complete. The approval p...
Project Specific Assumptions. The estimated duration and associated fees presented in this SOW are based on the following assumptions. Should any element(s) of these be lacking during execution of the Services, additional time, associated fees, and expenses may be required. 1. Insight will have no responsibility for the performance of ▇▇▇▇’s other contractors, subcontractors or vendors or for delays caused by them, in connection with the Services. 2. Any changes to the scope and/or assumptions will require joint written approval, which such changes shall be governed by the Change Order Procedure set forth in the Agreement. This may extend the duration of the engagement and/or require additional resources, resulting in additional cost to OCIO. 3. Each Party agrees that personnel of either Party will not be asked to perform, nor volunteer to perform, engineering and/or consulting tasks that lie outside scope of Insight’s Proposal and State’s Request for Proposal. Personnel have the right to decline a service request if the request falls outside the scope of the Agreement, RFP, Vendor’s Response, or applicable Special Terms and Conditions or other corresponding attachments, addenda, exhibits, schedules and Special Terms and Conditions of or related to the Agreement.
Project Specific Assumptions. The estimated duration and associated fees presented in these Program Terms are based on the following assumptions. Should any element(s) of these be lacking during execution of the Services, additional time, associated fees, and expenses may be required, which such changes shall be governed by the Change Order Procedure set forth in the Agreement. 1. Insight has no obligation to, and will not, install, mount, affix, screw, or otherwise fasten any cable, hardware, or other product to any building or structure (inside or outside) of or belonging to the State of Iowa in connection with the Services. Further, Insight has no obligation to, and will not, run cable above, under, behind, or through any ceiling, floor, or wall of any building or structure of or belonging to the State of Iowa in connection with the Services. To the extent that any such construction-type services are required, such services will be performed by another person or entity engaged directly by Client. 2. Any changes to the scope and/or assumptions will require joint written approval. This may extend the duration of the engagement and/or require additional resources, resulting in additional cost to Client. 3. Each Party agrees that personnel of either Party will not be asked to perform, nor volunteer to perform, engineering and/or consulting tasks that lie outside scope of Insight’s Proposal and State’s Request for Proposal. Insight Program Manager has the right to decline a Service request if the request falls outside the scope of the Agreement
Project Specific Assumptions. 4 • CONTRACTOR will provide the solution on the emerging release (example: 2012.01) 5 and all future releases.

Related to Project Specific Assumptions

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones: 6.1 Substantial Site work completed. On or before July 1, 2021, Interconnection Customer must demonstrate completion of at least 20% of project site construction. At this time, Interconnection Customer must submit to Interconnected Transmission Owner and Transmission Provider initial drawings, certified by a professional engineer, of the Customer Interconnection Facilities. 6.2 Delivery of major electrical equipment. On or before July 15, 2021, Interconnection Customer must demonstrate that all generating units have been delivered to Interconnection Customer’s project site.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • ESTIMATED / SPECIFIC QUANTITY CONTRACTS Estimated quantity contracts, also referred to as indefinite delivery / indefinite quantity contracts, are expressly agreed and understood to be made for only the quantities, if any, actually ordered during the Contract term. No guarantee of any quantity is implied or given. With respect to any specific quantity stated in the contract, the Commissioner reserves the right after award to order up to 20% more or less (rounded to the next highest whole number) than the specific quantities called for in the Contract. Notwithstanding the foregoing, the Commissioner may purchase greater or lesser percentages of Contract quantities should the Commissioner and Contractor so agree. Such agreement may include an equitable price adjustment.

  • Product Specific Terms these terms apply to specific Products referenced in this section.