Asset Templates

Import & Export

Share templates as JSON files for reuse across organizations.

Templates can be exported as JSON files and imported into other Fleetera organizations. This is useful for sharing standardized asset definitions, creating backups, or setting up new tenants with pre-built templates.

Exporting a template

On the template detail page, click Export Template. The entire template — including its metadata, variable definitions, and child template hierarchy — is downloaded as a JSON file named [alias]-template.json.

Import format

The JSON file follows this structure:

{
  "schemaVersion": "1.0",
  "name": "Centrifugal Pump - Model X200",
  "alias": "centrifugal-pump-model-x200",
  "category": "centrifugal_pump",
  "description": "Standard centrifugal pump template with motor and seal subsystems",
  "variables": [
    {
      "key": "discharge_pressure",
      "name": "Discharge Pressure",
      "kind": "raw",
      "dataType": "Float64",
      "unitCode": "bar",
      "samplingHintMs": 1000,
      "isIndex": false,
      "description": "Pump discharge pressure"
    }
  ],
  "children": [
    {
      "schemaVersion": "1.0",
      "name": "Drive Motor",
      "alias": "drive-motor",
      "category": "motor",
      "variables": [],
      "children": []
    }
  ]
}

Required fields

FieldDescription
schemaVersionMust be "1.0"
nameTemplate display name
aliasUnique identifier (lowercase, hyphens)
categoryAsset category alias

Optional fields

FieldDescription
descriptionTemplate description
variablesArray of variable definitions
childrenArray of child templates (same structure, recursive)

Variable definition fields

FieldRequiredDescription
keyYesMachine-readable identifier in snake_case
nameYesHuman-readable label
kindYes"raw" or "derived"
dataTypeYesData type (e.g., "Float64", "Int32", "Boolean", "String")
unitCodeNoUnit of measurement (e.g., "kW", "°C", "rpm")
samplingHintMsNoSuggested sampling interval in milliseconds
isIndexNoWhether this variable is an index/identifier
descriptionNoDescription of the variable

Importing a template

On the templates list page, click Import. In the dialog, upload a JSON file by dragging and dropping or clicking to browse. Only .json files are accepted.

Before importing, the platform validates the file and shows a preview:

  • Template name
  • Number of child templates
  • Number of variable definitions
  • Any validation errors (missing required fields, invalid format)

On confirmation, the import creates:

  • The root template and all child templates recursively
  • All variable definitions on each template
  • Parent-child relationships between templates

A summary shows the total number of templates and variables created.

If a template with the same alias already exists in your organization, the import will fail with a conflict error. Rename the alias in the JSON file before re-importing.

Schema and example files

The templates list page provides two reference downloads:

  • Download Schema — the JSON schema file that defines the expected structure of a template file
  • Download Example — a sample template JSON file that you can use as a starting point

On this page