The vendor is required to provide crash data entry portal will fill a critical need to collect complete crash data electronically to expand our analysis and allow the office to better allocate resources to address high-crash areas, with the goal of saving lives of state residents.
- The crash data is then analyzed using rudimentary crash details (date, time, location) in an excel spreadsheet on an annual basis.
- Crash data entry web portal including:
1. Data accessibility: provide local police departments with a user-friendly interface for submitting crash data in a secure and efficient manner.
2. Data validation: ensure data accuracy and completeness through automated validation mechanisms.
3. Integration: seamlessly integrate submitted data into the state’s vision© crash database; vision© is a custom-built, on premise solution based on the Microsoft dynamics platform.
4. Security: comply with applicable data security and privacy standards.
-  Requirements:
• Provide an overview of the portal’s architecture and functionality.
• Describe the technologies and platforms used.
• Provide a high-level implementation timeline with milestones.
• Explain how your solution can support both MMUCC5 and MMUCC6.
• Outline the implementation timeline to move from MMUCC5 to MMUCC6 with state-specific requirements.
- User authentication and access control:
• Describe your user authentication and access control methods. (Multi-factor authentication, role-based access control, etc.)
- Data entry and validation:
• Describe your use of intuitive forms for manual data entry.
• Explain how your solution uses automated data validation to check for missing or incorrect fields.
• Indicate whether your solution supports attachments, such as scanned documents or images.
• Identify any local storage capabilities your solution provides.
• Describe your solution’s use of multi-tenancy, if applicable.
- Data integration:
• Explain how your solution will provide API integration with the state’s vision© crash database.
• Indicate whether your solution involves real-time data synchronization.
- Audit and monitoring:
• Explain your solution’s comprehensive logging of all user activities.
• Describe your solution’s audit trails for data submission and modification.
- Security and compliance:
• Outline the type of data encryption used during transmission and storage.
• Explain what measures are used to ensure data security and compliance.
• Indicate whether your solution is compliant with CJIS, NIST, and other relevant security standards.
- User support and training:
• Describe the online training materials and user guides you will provide.
• Outline your support model.
- Maintenance:
• Explain what type of maintenance programs you offer.
- Questions/Inquires Deadline: February 14, 2025