Specifications include, but are not limited to: The AOA has a strong preference towards solutions that can meet the following requirements. The State is open to both off-the-shelf solutions as well as custom-built solutions that may be created with existing software and technologies used by the State in addition to new ones that may be purchased. • Be a solution that has been successfully implemented in at least five public agencies like the State of Vermont within the past five years. • Be a fully integrated system that can handle standard performance measurement data acquisition, analysis, and reporting needs. • Be highly configurable, allowing integration with current and future systems containing performance data. • Be scalable and adaptable, capable of handling increasing data volumes and accommodating future growth or changes in requirements. • Support migration and integration of historical data. • Seamlessly integrate with existing systems and databases, including automatic scheduled ingestion of data from external systems. Data should also be made available to 3rd party systems in real time for reporting or increased visibility. • Be accessible through the web and allow for concurrent access. • Enable the creation of browser-based reports with setups customizable by external end-users, including sorts, groupings, and selection criteria. • Have data visualization capabilities, including tables, charts, graphs, combo charts, multiple dashboard components, and multiple output and print formats. • Allow for hyperlinks within data visualizations to direct to other sites or locations with contextual information or related data. • Allow for the combination of data visualizations and text to tell robust data stories. • Allow for the reuse of data, visuals, and text across the solution. • Include built-in math and statistical functions such as count, mean, median, standard deviation, sum and forecasting. • Include collaboration and sharing capabilities, enabling user collaboration, sharing of reports or visualizations, and commenting or annotation functionalities. • Allow sharing visualizations with or without sharing the underlying data. • Allow for both external and internal-only sharing. • Allow for Application Programming Interface (API) requests. • Allow for embedding within the solution and externally to the solution. • Support tagging or labeling data, making it searchable, and assigning it to specific groups or people. • Support searching by data source. • Allow for the use and manipulation of data by external end-users. • Prioritize a user-friendly interface and intuitive user experience to ensure ease of navigation and utilization for all users. • Ensure data security and privacy, adhering to industry best practices for protection, encryption, user access controls, and compliance with relevant regulations. • Support role-based security and provide an audit trail with user ID and date/time stamp for any changes made to application elements. • Enable data storage outside of any software application to avoid data loss. • Support shared back-end data storage and access across multiple departments and agencies. • Offer automatic notifications for preset update schedules. In addition to the above preferred requirements, the State is also interested in solutions that can additionally do the following: • Allow for the cascading and roll up of measures across organizational hierarchies. • Allow for the tracking of strategic objectives, priorities, and actions. • Have the ability to track improvement ideas generated at various levels in the organization.
