Michael F. Koehler
Analyst
Okay. The way we would characterize it is, like you said, core to Teradata was the integrated data warehouse, an Enterprise Data Warehouse. And in a way, it's a no-brainer, it's a best-in-class architecture and reduces a ton of cost by centralizing data that can give better insight into the business when it's integrated from other data across the enterprise. And it also, as I discussed earlier about our Active Data Warehouse Private Cloud, it consolidates underutilized data marts and puts them in one central location to be shared with multiple organizations, multiple users and everything else and drives a higher utilization, and as a result, reduces data center footprint and gets a ton of costs down. So for data that has better value being integrated and for data that is relevant and should be used by multiple organizations in a company, an Enterprise Data Warehouse is, without a doubt, the right architecture. Think of that as a workload. So it's a workload or data that's used by lots of people, lots of organizations and shared throughout the company to get higher utilization, lower costs, better information. So what we saw with the workload-specific data warehouses or the platform family is -- what we began to see is there's workloads such as our Extreme Data Appliance where it's lots of history, if it's archival or regulatory or it's clickstream data from the web that, that data is relevant to less people within the organization. So our 1000 series Extreme Data Appliance, we build something that has lots of storage, can have lots of data in it, but it doesn't have a lot of CPU to serve a lot of users, and in effect, we’re building a configuration that is a much lower cost per piece of data than an EDW to serve a smaller group of people that are using it. So it's workload-specific. So when you look at the Aster Data Appliance once again, in Aster Data Appliance, you're doing exploratory and discovery types of analytical analysis on big data. And you don't need a mission-critical environment similar to the 1000. You don't need all the robustness that you need in an Enterprise Data Warehouse, and you're using it with a smaller group of users. So it gets back to a workload that's more specific for a limited number of users and requirements that aren't the same as running your company on the data warehouse like our EDWs. Our customers in EDW’s side need 49s [ph] availability. It's mission-critical. The thing is critical. So we continue to slice and dice workload-specific data warehouses to address different workloads and different user sets in addition to an Enterprise Data Warehouse to integrate and share data and information across all the organizations that's required, because in that environment, that's the lower-cost solution.