Ontology primitives and data model configuration（本体论原语与数据模型配置）

The Ontology primitives for dynamic scheduling are comprised of one Schedule object and one or more Resource objects. Begin by creating your objects in the Ontology Manager. At a minimum, the Workshop widget requires two object types: a Schedule object and a Resource object.

Object Type	Description
Schedule object	A schedule object represents the task or activity of interest and should include a start and end time of when that event is occurring and/or the expected duration.
Resource object	A resource object represents any entity (such as a person, location, project, etc.) that the schedule object is being assigned to or scheduled against.

Ontology requirements

The Schedule object must meet the property and link requirements outlined below.

Required schedule object properties

Object property	Type
Foreign key to resource	String
Start time	Timestamp
End time	Timestamp

Required Ontology links

The schedule object type should be linked to each resource object type. Both many-to-one and many-to-many relationships are supported. For instance, in the example above, many tasks can be assigned to one aircraft. The Resource Link Type in the widget configuration determines whether the relationship is many-to-one or many-to-many.

Example: Aircraft maintenance schedule

The example below demonstrates the process of scheduling maintenance tasks for aircraft.

Simple configuration

The two-object-type configuration, the minimum requirement for the Dynamic Scheduling Workshop widget, is illustrated below.

• Schedule object type: In the example below, maintenance tasks are a time-bound activity.
• Resource object type: Aircraft are the object/place where the tasks are conducted.

Advanced configuration

The dynamic scheduling data supports a variety of additional configurations beyond the two-object-type model, allowing application builders to create complex, advanced workflows.

Building on the two-object-type model above, in addition to scheduling when maintenance tasks will occur on an assigned aircraft, users can also determine who will carry out the maintenance task by assigning the task to a specific mechanic. In this new Ontology, as pictured below, the mechanic object acts as a second resource object type, which can be unlimited in number.

• Schedule object type: Maintenance tasks are a time-bound activity.
• Resource object type 1: Aircraft are the object/place where the tasks are conducted.
• Resource object type 2: Mechanic who will carry out the assigned maintenance task.

---

中文翻译

本体论原语与数据模型配置

动态调度的本体论原语由一个Schedule（调度）对象和一个或多个Resource（资源）对象组成。首先在本体论管理器中创建您的对象。Workshop（工作坊）组件至少需要两种对象类型：一个Schedule对象和一个Resource对象。

对象类型	描述
Schedule对象	调度对象表示感兴趣的任务或活动，应包含该事件发生或预计持续的开始和结束时间。
Resource对象	资源对象表示调度对象被分配或排程所针对的任何实体（如人员、地点、项目等）。

本体论要求

Schedule对象必须满足以下概述的属性和链接要求。

必需的调度对象属性

对象属性	类型
指向资源的外键	String（字符串）
开始时间	Timestamp（时间戳）
结束时间	Timestamp（时间戳）

必需的本体论链接

调度对象类型应链接到每个资源对象类型。支持多对一和多对多关系。例如，在上述示例中，多个任务可以分配给一架飞机。组件配置中的资源链接类型决定了关系是多对一还是多对多。

示例：飞机维护调度

以下示例演示了为飞机安排维护任务的过程。

简单配置

下图展示了两种对象类型的配置，这是动态调度Workshop组件的最低要求。

• 调度对象类型： 在以下示例中，维护任务是具有时间限制的活动。
• 资源对象类型： 飞机是执行任务的对象/场所。

高级配置

动态调度数据支持超出两种对象类型模型的多种额外配置，使应用程序构建者能够创建复杂的高级工作流。

在上述两种对象类型模型的基础上，除了安排维护任务何时在指定飞机上执行外，用户还可以通过将任务分配给特定机械师来确定谁来执行维护任务。如下图所示，在这个新的本体论中，机械师对象充当第二个资源对象类型，其数量可以无限增加。

• 调度对象类型： 维护任务是具有时间限制的活动。
• 资源对象类型1： 飞机是执行任务的对象/场所。
• 资源对象类型2： 执行分配维护任务的机械师。