Installed Capacity and Performance Security
Installed Capacity and Performance Security Sample Clauses
Related to Installed Capacity and Performance Security
Payment and Performance Bond Prior to the execution of this Contract, City may require Contractor to post a payment and performance bond (Bond). The Bond shall guarantee Contractor’s faithful performance of this Contract and assure payment to contractors, subcontractors, and to persons furnishing goods and/or services under this Contract.
Payment and Performance Bonds The Contractor shall comply with the following minimum bonding requirements:
DELIVERY AND PERFORMANCE All work performed under contracts or task orders will be at the highest quality applicable and delivered according to Statement of Objectives (SOO), Statement of Works (SOW), or Performance Work Statements (PWS). The Contractor must deliver and perform according to the requirements of the contract or task order, and may be denied further work for substandard performance. The Government may include deliveries or performance requirements, such as (1) optional clauses, (2) agency clauses, or (3) specific clauses, in a contract or task order.
COMPLIANCE AND PERFORMANCE EVALUATION Two (2) Mandatory Compliance and Performance Evaluation Meetings shall be conducted during each Term of this Agreement. Additional meetings may be scheduled at the discretion of Department to ensure Concessionaire’s effectiveness and compliance. The meetings shall review all aspects of the Concession Operation, ensuring that quality public services are being provided on a continuing basis in accordance with the Bid Specifications and this Agreement, that operational problems/concerns are addressed on a timely basis, and that all terms and conditions are clearly understood. The meetings shall be held on site with Department-designated State Park Service staff representative(s), the on-site concession manager, and a management/supervisory representative of Concessionaire’s firm. A report form shall be utilized to document the meeting, and to identify any deficiencies and the corrective action required. A copy of the completed report form shall be provided to the on- site concession manager or the management/supervisory representative of Concessionaire’s firm and shall be attached to and made a part of this Agreement. The Mandatory Compliance and Performance Evaluation Meetings shall be held as follows: • Meeting #1 - Prior to commencement of the Period of Operation or Memorial Day, whichever comes first. • Meeting #2 - Within ten (10) calendar days after the last approved day of the Period of Operation.
Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as: (A) line-side facilities, which include, but are not limited to, the connection between a loop termination at a main distribution frame and a switch line card; (B) trunk-side facilities, which include, but are not limited to, the connection between trunk termination at a trunk-side cross-connect panel and a switch trunk card; (C) switching provided by remote switching modules; and (D) all features, functions, and capabilities of the switch, which include, but are not limited to: (1) the basic switching function of connecting lines to lines, line to trunks, trunks to lines, and trunks to trunks, as well as the same basic capabilities made available to BellSouth’s customers, such as a telephone number, white page listings, and dial tone; and (2) all other features that the switch is capable of providing, including but not limited to customer calling, customer local area signaling service features, and Centrex, as well as any technically feasible customized routing functions provided by the switch. Any features that are not currently available but are technically feasible through the switch can be requested through the BFR/NBR process.
Registry Performance Specifications Registry Performance Specifications for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.
System Security (a) If any party hereto is given access to the other party’s computer systems or software (collectively, the “Systems”) in connection with the Services, the party given access (the “Availed Party”) shall comply with all of the other party’s system security policies, procedures and requirements that have been provided to the Availed Party in advance and in writing (collectively, “Security Regulations”), and shall not tamper with, compromise or circumvent any security or audit measures employed by such other party. The Availed Party shall access and use only those Systems of the other party for which it has been granted the right to access and use.
