Shuttle Transportation Management Application Amendment Questions and Answers

Shuttle Transportation Management Application 36C25226Q0191 Questions & Answers The description in the provided doc states the requirement "Quick installation with no wiring modifications required , but we are wondering if the device will have access to the OBD-II port for power (or otherwise rely on its own battery)? The device will need to be plugged into the vehicle s OEM port.

Will all 10 GPS tracking devices be deployed at Jesse Brown VAMC only, or should the solution be architected with anticipated expansion to additional shuttles or facilities within VISN 12? Deployed at Jesse Brown Shuttles only. Are there specific operational challenges you are most focused on resolving (for example, long or unpredictable wait times, difficulty communicating route changes, accessibility concerns, or limited visibility for dispatch)?

No foreseen challenges since the shuttles already maintain a communication system application will augment the system in place for better communication with riders. Are there key performance indicators (such as on time performance, average rider wait time, or shuttle utilization) that you would like the contractor to measure and report routinely? Yes Who is the incumbent?

New requirement Are there site access, badging, or security onboarding steps that could affect the 30-day delivery and full operational capability schedule? No Approximately how many VA staff members do you anticipate using the administrative dashboard, and do you have a preferred format for training (virtual, on site, recorded modules) and timing (business hours vs. off peak)? ~28 Residents No training is planned. The app is self-explanatory.

Should the solution integrate with any existing VA systems (such as transportation scheduling tools, facilities dashboards, or other VISN wide platforms), or do you currently envision a stand-alone system? No. This system is strictly stand-alone. Are there required export formats or reporting cycles (e.g., monthly or quarterly summaries, CSV/Excel exports) we should plan to support out of the box? There will be an internal summary kept for Fleet Department purposes only.

In addition to the VAAR 852.239 series clauses cited in the RFQ, are there specific VA security templates or processes (e.g., security questionnaires, System Security Plan format, or an established path to ATO for similar SaaS solutions) that you expect the selected contractor to follow?

No Can you confirm whether the VA is seeking a rider application limited to fixed-route shuttle tracking and ETA visibility, or if there is any expectation for on-demand ride requesting or dispatch functionality as part of this RFQ? There is no expectation for on-demand ride requesting. The shuttles run on fixed routes and schedule. The solicitation specifies a quantity of 10 GPS tracking devices.

Should this be interpreted as supporting up to 10 trackable (online) vehicles, with no additional requirement for a minimum number of concurrently operating vehicles? Yes, this should be interpreted as supporting 10 trackable vehicles with no additional requirement at this time. Are shuttle routes and stops expected to be predefined and static, or should the proposed solution support frequent route or stop adjustments by administrative users? Shuttle routes and stops expected to be predefined and static.

Should the rider application strictly provide real-time vehicle location, ETA at stops, and notifications, or is there interest in future optional capabilities such as ride requests or stop selection, even if not required for award? Strictly provide real-time vehicle location, ETA at stops, and notifications, no other capabilities are required currently.