How to add company terms and abbreviations to FocusGPT in DataFocus OT Flash through My Knowledge Base, share them system-wide through Admin > Knowledge, and check how a question was parsed.
OT Flash lets you teach Data Search your company's vocabulary: synonyms for column names and values, custom keywords, custom locations and a custom date such as a fiscal year. This tutorial shows where each setting lives and how to check it.
Two reports disagree on one metric because each re-implements it and makes five unlabeled choices: filters, date column, grain, join path and source system. A worked revenue reconciliation, a triage order and what an executable, owned definition requires.
Public enterprise benchmarks show raw text-to-SQL still fails on most real warehouse tasks. The gap is mostly missing business definitions. Here is how definition-bound queries that show their SQL compare, and when plain text-to-SQL is fine.
How DataFocus OT Flash keeps imported tables current with scheduled import tasks instead of an ETL engine: connect a read-only source, pick tables, set a schedule, and watch health in System Manager.
OT Flash's r57 manual lists 26 external source types, from MySQL and Oracle to Hive and Iceberg. The secure path is a dedicated read-only account, a tested connection, and a scheduled import into OT Flash's own store. Here is each step, and what the manual leaves to you.
DataFocus OT is free to self-host, but the model service is a separate bill. A worksheet for sizing it: which actions call the model, how many tokens each uses, and how to revisit the estimate as prices fall.
OT Flash names no built-in model. An administrator configures the LLM service, and that choice decides both what data leaves your network and what the model bill looks like. A walk through the admin screens, the egress decision and a monthly review habit.
The seven decisions DataFocus asks you to settle before self-hosting OT Flash, each with an owner, the artifact it produces, the mechanism behind it, and a first-hour verification sequence taken from the r57 manual.
DataFocus documents the same ontology concepts in both editions and lists definitions, mappings and tests as reusable. It does not document an in-place Flash-to-Heavy upgrade, so plan the move as a rebuild with reused assets and ask support the open questions.
DataFocus publishes a reference node and a license policy but no sizing table. This checklist turns those documented facts into measurable signals you collect yourself before choosing Flash or Heavy.
Flash runs the ontology on one Apache Doris engine; Heavy runs it over Trino, Hive, Iceberg and Hadoop with DataSpring ETL and AutoML. Three questions, a worked example and the licence facts that decide between them.
A BI copilot answers well inside one tool's semantic model. When a question crosses CRM, ERP and contracts, or must give the same figure to dashboards and external agents with the SQL attached, an ontology layer is the better home.
A checklist for choosing one business question for a first OT Flash pilot: data, policy documents and a named owner, written acceptance criteria, synthetic data first, and a go or no-go rule.
From first login to an agent answer you can audit: bring in three tables, create an ontology, bind tables and definition documents, then check View processing details against Data Explore before inviting colleagues.
For a small company with no data platform, OT Flash's one-engine design and one-ontology-per-question approach is a reasonable starting point, provided you budget for servers, model calls and operations.
A step-by-step walk from a spreadsheet on your desktop to a searchable OT Flash table bound to an ontology, using only the Tables, Ontology and Data Search screens.
A business ontology models one business area's objects, relationships, rules, actions and permissions in one model people and agents share. Agents need it to close three gaps a schema cannot: context, boundaries and an approval path. Plus a rule for when not to build one.