v. 05252026

TARRANT COUNTY

HOSPITAL DISTRICT d/b/a

JPS HEALTH NETWORK

REQUEST FOR PROPOSAL #20261395814

Parking Garage Modernization and Technology

The Tarrant County Hospital District d/b/a JPS Health Network (the “District”) is seeking proposals for the provision of Parking Garage Modernization and Technology.

The District will reject any proposal that fails to comply in all respects with the instructions set forth herein for responding to this Solicitation. NO EXCEPTIONS WILL BE MADE, even if you are a current or prior vendor for the District. The contract awarded, if any, under and pursuant to this

Solicitation shall supersede any previous contract, bid, or GPO agreement for the products or services described herein.

Release Date: 09/25/2026

Response Deadline: 10/16/2026, 2:00 p.m. CST

I. OVERVIEW

A. INTRODUCTION AND OVERVIEW

The District desires to award a contract or contracts based upon vendor proposals (“Solicitation

Response(s)”) to this Solicitation (“Solicitation”). The District is soliciting vendor proposals from vendors capable of supplying the District with Parking Garage Modernization and Technology (the “Project, as set forth and specified herein (See Section II below, BUSINESS REQUIREMENTS, attached hereto and incorporated herein for all purposes). All Solicitation Responses must be delivered to the District by the date and time, and in the manner specified in Section I.B hereof to be considered a Solicitation Response by the District.

A Solicitation Response does not commit the District to accept such Solicitation Response or to award a contract based on any Solicitation Response (“Contract Award”) merely because a Solicitation Response may propose the lowest price for the Project. The District expressly reserves the right to base any Contract

Award hereunder upon its evaluation of all relevant factors regarding the vendor, including, but not limited to, Project pricing and terms, management experience and expertise, industry reputation and profile, performance history, support services, location and accessibility, and any other information relevant to its evaluation. Qualifications and omissions will be considered when evaluating vendor solicitation responses.

A Solicitation Response that does not meet the minimum requirements set forth in Section II below, BUSINESS REQUIREMENTS, will be disqualified.

This Solicitation is not an order and does not commit the District to pay for any costs incurred by the prospective vendor in the preparation or submission of the Solicitation or in the procurement of the Project.

Project quantity estimates used herein may or may not reflect actual quantities needed or used by the District in the future, and do not commit the District to order specific Project quantities. Any Solicitation Response accompanied by terms and conditions that conflict with this Solicitation may be rejected by the District.

The District reserves the right to reject any or all Solicitation Responses and to issue a Contract Award or not to issue a Contract Award based solely on the Solicitation Responses received by the District in response to this Solicitation. However, prior to making any award hereunder, the District also reserves the right to engage in additional discussions with one or more of the vendors responding to this Solicitation.

Any prospective Respondent may request an explanation or interpretation of any portion of this Solicitation by complying with the request procedure described in Section I.C.2 below. The responses, if any, of the

District to such requests are subject to and will be in the form of amendment to the Solicitation and will comply with the provisions of Section I.C.2 below. The District may elect not to respond to any or all such requests received from prospective Respondents.

SMALL OR HISTORICALLY UNDERUTILIZED BUSINESS PARTICIPATION

The District maintains a policy of encouraging and engaging in business transactions with vendors who are small or historically underutilized businesses. The District establishes a 25% good faith target goal. The

District also encourages its vendors to utilize subcontractors and vendors who qualify and are certified under applicable law as HUBs. HUB Respondents are also strongly encouraged to subcontract to other

HUBs to expand HUB participation beyond Respondent’s own self-performance. HUB Respondents should identify and list HUB subcontractors and other relevant information under the appropriate

Solicitation Response section(s) and on the Good Faith Form (Exhibit F). Prior to the Contract Award, a

Respondent’s good faith efforts to utilize HUB subcontractors and vendors in its business transactions shall be part of the criteria under which the vendor proposals will be considered. Each Respondent will be required to show in its Solicitation Response its efforts to utilize HUB subcontractors and vendors in its business transactions.

VENDOR PORTAL

Prior to the District’s consideration of a Respondent’s Solicitation Response each Respondent is required to register as a vendor in the District’s online vendor portal, B2Gnow, located on the District’s Website at:

https://jpshealth.gob2g.com.

The District will monitor contract compliance via B2GNow. The prime vendor and any subcontractors awarded contracts as a result of this Solicitation are required to use the secure web-based system to submit project information including, but not limited to, monthly progress payment reports and other information related to HUB participation. The District may require additional information related to the contract to be provided electronically through the system at any time before, during, or after contract award.

Noncompliance may result in exclusion of a vendor from future contract opportunities with the District.

COMPLIANCE WITH TEXAS GOVERNMENT CODE SECTION 2252.908

Please note that Texas Government Code Section 2252.908 does not require any action until after a vendor has been awarded and a contract is ready for the District’s Board of Managers approval. Form 1295s require the District’s contract tracking number, which does not exist until after a vendor has been awarded.

Texas Government Code Section 2252.908 (“Section 2252.908”) states that a governmental entity or state agency may not enter into certain contracts with a business entity unless the business entity submits Form

1295, a disclosure of interested parties, to the governmental entity or state agency at the time the business entity submits the signed contract to the governmental entity or state agency. Section 2252.908 applies to all contracts entered into from and after January 1, 2016 between business entities and Texas governmental entities and state agencies which meet either one of the following criteria:

1. the contract requires a vote of the governing body of the Texas governmental entity, or

2. the contract has a contractual value of at least $1 Million.

The Texas Ethics Commission has adopted a Certificate of Interested Parties form (“Form 1295”) and has made it available on the TEC website.

In 2017 Section 2252.908 was amended to provide that the requirements of Section 2252.908 do not apply to the following contracts entered into or amended after January 1, 2018:

1. a contract with a publicly traded business entity, including a wholly owned subsidiary of the business entity;

2. a contract with an electric utility, as that term is defined by Section 31.002, Texas Utilities Code; or

3. a contract with a gas utility, as that term is defined by Section 121.001, Texas Utilities Code.

In the event a Contract Award is issued pursuant to this Solicitation, the Respondent receiving the Contract

Award shall be required to comply with the provisions of Section 2252.908, Texas Government Code, and the Chapter 46 Rules of the TEC, prior to entry into a contract with the District. The TEC has posted a video tutorial to its website for business entity filings of Form 1295. The TEC video provides step-by-step tutorials for creating login accounts for the business entity for completing and filing Form 1295. The TEC video tutorials can be viewed on its website at:

https://www.ethics.state.tx.us/filinginfo/1295/

The TEC’s FAQs are posted on its website at:

https://www.ethics.state.tx.us/resources/FAQs/FAQ_Form1295.php

COMPLIANCE WITH TEXAS GOVERNMENT CODE CH. 2271 (Boycott of Israel Prohibited)

In 2017 Texas Government Code Section 2271.001 et seq. was enacted to provide that a Texas https://jpshealth.gob2g.com/ https://www.ethics.state.tx.us/filinginfo/1295/ https://www.ethics.state.tx.us/resources/FAQs/FAQ_Form1295.php https://statutes.capitol.texas.gov/Docs/GV/htm/GV.2271.htm governmental entity is prohibited from entering into a contract with a company unless the contract contains a written verification by the company that (i) the company does not boycott Israel, and (ii) the company will not boycott Israel during the term of the contract. The requirement was modified in 2019 to apply only to contracts with a value of $100,000 or more that are made with a company (not including sole proprietorships) with 10 or more full-time employees. The term “boycott Israel” is defined in Section

808.001(1) of the Texas Government Code and means refusing to deal with, terminating business activities with, or otherwise taking any action that is intended to penalize, inflict harm on, or limit commercial relationships specifically with Israel, or with a person or entity doing business in Israel or in an Israel-controlled territory, but does not include an action made for ordinary business purposes. Any awarded contract must comply with the verification requirements in Texas Government Code Section 2271.001, and a Respondent’s failure or refusal to comply will result in the withdrawal of the Contract Award.

Respondents should ensure they and their affiliates do not appear on the Texas Comptroller’s List of

Companies that Boycott Israel.

COMPLIANCE WITH TEXAS GOVERNMENT CODE SECTIONS 2252.151 et seq. (Scrutinized

Business Operations in Sudan, Iran, or with Designated Foreign Terrorist Organizations Prohibited)

In 2017 Texas Government Code Chapter 2252 was amended by adding Sections 2252.151 et seq. to provide that a Texas governmental entity is prohibited from entering into a contract with a company that engages in certain scrutinized business operations in Sudan, Iran, or with foreign terrorist organizations. A

Texas government entity may not enter into a contract with a “scrutinized company” as defined in Section

2270.0001(9) of the Texas Government Code. Respondents should ensure that they and their affiliates do not appear on the Texas Comptroller’s Scrutinized Companies Lists. The District is prohibited by law from entering into a contract with a company on such a list (including a company with any affiliate on the list).

COMPLIANCE WITH TEXAS GOVERNMENT CODE CH. 2274 (Discrimination Against Firearm

Entities or Firearm Trade Associations Prohibited)

In 2021, Texas Government Code Chapter 2274 was enacted to provide that a Texas governmental entity is prohibited from entering into a contract with a company unless the contract contains a written verification by the company that (i) the company does not have a practice, policy, guidance, or directive that discriminates against a firearm entity or firearm trade association, and (ii) the company will not discriminate against a firearm entity or firearm trade association during the term of the contract. The requirement applies only to contracts with a value of $100,000 or more that are made with a company (not including sole proprietorships) with 10 or more full-time employees. The requirement does not apply to sole source contracts or competitive solicitations-related contracts where no respondent can provide the verification required. (See Sec. 2274.002(c)). The term “discriminate against a firearm entity or firearm trade association” is defined in Texas Government Code Section 2274.001(3) and means, with respect to the entity or association, to: (i) refuse to engage in the trade of any goods or services with the entity or association based solely on its status as a firearm entity or firearm trade association; (ii) refrain from continuing an existing business relationship with the entity or association based solely on its status as a firearm entity or firearm trade association; or (iii) terminate an existing business relationship with the entity or association based solely on its status as a firearm entity or firearm trade association; the term does not include: (i) the established policies of a merchant, retail seller, or platform that restrict or prohibit the listing or selling of ammunition, firearms, or firearm accessories; and (ii) a company’s refusal to engage in the trade of any goods or services, decision to refrain from continuing an existing business relationship, or decision to terminate an existing business relationship: (aa) to comply with federal, state, or local law, policy, or regulations or a directive by a regulatory agency; or (bb) for any traditional business reason that is specific to the customer or potential customer and not based solely on an entity’s or association’s status as a firearm entity or firearm trade association. Any awarded contract must comply with the verification requirements in Texas Government Code Section 2274.002, and a Respondent’s failure or refusal to comply https://statutes.capitol.texas.gov/Docs/GV/htm/GV.808.htm https://statutes.capitol.texas.gov/Docs/GV/htm/GV.2271.htm https://comptroller.texas.gov/purchasing/docs/anti-bds.pdf https://comptroller.texas.gov/purchasing/docs/anti-bds.pdf https://statutes.capitol.texas.gov/Docs/GV/htm/GV.2252.htm#2252.151 https://statutes.capitol.texas.gov/Docs/GV/htm/GV.2270.htm#2270.0001 https://comptroller.texas.gov/purchasing/publications/divestment.php https://statutes.capitol.texas.gov/Docs/GV/htm/GV.2252.htm#2252.152 https://statutes.capitol.texas.gov/Docs/GV/htm/GV.2252.htm#2252.152 https://statutes.capitol.texas.gov/Docs/GV/htm/GV.2274.htm https://statutes.capitol.texas.gov/Docs/GV/htm/GV.2274.htm#2274.002 https://statutes.capitol.texas.gov/Docs/GV/htm/GV.2274.htm#2274.001 https://statutes.capitol.texas.gov/Docs/GV/htm/GV.2274.htm#2274.002 will result in the withdrawal of the Contract Award.

COMPLIANCE WITH TEXAS GOVERNMENT CODE CH. 2276 (Boycott of Certain Energy

Companies Prohibited)

In 2021, Texas Government Code Chapter 2276 was enacted to provide that a Texas governmental entity is prohibited from entering into a contract with a company unless the contract contains a written verification by the company that (i) the company does not boycott energy companies, and (ii) the company will not boycott energy companies during the term of the contract. The requirement applies only to contracts with a value of $100,000 or more that are made with a company (not including sole proprietorships) with 10 or more full-time employees. The term “boycott energy company” is defined in Section 809.001(1) of the

Texas Government Code and means, without an ordinary business purpose, refusing to deal with, terminating business activities with, or otherwise taking any action that is intended to penalize, inflict economic harm on, or limit commercial relations with a company because the company: (A) engages in the exploration, production, utilization, transportation, sale, or manufacturing of fossil fuel-based energy and does not commit or pledge to meet environmental standards beyond applicable federal and state law; or (B) does business with a company described by subsection (A). Any awarded contract must comply with the verification requirements in Texas Government Code Section 2276.002, and a Respondent’s failure or refusal to comply will result in the withdrawal of the Contract Award.

TEXAS PUBLIC INFORMATION ACT

Each Respondent acknowledges that the District is a governmental body operating under and subject to the provisions of the Texas Public Information Act (“TPIA”) (Chapter 552 of the Texas Government Code) and thereby acknowledges that certain information collected, assembled, or maintained in connection with the transaction of official business by a governmental body is considered public information potentially subject to disclosure pursuant to a valid TPIA request. Respondent is responsible for challenging any requests for information it considers confidential under the TPIA. The requirements of Subchapter J, Chapter 552 of the Texas Government Code apply to this bid, and the contractor or vendor agrees that that the contract can be terminated if the contractor or vendor knowingly or intentionally fails to comply with a requirement of that subchapter. Respondents should consult the Attorney General’s website

(https://www.texasattorneygeneral.gov/open-government/office-attorney-general-and-public-information-act) for information concerning the application of the provisions of the TPIA to proposals and proprietary vendor information.

B. SOLICITATION RESPONSE REQUIREMENTS, CONDITIONS AND RELATED

INFORMATION

1. Preparation of Solicitation Response.

a. Each Respondent should carefully examine and familiarize itself with this Solicitation and all exhibits, drawings, specifications, and instructions included in this Solicitation. Each Respondent, by submitting a Solicitation Proposal, represents that Respondent has read and understands this

Solicitation and the drawings, exhibits attached to this Solicitation.

b. Each Solicitation Response shall be fully completed, shall contain all the information required from the Respondent by this Solicitation, including the Vendor Certification Form attached hereto as

Exhibit D (“Required Information”), and shall be signed and executed, on the Signature Form attached hereto as Exhibit B by an officer or other authorized representative of the Respondent.

Each page of a Solicitation Response shall contain the company name of the Respondent. A

Respondent’s failure to provide any of the Required Information in its Solicitation Response, or the failure of the Solicitation Response to contain the signature of Respondent’s officer or other duly authorized representative, may result in the District’s disqualification of such Solicitation https://statutes.capitol.texas.gov/Docs/GV/htm/GV.2276.htm https://statutes.capitol.texas.gov/Docs/GV/htm/GV.809.htm#809.001 https://statutes.capitol.texas.gov/Docs/GV/htm/GV.2276.htm#2276.002 https://www.texasattorneygeneral.gov/open-government/office-attorney-general-and-public-information-act https://www.texasattorneygeneral.gov/open-government/office-attorney-general-and-public-information-act

Response. The Required Information shall include detailed information regarding the Respondent’s historical efforts (for the last year) to utilize HUB subcontractors and vendors in its prior business transactions and shall include such detailed information in its Solicitation Response.

c. Each Respondent shall be responsible for and shall bear all costs for the preparation and presentation of its Solicitation Response. Unless otherwise designated by Respondent and agreed by the District, the Solicitation Response and all drawings, materials, supporting documentation, manuals, etc. submitted with any Solicitation Response (“Submitted Materials”) will, immediately upon submission, become the property of the District. After the date upon which the final vendor is selected (See Section I.C.1 below) Respondents may request the return of the Submitted

Materials. However, all costs associated with returning the Submitted Materials to a Respondent shall be born and paid in advance by the Respondent.

d. The District does not guarantee the confidentiality of any Submitted Materials. Each Respondent, by submitting a Solicitation Response, acknowledges and agrees that any Submitted Materials will be distributed or made available to appropriate District personnel and consultants involved in this

Solicitation process, and further understands that the Submitted Materials may be subject to disclosure pursuant to the TPIA. Information considered proprietary by a Respondent should be clearly marked “Proprietary” when submitted with a Solicitation Response.

e. The District reserves the right to modify and/or supplement this Solicitation by amendment issued by the District prior to the date and time of the Response Deadline (defined herein). Any such amendments will be posted online prior to the Response Deadline at the same District internet site where this Solicitation is kept available for solicitation of Solicitation Responses. It is the responsibility of each Respondent to check that internet site frequently to determine if any amendments have been issued.

f. The District reserves the right to withdraw this Solicitation, at its sole discretion, from any or all prospective vendors and Respondents at any time, before or after the Response Deadline. The withdrawal, if ever, of this Solicitation shall be effective upon the District’s issuance of written notice posted online at the same District internet site where this Solicitation is kept available for solicitation of Solicitation Responses, which notice may also be sent by the District to the prospective Respondents in any manner deemed reasonable by the District.

2. Form of Contract.

Any Respondent awarded a contract with the District for the purchase and sale of the products and/or services pursuant to this Solicitation shall be required to execute an agreement between the Respondent and the District which shall in all material respects contain the terms and conditions set forth in Exhibit C

(Contract Terms), which is attached hereto and incorporated herein for all purposes. The District will not agree to change the Contract Terms except under unusual circumstances approved in the sole discretion of the District and its legal counsel. The District will entertain changes to the Contract Terms to the limited extent required to conform the unique terms of the Solicitation Response to the Contract Terms (e.g., unique payment provisions, terms and conditions). The District reserves the right to approve or reject any proposed changes to the Contract Terms submitted by Respondents.

Respondents may not request additional changes to the Contract Terms after the Solicitation Response has been submitted to the District, nor will the District agree to negotiate any requested changes to the Contract

Terms which are not included with the Solicitation Response in the manner and form set forth above in this section I.B.2 and in Exhibit C.

3. Submission of Solicitation Responses.

a. All Solicitation Responses shall be submitted to the District as follows:

(i) All Solicitation Responses must be electronically submitted via file upload at this website: https://f1.jpshealth.org/form/RFPResponseForm. Please ensure this RFP# is entered in the “Bidding Opportunity Num” field on the Response Form, as well as in the file name(s) of each uploaded file. The proposal must include an electronic, editable, unlocked/unsecured copy of your proposed contract (e.g., PDF or TIFF is not acceptable).

If you submit a redline of the Contract Terms in response to Exhibit C, you must provide an editable, unlocked/unsecured version of the redline with your Solicitation Response

(preferably in track changes). The rest of your response must be submitted in a format that preserves the original graphic appearance, such as portable document format (PDF) or other digital image format that is platform-independent and easily readable without purchased software.

(ii) An attempted award will be deemed invalid if the Respondent, upon award of a contract (if ever), is not registered with JPS Vendor Portal (https://jpshealth.gob2g.com/) or is not in compliance with the District’s requirements for vendor credentialing.

(iii) Respondents must submit the Solicitation Response as follows: the file name(s) of each file making up the Solicitation Response must begin with (i) the RFP# followed by (ii) the

Respondent’s name. Also, the cover page of the Solicitation Response must state the following: (i) the name and address of the Respondent, (ii) the Response Deadline, and (iii) the RFP#. Please put the RFP# in the “Bidding Opportunity Num” field on the Response

Form.

(iv) Unless otherwise expressly provided in this Solicitation or in any amendment to this

Solicitation, no Respondent shall modify or cancel the Solicitation Response or any part thereof for thirty (30) days after the Response Deadline. Respondents may withdraw

Solicitation Proposals at any time before the Solicitation Proposals are opened by the District, but may not resubmit them. No Solicitation Proposal may be withdrawn or modified after the

Solicitation Proposal deadline.

(v) Solicitation Proposals will not be considered if they show any omissions, alterations of required forms, additions or conditions not requested or irregularities of any kind. However, the District reserves the right to waive any irregularities and to make the award in the best interest of the District.

(vi) The Respondent acknowledges the right of the District to reject any or all Solicitation

Responses and to waive any informality or irregularity in any Solicitation Response received.

In addition, the District reserves the right to reject any Solicitation Response if the Respondent failed to submit the data, information or documents required by this Solicitation, or if the

Solicitation Proposal is in any way incomplete or irregular.

(vii) Failure to follow the instructions regarding the submission of Solicitation Responses may result in the District’s disqualification of such Solicitation Responses.

b. Solicitation Responses are due on or before 10/16/2026, 2:00 p.m. CST (“Response Deadline”).

The Response Deadline may be extended by the District upon amendment to this Solicitation issued prior to the then-existing Response Deadline. Solicitation Responses are not scheduled for public opening. No email, telephone, telephonic, or FAX Solicitation Responses will be accepted. The https://f1.jpshealth.org/form/RFPResponseForm https://jpshealth.gob2g.com/

District will not be responsible for missing, lost, or late deliveries. Solicitation Proposals delivered after the Response Deadline will not be accepted or considered under any circumstances.

c. Each Solicitation Response shall contain the completed form entitled, “Vendor Certification Form” set forth on Exhibit D which is attached hereto and incorporated herein for all purposes.

C. SOLICITATION SCHEDULE AND RELATED INFORMATION

1. Estimated Schedule

Milestone Date

Solicitation Issued 09/25/2026

Deadline for Questions Submitted by Respondents 10/09/2026, 2:00 p.m. CST

Pre-Proposal Conference 10/07/2026, 1:00 p.m. CST

Response Deadline 10/16/2026, 2:00 p.m. CST

Solicitation Evaluation Period TBD

a. Pre-Proposal Conference. A mandatory pre-proposal conference will be held to allow respondents time to walk through the location. Attendees will meet at JPOC/Bldg. 1350 located at

1350 S Main Street, Fort Worth, TX 76104 on 10/07/2026 at 1:00 p.m. CST.

b. Milestone Dates. Milestone Dates are estimated for planning purposes only and are subject to change.

2. District Solicitation Contact

Respondents may, in the manner prescribed herein, present requests (“Submission Questions”) for an explanation, clarification or interpretation of the BUSINESS REQUIREMENTS in this Solicitation and/or other requirements for submission of Solicitation Responses to the Solicitation Contact identified below during the proposal submission period. All Submission Questions must be submitted in a Questions

Submission Form (attached to the Bidding Opportunity) as an editable Excel document. All Submission

Questions must be electronically submitted via file upload at this website:

https://f1.jpshealth.org/form/RFPResponseForm, and must reference the appropriate pages and sections number of this Solicitation that are the subject of such Submission Questions. The file name of the

Questions Submission Form must begin with (i) the RFP# followed by (ii) the Respondent’s name.

The final date and time to submit Submission Questions is 10/09/2026, 2:00 p.m. Central Time. NO

PHONE CALLS PLEASE. Confirmation of the delivery of Submission Questions to the District is the sole responsibility of the Respondent. The District may, in its sole discretion, elect not to answer or respond to any or all Submission Questions it receives, and the failure of refusal of the District to answer or respond to any Submission Question will not affect, in any way, this Solicitation. Submission Questions may be informally addressed during the Pre-Proposal Conference; provided, however, that no answer or response to any Submission Question by any representative of the District shall be effective unless and until it is issued by the District in writing in the form of one or more addenda to the Solicitation, and has been posted to the District’s Solicitation website link prior to the Response Deadline. It is the responsibility of each

Respondent to check the website for all addenda to the Solicitation up to the Response Deadline.

Prospective vendors are advised that no District employee other than the Solicitation Contact is empowered to make binding statements regarding this Solicitation, and no statements, clarifications, or corrections https://f1.jpshealth.org/form/RFPResponseForm regarding this Solicitation are valid or binding on the District except those issued in writing by the

Solicitation Contact as addenda to the Solicitation.

Contact between Respondents and the District, other than in the manner described and set forth in this Section I.C.2, during the Solicitation Response submission period or evaluation period is prohibited. Any attempt by a Respondent to engage in prohibited contact with the District or the

Solicitation Contact may result in disqualification of its Solicitation Response.

The Solicitation Contact is:

Kerron Haywood, Sourcing & Contracts Specialist

Supply Chain Department

JPS Health Network

JPS Purchasing Office

1500 S. Main Street

Fort Worth, TX 76104

Email: Bid_Submissions@jpshealth.org

District’s Solicitation website link: https://www.jpshealthnet.org/vendors/open-rfpsrfbsrfqs

Solicitation Response submission website link: https://f1.jpshealth.org/form/RFPResponseForm

II. BUSINESS REQUIREMENTS

A. INTRODUCTION

The District is requesting proposals from qualified vendors to provide Parking Garage Modernization and

Technology.

B. BACKGROUND

The Tarrant County Hospital District, known as JPS Health Network (“District”), is a tax-supported organization serving the healthcare needs of families across Tarrant County. JPS provides adult inpatient care at John Peter Smith Hospital, a facility licensed for 582 beds and located in Fort Worth, Texas. JPS has served as a Level I Trauma Center for Tarrant County for over a decade and is currently the largest training institution in Fort Worth.

The health network offers comprehensive services including primary care, specialty care, and pharmacy at more than 25 community locations. JPS is dedicated to providing a full continuum of behavioral health services, including inpatient services at Trinity Springs Pavilion, emergency behavioral health services at our Psychiatric Emergency Center, outpatient services at our JPS clinics, and mental health services for children and adolescents through programs like TCHATT.

JPS is governed by an eleven (11) member Board of Managers, whose members are appointed by the

Tarrant County Commissioners Court.

C. PROJECT SCOPE

The District seeks modernization of the organization’s parking technology system. This engagement is structured in two phases. Phase 1 consists of a fixed-fee assessment and strategy engagement to develop recommendations for a modern, integrated parking solution that improves operational efficiency, supports revenue management, and integrates with JPS’s enterprise technologies, as further described in this Section mailto:Bid_Submissions@jpshealth.org https://www.jpshealthnet.org/vendors/open-rfpsrfbsrfqs https://f1.jpshealth.org/form/RFPResponseForm https://jpshealthnet.org/ https://jpshealthnet.org/medical-professionals/tcmhcc

II.C. Phase 2 consists of implementation of the District-approved recommendations from Phase 1, as described in Section II.C.5 below and priced in Exhibit A.

The assessment will include Parking Access and Revenue Control Systems (PARCS), parking guidance technologies, parking operations, and enterprise systems integration to support a comprehensive parking modernization strategy.

Project Goals

The recommended solution should support the following objectives:

• Improve the patient and visitor parking experience

• Reduce congestion and parking search time

• Enhance operational efficiency

• Standardize parking technologies across all garages on the campus

• Improve revenue accountability and reporting through all departments

• Simplify parking management

• Increase automation through systems integration

• Support future campus growth and expansion

• Minimize disruption to hospital operations during implementation

1. PARCS Evaluation

As part of Phase 1, the vendor shall evaluate the existing PARCS environment, including:

Standardization Assessment. The assessment shall evaluate options for standardizing PARCS technology across all three garage locations, including but not limited to: (i) extending the platform currently in use at

Main Street Garage to Pavilion and Allen Garages; (ii) replacing all three garages’ PARCS technology with a different unified platform; or (iii) another approach supported by the vendor’s independent analysis. The vendor’s recommendation shall be based on its own assessment findings and shall not presume any particular outcome. The vendor’s cost-benefit comparison of standardization options shall explicitly account for the remaining useful life, current condition, and any disposal or stranded-asset cost of existing

PARCS equipment at each garage, so that a recommendation to replace functioning equipment is weighed against the cost of retaining and extending it, rather than compared on operational or technical merits alone.

• Parking equipment and lane devices including gates arms, entry and exit stations

• Entry and exit workflow operations

• Pay-on-foot and cashier systems

• Revenue controls and reporting

• Staff parking and parking sticker administration

• Patient/visitor, team member, physician, and vendor parking workflows

• Equipment lifecycle and replacement planning including preventative maintenance

• Software functionality and support

• Payment processing architecture with Windcave

• PCI compliance considerations

• Business continuity and system resiliency

The vendor(s) shall identify opportunities to:

• Standardize parking technologies across multiple locations on campus

• Improve patient/visitor, team member, physician, and vendor experience

• Increase operational efficiency across all garages

• Improve reporting and revenue controls

• Reduce maintenance complexity and issues

• Support future expansion and scalability

Deliverables

• Current State Assessment

• PARCS Technology Evaluation

• Future-State PARCS Strategy

• Budgetary Replacement Options

2. Parking Guidance Technology

If requested, the vendor shall evaluate parking guidance technologies that improve patient/visitor, team member, physician, and vendor access and reduce parking search times.

The assessment may include:

• Occupancy detection systems

• Dynamic signage

• Real-time parking availability

• Space counting technologies

• Patient and visitor wayfinding

• ADA parking monitoring

• Analytics and utilization reporting

• Integration with mobile applications and PARCS

Deliverables

• Parking Guidance Assessment

• Recommended Technology Options

• Preliminary Implementation Strategy

3. Parking Operations

Parking operations are currently performed by parking services staff members. If requested, the vendor(s) shall evaluate current operational practices and identify opportunities for improvement and efficiency.

Assessment may include:

• Current parking operations staffing model o Including Staffing optimization o Parking services performance metrics

• Patient/visitor entry and exit traffic flows o Patient/visitor assistance

• Monitoring and controlling physician and employee parking operations

• Revenue collection procedures and policies

• Standard operating procedures

• Customer service performance

• Performance metric reporting

• Staffing models and optimization

If requested, the vendor may also identify opportunities for operational improvements or alternative service delivery models while maintaining a patient-centered approach.

Deliverables

• Parking Operations Assessment

• Operational Improvement Recommendations

• Staffing and Service Model Options

4. Systems Integration

The vendor shall assess integration requirements between parking systems and the District’s enterprise technologies.

Badge Access

Evaluate integration with employee and physician badge/credentialing systems. The District's current employee and physician badge/credentialing system is APACS. Consider:

• Employee parking access using badges

• Physician parking privileges in Pavilion and Allen Garages

• Contractor access

• Role-based parking permissions

Toll Tag Integration

Assess opportunities to utilize toll tags for physicians, staff, and vendors parking in all garages across the

JPS campus. Evaluate toll tag capabilities for:

• Staff, physicians, and vendors parking across all garages located at \JPS campus

• Parking enforcement

License Plate Recognition (LPR)

Evaluate LPR capabilities for:

• Permit management

• Credential-free entry and exit

• Employee parking

• Physician parking

• Visitor parking

• Parking enforcement

• Lost ticket reduction

• Revenue protection

• Operational analytics

Mobile Applications

Assess mobile capabilities including:

• Integrated mobile payment at kiosk or Pay-on-Foot (POF) stations

• Navigation and wayfinding

• Customer notifications

• Parking reservations

• Digital permits

• Account management

Patient Parking Validation

Evaluate integration with clinical and administrative workflows to support:

• Integrated departmental validation o Including all outpatient and inpatient clinic validations at the JPS campus o Scannable and QR code validation

• Validation voucher reporting and reconciliation within integrated garage systems

• Integration with hospital business systems where appropriate

Deliverables

• Integration Requirements Matrix

• Future-State Integration Architecture

• Interface Recommendations

Phase 1 Synthesis Deliverables

In addition to the component-level deliverables identified above, the vendor(s) shall synthesize the following consolidated deliverables across all four Phase 1 components (no duplicate work is required):

• Consolidated Gap Analysis

• Future-State Parking Technology Architecture

• Phased Implementation Roadmap

• Budgetary Cost Estimates for Phase 2

• Executive Presentation to Leadership

JPS currently operates two distinct PARCS environments across the campus. Pavilion Garage and

Allen Garage operate an existing PARCS platform recently upgraded from software version 10 to version 16 under a SaaS subscription; that upgrade addressed software and select workstation hardware only and did not replace the underlying physical equipment (gate arms, lane devices, cameras, and related field equipment) at those two garages. Main Street Garage, a newly constructed facility, operates a separate PARCS platform installed with the garage's original construction and currently maintained under a separate service and preventative maintenance agreement.

Current payment gateway processing is provided through Windcave for all garage locations at the

JPS campus.

5. Phase 2: Implementation & Managed Services

Upon the District’s issuance of Notice to Proceed for Phase 2 as set forth in Section II.F, the awarded Phase

2 vendor(s) shall implement the District-approved recommendations arising from Phase 1, including:

• Procurement, installation, and commissioning of the District-approved PARCS, parking guidance technology, and systems integration components

• Transition coordination with existing parking operations staff and implementation of any District-approved operational changes

Parking Facility Locations

1. Pavilion Garage

2. Allen Garage

3. Main Street Garage

• Ongoing maintenance, software support, and help desk / response-time obligations for the term of the contract

• Vendor shall provide service manuals, calibration standards, and diagnostic software or tools to

District facilities/IT staff rather than withholding them as proprietary; shall provide a minimum period of spare parts availability following any end-of-life or discontinuation notice, with advance notice before parts support ends; and shall ensure that in-warranty use of vendor-provided documentation or diagnostic tools by qualified District or third-party personnel does not void the equipment warranty. Vendor shall warrant all equipment for a minimum of twelve (12) months, commencing on the applicable acceptance date, not the contract execution date.

Hosting and Infrastructure

• Vendor shall specify the hosting model for the proposed PARCS platform (vendor-hosted, cloud, on-premise, or hybrid) and shall state Recovery Time Objective (RTO) and Recovery Point Objective

(RPO) commitments appropriate to the criticality of revenue and access-control functions supported by the system.

Hardware Replacement and Stabilization

• Mission-critical hardware components shall be replaced within 24 hours of a confirmed failure;

standard hardware components shall be replaced by the next business day.

• Vendor shall provide a defined hypercare/stabilization period of not less than 60 days immediately following go-live, during which Vendor shall provide elevated support beyond normal steady-state service levels, including a stated staffing commitment and defined exit criteria for transitioning to steady-state support.

Site Coordination and Scheduling

• Vendor shall provide advance notice for any work affecting garage utilities, vehicle or pedestrian egress, or generating noise or vibration near occupied hospital areas; shall state whether after-hours or off-shift work is required and address any associated pricing premium; and shall follow a utility shutdown protocol with a defined lead time and District sign-off before any planned outage.

Acceptance Testing

• Vendor shall provide defined acceptance criteria for installed equipment and systems, including functional testing, a punch list process with a set cure period, and identification of who performs acceptance testing or inspection. Final payment and any Retainage release shall be conditioned on acceptance sign-off, not substantial completion alone, and the warranty period shall commence on the acceptance date rather than the contract execution date.

Performance Standards (KPIs)

Vendor performance under Phase 2 shall be measured against the following KPI floors, organized under the District’s four-pillar framework:

• Operational/Delivery – System uptime of 99.5% or greater; critical-component repair response within 4 hours; standard-component repair response by the next business day

• Quality/Compliance – Preventive maintenance completion of 95% or greater; maintenance of all required PCI compliance attestations; rework/callback rate not to exceed 10%

• Financial/Value – Daily revenue reconciliation variance not to exceed 0.5%, measured following a 30-day stabilization period after go-live

• Relationship/Responsiveness – Complaint acknowledgment within 48 hours; escalation response consistent with the critical/standard repair tiers set forth above

Reporting and Records. Vendor shall self-report performance against each KPI set forth above on a monthly basis, in a format specified by the District. Vendor shall maintain complete supporting documentation for all reported metrics – including but not limited to maintenance and repair records, revenue reconciliation records, and complaint/response logs – for the duration of the contract and for three

(3) years following termination or expiration. Upon reasonable written notice, the District, or its authorized representative, may inspect and audit such documentation during Vendor’s normal business hours, no more frequently than annually absent a reasonable basis to believe reported performance or revenue figures are inaccurate, to verify Vendor’s compliance with the performance standards set forth in this Section. Vendor shall produce the requested documentation within ten (10) business days of such request. If an audit reveals a discrepancy between Vendor’s reported figures and the audited figures, the parties shall true up any resulting overpayment or underpayment within thirty (30) days of the audit’s conclusion, regardless of whether the discrepancy favored the District or Vendor. Vendor’s failure to maintain such documentation or to provide access as required under this Section shall constitute a material breach of the contract.

Post-Award Governance

Vendor performance under Phase 2 shall be reviewed on a monthly basis, consistent with the KPI reporting cadence set forth above. Vendor shall designate a day-to-day contact for routine operational matters, separate from any named contract owner where the two are not the same individual; this contact shall be identified by role in the Solicitation Response, with a named individual identified in the executed contract exhibit consistent with the RACI Matrix Requirement set forth in Section II.E.

Where Vendor’s day-to-day contact changes during the term, Vendor shall provide a documented handoff to the incoming contact before the outgoing contact disengages, including a transfer of open issues, upcoming milestones, and any pending KPI concerns. This handoff requirement is mandatory and applies regardless of the reason for the change in contact.

Deliverables

• Implementation Plan and Schedule

• Commissioning and Acceptance Documentation

• Ongoing Performance Reports

D. PRICE QUOTES

Price quotes shall remain firm during Solicitation evaluation and for an additional 120 days after recommendation for award. Pricing must remain fixed for the initial term of the agreement. Respondents must include all costs associated with use of the items. Any costs not included in the Solicitation response cannot be charged to the District. Phase 2 renewal pricing shall be adjusted in accordance with the pricing adjustment provision set forth in Section II.F; no Vendor-proposed pricing increases will be considered.

Use the spreadsheet attached as Exhibit A to this Solicitation to provide line-item pricing in your Response.

E. EQUIVALENT OR APPROVED EQUAL

Whenever a product is defined by describing a proprietary product, or by using the name/model of a manufacturer or vendor, the term “or other units considered to be equivalent”, if not inserted, shall be implied. The specific product described shall be understood as indicating the type, function, and minimum standard of design, efficiency, and quality desired and shall not be construed in such a manner as to exclude products of comparable quality, design, and efficiency.

The references to brand names and/or numbers are intended to be descriptive, and not restrictive, unless otherwise specified. If the specific product cannot be supplied, equivalent items meeting the standards of quality specified shall be considered. The determination of equivalent or approved equal is at the sole discretion of the District.

A Respondent that submits a Solicitation Response for both Phase 1 and Phase 2 of this Solicitation is not precluded from award of either or both phases solely on that basis. However, any Respondent proposing on both Phase 1 and Phase 2 must disclose that intent in its Phase 1 response and must affirmatively confirm that its Phase 1 recommendations are vendor-neutral and are not structured to favor its own Phase 2 proposal, consistent with the equivalent-or-approved-equal standard set forth above.

Additionally, any Respondent performing Phase 1 assessment work shall disclose any existing business relationship with a specific equipment manufacturer, authorized dealer, or servicer that could reasonably be perceived to bias its standardization recommendation under Section II.C, regardless of whether that

Respondent intends to bid on Phase 2.

RACI Matrix Requirement. Each Respondent shall submit, as part of its Solicitation Response, a proposed RACI matrix (Responsible, Accountable, Consulted, Informed) covering the major delivery and post-acceptance support activities described in this Solicitation, including at minimum: Phase 1 assessment deliverable development, Phase 2 procurement and installation, systems integration and commissioning, ongoing maintenance and support, and performance/KPI reporting. Respondent’s proposed matrix shall identify District-side roles by department only (e.g., Parking Services, Sourcing & Contracts, IT Security), and shall not identify District personnel by name. The RFP-stage RACI matrix is not binding on the District and may be discussed and revised during negotiation with the successful Respondent(s).

Upon Contract Award, a final RACI matrix shall be attached to the executed contract as an exhibit, identifying named individuals on both the Vendor side and the District side against the functional roles established during solicitation. The executed RACI exhibit is binding upon incorporation into the contract.

Substitution of any named individual on the executed RACI exhibit, or other amendment to the matrix, requires ten (10) business days’ written notice. Vendor's named contract owner on the executed RACI exhibit shall remain assigned to the contract for a minimum of twelve (12) months from Contract Award, absent a documented reason for earlier substitution accepted by the District.

F. CONTRACT TERM

Phase 1 shall be completed on a fixed-fee basis within ninety (90) days of Notice to Proceed. Upon the

District’s acceptance of the Phase 1 deliverables and at the District’s sole discretion, the District may issue

Notice to Proceed for Phase 2.

Upon Notice to Proceed for Phase 2, the…