1. What’s Next The Collibra Roadmap Stijn “Stan” Christiaens
Co-founder and CTO
May 2, 2017
Opening statement: Thank you for taking time to attend this session on data governance leads to data quality
Name: I am Kash Mehdi
Responsibilities: Senior Product Specialist and Instructor at Collibra
Experience: Been with Collibra for about 3 years now started back in 2014 when Collibra was just starting out and we had a 2 months old office right on the Wall St. I am moved here from Arkansas (it’s a long story…), prior to joining Collibra I worked as a researcher for a national cancer institute where I creted an ontology driven data quality framework to effecitively capture clinical trial data. Here at Collibra I have been working in all different industries including finance, healthcare, government, retail, and more.
Timeline: The session is going to take about 30mintes or less and at the end we will have time for questions.
Topic: Data governance leads to data quality

2. Disclaimer
This presentation is intended to outline our general product direction. It is for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Collibra products remain at the sole discretion of Collibra.

3. Scarcity VS Abundance • Data is every where from many sources
The Age of Abundance
Scarce data
• A by-product of process execution
• Expensive to store
• Completely described ahead of time (supposedly)
• Centralized processes and processing
• Store only what you know you need and nothing more
Abundant data
• Data is every where from many sources
• Costs little to keep
– Constraint is on how much it can be found and used
• Search the data to find the valuable bits
• Enrich it as it is used
• Everyone contributes to the knowledge about the data

4. Organizations and Data Practices Change
Scarcity
Data warehouse
Regulatory focus
Control orientation
Abundance
Data lake
Enablement
Self-service

5. How Data Governance Changes in the Age of Abundance
From data scientists through data citizens
Diversity of users, diversity of objectives
Engage the data citizen
Cover all the use cases, and all usage styles and modes
The lineage that really matters
Value comes from usage
Navigate the information to find the suitable data
Solid, stable and scalable platforms
Data processes
Trust in the data and process
Manage the value of your data assets
Substantiate valuation
System of record
This should follow the headlines of the content slides.

6. (Re)Defining the Data Governance Category
2017
2020+
Lead the Data Governance Category
Data System of Record
Expand the Data Governance Category
Data System of Engagement
Surpass the Data Governance Category
Data Value Platform
Strategic
Objective
Product Strategy

7. Strategic Themes for Product
Focus
Usage to Value
“The data lineage that really matters”
Engage!
“Every data citizen is a Collibra user”
System of Record
“The system of record for the data authority”
Extend!
“Designed for extensibility (elegance)”
Rock solid
“Enable enterprise-wide trust”

8. Every Data Citizen is a Collibra user
Engage!
Every Data Citizen is a Collibra user

9. From Data Scientists Through Data Citizens
I need to understand the characteristics of this data
– Hélène, Data Scientist
I need to get the latest information about my campaigns before this meeting
– Joanna, Marketing
I need to organize the data in my own way for my project team
– Luke, Project lead
Demo of tagging profiling and mobile. Recommendations?
Not only do we have different styles of users, we have different roles and organizational relationships. They need to be engaged across the enterprise.
Users must be able to clearly determine the suitability of data for their purposes, not for some general case.
Tagging – need words/classify data in own ways
Profiling – Data scientists need to understand the statistical nature of the data
Mobile – occasional users need simplified access from wherever they are.
Every one needs customized recommendations

10. Step 6 of ingestion process: generate new code set (alternatively add to existing code set)
Domain/Community: created on the fly?

11. The lineage that really matters
Usage to Value
The lineage that really matters

12. The Lineage That Really Matters
The value of data is in its use
Find
Understand
Trust
VISUAL
TEXTUAL
How many of you prefer to look at spreadsheets? How many prefer graphs. ?
Value comes when people use the data
They need to find and understand and engage with the data to use it
Mention Catalog on day 2
Talk about visual exploration of the information
Demo Lineage diagrams
Management of distributed responsibilities (new stewardship stuff)
KEYBOARD
MOBILE

13. Data Governance Center
Paradigm Shift: Never leave the Diagram
Style makeover
Easy to navigate
Trace, collapse, and condense
Smart explore
Filter on all nodes and attributes
Easy to understand
Informative overlays on key attributes
Rich content
Easy to configure
Interactive Canvas
Add assets, relations in the diagram
Static versus generated diagrams
The Tag line for the new developments in the context of data lineage is “Never Leave the Diagram”. With this tag line we want to reinforce our product vision message that we want to drastically improve the capabilities of diagrams and allow our users to be able to do much more – or even everything they need to be able to do – from within the diagrams. As I mentioned in my blog post on lineage we ‘d like to realize a paradigm shift.
In terms of features we will focus in release 5.1 and beyond on the following:
See bullets
Now let’s have a closer look at the feature for 5.1

14. Step 6 of ingestion process: generate new code set (alternatively add to existing code set)
Domain/Community: created on the fly?
Data 2020

15. Designed for extensibility
Extend!
Designed for extensibility

16. Solid, Stable, Scalable Platform
Governance insight
Scalable data processes
Trustworthy, governed information
Focused on the processes that enable use and value capture
Manage and record that environment.
Create trust in the information delivered from the platform and its applications
Insight into the activites and information within the platform (reporting)

17. The Value of a Platform is in its Extensibility
Extensible, configurable, reproducible
Address new use cases
Accommodate new technologies (spark, IOT, AI, etc. )
Enable others to innovate
Extensions
API
Extensions
Extensions
Core platform
Extensions
Integration mechanisms
So much data – don’t know what’s coming w/ IoT, AI/Machine Learning – need to account for those
Designed for extensibility – APIs, marketplace, and all that kind of stuff
Demo marketplace and one of the extensions from Ram or partner

18. The system of record for the data authority

19. Valuable Assets Need a System of Record
The lifecycle of data assets needs to be managed
Their value needs to be assessed
And their attributes, whatever they are, need to be maintained. This includes new attributes that come with new types of data (IOT) and new capabilities
Records need to be continually enhanced
Demo anyting relating to lifecycle.. Heatmaps, etc.

20. Reference Data
Ingesting reference data code sets into Collibra from a variety of sources, including databases
Defining code patterns to govern reference data at the core
Building and managing structures over the code sets of reference data
Mapping of code values between code sets combining filters and diagrams
Versioning of code values, code sets, code mappings
Our Insights product is for the moment still in prototype phase and therefore only meant to discuss our plans, ideas, features, general direction with you.
This is how Insights in Collibra might look like.
Until today we had more than 15 intensive sessions with existing customers, most of these customers endorsed our plans and are excited about them. So it is safe to say that we got green light from you and even better we received fantastic suggestions to even make the Insights application better!
Our goals is to provide you with a flexible, configurable and easy to use analytic capabilities from within the product to meet like most (80%) of your existing reporting requirements. Our goal is to allow you to report from within Collibra or without having to leave Collibra to give you a more seamless experiences.
The remaining 20% of your needs, which are obviously more complicated, we would fix this with providing you a reporting data layer which would allow you to build your own reports from that data layer with tools like Tableau, Qlik, PowerBI, etc.
Let’s have a quick look at the key features for the upcoming releases of Insights:
- Next slide

21. Step 6 of ingestion process: generate new code set (alternatively add to existing code set)
Domain/Community: created on the fly?

22. Step 6 of ingestion process: generate new code set (alternatively add to existing code set)
Domain/Community: created on the fly?

23. Step 6 of ingestion process: generate new code set (alternatively add to existing code set)
Domain/Community: created on the fly?

24. Step 6 of ingestion process: generate new code set (alternatively add to existing code set)
Domain/Community: created on the fly?

25. Step 6 of ingestion process: generate new code set (alternatively add to existing code set)
Domain/Community: created on the fly?

26. Summary Engage all the users Focus on usage as the driver of value
Deliver a solid, stable, scalable platform
Extend the environment to incorporate rapid change
Act as a system of record

27. Data Governance Center
5.1
5.2
5.3
5.4
Upgrade
Diagrams
Catalog
Advanced Filters
Browser
API v2
Apache Spark
Performance Improvements
Feedback Beta Program
Diagrams
Catalog
Feedback Beta Program
Validation rules
Performance
Diagrams
Insights
Catalog
Import
Collaboration
Performance
Diagrams
Insights
Catalog
Collaboration
Reference Data
Controlled Publication
Versioning
Q3 ‘17
Q4 ‘17
Q1 ‘18
Q2 ‘17
Improve RD WF
RD Catalog
RD Hierarchies
RD Code Mapping
Complex Relations
Improved User Experience
Reference Data
Improved Audit
Granular Point in Time Restore
Partial Restore
Version Management
Replace Snapshots
Change Management
Let’s have a look a the roadmap for Data Governance Center for 2017 and beyond.
Release 5.1 the main themes of the release are
Lineage – more on lineage in the next slides
Catalog – peter will talk about the new cool stuff for Catalog later during this webinar
Upgrade
Now a quick word on upgrade. The goal of our upgrade is to be able to get most of our 4.x install base to the latest version of release 5. I firmly believe that this will be possible. However since we decided to take out a number of existing functionality and substantially improve that in future releases like Code Mapper and Snapshots, some customer might want to wait before they decide to upgrade.
I would also like to mention that there is – based on the current progress – a chance that we will have to de-scope the Validation Rules from 5.1. So those customer that are using our Validation Rules might not have this in release 5.1 and prefer to wait for release 5.2.
We did however decide to include an intermediate release in Q3 (July) to be able to bring faster features to market for Catalog and Data Lineage Diagrams. If Validation Rules drops from the scope of 5.1 , we will include it in this intermediate Q3 release.
Towards the end of the year we plan release 5.3
The main themes of this release will be:
Catalog
Data Lineage Diagrams
Insights – our new and improved reporting capabilities
This release will also come with drastically improved Import capabilities and performance improvements. We will also continue to focus on making it easier for you to engage more people by developing a set of Collaboration features like tagging, rating, user mentioning, etc.
Within PM we have already started with two new prototypes – like we made the Insights prototype – around Reference Data and Change Management. In the reference data we aim to make it easier to onboard reference data, to automatically link it to business terms, to build more usable hierarchies and mappings for reference data.
For change management we aim to make auditing easier, compare versions of assets, restore from the asset history, put assets in draft and then publish them to broader community, etc.
All very exciting things!
Now let’s have a closer look to the new developments in the context of Release 5.1 and beyond.

28. Research Projects Usage to Value
Artificial intelligence recommendation improvements
Duplicates
Engage!
Natural language/chatbot AR
Extend!
Hackathon hangman
Note.. I made these up.. Need to confirm with Stan

29. What’s Next Visit Product Management in Collibra Corner
Sign up for the Quarterly Roadmap Updates (via DeeCee Touch)
Sign-up for the User Participation Program (UPP)
Mention product manager for a day sessions – indicate they are happening but are fully subscribed

30. Thank You
Stijn “Stan” Christiaens