Instantiating Assets

Instantiation is the process of creating assets from a template. Fleetera supports three modes: single asset, full hierarchy, and bulk creation.

Single instantiation

Single instantiation creates one asset from a template, linked to the template's latest version. Variable definitions on the template become variable instances on the new asset.

Click Instantiate on the template detail page. The wizard walks you through three steps:

1. Select a site — choose the site where the asset will be created.
2. Enter asset details — provide the asset name and alias. The alias is auto-generated from the name and validated for uniqueness in real time.
3. Review and confirm — review the summary (site, asset name, alias, template name, and category) then confirm.

The asset is created and you are navigated to the site's asset hierarchy.

Hierarchy instantiation

Hierarchy instantiation creates the entire template tree as nested assets — the parent template and all its child templates in one operation.

Click Instantiate Hierarchy on the template detail page. The wizard has four steps:

1. Select template and site — choose the template (if not pre-selected) and the target site.
2. Configure quantity — enter the number of instances to create (1 to 100).
   • Single mode (quantity = 1): you provide a name and alias for the top-level asset.
   • Bulk mode (quantity > 1): you provide a base name and configure numbering. See bulk creation below.
3. Preview and customize — review the hierarchy tree for each instance. For each node you can:
   • Include or exclude optional child templates (required children are always included)
   • Edit the name and alias
   • Check for alias conflicts (highlighted in red)
4. Review and confirm — verify the summary (number of instances, total asset count, template, and site) and confirm.

Naming conventions

During hierarchy instantiation, child assets are named automatically:

• Child name: the child template's default name, or the child template's own name if no default is set
• Child alias: derived from the parent alias and child template alias (e.g., pump-001-drive-motor)

You can override any name or alias in the preview step.

Bulk creation

When creating more than one instance, the bulk mode lets you configure a naming pattern:

The preview shows the first few generated names so you can verify the pattern before proceeding.

For example, with base name "WTG", starting from 1, and zero padding enabled:

WTG-01
├── Generator
├── Gearbox
└── Ambient System
WTG-02
├── Generator
├── Gearbox
└── Ambient System
WTG-03
├── ...

Each instance can be individually customized in the preview step if needed.

Alias validation

Before creation, the platform validates all aliases across the entire batch:

• Each alias must be unique within its parent
• Aliases must follow the standard format (lowercase, hyphens, alphanumeric)
• Conflicts are highlighted in red in the preview

The submit button is disabled until all alias conflicts are resolved.

What gets created

For each instantiated asset:

• The asset is created and linked to the template's latest version
• All variable definitions from the template version become variable instances on the asset
• The full hierarchy of child templates becomes nested sub-assets
• Each sub-asset gets its own variable instances from its respective template