Skip to main content
Version: 2026.04

Resources

A Resource is any file that has been registered with the Istari Digital Platform — uploaded to your own storage or connected from a third-party app. Registration gives a file a stable identity (a UUID), a revision history, and a place in the platform's permissions, sharing, and composition primitives. File contents stay in your data plane (your own storage) or in the third-party app where they originate; the platform's control plane holds only metadata.

Note: When a Resource is used as input for platform functions (e.g. extraction, simulation), we call it a model. Artifact refers to a Resource produced by a function, or to a standalone Resource not further processed. Both are Resources. See Terminology for full definitions.

Why does it matter?​

  • Traceability and auditability. Every Resource has a unique, immutable UUID. You can track its lifecycle, revisions, and who accessed or changed it across teams and supply chains.
  • No data lock-in. Resource contents never leave your control — they sit either in your object store (uploaded) or in the external app (connected). The platform orchestrates access and processing without holding your data.
  • Seamless collaboration. Once registered, a Resource can be shared, included in a System, and used by agents for extraction or simulation while you keep a single source of truth.

How a Resource comes into being: connect or upload​

  • Connect. Create a secure link to a file stored in an external system (cloud storage like Google Drive or Microsoft 365, or PLM/ALM systems like Windchill or Teamwork Cloud). The platform stores only the reference and metadata — your file remains in its original location. When a job runs, authorized agents fetch the file directly from the source. This is the right pattern when your data already lives in those systems and you want to keep a single source of truth.
  • Upload. Register a Resource by sending the file to your own data plane (e.g. S3, Azure) via the platform. The platform never stores the bytes; it records metadata and the location in your storage. Best when you own the file locally or want it in your own bucket.

In both cases the Resource receives a UUID and can be used as a model for functions, included in Systems, and shared with controlled access.

Key details​

  • The control plane holds metadata only; the data plane (or the third-party app) holds the actual bytes.
  • Registered Resources can be grouped in Systems, versioned, and used as inputs for functions (e.g. extraction) run by the Istari Digital Agent.

How to register Resources​

User guide (UI):

Python client (SDK):

  • SDK setup — Install and configure the Istari Digital Python client.
  • Files, models & artifacts — add_file, add_model, create_revision, and related Resource APIs; see the Client reference for the full Client method list (including generate_upload_url / generate_download_url).

Artifact, Control plane, Data plane, File, Link, Model, Storage, Third-party data source