confirmit hub n.
Skip this Video
Loading SlideShow in 5 Seconds..
Confirmit Hub PowerPoint Presentation
Download Presentation
Confirmit Hub

Confirmit Hub

202 Vues Download Presentation
Télécharger la présentation

Confirmit Hub

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Confirmit Hub What’s New in Confirmit Felix – 2013-08-07 Ole Andresen Director, Product Management

  2. Confirmit Hub - Overview The introduction of the Confirmit Hub in Confirmit 18 serves two main purposes: • Act as a replacement/alternative to the proprietary “BitStream” columnar database for analytics/reporting, offering further improvements in performance, scalability and stability of our reporting solutions (handling millions of records). It will also make life easier for SaaS Operations/On Premise clients. • Allow data sources of different types to be brought together for use in dashboards, analysis, action management, and other areas.

  3. Main use cases The Confirmit Hub should provide good support for two main “classes” of use cases: • Reporting and analytics on independent, ad-hoc surveys, whether it is done through Reportal, Active Dashboards or the new Ad-hoc Analytics capabilities that will be introduced in version 18. • Reporting and analytics on survey programs (VoC and other types of programs) where we bring multiple data sources of different types together. This is done through a new module called the Hub Designer where we define which data sources that should be brought in and the relationships between them, so that we can build dashboards and reports performing analysis across these data sources.

  4. Supported Surveys/Panels The Confirmit Hub will support: • Surveys (Professional/Express/Polls) on Optimized DB format • Standard Panels/Professional Panels The Confirmit Hub will not support: • Surveys on Legacy DB format • Basic Panels

  5. Hub Database Technology The Confirmit Hub is built onColumnstore Indexes, which was introduced in MS SQL Server 2012. Columnstore Indexes can read and process very large datasets quickly. This requires MS SQL Server Enterprise Edition, so On-Premise clients that want to use the Confirmit Hub, will have to have Enterprise Edition installed. Note that BitStream will still be supported in Version 18, so Enterprise Edition is not mandatory for Version 18, but without it On-Premise clients will not get access to the Hub functionality. Over time BitStream will be phased out and we will only support SQL Columnstore Indexes (exact timing TBD).

  6. On-Premise Availability The Hub will be included in version 18 for both SaaS and On-Premise clients (if on SQL Server Enterprise Edition). In version 18 there will be 3 reporting platforms available on top of the Hub: Reportal, Ad-hoc analytics (new) and Active Dashboards (from CustomerSat). In addition CustomerSat’s Action Management platform will be integrated with the Hub. Availability:

  7. 1. Single survey data source – replacing BitStream

  8. Replacing BitStream Nothing will automatically change when Version 18 is introduced. Existing reports will continue to use BitStream just as now, and BitStream will continue to be supported. Users will have to specifically switch to using Confirmit Hub for existing reports.

  9. Using Hub for single-survey reports For single-survey reports, users can generate a Hub for reporting and analysis in similar way to generation of BitStream files: Currently you also need to «Enable Change Tracking» in Survey Management->Overview, but this will be changed to happen automatically behind the scenes.

  10. Use BitStream or Hub in Reportal • You can create both Bitstream files and Hub on the same project, and switch between the two back-ends in Reportal. So we are able to directly compare the BitStream and Hub analytics engine. • When reporting off an independent survey the report is set up just as today, selecting the survey as source in the create report wizard. • For a project on optimized db format, unchecking “Use BitStream files” means Hub will be used. For a project on legacydb format, unchecking it means the old SQL tabulation engine will be used, not Hub.

  11. Reportal functionality not yet supported The following functionality is not yet supported in reports using Hub as back-end, but we are working on it: • Hitlists/Single View/Verbatim tables • Recoded variables • Cluster/factor/regression/correlation • Fiscal Calendar • Standard and Professional Panels • Filter expressions

  12. Reportal functionality not supported The following functionality will not be supported in Reportal reports using Hub as back-end: • Timezone offset (may come after v18) • Basic Panels • Legacy Dbformat • Filter tree/TGL filter/Simple filter In addition, data sources with multiple surveys, joins and unions will require using the Hub Designer instead of the current data source functionality in Reportal.

  13. Loop handling (One-to-many) With the Hub we are introducing two long requested new features for reporting across loop levels in a survey. Examples: • Doctors->Patients->Drugs • Traveler->Trips • Household->Household members These features are: • Aggregation level • Pre-aggregation These features will also be supported in one-to-many relationships defined in the Hub Designer.

  14. Aggregation Level Currently level of aggregation is chosen automatically as the lowest level in an intersection among all groupings, measures and filters in an aggregated table. This means you can aggregate on the lowest level, so you can for example do a table to get the number of male and female patient’s grouped by the doctor’s location in the survey on the right.But you can not get number of doctors, grouped by location, that have patients that use a particular drug, i.e. aggregating on a higher level. Also, you can not process intersections with variables from different branches, so combining data on household_members with data on household_cars in the example on the left hand. (“Car brands in household by age of household members.”)

  15. Aggregation Level Current behavior (lowest level) will continue to be default. In addition, users can now set level of aggregation, as a property on tables, so that you could set “doctors” as the level when crossing with “drugname”. Also, for more complex examples involving crossing variables from different branches, the system should be able to select default aggregation level as the lowest common level, i.e. the household in the left example.

  16. Pre-aggregation When aggregation level is not the lowest level, there will be a two-step aggregation: First aggregate on lower level, and then aggregate on the higher level. This is called pre-aggregation. To support this, we have introduced pre-aggregation functions in addition to the existing aggregation functions: Average (default), Count, Max, Min, Sum. This way we can combine different pre-aggregation and aggregation functions, and retrieve for example average number of people per household (Average of Count). Pre-aggragation is a newpropertyon header variables.

  17. 2. Multiple data sources – Hub Designer

  18. Multiple Data Sources The Backbone of Confirmit Voices The Confirmit data hub is a centralized area for data management and optimization. It allows data sources of different types to be brought together, relationships defined, and readied for use in dashboards, analysis, action management, and other areas. • Key Functions of the Hub • Bring data in from different sources into a single environment • Surveys • Customer and employee databases • Organizational Hierarchies • CRM / Financial Data • Benchmarks • Structured / Unstructured • Monitor and manage continual data feeds • Resolve issues that arise • Merge data across sources • Example: A global NPS score merged from all transaction surveys • Map data sources together • Example: Map revenue data to the hierarchy • Prepare data for use in reporting, analytics and action management

  19. Hub Loader – Near real-time updates With the Hub we will continuously move data from surveys and other data sources over to a separate database (with SQL column indexes) for reporting and analytics, just as for BitStream files. The Confirmit Hub will support “near real-time“ updates of data, as an alternative to updating according to a set recurrence pattern (e.g. daily) as today. The Hub Loader will continuously (every 5 minutes) check data sources for changes, and trigger a synchronization of data when necessary. Both data and meta data (survey schema) will be synchronized.

  20. Hub Designer The Hub Designer is a new Confirmit module that will be introduced in version 18. In the Hub Designer users set up a Hub, select which data sources that should be made available in the Hub, and define relationships between the data sources. In addition the users should be able to go to the Hub designer to monitor data feeds into the Hub, resolve issues etc. We expect most enterprise clients to have one Hub for their VoC program. MR companies, VoC consultancies as well as Confirmit users will be working with multiple Hubs, at least one per company they are working with.

  21. Hub Designer

  22. … be continued….

  23. Test server • Hubfunctionalitywill start appearingonauthor.testlab in a fewweek’s time. • Untilthen, Hubfunctionalitycan be testedonhttp://osl-devb70-ht01/confirm/ (contact me for logins) • Wewould like to getaccess to somelarge, real databases for testing. Please let meknowifyou have anycandidates.

  24. Thank You Ole Andresen | Director, Product Management