Model Management

System Platform → Model Management has four submenus, each mirroring one of the four model resources in the tenant-side "Model" section:

Submenu	Tenant-side doc
Thing Model	Thing Model
RPC Model	RPC Model
Trigger Model	Trigger Model
Device Template	Device Template

The UI is identical to the tenant side (same tables, same edit forms). For operation details please refer to the tenant-side docs linked above. This page only covers the admin-specific differences.

Key Differences

1. Cross-Tenant Visibility

The model-management lists in the System Platform have an additional tenant_code column. The admin sees models from all tenants, including PUBLIC (built-in) models. Tenant-side users only see their own models plus PUBLIC ones.

2. Promote a Tenant Model to PUBLIC

To turn a model that's been battle-tested in one tenant into a platform-wide default:

1. Open the relevant submenu (e.g. "Thing Model").
2. Click Details or Copy on a row to enter the edit form.
3. Change the tenant_code field to PUBLIC and submit.
4. The model is now visible and usable by every tenant and becomes a system-built-in resource.

3. PUBLIC Models Cannot Be Demoted

The backend enforces a guardrail: a model that is already PUBLIC cannot have its tenant_code changed back to a specific tenant. This prevents accidental "privatization" of built-in models. If a PUBLIC model truly needs to be removed, just delete it.

Typical Workflows

• A customer fine-tunes a set of water-meter / electric-meter thing models in a demo tenant → admin switches to System Platform → promotes the set to PUBLIC → when other customer tenants are provisioned, those models are immediately usable, no need to re-model.
• The mtfac team curates an official set of device templates as PUBLIC, then uses Remote Data Pull to sync them to every branch TKL deployment.