跳转至

Ecosystem（生态系统）

Before getting started with resource management in Foundry, review the following concepts to understand the ecosystem of resource access and user enrollments.

Diagram of the resource management ecosystem.

  • Enrollment: An enrollment is the primary identity of your Organization and establishes your company's identity with Foundry services and the Foundry platform.
  • Organization: Organizations are access requirements applied to Projects that enforce strict silos between groups of users and resources. Every user is a member of one Organization, but can be a guest member of multiple Organizations. Learn more about Organizations.
  • Project: A Project is a collaborative space that brings together users, files, and folders for a particular purpose. Projects are the primary security boundary in Foundry and can be thought of as buckets of shared work. Learn more about Projects.
  • Resource: There are two potential uses of the term "resource" when working with Foundry. Service-level resources like CPU cores, virtual machines, and databases power the computation and data processing on the Foundry platform. Foundry resources sit above the service-level resources and include data concepts and structures such as Projects, workbooks, ontologies, and datasets. Most Foundry resources incur some form of service-level resource usage when users interact with them (e.g. by rebuilding a dataset).
  • Ontology and Ontology resources: The Foundry Ontology is an Organization’s digital twin; a rich semantic layer that sits on top of the digital assets integrated into Foundry. Ontology resources, namely object types and link types, are the building blocks, or "primitives", of an Ontology. Ontology usage is attributed to the Project of each object's input datasource. Learn more about the Ontology.
  • Usage account: A usage account combines and reports the usage incurred in a group of one or more Projects, typically for accounting purposes.
  • A usage account is associated with exactly one Enrollment.
  • Usage accounts are exclusive: Every Project must belong to exactly one usage account.
  • Usage accounts can be marked with one or more Organizations. These Organizations must be a part of the same Enrollment.
  • Projects can be transferred between usage accounts.
  • Usage accounts with associated Projects cannot be deleted.
  • Project label: A project label supports grouping Projects for ad-hoc usage analysis.
  • Project labels are not exclusive: a Project can be included in any number of project labels, and a project label can contain any number of Projects.
  • User: A user is an individual who has been authenticated and has access to Foundry. As users interact with the platform, they incur usage that can be tracked within the Resource Management app. Learn more about users.

中文翻译

生态系统

在开始使用 Foundry 中的资源管理之前，请先了解以下概念，以理解资源访问和用户注册（enrollment）的生态系统。

资源管理生态系统示意图

  • 注册（Enrollment）： 注册是您组织的首要身份标识，用于在 Foundry 服务和 Foundry 平台中建立您公司的身份。
  • 组织（Organization）： 组织是应用于项目（Project）的访问要求，用于在用户组和资源组之间实施严格的隔离。每个用户都是一个组织的成员，但可以作为访客成员加入多个组织。详细了解组织。
  • 项目（Project）： 项目是一个协作空间，为特定目的将用户、文件和文件夹整合在一起。项目是 Foundry 中的主要安全边界，可视为共享工作的容器。详细了解项目。
  • 资源（Resource）： 在使用 Foundry 时，“资源”一词有两种可能的含义。服务级资源（如 CPU 核心、虚拟机和数据库）为 Foundry 平台上的计算和数据处理提供动力。Foundry 资源位于服务级资源之上，包括数据概念和结构，如项目、工作簿、本体（Ontology）和数据集。大多数 Foundry 资源在用户与之交互时（例如，通过重建数据集）会产生某种形式的服务级资源使用。
  • 本体（Ontology）和本体资源： Foundry 本体是组织的数字孪生；它是一个丰富的语义层，位于集成到 Foundry 中的数字资产之上。本体资源，即对象类型（object type）和链接类型（link type），是本体的构建块或“原语”。本体的使用归属于每个对象输入数据源的项目。详细了解本体。
  • 使用账户（Usage account）： 使用账户合并并报告一组一个或多个项目中产生的使用量，通常用于会计目的。
  • 一个使用账户仅与一个注册相关联。
  • 使用账户是排他性的：每个项目必须恰好属于一个使用账户。
  • 使用账户可以标记一个或多个组织。这些组织必须属于同一个注册。
  • 项目可以在使用账户之间转移。
  • 有关联项目的使用账户无法删除。
  • 项目标签（Project label）： 项目标签支持对项目进行分组，以便进行临时使用分析。
  • 项目标签是非排他性的：一个项目可以包含在任意数量的项目标签中，一个项目标签也可以包含任意数量的项目。
  • 用户（User）： 用户是经过身份验证并有权访问 Foundry 的个人。当用户与平台交互时，会产生可在资源管理（Resource Management）应用中跟踪的使用量。详细了解用户。