Request for Proposal for Desktop and Laptop Computer System Sample Clauses

POPULAR SAMPLE Copied 5 times
Request for Proposal for Desktop and Laptop Computer System. Having examined the Proposal Documents, the receipt of which is hereby duly acknowledged, we, the undersigned, offer to supply and deliver Hardware/Software, in conformity with the said Proposal documents for the sum of including Tax (Total Proposal amount in figures and words) or such other sums as may be ascertained in accordance with the Schedule of Price attached herewith and made part of this proposal. We undertake, if our Proposal is accepted, to deliver, install and commission the system in accordance with the delivery schedule specified in Clause 9 of Annexure C.
View Source
Request for Proposal for Desktop and Laptop Computer System. Having examined the Proposal Documents, the receipt of which is hereby duly acknowledged, we, the undersigned, offer to supply and deliver Hardware/Software, in conformity with the said Proposal documents. We undertake, if our Proposal is accepted, to deliver, install and commission the system in accordance with the delivery schedule specified in Clause 9 of Annexure C. Until a formal contract is prepared and executed, this Proposal, together with your written acceptance thereof and your notification of award, shall constitute a binding Contract between us. We undertake that, in competing for (and, if the award is made to us, in executing) the above contract, we will strictly observe the laws against fraud and corruption in force in India namely “Prevention of Corruption Act, 1988”. We understand that you are not bound to accept the lowest or any Proposal you may receive.
View Source

Related to Request for Proposal for Desktop and Laptop Computer System

  • Information Sources The Custodian may rely upon information received from issuers of Investments or agents of such issuers, information received from Subcustodians and from other commercially reasonable sources such as commercial data bases and the like, but shall not be responsible for specific inaccuracies in such information, provided that the Custodian has relied upon such information in good faith, or for the failure of any commercially reasonable information provider.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information.

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Software Ownership If Contractor develops or pays to have developed computer software exclusively with funds or proceeds from the Contract to perform its obligations under the Contract, or to perform computerized tasks that it was not previously performing to meet its obligations under the Contract, the computer software shall be exclusively owned by or licensed to the Department. If Contractor develops or pays to have developed computer software which is an addition to existing software owned by or licensed exclusively with funds or proceeds from the Contract, or to modify software to perform computerized tasks in a manner different than previously performed, to meet its obligations under the Contract, the addition shall be exclusively owned by or licensed to the Department. In the case of software owned by the Department, the Department grants to Contractor a nontransferable, nonexclusive license to use the software in the performance of the Contract. In the case of software licensed to the Department, the Department grants to Contractor permission to use the software in the performance of the Contract. This license or permission, as the case may be, terminates when Contractor has completed its work under the Contract. If Contractor uses computer software licensed to it which it does not modify or program to handle the specific tasks required by the Contract, then to the extent allowed by the license agreement between Contractor and the owner of the software, Contractor grants to the Department a continuing, nonexclusive license for either the Department or a different contractor to use the software in order to perform work substantially identical to the work performed by Contractor under the Contract. If Contractor cannot grant the license as required by this section, then Contractor shall reveal the input screens, report formats, data structures, linkages, and relations used in performing its obligations under the contract in such a manner to allow the Department or another contractor to continue the work performed by contractor under the Contract.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 WCS shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.