125DT041_Compliance_Matrix_-_Requirements.xlsx
XLSX spreadsheet 33 KB Posted
- Attached to
- Next Ride Mobile Application-Native Application State and local contract opportunity
- Solicitation number
- RFP 125DT041
- Issued by
- Denver County, Denver City, Colorado
About this file
The document is a Compliance Matrix for the Regional Transportation District (RTD) in Colorado, detailing requirements for a Next Ride Mobile Application development project. RTD is seeking a contractor to design and develop a custom mobile application for iOS and Android platforms, integrating multiple existing RTD mobile applications into a single user interface. The project timeline is 10-12 months, with the contractor required to provide three references of similar mobile application development projects. The mobile app must support multiple languages (English and Spanish at minimum), be compatible with Apple and Google Play Store requirements, and include features such as trip planning, service alerts, ticketing integration, and accessibility compliance.
The compliance matrix outlines extensive technical, design, and project management requirements, including the use of specific development tools like GitHub, JIRA, and React Native, integration with RTD's existing APIs and data feeds, and adherence to brand standards and accessibility guidelines. The contractor will be responsible for providing user interface designs, wireframes, prototypes, and comprehensive documentation. The project includes one year of post-deployment support and maintenance, with ongoing technical support during business hours. Key technical specifications include supporting offline mode, implementing secure storage solutions, and ensuring robust error handling and API integrations across various RTD systems and third-party services.
View the file
Other files for this state and local contract opportunity
| File | Type | Posted |
|---|---|---|
| 125DT041_SOW_-_Next_Ride_Mobile_Application-Revised_06-26-2025.pdf | ||
| Next_Ride_Mobile_Application-Native_Application_(Addendum_#1_Revision).pdf | ||
| 125DT041_Form_of_Contract_for_Next_Ride_Mobile_Application.pdf | ||
| Supplemental_Non-Disclosure_Terms_and_Conditions.pdf | ||
| Background_Investigation_Certification.pdf | ||
| Supplemental_Background_Checks_Terms_and_Conditions.pdf | ||
| 125DT041_Statement_of_Work_(SOW)_Next_Ride_Mobile_Application.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| This Requirements Compliance Matrix form must be completed and submitted with your proposal. | Company Name: | ||||
| Note: Please refer to the RFP 125DT041 Statement of Work, Section 4, for additional Project Requirement information | Please enter Company Name Here | ||||
| Instructions: For each table of requirments listed below please respond with one of the following response codes: | Date of Proposal: | ||||
| Please enter Proposal Date Here | |||||
| RESPONSE | DEFINITION | ||||
| CODE | |||||
| FC | Fully Compliant – Proponent fully complies with requirement. Responses that are qualified by exceptions or limitations, etc. in the Compliance Matrix shall be considered the equivalent of “NC” (does not comply). | ||||
| CM | Complies with Modified Requirement – Proponent shall provide modified requirement language to which they commit to comply. The “CM” shall be equivalent to a response of “FC” if RTD opts to change the requirement as proposed, or to a response of “NC” if RTD opts to not change the requirement. | ||||
| If complete alternate requirement wording is not proposed in conjunction with a “CM” response, the response shall be considered equivalent to a response of “NC” to the requirement as stated in the RFP. RTD alone shall be the judge of the completeness and appropriateness of alternate requirement language. | |||||
| NC | Does Not Comply – Proponent does not comply with the requirement. Accompanying comments are discouraged. . | ||||
| 1.1 GENERAL REQUIREMENTS | |||||
| Requirement ID | Requirement Name | Requirement Type | Requirement Description | Compliance Code | Clarification or Exception |
| REQ-1 | Stakeholder Engagement | Business | The Contractor shall engage the various stakeholder groups (provided by RTD) to determine end-user business needs. | ||
| REQ-2 | Project Timeline | Business | The Contractor shall complete all design and development for the mobile application in 10-12 months. | ||
| REQ-3 | Contractor References | Business | The Contractor shall provide (3) examples of mobile application development of similar size and scope to this project request. | ||
| REQ-4 | Github | Functional | The mobile app shall utilize GitHub's software for source control and associated version control tool Git. | ||
| REQ-5 | JIRA | Functional | The mobile app shall utilize JIRA for task and project management. | ||
| REQ-6 | Framework | Functional | The mobile app shall utilize a React Native, Ionic or similar framework for development. | ||
| REQ-7 | Source Code | Functional | RTD shall retain and own all source code once mobile application is developed. | ||
| REQ-8 | Mobile Device Compatibility | Functional | The mobile app must be accessible from any modern mobile device once mobile application is downloaded from Apple App Store or Google Play Store onto device. | ||
| REQ-9 | Google Play Store | Functional | The mobile app must be developed so that it is compatible and meets Google Play Store mobile app requirements. | ||
| REQ-10 | Apple App Store | Functional | The mobile app must be developed so that it is compatible and meets Apple App Store mobile app requirements. | ||
| REQ-11 | Language Translations | Functional | The mobile app shall be available in multiple languages. Currently, RTD’s language access plan specifies English, Spanish, Vietnamese, simplified Chinese, Russian and Korean. The application needs to support English and Spanish at a minimum. | ||
| REQ-12 | Analytics | Functional | The mobile app shall have analytics tools installed so RTD can track app performance, user experience and engagement through Google Analytics GA4 or similar. | ||
| REQ-13 | User Interface | Design | Contractor shall work with RTD's UI Developer and stakeholder team to create designs concepts | ||
| REQ-14 | User Interface | Design | The look and feel of the mobile app shall be streamlined and modern with a clean, simple design. | ||
| REQ-15 | Scope of Design Services | Design | The mobile app shall be designed using modern UI/UX practices for mobile devices and tablets. | ||
| REQ-16 | Scope of Design Services | Design | Contractor shall provide wireframes for 8-10 screens showing key functionality around navigation and content layout. | ||
| REQ-17 | Scope of Design Services | Design | Contractor shall provide high fidelity designs for 10-20 screens showing key functionality like Plan a Trip user experience flow | ||
| REQ-18 | Scope of Design Services | Design | Contractor shall provide clickable design prototype to show full user experience using Figma or Adobe XD. | ||
| REQ-19 | User Interface | Design | All mobile app text shall have a high contrast color to its background to ensure legibility and meet iOS and Android platform accessibility requirements. | ||
| REQ-20 | User Interface | Design | The design of instructions and graphics in the mobile app shall minimize glare and other effects of sunlight and ambient lighting accessed by Settings in the OS. | ||
| REQ-21 | Accessibility | Design | The mobile app should be developed to use the mobile device screen reader tools provided by iOS (VoiceOver) and Android (TalkBack). | ||
| REQ-22 | Accessibility | Design | The mobile app must be WCAG 2.2 Level AA compliant. | ||
| REQ-23 | Design Systems | Design | The collection of tools, platforms, mobile applications and software that comprise the new technology stack shall be complementary of one another. | ||
| REQ-24 | Developer Experience | Design | The solution shall provide a modern developer experience (DevX) for native Android and iOS mobile applications, incorporating the following standard - Modern Architecture: Clean, modular design (e.g., MVVM) with clear separation of concerns. | ||
| REQ-25 | Developer Experience | Design | The solution shall provide a modern developer experience (DevX) for native Android and iOS mobile applications, incorporating the following standard - Hot Reloading: Support for rapid UI iteration and testing. | ||
| REQ-26 | Developer Experience | Design | The solution shall provide a modern developer experience (DevX) for native Android and iOS mobile applications, incorporating the following standard - Declarative Rendering: Utilize Jetpack Compose (Android) and SwiftUI (iOS) for UI components where mobile applicable. | ||
| REQ-27 | Developer Experience | Design | The solution shall provide a modern developer experience (DevX) for native Android and iOS mobile applications, incorporating the following standard - Modern Tools and Languages: Kotlin for Android, Swift for iOS, and IDEs like Android Studio and Xcode. | ||
| REQ-28 | Developer Experience | Design | The solution shall provide a modern developer experience (DevX) for native Android and iOS mobile applications, incorporating the following standard - Reusable Components: Development of scalable, reusable components. | ||
| REQ-29 | Developer Experience | Design | The solution shall provide a modern developer experience (DevX) for native Android and iOS mobile applications, incorporating the following standard - Comprehensive Logging: Real-time debugging tools (e.g., Logcat, Xcode). | ||
| REQ-30 | Developer Experience | Design | The solution shall provide a modern developer experience (DevX) for native Android and iOS mobile applications, incorporating the following standard - Asset Pipelines: Efficient handling of images, fonts, and localized resources. | ||
| REQ-31 | RTD Brand Standards | Design | Design shall match RTD brand standards located at https://www.rtd-denver.com/brand-elements, while proposing guideline enhancements that visually connect with our audience. | ||
| REQ-32 | API Endpoints | Technical | The solution shall use all API endpoints existing on the current site (to be shared by RTD) in the development of the new mobile app. | ||
| REQ-33 | API Endpoints | Technical | The contractor must validate endpoint performance and reliability during development. | ||
| REQ-34 | API Endpoints | Technical | Any API gaps or issues must be flagged by the contractor, who shall collaborate with RTD to resolve them. | ||
| REQ-35 | Mobile Ticketing Integration | Technical | The mobile app shall connect to RTD's mobile ticketing mobile application via an API or SDK (third-party vendor). | ||
| REQ-36 | Mobile Ticketing Integration | Technical | Ensure PCI DSS compliance for all payment-related data handling. | ||
| REQ-37 | Mobile Ticketing Integration | Technical | Provide seamless integration for fare purchase, ticket validation, and transaction history using RTD's third-party mobile ticketing API or SDK. | ||
| REQ-38 | Safety and Security Integration | Technical | The mobile app shall connect to RTD's safety and security mobile application via an API or SDK (third-party vendor). | ||
| REQ-39 | Safety and Security Integration | Technical | This integration must support real-time safety alerts and reporting features as defined by RTD. | ||
| REQ-40 | Service Alerts Integration | Technical | The mobile app shall integrate with RTD’s service alert APIs to display real-time alerts by route or service. | ||
| REQ-41 | Service Alerts Integration | Technical | Support filtering of alerts by user preferences (e.g., route, location, or time). | ||
| REQ-42 | Service Alerts Integration | Technical | Alerts must update dynamically without requiring mobile app restarts. | ||
| REQ-43 | Trip Planner Integration | Technical | The mobile app shall integrate with the Open Trip Planner (Arcadis) API. | ||
| REQ-44 | Trip Planner Integration | Technical | The mobile app shall support trip plan search functions by route, stop and address using RTD's third party vendor Mapbox. | ||
| REQ-45 | Trip Planner Integration | Technical | Support both REST (v1) and GraphQL (v2) APIs. | ||
| REQ-46 | Trip Planner Integration | Technical | Include fallback mechanisms for handling API outages or errors. | ||
| REQ-47 | Trip Planner Integration | Technical | The mobile app shall integrate with RTD’s geocoding and search suggestions API to support trip planning functions. | ||
| REQ-48 | Trip Planner Integration | Technical | Forward Geocoding: Convert addresses, business names, places of interest, or event names (e.g., concerts) into geographic coordinates (Lat/Lng). | ||
| REQ-49 | Trip Planner Integration | Technical | Search Suggestions: Provide real-time suggestions for user-entered search terms, ordered by best match as determined by RTD’s API algorithm. | ||
| REQ-50 | Trip Planner Integration | Technical | The Contractor shall inform RTD of any API gaps and collaborate with RTD to address them. | ||
| REQ-51 | Trip Planner Integration | Technical | Ensure robust error handling with fallback or retry mechanisms. | ||
| REQ-52 | Trip Planner Integration | Technical | Optimize the integration for high query volumes with minimal latency. | ||
| REQ-53 | Scheduling Integration | Technical | The mobile app shall integrate with RTD’s TIS API to fetch scheduling data. | ||
| REQ-54 | Scheduling Integration | Technical | Support timetable lookups for routes and stops. | ||
| REQ-55 | Scheduling Integration | Technical | Ensure accurate schedule adherence updates during trip planning. See GTFS requirement. | ||
| REQ-56 | Concert / Music Artist Integration | Technical | The mobile app shall connect to RTD's concert/music artist data feed via an API or SDK (third-party vendor). | ||
| REQ-57 | Facilities | Technical | The mobile app shall integrate with RTD’s facilities data feed via an API to display Facility locations (e.g., parking lots, restrooms). | ||
| REQ-58 | Facilities | Technical | The mobile app shall integrate with RTD’s facilities data feed via an API to display additional metadata such as accessibility features and operating hours. | ||
| REQ-59 | GTFS | Technical | The mobile app shall support GTFS data provided by RTD for Static Data: Process weekly updates or updates tied to specified runboard change dates. | ||
| REQ-60 | GTFS | Technical | The mobile app shall support GTFS data provided by RTD for Real-Time Data: Refresh GTFS-RT updates at a maximum interval of 30 seconds during active app usage. | ||
| REQ-61 | GTFS | Technical | The mobile app shall support seamless transitions between static and real-time data. | ||
| REQ-62 | GTFS | Technical | The mobile app shall allow direct consumption of GTFS feeds or through RTD-provided APIs. | ||
| REQ-63 | User Profile / Account | Technical | User authentication, payment storage, and ticket management shall occur within the third party mobile ticketing ecosystem. | ||
| REQ-64 | Opt-In / Opt-Out | Technical | The mobile app shall have opt-in/opt-out capabilities for features like push notifications, marketing communications, and data sharing with third parties. | ||
| REQ-65 | Offline Mode Support | Technical | Key functionalities should remain usable with limited or no connectivity. | ||
| REQ-66 | Share a Trip | Technical | The mobile app shall integrate with a SMS provider to provide share a trip function via SMS or email to customers (third-party vendor). | ||
| REQ-67 | Share a Trip | Technical | The shared trip details must include key information like route, stops, and estimated travel time. | ||
| REQ-68 | Share a Trip | Technical | Ensure that the shared content is accessible and compatible with mobile and desktop email clients. | ||
| REQ-69 | Caching | Technical | The Contractor shall implement mechanisms to fetch, manage, and refresh caches across all environments. | ||
| REQ-70 | Caching | Technical | The Contractor shall use caching strategies to optimize performance for static and frequently accessed data. | ||
| REQ-71 | Feedback Form | Technical | The mobile app shall include a web form for users to provide feedback. | ||
| REQ-72 | Feedback Form | Technical | The mobile app web form shall pass information to RTD's Salesforce backend solution. | ||
| REQ-73 | Off-Site Links | Technical | The mobile app shall provide functionality to link to third-party mobile apps and websites. | ||
| REQ-74 | Social Profile Links | Technical | The mobile app shall link to RTD's social media accounts/profiles. | ||
| REQ-75 | Content | Content | The contractor shall copy all current Next Ride content into the mobile application. | ||
| REQ-76 | Secure Storage | Security | The mobile app shall utilize secure storage solutions for iOS and Android to safeguard sensitive user data, including payment details and authentication tokens. | ||
| REQ-77 | Javascript Libraries | Security | Contractor shall vette any Javascript Libraries before implementing into mobile app to prevent code injections/attacks. | ||
| REQ-78 | Third-Party Libraries | Security | Contractor shall vette any Third-Party Libraries before implementing into mobile app to prevent code injections/attacks. | ||
| REQ-79 | Recovery Point Objective (RPO) | Security | Data backups shall occur no less than every (12) hours. | ||
| REQ-80 | Recovery Time Objective (RTO) | Security | System downtime must not exceed 60 minutes for critical functions. | ||
| REQ-81 | Project Management | Project Management | The Contractor shall assign a dedicated project manager to this project | ||
| REQ-82 | Kick-off Meetings | Project Management | A Project Kickoff Meeting, coordinated with the RTD Project Manager, shall be scheduled within seven (7) days after Notice to Proceed (NTP) and conducted within twenty-one (21) days. The Project Kickoff Meeting will be conducted by the Contractor and the RTD Project Manager at RTD offices, through Microsoft Teams, or other high-quality teleconferencing approach. | ||
| REQ-83 | Project Meetings | Project Management | The contractor shall schedule and facilitate Progress Meetings held between the Contractor and RTD on a weekly or every other week basis, as deemed necessary by RTD, for the purpose of reviewing progress, coordinating activities, and other project activities that cannot be resolved by correspondence. The timing of these meetings shall be conducted at RTD’s sole discretion, based on the nature of the current project activities. These meetings may be at RTD offices, through Microsoft Teams, or other high-quality teleconferencing approach. | ||
| REQ-84 | Project Meetings Agendas | Project Management | Agendas for the Progress Meetings will be prepared by the Contractor and may include any topics that the Contractor's Project Manager determines to be relevant to the project. The Contractor shall insure those persons knowledgeable in the topics to be discussed, including subcontractors, subject matter experts, and/or technical representatives, are present at all necessary meetings. Agendas will be submitted at least two (2) business days prior to the meeting. | ||
| REQ-85 | Meeting Summaries | Project Management | Meeting summaries shall be taken at all meetings. Summaries shall include a summary of all topics discussed, a listing of all understandings and agreements reached, and an updated Action Item List (AIL). Unless otherwise agreed, the Contractor shall be responsible for taking all meeting summaries. The format for the meeting summaries shall be developed based on input from RTD. Completed meeting summaries shall be uploaded to the RTD Teams project site by the Contractor. | ||
| REQ-86 | Meeting Summaries | Project Management | The meeting summaries shall be distributed to all attendees for review within three (3) business days from the end of the meeting. | ||
| REQ-87 | Action Item List | Project Management | During meetings, action items will be identified, with each action item assigned to an individual for disposition by a pre-determined response date. These action items shall be maintained and updated throughout the project by the Contractor, in an Action Item List (AIL). The AIL format will be mutually agreed upon by the Contractor and RTD. The AIL shall be maintained in the RTD Teams project site. | ||
| REQ-88 | Issue Tracking Systems | Project Management | The Contractor shall provide RTD key personnel access to any issue tracking system used by the Contractor to support the project. The Contractor will provide no less than monthly a status report of all tickets. RTD prefers JIRA for this. | ||
| REQ-89 | Monthly Status Report | Project Management | Contractor shall provide to the RTD PM a status report monthly highlighting key accomplishments, risks, issues, and milestones/deliverables updates. The monthly status reports shall be uploaded by the Contractor to the RTD Teams project site. Status reports shall be uploaded by the Contractor to the RTD Teams project site. | ||
| REQ-90 | Invoice Documentation | Project Management | The Contractor shall keep and maintain reasonably complete and reliably detailed records of milestones achieved in performing the Contract, including records of productivity to identify basis for payment, sufficient to evaluate the accuracy, completeness, and currency of the costs or prices. | ||
| REQ-91 | Project Schedule | Project Management | Within thirty (30) days after Notice to Proceed (NTP), the Contractor shall furnish, to RTD for RTD’s approval, a detailed Project Schedule. The detailed Project Schedule shall be based on critical-path-method and constructed using Microsoft Project or RTD mobile approved substitute. | ||
| REQ-92 | Project Schedule | Project Management | The detailed Project schedule shall show start and completion of the work with |
dependencies for each activity and shall be properly ordered and sequenced. It shall identify all major work tasks including critical events of design, procurement, delivery schedule, installation, testing, and integration, and shall identify interface activities, subcontractor contributions and submittals, RTD inspections, tests, and mobile approvals as may be required by this document, additional details shall be provided, such as:
· A clear description of the activity, including its location
· The duration expressed in full working days
· A responsibility for work denoting the Contractor, a subcontractor, RTD, or entity performing the activity
· The quantity of material, in units
· Type of equipment needed (if significant or unusual)
· The integer percent complete representing the installed progress
· The actual start and finish dates when mobile applicable Requirements and events which impose limitations, as well as dates and milestones which constrain the time, shall be clearly identified.
| REQ-93 | Project Schedule | Project Management | The Contractor shall be required to submit project schedule updates on at least a monthly basis. More frequent near-term schedule updates may be required, if deemed advantageous by RTD for monitoring the progress of specific phases of the project. |
| REQ-94 | Personnel | Project Management | All personnel assigned by the Contractor must display appropriate identification while on RTD property and must adhere to all RTD Rules and Regulations. |
| REQ-95 | Collaboration Tools | Project Management | The Contractor shall use RTD's Microsoft Team Site for team chats outside of project meetings. |
| REQ-96 | Project Communications | Project Management | Within thirty (30) days of Notice to proceed (NTP), the Contractor shall provide a RACI along with Contractor’s escalation procedure, including contact names and information for each level of escalation. |
| REQ-97 | Project Communications | Project Management | The Contractor shall promptly notify the RTD PM of any problems or difficulties that may affect the timely or effective completion of the project or any scheduled deliverables. |
| REQ-98 | Project Communications | Project Management | The Contractor shall coordinate activities with RTD PM regarding affected RTD business units and personnel, and with external individuals and organizations. |
| REQ-99 | Project Communications | Project Management | All email communications from the Contractor shall originate from accounts that are owned and managed by the vendor through access management controls. |
| REQ-100 | Subject Matter Experts | Project Management | The Contractor shall make all subject matter experts available - when required or requested. |
| REQ-101 | Quality Assurance | Testing | The Contractor shall plan, establish, and maintain a Quality Assurance (QA) program. The Contractor’s QA program shall be imposed upon all entities within the Contractor’s organization and on all subcontractors whenever contract work is performed. |
| REQ-102 | Quality Assurance | Testing | A QA Program Plan shall be submitted for review within 30 days of Notice to Proceed (NTP). The QA Program Plan shall describe the methods for planning, implementing, and maintaining quality, schedules, and cost. The QA Program Plan shall contain a company policy statement that clearly defines the authority and responsibilities of QA personnel. |
| REQ-103 | Test Plan | Testing | The Contractor shall develop test plan(s) and detailed test cases, with acceptance criteria, cooperatively with RTD which demonstrates all requirements have been met. |
| REQ-104 | Test Plan | Testing | The Contractor shall supply, to RTD, a detailed test plan that spells out the types of testing that will be performed, testers, and schedule. |
| REQ-105 | Documentation | Documentation | The Contractor shall use RTD's Microsoft Team Site or Confluence for document sharing/repository. |
| REQ-106 | Documentation | Documentation | The Contractor shall provide User Guides in the document repository. |
| REQ-107 | Documentation | Documentation | The Contractor shall provide Technical Specifications in the document repository. |
| REQ-108 | Documentation | Documentation | The Contractor shall provide Deployment and Maintenance Procedures in the document repository. |
| REQ-109 | System Recovery Plan | Documentation | The Contractor shall provide a system recovery plan detailing the procedures and timelines in ensuring system operability is restored within 24 hours. |
| REQ-110 | System Implementation Plan | Documentation | The contractor shall deliver a comprehensive system implementation plan that includes data migration processes. |
| REQ-111 | System Implementation Plan | Documentation | The contractor shall deliver a comprehensive system implementation plan that includes knowledge transfer documentation for RTD’s internal teams. |
| REQ-112 | Cross-Collaboration | Project Management | The Contractor's dedicated project team shall collaborate with RTD's Marketing and Digital Communications team throughout the project timeline. |
| REQ-113 | Support Resources | Support-Maintenance | The Contractor shall provide phone and email support to RTD during [business hours Monday - Friday 8am - 5PM (Mountain Time)] to assist with any issues during the term of the contract. |
| REQ-114 | Maintentance and Support | Support-Maintenance | The Contractor shall provide support and maintenance for the application for 1 year after deployment. This includes bug fixes, enhancements, upgrades, patches, re-deployments to app stores. |
| &"Tahoma,Bold"&9Attachment B - Compliance Matrix | &"Univers,Bold"&9 &"Tahoma,Bold"&11 Solicitation Number |
| Solicitation Name | &26&KFF0000THIS IS A SAMPLE TEMPLATE ONLY |
&"-,Bold"&P of &N
File details come from the government source that posted it. Updated .