OpenGov Stories makes storytelling with data easier than ever. Put data in context with rich narratives, beautiful visualizations, user-friendly design, and powerful drill-down capabilities to inform technical and non-technical stakeholders alike, from educating citizens on strategic priorities to updating internal staff on new initiatives.
- Add narrative context to graphics and visualizations
- Static and interactive financial presentations
- Saved views and unique URLs for customized reports
- Document linking
- Report annotations
- Visualizations include pie, bar, stacked, line, or percentage graphs
- 24/7 Web-based availability
- Export directly as an excel, csv, or static image file
- Cross-department pivoting and filtering
- Tell a story with a customizable narrative
- Easy to understand interface improves citizen engagement
- Makes complex multi-fund accounting data understandable for everyone
- Save time responding to public information requests
- Put data in context
£4256 to £585000 per unit per year
+44 774 044 9843
|Software add-on or extension||No|
|Cloud deployment model||Public cloud|
|Service constraints||When needed, OpenGov will schedule downtime for routine maintenance or system upgrades (“Scheduled Downtime”) for its Services. OpenGov shall exercise commercially reasonable efforts to schedule Scheduled Downtime outside of peak traffic periods. OpenGov will notify Customer’s designated contact at least twenty-four (24) hours prior to the occurrence of Scheduled Downtime|
|Email or online ticketing support||Email or online ticketing|
|Support response times||OpenGov Product Support Service Level Objective is to respond within One (1) business day. However, The OpenGov support team’s first response time is typically 1 hour or less for most requests during support business hours. Active Staffed Support Business Hours: 7am - 7pm US Pacific Time Monday - Friday, excluding US Holidays. Responses to support requests are during these hours. Active Staffed Live Chat Support Business Hours: Monday – Friday 9:00 am – 5:00 pm US Pacific Time, excluding US Holidays. Responses to chats are during these hours.|
|User can manage status and priority of support tickets||No|
|Web chat support||Web chat|
|Web chat support availability||9 to 5 (UK time), Monday to Friday|
|Web chat support accessibility standard||None or don’t know|
|How the web chat support is accessible||Users click on a live chat support link and a window will open up to allow users to chat with our support team during our support business hours. Our live chat is text based|
|Web chat accessibility testing||None|
|Support levels||We currently have one level of product support. Product support is included with the software subscription.|
|Support available to third parties||Yes|
Onboarding and offboarding
The On-boarding process involves a kickoff call with the Customer’s project team and the OpenGov team to align on the priorities/objectives of the Customer and measures of success.
The Customer’s OpenGov Administrator(s) will be instructed on how to upload data into the OpenGov Platform, create and configure reports, use the Chart of Accounts editor, along with other OpenGov features. The deployment process officially comes to an end after the Customer has been trained on how to administer their platform and maintain it moving forward.
After the OpenGov deployment, OpenGov will begin hands on mentoring and training of the Customer’s staff to demonstrate how to use and configure the platform. In addition, Customers will have access to the following training materials:
• Live Webinars: Our webinars feature government finance experts and successful Customers’ use cases to ensure the trainings are relevant and impactful.
• OpenGov University: OpenGov maintains an extensive library of online on-demand video trainings. OpenGov University enables our customers to learn the skills they need to best utilize Open Data at the time that best suits their schedules.
|End-of-contract data extraction||Immediately upon receiving a written notice to terminate or suspend Services, (1) OpenGov shall discontinue advancing the work in progress, or such part that is described in the notice; (2) the Customer has access to export all previously uploaded data directly from the platform; (3) the Customer may request that OpenGov returns all collected raw data, draft reports, preliminary reports, working papers, estimates and forecasts entirely or partially completed, together with all unused materials supplied by the Customer.|
OpenGov has created a deployment process designed to have customers up and running on OpenGov as quickly and effectively as possible. At a high level, OpenGov asks the customer to send us their data files including their full Chart of Accounts & General Ledger extract. As part of the deployment, a CSA will format the data as needed, load it onto our platform, create reports, and validate the CoA and General Ledger data with the customer.
Once the platform review is complete, OpenGov will conduct an Administrative and User Training. The customer will then transition to full usage of the platform and will work with OpenGov to maximize the value of the platform.
Features and services beyond the scope of work are subject to additional costs.
Using the service
|Web browser interface||Yes|
|Application to install||No|
|Designed for use on mobile devices||Yes|
|Differences between the mobile and desktop service||Users can access all functionality available on the desktop service through their mobile device.|
|Accessibility standards||None or don’t know|
|Description of accessibility||OpenGov adheres to a large portion, but not all of the WCAG accessibility 2.0 standards. Under the perceivable category, OpenGov provides functionality consistent with the distinguishable and adaptable guidelines. Under the operable category, OpenGov provides functionality consistent with clear navigation, we avoid flashes, and we don't have content with time limits. Under the understandable category, OpenGov provides clear page layouts with information hierarchy and make sure all text, charts, tables, links, and buttons are readable and understandable.|
|Accessibility testing||OpenGov performs user testing on all of our products, including testing to determine accessibility. OpenGov has performed specific accessibility reviews, including VPAT and other tools which give accessibility recommendations. Additionally, we have incorporated many of our government customers' feedback to improve our platform and become more accessible. OpenGov is working toward any gaps we have in accessibility and becoming WCAG 2.0 AA compliant is on our roadmap.|
|What users can and can't do using the API||Our APIs enable integrations.|
|API documentation formats||
|API sandbox or test environment||Yes|
|Independence of resources||OpenGov horizontally scales the platform to ensure SLAs for customers|
|Service usage metrics||Yes|
|Metrics types||The OpenGov Portal has user analytics available to the Entity Administrators directly on the Portal. Customers have access to analytics such as how many visitors their page receives, how long the visitors are staying on the page, how many clicks they are making, and which browser the visitor is using. These metrics are available for 7, 30, and 90 day intervals.|
|Supplier type||Not a reseller|
|Staff security clearance||Other security clearance|
|Government security clearance||None|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing locations||Other locations|
|User control over data storage and processing locations||No|
|Datacentre security standards||Complies with a recognised standard (for example CSA CCM version 3.0)|
|Penetration testing frequency||Less than once a year|
|Penetration testing approach||Another external penetration testing organisation|
|Protecting data at rest||Physical access control, complying with CSA CCM v3.0|
|Data sanitisation process||No|
|Equipment disposal approach||Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001|
Data importing and exporting
|Data export approach||
Users can navigate to their dataset of interest, and export the raw data file in an XLSX format.
Additionally, there are exporting functions in each OpenGov report. Data can be exported into CSV or JPG formats from the reports.
|Data export formats||
|Other data export formats||XLSX|
|Data import formats||
|Other data import formats||XLSX|
|Data protection between buyer and supplier networks||TLS (version 1.2 or above)|
|Data protection within supplier network||Other|
|Other protection within supplier network||Access to our internal network is limited to users with public-private key authentication.|
Availability and resilience
OpenGov maintains an SLA for 99.9% uptime, excluding planned windows of scheduled downtime.
If uptime falls between 99.00 and 99.9%, OpenGov will credit 10% of the customer's monthly subscription cost to future monthly bills of the customer.
If uptime falls between 95.00 and 99.00%, OpenGov will credit 25% of the customer's monthly subscription cost to future monthly bills of the customer.
If uptime falls below 95%, OpenGov will credit 50% of the customer's monthly subscription cost to future monthly bills of the customer.
|Approach to resilience||To avoid datacenter or server disruptions, OpenGov relies on Amazon’s multi-availability zones to ensure that we can continue operations in case of a datacenter or server failure. We host our production servers and databases in an Amazon region. These regions have multiple zones, each with their own datacenter. Across these zones, data is continuously replicated. If a datacenter in this region goes down Amazon will immediately switch to another datacenter in the region.|
|Outage reporting||OpenGov emails its customers to report service outages, When we encounter partial outages we use in-app notifications to keep customers informed.|
Identity and authentication
|User authentication needed||Yes|
|User authentication||Username or password|
|Access restrictions in management interfaces and support channels||OpenGov uses role based security to limit access to management interfaces and support channels|
|Access restriction testing frequency||At least every 6 months|
|Management access authentication||Username or password|
Audit information for users
|Access to user activity audit information||No audit information available|
|Access to supplier activity audit information||No audit information available|
|How long system logs are stored for||Less than 1 month|
Standards and certifications
|ISO/IEC 27001 certification||No|
|ISO 28000:2007 certification||No|
|CSA STAR certification||No|
|Other security accreditations||No|
|Named board-level person responsible for service security||No|
|Security governance accreditation||No|
|Security governance approach||OpenGov is pursuing SOC2 compliance by 2018|
|Information security policies and processes||OpenGov uses Amazon Web Services (AWS) to host its data. Security information for AWS is available here: http://aws.amazon.com/compliance/. All external and public traffic occurs through HTTPS to prevent man-in-the-middle attacks, namely snooping and tampering with the data. AWS’ servers are only accessible through SSH with private key authentication. Thus, only employees who need access to servers are given access and AWS practices the principle of least privilege. All server and application logs are sent to a central log server that keeps track of everything occurring. AWS ensures that only those with valid credentials can access the database and AWS creates nightly backups for our databases that are stored for up to thirty days in multiple datacenters. AWS also uses multiple availability zones to automatically switch data centers in the event of a data-center failure. AWS internally reviews their security procedures on a quarterly basis. OpenGov reviews its security policies on a quarterly basis and is notified if there are any security breaches in its AWS databases.|
|Configuration and change management standard||Supplier-defined controls|
|Configuration and change management approach||OpenGov uses GitHub for its source code management. All changes to any code are tracked and can be reverted if needed. OpenGov maintains three release types under which all changes to our software are managed: Five Week Releases consist of major software updates. Before finalizing a release, there is extensive testing to ensure the release will be successful, both in terms of functionality and security. Weekly Maintenance Releases consist of fixing critical problems on the platform. All weekly maintenance releases are reviewed and tested internally. Hot Fixes consist of fixing any blockers on the platform and are prioritized for release.|
|Vulnerability management type||Undisclosed|
|Vulnerability management approach||OpenGov evaluates Open Source components for vulnerabilities. We also subscribe to security alerts from our vendors such as Ubuntu's security mailing list and monitor vulnerability services like full disclosure. Depending on the level of vulnerability we either patch our production environment as an immediate hot fix or a weekly maintenance fix.|
|Protective monitoring type||Undisclosed|
|Protective monitoring approach||OpenGov subscribes to vendor email alerts to identify breaches in OpenSource components and services. Internally, OpenGov is developing a robust auditing framework to detect potential compromises. Once a compromise is discovered, OpenGov’s breach disclosure policy is to generally disclose incidents without delay. However, delays may occur due to the investigation. For example, delays are sometimes required by law-enforcement.|
|Incident management type||Undisclosed|
|Incident management approach||
OpenGov maintains a 24hr incident response team that is activated to respond critical incidents. Once reported, incidents are monitored, and if needed, periodic updates are sent to affected customers. After every incident OpenGov holds postmortems to evaluate what went wrong and how to prevent the same incident from happening again.
Incidents are reported to our support team via email or in product chat. We maintain an internal escalation process to prioritize, address, and track issues.
We provide incident reports to customers upon request.
|Approach to secure software development best practice||Supplier-defined process|
Public sector networks
|Connection to public sector networks||No|
|Price||£4256 to £585000 per unit per year|
|Discount for educational organisations||No|
|Free trial available||No|
|Pricing document||View uploaded document|
|Service definition document||View uploaded document|
|Terms and conditions document||View uploaded document|