15-Amendment No. 03.pdf
PDF 393 KB Posted
- Attached to
- Photo and ID Card
- Solicitation number
- 696-BF-26-O033
- Issued by
- Texas
About this file
This is Amendment No. 3 to a solicitation issued by the Texas Department of Criminal Justice (TDCJ) for a Photo and ID Card solution. The amendment provides responses to 18 clarification questions submitted by potential respondents. The solicitation (696-BF-26-O033) seeks a contractor to provide, by lease, a comprehensive photo and ID card system capable of producing digitally printed color identification cards for both TDCJ employees and inmates, as well as storing and retrieving black-and-white mug shots of inmates, preferably utilizing a web-based solution. The response opening date and time is October 2, 2026, at 3:00 p.m. Respondents are required to acknowledge receipt of this amendment in their submissions. The contract will involve integration with TDCJ's physical access control system (PACS) utilizing RFID cards, multi-factor authentication (MFA) for logical access to agency systems, and employee credentials serving as unified identity credentials for both physical and logical access. The solution must be compatible with future facial recognition technology and capable of integrating with a planned replacement Inmate Management System (IMS) hosted in a CJIS-compliant environment.
Key technical clarifications in this amendment address the contractor's middleware layers and badge printing software capabilities, the optional nature of facial recognition technology, and the approximate user population of 40,000 for the Ping AIC deployment. The 250 hours of included programming referenced in the solicitation applies across the entire contract term rather than annually. The Department confirmed that archives refer to historical system records and audit/log files maintained in the MS SQL Server database housed in Azure Cloud. Regarding post-contract ownership, the vendor will retain ownership of the SaaS solution following contract expiration, while TDCJ will only own agency data. The amendment clarifies that service level agreements (SLAs) of four hours are mandatory requirements with no flexibility, and that detailed information regarding current systems and software names will not be provided; respondents must propose solutions based solely on the stated solicitation requirements. No second question-and-answer phase will be granted beyond this amendment.
View the file
Other files
Show all 14
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
T e x a s D e p a r t m e n t o f C r i m i n a l J u s t i c e
Bobby Lumpkin Executive Director
Contracts and Procurement Department
AMENDMENT No. 3
SOLICITATION NO.: 696-BF-26-O033
PURCHASER / CONTRACT SPECIALIST: Robbie Tucker RESPONSE OPENING DATE &TIME: 10/02/2026 at 03:00 p.m.
The purpose of this amendment is to:
1. Provide Response to Clarification Questions.
Reference attached pages of this amendment.
IN THE SUBMISSION OF RESPONSES, RESPONDENT MUST ACKNOWLEDGE
RECEIPT OF THIS AMENDMENT; OTHERWISE, RESPONSE MAY NOT BE GIVEN
CONSIDERATION. RESPONDENT MAY ACKNOWLEDGE RECEIPT ON FACE OF
RESPONSE OR BY RETURNING ONE COPY OF THIS NOTICE.
SIGNED:
RESPONDENT
COMPANY NAME:
Our mission is to provide public safety, promote positive change in offender behavior, reintegrate offenders into society, and assist victims of crime.
2 Financial Plaza, Suite 703
Huntsville, Texas 77340
(936) 437-3885 www.tdcj.texas.gov
Amendment No.3 Bid No.: 696-BF-26-O033
Response to Clarification Questions
Question
No.
Question
Answer
1 We are committed to providing a comprehensive and high-quality response that fully addresses your requirements.
Due to [brief reason, if appropriate], we would respectfully request consideration of an extension to the proposal submission deadline from September 17th to October 1st.
Refer to Amendment No. 2.
2 We respectfully request consideration of an extension to the proposal submission deadline from September 17th to October 17th.
Refer to Amendment No. 2.
3 Do you have any middleware layers utilizing specific APIs to print with your current badge printing software?
Yes.
4 Does the solution require the inclusion of facial recognition, or is that a technology that will be added later?
Per Sections C.4.G and C.7.3.A.11, the software shall be compatible with facial recognition technology, which may be added later.
5 Please define TDCJ's planned PACS architecture and intended use of the DESFire credential.
The Department’s planned PACS architecture includes RFID cards for building access. The MFA will be utilized to access agency systems. The use of DESFire will be determined at a later date.
6 Please identify the current and planned Ping AIC deployment architecture and expected user population.
The current and planned Ping AIC deployment architecture is proprietary, but will be provided to the awarded contractor. The user population is approximately 40,000.
(936) 437-3885 www.tdcj.texas.gov
7 Please provide details on the future IMS replacement project and anticipated integration timeline.
The Department is currently evaluating replacement options for its Inmate Management System (IMS).
At this time, the Department cannot provide additional planning assumptions regarding an anticipated integration timeline.
8 Please clarify whether the 250 hours of included programming applies per year or across the entire contract term.
The 250 hours of programming referenced in Section C.7.4.I are for the life of the contract.
9 TDCJ requires employee credentials to support both FIDO2/WebAuthn logical access and future PACS enrollment utilizing DESFire-based technology. Can TDCJ confirm whether the intent is for the employee credential to serve as a unified identity credential supporting both physical and logical access throughout the contract term?
Yes, the employee credential will serve as a unified identity credential for both physical and logical designated access throughout the contract term.
10 The solicitation notes TDCJ's planned replacement of the current inmate management environment. Can TDCJ provide planning assumptions regarding the anticipated timeline, target architecture, and preferred integration approach respondents should consider during solution design?
At this time, the Department cannot provide additional planning assumptions regarding implementation timeline, target architecture, or integration methodology beyond the information contained in this Solicitation. Respondents should propose solutions capable of integrating with a future IMS solution hosted in a CJIS-compliant environment as described in Section C.3.2.K.
(936) 437-3885 www.tdcj.texas.gov
11 Can the Department please explain the process for gaining access to facilities.
We understand that today it can take two or three days to gain access. How will the Department determine what constitutes a delay and who is responsible for that delay?
Section C.10 outlines the criteria for contractor access to the TDCJ secured facilities and establishes the associated liability for delays.
12 The requested SLA of 4 hours is possible but will add significant cost to the maintenance/support program. Will the Department consider reverting to the existing SLAs, which we understand have been effective throughout the life of the contract and will help reduce unneccesary staffing costs for the anticipated limited number of service events.
There will be no change to the Solicitation requirements.
Respondents shall propose solutions that meet the service level requirements specified in Section C.12.B.
13 Are these SLAs flexible? Is the Department open to alternative approaches?
Respondents may describe alternative approaches; however, proposed solutions must meet the minimum service level requirements specified in Section C.12.C. Any exceptions must be clearly identified in the Respondent’s proposal.
14 Please confirm the meaning of "archives." Is this referring to the system-generated audit and log files?
For the purposes of this solicitation, “archives” refers to historical system records and data maintained by the MFES system within the MS SQL Server database housed in the Azure Cloud. This refers to the system generated audit and log files, which may include audit and transaction history retained by the system.
(936) 437-3885 www.tdcj.texas.gov
15 General After the first round of questions are answered, can the Department grant a second question-and-answer phase, with questions due on September 4?
No.
16 What software is being used to print? The RFP mentions 'Department's Classification Profile Software' but doesn't call it by name? How will the photos be imported to this software?
Additional information regarding the software and photo import processes are not currently available.
Respondents should propose a solution that can meet the requirements stated in this Solicitation.
17 What is the currentPID system being used to print IDs?
The current PID system information is not being provided. Respondents should base their proposals on the requirements contained in this Solicitation.
18 If the Vendor provides a SaaS solution, with modifications/customizations, is it understood the the Vendor will maintain total ownership of the solution after the contract period? Or, does TDCJ desire to own the software outright post contract?
The Department only owns agency data. The vendor will maintain ownership of the solution post contract.
File details come from the government source that posted it. Updated .