PAST PERFORMANCE REFERENCES Sample Clauses

PAST PERFORMANCE REFERENCES. 4.2.14.1 Each Offeror is responsible for sending out the past performance survey questionnaire to at least five (5) past clients which is included as Attachment G – Reference Template.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
PAST PERFORMANCE REFERENCES. Reference 1 Client & Date of supply provided: ___________________________________________________________________ Client Phone Number: Location/Address: Contract Value (USD): Name(s) and email addresses of at least 1 contact person from the Client:
Sample 1Sample 2Sample 3See All (4)
PAST PERFORMANCE REFERENCES. The Offeror shall submit no more than two (2) past performance references from Contractor Performance Assessment Reporting System (CPARS) for itself as the prime contractor of relevant contracts in scope, magnitude of effort, and complexities with this requirement. References should be within the past three (3) years. The contracts may be past or current as long as the performance did not end more than 3 years prior to the due date for the submission of this request for proposal. If the contractor does not submit any contracts to reference, a review of CPARS will be conducted and the two (2) most recent Assessment Date entries will be reviewed. The Offeror shall list ongoing and previous Government contracts held during the past three years, which are relevant to the PWS, including: • Past performance utilizing a secure contractor-owned, -operated, and -hosted web-based electronic system that is capable of fully supporting a technical review process. • Past performance recruiting subject matter experts, to include scientists, clinicians, and consumer advocates, within timeline constraints. • Past performance in planning and executing large-scale and concurrent review meetings using various modalities. • Past performance in quality-control of high volume data and file processing and transfer to and from government systems. • Past performance with managed hosting of applications, servers and related activities including information assurance and security compliance. In addition, any and all contracts terminated for cause, in whole or in part, during the past five (5) years, to include those currently in the process of such termination are considered relevant and the Offeror shall provide past performance information for those contracts. The number of past performance references shall be limited to no more than five (5) for the prime contractor and no more than three (3) for each subcontractor. The Offeror shall provide a narrative, which explains the relevance of each of the previous efforts, with respect to the effort described in this RFP. L.4.4. VOLUME IV –SMALL BUSINESS PARTICIPATION PLAN, SMALL BUSINESS SUBCONTRACTING PLAN (if Applicable)
Sample 1Sample 2
PAST PERFORMANCE REFERENCES. On a continuation page, please provide past performance information requested in the RFA.
Sample 1
PAST PERFORMANCE REFERENCES a) Note and explain any occasion in which a contract to manage a facility has been canceled or not renewed.
Sample 1
PAST PERFORMANCE REFERENCES. On a continuation page, please provide a list of all U.S. Government and/or privately-funded contracts, grants, cooperative agreements, etc., for similar programs for the last three years and the name, address, and telephone number of the Contract/Agreement Officer or other contact person.
Sample 1

Related to PAST PERFORMANCE REFERENCES

  • Ongoing Performance Measures The Department intends to use performance-reporting tools in order to measure the performance of Contractor(s). These tools will include the Contractor Performance Survey (Exhibit H), to be completed by Customers on a quarterly basis. Such measures will allow the Department to better track Vendor performance through the term of the Contract(s) and ensure that Contractor(s) consistently provide quality services to the State and its Customers. The Department reserves the right to modify the Contractor Performance Survey document and introduce additional performance-reporting tools as they are developed, including online tools (e.g. tools within MFMP or on the Department's website).

  • Annual Performance Evaluation On either a fiscal year or calendar year basis, (consistently applied from year to year), the Bank shall conduct an annual evaluation of Executive’s performance. The annual performance evaluation proceedings shall be included in the minutes of the Board meeting that next follows such annual performance review.

  • Annual Performance Review The Employee’s performance of his duties under this Agreement shall be reviewed by the Board of Directors or a committee of the Board of Directors at least annually and finalized within thirty (30) days of the receipt of the annual audited financial statements. The Board of Directors or a committee of the Board of Directors shall additionally review the base salary, bonus and benefits provided to the Employee under this Agreement and may, in their discretion, adjust the same, as outlined in Addendum B of this Agreement, provided, however, that Employee’s annual base salary shall not be less than the base salary set forth in Section 4(A) hereof.

  • Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.

  • SCHEDULE FOR PERFORMANCE REVIEWS 8.1 The performance of each Employee in relation to his/her performance agreement shall be reviewed on the following dates with the understanding that reviews in the first and third quarter may be verbal if performance is satisfactory:

  • Performance Measurement Satisfactory performance of this Contract will be measured by:

  • Contractor Performance Evaluations The Contract Administrator will evaluate Contractor’s performance as often as the Contract Administrator deems necessary throughout the term of the contract. This evaluation will be based on criteria including the quality of goods or services, the timeliness of performance, and adherence to applicable laws, including prevailing wage and living wage. City will provide Contractors who receive an unsatisfactory rating with a copy of the evaluation and an opportunity to respond. City may consider final evaluations, including Contractor’s response, in evaluating future proposals and bids for contract award.

  • Performance Evaluations 34.1. The Contractor is subject to an annual performance evaluation to be conducted by NYCDOT pursuant to the PPB Rules.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!