Skip to main content

Collaborative Intelligence Engine

The Collaborative Intelligence Engine is an extension for the Cinchy platform that converts enriched customer data into insights. It empowers you to create impossible insights by harnessing AI on connected data—without requiring traditional system integration. Built on Cinchy’s Data Collaboration Platform, the CI Engine reuses liberated and federated data to create insights enriched by the context of multiple systems, and from real people.

Imagine the CI Engine as your Intelligence Kitchen, where you—the chef—combine ingredients (data), follow recipes (configurations), and use appliances (AI models) to craft collaborative insights. What sets the CI Engine apart is its unique ability to turn the output of one insight into a new ingredient for another, enabling a collaboration of insights. This elevates the concept beyond mere data collaboration, allowing insights to grow in value through their connections.

The general workflow is:

  1. Create a recipe in the [CI Recipes] table. This serves as a prompt that will bring together the "ingredients" (i.e. data), AI models, instructions, safety filters, how the insights will be delivered, etc.
  2. The CI Engine will return an enriched response in the [CI Insights] table.
  3. The insights can then be reused as "ingredients" for future recipes.

Access Controls​

Like everything in Cinchy, the CI Engine features enhanced governance and integrated access controls.

QUESTIONS:

  • Best practices for assigning group roles?
  • Who can see the recipes table, insights table, etc.

Groups​

CI Engine users should be assigned to one of the following three groups, based on their business needs:

  • CI Engine Admins: This group gives edit access to all of the objects in the package.
  • CI Engine Builders: This group gives design access to the objects, as well as edit access to specific columns in the package tables.
  • CI Engine Users: This group gives users access to create recipes, as well as edit the recipes they have access to.

Token Authorization​

Further Reading​

  • Deploying the CI Engine
  • Configuring the CI Engine