Import & Export
Asset Manager supports bulk export and import of your entire asset inventory as JSON, as well as a PDF import workflow for populating assets from CONF-JIRA style documents.
Exporting Assets
Export produces a full JSON backup of all Asset Manager data, including:
- All assets and their property values
- All asset types and property definitions
- All parent-child links
This is useful for backups, migrating data between workspaces, or inspecting your inventory programmatically.
To export, use the export option from the Asset Manager settings or API. The result is a single JSON file.
Importing Assets
To import, upload a previously exported JSON backup file. VSEC will restore the full asset structure as it existed at the time of the export.
PDF Import
The PDF import workflow lets you create a Vehicle + Component asset structure from a CONF-JIRA style product document.
How It Works
VSEC parses the PDF for a set of known fields and uses them to build a proposed asset tree:
| PDF Field | Maps To |
|---|---|
| Vehicle Line | Vehicle asset name + Vehicle Line property |
| Initial / Lead Model Year | Vehicle asset name + Model Year property |
| Project Name | Product ID property on both Vehicle and Component |
| ECU CS.##### (line) | Component asset name |
The result is a two-level hierarchy:
Vehicle: <Vehicle Line> <Model Year>
└── Component: <ECU name>Both assets are pre-populated with the extracted property values.
Re-importing
If you import a PDF for a vehicle that already exists (matched by Vehicle Line + Model Year), VSEC detects the existing asset and updates it rather than creating a duplicate. The same deduplication applies to components linked to that vehicle.
After Import
After the PDF is parsed, a proposed tree is presented for your review. You can edit the names and properties before confirming. Once applied:
- The assets are created (or updated) in your inventory
- The original PDF is automatically attached to the Vehicle asset as a file attachment