1Overview
Supplementary assets are profile-defined additions outside the standard ADAC asset catalogue. They use their own JSON, line types and block folders but share the main creation, edit, audit and export workflows.
The receiver profile defines a local asset type that is not part of the selected base ADAC schema.
2Supplementary profile behaviour
Supplementary assets are first-class in creation and exchange, but recognition is profile-specific.
| Feature or choice | Current behaviour |
|---|---|
| Profile files | Uses SupplementaryAssets_<standard>.json, optional line types and Supplementary block folders.The package carries all resources needed by another user. |
| Feature class | The definition supplies receiver-facing class/category context.Audit and reporting can group the local type correctly. |
| Runtime import support | XML import can resolve or temporarily register unrecognised supplementary definitions and later offer to append them to the loaded profile.Incoming local types can be recovered rather than silently discarded. |
| Editing | Editable profiles can add, clone, edit and delete supplementary definitions in the Asset Library.Local catalogues can evolve without changing shipped standard data. |
3Create a receiver-specific asset
Keep the definition and every required resource inside the same profile package.
Choose a supplementary definition
Open the profile-specific list.
- Run
ADACSupplementary. - Search the Supplementary list by class or name.
- Review the selected definition before creating it.
Create compatible geometry
Follow point, line, polygon or grouped prompts.
- Place or draw the required geometry.
- Use profile-supplied blocks and line types where configured.
- Complete grouped components before opening attributes.
Set identity, attributes and save
Supplementary assets still require ADAC project context.
- Confirm ADACId and Class values.
- Apply category/global and specific prefills.
- Complete required supplementary attributes and supporting files.
- Save the asset.
4Product differences
The task is shared where possible, but selection, interface integration and model operations follow the host shown below.
Supplementary blocks, line types and geometry are created in AutoCAD from the loaded IDC package.
BricsCAD uses the equivalent profile resources and creation logic.
5Before you begin
- Load the receiver profile that contains the supplementary definition.
- Confirm the feature class and export type expected by the receiver.
- Use the Asset Library to verify geometry and required attributes.
6Troubleshooting
No supplementary assets are listed
The active profile may not contain a valid supplementary JSON or may intentionally define none. Load the receiver profile or add definitions through the Asset Library.
Audit reports Not In Profile
Run audit with the profile that owns the type, or add/correct the supplementary definition and reload that profile.
A block or line type is missing
Reimport the complete IDC profile and verify its Blocks/Supplementary and supplementary LIN resources were packaged.