Attachment_D_Submission_Forms_A-G_7.8_Word.pdf
PDF 202 KB Posted
- Solicitation number
- RFP 126DT039
- Issued by
- Denver County, Denver City, Colorado
About this file
This document is a technical submittal form package for an Enterprise Resource Planning (ERP) Software-as-a-Service (SaaS) solution procurement by the Regional Transportation District (RTD) in Colorado. The RFP seeks to replace RTD's existing Oracle E-Business Suite (EBS) with a modern, cloud-based SaaS ERP platform to support core business functions in finance, procurement, and inventory management, with a secondary objective to include human resources capabilities. The procurement is focused exclusively on ERP software platform selection, with a separate and subsequent RFP planned for Systems Integrator (SI) services. RTD's evaluation will focus on alignment with detailed agency-specific functional requirements, long-term strategic fit, overall value, and the platform's maturity, flexibility, and extensibility to support evolving business needs across all administrative business functions.
The technical submittal forms require proposers to provide comprehensive information across seven key submittals: SaaS Proposer Profile (Solution Identification, Delivery Model, Organizational Experience, Service Availability, Security and Compliance, Product Maturity, AI Capabilities, and Support Model); Partner/Third-Party Vendor Profiles; three Client References reflecting RTD's SaaS scope; Financial Qualifications; Legal Disclosures; ERP Functional Requirements and Non-Functional Requirements (provided in separate Excel files); and SaaS and Other Agreements/Documents. Proposers must detail their platform's deployment model (multi-tenant, single-tenant, or hybrid), hosting environment, service level agreements, upgrade model, disaster recovery approach, certifications (SOC 1, SOC 2, ISO 27001, FedRAMP), support availability and channels, implementation partner ecosystem, and experience serving public sector and transit/transportation agencies. References must document specific functional modules delivered as SaaS and technical deployment and managed service implementations.
View the file
Other files
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
Technical Submittal A: SaaS Proposer Profile
Proposer Organization Information
Legal Name:
Headquarters Location (City, State/Country)
Primary Business Address:
Website URL:
Year Established:
Ownership Type (Public/Private/Other):
Parent Company (if applicable):
Relevant Subsidiaries/Affiliates (if applicable):
Proposed SaaS Solution Identification
Name of Proposed ERP SaaS Solution:
Version / Platform (if applicable):
Brief Description of Solution (2-3 Sentences):
Primary Functional Areas Included (check all that apply):
Finance
Procurement
Inventory
HR
Other (Analytics/Reporting/Other Please Specify):
SaaS Delivery Model and Hosting
Deployment Model:
Multi-Tenant
Single-Tenant
Hybrid
Other (Describe):
Hosting Environment:
AWS
Microsoft Azure
Google Cloud Platform
Vendor-Owned Data Center
Other (Please Specify):
Primary Date Residency (Region/County):
Multi-Region / Failover Capability (Yes/No Brief Description)
Organizational Experience & Market Presence
No. of Years Providing ERP SaaS Solutions:
No. of Years Serving Public Sector Clients:
No. of Years Serving Transit/Transportation Agencies:
Total Number of Active ERP SaaS Customers:
Number of Public Sector Customers:
Number of Transit/Transportation Customers:
Customer Scale and Adoption
Total Estimated Active Users Across All Customers:
Largest Customer Size (Approx. Users)
Average Customer Size (Approx. Users or Employees)
SaaS Platform Operations
Service Availability SLA (%):
Typical Release Frequency:
Monthly
Quarterly
Biannual
Other (Specify):
Upgrade Model:
Vendor Managed Automatic Updates
Customer Controlled Updates
Other (Describe):
Disaster recovery Approach (Brief):
Security and Compliance
Certifications (Check all that Apply):
SOC 1
SOC 2
ISO 27001
FedRAMP
Data Security Approach (Very Brief):
Data Isolation Approach (Very Brief for Multi-Tenant):
Product Maturity and Roadmap
Current Platform Generation/Major Version:
Frequency of Major Enhancements:
Key Areas of On-Going Investment:
AI / Machine Learning
Automation
Analytics
Description of Roadmap (Very Brief):
AI and Advanced Capabilities (if Applicable)
AI/ML Capabilities Included in Base Platform (Brief):
AI/Agent-Based Features Available as Add-On (Brief):
General Pricing Model for AI Capabilities:
Included in Base
Subscription Add-On
Usage Based
Customer Support and Success Model
Support Availability:
24x7
Business hours
Support Channels (Check all that Apply):
Web Portal
Phone
Chat
Customer Success Model (Brief):
Dedicated Account Management (Yes/No):
Implementation Partner Ecosystem
Approximate Number of Certified SI Partners:
Approximate Number of SI Partners w/Public/Transit Exp.:
Availability of Managed Services Partners (Yes/No):
Additional Information
Please use this space for any additional information (include pertinent information only, no marketing information):
Technical Submittal B: Partner / Third-Party Vendor Profile
Third-Patry Provider Information
Provider Name:
Product/Component Name:
Primary Function within Proposed Solution (Brief Description):
Integration with Proposed SaaS Solution
Type of Integration:
Native / Embedded
API-Based
Third-Party / Middleware
Level of Dependency on Third-Party Component (Brief):
Functional Scope
Key Functional Areas Supported (e.g., Procurement, Analytics):
Related Functional Requirements Areas (to Tech. Submittal F):
Licensing and Responsibility
Licensing Model:
Included in Proposer Pricing
Separate Licensing Required
Contracting Approach:
Through Proposer
Direct with RTD
Support and Accountability
Support Responsibility:
Proposer
Third-Party Provider
Shared
Brief Description of Support Model (If Shared):
Technical Submittal C: Client Reference
COMPLETE ONE FORM FOR EACH OF THE THREE PAST PROJECT REFERENCES
MOST CLOSELY REFLECT RTD S SAAS SCOPE OF SERVICES
GENERAL BACKGROUND
Name of Client:
Project Manager/Contact: Title:
Phone: E-mail:
ERP Software/Version:
Project Title: Project Cost:
Size of Organization (Employees): Size of Operating Budget:
SaaS Vendor Contact:
ERP SAASFUNCTIONAL SCOPE (ONLY CHECK MODULES THAT WERE SERVED AS SAAS BY THE PROPOSER)
Accounts Receivable Accounts Payable Budgeting
General Ledger/COA Treasury/Debt Management Fixed Assets
Grants and Capital Accounting Procurement/Purchasing Contract Management
HR Personnel/Records Benefits Administration Talent Acquisition
Learning Management Incident Management Time Keeping
Payroll Project Planning/Monitoring/Co. Self-Services (Emp. &Vendor)
Business Intelligence (BI) ERP AI Enablement Data Archival/Retrieval/Warehouse
Integrations w/EAM/PMIS/Other Inventory Management Warehousing
TECHNICAL SCOPE IT DEPLOYMENT & MANAGED SERV. (ONLY CHECK MODULES THAT WERE IMPLEMENTED SUCCESSFULLY)
Enterprise Architecture & Ops. ISO 27000+/SOC 2 Compliance System Performance/Availability
General Reporting/Queries Interfaces/Integration Data Structure/Storage
Workflow Management SaaS Application Admin. SaaS Infrastructure Mgmt.
SaaS Production/User Support SaaS Service Levels Mgmt. SaaS Cyber Security
SaaS ITSM/ITIL Standards SaaS Disaster Recovery/BC SaaS from FedRamp Facility
OTHER INFORMATION
Date of Go-Live (If Implemented):
Current version:
Provide Details on Current SaaS and, if any, Application Managed Services (Post Go-Live) If under contract:
Type of Implementation Deployment Model & On-Going Managed Services (Check all that apply):
On-Premises Hosted Service Managed Service SaaS
Any Other Information (Please use this Space):
Technical Submittal D: Financial Qualifications
PROVIDE THIS INFORMATION FOR SAAS PROPOSER AND KEY PARTNERS
<< PROPOSER TO PROVIDE THIS INFORMATION IN ITS OWN FORMAT >>
Technical Submittal E: Legal Disclosures
Technical Submittal F: ERP Functional Requirements
RTD PROVIDED THIS SUBMITTAL IN SEPARATE EXCEL FILE
FOLLOW INSTRUCTIONS IN THE EXCEL FILE
Technical Submittal F.1 SaaS Non- Functional Requirements
RTD PROVIDED THIS SUBMITTAL IN SEPARATE EXCEL FILE FOLLOW
INSTRUCTIONS IN THE EXCEL FILE
Technical Submittal G: SaaS and Other Agreements/Documents
| Complete one form for each of the three past project references most closely reflect RTDs SaaS scope of Services |
| ERP SaaSFunctional Scope (Only check modules that were Served as SaaS by the Proposer) |
| Provide this information for SaaS Proposer and Key Partners |
| Provide this information for SaaS Proposer and Key Partners |
| Provide this information for SaaS Proposer and Key Partners |
File details come from the government source that posted it. Updated .