> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cognite terminology

> A glossary of approved, pending, and discouraged terms for Cognite documentation, with usage guidance and examples.

## A

<AccordionGroup>
  <Accordion title="agent">
    An app that use generative AI (genAI) language models to gather and process real-time industrial data stored in Cognite Data Fusion's knowledge graph. Each agent interacts with humans and its environment and uses the data to meet predetermined goals.
  </Accordion>

  <Accordion title="alert">
    An alert is a message that informs users about threshold breaches that may require attention or action. Depending on user settings, an alert can also create a notification email.
  </Accordion>

  <Accordion title="alpha">
    Describes the release status of the functionality. It indicates an early testing phase, and it will likely change or be removed without prior notice

    See beta, generally available.
  </Accordion>

  <Accordion title="Amazon Cognito">
    Amazon's cloud-based identity and access management (IAM) solution. This term can be abbreviated as Cognito if needed.
  </Accordion>

  <Accordion title="annotation">
    A combination of labels and relationship resources that are added to visual data and are stored with files, as opposed to being stored as text strings next to files. Annotations have defined, validated data models. Annotation types are: shapes and keypoint collections. Annotations aren't resource types.
  </Accordion>

  <Accordion title="asset">
    Systems that support industrial functions or processes. Assets are often organized in hierarchies.
  </Accordion>

  <Accordion title="asset tag">
    See asset.
  </Accordion>
</AccordionGroup>

## B

<AccordionGroup>
  <Accordion title="beta">
    Describes the release status of the functionality. It indicates that a product or functionality is in a mature testing phase, but is still subject to change or retirement.

    See alpha, general available.
  </Accordion>
</AccordionGroup>

## C

<AccordionGroup>
  <Accordion title="Canvas">
    Cognite's visual collaboration tool. When talking about a generic canvas, not the feature, use lower case.
  </Accordion>

  <Accordion title="capability">
    Defines what access permissions users have to work with different data objects in Cognite Data Fusion, for example, if they can read a time series.
  </Accordion>

  <Accordion title="CDF application">
    In technical product documentation, use CDF or CDF application. In any other kind of documentation, use Cognite Data Fusion or Cognite Data Fusion application.
  </Accordion>

  <Accordion title="CDF Clean">
    Rewrite to avoid this term.

    Do not use.
  </Accordion>

  <Accordion title="CDF project">
    An instance of a CDF environment. The data in a project is completely isolated from the data in other projects.
  </Accordion>

  <Accordion title="CDF project admin">
    A user who can create new groups and add or remove capabilities and scopes from groups in a CDF project. A CDF project has to be owned by an organization.
  </Accordion>

  <Accordion title="CDF RAW">
    CDF's staging area for ingesting data. Spell out the full name the first time the name appears in an article.

    Use the short form RAW for secondary mentions. Use Raw (initial cap) for the CDF API endpoint.
  </Accordion>

  <Accordion title="Charts">
    Cognite's tool for visualizing, exploring, trending, and analyzing time series data. When talking about a generic chart, not the feature, use lowercase.
  </Accordion>

  <Accordion title="checklist">
    In InField, a list of tasks that are either pre-defined in a template or generated from a work order.

    See template, work order, task.
  </Accordion>

  <Accordion title="Cognite Atlas">
    Use in a general sense to describe all of Cognite's AI-powered agents. Cognite Atlas AI isn't a technology, feature, product, or service, so don't say things like Powered by Cognite Atlas AI.
  </Accordion>

  <Accordion title="Cognite Data Fusion">
    The official name of our flagship SaaS platform product. It's available through several interfaces, including GUIs, APIs, and SDKs.

    Spell out the full name Cognite Data Fusion the first time the name appears in an article. Use the CDF abbreviation for secondary mentions in the product documentation. Avoid using CDF in the product UI, and always spell out the full name, Cognite Data Fusion, in sales and marketing content.
  </Accordion>

  <Accordion title="Cognite data model">
    An umbrella term for data models created by Cognite and included in the CDF subscription.
  </Accordion>

  <Accordion title="Cognite Data Source for Grafana">
    This is the full name of our connector to use a Cognite Data Fusion (CDF) project as a data source in Grafana. Spell out the full name the first time the name appears in an article.

    Use the short form Grafana Data Source for secondary mentions.
  </Accordion>

  <Accordion title="Cognite Functions">
    This is the full name of our service to schedule, call, and monitor Python functions hosted in our cloud. Spell out the full name, Cognite Functions, the first time the name appears in an article.

    Use the short-form Functions for secondary mentions.
  </Accordion>

  <Accordion title="Cognite InField">
    This is the full name of our field operations (APM) solution. Spell out the full name Cognite InField the first time the name appears in an article.

    Use the short form InField for secondary mentions.
  </Accordion>

  <Accordion title="Cognite JavaScript Software Development Kit (SDK)">
    This is the full name of our SDK for JavaScript developers who build front-end applications. Spell out the full name the first time the name appears in an article.

    Use the short-form JavaScript SDK for secondary mentions.
  </Accordion>

  <Accordion title="Cognite Maintain">
    This is the full name of our collaborative planning (APM) solution. Spell out the full name Cognite Maintain the first time the name appears in an article.

    Use the short form Maintain for secondary mentions.
  </Accordion>

  <Accordion title="Cognite PostgreSQL gateway">
    This is the full name of the service that provides a PostgreSQL interface to CDF. Spell out the full name the first time the name appears in an article.

    Use the short-form PostgreSQL gateway for secondary mentions.
  </Accordion>

  <Accordion title="Cognite Power BI connector">
    This is the full name of our connector to use a Cognite Data Fusion (CDF) project as a data source in Power BI. Spell out the full name the first time the name appears in an article.

    Use the short form Power BI connector for secondary mentions.
  </Accordion>

  <Accordion title="Cognite Python Software Development Kit (SDK)">
    This is the full name of our SDK for provisioning, managing, and using CDF resources from Python application code. Spell out the full name the first time the name appears in an article.

    Use the short-form Python SDK for secondary mentions.
  </Accordion>

  <Accordion title="Cognite Toolkit">
    A command-line interface (cdf-tk) for managing the configuration of Cognite Data Fusion projects. In the documentation, use the full name, "Cognite Toolkit".

    Don't use "Toolkit". Always use the definite article (the) before the name, as in "the Cognite Toolkit".
  </Accordion>

  <Accordion title="connector">
    A service that tranfers data between an external system and CDF.

    Use the full name, such as Cognite Fabric connector, at first mention, then use only Fabric connector. Do not capitalize.
  </Accordion>

  <Accordion title="constraint">
    Restricts the values that can be stored in a property or container. Constraints ensure that the data has integrity.
  </Accordion>

  <Accordion title="container">
    The physical storage for properties for instances (nodes and edges ).

    They're defined within a space and hold a set of properties that logically belong together.
  </Accordion>

  <Accordion title="core data model">
    The Cognite data model containing standardized, generic building blocks for industrial data.

    See Cognite data model, data model, custom data model.
  </Accordion>

  <Accordion title="custom data model">
    A data model extended from either the core data model or an industry data model. It can also be created from the ground up by Cognite, partners, or customers.

    See Cognite data model, data model, core data model.
  </Accordion>
</AccordionGroup>

## D

<AccordionGroup>
  <Accordion title="Data catalog">
    A collection of data sets that serves as a central and secure repository that can be searched, explored, and managed in CDF. When talking about a generic data catalog, not the feature in CDF, use lowercase.
  </Accordion>

  <Accordion title="data contract">
    A formal agreement that defines expectations for data, including SLAs, schema, ownership, quality rules, and usage terms. Both domains and data products have contracts.

    JSON/YAML specification attached to domains and products. Based on Open Data Contract Standard (ODCS). Domain contracts define internal structure, medallion stages, and lineage. Product contracts define external interface, SLAs, and consumer terms. May be referred to as "contract" when context is clear.

    See data product, data domain.
  </Accordion>

  <Accordion title="data contextualization">
    The process of establishing relationships between data elements.
  </Accordion>

  <Accordion title="Data explorer">
    This is the name of one of the search and validation functionalities in Cognite Data Fusion, targeted to data managers, data stewards, and data scientists to query, find, and validate data.

    See search.
  </Accordion>

  <Accordion title="data flow">
    Use data workflow
  </Accordion>

  <Accordion title="data integration">
    The process of transferring data between external systems and CDF.

    Do not capitalize.

    See Extractors, Connectors, and Data pipelines.
  </Accordion>

  <Accordion title="data model">
    An abstract representation of real-world entities. Data models organize data elements and their properties and standardize how they relate.

    In the data modeling service (DMS), a data model is a collection of views that belong together.

    See Cognite data model, custom data model, core data model.
  </Accordion>

  <Accordion title="data pipelines">
    The combined process of data integration, data transformation, and data contextualization. Do not capitalize.
  </Accordion>

  <Accordion title="data product">
    A curated self-contained unit of data designed to serve specific consumer needs. Data products are built from domain gold layers and governed by data contracts.

    Non-materialized views from one or more domain gold layers with metadata, SLAs, and ownership. May be referred to as "product" when context is clear. Types: read-only data product, write-back data product.

    See data domain, data contract, gold layer.
  </Accordion>

  <Accordion title="data set">
    A container for data objects and metadata about the data it contains. Data sets group and track data by its source.
  </Accordion>

  <Accordion title="data transformation">
    The process of shaping data to fit a CDF data model.  Do not capitalize.

    See also data pipelines.
  </Accordion>

  <Accordion title="data workflow">
    A service to order and schedule CDF processes.
  </Accordion>

  <Accordion title="deprecated">
    Use to indicate that we no longer actively develop the feature or functionality and will remove it in a future release. Do not use deprecated in the user interface.

    See alpha, beta, generally available.
  </Accordion>

  <Accordion title="direct relation">
    A property holding a reference to a node. Similar to a foreign key in relational models.
  </Accordion>

  <Accordion title="discipline">
    In InField, a group of people combined based on the skills they have to perform a certain type of work.
  </Accordion>

  <Accordion title="documents">
    A specific term for text files.
  </Accordion>
</AccordionGroup>

## E

<AccordionGroup>
  <Accordion title="Early Adopter group">
    Describes a feature or functionality that are only available to customers via the Early Adopter group. To become part of the group, users need to sign up on the Cognite Hub.
  </Accordion>

  <Accordion title="edge">
    Edges denote relationships between nodes in a knowledge graph.
  </Accordion>

  <Accordion title="event">
    An activity that happens over a period of time. Events have a start and an end time.
  </Accordion>

  <Accordion title="execute">
    Use run instead.
  </Accordion>

  <Accordion title="extractor">
    A service that transfers data from an external system into CDF.

    Use the full name, such as Cognite PI extractor, at first mention, then use only PI extractor. Do not capitalize.

    See connectors, data pipelines.
  </Accordion>
</AccordionGroup>

## F

<AccordionGroup>
  <Accordion title="file">
    A generic term for any data stored on a computer, such as spreadsheets, media, and executables.

    Use File when you're referring to a list of mixed file types. Otherwise, use a specific term.

    See Documents.
  </Accordion>

  <Accordion title="Functions">
    This is the short name of our service to schedule, call, and monitor Python functions hosted in our cloud.

    Spell out the full name, Cognite Functions, the first time it appears in an article, and separate it from Azure Functions and  AWS Lambdas. When talking about a generic function, not the feature, use lowercase.
  </Accordion>

  <Accordion title="Fusion">
    Use Cognite Data Fusion.

    See Cognite Data Fusion.
  </Accordion>
</AccordionGroup>

## G

<AccordionGroup>
  <Accordion title="GA">
    See [generally available (GA)](#generally-available-ga).
  </Accordion>

  <Accordion title="gateway">
    Use extractor or connector.

    See PostgresSQL gateway.
  </Accordion>

  <Accordion title="generally available (GA)">
    The feature or functionality is fully functional and ready for production use.

    See alpha, beta.
  </Accordion>

  <Accordion title="Grafana Data Source">
    This is the short name of our connector to use a Cognite Data Fusion (CDF) project as a data source in Grafana.

    Use the short form Grafana Data Source for secondary mentions.
  </Accordion>
</AccordionGroup>

## I

<AccordionGroup>
  <Accordion title="index">
    Speeds up data access and support constraints such as uniqueness and efficient cursoring with custom sorts. An index belongs to a container and is not a flag on a property.
  </Accordion>

  <Accordion title="InDSL">
    This is the short name of Cognite's collection of data science algorithms and models. Spell out the full name, Industrial Data Science Library, the first time the name appears in an article.

    Use the short form InDSL for secondary mentions.
  </Accordion>

  <Accordion title="Industrial Canvas">
    The full name of Cognite's visual collaboration tool

    Don't use in technical product documentation or user interfaces.
  </Accordion>

  <Accordion title="Industrial Data Science Library">
    This is the full name of Cognite's collection of data science algorithms and models.

    Spell out the full name the first time the name appears in an article. Use the short form InDSL for secondary mentions
  </Accordion>

  <Accordion title="industrial knowledge graph">
    Contains all the containers, properties, nodes, and edges that implement the information model to be represented in Cognite Data Fusion. In CDF, the industrial knowledge graph is implemented as a property graph.
  </Accordion>

  <Accordion title="industry data model">
    A Cognite industry-specific data model extended from the core data model.
  </Accordion>

  <Accordion title="InField">
    This is the short name for our field operations (APM) solution.

    Use the short form InField for secondary mentions.
  </Accordion>

  <Accordion title="instance">
    An umbrella term for nodes and edges.
  </Accordion>
</AccordionGroup>

## J

<AccordionGroup>
  <Accordion title="JavaScript SDK">
    This is the short name of our SDK for JavaScript developers to build front-end applications.

    Spell out the full name, Cognite JavaScript Software Development Kit (SDK), the first time the name appears in an article. Use the short-form JavaScript SDK for secondary mentions.
  </Accordion>
</AccordionGroup>

## L

<AccordionGroup>
  <Accordion title="location">
    A digital representation of a physical area or a grouping of physical objects and related data, such as a platform or a factory.

    See asset.
  </Accordion>
</AccordionGroup>

## M

<AccordionGroup>
  <Accordion title="Maintain">
    This is the short name of our collaborative planning (APM) solution.

    Spell out the full name Cognite Maintain, the first time the name appears in an article. Use the short form Maintain for secondary mentions.
  </Accordion>

  <Accordion title="Microsoft Entra ID">
    Microsoft's cloud-based identity and access management (IAM) solution. Formerly Azure Active Directory or AAD.

    Can be abbreviated as ME-ID if needed.
  </Accordion>
</AccordionGroup>

## N

<AccordionGroup>
  <Accordion title="node">
    Nodes are the basic building blocks of knowledge graphs. They can represent any real-world object, for example, pumps.
  </Accordion>

  <Accordion title="notification">
    Notifications keep you informed about things that need your attention.
  </Accordion>
</AccordionGroup>

## O

<AccordionGroup>
  <Accordion title="observation">
    Information to collect on malfunctioning equipment for further evaluation.
  </Accordion>

  <Accordion title="operation">
    In InField, an individual step in a work order that comes from a work management system, such as SAP. An operation becomes a task when a checklist is created.

    See task.
  </Accordion>

  <Accordion title="organization">
    A collection of CDF projects. Organizations are linked to one customer Identity Provider (IdP).
  </Accordion>
</AccordionGroup>

## P

<AccordionGroup>
  <Accordion title="PostgreSQL gateway">
    This is the short name of the service that provides a PostgreSQL interface to CDF.

    Spell out the full name, Cognite PostgreSQL gateway, the first time the name appears in an article. Use the short-form PostgreSQL gateway for secondary mentions.
  </Accordion>

  <Accordion title="Power BI connector">
    This is the short name of our connector to use a Cognite Data Fusion (CDF) project as a data source in Power BI.

    Spell out the full name, Cognite Power BI connector, the first time the name appears in an article. Use the short form Power BI connector for secondary mentions.
  </Accordion>

  <Accordion title="preview">
    Use alpha or beta to indicate release status. Features in beta may be referred to as "preview" in the user interface or in marketing materials

    but they follow the support and lifecycle guidelines of the beta status."

    See general.
  </Accordion>

  <Accordion title="principal">
    An umbrella term for user accounts and service accounts.
  </Accordion>

  <Accordion title="product">
    Cognite Data Fusion

    See tool, solution.
  </Accordion>

  <Accordion title="property">
    Provides additional context or information to nodes and edges in a knowledge graph. Properties can include types, such as Pump or flows-to, but they can also include other attributes describing the nodes and edges.
  </Accordion>

  <Accordion title="property graph">
    Represents a well-defined structure consisting of nodes and edges that can be associated with properties
  </Accordion>

  <Accordion title="Python SDK">
    This is the short name of our SDK for provisioning, managing, and using CDF resources from Python application code. Spell out the full name, Cognite Python Software Development Kit (SDK), the first time the name appears in an article.

    Use the short-form Python SDK for secondary mentions.
  </Accordion>
</AccordionGroup>

## R

<AccordionGroup>
  <Accordion title="RAW">
    The short name for the staging area for ingesting data.

    Spell out the full name, CDF RAW, the first time the name appears in an article. Use Raw (initial cap) for the CDF API endpoint.

    See CDF RAW.
  </Accordion>

  <Accordion title="release state">
    Describe the status of the feature or functionality: - [alpha](#alpha) - early testing phase, and it will likely change or be removed without prior notice - [beta](#beta) - mature testing phase, but is still subject to change or retirement.

    * [generally available (GA)](#generally-available-ga) - the feature or functionality is fully functional and ready for production use. - [deprecated](#deprecated) - no longer actively developed and will be removed in a future release. - [retired](#retired) - no longer available for use

      See alpha, beta, generally available.
  </Accordion>

  <Accordion title="retired">
    Use to describe the status of the feature or functionality after it has been removed. It's no longer available for use.
  </Accordion>
</AccordionGroup>

## S

<AccordionGroup>
  <Accordion title="schema">
    In the data modeling service (DMS),  schemas consist of three key elements: - Containers: define physical storage that contains properties. - Views: establish logical schemas that map properties. Data models: serve as collections of views
  </Accordion>

  <Accordion title="search">
    Cognite's engine for finding and discovering industrial data. Search functionality includes AI,  filtering, and a visual and interactive Digital Twin in 3D. Search is targeted to the needs of industrial data subject matter experts, like process, production, and reliability engineers.

    See Data explorer.
  </Accordion>

  <Accordion title="service account">
    A service account is associated with an application, service, or compute workload that wants to interact with CDF, such as an extractor or Cognite Functions, rather than a person.
  </Accordion>

  <Accordion title="sign in">
    Use "sign in" to describe starting a session on a computer, a device, a network, an app, or anywhere a username and password are required. Use "sign out" to refer to ending a session
  </Accordion>

  <Accordion title="solution data model">
    A custom data model developed for specific solutions and apps by Cognite, partners, or customers
  </Accordion>

  <Accordion title="space">
    Can contain both schemas and instances to organize a graph It functions as a namespace and serves as a scope for governance and access control.
  </Accordion>

  <Accordion title="staged data">
    The data collected from a source system that hasn't been processed for use in CDF and doesn't adhere to the CDF data model.

    See RAW.
  </Accordion>

  <Accordion title="sunset">
    Use retired instead.
  </Accordion>

  <Accordion title="system schema">
    In the data modeling service (DMS), system schemas are defined in globally available spaces. They are prefixed with cdf\_ and contain containers, views, and data models available out of the box in a CDF project.
  </Accordion>
</AccordionGroup>

## T

<AccordionGroup>
  <Accordion title="tag">
    An identification marker attached to an asset. Only some customers use this term.

    See asset.
  </Accordion>

  <Accordion title="task">
    In InField, an individual step in a template and a checklist.

    See template, checklist, operation.
  </Accordion>

  <Accordion title="template">
    In InField, a list of tasks that can be used to generate multiple, identical checklists.

    See checklist.
  </Accordion>

  <Accordion title="tenant">
    Our customers are Cognite tenants. Their CDF projects run in a multi-tenant cluster or in a dedicated cluster.

    3rd-party companies may also refer to their customers as ""tenants"", for example Microsoft Azure.
  </Accordion>

  <Accordion title="time series">
    A series of data points in time order. Examples of a time series are the temperature of a water pump asset, the monthly precipitation in a location, and the daily average number of manufacturing defects.

    It's always spelled in two words, except when it's the name of a function or similar in an API or SDK. Time series is a count noun and can be singular or plural without the word itself changing.
  </Accordion>

  <Accordion title="tool">
    Features within CDF, such as  Charts and Canvas.

    See product.
  </Accordion>

  <Accordion title="transform">
    Used to describe moving data from a source system, between data models, or from CDF RAW into CDF data models or resource types.

    When talking about a generic transformation, not the feature in Cognite Data Fusion, use lowercase.
  </Accordion>

  <Accordion title="Transformations">
    Cognite's tool to transform data in the staging area (RAW) into a data model.
  </Accordion>
</AccordionGroup>

## U

<AccordionGroup>
  <Accordion title="unit catalog">
    Defines the available units in a data model.
  </Accordion>

  <Accordion title="user account">
    A user account is associated with a person who wants to interact with CDF.
  </Accordion>
</AccordionGroup>

## V

<AccordionGroup>
  <Accordion title="view">
    Logical schemas to consume and populate a graph.
  </Accordion>
</AccordionGroup>

## W

<AccordionGroup>
  <Accordion title="work order">
    In InField, a list of operations that comes from a work management system, such as SAP. A checklist can be created from a work order or its individual operations.

    See checklist.
  </Accordion>

  <Accordion title="workflow orchestration">
    Use data workflow
  </Accordion>

  <Accordion title="workspace">
    A collection of tools and resources that enable a user to accomplish a set of related tasks, such as field operations.
  </Accordion>
</AccordionGroup>