Functional Performance Requirements of the System Sample Clauses

Functional Performance Requirements of the System. 1.2.1 [ describe, at the appropriate level of detail for the particular System being supplied and installed: the relevant throughput and/or response times for specific business processes and procedures automated by the System; also describe: in business process terms, the relevant conditions under which the System must achieve these performance standards (e.g., the number of concurrent users, type of transactions, type and quantity of business data that the System must process in achieving these performance standards, etc.) ] Note: As indicated above, performance requirements in business function terms are less critical for many of the Systems to be procured using the single-stage bidding process. Nevertheless, whenever feasible, business functions should be stated and used as the basis for performance specifications. Relying solely on technological requirements can inadvertently restrict competition.
Sample 1
AutoNDA by SimpleDocs
Functional Performance Requirements of the System 
Sample 1Sample 2

Related to Functional Performance Requirements of the System

  • Performance Requirements 1. Neither Party may impose or enforce any of the following requirements, or enforce any commitment or undertaking, in connection with the establishment, acquisition, expansion, management, conduct or operation of an investment of an investor of a Party or of a non-Party in its territory:

  • Service Requirements Grantee shall:

  • Service Requirement Except as otherwise provided in Section 6(e) of the Plan or Section 2 of this Agreement, this Option may be exercised only while you continue to provide Service to the Company or any Affiliate, and only if you have continuously provided such Service since the Grant Date of this Option.

  • Maintenance Requirements The Contractor shall ensure and procure that at all times during the Maintenance Period, the Project Highway conforms to the maintenance requirements set forth in Schedule-E (the “Maintenance Requirements”).

  • Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.

  • Service Levels Annex 1 to this Part A of this Call Off Schedule sets out the Service Levels the performance of which the Parties have agreed to measure. The Supplier shall monitor its performance of this Call Off Contract by reference to the relevant performance criteria for achieving the Service Levels shown in Annex 1 to this Part A of this Call Off Schedule (the Service Level Performance Criteria) and shall send the Customer a Performance Monitoring Report detailing the level of service which was achieved in accordance with the provisions of Part B (Performance Monitoring) of this Call Off Schedule. The Supplier shall, at all times, provide the Services in such a manner that the Service Levels Performance Measures are achieved. If the level of performance of the Supplier of any element of the provision by it of the Services during the Call Off Contract Period: is likely to or fails to meet any Service Level Performance Measure or is likely to cause or causes a Critical Service Failure to occur, the Supplier shall immediately notify the Customer in writing and the Customer, in its absolute discretion and without prejudice to any other of its rights howsoever arising including under Clause 12 of this Call Off Contract (Service Levels and Service Credits), may: require the Supplier to immediately take all remedial action that is reasonable to mitigate the impact on the Customer and to rectify or prevent a Service Level Failure or Critical Service Level Failure from taking place or recurring; and if the action taken under paragraph (a) above has not already prevented or remedied the Service Level Failure or Critical Service Level Failure, the Customer shall be entitled to instruct the Supplier to comply with the Rectification Plan Process; or if a Service Level Failure has occurred, deduct from the Call Off Contract Charges the applicable Service Level Credits payable by the Supplier to the Customer in accordance with the calculation formula set out in Annex 1 of this Part A of this Call Off Schedule; or if a Critical Service Level Failure has occurred, exercise its right to Compensation for Critical Service Level Failure in accordance with Clause 13 of this Call Off Contract (Critical Service Level Failure) (including subject, for the avoidance of doubt, the proviso in Clause 13.1.2 of this Call Off Contract in relation to Material Breach). Approval and implementation by the Customer of any Rectification Plan shall not relieve the Supplier of any continuing responsibility to achieve the Service Levels, or remedy any failure to do so, and no estoppels or waiver shall arise from any such Approval and/or implementation by the Customer. SERVICE CREDITS Annex 1 to this Part A of this Call Off Schedule sets out the formula used to calculate a Service Credit payable to the Customer as a result of a Service Level Failure in a given service period which, for the purpose of this Call Off Schedule, shall be a recurrent period of [one Month] during the Call Off Contract Period (the Service Period).

  • Disclosure to numbering service providers (a) Any Finance Party may disclose to any national or international numbering service provider appointed by that Finance Party to provide identification numbering services in respect of this Agreement, the Facility and/or one or more Obligors the following information:

  • Performance Reporting The State of California is required to submit the following financial reports to FEMA:

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