Managing Vault-Based Components on a Schematic
Parent article: Vault-Based Components
Having initially placed vault-based components onto schematic sheets of a board design, there now needs to be some way of updating those component instances, with any changes to their linked source Component Items in the vault. In other words, a means by which to keep the design synchronized with the vault entities that it uses.
For example, the source definition for a Component Item may have been re-released, perhaps reflecting a change to a child model. This results in a new revision of that Component Item. The placed instance of that Item is now using an older revision and you may want to update it to use the latest revision instead. Alternatively, you may have decided to use a different component altogether, and simply need to change the existing component in the design for a new one.
This document takes a look at the methods available by which to manage the components after initial placement into a design.
Single Instance Component Change
Each placed component has a link back to the Component Item in the vault. This information can be found in the associated properties dialog for the component.
At this lowest, individual component level, the placed instance can be updated to a later revision of the same Component Item (or changed to a totally different Component Item) simply by clicking the Choose button. The Choose Item dialog will appear, with the currently linked Item (and revision thereof) focused in the source vault. Select the later revision, or browse for another Component Item to use, as required.
Effecting Batch Component Changes - the Item Manager
Related article: Managing Vault Items with the Item Manager
Individual component update is great, however it soon becomes tiresome when dealing with a more sizable number of components. For this, you need a single, centralized place from which to effect multiple changes in a batch-like manner. Enter the Item Manager (Tools » Item Manager).
The Item Manager is 'command-central' for synchronizing vault-based (or 'managed') design entities – placed on schematic sheets – with the source Items they are linked to in a vault. It automatically compiles the schematic project, detects and lists all components, flagging if they are managed or not, and then compares the Item-Revision of each managed component on the schematics against the available Revisions of that Item in the Vault. For each entity, information about the current linked Item is given, in terms of revision, lifecycle state and the source vault in which it resides.
You have full control over which of these managed entities to update, and how. Select an individual entry and choose a later revision of the linked Item to be used. Or select a group of entries that utilize the same linked Item and choose the next revision in one hit. All proposed changes are reflected back in the manager.
Once changes have been set up as required, simply generate an Engineering Change Order (ECO) and browse the actions that will be taken to implement those changes. Disable any actions if required – you are always in the driving seat! When ready, execute the ECO and the changes will be effected. Fast and efficient, your placed vault items are managed with simplistic ease.
Not only can the Item Manager be used to keep your managed components in your designs in-sync with changes to the source Items in the vault(s), it is also a powerful tool to aid in the migration of your existing board designs – from using unmanaged design items to using managed, vault-based design Items. Once you have migrated your design components to a vault – releasing SCHLIB(s), PCBLIB(s) and CMPLIB(s) – and any schematic sheets (device sheets), you simply use the Item Manager to 'replace' the existing components and sheet symbols with their newly migrated vault-based incarnations. In other words, the components remain the same, from the design perspective, but the source of those components changes.