Version: V1.0.0
Copyright: Shenzhen Intgeo Innovation Technology Co., Ltd. (深圳市英特吉欧创新科技有限公司)
Last Updated: 2026.03.16
"Shenzhen Intgeo Innovation Technology Co., Ltd. (深圳市英特吉欧创新科技有限公司)" and "GeoTwin" are trademarks or product identifiers of Shenzhen Intgeo Innovation Technology Co., Ltd. (深圳市英特吉欧创新科技有限公司). Unauthorized use is prohibited.
| Version | Date | Summary |
|---|---|---|
| V1.0.0 | 2026.03.16 | Initial release covering asset overview, product/device management, alert center, rule center, and ingestion APIs |
/api) and the SSE channel (TBD)| Component | Recommended |
|---|---|
| CPU | 4 cores or above |
| Memory | 16GB or above |
| Storage | 256GB SSD or above |
| Network | Gigabit Ethernet or equivalent |
apps/geotwin and start dev server (npm run dev);npm run build:prod) and deploy static assets to a web server (Nginx/gateway, TBD).When to use: Access the system via the unified portal. The system uses a token for API calls and message subscriptions.
Steps:
Troubleshooting:
/api, TBD) and check request errors in the browser developer tools (TBD).Offline licensing is not available in the current version (TBD: will be documented if supported in future releases).
GeoTwin (IoT) is an IoT asset management and visualization application. It provides product/device management, device data ingestion (API push), alert viewing and handling, and rule center configuration. It is suitable for unified IoT device management in campuses, cities, and enterprise asset scenarios.
| Data Type | Supported Format | Notes |
|---|---|---|
| Device data push (HTTP) | JSON | POST /gtportal/iot/api/{seriesNumber}/device/data; fields depend on product dynamic schema |
| Device coordinate push (HTTP) | JSON | POST /gtportal/iot/api/{seriesNumber}/device/location; includes x/y/z |
| Product icon upload | Image files (TBD) | System icon selection or custom upload |
| Output | Supported Format | Notes |
|---|---|---|
| Dashboards | In-app visualization | Trends and distributions (no file export, TBD) |
| Device charts | In-app visualization | Time-series charts for numeric fields (no file export, TBD) |
| Links / API endpoints | URL | Copyable data push service endpoints |
How it works: Aggregates key indicators (products, devices, alerts) into summary cards and trend charts for fast situational awareness.
Key features:
Steps:
Open "Asset Overview" from the left menu;
Switch the time scope and review trends;
Drill down to the alert list or device details for further handling (TBD: per actual UI).
Fig 5-1-1-1: Asset Overview (TBD)
How it works: Uses "Product" as a device-type abstraction. Protocol, schema, icons, and alert rules are configured at the product level as a foundation for device onboarding and alert evaluation.
Key features:
Steps:
Open "Product Management" to view the product list;
Click "Create" to add a new product and fill required fields (TBD: per actual UI);
Open product settings to configure protocol and connection details;
Configure the icon (system icon or upload a custom icon);
Configure fields and alert rules as needed, then save (TBD: activation policy per actual UI).
Fig 5-1-2-1: Product Management (TBD)
How it works: Uses "Device" as the concrete asset instance bound to a product. Device detail consolidates attributes, records, alerts, topics, and ingestion APIs for operations and integrations.
Key features:
Steps:
Open "Device Management" and search/filter devices (TBD: filters per actual UI);
Click "Create" to add a device, select a product, fill name and coordinates, then save;
Open device detail tabs to update attributes, review records/alerts, and copy MQTT/API information;
For camera devices, open the monitoring modal and verify playback (TBD: depends on stream URL and network).
Fig 5-1-3-1: Device Management (TBD)
How it works: Centralizes all alerts into a unified list, with filters by time range and product for quick triage and traceability.
Key features:
Steps:
Open "Alert Center" and set time range and product filters;
Review alert list and navigate to related device/detail when needed (TBD: entry per actual UI);
With sufficient permissions, delete single alerts or batch delete.
Fig 5-1-4-1: Alert Center (TBD)
How it works: Manages alert/strategy rules and binds them to devices via "Applied Devices" to control the effective scope.
Key features:
Steps:
Open "Rule Center" and review rule list/descriptions;
Open "Applied Devices" for the target rule;
Select devices and save to make the rule effective for the selected devices (TBD: effective timing per actual UI).
Fig 5-1-5-1: Rule Center (TBD)
Create a product in "Product Management" and complete protocol/schema configuration (TBD);
Create a device in "Device Management", select the product, and fill name and coordinates;
Open the device details "API" tab to obtain endpoints:
POST /gtportal/iot/api/{seriesNumber}/device/dataPOST /gtportal/iot/api/{seriesNumber}/device/location (only visible when realtime coordinate push is enabled)Send JSON payloads from external systems according to API docs. Data will be used for records/alerts/visualization (backend-dependent).
Fig 5-2-1-1: Device Detail - API (TBD)
Configure alert rules in product settings (threshold/severity/message; TBD);
In "Rule Center", open "Applied Device" for a rule, select target devices, and save;
When ingested data meets trigger conditions, alerts appear in "Alert Center" and "Device Detail - Alert".
Fig 5-2-2-1: Rule Center - Applied Devices (TBD)
In "Alert Center", filter by time range and product to locate alerts;
In "Device Management", open device details:
For exporting data as files, contact the delivery team to enable export features (TBD).
Fig 5-2-3-1: Alert Center - Filters and List (TBD)
Issue 1: Permission denied / API returns 401 or 403
Fix: Re-login; check token expiry; contact an admin to grant roles/permissions.
Issue 2: Coordinate push API is not shown in device detail
Fix: Ensure the product has realtime coordinate push enabled and refresh the page.
Issue 3: Camera stream cannot be played
Fix: Verify the stream URL accessibility; for m3u8 ensure HLS is reachable; check backend transcoding settings (TBD).
Issue 4: Alerts are missing or abnormal
Fix: Verify pushed fields match the product schema; verify rule thresholds and device bindings; confirm the rule is applied to the device.
| Term | Definition |
|---|---|
| Product | The device type abstraction, including protocol, schema, and icon |
| Device | A concrete asset instance bound to a product, with name/coordinates/series number |
| Series Number | A device identifier used to compose data push API paths |
| Dynamic Field | The product-defined reportable field set, defining JSON payload keys |
| Alert | A warning/event generated when rule conditions are met |
| Rule | A rule configuration for alerts/push strategies, can be applied to devices |
| Token / clientid | Authentication parameters for backend APIs, typically issued after login |
| SSE | Server-Sent Events channel for notifications/messages |
docs/images/en/5-1-1-1-asset-overview.png, docs/images/en/5-1-2-1-product-list.png, docs/images/en/5-1-3-1-device-list.png, docs/images/en/5-1-4-1-alert-center.png, docs/images/en/5-1-5-1-rule-center.png, docs/images/en/5-2-1-1-device-detail.png, docs/images/en/5-2-2-1-rule-applied-devices.png, docs/images/en/5-2-3-1-alert-list.png (and other key steps)