Skip to main content

Terminology

Agent (Istari Digital Agent) Software deployed in your infrastructure that executes jobs (e.g., extraction) on your files. Your data remains in your network, and the Agent securely returns results to the platform.

Agent Token A credential used exclusively by the Agent to authenticate with the platform. Not used by end users.

Artifact A file generated by running a function on a model (e.g., extracted images, tables). Also refers to standalone files that are not further processed by the platform.

Baseline In Systems: A snapshot tag that marks a reference state of a configuration, such as the required baseline tag on the first snapshot.

Configuration In Systems: A named collection of files (models and artifacts) within a system, with tracked or pinned revisions. Snapshots capture the state of a configuration at a specific point in time.

Control Plane The central services of the Istari Digital Platform, handling authentication, orchestration, and metadata (e.g., file existence, access permissions, job status). Note: The control plane does not store your file contents; your data remains in your own storage.

Control Tag A tag that restricts access to a resource. To access a resource with control tags, a user must have all assigned tags. Control tags only restrict access; they do not grant it.

Data Plane The storage location for your actual files (models and artifacts), typically your own object store (e.g., S3, Azure). The platform stores metadata in the control plane, while your file contents remain in your data plane.

DE Tool (Digital Engineering Tool) Software used to create or manipulate design or engineering files (e.g., CAD, requirements, simulation tools).

Extraction A Function that processes a model to generate artifacts (e.g., decomposing a 3D CAD file into 2D images, tables, or other derived files). Extraction is one of the most common functions, enabling users to work with and share derived data without requiring access to the original source tool (e.g., CAD software).

File Any file in the platform (uploaded or connected). When distinction is necessary:

  • Model: A source file that can be processed or used to produce artifacts.
  • Artifact: Output of a function or a standalone file that is not further processed.

Function An operation executed on one or more models to produce results, such as artifacts or simulation outputs. Functions are provided by modules installed on the Agent and can include operations like extraction, simulation, validation, or compliance checks. Each execution of a function is recorded as a job.

Infosec Level A classification level for access control (e.g., DOD infosec schema). Assign infosec levels to models, artifacts, and systems. (Experimental feature.)

Installation A single deployed instance of the Istari Digital Platform within your organization.

Integration A feature enabling the platform to interact with external tools or data sources (e.g., CAD tools, Office, third-party apps). Delivered via a module installed on the Agent.

Job A single execution of a function on a model (or models).

Model A file that the platform can process (e.g., from a DE tool) to produce artifacts. Broadly, any file you upload or connect.

Module Software installed on an Agent that provides one or more functions for a specific tool (e.g., Dassault CATIA V5 module). Each integration is delivered by a module.

Organization / Tenant Your company or customer entity. In admin and technical documentation, this is sometimes referred to as a tenant.

PAT (Personal Access Token) A credential for accessing the platform via API or CLI. Used by you; Agents use agent tokens.

Snapshot In Systems: An immutable, point-in-time record of file revisions in a configuration. Create and manage snapshots from the system overview. See the Systems guide.

Storage Where your data is stored (e.g., your object store, S3-compatible or Azure). Sometimes referred to as a bucket or object store.

System A method to group related models and artifacts into configurations. Use systems to track versions, take snapshots, compare changes, and share consistent file sets with your team. See the Systems guide.

Upstream / Downstream In remote sharing:

  • Upstream: The installation owning and sharing models.
  • Downstream: The installation receiving and viewing shared models (read-only).