Altium NEXUS Documentation

Single Component Editing in Altium NEXUS

Created: December 3, 2020 | Updated: February 16, 2022

Parent page: Working with Components

A component is defined/edited using the Component Editor, which can operate in two modes – Single Component Editing and Batch Component Editing. The former provides a streamlined interface when defining/editing a single component. This is the default mode when creating a new component, or editing a single revision of an existing component. The latter provides the interface for defining/editing multiple components, but can be used to define/edit a single component, should you wish.

This document looks at working with the Component Editor in its Single Component Editing mode.

The Component Editor in this mode is accessed when creating/editing a component through the Components panel, or Explorer panel. It is also directly accessed by using the File » New » Component command, from the main menus.
For more information on working with the Component Editor in its Batch Component Editing mode, see Batch Component Editing.

Facilitating the Functionality

This Single Component Editing functionality is delivered through a purpose-made extension for the Component Editor – the Single Component Editor extension.

The Single Component Editor extension.
The Single Component Editor extension.

This feature is only made available, provided the Single Component Editor extension is installed as part of your Altium NEXUS installation. This extension is installed by default when installing the software, but in case of inadvertent uninstall, can be found back on the Purchased tab of the Extensions & Updates page (click on the current user control (e.g. ) at the top-right of the design space and choose Extensions and Updates from the menu).

Interface Overview

In its Single Component Editing mode, the Component Editor interface is essentially divided into four main regions, illustrated in the following image and summarized thereafter.

The Component Editor, when operating in its Single Component Editing mode, can be divided into four key regions.
The Component Editor, when operating in its Single Component Editing mode, can be divided into four key regions.

  1. Component – where you define key properties of the component, including its Name, Description, unique Id, resident Folder, Type, and reference to any Component Template as required.
  2. Models – where you add links to saved (or created on-the-fly) domain models, for use by the component.
  3. Parameters – where you craft a set of parametric data that will be applied to the component. This can include parameters from a referenced Component Template, as well as additional user-defined parameters. Links to website URLs can also be added here, as well as datasheets.
  4. Part Choices – where you can search for and add Part Choices for the component; the real world manufacturer parts that you want to be used for the design component when the board is manufactured and assembled.

Component

This region provides controls for defining the following component attributes:

  • Name – reflects the humanly-readable name given to the component. This system parameter is available and indexed when searching within the Workspace and will provide a good means to locate specific components beyond having to remember their Item ID!

    As you start typing the name, a pop-up listing of available manufacturer parts – from the Workspace's Local Part Catalog – will appear. You can select an entry to quickly define your component, with the data chosen (parameters, models, datasheets). This creation from manufacturer part search facility is also available by pressing the button at the far right side of the field. For more information, see Creating the Component from a Manufacturer Part Search.

    The field will populate with any default value for the Name system parameter that has been defined in a referenced Component Template. Also, if the component is being created from a manufacturer part search, and the Name parameter is enabled in the Use Component Data dialog, the Name field will be populated with the name from that chosen part.
  • Description – reflects the description added to the component. This system parameter is available and indexed when searching within the Workspace.

    The field will populate with any default value for the Description system parameter that has been defined in a referenced Component Template. Also, if the component is being created from a manufacturer part search, and the Description parameter is enabled in the Use Component Data dialog, the Description field will be populated with the description from that chosen part.

In addition, and by clicking the Advanced Settings control, you get access to the following:

  • Id – this field is used to determine the ID used for the saved component in the Workspace. For a new component created through the File » New » Component command or the Components panel, this field is populated in accordance with the component template defined for the component type chosen in the Create new component dialog. Where a template does not exist, or where the <Undefined> entry is chosen in the dialog, a default naming scheme is used; CMP-{00000}. For a new component created through the Explorer panel, this field is populated in accordance with the default naming scheme specified for that component's parent folder. If the parent folder has a component template attached, then defined Component Naming will be brought in from that template. The software will automatically assign the next available unique ID, based on that scheme, having scanned the entire Workspace and identifiers of existing content.

    Alternatively, you can override the auto-assigned ID for the component by entering the ID required directly in the Id field. You always have full control and final say over how the content is identified.

    This field will be read-only if the component has already been saved to the Workspace.
  • Folder – use this field to save the component to a specific folder in the target Workspace. For a new component created through the File » New » Component command or the Components panel, this field is populated in accordance with the component template defined for the component type chosen in the Create new component dialog. Where a template does not exist, or where the <Undefined> entry is chosen in the dialog, this field is blank. For a new component created through the Explorer panel, this field is populated with that component's parent folder. You have full control over where in the target Workspace a component will be stored. To manually specify a target folder, click the button to access the Choose Folder dialog. Browse to, and choose an existing folder, or create a new one on-the-fly.

    Taking the time to carefully determine the folder path for your component ensures it is saved into the correct destination folder from the outset. However, content can be easily moved to any folder in the Workspace structure once saved, if need be.
    This field will be read-only if the component has already been saved to the Workspace.
  • Template – this field provides the ability to reference a defined Component Template. Click on the field to access a listing of all Component Templates currently available in the connected Workspace (to which you are signed in). Click on an entry to create a link to the indicated (latest) revision of that Component Template. Template information will be brought into the Component Editor (Name, Description, Id naming format, Folder, Type, Models, and Parameters). For more information, see Referencing a Component Template.

  • Type – this field supports the ability to define the type of component and is a key attribute used to facilitate targeted searching of components. When browsing your own components using the Components panel, the Categories grouping for components is derived from the component type defined for each component. Click on the field to access a listing of currently defined component types from which to choose. The types are defined at the preferences level. Click the button at the right of the field to access the Data Management – Component Types page of the Preferences dialog, from where you can craft this listing to better suit your needs – either by adding new types and sub-types, or editing and removing existing types.

    It is also possible to change the component type for one or more components after saving to a completely different type, on-the-fly. In the Components panel or Explorer panel, select the component(s) that you want to change, then right-click and choose the Operations » Change Component Type command from the context menu. The Choose component type dialog will appear from which you can select the new component type.
    The field will populate with any default value for the ComponentType parameter that has been defined in a referenced Component Template, or with the component type selected through the Create new component dialog, which appears when you attempt to create a new component using the File » New » Component command.

Models

This region of the editor is used to add links to saved (or created on-the-fly) domain models, for use by the component.

At the most basic level, a component used in board design requires representation in the schematic and PCB editing domains. It therefore needs schematic symbol and PCB footprint models.

The Models region, providing the controls to define the models required to represent the component in the Schematic, PCB, and Simulation domains.
The Models region, providing the controls to define the models required to represent the component in the Schematic, PCB, and Simulation domains.

Use the following collapsible sections to learn more about working with models.

The links to required models for the component can be defined in a variety of ways:

  • Selecting an existing model. Click the drop-down icon on the button below the model type, and choose Existing from the associated menu. Choose the model of the required type through the subsequent dialog. Note that the Revision State field, below the preview of the model, will reflect the current lifecycle state of the chosen revision of the model, and whether it is the latest revision (Up to date) or not (Out of date).

    Note that the button is dynamic and will reflect the last command (from its menu) that was used.

    Dialog-based addition of an existing model.
    Dialog-based addition of an existing model.

  • Drag and drop a model directly from the Explorer panel.

    Add one, or multiple models, through drag and drop from the Explorer panel.
    Add one, or multiple models, through drag and drop from the Explorer panel.

  • Create a new model manually. Click the drop-down icon on the button below the model type, and choose New from the associated menu. The corresponding temporary editor for that model type will open, ready for you to define the model. The model will initially be named using the name of the component currently being defined, model type, and model number – change this as required. Once defined, just save and close the editor – the model will appear linked back in the Models region. Note that the Revision State field, below the preview of the model, will show Not released. Upon save of the component, any newly defined model will automatically be saved to the Workspace also, into the initial revision of a new Item.

    Example manual creation of a new model for a component, in this case, a schematic symbol. The symbol was initially named Diode_Schottky – after the parent component – but subsequently renamed to Diode_Schottky_Red. Note that the model is not saved to the Workspace until the parent component is saved.
    Example manual creation of a new model for a component, in this case, a schematic symbol. The symbol was initially named Diode_Schottky – after the parent component – but subsequently renamed to Diode_Schottky_Red. Note that the model is not saved to the Workspace until the parent component is saved.

  • Create a new model using a Wizard (for symbol and footprint only). Click the drop-down icon on the button below the model type, and choose Wizard from the associated menu. The process is similar for these two model types, just using a different Wizard:
    1. For a symbol, the Symbol Wizard will appear. For a footprint, the IPC Compliant Footprint Wizard will appear. Use the respective wizard to define the model as required.
    2. After finishing in the wizard, the corresponding temporary editor for the model type will open, with the resulting model – generated from the wizard – loaded. A generated symbol will initially be named using the name of the component currently being defined – change this as required. A generated footprint model will take the naming defined for it in the Wizard.
    3. Make any additional changes as required, then save and close the editor – the model will appear linked back in the Models region. Note that the Revision State field, below the preview of the model, will show Not released.
    4. Upon the save of the component, any newly defined model will automatically be saved to the Workspace also, into the initial revision of a new Item.

    Example using the Symbol Wizard to create the required symbol for the component being created/edited. Hover over the image to see an example of using the IPC Compliant Footprint Wizard to create a footprint model for the component.
    Example using the Symbol Wizard to create the required symbol for the component being created/edited. Hover over the image to see an example of using the IPC Compliant Footprint Wizard to create a footprint model for the component.

  • From a template. If the component references a component template, all models that are defined (as dedicated parameters) in that template (SCHLIB and PCBLIB(s) only), will be brought in to the Models region. For more information, see Referencing a Component Template.
  • From a Manufacturer Part Search. If the component is being created from a manufacturer part search, and the model options are enabled in the Use Component Data dialog, selected models defined for that chosen part will be brought in. For more information, see Creating the Component from a Manufacturer Part Search.

Storage of Newly-created Models

You can define default target folders in which newly-created models should be created, or override those to specify a different target folder, should you need – affording you greater control and flexibility over how your models are created and stored.

Defining Default Target Folders

Default release target folders for newly-created models are defined on the Admin – Settings – Vault – Components page of the NEXUS Server Workspace's browser interface.

To change a default folder, click the Select button. The Explorer window will appear with which to choose the desired new default target release folder for that model type. Once chosen, click OK to close the window and return to the Components page, with the applicable field updated with the new folder path.

If any changes to the default release target folders are made, ensure to click the Save button at the top-right of the page.

Overriding the Default Target Folder

Newly-created models – when creating components through the Component Editor in its Single Component Editing mode – will be stored in the Workspace according to the defined default target release folders, as described previously. However, should you wish, you can override the default by nominating a specific folder in which to store the created model. To do so, click on the control – at the top-right of the model's preview – and choose the Select Target Folder entry from the menu. The Choose Folder dialog will appear (essentially a trimmed incarnation of the Explorer panel). Use this to choose the required target folder and click OK.

Override the default release folder for a model type by choosing a different one.
Override the default release folder for a model type by choosing a different one.

While the component is still unreleased, the chosen target folder will be presented, textually, above the model's preview window – a useful reminder of where the new model will be found!

While the component remains unreleased, the chosen folder for the model is presented.
While the component remains unreleased, the chosen folder for the model is presented.

To modify a model that is currently being used (referenced) by the component, click the control at the top-right of its preview. The corresponding temporary editor for that model type will open, ready for you to make changes to the model as required. Once ready, just save and close the editor – the modified model will appear linked back in the Models region. Upon saving of the component to the Workspace, the modified model will automatically be saved to the Workspace also, into the next revision of its parent Item.

If the model is referenced by multiple components, a dialog will appear alerting you to this, and offering you various choices. You can create a copy of the model (clone it) so that the change affects only the current component. Or you can continue with editing this shared model, and update the other components that reference it later. Or you can simply cancel out of the editing process.

An example of editing an existing model that is being referenced by the component.
An example of editing an existing model that is being referenced by the component.

To change a model, click on the control – at the top-right of the model's preview – and choose the Select Model entry from the menu. Use the subsequent dialog that appears to browse for and choose, a different model, or a different revision of that same model.

An example of switching the symbol used to represent a component.
An example of switching the symbol used to represent a component.

To clone an existing referenced domain model, click on the control – at the top-right of the model's preview – and choose the Clone entry from the menu. The corresponding temporary editor for that model type will open, with the cloned model ready for you to make changes as required (including changing the new model's name, to distinguish it). Once ready, just save and close the editor – the cloned model will appear linked back in the Models region. Note that the Revision State field, below the preview of the model, will show Not released. Upon saving of the component to the Workspace, the cloned model will automatically be saved to the Workspace also, into the initial revision of a new Item.

Example of cloning an existing model – allowing you to quickly create a new model on-the-fly, and have your component use it, whilst not having to reinvent the wheel to do so.
Example of cloning an existing model – allowing you to quickly create a new model on-the-fly, and have your component use it, whilst not having to reinvent the wheel to do so.

To quickly browse to the model in the Explorer panel, click on the control – at the top-right of the model's preview – and choose the Show in Explorer entry from the menu. The panel will present (or be focused) with that model (and revision thereof) displayed.

Example browsing to the revision of the model in the Explorer panel.
Example browsing to the revision of the model in the Explorer panel.

When you attempt to save a component back to the Workspace, the Component Editor runs a validation – a Component Rule Check. As part of this, if the Editor detects that a linked model is not the latest revision, this is flagged by a validation failure dialog, and the issue detailed in the Messages panel. Revision State information can be found beneath the graphical preview of the referenced revision of a model. If there is a later revision of the model available, the Revision State field will reflect this using the text Out of date, to the right of the current revision's lifecycle state. When the latest revision is being referenced, the text will be Up to date.

Detecting a model is out of date as part of the Component Editor's automatic component validation checks.
Detecting a model is out of date as part of the Component Editor's automatic component validation checks.

You have the option to cancel saving and fix the issue(s), or ignore any violation(s) and save regardless. To update the link to use the latest revision of the model, click on the control – at the top-right of the model's preview – and choose the Update to Latest entry from the menu.

While validation of the component is automatically carried out at time of saving, it can be performed at any time, manually, by running the Tools » Component Rule Check command from the main menus. For more details on what checks are involved, and their configuration, see Running a Component Rule Check.

While a component can reference a single symbol, and single simulation model, provision is made for referencing any number of footprint models. This will be a welcome feature for those wishing to create components that reference 3 footprints, satisfying the IPC requirements for different density levels: L (least or minimum copper), M (most, or maximum copper), and N (nominal, or median copper). To this end, once a footprint model has been linked, the Add Footprint control will still remain available. The default footprint is the first linked, and is distinguished by the icon at the model's top-left.

You can set another footprint model to be the default model by clicking the control – at the top-right of the model's preview – and choosing the Set Default entry from the menu.

A component can reference multiple footprint models. The default footprint (highlighted in orange) is distinguished by an icon at its upper-left corner.
A component can reference multiple footprint models. The default footprint (highlighted in orange) is distinguished by an icon at its upper-left corner.

When a symbol and footprint model have both been added to the component, visual cross-probe highlighting is supported between the pins of that symbol and the corresponding pads of that footprint model. The footprint model must be displayed in 2D and cross-probing is uni-directional (pin-to-pad only).

Cross-probe highlighting between symbol pins and 2D footprint model pads for a component being edited.
Cross-probe highlighting between symbol pins and 2D footprint model pads for a component being edited.

To remove a model, click on the control – at the top-right of the model's preview – and choose the Remove entry from the menu.

To rename a model, click on the control – at the top-right of the model's preview – and choose the Rename entry from the menu. Use the subsequent Rename dialog to change the name and description as required, and to add any pertinent release notes as well.

To view and edit the pin mapping for the component – between the pins of its referenced schematic symbol and the pads/pins of referenced footprint and simulation models – click on the control (at the top-right of the model's preview) to access the Pins panel.

This functionality is not currently supported when connecting to a NEXUS Server Workspace.

Access the Pins panel, with which to define pin mapping for your component between the various design domains as required.
Access the Pins panel, with which to define pin mapping for your component between the various design domains as required.

By default, all defined models will be presented in the panel – use the control at the top-right of the panel to change this as required.

By default, the numbered pins of the symbol will be mapped to the same numbered pads/pins in the referenced footprint and simulation models. Change the mapped pad/pin targets directly by clicking on a cell of the model and entering the required value. This allows for custom pin mapping and where such custom mapping is implemented, the icon will be presented at the top-right of the domain model's preview.

For a footprint model, the default one-to-one pin-pad mapping can be changed to have one pin being connected to multiple footprint pads or any other non-aligned pin to pad number relationship. When mapping a pin to multiple pads, the mapping entries are entered using a comma-delimited numeric format (1,2,3,4, etc).

Example of mapping a single pin of a component's symbol to multiple pads of a referenced footprint model.
Example of mapping a single pin of a component's symbol to multiple pads of a referenced footprint model.

Pin-to-pad cross-probe highlighting is supported for multiple common footprint pads.
A placed component with custom pin-to-pad mapping is fully supported during design schematic-PCB synchronization, for pin and part swapping, and by the Component Pin Editor dialog. Note that schematic components show pad designators rather than pin designators, and where custom mapping has been applied the pin designator is shown in gray. The latter can be disabled by unchecking the Show Pin Designators option on the Schematic – Graphical Editing page of the Preferences dialog.

Things to consider when mapping pins:

  • You can not leave a target model pad/pin cell empty – it must be mapped.
  • You can not enter a model pad/pin number that does not exist on that model.
  • You can not assign a model pad/pin to more than one symbol pin.

Any of these conditions will result in the icon appearing in the cell – remedy the issue accordingly.

Parameters

This region of the editor is used to add parametric data to the component. Three types of parameter can be manually added here:

  •  Parameter – a standard, user-defined parameter.
  •  Link – a URL link to the page of a website, for example a manufacturer's website, or an online datasheet.
  •  Datasheet – providing a link to a datasheet (in any format) that has been uploaded to the Workspace and is referenced by the component.

The Parameters region, providing the controls for adding parametric data to the component.
The Parameters region, providing the controls for adding parametric data to the component.

Any number of these parameter types may be added as required. To do so, click the drop-down part of the button at the bottom of the region, then choose the relevant entry from the menu. A new parameter will be added to the list as follows:

  • Parameter – will be added below the currently selected entry in the list. The name will be in the default format Parameter n, click on the Name field to change this as required. Click on the Value field and type the value as required.
  • Link – will be added at the bottom of the list. Click on the Name field and enter the required name. This will be presented on the right-click References sub-menu, when accessed for a placed instance of the component on a schematic sheet. Type (or paste) the URL for the target page into the Value field. This will become a hyperlink, with which to access the target.
  • Datasheet – a standard Windows Open dialog will appear, with which to browse to, and select, the required datasheet. Multiple datasheets can be added simultaneously through this dialog. Each datasheet will be added at the bottom of the list. The Name will initially be that of the file itself, and is presented in the Explorer panel, and also in the References sub-menu for a component, after it is placed on a schematic sheet. Change this to a more suitable caption as required. The Value will be the file, in terms of its name, format, and size on disk. This will be a hyperlink, with which to quickly access the datasheet.
Clicking the button directly (not accessing its drop-down menu) will add a standard Parameter. To remove a parameter, select it in the list (multiple parameters can be selected for removal) and click the button.
The Parameters region can also be populated with parametric data from a part found by conducting a Manufacturer Part Search. For more details, see Creating the Component from a Manufacturer Part Search.

Attaching Datasheets through Drag and Drop

In addition to the manual attachment through the Open dialog mentioned in the previous section, you can also attach one or more datasheets to the component in the following ways:

  • By dragging and dropping from Windows File Explorer to anywhere within the Parameters region.

    Example demonstrating attachment of datasheets from a local drive, and then editing the local caption for the main datasheet.
    Example demonstrating attachment of datasheets from a local drive, and then editing the local caption for the main datasheet.

  • By dragging and dropping a datasheet link from a web page in an external web browser, to anywhere within the Parameters region.

    Example demonstrating attachment of a datasheet from a web page.
    Example demonstrating attachment of a datasheet from a web page.

Template Parameters

In addition, if the component references a Component Template, then any parameters defined in that template will be brought in, and added to the Parameters region.

Example parameters from a referenced Component Template.
Example parameters from a referenced Component Template.

Things to note:

  • A standard template parameter (not marked as Read-only or Required) is distinguished in the Parameters region by use of the icon.
  • A template parameter marked as Read-only is distinguished in the Parameters region by use of the icon.
  • A template parameter marked as Required is distinguished in the Parameters region by use of the icon.
  • An existing user-defined parameter that has the same name as a parameter in the linked Component Template, will be replaced with the template version. Any existing value for that parameter will be kept (and not overwritten with the value in the template).
  • The value fields for template-based parameters that have been marked as read-only, will be non-editable. For all other template-based parameters, that have not been marked as read-only, you are free to change the values as required.
  • If a template-based parameter has been marked as Required, but has not been given a value in the template, its value field will contain the icon, alerting you to the fact that a value is required for this parameter. You will not be able to save a component to the Workspace until values are defined for all required parameters.
  • If a parameter in the template has a description defined for it, then the Description column will be presented in the Parameters region of the Component Editor accordingly.

Template Parameters cannot be removed.

Support for Unit-aware Component Parameter Data Types

The Component Editor supports unit-aware component parameter data types that are defined within a referenced Component Template. You can enter a parameter's value directly into the applicable field using a range of formats - such as 2.2k, 2k2, 4M, 2.5GHz – with the Workspace engineered with the requisite smarts to recognize the numerical value behind those entries.

This feature of a component template facilitates targeted searching through the Workspace's Search facility – a facility that not only allows you to search by component type, but allows you to search smarter, with range searches. Using the power of unit-aware component parameters, you can quickly define a search, for example, to find all capacitors with a capacitance between 47uF and 220uF.

Unit-aware parameters are also used for smart filtering when searching through your own components using the Components panel.
Unit-aware data types for component parameters can only be defined through a component template.

Component parameters from a referenced component template that have unit-aware data types.
Component parameters from a referenced component template that have unit-aware data types.

When entering a value for a component parameter that uses a unit-aware data type, the following are things to consider:

  • You can enter the value in a range of different formats:
    • Numerical value only (e.g. 10). Note that if the data type has a unit, this will be applied automatically. Those types with units, have the unit in brackets after their name.
    • Numerical value in scientific notation (e.g. 1e10, 1E6).
    • Numerical value and units (e.g. 10F).
    • Numerical value with prefix (e.g. 10k). The appropriate unit will automatically be added (where applicable).
    • Numerical value with prefix and units (e.g. 10kF).
    • Numerical value with prefix in typical engineering format (e.g. for a resistance: 2k2, 2K2, 10r2, 10R2). The value will automatically be normalized accordingly (e.g. 2K2 will become 2.2k).
  • You can enter prefix and/or units with or without a space after the numerical value (e.g., 10uF, or 10 uF). The space will be automatically stripped.
Note that engineering abbreviations are case insensitive, so entering 2k2 is the same as entering 2K2, and entering 100R is the same as entering 100r. The only exception is M (Mega) and m (milli).

The following unit-aware data types are supported:

Most data types have a unit (shown in brackets in the Component Template). This will be applied if no unit is specified when entering a value for a parameter.
  • Volt(V)
  • Ampere(A)
  • Ohm
  • Farad(F)
  • Henry(H)
  • Watts(W)
  • Hertz(Hz)
  • Celsius(C)
  • Decibel(dB)
  • Percent(%)
  • Metre(m)
  • Gram(g)
  • Second(s)

The following table lists the prefixes that are supported when entering a value for a unit-aware parameter type.

Prefix Term Value (Scientific) Value (Normal)
T Tera 1 x 1012 1,000,000,000,000
G Giga 1 x 109 1,000,000,000
M Mega 1 x 106 1,000,000
k kilo 1 x 103 1,000
m milli 1 x 10-3 1 / 1,000
u micro 1 x 10-6 1 / 1,000,000
n nano 1 x 10-9 1 / 1,000,000,000
p pico 1 x 10-12 1 / 1,000,000,000,000
f femto 1 x 10-15 1 / 1,000,000,000,000,000
Note that the use of some, or all prefixes may not be applicable, depending on the parameter type. For example, no prefix is valid for a Percentage. The software will alert you to any invalid use of prefixes.

When a unit-aware data type is used for a component parameter, the entered value is validated against the specified data type. This ensures that the correct measurement unit for that data type is being used, where the unit is entered. For example, a parameter of type Celsius cannot have a value of 10V!

In the Component Editor, entering an invalid value for a parameter will cause a dialog to appear, alerting you to the fact that the entry is not a valid value. This is also the case when copying and pasting a value between cells. Clicking OK in the dialog will revert the value back to its previous entry.

Data validation – the Component Editor has the smarts to alert you to a mismatch between the value entered for a unit-aware parameter, and its data type.
Data validation – the Component Editor has the smarts to alert you to a mismatch between the value entered for a unit-aware parameter, and its data type.

Item Level Parameters

Altium NEXUS, in conjunction with a connected Workspace, supports the concept of Item level parameters. These are parameters that are added to the parent Component Item, and available to all its released revisions, without having to re-release the Item into a new revision to pick up those parameters. As such, they are often referred to as Dynamic Parameters. This feature allows for component updates without having to create new component revisions, which in turn would affect related designs in which those components are used. An example might be a cost parameter change – applied dynamically on-the-fly as it were.

This functionality is available when instigated through a connected enterprise system instance, or through use of the CSV uploader. When defining parametric attributes through the relevant configuration file, you can determine whether a parameter should be pushed to the item, or the revision, with the latter being the default. For more information, see PLM Integration.

Item-level, or dynamic parameters can be viewed when editing a Component Item revision. Note that they are only visible when using the Component Editor in its Single Component Editing mode.

Example Item level parameter that has been added to a Component Item, and available to its revisions.
Example Item level parameter that has been added to a Component Item, and available to its revisions.

Note that such parameters have a different icon – – to distinguish them in the Parameters region of the Editor. Hovering over the icon will display the text Dynamic.

Part Choices

This region of the editor is used to specify one or more Part Choices for the component – the 'allowed' manufacturer parts that can be used to implement the component on the assembled board. The actual supply chain intelligence – comprising Manufacturer (and part number), Supplier (and part number), Description, Pricing and Availability – is sourced from the Workspace's local Part Catalog and the relevant Part Source.

Each Workspace has its own dedicated Part Catalog. This is a local part catalog database, dedicated to the management and tracking of manufacturer parts and their associated supplier parts. The local Part Catalog stores items representative of actual Manufacturer Parts, along with one or more items representative of Supplier Parts – the incarnations of those Manufacturer Parts, as sold by the Suppliers/Vendors. Each Supplier Part is a reference to an item in a parts database – either the aggregate parts database of the Altium Parts Provider (the default Part Source which itself interfaces to, and gathers the parts from, enabled Suppliers), or a linked local parts database (a Part Source configured as a Custom Database Parts Provider). Enable required Suppliers and determine Location/Currency ranges for the Altium Parts Provider within the Part Providers area of the Workspace's browser interface. While you remain connected to your Workspace from Altium NEXUS, the Altium Parts Options region – on the Data Management – Parts Providers page of the Preferences dialog – becomes read-only and adopts those settings defined for the Workspace. For more information on managing the Altium Parts Provider part source for your NEXUS Server Workspace, see Supply Chain Management.

Example Part Choices list for a component being defined, containing a single manufacturer part.
Example Part Choices list for a component being defined, containing a single manufacturer part.

A manufacturer part can be added to the Part Choices list for the component in two ways:

To manually add a part choice, click the button at the bottom of the region. The Add Part Choices dialog will appear – search for the required manufacturer part, select a part, then click the OK button. Click the SPNs entry for a manufacturer part – Supplier Part Numbers – to see the available suppliers of that part, and assess whether you are making the right part choice, based on availability, pricing, etc.

Use the following Use Component Data dialog to decide how you want to use the result, should you wish to replace any or all existing data or, to just have the part added as a part choice, click Cancel.
Search results in the dialog are by Manufacturer Part, with the associated SPN entries reflective of the enabled vendors supplying that part. When you select a part, it is the manufacturer part that is added to the Part Choices list. And by using the manufacturer part, and not a specific vendor/supplier, you get a single Part Choice that will bring with it all solutions based on the suppliers vending that part (and who are available for use through your Workspace).

Making a manual part choice – use the Add Part Choices dialog to search for the required manufacturer part, select its entry and click OK.
Making a manual part choice – use the Add Part Choices dialog to search for the required manufacturer part, select its entry and click OK.

To remove a part choice, select it in the list, then click the button.

A Part Choice contains various pieces of information, as summarized in the following image, and detailed thereafter.

The 'anatomy' of a Part Choice – the entry can be broken down into 9 key pieces of information.
The 'anatomy' of a Part Choice – the entry can be broken down into 9 key pieces of information.

  1. Part Image.
  2. Manufacturer Name and Manufacturer Part Number. This is a clickable link to the Octopart website, providing detailed information on that manufacturer part.
  3. Description.
  4. Stock. This entry displays the total sum of the stock available from the suppliers enabled as part of the Altium Parts Provider source for your Workspace.
  5. Median unit price. This entry will be displayed in red text if there are no prices, or the price = 0.
  6. Manufacturer Lifecycle Bar. Hover over the bar for an informative tool-tip. This can appear in one of four states:
    • White/Gray = Default, unknown or no information
    • Green = New or Volume Production states
    • Orange = Not Recommended for New Design
    • Red = Obsolete or EOL
    The manufacturer lifecycle status is designed to be used as an indicator, for a number of reasons:
    1. Altium maintains a database of many millions of components, produced by thousands of component manufacturers. Since there is no single, consistent method used by those manufacturers to reflect a component's lifecycle state, the status is based on information aggregated from manufacturers, global distributors and global sales analysis.
    2. A part is only reported as EOL or Obsolete when there is at least one authorized distributor or manufacturer that has confirmed this status.
    3. Determining the Not Recommended for New Design status is more complex. Manufacturers sometimes just report if a part is active or not, and may not give advance warning that a part is to be discontinued or replaced. Therefore this lifecycle status does not always concur with the status provided by the manufacturer. The status algorithm uses various information, including real time and historical stock availability from all distributors, to try to determine the availability of the part. Parts which have consistently poor availability (when they have been generally available in the past), or cannot be sourced over a period of time after having previously having good availability, will eventually be flagged as Not Recommended for New Design (if they are not already EOL or Obsolete).
    4. The idea of the lifecycle status indicator is to provide simple-to-understand information that helps you to make more informed decisions about a part, by highlighting those parts which may be problematic. However, due to the sheer volume of data and number of components that are managed, there is always a chance that the Altium status lags behind the instantaneous manufacturer status, and is therefore not up-to-date. It is not possible for Altium to guarantee the accuracy of the lifecycle status, it is recommended that if there is any doubt that you double-check with the manufacturer for authorized lifecycle information.
  7. Datasheet. Click the button to open the manufacturer's datasheet for the part. All datasheets are hosted on the Ciiva website.
  8. SPNs (Supplier Part Numbers). Indicates the number of suppliers (for those enabled as part of your Workspace's Altium Parts Provider source) who can deliver this part. Click the link to display detailed supply chain information about the suppliers that carry that part, ordered by availability and price. Each Supplier's details about that part are presented on a tile with a colored banner. Details about the icons and information in each tile is given below.
  9. User Rank. If multiple manufacturer parts are available – multiple part choices made for the component and therefore multiple solutions when using ActiveBOM (and a BomDoc) – the solutions are automatically ranked from highest to lowest, based on the part's availability, price and manufacturer lifecycle state. If you prefer to use a lower-ranked solution, for example to use a specific manufacturer, you can override the automatic ranking by defining a User Rank, using the star feature. Click on the number of stars required, to increase or decrease the ranking level of that particular part choice. To remove ranking, click the control to the right of the stars.

Understanding the Supplier Tile

There is a large amount of information presented in each SPN tile. Hover the cursor over an icon or detail to display a tooltip with more information.

The SPN tile includes detailed information about

the part's availability from that specific supplier.
The SPN tile includes detailed information about
the part's availability from that specific supplier.

  1. Tile banner showing the supplier name where the banner color indicates:
    • Green = Best choice
    • Orange = Acceptable
    • Red = Risky
  2. Supplier part number (links to that part on the supplier's website).
  3. Country code for the supplier location (ISO alpha 2).
  4. Part Source (typically the Altium Parts Provider) and Last update; the color indicates:
    • Light Gray = Default, updated less than one week ago
    • Orange = 1 week < last update < month ago
    • Red = last update > 1 month ago
  5. Stock quantity; red if no stock available.
  6. Unit price, red if no price available. Unit price includes currency icon; currency is determined by the location of the supplier.
  7. Packaging of supplied parts (e.g. Tr = Tray).
  8. Available price breaks, with Minimum Order Quantities.

Providing a boost to creation of a component, Altium NEXUS supports the ability to search for a real-world manufacturer part, courtesy of Manufacturer Part Search functionality, and then add that part (or a portion of its data) into the Component Editor. In this way, you can quickly define a new component for addition to your Workspace, without having to craft that component from scratch. There is no having to 'reinvent the wheel' as it were, since all data for that part – its name, description, parameters, datasheets, part choices and any defined models – can be brought in.

The feature itself can be accessed in a number of ways – click on a collapsible section to explore further.

In each case, the Use Component Data dialog will open providing controls for selecting data you would like to apply to the component being currently created/edited: name, description, parameters, models, and datasheets. If the component has no data yet defined, all data available for that part will be enabled by default in this dialog for loaded into the component. If the component is partially defined with its Name, Description and/or Symbol, appropriate options will be disabled by default in the dialog – providing you controls for replacing them with data from the selected part though.

Use the Use Component Data dialog for selecting data to be added to the component from the chosen part.
Use the Use Component Data dialog for selecting data to be added to the component from the chosen part.

The Name field gives two methods of access to the Manufacturer Part Search feature:

  • Typing Directly – as you start typing in the Name field, a pop-up listing of matching manufacturer parts is presented (with manufacturer indicated to the right). Select a part to use.

    Start typing the name of the required manufacturer part – and select the relevant entry from the convenient pop-up listing. The image shows all data for that part being brought into the Component Editor.
    Start typing the name of the required manufacturer part – and select the relevant entry from the convenient pop-up listing. The image shows all data for that part being brought into the Component Editor.

  • Using the Manufacturer Part Search dialog – click the button at the far right of the field to access the Manufacturer Part Search dialog. Search for the required manufacturer part, select an entry, then click the OK button.

    The dialog is used in the same way as the Manufacturer Search panel, or the Add Part Choices dialog. Refer to those linked pages for more information.
    Search results in the dialog are by Manufacturer Part, with the associated SPN entries reflective of the enabled vendors supplying that part. When you select a part, it is the manufacturer part that is used to create the new component. And in terms of Part Choice, by creating based on the manufacturer part, and not a specific vendor/supplier, you get a single Part Choice that will bring with it all solutions based on the suppliers vending that part (and who are available for use through your Workspace). Parameters are imported in accordance with defined Parameter Import Options – configured on the Data Management – Parts Providers page of the Preferences dialog.

    Use the Manufacturer Part Search dialog to find the required manufacturer part, select it, then click OK. The image shows all data for that part being brought into the Component Editor.
    Use the Manufacturer Part Search dialog to find the required manufacturer part, select it, then click OK. The image shows all data for that part being brought into the Component Editor.

The Manufacturer Part Search feature can be accessed by choosing the Tools » Create from Part Search command, from the main menus. Alternatively, use the Shift+Ctrl+M keyboard shortcut. The Manufacturer Part Search dialog will appear. Search for the required part, select an entry, then click the OK button.

The dialog is used in the same way as the Manufacturer Search panel, or the Add Part Choices dialog. Refer to those linked pages for more information.
Search results in the dialog are by Manufacturer Part, with the associated SPN entries reflective of the enabled vendors supplying that part. When you select a part, it is the manufacturer part that is used to create the new component. And in terms of Part Choice, by creating based on the manufacturer part, and not a specific vendor/supplier, you get a single Part Choice that will bring with it all solutions based on the suppliers vending that part (and who are available for use through your Workspace). Parameters are imported in accordance with defined Parameter Import Options – configured on the Data Management – Parts Providers page of the Preferences dialog.

Use the Manufacturer Part Search dialog to find the required manufacturer part, select it, then click OK. The image shows all data for that part being brought into the Component Editor.
Use the Manufacturer Part Search dialog to find the required manufacturer part, select it, then click OK. The image shows all data for that part being brought into the Component Editor.

A part can also effectively be chosen, and its data loaded, when manually adding a Part Choice. After clicking the button at the bottom of the Part Choices region, the Add Part Choices dialog will appear. This is very similar to the Manufacturer Part Search dialog. Search for the required manufacturer part, select an entry, then click the OK button.

Search for a Part Choice, and bring all the data associated with that part into the Component Editor, effectively defining the component.
Search for a Part Choice, and bring all the data associated with that part into the Component Editor, effectively defining the component.

Running a Component Rule Check

Before saving a Workspace Library component defined/edited in the Component Editor to the connected Workspace and making the component be available for use in designs, it is essential to make sure that this component meets the requirements in accordance with the configured settings. The Component Editor runs a validation – a Component Rule Check – when you attempt to save a component back to the Workspace or run this feature manually.

To learn more about component validation, see the Verifying a Component page.

A Word About Linked Simulation Models

Related page: Simulation Model

As with symbol and footprint models, a component can also reference a revision of a simulation model. Adding a model link of this type is similar to adding a symbol and footprint, with the exception of there being no Wizard-based creation option, so refer back to the previous sections for information on that. Here, we look at including component-level simulation parameters, and also configuration of pin mapping.

Adding Component-Level Simulation Parameters

When using a simulation model for a component in a design, parameters specific to that model can be specified at two different levels:

  • Model-Level Parameter – specified as part of the simulation model definition itself (in the SimModel file), and saved with that definition into a revision of the linked simulation model.
  • Component-Level Parameter – specified as part of the component definition (here in the Component Editor), and saved with that definition into a revision of the linked component.
Component-level parameters are used for parameters that are shared between multiple models or where the designer wants to make such a parameter visible/editable on the schematic (e.g. value, frequency, etc).

Parameters are added at the component-level in the Parameters region of the Component Editor. It is important to note that the naming of parameters must be the same as those parameters defined at the model-level. To see the model-level parameters, and therefore which parameters can be added at the component-level (and their names!), click the View Parameters control, at the bottom of the Simulation model's preview window.

View the model-level parameters for a simulation model, to see which parameters can be added at the component-level – and how they are named!
View the model-level parameters for a simulation model, to see which parameters can be added at the component-level – and how they are named!

Armed with the available model-level parameters, you can now proceed to add any of those same parameters at the component-level. To do so, click the button at the bottom of the Parameters region. A new parameter entry will be added to the list. Change the name as required – remembering to match exactly the name of the corresponding model-level parameter.

Add sim-related parameters at the component-level. Notice that one parameter is already available – Area Factor – courtesy of a referenced Component Template.
Add sim-related parameters at the component-level. Notice that one parameter is already available – Area Factor – courtesy of a referenced Component Template.

When an instance of the saved component is placed in a design, a simulation parameter can have a different value at the component-level, to that for the same parameter at the model-level. When the netlist is generated, the component-level parameter will have priority.
For some of the built-in SPICE3f5 models, entering a value for a parameter at the component-level will override a related parameter defined in a linked model file (*.mdl). For a semiconductor capacitor, for example, specifying a value for the component-level Width parameter will override any value specified for the DEFW parameter in the associated model file. If a parameter is specified at the component-level for a subcircuit model, that value will override the value defined for it in the linked subcircuit file (*.ckt).

Pin Mapping

Once the link to the required simulation model has been chosen, you need to ensure that the pins of the component – when represented in the schematic domain – are correctly mapped to the pins of the simulation model. Where this is performed depends on the current mode of the Component Editor:

  • Single Component Editing mode – mapping is performed using the Pins panel. See Edit Pin Mapping for more detail.
  • Batch Component Editing mode – mapping is performed using the Pin Mapping dialog. See below for detail.

Once you have switched the Component Editor to its Batch Component Editing mode, mapping is performed in the Pin Mapping dialog, accessed by right-clicking on the component definition's SIM model entry and choosing Operations » Edit Pin Mapping from the context menu. For each schematic pin, use the available drop-down to change the associated Model Pin entry accordingly. If the device is multi-part, be sure to check the mapping for each part. Once finished, you can switch back to Single Component Editing mode (Tools » Switch to Single Component Editor), or proceed to saving from within the Batch Component Editing mode.

Ensuring correct schematic pin-to-model pin mapping.
Ensuring correct schematic pin-to-model pin mapping.

For a multi-part component, the ability to exclude a part from the simulation is also determined through the Pin Mapping dialog.
For the built-in SPICE3f5 and supported PSpice models, the function of each of the pins in a model can be found in the general form section for that model, in the SPICE 3f5 user manual. For subcircuit models, the manufacturer will typically insert comments for each pin of the model, describing that pin's function. If no commenting is evident, then the pinout of the model will typically be that of the physical device itself. Consult the datasheet for the device in this case.
Found an issue with this document? Highlight the area, then use Ctrl+Enter to report it.

Contact Us

Contact our corporate or local offices directly.

We're sorry to hear the article wasn't helpful to you.
Could you take a moment to tell us why?
200 characters remaining
You are reporting an issue with the following selected text
and/or image within the active document: