Parent page: Altium Vault
Through the Altium Content Vault, Altium serves up an incredible array of design content, including components and managed schematic sheets of circuitry - for reuse by designers in their board designs. And while this prolific offering of design data continues to grow, there has always been one thing missing, one hardy barrier to the up-take of vault-based content by the masses: Ownership. For while placement of design data is straightforward, maintenance of that data has always remained the responsibility of Altium. And while technically possible to obtain the source and release afresh into a local vault, the hassle factor simply proved too much. After all, designers want to run with the data and design with it, not jump through hoops to get at it!
Providing an elegant solution, Altium facilitates the ability for an organization to copy the content they need, between nominated source and target vaults. So in this case, a perfect solution to obtaining content from the Altium Content Vault, and delivering it to their local Altium Vault - a process referred to simply as Vault Data Acquisition.
By acquiring design content, ownership is placed firmly in the hands of the receiving organization, who are free to make local modifications and maintain the content as they desire moving forward. And by keeping a link between the acquired data and its original source, intelligent handling of the data can be performed, including notification when the source of any copied content is updated. So for example if, down the track, a change is made to a revision of a design item in the source vault, the target vault has the ability to update to that revision, resynchronizing with the 'mother ship' as it were. And no matter if additional releases have been made to an item locally, there is always the possibility to revert to a previous revision from the source vault - all by keeping a link back to the item's original source, or Origin.
Moving forward, this ability to acquire content - or efficiently transfer content between two nominated vaults in a controlled way - opens up the possibility for third parties (suppliers, manufacturers, etc..) to create their own content vaults, potentially forming an expanded network of 'eData sources', into which designers the world over can come to source the design content they need.
Data Acquisition is delivered as a service through the Altium Vault platform - the platform through which the Altium Vault itself is also provided. The Data Acquisition service is installed as part of the Altium Vault installation. For more information, see Altium Vault.
Verification that the Data Acquisition service is running can be performed from the Windows Internet Information Services (IIS) Manager panel - accessed from Window's Administrative Tools window. Simply check to confirm the following Application Pool is in the
Altium Vault - Data AcquisitionService
The following image provides a higher-level, graphical illustration of the data acquisition concept. The principles of data acquisition depicted are the same, regardless of the type of data being acquired. For illustrative purposes, the Altium Content Vault has been used as the 'source vault', with an Altium Vault as the 'target vault'.
The following Item types can be acquired from a source vault, into a target vault, using the Data Acquisition feature:
Things to take into consideration when acquiring data:
Related page: Working with the Content Cart
Acquisition is performed using the Content Cart dialog. Access to this dialog is made from within the Vaults panel. While browsing the source vault from which you wish to obtain data, simply right-click on an Item Revision that you wish to acquire, and choose the Add to Content Cart command from the context menu. You can add one or more selected Item Revisions, or even a folder of Items (which will load the cart with the latest revision of all Items in that folder).
Use the Content Cart to acquire all the data content you need. The process of acquiring data Items from a source vault is straightforward, and can be summarized in the following steps:
Transfer new revision and item. While the previously specified default acquisition options are applied during this preparation phase, properties of proposed target Items can be modified on an individual basis, as and if required. To do so, simply select an Item in the list and click the Edit button.
Acquired data points back to its original source. This ancestral link information can be seen by changing the aspect view for the target Item revision to its Origin aspect view.
Engineers are curious by nature. Off-the-shelf functionality through black-box delivery is great, but knowing 'what' is being done is only half the picture to an Engineer. To really satisfy their curiosity, they need to dive deeper and see 'how' something is done. Hands up how many of us get a new mobile phone, and quickly pop open the back cover to see what is beneath? Or to put that another way, if given a black box with IO connectors and an interactive panel, how many of us would start by looking for the screws!
This section gives a little more insight into the basic procedural flow employed by the data acquisition feature, and the general scenarios encountered when managing data acquisition.
The following image takes a closer look at the mechanics of acquiring data from a source vault. It illustrates the procedural flow involved, to essentially copy a chosen revision of a source item between the nominated source and target vaults.
As can be seen, the procedure essentially boils down to three distinct stages, ensuring that the data is transferred between vaults whilst maintaining its integrity:
In the previous section, the basic flow of acquisition was seen. To effectively manage the acquisition of data, the relative history of both the source and acquired items is tracked, so that the relevant acquisition actions are available to the designer through the acquisition management interface.
The following sections take a look at the general scenarios encountered when managing data acquisition. In each case, the state of the acquired data - in terms of target Item and any revisions - is compared with its original source Item and its revisions.
In this scenario, no revision of the source Item has been acquired previously. A source Item revision is to be acquired into the initial revision of a new target Item. The the new target Item and revision is created as part of acquisition setup.
In this scenario, a revision of the source Item has been previously acquired. The source Item has subsequently been modified, leading to a later revision being available. In this case, a new revision of the existing target Item would be created, to acquire the later source Item revision.
In this scenario, the latest revision of the source Item has already been acquired - there is nothing further to acquire.
Valid students can get their very own 6-month Altium Designer Student License for FREE! Just fill out the form below to request your Student License today.