Glossary
The words used in Cortex and in this documentation, explained in plain language, with the Dutch word where the Dutch interface uses another one.
The words below appear in Cortex and in this documentation. Where the Dutch interface uses another word, it is given in brackets. Each entry says in one or two sentences what the word means and where to read more.
Who can do this
Everyone. The glossary only explains words. Some terms belong to what builders (Studio) or admins (Control) do; they are marked as such.
How the words fit together
A system where data lives, connected by IT. Datasets are what it offers.
Tables, relationships, figures and rules. Figures can be certified.
A dashboard, app or workflow. Ask is the front door.
Pin, subscribe, handle tasks. Your access decides what you see.
A sentence in Cortex words: "IT connected the ERP as a source; a builder defined the figure Revenue in the Sales model and the owner certified it; the finance dashboard shows it, and Lotte pinned it to Home."
Products
Cortex Hub. The place where everyone works: Home, Ask, experiences, tasks and notifications. See Find your way around.
Studio. The Hub's section for builders. You see it only with a Studio seat. Here you build dashboards, apps, workflows and models. See Start something and follow your requests.
Cortex Control. The place where IT administers Cortex: people, approvals, policy, budgets, data sources, the licence, the AI engine, the audit log and health. See Overview, attention list and health.
Home. The first page in the Hub: ask a question, your pinned values, recent questions and what you opened recently. See Home.
Factory. An area of the Hub for factory data such as lines, OEE and energy. It appears when your organisation uses the Factory pack.
Building blocks
Experience (ervaring). Something people open and use: a dashboard, an app or a workflow. See Experiences.
Dashboard. An experience that shows key figures in tiles and charts.
Tile. One block on a dashboard: a figure, a chart or a text. A tile asks the model for its numbers when you open the dashboard. See Tiles, filters and pages.
App. An experience for working with records, built for your organisation. See Apps and workflows.
Workflow. An experience that runs a process, with steps, tasks for people and checks. See Workflows: build the steps.
Run (uitvoering). One go through a workflow, from its start to its end. A run can wait for a person. See Workflow runs.
Trigger. What starts a workflow: someone, a schedule, a new record, an app event, a webhook or a certified figure crossing a line.
Workspace (werkruimte). A group of related experiences with its own access setting, accent colour and logo. See Workspaces.
Draft (concept). A version that only its builder sees. It goes live when it is published.
Publish (publiceren). Make a draft live for the people it is shared with. A model, a dashboard, an app and a workflow are published separately. Depending on your organisation's policy a publish may need approval.
Version. A saved state of a published model, dashboard or workflow. An earlier version can be brought back.
Ready-made. A badge on ready-made experiences that come with a pack. They cannot be edited, only copied.
Data and trust
Source (bron). A system or dataset where data comes from, connected by IT. Cortex reads it and does not replace it. See Data sources.
Dataset. A named set of data that a source offers, such as the invoice lines of the ERP. IT adds datasets and decides who may read them. See Datasets and grants.
Grant (toegang). The permission for an app or model to read a dataset. A builder asks for it, and IT approves it per app and per environment.
Pack. A ready-made set, managed by the platform, for a domain or a business system, such as a connection to an ERP or content for factories. See Connector packs.
Model (model; also semantic model). The agreed meaning of your data: tables, relationships, figures and rules. See Semantic models.
Figure (kengetal). A named number defined in a model, such as revenue. Technical conversations may call it a measure. "Also called" lists other names for it that Ask recognises.
Certified (gecertificeerd). A figure that has been compared with the source and confirmed by the model's owner, and that is checked again every night. See Certified figures and nightly checks.
Reference check. The comparison that happens when an owner certifies a figure: the model's answer against an independent total from the source.
Nightly check. What Cortex does every night on every published model: data still arriving, tables sound, certified figures still matching. See Model checks.
Badge. The sign next to a figure that says it is certified. It goes away by itself when the figure stops matching and comes back when it matches again.
Verified question. An example question with a known right answer, stored with a model. Ask can answer a matching question without an AI call. See Ask and AI.
Row-level security (rijbeveiliging). Rules that decide which rows of data a person sees. See Access and security.
Audience (doelgroep). A group of people that a rule or a model refers to, for example "plant managers".
Document. A manual, procedure or other file attached to a model. Ask can answer from documents and quote them. See Documents and sources.
OCR. Reading the text of a scanned document. Cortex shows how sure the reading was.
Data freshness. The pill in the Hub that tells you whether the data behind your dashboards is up to date.
Asking and following
Ask. The AI front door of Cortex: you ask a question and get an answer from governed data. See Ask and AI and Ask Cortex.
How I got this (Zo kwam ik hierop). The line under an answer that lists the figures, filters, period and data date behind it.
Pin (vastzetten). Put a value on your Home, or a dashboard, app or workflow in your menu, so you see it without searching. See Pin a value, pin a dashboard, subscribe.
Subscription (abonnement). A digest or an alert that you asked Cortex to send you. See Subscriptions.
Digest (samenvatting). A short summary of key figures that you get on a schedule after subscribing to a dashboard.
Alert (waarschuwing). A message when a figure crosses a value you set.
Report access (rapportagetoegang). The narrow permission you give Cortex so it can send a digest or alert on data that only shows you part of the rows. It ends after 90 days and can be withdrawn.
Inbox. The place for what waits for you (tasks, approvals) and what you sent, such as access requests and feedback. Builders also see their requests and the roadmap. See The Inbox.
Task (taak). A step of a workflow that waits for a person, for example an approval. Tasks are in the Inbox.
Notifications (meldingen). The bell: your digests, alerts and other messages. Tasks that wait for your decision are in the Inbox. See The notification bell.
Discover (ontdekken). A shelf at the bottom of Experiences with dashboards that exist but are not shared with you yet. You see what it is and who owns it, and can ask for access.
People and access
Seat (plek). A licence place. A Studio seat gives a person access to Studio. See Licence and seats.
Builder (bouwer). A person with a Studio seat.
Admin (beheerder). A person who administers Cortex Control.
Owner (eigenaar). The person who looks after an experience or a model and decides who can use it. Only an owner of a model can certify its figures.
Request. A builder's or an app's ask to an admin, for example a new app, access to a dataset or a publish. It waits in Approvals. See Approvals.
Entra. Your organisation's Microsoft sign-in. Cortex uses it to know who you are.
Audit log (auditlog). The record of who did what and when, readable by admins. See Audit log.
AI and cost
AI engine. The language model your organisation chose and that IT set up in Control. See AI engine and models.
Tier. One of the three levels of AI model that IT sets: Small, Medium and Large. Cheap models do the easy work and strong models are used where they pay off.
EU only. A switch in Control that lets IT choose only engines that run in the EU.
Budget. The monthly amount a builder, or your organisation, may spend on AI. See Cost and limits.
Policy. The rules IT sets for your organisation: limits per owner, outside data, AI steps, production approvals and how long run data is kept. See Builder permissions and policy.
Channel. A place other than the Hub where Cortex answers: AI apps such as Claude and ChatGPT, and Cortex Hub inside Microsoft Teams. See Channels: AI apps and Microsoft Teams.