ESBD_432148_1751314431120_00 - 3202500148 RFO Mobile Credential Wallet.pdf

Texas Workforce Commission

Request for Offer

Mobile Credential Wallet

3202500148

Issued: June 30, 2025

Responses Due: August 11, 2025, 10:00 CST

Class & Item Description

208-54 *Internet, Web Site and Mobile Application Development Software, Microcomputer

209-54 *Internet and Web Site Software For Main Frame Computers

920-40 *Programming Services, Computer (Including Mobile Device Applications)

3202400011 Credential Wallet RFO

SOLICITATION CONTENTS

The list below contains a summary of the documents comprising this Request for Offer (RFO) issued by Texas Workforce Commission (TWC). The Successful Respondent shall be responsible for fulfilling all requirements contained in these documents.

1. Credential Wallet RFO (this document)

a. Attachments

i. Attachment 1: Texas Workforce Commission (TWC) Terms & Conditions

ii. Attachment 2: Execution of Offer

iii. Attachment 3: Voluntary Product Accessibility Template

(VPAT)

iv. Attachment 4: Policy Driven Adoption for Accessibility

(PDAA)

v. Attachment 5: Statement of Work (SOW)

vi. Attachment 6: Pricing Worksheet

vii. Attachment 7: Pricing Assumptions (if applicable)

viii. Attachment 8: HUB Subcontracting Plan (HSP) Guide and HUB Vendors List

ix. Attachment 9: HUB Subcontracting Plan (HSP) Form

x. Attachment 10: Evaluation Scoring Matrix

xi. Attachment 11: Questions and Answers

xii. Attachment 12: Data Center Services (DCS) and DCS Templates

xiii. Attachment 13: Cybersecurity Requirements and Certificates

xiv. Attachment 14: Substitute W-9 & Direct Deposit Form

xv. Attachment 15: How to fill out the PAR

xvi. Attachment 16: Financial Questionnaire

xvii. Appendix A: Texas Workforce Board Map

b. Response Packages (to be used for materials expected back from Respondents)

i. Response Package 1 – Administrative Submission Requirements (See Table 3)

ii. Response Package 2 – Response to Service Requirements (See Table 7)

iii. Response Package 3 – Service Pricing (See Table 8)

iv. Response Package 4 – HUB Subcontracting Plan (See Table 9)

Table of Contents

1.0 INTRODUCTION

1.1 Purpose

1.2 Statutory Authority

1.3 Background

1.4 TWC Information

2.0 SCOPE

2.1 Required Goods and Services

2.2 Excluded Services

2.3 Electronic and Information Resources (EIR) Accessibility

2.4 Texas Data Center Services (DCS)

2.5 Form of Contract

2.5.1 Contract and Terms Negotiation

2.5.2 Proposed Changes and Exceptions

2.5.3 Term of Contract

3.0 GENERAL INFORMATION

3.1 Point of Contact

3.2 Response Integrity

3.3 Schedule of Events

3.3.1 RFO Schedule 7

3.3.2 Optional Pre-Offer Conference

3.3.3 Written Questions and Official Answers

3.4 Historically Underutilized Businesses

3.4.1 HUB Subcontracting Plan (HSP)

3.5 Response Deadline and Submission Requirements

3.6 Response Instructions

3.6.1 No Marketing Materials

3.6.2 Response organization

3.6.3 Response Package 1: Administrative Submission Requirements

3.6.4 Response Package 2: Response to Service Requirements

3.6.5 Response Package 3: Pricing

3.6.6 Response Package 4: Completed HUB Subcontracting Plan

3.7 Right to Amend or Withdraw RFO

3.8 Pre-agreement Costs

3.9 Ownership of Responses

3.10 Public Information

3.11 News Release

4.0 EVALUATIONS, NEGOTIATIONS, AND AWARD

4.1 Evaluation of Responses

4.2 Minimum Qualifications (Pass/Fail Criteria)

4.3 Evaluation Criteria for Written Responses

4.4 Demonstrations

4.5 Clarification Sessions

4.6 Best and Final Offer (BAFO)

4.7 Negotiations

4.8 Award of Contract

5.0 SPECIFIC CONTRACT TERMS

5.1 Warranty

5.2 Security Agreements, Background Checks, and Mandatory

Training

5.3 Bonding and Insurance

5.3.1 General Insurance Requirements

5.3.2 Policies must include the following clauses, as applicable:

5.3.3 Specific Insurance Coverage Required

3202500148 Mobile Credential Wallet RFO Page 1

1.0 INTRODUCTION

1.1 Purpose

The objective of this Request for Offer (RFO) is to seek a Successful Respondent to provide a web-based software solution which stores personal inventories of earned academic and workforce credentials. The software solution may be configurable, but must be fully built, tested, and already in use in at least one production environment. A response without evidence of a fully developed solution is cause for disqualification.

As a result of this RFO, TWC expects to receive and evaluate Responses and select one (1) qualified Respondent whose response fully meets all requirements of the scope of work with whom the agency can enter negotiations to define final pricing and refine details within the scope of work. Section 4.0 – EVALUATIONS, NEGOTIATIONS AND AWARD contains more information regarding the Response evaluation and vendor selection process.

1.2 Statutory Authority

TWC is issuing this solicitation under the authority of Chapter 2157.006(a)(2) of the Texas Government Code.

This RFO is not a solicitation for professional or consulting services as defined in Chapter 2254, Texas Government Code (https://statutes.capitol.texas.gov/Docs/GV/htm/GV.2254.htm).

1.3 Background

1. TWC has set a goal of ending the middle skills gap in Texas. As part of that goal, this RFO seeks to acquire a Solution in which individuals have access to personal inventories of earned academic and workforce credentials. These inventories are often referred to as credential wallets.

2. TWC is committed to supporting the state's economic growth by addressing the middle skills gap and promoting workforce development.

To empower Texas job seekers with greater control over their credentials, TWC seeks a solution that provides personal, digital inventories, commonly known as credential wallets. The goal is to simplify the process of accessing and sharing credentials necessary to apply for post-secondary training and employment opportunities through a user-friendly platform offered as a service through the Workforce Solutions System.

3. The Solution will allow an individual to:

a. store and display credentials (for example, certifications, licenses, https://statutes.capitol.texas.gov/Docs/GV/htm/GV.2254.htm

3202500148 Mobile Credential Wallet RFO Page 2 diplomas),

b. track credential expiration and renewal dates (as applicable),

c. receive information about the next credential(s) to pursue while on a career pathway established in accordance with Credential Transparency Description Language (CTDL), and

d. share credentials instantly and securely with various audiences such as employers, workforce training programs, local education agencies, and institutions of higher education.

1.4 TWC Information

TWC is an administrative agency within the executive branch of the State of Texas, having its principal office at 101 East 15th Street, Austin, Texas 78701. Information regarding TWC and its programs is available online and can be accessed at www.twc.texas.gov.

2.0 SCOPE

2.1 Required Goods and Services

The Successful Respondent must provide a software Solution with a mobile responsive website, in accordance with Attachment 5 Statement of Work

(SOW).

2.2 Excluded Services

A custom-built solution or custom hosted solution or any solution that requires customization of the software core code will not be considered.

2.3 Electronic and Information Resources (EIR) Accessibility

1. Under Texas Government Code, Chapter 2054, Subchapter M, § 2054.451 et seq., TWC must procure EIR that comply with the Accessibility Standards defined in the Texas Administrative Codes 1 TAC 206, 1 TAC 213 and in the Worldwide Web Consortium WCAG 2.1 AA technical standard as applicable, and when such products or services are available in the commercial marketplace or when such products are developed in response to procurement solicitations.

2. Accordingly, all Respondents must provide accurate Accessibility Conformance Reports (ACRs) created using the applicable sections of the Voluntary Product Accessibility Template® (VPAT®) Revised Section 508 Edition (Version 2.4 or higher) or links to ACRs located on manufacturer websites for Commercial Off the Shelf (COTS) products, including Software as a Service (SaaS), for each product or product family (as https://credentialengine.org/credential-transparency/ctdl/ https://credentialengine.org/credential-transparency/ctdl/ http://www.twc.texas.gov/ https://texreg.sos.state.tx.us/public/readtac$ext.ViewTAC?tac_view=5&ti=1&pt=10&ch=206&sch=B&rl=Y https://texreg.sos.state.tx.us/public/readtac$ext.ViewTAC?tac_view=4&ti=1&pt=10&ch=213 https://texreg.sos.state.tx.us/public/readtac$ext.ViewTAC?tac_view=4&ti=1&pt=10&ch=213 https://www.w3.org/ https://www.w3.org/TR/WCAG21/

3202500148 Mobile Credential Wallet RFO Page 3 applicable) included in the submitted pricelist. Instructions on how to complete this document are included in the template itself. ACRs based on earlier versions of the VPAT® template will be accepted if such completed ACRs already exist, and there have been no changes to the product/service since the time of the original document completion.

Respondents must submit a completed, accurate Voluntary Product Accessibility Template (VPAT) for each product or service included in the submitted pricing (Attachment 6 Pricing Worksheet). The following sections for each submitted VPAT must be completed: WCAG 2.0 level A and AA, WCAG 2.1 level A and AA, and the Revised Section 508 standards.

3. Respondents that claim their products are exempt from accessibility requirements must present that position to TWC as a question during the question-and-answer period of the solicitation.

4. Additionally, Respondents must ensure that EIR Accessibility criteria are integrated into key phases of the project development lifecycle including but not limited to planning, training, design, development, functional testing, user acceptance testing, maintenance; and report accessibility status at key project checkpoints as defined by TWC.

5. In addition to the VPAT requirement, Respondents must complete the Policy Driven Adoption for Accessibility (PDAA) for Vendor Self- Assessment. The PDAA is an indicator of the extent to which a Respondent’s organization has implemented accessibility best practices within operations and integrated accessibility criteria into all phases of a product life cycle.

6. Respondent shall complete:

a. Attachment 3 VPAT and

b. Attachment 4 PDAA.

Per Table 2: Response Package 1 Files, the Respondent shall include the above referenced attachments in Response Package 1.

7. Responses without completed VPAT and PDAA will not be considered.

8. The proposed solution must meet TWC EIR accessibility standards subject to review by the TWC Software Acquisitions Review Committee (SARC) before contract award.

2.4 Texas Data Center Services (DCS)

In accordance with Texas Government Code 2054.391, TWC is required to participate in DIR’s Data Center Services (DCS). By direction of the DIR

3202500148 Mobile Credential Wallet RFO Page 4

Executive Director, TWC must include DCS requirements in all technology solution solicitations. TWC requires all Respondents to complete and include the most recent version of DIR’s DCS forms (Attachment 12 Data Center Services (DCS) and DCS Templates, Section 2) provided with this solicitation so that TWC can obtain a rough order of magnitude (ROM) quote from DCS on the Respondent’s solution. (See and complete Attachment 12 Data Center Services (DCS) and DCS Templates, Section 2.) TWC will include the DCS quote/cost when scoring the Respondent’s submission and will provide a copy of the information received from DIR to the individual Respondents.

Respondents may propose a Software as a Service (SaaS) subscription option to include hosting outside of the DIR DCS, but the proposed solution must meet the NIST definition of a SaaS, must not interface with DIR DCS compute, and must include Attachment 12 Data Center Services (DCS) and DCS Templates, Section 2. Responses including a SaaS solution without completed Attachment 12 Data Center Services (DCS) and DCS Templates, Section 2 will not be considered. Before TWC can award a contract for a SaaS solution hosted outside of the DIR DCS, it must obtain a DCS exemption for the specific SaaS solution from DIR.

2.5 Form of Contract

2.5.1 Contract and Terms Negotiation

The final terms and conditions of any agreement resulting from this solicitation (“Contract”) shall be agreed upon during negotiation. However, the minimum standard terms and conditions that shall be included in any awarded Contract are contained in the TWC Terms and Conditions (see Attachment 1). Many of the standard terms and conditions contained in Attachment 1 TWC Terms & Conditions are required by Texas law, which shall be the governing law for any Contract.

2.5.2 Proposed Changes and Exceptions

TWC reserves the right to make changes to the TWC Terms and Conditions if it is in the best interest of the State to do so. Should this occur prior to the award of any Contract, any Respondent selected for negotiations will be notified.

2.5.3 Term of Contract

1. TWC anticipates an initial contract term of one (1) year with four (4) optional one (1) year renewals to be exercised by TWC at its discretion.

3202500148 Mobile Credential Wallet RFO Page 5

The Contract is contingent upon the continued availability of funding. If funds become unavailable through lack of appropriations, legislative budget cuts, amendment of the General Appropriations Act, TWC consolidation of offices, or any other disruption of current appropriations, Termination provisions of Attachment 1 TWC Terms & Conditions shall apply.

Following the base term and any allowable renewals or extensions, TWC may extend any resulting Contract for not more than one additional option period to address immediate operational or service delivery needs.

If the resulting Contract does not include a defined option period, the extension is limited to one year.

2. In the event of prolonged Contract negotiations which exceed thirty (30) calendar days due to the number and/or significance of exceptions taken, lack of responsiveness, or other failure to close Contract negotiations on the part of Respondent that are not due to a failure on the part of TWC, TWC may, in its sole discretion, bypass the Respondent and commence negotiations with the next-highest scoring Respondent, or continue with the current Respondent but the resulting contract may be for a shorter contract term depending on funding requirements.

3. Section 3.6.3.2 of this RFO contains the instructions for Respondents to note any objection or exceptions to any provision, term, or condition specified in the RFO.

3202500148 Mobile Credential Wallet RFO Page 6

3.0 GENERAL INFORMATION

3.1 Point of Contact

1. Kelly Hall is the sole TWC point of contact for this procurement.

All communications regarding this RFO must be addressed in writing to:

Kelly Hall, CTCD IT Purchaser Texas Workforce Commission Procurement and HUB Services Email: vendorproposals@twc.state.tx.us Required Subject Line for all Communications related to this

RFO:

3202500148 Mobile Credential Wallet – ABC Question(s)/ABC RFO Response

Note: ABC refers to Respondent name

2. Upon issuance of this RFO, Respondents shall make no contact concerning this RFO with other TWC personnel, except as permitted by the point of contact. Failure to comply with this requirement at any point prior to contract award may result in disqualification. This restriction does not preclude discussions between affected parties for the purpose of conducting business unrelated to this procurement.

3. Exception to the Sole Point of Contact: Contact with the TWC Historically Underutilized Business (HUB) office is allowed solely for the purpose of addressing HUB Subcontracting Plan (HSP) questions. A Respondent with questions relating to the HSP is permitted to direct those questions to the TWC HUB staff: TWCHUBinfo@twc.texas.gov.

3.2 Response Integrity

1. To ensure the integrity of the competitive process, a Respondent may not directly or indirectly communicate any of the contents of its Response to:

a. A competitor of the Respondent; or

b. Any other company, corporation, firm, partnership, individual, or related entities of the same parent company engaged in the same line of business as the Respondent; or

c. A related entity of the Respondent engaged in the same line of business as the Respondent; or

d. Other state officials.

mailto:vendorproposals@twc.state.tx.us mailto:TWCHUBinfo@twc.texas.gov

3202500148 Mobile Credential Wallet RFO Page 7

This prohibition does not preclude discussions with entities serving as subcontractors to the Respondent on this solicitation.

2. This prohibition is in effect during the preparation of the offer and while the offer is pending with TWC, including the negotiation and finalization of any resulting Contract. The term “related entities” includes, but is not limited to, affiliates, subsidiaries, associates, branches, and divisions. It does not include entities that may occasionally enter into teaming/subcontracting agreements with one another to provide services under a contract with a third party but otherwise have no legal relationship with each other.

3. When a related entity of the Respondent (whether related at the time Responses are due or at any time thereafter) submits a competing offer, TWC may require additional information to ensure each separate Response is independent. Failure to provide or fully disclose all such information may, at TWC’s discretion, disqualify Respondent or result in the termination of any resulting contract. RESPONDENT HAS AN

ONGOING DUTY TO UPDATE REQUIRED INFORMATION ANY TIME

THAT SUCH INFORMATION CHANGES.

3.3 Schedule of Events

3.3.1 RFO Schedule

It is TWC’s intention to comply with the following schedule for this RFO.

These dates represent a tentative schedule of events. TWC reserves the right to modify these dates at any time. Prospective Respondents will be notified of modifications to the schedule via the Electronic State Business Daily (ESBD) web site. Respondents are advised to regularly check the ESBD for updates to this solicitation.

Table 1: Schedule of Events

Activity Date RFO Posted to ESBD June 30,2025 Pre-Offer Conference (attendance is optional)

July 9, 2025 at 2:00 PM Central Time

Deadline for Submitting RFO Questions

July 14, 2025 at 5:00 PM Central Time

Deadline for courtesy HSP review July 22, 2025 at 5:00 PM Central Time

Answers posted to ESBD July 28, 2025 at 5:00 PM Central Time or soon thereafter

3202500148 Mobile Credential Wallet RFO Page 8

Activity Date Deadline for submitting Response

August 11, 2025 at 10:00 AM Central Time

Evaluation, Clarification, Amended Responses and Final Negotiations August-October 2025

Award of Contract November 2025 Anticipated Contract Start Date December 2025

3.3.2 Optional Pre-Offer Conference

The Optional Pre-Offer Conference will be held remotely. There is no option for in-person attendance.

3.3.2.1 Conference Information

1. A conference will be held on the date and time specified in RFO Section

3.3.1 above.

2. To reserve a conference seat, register at:

https://zoom.us/webinar/register/WN_SafPnk8OSHWEh_baH49gyQ

3. After registering, you will receive a confirmation email containing information about joining the Conference.

3.3.3 Written Questions and Official Answers

1. Using Attachment 11 Questions and Answers Respondents shall submit all questions regarding this RFO by e-mail to the Point of Contact listed in Section 3.1 Point of Contact. Questions regarding this RFO will be accepted until the date and time specified in Section 3.3 Schedule of Events. Official answers will be posted as an Addendum to this RFO, on the Electronic State Business Daily (ESBD), available at http://www.txsmartbuy.com/esbd. Please only use Google Chrome to navigate to ESBD.

2. By submission of a question, Respondent acknowledges that the applicable question will be posted with each official answer and therefore Respondent should not include any confidential or proprietary information in such questions. TWC will not publish the identity of any vendor that submitted any inquiry.

3.4 Historically Underutilized Businesses

3.4.1 HUB Subcontracting Plan (HSP)

1. TWC has determined that subcontracting is probable under any contract awarded as a result of this RFO. ALL RESPONDENTS RESPONDING TO https://zoom.us/webinar/register/WN_SafPnk8OSHWEh_baH49gyQ http://www.txsmartbuy.com/esbd

3202500148 Mobile Credential Wallet RFO Page 9

THIS RFO, INCLUDING THOSE THAT ARE HUB CERTIFIED OR THOSE

WHO DO NOT PLAN TO SUBCONTRACT, MUST COMPLETE A HUB

SUBCONTRACTING PLAN (HSP) IN ACCORDANCE WITH THE STATE’S

POLICY ON UTILIZATION OF HUBs. THE HSP MUST BE INCLUDED AS

PART OF THE RESPONSE TO THIS RFO. FAILURE TO SUBMIT A COMPLETE

HSP AS INSTRUCTED WILL RESULT IN DISQUALIFICATION OF THE

RESPONSE FROM CONSIDERATION.

2. The State’s Policy on Utilization of Historically Underutilized Businesses and HSP forms are available at:

https://comptroller.texas.gov/purchasing/vendor/hub/forms.php. Please review the HSP forms carefully and allow sufficient time to identify and contact HUBs and allow them to respond. Completed HUB Subcontracting Plan must be submitted in Section 3.6.6.1 Response Package 4 (See Table 8). NOTE: Respondent must demonstrate a good faith effort to contract with new HUBs if currently proposed HUBs have performed as subcontractors to the Successful Respondent for more than five (5) years.

If the Successful Respondent does not plan to subcontract, Successful Respondent must state that fact in its plan.

3. See Attachment 8: HUB Subcontracting Plan (HSP) Guide for assistance filling out the HUB Subcontracting Plan Form.

4. An HSP form is available, see Attachment 9: HUB Subcontracting Plan (HSP) Form.

5. TWC requires, as a condition of an award, that Respondents comply with

Texas Government Code Chapter 2161, Subchapter F and TWC’s HUB Plan relating to the State’s program on Historically Underutilized Businesses (HUBs). Respondents must comply with Texas Workforce Commission HUB Subcontracting Plan (HSP) Procedure. If awarded, the Awarded Contractor will be required to submit a monthly compliance report (Prime Contractor Progress Assessment Report – Attachment 15 – How to fill out the PAR) to TWC.

6. TWC adheres to the administrative rules, policies, and forms developed by the agency relating to HUBs. For more information about the HUB program at TWC, contact TWC HUB Outreach Coordinator at:

TWCHUBInfo@twc.texas.gov.

7. Agency Special Instructions/Additional Requirements

A. The TWC HUB goal is 26% for all other service contracts. TWC finds that this contract contains subcontracting opportunities in the following services areas:

https://comptroller.texas.gov/purchasing/vendor/hub/forms.php mailto:TWCHUBInfo@twc.texas.gov

3202500148 Mobile Credential Wallet RFO Page 10

NIGP Codes:

204-29 Data/File Security Hardware/Software, to Include Encryption

208-81 Software For Computer Software Training, Microcomputer

470-54 Orientation or Navigational Aids for the Disabled

918-25 Compliance Consulting, Including American Disabilities Act (ADA)

920-05 Application, Infrastructure, Hosting, Data Hosting and Cloud Computing Services, Vendor Hosted and Internally Hosted

920-45 Software Maintenance and Support Services and Updates and Data Hosting Services

920-75 Technical Writing and Documentation, IT Services

961-20 Customer Service Evaluation Services

961-93 Communication Access Realtime Translation (CART) as further explained here in the ADA Requirements for Effective Communication and Closed Captioning for Broadcast Television/Webcasts

962-69 Personnel Services, Temporary

990-48 Identity Theft Protection and Data Security Services

However, you are not restricted to these services only.

Include the NIGP Code for each subcontracting opportunity identified in Section 2: Respondent’s Subcontracting Intentions, on the Subcontracting Opportunity Description line of the HSP.

Submit supporting documentation (i.e., email, fax, certified letter) demonstrating good faith effort to notify Texas HUBs and Trade Organizations or Development Centers.

B. HUB Subcontractors

i. Locate a list of HUB subcontractors on the Centralized Masters Bidders List (CMBL) at:

https://mycpa.cpa.state.tx.us/tpasscmblsearch/tpasscmbls earch.do.

ii. Select HUBs Only, Multiple Vendor Search, Enter NIGP Class / Item Code and Highway District #, click on Search.

iii. Please note: Texas HUB vendors must have an active (A) https://mycpa.cpa.state.tx.us/tpasscmblsearch/tpasscmblsearch.do https://mycpa.cpa.state.tx.us/tpasscmblsearch/tpasscmblsearch.do

3202500148 Mobile Credential Wallet RFO Page 11 certification on the date the solicitation is due. If the vendor’s HUB certification expires before the solicitation due date the HSP will be rejected as a failure to comply with the Good Faith Effort (GFE).

3.5 Response Deadline and Submission Requirements

1. Respondents are required to submit Responses in accordance with the requirements outlined in this document. Responses must be received by TWC on or before the date and time specified in RFO Section 3.3 Schedule of Events. No late Responses will be reviewed.

2. The system clock in the TWC electronic mail address is the official timepiece for determining compliance with the deadline.

3. Responses must be e-mailed to the designated email address in Section

3.1. TWC only accepts emailed responses. Responses received after the submission deadline will be disqualified. Note: TWC does not accept emailed responses that include html link(s) or encrypted emails that require downloading additional software.

TWC is not responsible for responses emailed late, illegible, incomplete, or otherwise considered disqualified due to failure of electronic equipment or operator error.

4. Respondent must submit all components on its response in the form and manner specified in Section 3.6 of this RFO.

5. Respondent must submit copies of Respondent’s entire Offer, including all exhibits and attachments, in searchable portable document format (PDF) in accordance with Section 3.10.6 of this RFO.

3.6 Response Instructions

1. Respondent will follow the instructions set forth in the RFO and Attachments.

2. Each Section and Attachment of this RFO, along with any other associated files, contains individual detailed instructions regarding the required format of the Respondent’s Response. The Respondent is required to respond according to the instructions contained in each section of this

RFO.

3. Respondent’s Response must be consistent with the structure, sequencing, and terminology used in this RFO.

4. Submission of a Response indicates Respondent’s agreement that it understands the individual requirements of the RFO and will comply with

3202500148 Mobile Credential Wallet RFO Page 12 them unless specifically stated otherwise by the Respondent.

3.6.1 No Marketing Materials

Brochures or other presentations beyond those requested and required to present a complete Response will not be reviewed.

3.6.2 Response organization

Respondent shall organize Response as follows:

1. Response Package 1: Administrative Submission Requirements

2. Response Package 2: Response to Technical, Functional, and Non-functional Requirements

3. Response Package 3: Price Cost Sheet

4. Response Package 4: HUB Subcontracting Plan

Response shall be a maximum of one hundred (100) pages in total across all four required Response Packages. Failure to stay within one-hundred-page limit may be grounds for disqualification per TWC’s discretion. Note: Signature pages and financial documentation are excluded from the one-hundred-page limit. All other documentation is included in the one-hundred-page limit.

3.6.3 Response Package 1: Administrative Submission Requirements

3.6.3.1 Transmittal Letter and Executive Summary

1. Respondent shall submit a transmittal letter on company letterhead, signed by an individual with authority to bind the company in a contract with TWC. The transmittal letter shall include a statement that the person signing is authorized to contractually bind the organization.

2. Respondent shall submit an Executive Summary that shall not exceed two

(2) pages in length (excluding title page). No appendices or specific references to additional information will be accepted. The Executive Summary should be written to communicate a summary of the Respondent’s Response. Respondent must not include any pricing information or estimated savings in the Executive Summary.

3. The Respondent must provide the documents in its Response, as two separate Microsoft Word documents, with such files entitled “ABC_RFO_3202500148_Transmittal_Letter.docx” and “ABC_RFO 3202500148 _Executive Summary.docx.”

3202500148 Mobile Credential Wallet RFO Page 13

Note: “ABC” in the required file name format refers to Respondent name.

3.6.3.2 Execution of Offer Form and Exceptions to Requirements

1. The Respondent shall complete and sign the Execution of Offer Form found in Attachment 2 of this RFO document. This form must be completed and signed, or the Response will be disqualified as noncompliant. By signing, Respondent agrees to provide the services described in this RFO and agrees to abide by all TWC Terms & Conditions as specified in this RFO, except to the extent exceptions are filed, and in any Contract resulting from an award.

2. Exceptions to Requirements (including exceptions to Attachment 1 TWC Terms & Conditions)

a. The final terms and conditions of any Contract shall be agreed upon during negotiation. However, the minimum required standard terms and conditions that will be included in any awarded Contract are contained in the Attachment 1 TWC Terms & Conditions included in the RFO documents.

b. Any exception included in an Offer may result in a Respondent not being awarded a Contract. If a Respondent includes exceptions in its Offer, Respondent is required to use Attachment 2, Execution of Offer Form of this RFO and provide all information requested on the form. An explanation as to why the Respondent cannot comply with the provision, term, or condition and why the proposed alternative language must be included in the Response. Examples of nonresponsive explanations include:

i. Referencing negotiation of revised language in another TWC or other state agency contract;

ii. Referring to an internal division’s need for the revised language without a valid reason as to why the exception is necessary;

iii. Indicating the proposed language is “negotiable”; and

iv. Referencing an internal Respondent’s terms and conditions document.

c. Exceptions must include:

i. Explanation as to why Respondent cannot comply with the term or condition; and

ii. Proposed alternate language (redline).

3202500148 Mobile Credential Wallet RFO Page 14

d. If Respondent fails to note any exception within its Response, Respondent will not be allowed to request an exception after submitting its proposal, during contract negotiations, or upon award.

e. Respondents are encouraged not to request exceptions to contract terms and conditions; TWC, in its sole discretion, may or may not accept the Respondent’s requested exceptions. Any exceptions or deviations by Respondent to Attachment 1 TWC Terms & Conditions (T&Cs), may make the offer unacceptable for award without discussion. If a Respondent proposes exceptions to the T&Cs, TWC may make an award without discussion to another Respondent that did not take exceptions to the T&Cs.

f. If there are no exceptions, the Respondent shall explicitly state the Respondent takes no exception to any part of this RFO. Any exception may result in the Contract not being awarded to the Respondent.

3. The Respondent must provide, as a separate Microsoft Word document, a file entitled ABC_RFO_3202500148_ExecutedOfferForm (.docx or .pdf)

3.6.3.3 Minimum Respondent Experience and Proposed Solution

Qualifications

Respondent must clearly state how it meets the required minimum qualifications listed below, and provide that information in a separate Microsoft Word document, in a file entitled ABC_RFO_3202500148_Qual.docx. Respondents that do not meet the minimum qualifications listed below will be disqualified from consideration.

1. Respondent must have either recently been in business or the principals/owners must have had ownership/executive in a previous company, for a minimum of five (5) years, directly supporting and managing a Mobile Credential Wallet solution similar in size and complexity to the Mobile Credential Wallet solution as required in this

RFO.

2. Solution version proposed must be fully built, fully tested, production ready, and must have been in production use for a minimum of one-year.

3.6.3.4 Financial Soundness

The Respondent must include Attachment 16 Financial Questionnaire with your response. Failure to include a document titled “ABC_RFO_3202500148_FinancialQuestionnaire.docx” may result in

3202500148 Mobile Credential Wallet RFO Page 15 disqualification of the Respondent’s Response. If TWC learns of a failure to disclose after a Contract has been awarded to the Successful Respondent, the Contract may be terminated. In the event of such termination, the Successful Respondent shall be liable for all costs associated with the re-procurement, including any increased costs for the services originally awarded.

3.6.3.5 Addenda to the RFO

To acknowledge receipt of all Addenda, the Respondent shall provide a completed and signed “page one” of each Addendum.

3.6.3.6 Attachment 3 Voluntary Product Accessibility Template

(VPAT)

Respondent must provide Attachment 3 Voluntary Product Accessibility Template, as stated in Section 2.3 Electronic and Information Resources (EIR) Accessibility of this RFO.

3.6.3.7 Attachment 4 Policy Driven Adoption for Accessibility

(PDAA)

Respondent must provide Attachment 4 Policy Driven Adoption for Accessibility as stated in 2.3 Electronic and Information Resources (EIR) Accessibility of this RFO.

3.6.3.8 Cybersecurity Certifications

Respondent must provide Attachment 13 Cybersecurity Requirements and Certifications, as stated in Attachment 13 Cybersecurity Certifications.

3.6.3.9 Substitute W-9 and Direct Deposit Form

Respondent must provide completed Attachment 14: Substitute W-9 and Direct Deposit Form if they do not currently have a contract with TWC.

3.6.3.10 Response Package 1 Files

The following table summarizes the files to be included in Package 1 with the corresponding file names.

3202500148 Mobile Credential Wallet RFO Page 16

Table 2: Response Package 1 Files

RFO Reference Form of Response

Respondent Transmittal Letter “ABC_RFO_3202500148_Transmittal_Letter .docx”

Respondent Executive Summary “ABC_RFO_3202500148_Executive Summary.docx”

Attachment 2 Execution of Offer Form (EOF)

“ABC_RFO_3202500148_EOF (.docx or .pdf)

Minimum Respondent Experience and Proposed Solution Qualifications

“ABC_RFO_3202500148_Qual.docx”

Attachment 16 Respondent Financial Soundness

“ABC_RFO_3202500148_Financial Questionnaire.docx”

Addenda to the RFO (if applicable)

“ABC_RFO_3202500148 _Addenda (.docx or .pdf)

Attachment 3 VPAT (Completed) “ABC_RFO_3202500148_VPAT.docx” Attachment 4 PDAA (Completed) “ABC_RFO_3202500148_PDAA.xlsx” Attachment 12 Data Center Services (DCS) and DCS Templates (Completed)

“ABC_RFO_3202500148_DCS_Templates.d ocx”

Attachment 13 Cybersecurity (Completed)

“ABC_RFO_3202500148_CyberRequirement

s. (.docx or.pdf)

If Respondent has the following Cybersecurity certifications, include in Response Package 1 (see Attachment 13):

Cybersecurity Certification –

SSAE 18 SOC 2

“ABC_RFO_3202500148_SSAE18SOC2

(.docx or .pdf)

Cybersecurity Certification – ISO 27001

“ABC_RFO_3202500148_ISO27001 (.docx or .pdf)

Cybersecurity Certification – FedRAMP Level 1 or Level 2 Certification

“ABC_RFO_3202500148_FedRAMP (.docx or .pdf)

Attachment 14 Substitute W-9 and Direct Deposit Form (if applicable)

“ABC_RFO_3202500148_SubW9&DD_Form (.pdf)

3.6.4 Response Package 2: Response to Service Requirements

3.6.4.1 Response to Requirements in Attachment 5 Statement of Work (SOW)

Respondent will follow the instructions set forth:

3202500148 Mobile Credential Wallet RFO Page 17

Respondent’s Response must be in-line in Attachment 5 Statement of Work. Respondent shall respond to each section using blue ink as designated.

Respondent must respond as specifically requested for each section with the structure, sequencing and terminology used. This blue-line response shall be inserted within the requested section. Respondent shall fulfill all other response requirements contained.

Where instructed, Respondent shall provide attachments of the additional documentation required by TWC.

Where requested, Respondent shall acknowledge their agreement to comply with the SOW requirements or note any exceptions to the requirements of the section.

Respondent shall provide a brief description of how they will fulfill the requirements and include relevant information about the technology and value-added components of their solution.

The SOW Response shall be titled “ABC_RFO_3202500148_SOW.docx”. The response shall be limited to no more than 40 pages, inclusive of the original pages provided by TWC. The page limit includes any graphics, tables, etc., and Respondent shall not alter the font of the document in providing their Response.

3.6.4.2 Technical Solution Summary

1. Respondent shall provide a summary description of the technical solution the Respondent proposes to meet the requirements in Attachment 5 SOW Section 2 Scope.

2. The Respondent must describe the solution’s Architecture and Application Technology Stack—technical environment specifications; framework;

scalability; performance metrics; operating systems; database management system; software development language; web servers;

browsers and mobile devices supported; and reporting environment and tools.

3. The Respondent must describe the Software Development Life Cycle (SDLC) for the solutions—environments, processes and practices, controls, and tools.

4. The Respondent is encouraged to submit Diagrams, Flow Charts, Screen Shots, Wireframes, Pictures, etc., of its technical solution.

3202500148 Mobile Credential Wallet RFO Page 18

5. The electronic version shall be in Microsoft Word format and must be entitled “ABC_RFO_3202500148_TechnicalSolution.docx.”

3.6.4.3 Respondent Experience

1. In no more than five (5) pages, and in keeping with the minimum qualifications as stated in Section 3.7.3.3, Respondent shall include experience in a file entitled “ABC_RFO_3202500148 _Experience.docx.” Respondent shall provide information regarding its past relevant experience for three (3) Mobile Credential Wallet SaaS solution projects on which the Respondent served as the prime vendor within the last five (5) years. Respondent shall duplicate as necessary to provide all required experience.

2. Respondent shall use projects reflecting the markets in which it typically works (i.e., state agency, federal government, education, local governments, etc.). Respondent shall describe and/or demonstrate how the experience supports Respondent qualifications described in this RFO.

3. Respondent shall not refer to information located outside the RFO Response, such as a reference to a website, or linked document.

Respondent’s response to each section must be fully contained within the section response, without referral to a response within another section;

however, clearly marked attachments are acceptable if clearly referenced within the response to which they pertain.

3.6.4.4 Respondent References

Using Table 3 below, Respondent shall provide the name, title, contact number, and description of services provided for three (3) references for which the Respondent provided Mobile Credential Wallet SaaS Solution within the past five (5) years as the prime vendor. These references must relate to similar contracts or projects performed as described in Section 2 Scope of this RFO, and preferably, should be from state, federal, and/or local governmental entities. TWC is not responsible for undeliverable emails or for non-responsive references.

3202500148 Mobile Credential Wallet RFO Page 19

Table 3: Past Performance Reference Information

Company or Entity Name and Address

Contract Description

(including contract number, award date, operations start and end dates)

Contact Information

1.

Contact Name:

Contact Title:

Contact Phone Number:

Contact e-mail:

2.

Contact Name:

Contact Title:

Contact Phone Number:

Contact e-mail:

3.

Contact Name:

Contact Title:

Contact Phone Number:

Contact e-mail:

3.6.4.5 Terminated Contract References

1. Using Table 4: Terminated Contracts, Respondent shall provide the name, title, contact number, and description of services provided for any contract that was canceled or terminated prior to completion in the past five (5) years. Respondent shall include details on the reason for the cancellation or termination and the Respondent’s position relevant to the cancellation or termination, including the final resolution of the contract termination. Respondent shall add additional rows to Table 4: Terminated Contracts as necessary to provide all terminated contracts within the required timeframe.

3202500148 Mobile Credential Wallet RFO Page 20

Table 4: Terminated Contracts

Company or Entity Name and Address

Contract Description

(including contract award date, operations start and end dates)

Reason for Termination

Contact Information

1. Contact Name:

Contact Title:

Contact Phone Number:

Contact e-mail:

2. Contact Name:

Contact Title:

Contact Phone Number:

Contact e-mail:

3. Contact Name:

Contact Title:

Contact Phone Number:

Contact e-mail:

2. Respondent shall provide contact information for individuals able to address questions concerning the termination. Failure to fully disclose a terminated contract within the scope of this requirement will result in disqualification, if termination was known at the time the Response is submitted. If the failure to disclose is not learned by TWC until a Contract has been awarded to the Successful Respondent, the Contract may be terminated. In the event of such termination, the Successful Respondent shall be liable for all costs associated with the re-procurement, including any increased costs for the services originally awarded.

3. If there are no terminated contracts, the Respondent shall affirm such in this section.

4. Completed Table 3 and Table 4 shall be consolidated into one (1) Microsoft Word document and must be entitled “ABC_RFO_3202500148_References.docx”.

3202500148 Mobile Credential Wallet RFO Page 21

3.6.4.6 System Support

Respondent shall provide the following information:

Description of how the help and technical documentation is embedded in the Solution and accessible to TWC and End-Users.

Description of the available system support service level plans.

Description of how TWC interacts with the support team, including but is not limited to, the following:

a. How client relations are handled.

b. How TWC would report an issue.

c. How issues are tracked.

d. How issues are escalated.

Description of the lifecycle of issue resolution (initiation, response time, escalation process, resolution time, onsite assistance).

Description of the reporting capabilities of issue tracking available to TWC, including metrics on issue ticket creation, reply, escalation and resolution.

Respondent’s Response shall be in Microsoft Word format and must be titled “ABC_RFO_3202500148_SystemSupport.docx”.

3.6.4.7 System Currency

Respondent shall provide the following information:

Describe your approach to product enhancements and how future product roadmaps are communicated to a customer.

Features are on the one (1) to five (5) year roadmap for this Solution.

Respondent’s Response shall be in Microsoft Word format and must be titled “ABC_RFO_3202500148_SystemCurrency.docx”.

3.6.4.8 License Agreements

Respondent shall provide the following information:

Respondent shall state how any required Respondent provided software is licensed.

Respondent shall provide copies of any Respondent’s current license and support agreements applicable to any components of the proposed Solution, including but is not limited to: hardware, software, operation system and database.

Respondent must align the terms of any license and support agreements with the terms and conditions of Attachment 1 TWC Terms & Conditions and the RFO.

Respondent shall acknowledge and agree that TWC’s Attachment 1 TWC

3202500148 Mobile Credential Wallet RFO Page 22

Terms & Conditions will have precedence over such software license and maintenance agreements except for software license agreement provisions relating to scope and grant of license, Respondent’s ownership of its intellectual property, and Respondent’s intellectual property rights.

Additionally, Respondent shall further acknowledge and agree that if recommended for contract award, any terms and conditions in the software license agreement and/or maintenance agreement that conflict with RFO Attachment 1 TWC Terms & Conditions will be revised as needed to bring them into conformance with Attachment 1 TWC Terms & Conditions.

Respondent’s Response shall be in Microsoft Word format and must be titled “ABC_RFO_3202500148_LicenseAgreement.docx”.

3.6.4.9 Service Level Agreements

Respondent shall:

1. Describe the stability, response time to issue tickets, escalation time to issue tickets and uptime of your solution.

2. Respondent shall provide a sample monthly report of Service Level Metrics typically provided to demonstrate to clients they have met their required monthly Service Level Metrics.

Respondent’s Response shall be in Microsoft Word format and must be titled “ABC_RFO_3202500148_SLAs.docx”.

3.6.4.10 Proposed Organization

1. Respondent shall provide a proposed organization chart for the project, indicating which positions are considered Key Personnel, and describe the responsibilities of key positions and departments. Additionally, Respondent shall describe the benefits of such an organization and the time frame for implementation. The role of Subcontractors on this Contract must also be described in the proposed organization.

Respondent shall complete Table 5: Subcontractors to provide a list of the subcontractors who will provide goods or services under the Contract, including those identified in the HSP.

3202500148 Mobile Credential Wallet RFO Page 23

Table 5: Subcontractors (including HUBs)

Name of Subcontractor

(Company/Indivi dual)

Subcontra ctor Scope of Work

Location where

Subcontra ctor will Perform

Work

Anticipated Duration of Subcontrac ting Engageme nt

Check this box if subcontra ctor is a

HUB

2. Respondent must include in its Response the resumes and qualifications of all proposed Respondent Key Personnel, including their specific experience working on related projects. Resumes should specifically detail experience working on projects and services of similar scale and complexity as the services sought through this RFO, including work on projects used as references. Resumes shall not be more than two (2) pages in length.

3. The Response must include actual names of Key Personnel initially assigned to the project, their resumes, not simply generic resumes with the types of skills sought. Successful Respondent’s Key Personnel are required to remain on the project a minimum of six months from project kickoff date and, if Respondent is selected for a demonstration, Key Personnel must attend the demonstration. The Respondent must provide these resumes as attached pages at the end of the “Proposed Organization Chart” document.

4. Respondent must provide, as a separate Microsoft Word document, a file entitled “ABC_RFO_3202500148_ProposedOrganizationChart.docx.”

3.6.4.11 Response Package 2 Files

1. The table below summarizes the files to be included in Package 2 with the corresponding file names, with a description of each file to follow.

2. Files to be included in Package 2 are summarized in the table below:

3202500148 Mobile Credential Wallet RFO Page 24

Table 6: Response Package 2 Files

RFO Reference Form of Response Response to Requirements in Attachment 5 SOW “ABC_RFO_3202500148_SOW.docx”

Technical Solution Summary “ABC_RFO_3202500148_TechnicalSolutio n.docx”

Respondent Experience “ABC_RFO_3202500148_Experience.docx” Respondent References (See Table 3) and Respondent Terminated Contracts (See Table 4)

“ABC_RFO_3202500148_References.docx

System Support “ABC_RFO_3202500148_SystemSupport.

docx”

System Currency “ABC_RFO_3202500148_SystemCurrency.

docx”

License Agreement “ABC_RFO_3202500148_LicenseAgreeme nt.docx”

Service Level Agreements “ABC_RFO_3202500148_SLAs.docx”

Proposed Organization “ABC_RFO_3202500148_ProposedOrganiz ation.docx”

3.6.5 Response Package 3: Pricing

1. Respondent shall use Attachment 6 Pricing Worksheet and provide a detailed written response.

2. Respondent shall use Attachment 7 Pricing Assumptions to list assumptions, if any, associated with the proposed Charges and Services submitted with Attachment 6 Pricing Worksheet.

3. The following table summarizes the files to be included in Package 3 with the corresponding file names.

Table 7: Response Package 3 Files

RFO Reference Form of Response Attachment 6 Pricing Worksheet (Completed)

“ABC_RFO_3202500148_Pricing Worksheet”

Attachment 7 Pricing Assumptions (Completed if applicable)

“ABC_RFO_3202500148_Pricing Assumptions”

3202500148 Mobile Credential Wallet RFO Page 25

RFO Reference Form of Response Respondent Form of Invoice

“ABC_RFO_3202500148_Form of Invoice”

3.6.6 Response Package 4: Completed HUB Subcontracting Plan

3.6.6.1 HUB Subcontracting Plan – Attachment 9 HSP Form

1. All Respondents, INCLUDING THOSE WITH HUB DESIGNATION AND THOSE THAT DO NOT PLAN TO USE SUBCONTRACTORS, must submit a HUB Subcontracting Plan (HSP) using Attachment 9 HUB Subcontracting Plan. The HSP should be labeled “ABC_TWC_ RFO_3202500148_HUB Subcontracting_Plan.pdf” and include all supporting documentation in accordance with Attachment 9 HUB Subcontracting Plan. Refer to Section 3.4 Historically Underutilized Businesses for more information regarding HUB subcontracting.

2. Courtesy Review of HSP

a. A courtesy review of a Respondent’s completed HSP by TWC is optional and is available upon request to assist Respondent in providing a compliant and responsive HSP. This courtesy review may only identify possible deficiencies, and a final compliant determination cannot be provided until the Offer is submitted.

b. To request a courtesy review, submit the completed HSP, including all supporting documentation, in a PDF format by email to the TWC HUB Program Office by or…