Factory Management

Table of Contents

• Overview
• Screen Layout — 6 Submenus
• Model Screen (/model/index)
  • Top Toolbar
  • Site List (Card Grid)
  • Logical / Physical Model (Left / Right Trees)
• Asset Screen (/asset/tree/index)
  • Left — Asset Tree
  • Right — Asset Detail Form + Child Table
• Tag Screen (/tag/index)
  • Top Toolbar
  • Search Form (Multiple Filters)
  • Tag Table (10 Columns + Actions)
• Ontology Screen (/ontology/index)
• Metadata Screen (/metadata/index)
• Base Data Screen (/basedata/index)
• Factory Model Commit
• Usage Scenarios
• FAQ
• Related Screens

---

Overview

The Factory Model group is where you register, edit, and delete the plant structure and its domain meta information (assets, tags, ontology, metadata, base data). It consists of six sub-screens, all of which connect directly to the operational meta store.

Submenu	Internal URL	Purpose
Model	/model/index	Add sites + map logical/physical models + commit the model
Asset	/asset/tree/index	Edit the asset tree (site→area→line→equipment→tag)
Tag	/tag/index	List, search, bulk-delete, and export registered tags to Excel
Ontology	/ontology/index	Register the asset classification scheme (categories and meta attributes)
Metadata	/metadata/index	User-defined meta attribute key-values per domain
Base Data	/basedata/index	Register code masters and reference values

You must register all sites, assets, and tags in this menu before operation begins — otherwise other screens such as the Dashboard, Data Points, and Alarms have nothing meaningful to show.

---

Screen Layout — 6 Submenus

Operational flow:

[모델]   →   [에셋]   →   [태그]
사이트 추가      자산 계층 등록      태그 등록·매핑
   │              │                  │
   └─────[온톨로지·메타데이터·기준정보 보강]──────┘
   │
   └→ [팩토리 모델 확정] (배포)

Screen	Frequency of Use	When to Open It
Model	Medium	When adding a new site or adjusting logical↔physical mapping
Asset	High	When changing the asset hierarchy or asset meta
Tag	Very high	Tag registration, editing, alarm band setup — the most frequently used screen
Ontology	Medium	When reorganizing the classification scheme
Metadata	Low	When adding user-defined meta attributes
Base Data	Low	When adjusting the code master

---

Model Screen (/model/index)

Top Toolbar

🗂 모델                     [✓ 팩토리 모델 확정] [💾 메타 스토어 백업] [↻]

Button	Action
Commit Factory Model	deployAssetToEvent() — Applies registered assets/tags to the event rules and pushes them to the rule engine (see Factory Model Commit below)
Back Up Meta Store	backup() — Backs up the entire meta store (for administrator retention)
Refresh	refresh()

Information Box

🏭 Add a site and configure the physical/logical model Register the factory (site) to which industrial data will be connected. Next, connect to the OPC or other industrial protocol linked to that site to complete the physical model. Once you substitute the physical model with a logical model, the site structure configuration is complete.

Site List (Card Grid)

사이트 목록 [전체 N개의 사이트]                    [➕ 사이트 추가]
─────────────────────────────────────────────────
[ 사이트 카드 ] [ 사이트 카드 ] [ 사이트 카드 ] ...

Each site card (site-panel, 240px) shows the following.

Area	Display
Top (site-title)	Site ID (yellow background)
Body (site-body)	🏭 Site icon + site name + description — clicking it loads that site's asset/connection tree below (loadTreeData())
Footer (site-footer)	🔧 Edit (editSite()) / 📁 Delete model (deleteModels()) / 🗑 Delete site (deleteSite())

Add Site Form

Field	Description
Site ID	Letters, digits, and _ only
Site Name	A human-readable name
Description	Free text
Latitude / Longitude	Coordinates where the marker appears on the map (optional)

Logical / Physical Model (Left / Right Trees)

Selecting a site card expands two trees below it, side by side.

Left — Asset [Logical Model] (assetTreeDiv)

Action	Action ID	Description
Refresh model tree	loadTreeData(last_tree_site_id)	Reloads the tree
Search assets	searchItem('Asset')	Toggles the search input above the tree
Add asset	showAddModal('Asset')	Opens the Add Asset modal
Edit asset	showModifyModal('Asset')	Edits the selected asset
Delete asset	deleteItem('Asset')	Deletes the selected asset

The logical model is structured as site→area→line→equipment→tag, and is the hierarchy the operator builds semantically.

Right — Connection [Physical Model] (opcTreeDiv)

Action	Action ID	Description
Search connections	searchItem('OPC')	Toggles the search input above the tree
Add connection	addOpc()	Goes to the registration form in Connection Management

The physical model is a communication-unit tree of the form OPC server→channel→tag.

Logical ↔ Physical Mapping

Link the logical asset nodes on the left to the physical OPC tags on the right by dragging or mapping. This mapping lets the system know which physical tag (e.g. PDI_001 on OPC-LINE-A) supplies the data for a logical asset (e.g. the motor on Line A).

Add/Edit Asset Modal

Clicking Add Asset or Edit Asset in the left toolbar opens the standard modal. With the V2026.05 design system, every form in the modal follows a unified fieldset + form-stack structure.

┌─🏭 에셋 추가 및 수정─────────────────── × ─┐
│                                          │
│  ┌─🗂 상위 에셋──────────────────────┐   │
│  │ 상위 에셋 ID    [읽기 전용]          │   │
│  │ 상위 에셋 명    [읽기 전용]          │   │
│  └──────────────────────────────────┘   │
│  ┌─📦 에셋 정보─────────────────────┐   │
│  │ 에셋 ID         [입력]               │   │
│  │ 에셋 명         [입력]               │   │
│  │ 설명            [입력]               │   │
│  └──────────────────────────────────┘   │
│                                          │
├──────────────────────────────────────────┤
│                       [× 취소] [💾 저장]  │
└──────────────────────────────────────────┘

Area	Display
Modal header	🏭 icon + title + × close
Parent asset fieldset	ID and name of the parent node (read-only — shows the tree selection)
Asset info fieldset	ID, name, and description of the new asset (input)
Modal footer	× Cancel / 💾 Save (on save, saveForm('Asset'))

All field labels use the form-label control-label class, so widths and alignment are consistent. Modals on other screens (work order, event, shift schedule, and so on) use the same fieldset + form-stack pattern.

---

Asset Screen (/asset/tree/index)

Edit the asset tree in depth and define asset-level meta, tags, and connection relationships on a single screen. The ✓ Commit Factory Model button is at the top right, and the screen consists of a col-lg-3 tree on the left plus a col-lg-9 detail form, timeline, and child table/tabs on the right.

Left — Asset Tree

🗂 모델 — 사이트 → 구역 → 라인 → 설비   [💬] [🔍] [📋]
사이트: [▼]
[에셋 트리 / 연결 트리]
─────────────────────
🔗 오브젝트 ID:  -      ← 트리에서 호버 시 도메인 ID 표시 (footer)

Header Icon	Action
💬 (speech bubble) — Show tag descriptions	Toggles display of tag node descriptions in the tree
🔍 Search	Toggles the text search input within the tree
📋 Copy	Copies the selected tag name to the clipboard

Right — Asset Detail Form + Timeline + Children/Tabs

Empty State — No Asset Selected

If no node is selected in the left tree, the detail area on the right shows an empty-state message.

       🟦 (큐브 아이콘)
   에셋이 선택되지 않았습니다
왼쪽 에셋 트리에서 [에셋명을 선택]하여 주십시오.

Asset Information Panel — Two Full-Color Gradient Status Cards

When you select an asset, a single meta line (type + registration/modification date) plus two cards — Connection Status / Health Status — appear at the top left of the panel body.

Card	Icon	Display
Connection Status (connection_status)	📶 Wi-Fi	Full-color gradient — 🟢 Normal / 🟡 Delayed / 🔴 Abnormal / ⬛ Disconnected / ⚪ Unknown
Health Status (health_status)	💗 Heartbeat	Full-color gradient — 🟢 Normal / 🟡 Warning / 🔴 Critical

Each card shows an icon + label + value (e.g. "Connected", "Critical") on a gradient background, so the status is recognizable by color alone from a distance.

Asset Image (Right)

If an image is registered, it is shown as SVG/PNG. If not, an empty state is displayed:

       🖼 (이미지 아이콘)
       이미지 없음
선택한 노드에 등록된 이미지가 없습니다.

Basic Information Panel (Input)

Field	path	Placeholder / Description
Asset ID	asset_id	Assigned automatically by the system / read-only when editing
Asset Name	asset_name	placeholder: ASSET_NAME_00001 (영문 및 숫자, _ 만 입력)
Common Group	table_type	MOTOR/PUMP/VALVE, etc. — selector
Description	description	Free text

Asset Image Panel

Control	Action
📂 Choose File	Select a PNG/SVG (640×320 recommended)
☁ Upload	Registers the selected image to that asset

Timeline Panel — Trend Over Time

Selecting an asset displays the timeline panel below it. The panel header shows the period (from_to), and the body shows a horizontal bar timeline with a five-item legend on the right.

Legend	Color	Meaning
Unknown	⚪ Gray	No reception history
Normal	🟢 Green	No anomalies
Warning	🟡 Yellow	Warning alarm present
Critical	🔴 Red	Critical alarm present
Disconnected	⬛ Dark red	No data received for 24 hours or more

Hovering over the ⓘ info icon at the top left of the panel body shows a large tooltip with the mapping table for the 5 connection statuses and 3 health statuses.

Child Asset List (when SITE/AREA/LINE is selected)

Shown only when a SITE, AREA, or LINE node is selected.

Column	Width	Display
Asset ID	250px	ID of the child asset (domain badge)
Asset Name	250px	Name of the child asset
Description	Auto	Notes

When EQUIPMENT Is Selected — 10-Tab Panel

Selecting an equipment (EQUIPMENT) node displays a 10-tab panel instead of the child table.

Tab	Icon	Contents
① Connection	🌐	OPC/PLC connections mapped to that equipment
② Tags	🏷	Tags belonging to the equipment
③ Data	🗄	Recent data points
④ Alarms	🔔	Alarm occurrence history
⑤ Events	📅	Asset event log
⑥ Status	👁	Status (Context) key-values
⑦ Aggregation	🥧	1-minute / 5-minute / 1-hour aggregates
⑧ Commands	🎮	Commands that can be issued to the asset
⑨ Statements	💻	EQL statements evaluating the asset
⑩ Documents	📄	Attached documents related to the asset

---

Tag Screen (/tag/index)

The screen for searching, bulk-deleting, and exporting all registered tags to Excel.

Top Toolbar

🏷 태그 [전체 N개]                                [✓ 팩토리 모델 확정]

Button	Action
Total N	Number of registered tags (comma-separated thousands)
Commit Factory Model	deployAssetToEvent() — Same as on the Model screen

At the right of the list panel header are three buttons: Delete Selected Tags / Excel Download / Refresh.

Search Form (Multiple Filters)

Field	id	Width	Options
Site	site_id	180px	Select site + registered sites
Area	area_id	180px	Select area (refreshes automatically when the site changes)
Line	line_id	180px	Select line (refreshes automatically when the area changes)
Equipment	equipment_id	180px	Select equipment
Connection	opc_id	180px	Select OPC + registered OPCs
Tag ID	tag_id	180px	placeholder: "Tag ID"
Tag Name	tag_name	180px	placeholder: "Search tag name ..." (autocomplete)
Data Type	java_type	180px	INT/FLOAT/STRING/BOOL, etc. — selector

Tag Table (10 Columns + Actions)

Column	Width	Display
Select	50px	Checkbox for bulk deletion
No.	40px	Row number
Tag ID	100px	Domain identifier
Tag Name	300px	Human-readable name
Data Type	80px	String/Short/Integer/Long/Float/Double/Boolean/Date
Point Count	80px	Cumulative number of received points
Alarm Count	60px	Cumulative number of alarms
Current Value	60px	Last received value
Unit	40px	Measurement unit (°C, kPa, rpm, etc.)
Last Update Time	160px	Time of last reception
Actions	60px	🔧 Edit / 🗑 Delete — visible only to ADMIN

The list has no Description or Latency [MS] columns. Tag descriptions are in Tag Detail, and latency is in the connected tag list of Connection Management.

Only ADMIN can see the Actions column. For the USER and API roles the entire column disappears, so if the edit and delete icons are missing, it is a permissions issue.

Tag Registration/Edit Form (/tag/form)

The tag form is a two-tier structure: a tag form panel (basic information) at the top of the screen and 8 tabs at the bottom.

Top — Tag Form Panel (Always Visible)

Field	Description
Tag ID	Letters, digits, _ (read-only in edit mode)
Tag Name	For human identification — letters, digits, and the special characters _ and . only
Data Type	String / Short / Integer / Long / Float / Double / Boolean / Date
Tag Description	Free text (100 characters)

At the right of the panel header is a View Tag button — jumps straight to the Tag Detail screen.

Bottom — 9 Tabs

Tab	Icon	Role
① Attributes	☀	Data meta — unit, display format, validation range (min_value/max_value), null allowed
② Link	🔗	Maps this tag to equipment — see below
③ Alarm Band	🔔	Six-level thresholds (numeric) / true·false priorities (Boolean) — hi_hi/hi/lo/lo_lo are shown as color bands on a single bar via a CSS visual band
④ Formula	🧮	Formula for virtual tags, references to other tags
⑤ Sampling	💉	Collection interval, duplicate-value compression, outlier cutoff
⑥ Aggregation	🪙	1-minute / 5-minute / 1-hour aggregation intervals and aggregation types (min/max/avg/sum/count)
⑦ AI	🧠	Integration settings for prediction and anomaly detection models
⑧ Publish	📬	Automatic publishing to external topics (Kafka/MQTT) or workflows
⑨ Notes	💬	Operator notes and change history comments

Link Tab — Equipment Mapping (Prerequisite for OEE, RAM, and EMS)

Item	Description
Equipment Search	Search by equipment ID or name and select (e.g. ASSET_CNC_001, 사출기 #3)
Currently Mapped Equipment ID	Read-only — linked_asset_id updates automatically when you pick equipment
Unmap	Clears the mapping

Mapping Is to Equipment Only

The link target is equipment (asset_type='M') only. Lines and areas cannot be mapped.

The mapped equipment uses this tag's data in OEE / RAM / EMS analysis. Conversely, if a tag is not linked to equipment, that tag will not appear in ISO analysis — this is the first place to check when analysis results look empty.

Alarm Band Tab — Visual Band (Numeric)

For numeric tags, the Alarm Band tab shows a single-line graphic bar so you can see at a glance which color range lo_lo · lo · hi · hi_hi maps to within the min_value ~ max_value range.

[ ███ lo_lo ████ lo ════════════ 정상 ════════════ hi ████ hi_hi ███ ]
   🔴 심각        🟠 경고          🟢 정상           🟠 경고      🔴 심각

Changing a value redraws the visual band immediately — check the distribution after entering values and before saving.

Item	Description
lo_lo / hi_hi	Critical alarm threshold — the last warning line before a trip
lo / hi	Warning alarm threshold
trip_lo / trip_hi	Trip (equipment stop command) threshold — triggers an action beyond an alarm
band_message	Message displayed when the alarm occurs
use_alarm	Whether the alarm band is enabled — turning it off ignores all thresholds

Alarm Band Tab — Boolean

Item	Description
bool_true / bool_false	Alarm definitions for the two values (each with priority, message, and enabled flag)

Next to each field label is a 152px-wide inline help text (form-help-inline) describing the format and constraints.

Virtual Tags and Virtual Points

The tag screen offers two special registration methods.

Screen	Purpose
tag/add_vtag.jsp (64 lines)	Virtual tag — a tag created by combining/calculating other tags, with no physical sensor
tag/add_vpoint.jsp (51 lines)	Virtual point — a one-off calculated result point (added from the stream screen)

Tag Detail Screen (/tag/view/{tag_id})

You reach this screen by clicking a tag name in the tag list. It gathers all operational information for a single tag onto one screen, laid out as col-lg-3 on the left (2 panels) + col-lg-9 on the right (current value panel + data/alarm tabs).

Top — Page Header

🏷 태그 | {태그명}                       [ 태그명 입력 ▼ ] [태그 이동 →] [← 목록] [↻]

Control	Action
Tag name input + Go to tag	Search another tag with autocomplete and jump straight to its detail screen (moveTag())
← List	Returns to the tag list (/tag/index)
↻	Refreshes the screen (re-subscribes to real-time data)

Left ① Tag Information Panel — 4 ds-dl Sections

At the right of the panel header is a ⚙ gear — goes to the tag settings form (/tag/form). Saving is possible only for roles with change permission.

Section (view-section-title)	Displayed Items (definition list)
🪪 Basic Information	Tag ID (domain badge TAG) · Tag name · Data type · Tag description · Registration date
🔗 Connection Information	Connection ID (domain badge OPC) · Connection name
🏭 Site Information	Site ID (badge) · Site name
🟦 Asset Information	Asset ID (badge) · Asset name

All IDs are shown as color badges by domain; clicking a badge takes you to that domain's detail screen (e.g. site → site screen).

Left ② Statistics Panel — Points, Alarms, Alarms by Severity

At the right of the panel header is a Today / Yesterday toggle button that switches the statistics period.

Section	Display
📶 Points	Large number for "points received today" + 24-hour spark (point_24hh) + cumulative total point counter
🔔 Alarms	Large number for "alarms raised today" + 24-hour spark (alarm_24hh) + cumulative total alarm counter
❗ Alarms by Severity	Three-card grid — Info (blue) · Warning (yellow) · Critical (red), each with a large number and label

┌── 정보 ──┐  ┌── 경고 ──┐  ┌── 심각 ──┐
│   1,234   │  │    23     │  │     2     │
│  (파랑)   │  │ (노랑)    │  │  (빨강)   │
└──────────┘  └───────────┘  └───────────┘
       ↓ 그 아래에 도넛 차트
   [중요도별 점유율 도넛 차트]

Right ① Current Value Panel (5 Columns)

At the right of the panel header is a quick-navigation button group.

Quick Link	Action
🔀 Stream	View this tag in real time in Stream
🗄 Trend	The Trend for this tag
🔔 Alarms	The Alarm history for this tag

Column	Display
Current Value	Large number — quality color badge (good = green · uncertain = yellow · bad = red)
Last Update	Timestamp (yyyy-MM-dd HH:mm:ss)
Latency [MS]	Average response latency
Quality	OPC quality code (e.g. GOOD, BAD, UNCERTAIN)
Error Code	The code, if the last reception returned an error

Right ② Data/Alarm Tabs

Tab	Contents
📊 Data Points	Chart panel (real-time trend line — numeric) or status timeline (Boolean) + aggregate table (points received today · min · max · average · sum / for Boolean: first · last · sum)
🔔 Alarms	List of alarms raised on this tag and their handling status

The chart on the Data tab updates in real time over WebSocket. While the chart is loading, a "Loading chart..." message appears in the center.

This detail screen is the entry point for comprehensive per-tag operator inspection — threshold review, anomaly tracking, and physical mapping verification.

---

Ontology Screen (/ontology/index)

An advanced meta screen that visualizes the asset classification scheme (categories, meta attributes, relationships) and the site-level knowledge graph. With the design system overhaul it has been restructured into a site banner + left side cards + graph body.

Top — Site Banner (onto-site-banner)

A full-color banner appears directly below the page header.

🏭 {사이트명} | {사이트 설명}                     [기준시간 : {gen_timestamp}]

• When the site changes, the banner text updates immediately
• The reference time is when the tree and metrics were last refreshed

Left ① Site Panel (col-w-280)

Panel Header

Button	Action
❄ Radial toggle	Switches the tree in the panel body between a standard tree and a radial graph
↻ Refresh	Rebuilds the tree (createTree())

Panel Body — Two Selectors

Selector	Options
Select Site	All sites + registered sites (the tree is rebuilt immediately on change)
Initial Level	Site > Area / Site > Area > Line / Site > Area > Line > Equipment (default)

Panel Footer

Displays the total number of sites — 🏭 전체 사이트 N개.

Left ② Four Asset Count Cards (onto-count-stack)

Below the site panel is a full-color gradient four-card grid showing the asset counts for the selected site.

Card	Icon	Display
AREA	🏭 Garage	Number of areas (area_size)
LINE	📜 Conveyor	Number of lines (line_size)
EQUIPMENT	📺 Betamax	Number of equipment (equipment_size)
TAG	🏷 Tag	Number of tags (tag_size)

Body — Ontology Graph

Visualizes the selected site's asset tree on a large canvas.

Action	Shortcut
Click a node	Shows that node's meta panel (event/status/aggregation container for the selected site)
Zoom in/out	Mouse wheel
Drag a node	Moves its position
Hover a node	onto-tip-* tooltip (domain ID badge + meta key preview) — shown in a different oklch color per domain

Key Features

• Category tree / radial — Builds the asset classification hierarchy (e.g. rotating machinery → motor → AC motor)
• Meta attribute definition — Defines the meta keys an asset will have per category (e.g. rated output and voltage for a motor)
• Relationship definition — Expresses relationships between assets (parent / interlocked / substitute)
• Validation rules — Validation rules for meta input (required / numeric / range)
• Domain ID badges — SITE/AREA/LINE/EQUIPMENT/TAG colors unified to the same oklch colors as Domain ID Unified Search

The ontology is not a screen that general operators use often. The system administrator defines it during initial system deployment or when reorganizing asset categories.

---

Metadata Screen (/metadata/index)

A lightweight screen for registering user-defined meta key-values per domain.

Examples

Domain	Meta Key	Value
Asset	manufacturer	"ABC Industries"
Asset	installed_year	"2020"
Tag	description_en	"Pump discharge pressure"
Order	customer_class	"VIP"

Input Fields

Column	Description
Domain Type	Asset/Tag/Order/Customer, etc.
Domain ID	The identifier within that domain
Meta Key	User-defined
Meta Value	Free text or number

Unlike the Ontology, metadata is free-form meta not bound to any category. Use it when you need quick, ad hoc meta.

---

Base Data Screen (/basedata/index)

The screen for registering code masters and reference values. Various code groups are managed as tabs.

Tab Layout (based on basedata/tab.jsp)

Tab	Description
Code Group	Bundles of codes used by the system (e.g. alarm priorities, work order statuses)
Code Item	Individual codes within a code group (e.g. INFO/WARN/ERROR)
Unit Master	Standard measurement units (°C, kPa, rpm, etc.)
Common Type	Asset common types (MOTOR, PUMP, VALVE)

Input Form (Example — Code Item)

Field	Description
Code Group	Parent group (e.g. ALARM_PRIORITY)
Code ID	System identifier (e.g. INFO)
Code Name	Korean label (e.g. 정보)
Order	Display order
Active	Y/N
Description	Free text

Base data defines system standard values, so it rarely changes. Use it only when reorganizing standard codes.

---

Factory Model Commit

Clicking the ✓ Commit Factory Model button at the top of the Model or Tag screen pushes all registered sites, assets, and tags to the event rule engine (CEP > Statements) in one batch.

Procedure

1. Verify that the asset trees, tags, and mappings for all sites are registered as intended
2. Click ✓ Commit Factory Model at the top
3. The system automatically registers asset-level domain rules (status, aggregation, event, command)
4. After registration, the new rules appear in CEP > Statements

When Should You Commit?

• Immediately after bulk-registering new sites or assets
• After making major changes to asset classification or hierarchy
• After changing alarm bands or meta attributes in bulk

Avoid clicking Commit Factory Model frequently (re-registering the rule engine is costly). It is best to click it once after all changes are complete.

---

Usage Scenarios

Scenario	Procedure
Setting up a new plant	Model → Add site → Build the area/line/equipment tree on the Asset screen → Register OPC connections → Register tags automatically or manually → Commit the model
Adding a new line	Asset screen → Select the site's area → Add a line → Build the equipment tree under the line → Register tags
Bulk tag cleanup	Tag screen → Narrow down the tags to retire with the search form → Select → Delete Selected Tags
Enriching asset meta	Metadata screen → Freely add entries with domain = Asset, key = manufacturer, etc.
Standardizing asset categories	Ontology screen → Reorganize the category tree → Define meta attributes per category
Adding a new unit	Base Data → Unit Master tab → Add
Bulk export of operational meta	Tag screen → Search → Excel download

---

FAQ

Q. I added a site, but no marker appears on the Dashboard map. A. If you do not enter latitude and longitude when adding the site, no marker is displayed. Use 🔧 Edit on the site card → enter latitude/longitude.

Q. What is the difference between committing the model and backing up the meta store? A. Commit Model registers assets/tags into the rule engine in bulk (activates operation); Back Up Meta Store is a separate task that saves the entire meta store to a backup file (data preservation).

Q. Can I change an asset's parent in the asset tree? A. In general we recommend not changing an asset's parent node (for history and rule consistency). If a change is unavoidable, consult the system administrator first.

Q. If I delete a tag, is the historical data deleted too? A. The tag meta is deleted, but the time series data is retained for a certain period according to the retention policy. Ask your system administrator for the exact retention policy.

Q. What is the difference between a virtual tag and a regular tag? A. A regular tag receives data from an actual sensor or PLC, while a virtual tag is a virtual time series produced by calculating the values of other tags. Example: defining the difference between sensor A and sensor B as virtual tag C.

Q. What happens if I do not use the ontology? A. Basic operation is unaffected. Use the ontology when you want to manage assets by a classification scheme (e.g. a consolidated report for all motors).

Q. Committing the model from the asset tree takes a long time. A. The more assets there are, the longer it takes (several minutes for thousands of assets). We recommend committing the model outside business hours.

Q. Autocomplete does not work in tag search. A. Autocomplete only works once a site is selected. Set the site selector first.

Q. Where can I see the key-values I registered in Metadata? A. On the asset detail screen, in the meta area of the asset tree, and as part of the message payload in the domain CRUD nodes of Flow.

Q. Does changing a code in Base Data affect existing data? A. Yes, code changes affect existing data as well. Please consult your system administrator before making changes.

---

Related Screens

• Dashboard — Registered assets are reflected in the KPI cards and the site map
• Connection Management — Registering the physical model (OPC) and monitoring its status
• Data Points — Time series lookup for registered tags
• Equipment — Monitor the equipment in the asset tree as cards
• Production Management — Register work orders, customers, products, employees, and shift schedules
• CEP > Statements — Domain rules registered after committing the model
• Flow — Automating asset registration and meta updates
• Status Code Definitions — Connection status and health status code mapping