Frequently Asked Questions?
CluedIn is essentially a data processing pipeline and hence the more data, with the more functionality happening on this pipeline - results in the need for more CPU Cores.
In general, it is typically the case that more data = more CPU Cores, but we would like to talk about some of the detail.
Simple data is typically more efficient to process than complex data.
So what is "Simple Data"?
Data that has structure and is typically in tables is considered simple data in CluedIn's eyes.
Complex data is typically reserved for unstructured data such as files, mail and data with complex structure.
Simply put, simple data costs less CPU cycles in CluedIn because we are doing "less" to mature that data.
In saying that, the cleaner your data is to start with and the less that need to be done, will also result in the need for less CPU cores.
Technically, no. But practically? Yes. CluedIn only charges for CPU processes that are taken by the processing pipeline and hence the CPU cores for databases and other parts is not counted and doesn't require a CluedIn license.
CluedIn is a highly optimised processing engine and makes the assumption that you will be utilising many threads to process your workloads. Although CluedIn runs on one CPU Core, in production you will need more than one to achieve what you want.
The outset off costs you will need to cater for include:
- CluedIn Licenses
- Cloud or Hosting Costs
- Implementation costs (through a partner or building in-house)
So you have chosen an implementation partner or you have upskilled internally and you would like to know how long this will take. Reach out to get access to our implementation guide which will take you through the hours involved in a typical project.
We will typically see that CluedIn is running in your environment within a week, and ingesting data in week 2. Depending upon the amount of data you are ingesting, you could see value within days, for bigger datasets you might be waiting a bit more. This does not stop you from starting the other parts of CluedIn so when your data is finished, it is immediately ready to go.
The biggest part of your investment will typically happen in the first year and then year 2 and 3 will mainly be focussed on costs for licenses and maintenance.
As you start to build more internal use cases from your data, you might find that you need more CPU cores as more data is being processed and more data is being streamed to different locations.
No. You will only need to pay for licences for your production environment. This means that all your development, continuious integration and build environments and staging are all included in your license purchase.