Project Specific Assumptions Sample Clauses

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.
Sample 1Sample 2
AutoNDA by SimpleDocs
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.
Sample 1Sample 2
Project Specific Assumptions. 4 • CONTRACTOR will provide the solution on the emerging release (example: 2012.01) 5 and all future releases.
Sample 1
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.
Sample 1
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...
Sample 1

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:

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-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.

  • Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.

  • 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.

  • Product Specifications The Company agrees that all Products sold to Xxxx hereunder shall conform to the respective specifications set forth on Schedule A or to such other specifications as are from time to time agreed upon by the Parties.

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

Time is Money Join Law Insider Premium to draft better contracts faster.