7-Attachment E - Technical Criteria (1).pdf
PDF 112 KB Posted
- Attached to
- Point of Interaction (Credit Card Machines)
- Solicitation number
- CS26-18
- Issued by
- Utah
About this file
This is a Technical Criteria attachment for a Request for Proposals issued by the State of Utah Division of Purchasing, conducted by the Utah State Tax Commission, for Point of Interaction credit card machines. The RFP seeks a single contract award to provide comprehensive payment processing solutions including hardware terminals, software integration, and support services. The contract term is five years, with vendor pricing guaranteed for the first year.
Offerors must meet ten detailed technical criteria categories, including end-to-end encryption capabilities compatible with JP Morgan Chase Commerce Solutions' Safetech Enterprise Point solution; integration with purchasing entities' existing ERP and point-of-sale systems; support for EMV, swipe, and contactless payment methods including mobile wallets; provision of multi-media credit card terminals with lease and sale options; post-sales project management and implementation support; ongoing maintenance and hardware warranty; current annual PCI Attestation of Compliance documentation and PA-DSS, PTS, and P2PE compliance; secure remote terminal management tools that do not impact PCI scope; and tokenization capabilities for card storage. All proposals must provide point-by-point responses addressing each criterion in detail, demonstrating the offeror's capability to deliver a complete solution that reduces PCI scope for purchasing entities while maintaining security standards.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 4-Attachment B - Scope of Work.pdf | ||
| 8-Evaluator Score Sheet.xls | XLS spreadsheet | |
| 6-Attachment D - Price List (1).pdf | ||
| 5-Attachment C - Cost Proposal Form (2).xlsx | XLSX spreadsheet | |
| 2-Vendor Prerequisites - RFP Agency.pdf | ||
| 1-Claim of Business Confidentiality Updated.pdf.pdf | ||
| 3-Att.-A-Agency-Terms-and-Conditions-GS (9).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
Attachment E
Technical Criteria
For ease of evaluation, the proposals must provide a point-by-point response, addressing in detail each area of the evaluation criteria, including addressing how the point-by-point response addresses the issues discussed in this RFP. The criteria are not intended to limit a proposal's content or exclude any relevant or essential data. Offerors are at liberty and are encouraged to expand upon the criteria to demonstrate the Offeror’s capability to provide the State with a solution.
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.
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.
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.
4. Single Offeror Solution: Offeror to submit a detailed description of how they
a. Solution must be provided by a single Offeror or established hardware software partnership.
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.
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.
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.
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.
9. Remote Terminal Tools: Offeror to submit a detailed description of how they
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. 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.
File details come from the government source that posted it. Updated .