6-Points of Interaction Score Sheet.xls
XLS spreadsheet 49 KB Posted
- Attached to
- Points of Interaction (Credit Card Machines)V2
- Solicitation number
- TJ25-25
- Issued by
- Utah
About this file
This is a Score Sheet for a Request for Proposal (RFP) issued by the State of Utah Division of Purchasing, solicitation number BB23-4(TJ25-25), seeking a statewide contract for Point of Sale (POS) Hardware & Software with Points of Interaction (Credit Card Machines). The contract will run from the date of full execution to November 30, 2028, and may result in multiple awards. Vendors must meet mandatory minimum requirements, including providing a PCI-compliant end-to-end encryption solution with hardware and software applications, partner relationships with acquiring banks, and capabilities for custom data fields, transaction reporting, and dispute management.
The evaluation process involves a two-stage scoring methodology, with a total of 1,000 possible points divided into 70% technical evaluation (700 points) and 30% cost evaluation (300 points). Vendors must achieve a minimum technical score of 420 points out of 700 to advance to the cost evaluation stage. Cost points will be calculated using a formula that awards the maximum points to the lowest-cost vendor, with other vendors receiving proportional points. The final award will be made to vendors scoring a minimum of 650 points, with the lowest-priced vendor receiving the most favorable cost evaluation. No administrative fee is associated with this contract.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 2-Attachment B - Scope of Work.pdf | ||
| 3-Attachment C - Cost Proposal Form.xlsx | XLSX spreadsheet | |
| 5-Attachment E - Technical Criteria.docx | DOCX document | |
| 10-Disposition of RFP TJ25 Bonfire posting.docx | DOCX document | |
| 8-Vendor Prerequisites - Statewide RFP.pdf | ||
| 9-Submission Instructions - TJ25-25.docx | DOCX document | |
| 7-Att A Statewide IT Terms and Conditions.docx | DOCX document | |
| 4-Attachment D - Price List.docx | DOCX document | |
| 1-Claim of Business Confidentiality Updated.pdf.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Score Sheet
| ***FYI ONLY - DO NOT COMPLETE THIS FORM*** | |||||||||
| RFP Scoresheet | |||||||||
| Points Of Interaction (Credit Card Machines) | |||||||||
| SOLICITATION #BB23-4(TJ25-25) | |||||||||
| RFP EVALUATION SCORESHEET | |||||||||
| Score will be assigned as follows: | |||||||||
| 0 = Fail, the proposal fails to address the requirements or criteria described in the RFP or cannot be assessed du to missing information | |||||||||
| Firm Name: | 1 = Poor, the proposal inadequately addresses the requirements or criteria described in the RFP or cannot be assessed due to incomplete information | ||||||||
| 2 = Unsatisfactory, the proposal addresses the requirements or criteria described in the RFP in an unsatisfactory manner | |||||||||
| Evaluator: | 3 = Satisfactory, the proposal addresses all requirements or criteria described in the RFP in a minimum satisfactory manner | ||||||||
| 4 = Good, the proposal addresses all requirements or criteria described in the RFP and in some respects exceeds them | |||||||||
| Date: | 5 = Excellent, the proposal addresses and exceeds all of the requirements or criteria described in the RFP | ||||||||
| Minimum Mandatory Requirements | RFP Section | Evaluation (Pass/Fail) | |||||||
| 1 | Offeror must provide a PCI compliant E2EE solution. | PASS | |||||||
| 2 | Offeror must provide a solution including both hardware and software applications. | PASS | |||||||
| 3 | Offeror's solution must not be stand-alone. | PASS | |||||||
| 4 | Offeror must have a partner relationship with acquiring banks / payment processors. A partner relationship is one in which the offeror will have a secure communication and/or direct connection to the bank. Please specify your partner relationships with acquiring banks / payment processors. | PASS | |||||||
| 5 | Offeror must be able to accept a 26 character custom data field from cashiering systems and credit card readers that will become part of the transaction data for later download. | PASS | |||||||
| 6 | Offeror must provide daily downloadable reports showing all credit card transaction activity for each merchant account including the custom data field for reconciliation purposes. | PASS | |||||||
| 7 | Offeror must be able to charge separate credit card fees for each merchant account on a monthly basis. | PASS | |||||||
| 8 | Offeror must be able to provide a monthly statement for each merchant account that provides: counts of transactions by card type, detailed fees by card type, chargebacks, etc. | PASS | |||||||
| 9 | Offeror must provide online dispute/chargeback management that makes it possible to identify exactly which transaction is being disputed and/or charged back. | PASS | |||||||
| 10 | Offeror must upload a completed BB23-4 Attachment C - Cost Proposal form | PASS | |||||||
| 11 | Offeror must upload their response to Attachment E - Technical Criteria | PASS | |||||||
| Proceed to Scoring | |||||||||
| Scoreable Technical Criteria | RFP Section | Evaluator Score (0-5) | Criteria Weight | % of Tech Criteria | Points Possible | Points | |||
| Earned | Minimum Required | ||||||||
| 1 | Provide End to End Encryption: Offeror to submit a detailed description of how they will meet the following requirements. |
a. Offeror solution must provide a complex encryption algorithm for end-to-end encryption.
b. Offeror must be able to encrypt at swipe/ dip/ tap and maintain encryption all the way to the payment processor.
| c. Must be compatible with JP Morgan Chase Commerce Solutions’ Safetech Enterprise Point solution, must be a PCI P2PE solution. | 15 | 10.7% | 75.0 | 0.0 | ||
| 2 | Enable Integration to a Purchasing Entity's ERP/ Point of Sale System: Offeror to submit a detailed description of how they will meet the following requirements. |
a. Offeror must be able to load software that provides semi-integration to point-of-sale software or ERP used by the Purchasing Entity. Semi-integration means that only limited communication between the ERP/POS is allowed as described in 2(c).
b. Offeror software must be deployable on Purchasing Entity owned/ leased terminal hardware.
c. Offeror software must be able to communicate awake and authorization with the point-of-sale system on the local PC without bringing that PC or the point of sale software into PCI scope.
| d. Offeror must provide testing and certification of integration. | 15 | 10.7% | 75.0 | 0.0 | ||
| 3 | EMV, Swipe, Contactless: Offeror to submit a detailed description of how they will meet the following requirements. |
a. Offeror solution must be EMV ready.
| b. Offeror solution must accept full array of common RFID and NFC contactless. solutions including, but not limited to: tap and go, mobile wallets, Android Pay, Apple Pay, Samsung Pay. | 10 | 7.1% | 50.0 | 0.0 | ||
| 4 | Single Offeror Solution: Offeror to submit a detailed description of how they will meet the following requirements. | |||||
| a. Solution must be provided by a single Offeror or established hardware software partnership. | 10 | 7.1% | 50.0 | 0.0 | ||
| 5 | Hardware Solutions: Offeror to submit a detailed description of how they will meet the following requirements. |
a. Offeror must provide multi-media credit card terminals.
b. Offeror may also supply configurable key-in and/or SRED devices (if devices meet other listed requirements).
c. Offeror must load payment application software.
d. Offeror must inject debit and end-to-end encryption keys.
| e. Offeror must provide both lease and sale options. | 20 | 14.3% | 100.0 | 0.0 | ||
| 6 | Project Management / Sales Support: Offeror to submit a detailed description of how they will meet the following requirements. |
a. Offeror must provide post sales project management through full implementation.
b. Offeror project management must be coordinated with the Purchasing Entity.
| c. Offeror must provide necessary engineering and product support as needed by the Purchasing Entity. | 15 | 10.7% | 75.0 | 0.0 | ||
| 7 | Ongoing Maintenance and Support: Offeror to submit a detailed description of how they will meet the following requirements. |
a. Offeror must warranty hardware.
b. Application/ Software licenses must cover patches, upgrades and other technical support.
| c. Offeror must provide hardware maintenance including, but not limited to: replacement parts, tampered device replacement or rebuild. | 15 | 10.7% | 75.0 | 0.0 | ||
| 8 | PCI Compliance: Offeror to submit a detailed description of how they will meet the following requirements. |
a. Offeror must provide a current PCI AOC for service providers annually.
b. Offeror hardware and applications must maintain PCI compliance including PA-DSS, PTS, and P2PE as applicable.
| c. Offeror must provide documentation describing how the solution may reduce PCI scope for Purchasing Entities. | 20 | 14.3% | 100.0 | 0.0 | ||
| 9 | Remote Terminal Tools: Offeror to submit a detailed description of how they will meet the following requirements. |
a. Offeror must have a tool that will allow IT staff to remotely update and manage certain application components of the terminals.
| b. The remote terminal tool must not affect PCI scope and must be secure from unauthorized access. | 10 | 7.1% | 50.0 | 0.0 | ||||||||
| 10 | Tokenization: Offeror to submit a detailed description of how they will meet the following requirements. | |||||||||||
| a. Offeror solution must provide token responses for card storage requirements. | 10 | 7.1% | 50.0 | 0.0 | ||||||||
| 100.0% | 700.0 | 0.0 | 0.0 | |||||||||
| Required Technical Point Threshold | RFP Section | Min Percent | Min Points Required | Points Earned | Percent Earned | Evaluation | ||||||
| 60% | 420.0 | 0.0 | 0.0% | 0 | ||||||||
| Cost | RFP Section | Low Cost Option | Offered Cost | Percent of Total | Points Possible | Points Earned | ||||||
| 1 | Scenario 1 - Purchase 10 Points of Interaction Machines | 5% | 50.0 | 0.0 | ||||||||
| 2 | Scenario 2 - Lease 10 Points of Interaction Machines | 5% | 50.0 | 0.0 | ||||||||
| 3 | Scenario 3 - Purchase 100 Points of Interaction Machines | 5% | 50.0 | 0.0 | ||||||||
| 4 | Scenario 4 - Lease 100 Points of Interaction Machines | 5% | 50.0 | 0.0 | ||||||||
| 5 | Scenario 5 - Purchase 350 Points of Interaction Machines | 5% | 50.0 | 0.0 | ||||||||
| 6 | Scenario 6 - Lease 350 Points of Interaction Machines | 5% | 50.0 | 0.0 | ||||||||
| * Purchasing will use the following cost formula: The points assigned to each offerors cost proposal will be based on the lowest proposal price. The offeror with the lowest Proposed Price will receive 100% of the price points. All other offerors will receive a portion of the total cost points based on what percentage higher their Proposed Price is than the Lowest Proposed Price. The formula to compute the points is: Cost Points x (Lowest Proposed Price/Proposed Price). | ||||||||||||
| Total Evaluation Points | Percent of Total | Points Possible | Points Earned | |||||||||
| Total Technical Evaluation Points | 70% | 700.0 | 0.0 | |||||||||
| Total Cost Evaluation Points | 30% | 300.0 | 0.0 | |||||||||
| Total Evaluation Points | 100% | 1,000.0 | 0.0 |
File details come from the government source that posted it. Updated .