ESBD_371873_1723662958174_Attachment P - Vendor Compliance Checklist.pdf
PDF 121 KB Posted
- Attached to
- Legacy Systems Replacement Project
- Solicitation number
- 452-24-BLC020
- Issued by
- Travis County, Austin City, Texas
About this file
This document is a Vendor Compliance Checklist for a Request for Offers (RFO) issued by the Texas Department of Licensing and Regulation (TDLR) for a Legacy Systems Replacement Project. The RFO seeks business entities, manufacturers, and authorized resellers to provide the agency with a comprehensive, cloud-based licensing and regulatory software, along with the associated implementation, maintenance, and related services. The RFO has an opening date of September 16, 2024, at 2:00 P.M. CZT. The checklist outlines the required submittal sections, which include the company background and experience, product overview, functional and technical solution, implementation approach, payment milestones, staffing, and various forms and attachments.
The pricing workbook and service level agreements are also required. The jurisdictions involved in this opportunity include Travis County and several locations within the City of Austin. The project does not provide any information about pricing terms, set asides, incumbents, current environment, funding requirements and sources, or any other salient details beyond the submittal requirements.
View the file
Other files
Show 40 more
Latest 50 of 61 listed here. See the rest on GovTribe.
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
1 | P a g e
VENDOR COMPLIANCE CHECKLIST
Checklist for RFO# 452-24-BLC020 Title: RFO - Legacy Systems Replacement Project Opening Date: September 16, 2024, 2:00 P.M. CZT.
Respondent’s Name: ________________________
RFO SUBMITTAL:
1. Submitted one (1) original of the following: Included?
a. Section 1: Title Page ________
b. Section 2: Cover Letter/Executive Summary ________
c. Section 3: Table of Contents ________
d. Section 4: Company Background & Experience ________
Section 4A: Company Profile
Section 4B: Offeror Experience
Section 4C: Financial Assurance
e. Section 5: Product Overview ________
f. Section 6: Functional Solution ________
Section 6A: Functional Requirements Response Workbook
g. Section 7: Technical Solution ________
Section 7A: Conceptual Architecture
Section 7B: System Architecture
Section 7C: Security
Section 7D: Integration
Section 7E: Data Conversion/Migration
Section 7F: Reporting
Section 7G: Technical Requirements Response Matrix
h. Section 8: Implementation Approach & Understanding ________
Section 8A: Schedule and Work Plan
Section 8B: Staffing Requirements and Proposed Organizational Chart
Section 8C: Project Management Approach
Section 8D: Implementation Approach/Deployment Strategy
Section 8E: Key Implementation Risks and Mitigation Strategies
Section 8F: Design and Development Strategy
Section 8G: Test Strategy
2 | P a g e
Section 8H: Knowledge Transfer and Training Approach (optional: OCM)
Section 8I: Business Continuity and Disaster Recovery
Section 8J: Hosting, Production Support, and Transition
i. Section 9: Payment Milestones and Invoice Deliverables ________
j. Section 10: Offeror References ________
k. Section 11: Staff Resumes ________
l. Section 12: HUB Required Forms (Attachment F) ________
m. Section 13: Pricing Workbook (Attachment E) ________
n. Section 14: Service Level Agreements/Service Level Requirements ________
o. Section 15: Terms and Conditions ________
p. Section 16: Assumptions and Exceptions ________
q. Section 17: Glossary of Terms ________
ATTACHMENTS (Section 5.0)
2. Submitted one (1) original of the following: Included?
Attachment C – Functional Requirements Response Workbook ________
Attachment D – Technical Requirements Response Workbook ________
Attachment E – Pricing Workbook ________
Attachment F – HUB Subcontracting Plan Forms ________
Attachment G – Certificate of Interested Parties ________
Attachment P – Vendor Compliance Checklist ________
File details come from the government source that posted it. Updated .