跳转到内容
Tier0 Docs

UNS Modeling

适用版本EdgeCloudEnterprise

此内容尚不支持你的语言。

How the Demo UNS is Structured

Section titled “How the Demo UNS is Structured”

Asset Data

Section titled “Asset Data”

Industrial data from machines and equipment, assets that have physical locations, is modeled based on the ISA-95 standard.

ISA-95 Equipment Hierarchy

Section titled “ISA-95 Equipment Hierarchy”

The ISA-95 Equipment Hierarchy outlines how physical assets and control systems are structured within an organization. This structure ensures that each level interacts appropriately with higher and lower levels, creating a clear operational flow from the enterprise systems down to individual machines.
The ISA-95 equipment hierarchy is broken into the following levels:

  • Enterprise: The top level, representing the entire organization. This includes overall business processes and decision-making entities, typically supported by ERP systems.
  • Site: Represents a specific geographic location or facility. Each site can have its own management systems and local production control.
  • Area: An operational division within a site, often a functional area such as packaging, assembly, or warehousing.
  • Process Cell: The basic unit of manufacturing within an area. It encompasses all the equipment required to produce a specific product or perform a specific function.
  • Unit: A distinct part of the process cell, responsible for a specific function such as mixing, heating, or assembling.
  • Equipment Module: A modular piece of equipment that performs a specific task within a unit. For example, in a mixing unit, the module could be a heating element.
  • Control Module: The lowest level representing individual devices or controllers such as sensors, pumps, actuators or PID control loops that handle direct control of physical processes.

Demo Model

Section titled “Demo Model”
Terminal window
Enterprise (Level 4)
└── Site (Level 3/4)
    └── Area (Level 3)
        └── Work Center / Process Cell (Level 2/3)
            └── Equipment / Unit (Level 1/2)
                └── Control Module / Device (Level 0/1)

Business Data

Section titled “Business Data”

For data related business plan and process objects, such as production orders and order plan in an ERP, model it according to business context.

Business Data Modeling Guide

Section titled “Business Data Modeling Guide”
Terminal window
Factory / Business Domain / Business Object / topic Type / Topic

  • Business Domain: Confirm the business process or system the data belongs to.

    Terminal window
    ERP
    MES
    WMS
    QMS
    EAM
    LIMS
    Planning
    Inventory
    Maintenance
    Quality
    Logistics
    ...

  • Business Object: Managed core object in the business domain.

    Terminal window
    ProductionOrders
    WorkOrderPlan
    MaterialInventory
    QualityInspection
    MaintenanceOrders
    PurchaseOrders
    Shipments
    ...

  • Topic Type: Decide the data type among Metric, Action and State.

    Topic Type Used for Examples
    STATE Current status or current facts Work order status, order status, equipment status
    METRIC Continuously changing numeric values Temperature, speed, output, OEE, energy consumption
    ACTION Commands for external executors Start equipment, stop equipment, reset alarm, request work order dispatch

Demo Model

Section titled “Demo Model”
Terminal window
DemoFactory
└── ERP
    ├── ProductionOrders
    │   └── State
    │       ├── UpsertProductionOrder
    │       └── OrderList
    └── WorkOrderPlan
        ├── Metric
        │   └── SplitCount
        └── State
            ├── PlanStatus
            └── WorkOrderList

How to Avoid Topic Explosion

Section titled “How to Avoid Topic Explosion”

Tier0 uses 3 fixed topic types: Metric, Action, and State to avoid topic explosion.

  • Use Metric for high-frequency real-time data

    Put high-frequency measurements and telemetry under Metric instead of expanding the namespace for every signal detail.

    Terminal window
    Factory_A
    └── SMT_Line_1
        └── Machine_001
            ├── Temperature_Value
            ├── Temperature_Unit
            ├── Temperature_Status
            └── Speed_Value

  • Use State for low-frequency status data

    Put low-frequency status, snapshots, and current business state under State. Avoid creating a new topic for every changing entity such as jobs, batches, or orders.

    Terminal window
    Factory_A
    └── SMT_Line_1
        └── State
            ├── Job_001
            ├── Job_002
            └── Job_003

  • Use Action for low-frequency action data

    Put commands, requests, and operator actions under Action. Keep action inputs as fields on a topic rather than creating one topic per parameter.

    Terminal window
    Factory_A
    └── SMT_Line_1
        └── Machine_001
            ├── Start_Command
            ├── Target_Height
            └── Light_On

Payload Structure

Section titled “Payload Structure”

Data to be consumed and written back must both be considered when structuring the topic payload.

  • Action

    Action payloads automatically include _timestamp, which records when the data is stored in the Tier0 database.

    Terminal window
    {
      "light_turn_on": true,
      "height_adjust": 12.5,
      "_timestamp": "2026-07-10T10:00:00Z"
    }

  • Metric

    Metric payloads automatically include _timestamp, which records when the data is stored in the Tier0 database, and _quality, which maps the data quality.

    Terminal window
    {
      "production_order_id": "PO-20260710-001",
      "plan_id": "PLAN-001",
      "plan_number": "WOP-20260710-001",
      "split_count": 3,
      "updated_at": "2026-07-10T10:00:00Z",
      "_timestamp": "2026-07-10T10:00:00Z",
      "_quality": "Good"
    }

  • State

    State payloads automatically include _timestamp, which records when the data is stored in the Tier0 database.

    Terminal window
    {
      "event_id": "EVT-001",
      "event_type": "UPSERT",
      "source": "ERP",
      "production_order_id": "PO-20260710-001",
      "order_number": "PO-001",
      "product_code": "SKU-1001",
      "planned_qty": 1200,
      "unit": "pcs",
      "status": "Released",
      "due_date": "2026-07-12T00:00:00Z",
      "updated_at": "2026-07-10T10:00:00Z",
      "_timestamp": "2026-07-10T10:00:00Z"
    }