- When independently validated support quality and guaranteed response times are required
- Public community feedback includes strong criticism of support in some anecdotes. Agencies with low tolerance for vendor support risk should insist on contractual SLAs, named escalation paths, and reference calls with similarly sized agencies.
- When the dispatch operation is highly sensitive to modern UI/UX and contemporary workflows
- Community feedback suggests some users perceive the UI as dated and that mobile readability can be problematic in field conditions. Agencies prioritizing modern UX should require hands-on dispatcher-led demonstrations and usability testing.
- When organizational capacity for remediation is limited
- The Stafford County assessment indicates that severe implementation issues can occur. Agencies lacking resources for remediation should require staged rollouts, performance acceptance tests, and contractual remedies.
- When explicit, public security and compliance documentation for the specific product is required
- Infor provides broad trust resources, but EnRoute-specific certifications and CJIS-related documentation were not clearly public in sources reviewed. If procurement processes require product-level public attestations (not available upon request), acquisition timelines may be prolonged.
- Current limitations acknowledged by users
- Mobile readability and UI scaling issues (font size on iPad in apparatus mounts).
- Missing personalization features (for example, persisting column settings across logins).
- Roadmap / future features
- Public roadmap details were not located in the sources reviewed.
- Scale limitations
- No hard public limits (events/day, concurrent users, map object volumes) were found in accessible sources.
- The Stafford County case indicates performance problems can arise; procurement teams should require performance benchmarking that matches expected call volumes and AVL update rates.
- Security or compliance gaps
- EnRoute-specific security certifications and CJIS-related public documentation were not found in the accessible sources; procurement should treat this as a documentation gap until verified directly with Infor.
- API limitations or integration constraints
- Public interface details are not comprehensively documented in open sources; the ecosystem appears interface-heavy and likely requires ongoing integration maintenance.