FlockData, the data integration that I’ve been working with, is progressing along a normal startup progression scale. This means that it’s getting built, with a mix of customer success and setbacks.
We’ve been talking with customers in a wide range of industries:
- Financial services
- Health care
- Medical research
- Social media
- A few others
Mostly, we’ve been focused on asking the question:
Do you have problems that are best answered by data
that spans multiple systems?
And the answer has been a firm yes. In fact, we’re hearing that I in CIO is coming back to its original meaning – information, after years of focus on infrastructure. CEOs and boards of directors are looking at the CIO, realizing that he or she is sitting in the position with the deepest understanding of:
- What data assets a company has
- What systems that data are in
- Who has and should have access to the data
- Where the potential integration and export points are for the data
- How the data might be accessed
So what about you? Do you ever get challenged by data not all looking the same? Read this post to see how schemas are blocking that insight. Schemas keep the data stuck in exactly the format that it lives in natively. Of course, that’s fine for the data within its source applications (also sometimes called systems of origin or OLTP, online transactional processing applications), but it’s limiting.
What about for understanding the data within the entire business context?
This is where FlockData’s data integration and logical data warehouse can help. Simply load data in a business-aware context, and FlockData will go to work indexing the data in ways that help point you in the direction of understanding your data. If you want to learn more about it, you can ask me or contact the FlockData team.