Basics

This chapter explains the basic usage logic and general rules of DataMesh Inspector, helping users understand how the system works before diving into the detailed operation chapters.

Basic workflow overview

DataMesh Inspector provides a unified workflow centered around scenes, devices, alerts, and handling:

1. Enter the target building or park scene.
2. Review the overall operational status.
3. Identify and monitor alert information.
4. Locate the device associated with the alert.
5. Perform analysis, handling, or on-site inspection.

This workflow applies to all roles, but specific operations may vary depending on the client application.

Note:
This flow illustrates the overall usage logic and relationships between objects in DataMesh Inspector. It does not describe role-specific responsibilities or cross-application collaboration. Detailed alert handling workflows and operational steps are covered in later chapters.

Scenes, assets, and alerts

The core object system in DataMesh Inspector consists of:

• Scene

Organizes and displays the spatial structure of a building or park. It serves as the entry point for browsing and analysis.

• Asset (Device)

Represents the operational object, typically belonging to a specific space or system.

• Alert

An abnormal notification generated based on device status or business rules.

Users can navigate from a scene perspective to a specific device and then analyze and handle issues.

Basic alert handling process

This section explains the status flow of alerts from a system and management perspective. It helps users understand the alert lifecycle in DataMesh Inspector.

This section does not cover specific application UI operations or on-site handling steps. Detailed usage in Command Center and Inspector is covered in later chapters.

Basic workflow for alert handling

In the current version, alert handling follows this basic workflow:

Alert Generated → Alert Confirmed → Analysis & Handling → Alert Closed

Here, Confirm and Close are distinct management actions that indicate different stages in the alert lifecycle.

Alert status definitions

Confirm Alert
Indicates that the alert has been noted by the Operations Manager and has entered the handling process. This action assigns responsibility and tracks follow-up status, preventing alerts from being overlooked.
Confirmation does not mean the issue is resolved.

Close Alert
Indicates the issue has been resolved or determined not to require further follow-up.

Once closed, the alert lifecycle ends.

Permissions for status operations

• Confirm and Close actions can only be performed by Operations Managers in the Command Center.
• Inspector (Mobile Application) does not support alert status operations and is used primarily for on-site verification and information recording.

Alert statuses remain synchronized in real-time across application clients.

Cross-client consistency and differences

DataMesh Inspector operates on a unified data system, keeping core information consistent across application clients:

• Scene structure, device information, and alert statuses are synchronized across application clients.
• Alert confirmation and close operations take effect in real-time on all application clients.

Differences between application clients in usage methods and functional focus

• Command Center focuses on overall browsing, analysis, and management.

• Inspector (Mobile Application) focuses on on-site viewing, device location, and execution

Detailed operations for each application are described in later chapters.

Preparation and data prerequisites

DataMesh Inspector visualizes, analyzes, and supports operations on pre-built digital twin scenes.

Before using Inspector, necessary data and scene preparation must be completed in relevant platforms and tools.

This section describes the prerequisites and data sources for normal operation; it does not provide configuration or import steps.

Prerequisites

Before using DataMesh Inspector, ensure the following:

• Building or large-scale scenes have been created for display.
• Device digital twins have been created and relationships established.
• Spatial digital twins have been created with a complete hierarchy.
• Device digital twins are connected to operational data and can generate alerts.
• (Optional) Spatial scenes are associated to support 3D browsing and scene drill-down.
• (Optional) Scenes have positioning markers for MR scene overlay.

Note: If some spaces are not associated with digital twin scenes, Inspector can still display connected assets and operational data, but 3D scene browsing, spatial analysis, or MR features will not be available.

Data sources and responsibilities

DataMesh Inspector does not create data or scenes itself. Its data comes from multiple platforms and tools.

Prior to using Inspector, data preparation is typically completed within the following systems:

• FactVerse Platform – Provides BIM scenes, device, and spatial digital twins.
• FactVerse Designer – Provides 3D scene files and location information for MR overlays.
• DFS – Provides device operational data and generated alerts.

During runtime, Inspector unifies these data sources for display and interaction, supporting daily monitoring and operations.

Data usage scope in Inspector

In Inspector, users can:

• Browse prepared building or park scenes.
• View the device associated with these scenes.
• View alerts generated from device data.
• Locate the device and perform on-site viewing on supported application clients.

Inspector does not support:

• Creating or editing digital twins.
• Building or merging BIM scenes.
• Configuring device-to-space relationships.
• Managing data sources or alert rules.

These actions must be completed in the corresponding platforms or tools.

Reference documentation

For scene construction, digital twin creation, or relationship configuration, refer to:

• FactVerse Platform User Manual
• FactVerse Designer User Manual
• DFS User Manual

These documents provide detailed instructions for data preparation and configuration workflows.