Data Orchesterby Amtiri
Sign in Get Data Orchester
AI assistant

An AI assistant inside your configuration

Three chats in the Site read your configuration, the documents you attach and Data Orchester's documentation. Two of them propose changes you review on a card; the third explains, diagnoses and suggests an action plan. Nothing changes until you apply it, and nothing is saved until you press Save.

Read the guide See the allowances Download Data Orchester
Three assistants

One for each place you work

Each reads the whole configuration, not only the screen it sits on: variables, modules, peers, schemas, dashboards and panels, with the unsaved edits of your open Program tab.

The Assistant tab

General

Ask about your plant, diagnose a problem and get an action plan.

Ask it

  • What does this plant do?
  • Why has pump 2 stopped, and how do I get it back?
  • What would FIT_501 read if the PLC sent 20000?

It can

  • Explain the program, the dashboards and the engine's state, from the whole configuration
  • Diagnose from module health and messages, values and the console, with live values on
  • Answer with an action plan: checks before changes, each step with its impact and how to verify it
  • Hand a configuration change to the Program or dashboard chat, as a request you review there

Never: it changes nothing. Its buttons only open screens or hand a request to an editor's chat.

Beside the Program editor

Programming

Create, fix and review modules, variables and formulas, from your requests and documents.

Ask it

  • Create the Modbus master for this PLC from the attached register list
  • Why is FIT_501_ALARM never true?
  • Review this program and fix its load warnings

It can

  • Read the register lists, manuals and drawings you attach: PDF, images, spreadsheets, Word documents and text
  • Validate its draft, and simulate new and changed formulas on test values in a sandbox that touches nothing
  • Propose each change on a card, field by field, with its checks, sources and assumptions
  • Look things up in Data Orchester's documentation, and on the public web when you allow it

Never: it never saves, starts or stops the engine, and peers and schemas are read-only to it.

Beside the dashboard editor

Dashboard

Design and fix views from drawings and requests.

Ask it

  • Draw an overview of the dosing station from this P&ID
  • Make the alarm frame red when any pump fails
  • Align the pump symbols

It can

  • Read the pages of a P&ID and the screenshots of an old HMI as pictures
  • Bind gauges and fields to variables found anywhere in the configuration
  • Validate its draft before the card shows it, and mark any change that writes to the plant
  • Change only the dashboard open in its editor, as one step that Undo takes back

Never: it never saves. The view is yours to review, save and commission.

How a change happens

It proposes; you decide

The Program and dashboard chats never edit by themselves. Each change comes to you as a card, and only your Apply puts it into the editor.

  1. You ask In the chat beside the editor, with the documents it needs attached.
  2. It reads The configuration, your attachments and the documentation, with a line in the chat for each tool it uses.
  3. It checks It validates the whole change and, on the Program screen, simulates new and changed formulas on test values.
  4. It proposes A card shows every change field by field, with the checks it ran, the sources it used and what it assumed.
  5. You apply Apply, Apply and continue, or Discard. If a record the card was built on has changed since, the card is refused and nothing is applied.
  6. You save Undo takes the whole change back at once, and nothing reaches the disk until you press Save.
Safety

The plant stays in your hands

It never saves

Nothing it proposes changes your configuration until you apply its card, and nothing reaches the disk until you press Save, through the same checks as a change made by hand.

It never touches the plant

It never starts or stops the engine and never writes a value to the plant. A card that adds or alters something that writes to the plant says so.

Documents are data

What a document says is never an instruction to the assistant: when a page tells it to ignore its rules, it says in one line that it did not follow it, and goes on.

Nothing is kept

A conversation is never stored, and its attachments are dropped when it ends. Amtiri's Portal keeps the tokens and the cost of each call, never what was said.

What it reads

What it needs, never your secrets

The assistant reads what the question needs, and a page of an attachment leaves the instance only when the assistant reads it or looks at it.

  • The configuration Variables, modules, peers, schemas, dashboards and panels, and the instance's licence and engine state.
  • Your attachments PDF, images, Excel and Word files, CSV, text, Markdown, JSON and SVG: up to 10 per conversation, held in memory and never written to the instance's disk.
  • The documentation Data Orchester's documentation, always, looked up through Amtiri's Portal.
  • The web PLC manuals, protocol specifications and standards, only when Web search is on.
  • Live values Current values, module health and messages and recent console errors, only when Live values is on.

Never sent: secrets reach the assistant as «redacted» - a peer's secret, passwords and any credential written into a text - and users, licence files and logged history never leave the instance.

How it connects

One route, through Amtiri's Portal

The plant never talks to an AI provider. Every request goes through Amtiri's Portal, which holds the key and the limits.

  • Your instance Talks only to dataorchester.com, over HTTPS and signed with its own install key, as it does for its licence. It never holds an AI provider's key.
  • Amtiri's Portal Checks the licence and the organization's allowance, passes the request on, and keeps the tokens and the cost of each call, never what was said.
  • The AI provider Answers each request. Requests go only to providers that do not collect the data they are sent.
  • Off until you turn it on Per installation, by a user with the Configuration role, after a disclosure of what is sent and to whom. Web search and live values are two more switches, off until ticked.
  • No licence or no Portal, no assistant An instance without a valid licence, or one that cannot reach the Portal, has no assistant, nor has an air-gapped installation on an offline licence key.

What is sent, and what never is → How to turn it on → When the assistant is off →

Availability

Included with these editions

Each organization has a monthly AI allowance in US dollars, set by the edition of its licence and shared by all its installations. Each answer costs what the AI provider charges for it.

Compare the editions → How the allowance is spent →

Questions

Questions people ask

Which AI model does it use?

Amtiri sets the model each assistant uses on its Portal, so an assistant can move to a better model without a new release of Data Orchester. Before the assistant is turned on, the disclosure names the AI providers that serve it, and a move to a provider it did not name asks for consent again: see Turning it on.

What is sent to the AI?

What you type, the records the assistant reads and the pages of your attachments it reads or looks at. Secrets reach it as «redacted», live values only with Live values on and web searches only with Web search on. Users, licence files and logged history are never sent. The full list is in What is sent, and what never is.

Does the plant need internet access?

The instance must reach dataorchester.com over HTTPS, as it does for its licence, and nothing else: documentation lookups, web searches and the pages they cite all go through Amtiri's Portal. An air-gapped installation on an offline licence key has no assistant: see When the assistant is off.

Can it change my plant?

No. It proposes changes to your configuration on cards; you apply them, review them in the editor and save them, through the same checks as a change made by hand. It never saves, never starts or stops the engine and never writes a value to the plant.

Is it on by default?

No. It is off on every instance until a user with the Configuration role turns it on, for that instance, after reading what is sent and to whom. Web search and Live values are two more switches, off until ticked.

Which languages does it speak?

It answers in the language of your latest message. The Site around it, the chat included, is in English and Spanish.

What does it cost?

It is paid from the organization's monthly AI allowance, in US dollars, which the edition of its licence sets: see Pricing. Each answer costs what the AI provider charges for it, web searches included, and the chat shows what is left this month. Once the allowance is used up, the assistant waits for the first day of the next month (UTC). See Cost and allowance.

Turn it on in your Site

Install or update Data Orchester; then a user with the Configuration role turns the assistant on from the Assistant tab, after reading what it sends and to whom.

Download Data Orchester Read the guide