Altium Vault

Altium's Vault technology provides the foundation for Altium's Design Data Management solution. A distinct design solution in its own right, an Altium Vault works in harmony with Altium Designer to provide an elegant answer to the question of handling design data with secured integrity. An Altium Vault not only provides rock-solid, secure storage of data, but also enables re-release of data as distinctly separate revisions - essentially tracking design changes over time, without overwriting any previously released data. It also caters for the lifecycle of the data to be managed, allowing people that need to use the data to see, at-a-glance, what stage the data has reached in its 'life' and therefore what it can be safely used for.

But an Altium Vault is used to store so much more than just the data generated from a board design. It is also used to manage all other sets of data obtained from the Design Area through the running of specific release processes. This includes the release of component definitions, domain models, schematic sheets of circuitry and design templates. Indeed, you can even create and manage your entire design projects directly within the vault, with the additional benefit of collaboration support, meaning an entire team can work concurrently on the same board design - even annotating the design with comments. You can even control the working environments of your designers - ensuring that company-wide design standards are enforced and adhered to.

By furnishing a set of resuable design 'building blocks' within an Altium Vault, you can embark on fresh projects safe in the knowledge that each model, component, and higher-order design element has been ratified and approved for use, with no having to reinvent the wheel as it were. The vault becomes both the source and destination of design elements, with each new design utilizing elements realeased to, and managed through, the vault. And by designing only with elements from a vault - vault-driven electronics design as it were - the integrity of those designs is inherently assured.

Vault Items

Within an Altium Vault, each design entity that can be stored, managed, and reused, is represented as a specific type of Item. An Item is uniquely identified within the vault and can contain any number of Revisions, where a revision contains the data for that Item. Each time a change is made to the data contained within a revision - which for most Item types can be edited directly within an associated temporary editor - it is committed (or re-released) into a new revision of that Item, ensuring that no existing revision can ever be overwritten, and thereby ensuring the highest integrity.

An Item can have any number of revisions, which are essentially an evolution of that Item over time. A change is made and the new data content is committed/uploaded/released into a new revision. The data stored in each revision of an item is therefore typically different. To identify between these different revisions of an Item, a revision identifier (ID) is used, which in combination with the Item ID creates a unique identifier for each release of an Item. This gives us the Item-Revision.

Another important aspect of an Item Revision is its Lifecycle State. This is another identifier that can be used to quickly assess what stage that revision has currently reached in its life, and what designers are therefore authorized to do with it. Where the Revision reflects design changes made to the Item, the Lifecycle State reflects the state of the item from a business perspective, such as Planned, New From Design, For Production, Obsolete, and so on.

The Vaults Panel

Providing the direct interface to your Altium Vault is Altium Designer's Vaults panel. From this panel you can perform many activities, including:

• Creating and managing the organizational structure used in the vault.
• Creating any number of Items, each representative of a design object.
• Direct editing and placement of Item Revisions.
• Reviewing and managing the lifecycle of Item revisions.
• Interrogating the usage of a particular Item revision (Where-Used).
• Browsing and managing supply chain information for Component Items.
• Downloading stored data, including data generated through the managed release of board design projects.

The Vaults panel becomes your trusty right-hand, presenting a collection of features that can really enhance your productivity when working with an Altium Vault through Altium Designer.

Direct Editing

Vaults provide a flexible and secure method of centralizing the storage and management of all types of design data used in Altium Designer. From the schematic model to the component, from managed sheets through to completed PCB designs, an Altium Vault delivers an ideal method of storing and managing your electronic design data.

Many design entities can be edited and released into the initial revision of a corresponding, and newly-created vault Item, courtesy of the vault's support for direct editing. Direct editing frees you from the shackles of separate version-controlled source data. You can simply edit a supported Item type using a temporary editor loaded with the latest source direct from the vault itself. And once editing is complete, the entity is released (or re-released) into a subsequent planned revision of its parent Item, and the temporary editor closed. There are no files on your hard drive, no questioning whether you are working with the correct or latest source, and no having to maintain separate version control software. The Altium Vault handles it all, with the same great integrity you've come to expect, and in a manner that greatly expedites changes to your data.

And at any stage, you can come back to any revision of a supported Item in the vault, and edit it directly. Simply right-click on the revision and choose the Edit command from the context menu. Once again, the temporary editor will open, with the entity contained in the revision opened for editing. Make changes as required, then commit the release of the document into the next revision of the item.

Vault Components

Altium Designer, with its unified design approach, has traditionally used a component model that extends across all aspects of the electronics design process. However, to seamlessly fit the process of electronics design into the encapsulating product development process as a whole, this model needs to evolve - extending to cover other aspects including other design processes (in particular MCAD and Industrial Design), as well as business processes (such as procurement and manufacturing) that intersect with the product development process.

This evolved object model is known as the Unified Component Model.

Under this modeling paradigm, the design component, as seen by the designer, is separated from the Manufacturer and/or Vendor parts. This information is not defined as part of the component. Instead, a separate vault Item - a Part Choice List Item - is used to map the design component to one or more Manufacturer Parts, listed in a Part Catalog, which in turn can be mapped to one or more Vendor parts, allowing the designer to state up-front, what real parts can be used for any given design component used in a design.

These components, along with their part choices, are stored in a target Altium Vault. A component is stored as a series of revisions of a uniquely-identifiable Component Item. Each revision is lifecycle-managed, providing collections of certified components, authorized to be re-instantiated into new design projects, manufactured into prototypes, or used for production runs. In short, a catalog of components implemented through vault-based 'libraries'.

Private License Service

For organizations that require their Altium Designer installations to remain offline - isolated from the internet - the convenience and flexibly of on-demand software licensing can be provided by a localized Private License Server, rather than from the internet-based Altium Licensing Service. The Altium Vault installation provides just the ticket, through its local Private License Service. This service is simple to configure and provides a host of improved features over the existing Altium Private License Server that is installed as a windows service. It can be configured as a central, or local License Server, and can serve both Altium Designer and Altium Vault licenses over a local network. In addition, a vault administrator is able to take full control over the offline leasing of license seats, configure licensing for use by specific roles, and configure a license for Roaming, and much more.

The vault's PLS can be configured and used in different modes of operation, as summarized below:

• No PLS mode - the vault's standard configuration, where its acquired licenses are not made available (served) on the network.
• Local PLS mode - both Altium Designer and Altium Vault licenses that have been acquired by the vault are served over a network by the vault's (local) PLS service.
• External PLS mode - the vault connects to, and uses, an external PLS service (such as a remote vault PLS that has been set up as a central license server) in place of its own PLS service.

Local Version Control Service

The Altium Vault installation includes an SVN server (version 1.8). It provides version control possibilities right there where you need them, locally, without searching or paying for external SVN management software.

There are two key advantages over the standard SVN built in to Altium Designer (or sourced externally):

1. You have common users and rights management for both the Altium Vault and SVN. When you sign in to the Altium Vault, the local SVN version control service works with your session/credentials.
2. Repositories defined through the Altium Vault (through the VCS page of the vault's browser-based interface) are populated to the client automatically during login, so users do not have to worry about urls, protocols, password etc. It is simply configured once, on the server, and shared with the intended users as required.

By defining design repositories in this centralized fashion, an oganization can fully control which repositories its designers can access and use. Repositories can be created through the local SVN server, or external repositories can be connected to. Together, all repositories are centrally managed through the vault's browser-based interface, in terms of:

• Their displayed name and description.
• Their configured accessibility - which specific users can access them (or roles in the case of repositories defined through the local SVN server).
• Their availability - add or remove them centrally, rather than individual designers having to create and connect to repositories independently.

Centralized Project Management

The Altium Vault, in conjunction with Altium Designer, brings support for Managed Projects. In the past, the traditional use of an Altium Vault was to handle the release management stage of projects, with high integrity and security. Managed Projects target the development stage of the project lifecycle, simplifying the creation and ongoing workflow for version controlled projects. Centralized storage under the control of the Altium Vault also enables this feature to be a foundation for other collaborative services.

Some key benefits to using Managed Projects are:

• Simplified storage. No need to make decisions about storage locations. Backup and other basic services are taken care of.
• Foundation for collaborative features.
• Enforced version control.
• Beneficiary of a dedicated commenting system.
• Notifications and status. Document status including local modifications is visible to entire design teams.
• Concurrent PCB design works without any complex setup.

Management is performed through the Projects page of the vault's browser-based interface. New Managed Projects can be created through this interface, or through the New Project dialog in Altium Designer. Alternatively, an existing, non-managed project, can be quickly converted to a Managed Project.

Centralized Supply Chain Management

Each Altium Vault instance has its own dedicated Part Catalog. This is a managed local part catalog database, dedicated to the management and tracking of manufacturer parts and their associated supplier parts. The catalog is installed as a service (Part Catalog Service), provided through the Altium Vault platform, and works only with the Altium Vault.

The 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 Supplier database.

The actual supply chain intelligence is sourced from the part catalog and the relevant Supplier Database. The latter can be an external database (Supplier web-based service), or an internal company parts database (ODBC-based). It is this link to the Supplier database that yields real-time pricing and availability data.

Which Supplier Databases are actually used - a list of Approved Suppliers - is managed by the Altium Vault, through the Part Providers page of its browser-based interface. This facilitates centralized supply chain management, with designers across the entire organization using the same approved list of Vendors.

Configuration Management

Facilitating enterprise-level enforcement of a designer's work environment - to ensure that they are following the required standards expected by that organization for design, documentation and production - the Altium Vault installation provides the Team Configuration Center.

The role of the Team Configuration Center is to give the organization centralized control over the environment its designers operate in. It achieves this through the definition and management of Environment Configurations. These are used to constrain each designer's Altium Designer working environment to only use company-ratified design elements, including schematic templates, output job configuration files, and workspace preferences. In other words, it facilitates Centralized Environment Configuration Management.

Any number of environment configurations may be defined through the Center's dedicated browser-based interface. The data used and enforced by each configuration - referred to as Configuration Data Items - are sourced from the Altium Vault. And by associating each environment configuration with a specific user role, and in turn assigning users to those roles, the correct working environment is loaded into Altium Designer as soon as the user signs in to the Altium Vault. Using this role-based approach ensures that a designer always gets the setup they are entitled to, no matter whether they have their own PC, or are sharing a single PC with fellow designers.

Data Acquisition

Altium facilitates the ability for an organization to copy the content they need, between nominated source and target vaults - 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. 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 original source vault - all by keeping a link back to the item's original source, or Origin.

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 the revision of a supported Item type that you wish to acquire (or a folder of components, for example), and choose the Add to Content Cart command from the context menu.

Network Installation Service

The Altium Vault platform provides a dedicated Network Installation Service. This service, allows an organization to perform installations, or updates to Altium Designer, over their local network. The main goals of the Network Installation Service are:

• To improve speed of updates - people will download data inside of the local network.
• To remove dependency on Internet access for update functionality - it could work in isolated networks, without access to global internet.
• To provide the ability to control versions and updates in a centralized way.
• To support performing push installations, using Microsoft's Active Directory Group Policy.

The service is accessed through the Installations page of the vault's browser-based interface. Typically you would acquire the products and extensions that you need from Altium's Cloud Vault into your local Vault, then craft a deployment package for installation across your network. Subsequent updates can be configured automatically, or handcrafted manually for ultimate control over what gets installed on your designer's machines.

Backup and Recovery

Over time, your Altium Vault will accommodate a growing, and impressive amount of data. The value of this data cannot be overstated, for it is a mixture of source data that can be re-used in future design projects, as well as data from which past, current, and future products are fabricated and assembled. It is data that has been released and ratified under the highest scrutiny, and stored securely with the upmost integrity. And as with all valuable data, longevity of its integrity is ensured by being able to perform a backup.

The Altium Vault installation caters for the archival of your vault data through the provision of a command-line-driven Backup & Restore tool. The tool's executable - avbackup.exe - is located in the \Program Files (x86)\Altium\Altium Vault\Tools\BackupTool folder, for a default installation of the Altium Vault.

Applications & Services for Vaults

The Altium Vault Server is a platform server product that acts as the host for network-based services such as the Altium Vault, the Team Configuration Center, Data Acquisition service and so on. The Vault Server harnesses the web server capabilities of Windows™ Internet Information Services (IIS) to create the server platform. Because Web services use standard mechanisms to communicate over networks and the Web, they can easily interact with any type of remote device, application or service. In the case of the Vault service, this can be directly with Altium Designer, via a standard web browser, or potentially with an enterprise infrastructure like a company PLM system.

To enable the development of custom applications and interfaces that can interact with services hosted on the Vault Server, such as the Vault service, Altium has released the Altium Vault Software Development Kit (SDK). Also known as the Vault SDK, when installed it provides the resources needed to develop web service client applications using the Microsoft™ C# programming language. The collection of Vault web services are exposed at a network level through comprehensive Application Programming Interfaces (APIs), which define an XML-based request-response message format that’s passed using HTTP as a transport mechanism. All the service functions, data and notifications are available via the APIs, allowing the Vault Server to freely communicate and interact with other systems over conventional networks.

Ultimately, the Vault SDK is ideal for developing applications and interfaces that enable interactive communication between the server's hosted services and existing enterprise systems. For example the Vault’s advanced content management system and its inherent association with Altium Designer can be hooked in to company systems at any level, and potentially, at any remote location.