RFO DIR-CPO-STS-609_MNS_Final.docx
DOCX document 178 KB Posted
- Attached to
- Managed Network Services (MNS)
- Solicitation number
- DIR-CPO-STS-609
- Issued by
- Travis County, Austin City, Texas
About this file
This Request for Offer (RFO DIR-CPO-STS-609) is issued by the Texas Department of Information Resources (DIR) to procure a single Managed Network Services (MNS) vendor for the Shared Technology Services (STS) program. The MNS service component provider will deliver network design, configuration, management, support, governance, risk, and compliance assessments to eligible state and local government entities enrolled in the STS program. Services are designed particularly for entities constrained by size, budget, or staff. The RFO was issued on July 20, 2026, with a mandatory bidder's conference scheduled for August 5, 2026, at 2:00 PM CT via Zoom. Written questions must be submitted by August 17, 2026, at 2:00 PM CT, and responses are due by September 4, 2026, at 2:00 PM CT. DIR anticipates contract award in May 2027, followed by a transition period through August 2027. The contract term is approximately four years with optional renewals of up to four years, for a total anticipated contract award of between eight to ten years. The RFO specifies multiple class items (205, 206, 208, 209, 838, 915, 918, 920, 939) with associated line items.
Respondents must meet minimum qualification requirements including five or more years' experience providing managed network services in a multi-supplier environment within the past ten years and at least three contracts for similar major activities within the last five years with minimum annual contract values of $1,000,000 per contract. DIR will conduct evaluations using weighted criteria: Technical Solution (45 percent), Transition and Service Integration (20 percent), Pricing (15 percent), Proposed Account Organization and Personnel Experience (15 percent), and Experience (5 percent). All responses must include completed accessibility documentation, financial information, subcontracting plans, and pricing in accordance with specified templates. Respondents are discouraged from taking exceptions to the Master Services Agreement terms and conditions, as excessive exceptions may result in disqualification. Pricing and financial details must be submitted in separate response packages with specified Microsoft Office formats. The procurement includes provisions for discussion sessions, integration sessions with other service component providers, due diligence activities, and negotiations with selected respondents to determine best value for the State.
View the file
Other files
Show all 23
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
RFO DIR-CPO-STS-609
State of Texas Department of Information Resources
Managed Network Services (MNS) Request for Offer
DIR-CPO-STS-609
| Class |
| Item |
| 205 |
| 46, 64, 91 |
| 206 |
| 14, 20, 23, 56, 64, 87, 89 |
| 208 |
| 27, 90, |
| 209 |
| 28, 91 |
| 838 |
| 33, 83, 91 |
| 915 |
| 26, 79 |
| 918 |
| 30 |
| 920 |
| 05, 29, 31, 35, 37, 66 |
| 939 |
| 21 |
Issued: July 20th, 2026 Responses Due: September 4th, 2026, 2:00pm CT
SOLICITATION CONTENTS
The list below contains a summary of the documents comprising this Request for Offer (RFO) issued by DIR. The Successful Response shall be responsible for fulfilling all requirements contained in these documents.
Request For Offer (RFO) DIR-CPO-STS-609 Attachments:
Attachment A: Respondent Information Form Attachment B: Technical Solution Summary Attachment C: Policy Driven Adoption for Accessibility (PDAA) - Vendor Self-Assessment Attachment D: Voluntary Product Accessibility Template® (VPAT®) Attachment E: Vendor Accessibility Development Services Information Request (VADSIR) Attachment F: Request for Offer Questions Template Attachment G: Exceptions Attachment H: State of Texas Subcontracting Plan (SP) Master Services Agreement (MSA) with Exhibits Attachment 1: Definitions Attachment 2: Insurance and Risk of Loss Attachment 3: Form of Source Code Escrow Attachment 4: Form of Parent Guaranty Attachment 5: CJIS Security Addendum Request For Offer (RFO) DIR-CPO-STS-609 Exhibits Exhibit 1 – Statement of Work with Attachments and Appendices Attachment 1.1 Service Level and Deliverable Matrix Attachment 1.2 Service Level Definitions Attachment 1.3 Service Management Manual (SMM) Content and Organization Attachment 1.4 Key Personnel Appendices Appendix A – Reports Exhibit 2 – Financial Provisions and Pricing Requirements with Attachments Attachment 2.1 Pricing and Volumes Attachment 2.2 Financial Responsibility Matrix
TABLE OF CONTENTS
| 1. | INTRODUCTION | 5 |
| 1.1. | Objective | 5 |
| 1.2. | Statutory Authority | 5 |
| 1.2.1 | Precluded Vendors | 5 |
| 1.3. | Background and Overview | 5 |
| 1.4. | Vision | 6 |
| 1.5 | Eligible Customers and STS Program Restrictions | 6 |
| 1.6 | Stakeholders | 6 |
| 2. | SCOPE | 8 |
| 2.1 | Required Services - Purpose | 8 |
| 2.2 | Electronic and Information Resources (EIR) Accessibility | 8 |
| 2.3 | ACR Submission and Review | 9 |
| 2.4 | VADSIR Submission and Review | 10 |
| 2.5 | PDAA Submission and Self-Assessment Score | 10 |
| 2.6 | Form of Contract | 11 |
| 2.7 | Term of Contract | 11 |
| 3. | GENERAL INFORMATION | 11 |
| 3.1 | Point of Contact | 11 |
| 3.2 | Response Integrity | 12 |
| 3.3 | Schedule of Events | 12 |
| 3.3.1 | Bidder’s Conference | 13 |
| 3.4 | Federal and State Requirements | 14 |
| 3.4.1 | Federal Requirements | 14 |
| 3.4.2 | Performance and Debarment | 15 |
| 3.4.3 | Required Successful Respondent and Subcontractor Current and Former State Employee Disclosures | 15 |
| 3.5 | Response Submission Requirements | 15 |
| 3.5.1 | Response Deadline | 15 |
| 3.5.2 | Response Instructions | 16 |
| 3.5.3 | No Marketing Materials Desired | 16 |
| 3.5.4 | Response Format | 17 |
| 3.5.5 | Rejection of Responses | 17 |
| 3.5.6 | Right to Amend or Withdraw RFO | 17 |
| 3.5.7 | Pre-Agreement Costs | 18 |
| 3.5.8 | Ownership of Responses | 18 |
| 3.5.9 | Public Information | 18 |
| 3.5.10 | News Release | 19 |
| 3.5.11 | Response Organization | 19 |
| 3.5.12 | Response Package 1: Administrative Submission Requirements | 20 |
| 3.5.13 | Response Package 2: Response to Service Requirements | 24 |
| 3.5.14 | Response Package 3: Pricing | 35 |
| 3.5.15 | Response Package 4: Completed State of Texas Subcontracting Plan Form | 36 |
| 4. | EVALUATIONS, NEGOTIATIONS, AND AWARD | 37 |
| 4.1 | Evaluation of Responses | 37 |
| 4.2 | Evaluation Criteria | 38 |
| 4.2.1 | Pass/Fail Criteria | 38 |
| 4.2.2 | Evaluation Criteria | 39 |
| 4.3 | Revised Offer | 40 |
| 4.4 | Due Diligence | 40 |
| 4.5 | Negotiations | 40 |
| 4.6 | Award of Contract | 40 |
| 4.7 | Protest Procedures | 41 |
1. INTRODUCTION
1.1. Objective
Through this Request for Offer (“RFO”), the Texas Department of Information Resources (“DIR”) seeks to procure a vendor for Managed Network Services (“MNS”) to be provided to eligible DIR Customers through DIR’s Shared Technology Services (“STS”) program. DIR invites interested parties that meet the RFO qualifications to submit proposals regarding their solutions and related service offerings (the submitting parties “Respondents” and the submissions “Responses”). All information shall be submitted in the format stipulated in this RFO. Capitalized terms used but not defined in this document shall have the meanings provided to them in MSA Attachment 1 Definitions.
As a result of this RFO, DIR expects to receive and evaluate proposal Responses and select one (1) Respondent with whom to enter a contract (such Respondent a “Successful Respondent”) for the services described herein. Article 4 EVALUATIONS, NEGOTIATIONS, AND AWARD contains more information regarding the Response evaluation and vendor selection process.
1.2. Statutory Authority
DIR has authority to complete the objectives of this procurement. DIR is authorized to enter into this Agreement under Chapter 2054, specifically including Section 2054.0565 and Subchapters F, I, and L; and Section 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.
1.2.1 Precluded Vendors
The vendor and subcontractors performing the Multi-sourcing Services Integrator functions for the STS program are precluded from award of a contract resulting from this RFO, due to the oversight functions and independence required.
DIR may identify additional areas of conflict in the future. Should this be the case, DIR will note the preclusions in the applicable solicitations. Preclusions are subject to change at DIR’s discretion.
1.3. Background and Overview
MNS is a new Service Component Provider (“SCP”) within the STS program for the State of Texas, acting by and through DIR. The MNS SCP will provide DIR customer entities access to network best practices, services, and security protections, particularly for entities constrained by size, budget, or staff. MNS may include network design, configuration, management, support as well as governance, risk, and compliance assessments.
Successful Respondent will be responsible for delivering managed network services in a manner that maximizes value for the State by utilizing emerging technology coupled with best industry practices.
1.4. Vision
Successful Respondent will deliver to DIR Customers top-tier network services that minimize risks, enhance security, and modernize state government systems.
DIR desires the Successful Respondent achieve the following outcomes:
1. Maintain networks to meet the demands of eligible DIR Customers.
2. Improve access to network resources, best practices, and security protections, particularly for entities constrained by size, budget, or staff.
3. Identify network gaps through rigorous assessments and proactively mitigate those risks.
4. Provide expertise and capacity to facilitate modernization of legacy networks.
1.5 Eligible Customers and STS Program Restrictions
Eligible DIR Customers include state and local government entities, as provided by Section 2054.0525, Texas Government Code. All STS-enrolled DIR Customers are eligible to purchase MNS.
MNS is distinct from and complimentary to the Telecom Managed Services offered under DIR’s Texas Agency Network (“TEX-AN”) contracts. The TEX-AN Telecom Managed Services procurement model requires DIR Customers to develop a specific statement of work for managed services; whereas, the proposed STS Managed Network Services are predefined services within the STS program, as detailed in this RFO.
For further clarity, this RFO is not a solicitation for telecommunications services or as part of the consolidated telecommunications system under Chapter 2170, Texas Government Code. DIR Customers will continue to procure telecom and voice platform services through the TEX-AN program. Those services are not within the scope of this RFO.
1.6 Stakeholders
Successful Respondent shall work with the appropriate stakeholders to provide the Services. A summary of key stakeholders the Successful Respondent shall engage with as part of providing the Services is provided in Table 1 Stakeholder Overview.
Table 1 Stakeholder Overview
| # |
| Stakeholder |
| Description |
| 1 |
| DIR |
| DIR operates a sourcing management and governance organization that performs customer relationship leadership, service and sourcing strategy, service portfolio management, and contract and financial management roles. |
| 2 |
| MSI |
| The MSI integrates all SCPs within the STS program. Successful Respondent will leverage and integrate with the MSI-provided capabilities as described in Exhibit 1 (SOW) to deliver supply-side services. These capabilities include integration with the MSI-provided cross-functional processes and systems. |
| 3 |
| DIR Customers |
| The STS program enables DIR Customers such as state agencies, local government, and institutions of higher education the ability to share in technology managed services contracts. |
| 4 |
| TPC |
| Texas Private Cloud (TPC) manages the DCS private cloud assets and capabilities. Successful Respondent will work with the Texas Private Cloud SCP in the implementation, optimization and restoration of services related to Security Incidents, Vulnerability identification and remediation, patch compliance, and integration of security systems with the MSI. |
| 5 |
| PCM |
| Public Cloud Manager (PCM) manages State agency workloads in the four public clouds: AWS, Azure, Google, and Oracle. Successful Respondent will work with the Public Cloud Manager SCP in the implementation, optimization and restoration of services related to Security Incidents, Vulnerability identification and remediation, patch compliance, and integration of security systems with the MSI. |
2. SCOPE
2.1 Required Services - Purpose
As a result of this RFO, DIR expects to receive and evaluate Responses and select one (1) qualified Respondent with whom to enter into negotiations. Article 4 EVALUATIONS, NEGOTIATIONS, AND AWARD contains more information regarding evaluation and the Respondent selection process.
2.2 Electronic and Information Resources (EIR) Accessibility
1. Under Texas Government Code Chapter 2054, Subchapter M, and DIR implementing rules, DIR’s state agency and institution of higher education customers must procure EIR that complies with the accessibility standards defined in Texas Administrative Code Chapters 1 TAC 206 and 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 the following accessibility documentation (when applicable) in an accessible format:
a. For each commercial product (also referred to as commercial off the shelf or COTS), and service products such as Software as a Service (SaaS), Platform as a Service (PaaS), and any other managed services that include a user interface, a completed Accessibility Conformance Report (ACR) or the specific URL to view the ACR online. See RFO Section 2.3 ACR Submission and Review for detailed requirements.
b. For non-product offerings (such as IT related development services, services that include user interfaces, managed services, online components, etc.), a Vendor Accessibility Development Services Information Request (VADSIR), which documents Respondent's capability or ability to produce or customize accessible EIR (also referred to as Information and Communications Technology (ICT)). Support documentation and documentation as part of the final deliverable must be provided in an accessible format. Section 2.4 VADSIR Submission and Review for detailed requirements.
c. The Policy Driven Adoption for Accessibility (PDAA) for Vendor Self-Assessment. Section 2.5 PDAA Submission and Self-Assessment Score.
3. Responses with missing or incomplete required accessibility documentation may fail the EIR accessibility evaluation and be disqualified.
2.3 ACR Submission and Review
1. All Respondents must provide ACRs created using the applicable sections of the Voluntary Product Accessibility Template® (VPAT®) Revised Section 508 Edition (version 2.4 or higher), WCAG (version 2.4 or higher), or provide the specific URL to the online ACR on the manufacturer(s)’ websites (where available) for every product (as defined above) or product family (as applicable) included in the submitted pricelist. Instructions on how to complete this document are included in the template itself. The template is included in this RFO as Attachment D: Voluntary Product Accessibility Template® (VPAT®).
2. Respondents claiming that a proposed product or family of products is exempt from accessibility requirements must specify the product(s) as such in “Notes” located in the product information section of the VPAT v.2.4 or higher, specifying each exempt product or product family with a supporting statement(s) for this position.
3. Respondents that do not already have accessibility documentation should complete the form included in the bid package or may obtain the form located here: http://www.itic.org/public-policy/accessibility. Resellers should obtain an ACR(s) from the manufacturer or provide the specific URL for the online ACR on the manufacturer’s website.
4. For responses with greater than 10 ACRs, DIR will review a random sample of ACRs for credibility and completeness.
5. Respondents that submit incomplete ACRs or are unable to provide or obtain ACRs for products it manufactures or for products from manufacturers it represents, may be required to submit a letter (Accessibility Statement) stating that some or all product(s) accessibility documentation may be missing, product accessibility is untested, and an explanation of alternate accommodation.
2.4 VADSIR Submission and Review
1. Respondents must ensure that accessibility standards and best practices are integrated into key phases of the project development lifecycle including but not limited to, planning, design, development, functional testing, user acceptance testing, and maintenance; and report accessibility status at key project checkpoints as defined by DIR Customers.
2. Respondents must complete a VADSIR Questionnaire to document the Respondent's capability or ability to produce accessible EIR and ICT if the response includes one or more of the following offerings:
a. Website development services
b. Web Application Development Services
c. Custom development services as part of an integrated solution
d. Client-based software application development services
e. Other software development services containing one or more user interfaces (end user, administrative, etc.)
3. Support documentation and documentation as part of the final deliverable must be provided in an accessible format.
4. VADSIRs will be evaluated by DIR for credibility and completeness.
2.5 PDAA Submission and Self-Assessment Score
1. All Respondents must complete Attachment C: Policy Driven Adoption for Accessibility (PDAA) - Vendor Self-Assessment for responses that include technology products and services. The PDAA generates a self-assessment score which is an indicator of the Respondent’s organizational accessibility maturity or how the organization has implemented accessibility best practices within its operations and business processes. The PDAA is an organizational assessment, not an assessment of the products or services listed in the vendor’s response.
2. A missing, incomplete, blank, or zero-score PDAA may fail the EIR accessibility review and result in disqualification.
2.6 Form of Contract
The final terms and conditions of any Contract will be agreed upon during negotiation. However, the minimum standard terms and conditions that will be included in any awarded Contract are contained in the Master Services Agreement (MSA) included with the RFO documents.
Section 3.5.13.6 Exceptions to Requirements (including MSA Terms and Conditions) of this RFO contains the format for Respondents to note any exception to any provision, term, or condition specified in the RFO documents. Any objections or exceptions should be noted in keeping with RFO Section 3.5.13.7.
DIR reserves the right to make changes to the MSA if it is in the best interest of the State. Should this occur prior to the award of any Contract as a result of this RFO, any Respondents selected for negotiations will be notified.
2.7 Term of Contract
DIR anticipates that the term of the Contract will be approximately four (4) years with optional renewals of up to four (4) years. The length of this term may be adjusted as necessary to account for a period of transition services or a stub period at the end of a fiscal year, for a total anticipated contract award of between eight (8) to ten (10) years, to be determined prior to Contract award. In the event of prolonged Contract negotiations, DIR may determine that it is in the best interests of the State to bypass the Respondent and commence negotiations with the next-highest scoring Respondent or continue with the current Respondent with a shorter contract term.
3. GENERAL INFORMATION
3.1 Point of Contact
Correspondence shall be directed to the sole point of contact for this procurement as follows:
Cassandra Holmes, CTCM, CTCD Texas Department of Information Resources Chief Procurement Office Thomas Jefferson Rusk Building 208 E. 10th St, 3rd Floor Austin, TX 78701 Phone: 512-475-4873 Email: Enterprise609@dir.texas.gov Respondents shall make no contact concerning this RFO with other DIR personnel, except as permitted by the point of contact. Failure to comply with this requirement may result in disqualification.
3.2 Response Integrity
To ensure the integrity of the competitive process, a Respondent may not directly or indirectly communicate any of the contents of its Response to:
1. A competitor of the Respondent;
2. 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
3. A related entity of the Respondent engaged in the same line of business as the Respondent.
This prohibition is in effect during the preparation of the offer and while the offer is pending with DIR, 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 agreements with one another to provide services under a contract with a third party but otherwise have no legal relationship with each other.
When a related entity of the Respondent (whether related at the time Responses are due or at any time thereafter) submits a competing offer, DIR may require additional information to ensure each separate Response is independent. Failure to provide or fully disclose all such information may, at DIR’s discretion, disqualify Respondent or result in the termination of any resulting contract. RESPONDENT HAS AN ONGOING DUTY TO UPDATE ALL INFORMATION INCLUDED IN ITS RESPONSE AT ANY TIME THAT SUCH INFORMATION CHANGES.
3.3 Schedule of Events
DIR anticipates the following schedule for this RFO. DIR reserves the right to modify these dates at any time. Modifications to the schedule will be posted on the Electronic State Business Daily (“ESBD”) website.
Table 2 Schedule of Events
| Activity |
| Date |
| RFO Publication to ESBD |
| July 20, 2026 |
| Bidder’s Conference |
| August 5, 2026, 2:00 PM CT |
| RFO Question Submission Deadline |
| August 17, 2026, 2:00 PM CT |
| RFO Response Submission Deadline |
| September 4, 2026, 2:00 PM CT |
| Clarification, Evaluation, and Revised Responses |
| August 2026 – December 2026 |
| Integration Sessions, Due Diligence, and Negotiations |
| December 2026 – May 2027 |
| Contract Award |
| May 2027 |
| Transition |
| Date of Award through August 2027 |
3.3.1 Bidder’s Conference
DIR will hold a virtual Bidder’s Conference webinar for this procurement on the date and time listed above. It is recommended that at least one (1) Respondent representative be present at the conference.
The conference will provide overview information of the RFO and may provide preliminary answers to questions submitted prior to the Bidder’s Conference. Only answers provided in writing by DIR during the formal question and answer period shall be considered official. Information in any form other than the materials constituting this RFO and its Exhibits, the question-and-answer document(s), and any addenda shall not be binding on DIR. DIR reserves the right to amend answers prior to the offer submission deadline.
ATTENDANCE AT THE BIDDER’S CONFERENCE IS HIGHLY RECOMMENDED.
The Bidder’s Conference will be available live via the web. To participate in this live interactive webcast, you must register at:
https://www.zoomgov.com/webinar/register/WN_KCWmsYpNRkSTEiz7FaE9RA
3.3.1.1 Written Questions and Official Answers
Using RFO Attachment F (Request for Offer Questions Template) Each question submitted must include reference to the associated RFO document, section, (or cell reference if spreadsheet).
, Respondents shall submit all questions regarding this RFO via email 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 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 https://www.txsmartbuy.com/esbd.
By submission of a question, Respondents acknowledge that the applicable question will be posted with each official answer; therefore, Respondents should not include any confidential or proprietary information in such questions. DIR will not publish the identity of any Respondent that submitted any particular inquiry.
Wherever possible, DIR encourages Respondents to use this process to resolve any questions regarding this RFO rather than submitting assumptions or exceptions with its Response. DIR will make a good faith effort to answer all questions submitted. However, DIR may elect not to provide substantive answers to questions that are vague, overly broad, or unrelated to this RFO. Each question submitted must include reference to the associated RFO document, section, (or cell reference if spreadsheet).
3.3.1.2 Digital Data Room
To aid Respondents in preparing a Response, a digital data room has been created. Respondents may request access to the digital data room once they have executed DIR’s non-disclosure agreement (NDA) and have completed the access request available at this location:
https://dir.texas.gov/managed-network-services-MNS-procurement-rfo-dir-cpo-sts-609-digital-data-room Upon accessing the above link, prospective Respondents should:
1. Request access to the digital data room via the online form,
2. Download and execute (digitally sign) the NDA, and
3. Send it to the point of contact identified in Section 3.1 hereof, by email.
DIR will then make a determination and notify prospective Respondent of its decision.
DIR will continue to add information to the digital data room throughout this procurement. Updates will be announced via addendum. Respondents are responsible for checking the Electronic State Business Daily (ESBD) regularly to avoid missing important procurement-related information.
3.4 Federal and State Requirements
3.4.1 Federal Requirements
State agencies are prohibited from doing business with terrorists and terrorist organizations. Any Respondent listed in the Federal Excluded Persons List System (EPLS) authorized by Executive Order #13224, "Blocking Property and Prohibiting Transactions with Persons Who Commit, Threaten to Commit, or Support Terrorism”, available at https://www.state.gov/j/ct/rls/other/des/143210.htm, published by the United States Department of the Treasury, Office of Foreign Assets Control (Terrorism List) shall not be awarded a Contract as a result of this RFO. The Successful Respondent must agree that if at any time during the term of the Contract the Successful Respondent is listed on the terrorism list, the Successful Respondent shall promptly notify DIR. As part of DIR’s contract management, periodic checks will be performed to ensure the Successful Respondent remains in compliance with these federal requirements. DIR shall have the absolute right to terminate the contract without recourse in the event the Successful Respondent becomes listed on the terrorism list.
Should the Successful Respondent become suspended or debarred from doing business with the federal government as listed in the System for Award Management (SAM), available at https://sam.gov/content/home, maintained by the General Services Administration, the Contract may be terminated without recourse, at DIR’s sole discretion.
The Successful Respondent shall comply with the requirements of the Immigration and Reform Act of 1986, the Illegal Immigration Reform and Immigrant Responsibility Act of 1996 ("IIRIRA"), and the Immigration Act of 1990 (8 U.S.C.1101, et seq.) regarding employment verification and retention of verification forms for any individual(s) hired on or after the effective date of the 1996 Act who will perform any labor or services under the Contract.
3.4.2 Performance and Debarment
In accordance with 34 Texas Administrative Code, Chapter 20, Subchapter G, any vendor that is debarred from doing business with the State of Texas will not be awarded a contract under this solicitation. The list of debarred vendors is located on the Texas Comptroller of Public Accounts (TCPA) website at https://comptroller.texas.gov/purchasing/programs/vendor-performance-tracking/debarred-vendors.php
3.4.3 Required Successful Respondent and Subcontractor Current and Former State Employee Disclosures Respondent will certify, on behalf of itself and all its Subcontractors, that they are in compliance with Texas Government Code, Title 6, Subtitle B, Section 669.003, relating to contracting with the executive head of a state agency. If Section 669.003 applies, Respondent will complete the following information for the Response:
1. Name of Former Executive;
2. Name of State Agency;
3. Date of Separation for State Agency;
4. Position with Respondent; and
5. Date of Employment with Respondent.
3.5 Response Submission Requirements
3.5.1 Response Deadline
Respondents are required to submit Responses in accordance with the requirements outlined in this document.
Responses must be received by DIR on or before the date and time specified in RFO Section 3.3 Schedule of Events. DIR will not accept any Responses received after the Response Deadline. No late Responses will be reviewed.
Respondents shall respond electronically via email, providing Responses in an electronic format (i.e., Microsoft Word files submitted together in a .zip folder) at the date and time specified in Section 3.3 to Enterprise609@dir.texas.gov.
Non-submission of any of the requested information by the date and time specified in Section 3.3 may disqualify the Respondent’s Response from further consideration by DIR.
3.5.2 Response Instructions
Respondent will follow the instructions set forth in the following Exhibits and Attachments to this RFO.
Each section, Exhibit, 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.
Respondent’s Response must be consistent with the structure, sequencing, and terminology used in this RFO. Where provided, the Respondent must use the files enclosed with the RFO and the prescribed format to submit its Response.
Electronic responses are required. Respondents shall follow the specific naming conventions detailed in this section. Respondents must use a three-letter identifier preceding each named file (e.g., Big Service Company, Inc., “BSC”). This three-letter identifier shall replace the “ABC” referenced in the filenames below. All files submitted by the Respondent should use the same three-letter identifier.
Respondents should note that DIR expects each Respondent to comply with the requirements of this RFO as written, and to price its Response accordingly. DIR strongly discourages any Respondent from indicating that it does not agree or does not comply with a provision because the Respondent is unwilling to price it (for risk, liability, or any other reason).
Non-submission of any of the requested information may disqualify the Respondent’s Response from further consideration by DIR.
3.5.3 No Marketing Materials Desired
Unnecessarily elaborate brochures or other presentations beyond those requested and sufficient to present a complete Response are not desired. Respondents are encouraged not to provide materials beyond what is required in the RFO. If provided, marketing materials will be counted toward the maximum page counts as outlined below.
3.5.4 Response Format
Respondent’s complete Response submitted shall be organized in the four (4) packages as described in Section 3.5.11 Response Organization. The four (4) packages should be submitted as four (4) separate .zip folders with the required files for each package included in the .zip folder. Each package shall be clearly saved and labeled following the naming conventions identified for that package.
All documents created by the Respondent shall be formatted as follows:
1. Paper size: 8.5 x 11 inch; or 8.5 x 14 inch where appropriate.
2. Font parameters: Arial, 11-point font (except for footnotes, headers, tables, table titles, table graphics, or footers).
3. Maximum number of pages: as specified for each document below.
4. Ready for printing: all electronic files submitted will be pre-formatted for printing.
5. Software: all electronic files submitted should be created (or fully compatible) with the current versions of Microsoft Office 365 or Microsoft Project Software suites or packages. Except for documents that are to be signed, Respondents are encouraged NOT to use PDF files.
6. Respondents shall not submit password protected files.
3.5.5 Rejection of Responses
DIR has sole discretionary authority and reserves the right to reject any and all Responses received as a result of this RFO. Responses that do not comply with the mandatory submission requirements may be rejected. In addition, DIR reserves the right to accept or reject, in whole or in part, any Responses submitted, and to waive minor technicalities when in the best interest of the State.
3.5.6 Right to Amend or Withdraw RFO
DIR reserves the right to alter, amend, or modify any provision of this RFO, or to withdraw this RFO, in whole or in part, at any time prior to the award of a Contract if doing so is in the best interest of the State. DIR reserves the right to re-solicit for like or similar products and services whenever it determines re-solicitation to be in the best interest of the State.
Any changes or additional information regarding this RFO will be posted as an addendum on the ESBD, at https://www.txsmartbuy.com/esbd. It is the responsibility of Respondents to monitor the website for addenda. Respondent’s failure to periodically check the ESBD will in no way release the Respondent from addenda or additional information resulting in additional costs to meet the requirements of the RFO.
3.5.7 Pre-Agreement Costs
DIR shall not be responsible or liable for any cost incurred by any Respondent in the preparation and submission of its Response to this RFO or for other costs incurred by participating in this procurement process.
3.5.8 Ownership of Responses
All Responses become the property of DIR. DIR reserves the right to use any and all information or materials presented in response to this RFO. Disqualification of a Respondent’s Response does not eliminate this right.
3.5.9 Public Information
DIR is a government agency subject to the Texas Public Information Act. Responses submitted to DIR as a result of this RFO are subject to release as public information. Responses of Successful Respondents will be published on DIR’s website after contracts are executed, and all other Responses are subject to release upon completion of the procurement or if the procurement is terminated. If a Respondent believes that its Response, or parts of its Response, may be exempted from disclosure under Texas law, Respondent must submit both a redacted and unredacted copy of its Response. In the unredacted copy, Respondent must specify page-by-page and line-by-line the parts of the Response that it believes are exempt. Respondent may not mark its complete Response “copyrighted” or mark every page as proprietary or confidential and may not mark any part of its technical solution as confidential or copyright material. In addition, the Respondent must specify which exception(s) are applicable and provide detailed reasons substantiating the exception(s). DIR may publish or release the redacted copy of the Response without notice to or consent from Respondent. If a Respondent fails to provide redacted and unredacted copies of its Response or fails to specifically identify information that Respondent believes to be excepted from disclosure within its Response, then Respondent waives any and all claims against DIR for the release of such information, regardless of whether DIR provided prior notice to Respondent of such release. Pursuant to Texas Government Code Section 2252.907, Respondent is required to make any information created, or exchanged with the state pursuant to this Contract, and not otherwise excepted from disclosure under the Texas Public Information Act, available in a format that is accessible by the public at no additional charge to the state.
The Office of the Texas Attorney General (OAG) has the sole authority to determine whether information is confidential and not subject to disclosure under the Public Information Act. DIR shall comply with all decisions of the OAG.
DIR assumes no responsibility for asserting legal arguments on behalf of any Respondent. Respondents are advised to consult with their legal counsel concerning disclosure issues resulting from this procurement process and to take precautions to safeguard trade secrets and other proprietary information.
The issuance of this RFO does not imply that DIR is making an offer to do business with any RFO recipient or Respondent. No agreement or other binding obligation on DIR is implied or will occur unless and until a definitive agreement is executed. The issuance of this RFO and the submission of the Respondent’s Response do not create any obligation upon DIR to purchase goods or services from the Respondent, or to enter into any binding legal relationship with one (1) or more of the Respondents.
DIR makes no representations or warranties regarding the accuracy or completeness of the information contained in this RFO, its Appendices and Attachments, and in the digital data room. The Respondent is responsible for making its own evaluation of information and data contained in this RFO and in preparing and submitting its Response.
3.5.10 News Release
Respondent shall not issue any public statements or news or press releases pertaining to this RFO or the resulting Contract without prior written approval of DIR, which may be withheld in its sole and absolute discretion. A minimum of ten (10) Business Days written notice is required for such approval.
3.5.11 Response Organization
For each response submitted, Respondent shall organize its Response as follows:
1. Response Package 1: Administrative Submission Requirements
2. Response Package 2: Response to Service Requirements
3. Response Package 3: Service Pricing
4. Response Package 4: State of Texas Subcontracting Plan Each Response package should have a title page indicating the title and number of the RFO, name of the Respondent, and the date and version number of the proposal. This information should also be present on the header and/or footer of the proposal response along with page numbering. Each Response package should have an associated Table of Contents included within the zip file.
3.5.12 Response Package 1: Administrative Submission Requirements The Respondent must submit the following documents as described in the Table 3 Response Package 1 Files and subsections below. Response Package 1 should be labeled “ABC_DIR_RFO_Package 1.zip.”
Table 3 Response Package 1 Files
| RFO Reference |
| Maximum Page Count |
| Form of Response |
| Transmittal Letter and Executive Summary |
| 5 |
| “ABC_DIR_RFO_Executive_Summary.docx” |
| Attachment A: Respondent Information Form |
| No Limit |
| “ABC_DIR_RFO_Attachment_A.docx” |
| Qualification Requirements |
| No Limit |
| “ABC_DIR_RFO_Qualification_Requirements.docx” |
| Financial Information |
| No Limit |
| “ABC_DIR_RFO_Financial_Information.docx” |
| Addenda to the RFO |
| No Limit |
| “ABC_DIR_RFO_Addenda (.docx or .pdf) |
| Attachment C: Policy Driven Adoption for Accessibility (PDAA) - Vendor Self-Assessment |
| No Limit |
| “ABC_DIR_RFO_PDAA.xlsx” |
| Attachment D: Voluntary Product Accessibility Template® (VPAT®) |
| No Limit |
| “ABC_DIR_RFO_ACR.xxx” |
| Attachment E: Vendor Accessibility Development Services Information Request (VADSIR) |
| No Limit |
| “ABC_DIR_RFO_VADSIR.docx” |
Respondents will be held to the maximum page limit as indicated in the above Table 3. Pages that exceed the maximum page limit will not be evaluated.
3.5.12.1 Transmittal Letter and Executive Summary
Respondent shall submit a transmittal letter on company letterhead, digitally signed by an individual with authority to bind the company in a contract with DIR. The transmittal letter shall include a statement that the person signing is empowered to contractually bind the firm, and that the Response is valid for three hundred and sixty-five (365) days from the day after the deadline for submitting Responses. Any Response containing a term of less than three hundred and sixty-five (365) days for acceptance shall be rejected.
The transmittal letter should include an executive summary of the Response, including a brief written overview of the Respondent’s company and proposed solution, and key qualifications as to why the Respondent is best qualified to implement and operate the solution.
The executive summary shall not exceed five (5) pages in length (excluding title page). No appendices or specific references to additional information will be accepted.
The Respondent must not include any pricing information or estimated savings in the Executive Summary.
The Respondent must provide, as a separate Microsoft Word document, a file entitled “ABC_DIR_RFO_Executive_Summary.docx.”
3.5.12.2 Attachment A: Respondent Information Form
1. The Respondent shall complete and sign Attachment A Respondent Information Form of this RFO document. This form must be completed and digitally signed, or the Response may be disqualified as noncompliant.
2. The Respondent must provide, as a separate Microsoft Word document a file entitled “ABC_DIR_RFO_Attachment_A.docx.”
3.5.12.3 Minimum Respondent Qualifications
1. Respondent must clearly state how its team (inclusive of prime and subcontractor partners) meets each of the minimum qualifications/requirements set forth in the following Table 4 Qualification Requirements. Respondent shall complete and include in the Response the table below with the Respondent Comment column of the table explaining how the requirements are met, as described below.
Table 4 Qualification Requirements
| # |
| Qualification / Requirement |
| Respondent Comments |
| 1 |
| Five (5) or more years’ experience providing managed network services in a Multi-Supplier environment within the past ten (10) years as stated in Exhibit 1 (SOW) |
| Respondent shall explain how the Response meets all requirements of this RFO. Be specific – identify projects and initiatives, with details inclusive of dates. Indicate Respondent’s role – prime vs. subcontractor. |
| 2 |
| Held at least 3 contracts for similar major activities within the last five (5) years that have a minimum annual contract value of $1,000,000 per contract. |
| Respondent shall explain how the Response meets all requirements of this RFO. Be specific – identify projects and initiatives, with details inclusive of dates. Indicate Respondent’s role – prime vs. subcontractor. |
2. The Respondent must complete Table 4 Qualification Requirements, and provide, as a separate Microsoft Word document, a file entitled “ABC_DIR_RFO_Qualification_Requirements.docx.”
3.5.12.4 Financial Information
1. The Respondent must include the following items identified in the subsections below in its Response. Failure to include any of the items listed for the appropriate company type may result in disqualification of the Respondent’s Response. If the failure to disclose is not learned 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.
2. The Respondent must provide, as a separate Microsoft Word document, a file entitled “ABC_DIR_RFO_Financial_Information.docx.” (A .pdf form is acceptable if is the only form available).
3.5.12.4.1 Publicly Traded Companies
1. Dun and Bradstreet D-U-N-S number for the Respondent, where the number, company name and company address match the RFO Respondent.
2. Name of exchange on which common stock is listed (e.g., NYSE, AMEX) and ticker symbol (e.g., XOM).
3. Exact name of the Respondent on title page of the most currently filed SEC forms 10K and 10Q. Fully explain the reason(s) why any reports have not been timely filed within the past three (3) years.
4. Upon request, for the last three (3) fiscal years most recently ended, audited financial statements prepared in accordance with Generally Acceptable Accounting Practices (GAAP).
5. Upon request, debt and commercial paper ratings issued by Moody’s Investors Service, Standard & Poor’s, or Fitch’s Investors Service.
6. Statement describing all unasserted and asserted legal claims, current status, expected outcomes and judgments, and any off-balance sheet liabilities or contingencies.
7. Any official document displaying current proof of authority to conduct business in the State. Examples: State Franchise Tax Certification of Account Status and State Sales Tax Permit, both available from the Texas Comptroller of Public Accounts and the Certification of Fact, which is available from the Secretary of State (SOS Direct), available at: www.sos.state.tx.us.
8. Certificate of Insurance that sets forth limits of liability to include all insurance coverage of the company. If awarded a Contract, the Successful Respondent shall provide a certificate of insurance to protect DIR and DIR Customers for the coverages and in the amounts as described in MSA Attachment 2 (Insurance and Risk of Loss).
3.5.12.4.2 Privately Owned Companies (C and S corporations, LLCs and similar forms of ownership)
1. Dun and Bradstreet D-U-N-S number for the Respondent, where the number, company name, and company address match the RFO Respondent.
1. Upon request, for the last three (3) fiscal years most recently ended, audited financial statements prepared in accordance with GAAP. If audited financial statements are not prepared, un-audited financial statements will suffice as long as vendor affirms that it is not required to have its financial statements audited and therefore does not currently have audited financial statements to provide in response to this RFO.
1. Latest two (2) quarters internally prepared financial statements.
1. Upon request, debt and commercial paper ratings issued by Moody’s Investors Service, Standard & Poor’s, or Fitch’s Investors Service.
1. Statement describing all unasserted and asserted legal claims, current status, expected outcomes and judgments, and any off-balance sheet liabilities or contingencies.
1. Any official document displaying current proof of authority to conduct business in the State. Examples: State Franchise Tax Certification of Account Status and, State Sales Tax Permit, both available from the Texas Comptroller of Public Accounts and the Certification of Fact, which is available from the Secretary of State.
1. Certificate of Insurance that sets forth limits of liability to include all insurance coverage of the company. If awarded a Contract, the Respondent shall provide a certificate of insurance to protect DIR and DIR Customers for the coverages and in the amounts as described in MSA Attachment 2 Insurance and Risk of Loss.
3.5.12.5 Addenda to the RFO
Respondents are encouraged to acknowledge receipt of all addenda by providing a completed and signed version of page one of each addendum with their Response. Respondents will be held to all terms and requirements of each addendum regardless of the provision of a signed page one. Respondents will also be held to all terms and requirements of any addenda issued after their submission of a response to this solicitation.
3.5.12.6 EIR Attachments (Attachment C, Attachment D, and Attachment E) Refer to RFO Section 2.2 Electronic and Information Resources (EIR) Accessibility through RFO Section 2.5 PDAA Submission and Self-Assessment Score, complete each of the following and include in Response in accordance with Table 3 Response Package 1 Files:
1. Attachment C: Policy Driven Adoption for Accessibility (PDAA) - Vendor Self-Assessment
3. Attachment D: Voluntary Product Accessibility Template® (VPAT®)
4. Attachment E: Vendor Accessibility Development Services Information Request (VADSIR)
3.5.13 Response Package 2: Response to Service Requirements
3.5.13.1 Response Package 2 Files
The Respondent must submit the following documents as described in Table 5 Response Package 2 Files and subsections below. Response Package 2 should be labeled “ABC_DIR_RFO_Package 2.zip” Files to be included in Package 2 are summarized in Table 5 Response Package 2 Files:
Table 5 Response Package 2 Files
| RFO Reference |
| Maximum Page Count |
| Form of Response |
| Attachment B: Technical Solution Summary |
| 50 |
| “ABC_DIR_RFO_Technical_Solution.docx” |
| Transition Service Enablement Approach & Methodology |
| 50 |
| “ABC_DIR_RFO_TransitionService Enablement_Approach.docx” |
| Transition Project Plan (“MS Project” form) |
| No Limit |
| “ABC_DIR_RFO_Transition_Project_Plan.mpp” and PDF |
| Respondent Experience |
| 10 |
| “ABC_DIR_RFO_Experience.docx” |
| Proposed Account Organization |
| 10 |
| “ABC_DIR_RFO_Proposed_Account_Organization.docx” |
| Attachment 1.4 Key Personnel |
| No Limit |
| “ABC_DIR_RFO_Attachment_1.4_Key_Personnel.docx” |
| Attachment G: Exceptions |
| See RFO Section 3.5.13.7 Exceptions to Requirements, (including MSA Terms and Conditions) |
| “ABC_DIR_RFO_Exceptions.xlsx” AND “ABC_MSA_Exceptions.docx” |
Respondents will be held to the maximum page limit as indicated in the above Table 5. Pages that exceed the maximum page limit will not be evaluated.
3.5.13.2 Attachment B: Technical Solution Summary
The electronic version shall be in Microsoft Word format and must be entitled “ABC_Technical_Solution_Summary.docx”. Respondent shall not mark any of the Respondent technical solution as confidential or copyright material.
3.5.13.3 Transition Approach & Methodology
Respondent shall describe its approach and methodology to establish the services operations and provide ongoing steady-state services. Respondent’s approach must demonstrate Respondent’s experience, expertise, and ability to plan and complete all work required under a Contract arising from this RFO.
Respondent shall submit a narrative description of its proposed Transition Project Plan and initial draft Transition Project Plan schedule as described in the subsections below.
1. The narrative description addressing the transition factors of 3.6.13.3.3 Transition Timeline in a Microsoft Word document entitled “ABC_DIR_RFO_Transition_Approach.docx.”
8. See 3.6.13.3.4 Transition Project Plan regarding the Transition Project Plan.
3.5.13.3.1 Transition Overview
Respondent shall describe its plan to establish the services at the Commencement Date, including, but not limited to, documenting pre-Commencement activities that must occur, how transition to operational readiness will take place at the Commencement Date, and what post-Commencement Date activities will be required to fully implement all components of the services (e.g., assets, software licenses and operational documentation). Respondent shall include knowledge transfer requirements and associated activities and schedule for such activities.
Respondent shall provide an overview of their organizational change management philosophy, including an overview of recommended organizational change management (“OCM”) activities for a project of this nature based on lessons learned from previous experience, specifying whether they are to be conducted by the Respondent or DIR, identification of OCM services included in the Response, and Respondent shall provide an overview of how they will support OCM activities conducted by DIR.
3.5.13.3.2 Transition Services
Respondent shall describe its approach for the following:
Solution and Service Integration – Respondent shall describe how it will work through the Transition of Managed Network Services functions into the DIR operating model to ensure no disruption in service within the STS program. Respondent shall include a listing of integration points expected with tools and processes in order to identify SCP Transition scope of work.
Operations, Policies and Procedures – Respondent shall describe how it will establish its services to support and align with the SMM or, in the absence of an SMM, industry best practices . Respondent shall also describe how operations, policies, and procedures and program management plans (NOC, LAN/WAN, Fully Managed VPN, Disaster Recovery, etc.) will be established or transitioned.
Assured Operational Readiness – Respondent shall describe how it will assess operational readiness for the establishment and cutover of MNS.
Service Management Systems – Respondent shall describe how it will conform to the requirements for integration as set forth in Exhibit 1 (SOW). Include Respondent’s expectations for what Systems will be in place at the Commencement Date and what Systems or changes will be put in place subsequently, if any.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .