Artifact A - TCT System Details.pdf
PDF 177 KB Posted
- Attached to
- Take Charge Texas Support Services
- Solicitation number
- HHS0014612v2
- Issued by
- Texas
About this file
This is a system details document and related state contract opportunity for the Texas Health and Human Services Commission (HHSC) Department of State Health Services (DSHS) solicitation for Take Charge Texas (TCT) Support Services. The TCT application is an online platform for infectious disease reporting and service delivery that requires comprehensive maintenance and support services for client, agency, and pharmacy portals; application workflows; eligibility determinations; contracts management; and reporting functions. The contractor must employ Agile/Scrum methodology with sprint teams of five developers/analysts, a product owner liaison, a scrum master, and two testers. The pre-proposal conference was scheduled for November 12, 2025, with questions due by November 14, 2025, and proposals due December 8, 2025, at 10:30 a.m. Central Time. The anticipated award date is March-April 2026, with an anticipated contract effective date of June 2026. The initial contract term is three years with options for HHSC to extend for up to two additional one-year periods.
The TCT system requires support across four environments (DEV, SIT, UAT, PROD) with 24/7 uptime requirements, managing approximately 783.353 GB of production and archive databases. The system supports approximately 146 internal users, 1,075 external users, and 7,441 public users. Historical support demands include approximately 500 maintenance hours per month and 1,000 development and enhancement hours per month, totaling approximately 1,500 hours monthly across approximately 13 sprints annually, with monthly support ticket submissions ranging from 0 L1 tickets, 12 L2 tickets, and 52 L3 tickets. The contractor must provide maintenance and support during standard business hours (Monday-Friday, 7:30 a.m.-5:30 p.m. Central Time) with service request response times ranging from less than one hour for critical incidents to two business days for low-priority issues. Historical compensation has been approximately $800,000 per state fiscal year, with respondents expected to demonstrate cost savings relative to this baseline. Contractors must demonstrate five years of experience in maintenance and development services for similar systems, maintain financial solvency, comply with security and privacy requirements, and maintain all confidential information within the contiguous United States. The solicitation includes potential HUB (Historically Underutilized Business) subcontracting opportunities and requires insurance and comprehensive financial documentation.
View the file
Other files
Show all 38
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
ARTIFACT A: TCT SYSTEM DETAILS
Environments that require support DEV, SIT, UAT, PROD
Underlying code base .Net Framework, LIFT, Decisions, SQL Server
Total database size (production and archive)
783.353 GB
Tiered-request system used for Service requests
Jira Software
Databases Uptime Requirement 24/7
Support details
Maintenance: Historical system maintenance hours per month
~500 approximate hours
Anticipated system development / enhancement hours per month
~1000 approximate hours
Total Anticipated Hours per month
(Maintenance + Enhancements) ~1500 approximate hours
Historical number of Sprints Approximately 13 Sprints are completed per year for (Maintenance + Enhancements)
Monthly support tickets submitted by support level
L1 - 0
L2 - 12
L3 - 52
Licensing and User Counts
Number of Users ~Internal: 146
~External: 1075
~Public: 7441
Frameworks, Libraries, Tools
React Next.js
Lift – UI framework used for
React applications
Decisions – Business validation
JavaOracle – Document scanning GlobalScape – File transfer
OpCon – Batch jobs Developing and Deploying UI and backend API separately.
Version control for large projects for frontend UI and backend API.
Jira
Take Charge Texas – Estimated number of maintenance hours spent on Service Request (SR) tasks.
Take Charge Texas – Estimated number of enhancement hours spent on Service Request
(SR) tasks.
File details come from the government source that posted it. Updated .