Creating Assets

Click Create Asset in the top-right corner of the Asset Manager page to open the asset creation dialog. The dialog has three tabs depending on how you want to create the asset:

• Manual Creation — fill out the form yourself
• Import — upload a PDF or JSON file, or paste a JSON payload
• Generate — have VSEC create an asset from context and/or your own documents (only shown when an Intelligence provider is active)

A Team selector sits just below the tabs and is always visible — pick the team the new asset should belong to before submitting from any tab.

For Manual and Generate, you also fill in:

• Asset Name — the display name for the asset (e.g. “Compact A 2026”, “Telematics ECU”)
• Asset Type — the type this asset belongs to (e.g. Vehicle, Component, or any custom type)

Manual Creation

Select the Manual Creation tab to fill in properties directly.

Once you select an asset type, the properties associated with that type appear as editable fields. Property input controls vary by data type:

After filling in any properties you want to set upfront, click Create Asset. You can always edit properties later from the asset detail page.

Import

Select the Import tab to bring in assets from an external payload. This is the fastest way to add a vehicle + component tree from an existing document or from another system.

Two import methods are available:

Upload a File

Click Upload file and pick a .pdf or .json file. PDFs (for example, CONF-JIRA style product documents) are parsed automatically into a vehicle + component asset tree. JSON files must match the enrichment import schema.

Paste JSON

Click Paste JSON and paste a JSON payload into the text area. The payload must contain an assets array with at least one asset, and typically looks like:

{
  "source": "...",
  "provider": "...",
  "assets": [ ... ]
}

If the JSON is invalid or missing assets, the dialog shows an inline error.

After Submitting

After you click Import, the payload is stored for review immediately — the asset appears in your list with a Ready to review status right away (the “Generating…” status applies only to AI generation). Click Review from the asset row (or the Review button in All Assets) to accept or discard the proposed structure. Export files with multiple root assets are reviewed as one bundled tree, so all nested sub-assets stay visible together.

Generate

Select the Generate tab — labeled with a “(preview)” suffix — to have VSEC create an asset for you.

To generate an asset:

1. Enter the asset name and select a type (required, same as manual creation)
2. Optionally click Attach files (diagrams, specs, ICDs…) to upload supporting documents
3. Fill in the Context field with notes about the asset — e.g. “This is the central gateway ECU supplied by Acme; it bridges the powertrain and infotainment CAN buses…”. Notes and an attached file are each optional, but at least one of the two is required.
4. Click Generate asset

The asset itself is created right away. What happens next depends on whether you attached files:

• With files attached — VSEC drafts the whole asset structure from them: children, new types, and how they interact. A toast confirms VSEC is reading the documents and that you’ll get a notification when it’s ready to review; the asset shows a Generating… status in your list in the meantime, changing to Ready to review once the read finishes. Reviewing works like Item Definition’s document-generation review — a dialog with up to three steps (New types, Assets, Wires) — except nothing is placed on a canvas here.
• Context only (no files) — VSEC creates the asset immediately, seeds it with your context note, and starts curating it; you land directly on its Context tab, where curation fills in properties over time (see Enrichment). There’s no separate review/accept step for this path.

Reviewing Generated Suggestions

Imported assets (the Import tab above) go through a separate review: the asset’s status in the list view changes to Ready to review, and clicking Review opens an AI preview drawer showing the proposed structure — a nested tree of sub-assets for file/API imports.

Every node in the drawer is editable before you accept it: the asset name, its description, and its suggested property name/value pairs (rows can be added or removed). Nodes that match an asset already in your inventory carry an Existing chip.

Accepting & Discarding Suggestions

Each node has an Include switch — toggle off anything you don’t want created (toggling off a parent disables its children too). Then:

• Accept — creates or applies everything left included
• Discard — removes the suggestion without creating anything, after a confirmation dialog

Accepted suggestions are created as real assets and will appear in your list and tree views immediately.