A distinct self-managed, server-based design solution, Altium Concord Pro works in harmony with Altium Designer to provide an elegant answer to the question of handling design data with secured integrity. Altium Concord Pro 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.
Altium Concord Pro is used to store and manage components, domain models, schematic sheets of circuitry and design templates. Indeed, you can even create and manage your entire design projects directly within the server, 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.
By furnishing a set of reusable design 'building blocks' within Altium Concord Pro, 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 server becomes both the source and destination of design elements, with each new design utilizing elements released to, and managed through, the server. And by designing only with elements from Altium Concord Pro, the integrity of those designs is inherently assured.
And Altium Concord Pro facilitates bi-directional design collaboration with various supported mechanical design platforms. This enables you to keep MCAD and ECAD design teams on the same page by sharing changes to board shape, component placement, and mounting holes, and intelligently link together 3D component bodies with your electrical component data - creating a unified component model that accurately reflects design intent from the respective domains.
Within Altium Concord Pro, 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 Server 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.
From within Altium Designer, component management is streamlined through use of the Components panel and Manufacturer Part Search panel. However, another interface to your Altium Concord Pro installation is the Explorer panel. From this panel you can perform many activities, including:
Altium Concord Pro provides 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, Concord Pro 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 server Item, courtesy of Concord Pro'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 server 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. Concord Pro 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 Concord Pro, 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.
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, Part Choices are 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 Altium Concord Pro. 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 server-based 'libraries'.
Altium Concord Pro, in conjunction with Altium Designer, brings support for Managed Projects. 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 Altium Concord Pro also enables this feature to be a foundation for other collaborative services.
Some key benefits to using Managed Projects are:
Management is performed through the Projects page of the Concord Pro's browser interface. New Managed Projects can be created through this interface, or through the Create Project dialog in Altium Designer. Alternatively, an existing, non-managed project, can be quickly made available to Concord Pro.
Most electronic products that are designed are fixed to some kind of mechanical structure - either a chassis, or an enclosure. Finding a mechanical conflict between board (ECAD) and chassis/enclosure (MCAD) late in the design process can be a costly experience. And while you could get a 3D model exported from Altium Designer, it is a manual process that needs conscious decision and action to do so. In reality, this is performed very infrequently, with the result being that the MCAD designer is never quite sure if what they've got is the latest and greatest. It really shouldn’t be so hard to ensure you’re not about to waste a pile of money just because your tools don’t talk.
Altium Concord Pro facilitates native ECAD to MCAD collaboration where data flows seamlessly between domains. No more polling for updates, and no more uncertainty. Data is pushed between domains as the design evolves, ensuring design coherence.
The following MCAD platforms are supported:
Altium Concord Pro facilitates the uni- or bi-directional synchronization of component data with your enterprise systems. A configuration file allows you to specify the direction of synchronization and therefore which parameters are mastered in which system. Component data synchronization between Concord Pro and the target enterprise system uses a built-in synchronization process. which may be manually triggered or set as timed repeating event.
An Altium Concord Pro installation includes a CSV Component database importer tool that can be used to bring component data into Concord Pro from a file exported from another system (PLM, ERP, or otherwise). Implemented as a configurable batch (
*.bat) file, the desktop tool imports component data from a target spreadsheet file (
*.csv) into the server as determined by existing server templates or a dedicated configuration file.
In addition, direct support is provided for the following enterprise systems:
Interface configuration is performed through Concord Pro's browser interface, with the connection setup and parameter mapping defined within an XML-based configuration file (uploaded to the server). A smart configuration generator is also included to help in creating custom connection to enterprise systems.
When the synchronization process first adds a component's data in the target system, the generated item number is passed back to the component in Concord Pro as a
PlmPartNumber parameter. This acts as the key parameter when synchronizing data between Concord Pro and the enterprise system instance. In addition, the configuration can be arranged so that item parameters/attributes on the enterprise system side will update properties in the Concord Pro server (configurable per field), without having to formally release a new revision of that Component Item.
Altium Concord Pro has its own dedicated Part Catalog. This is a managed part catalog database, dedicated to the management and tracking of manufacturer parts and their associated supplier parts. The catalog works only with Concord Pro.
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 the aggregate parts database of the Altium Parts Provider (which itself interfaces to, and gathers the parts from, enabled Suppliers).
Which Suppliers are actually used - a list of Approved Suppliers - is managed by Concord Pro, 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 Suppliers, with which to source supply chain intelligence for parts used in their designs.
Altium facilitates the ability for an organization to copy the content they need from a source Server, and deliver it to a second target Server - a process referred to simply as Server 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 Server - 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 Explorer panel. While browsing the source server 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.
For organizations that require their Altium Designer installations to remain offline - isolated from the internet - the convenience and flexibility 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 Concord Pro installation provides just the ticket, through its local Private License Service. It can be configured as a central, or local License Server, and can serve both Altium Designer and Altium Concord Pro licenses over a local network. In addition, a server 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 server's PLS can be configured and used in different modes of operation, as summarized below:
The Altium Concord Pro installation provides localized (and centralized ) version control, courtesy of its Version Control service. This service provides version control possibilities right there where you need them, locally, without searching, or paying for, external VCS management software.
A new installation of Altium Concord Pro provides a single Git-based design repository for accommodating all of your managed design projects - and that's it! This avoids any setup and complexity regarding the Server's local Version Control service. You have a single design repository - Versioned Storage - for all your designers to access and release into. As such, the VCS page of the Server's browser interface becomes purely informational - you cannot add a new repository, and the single Git repository cannot be modified in any way, nor deleted. If you have upgraded to Altium Concord Pro from Altium NEXUS Server 1.0 (or Altium Vault 3.0) then use of SVN repositories will also be enabled, so that you can continue to use your previous (and established) design flow. In this case, you can continue to create repositories through the local Version Control service (SVN-only), or connect to external repositories (SVN or Git).
By defining design repositories in this centralized fashion, an organization can fully control which repositories its designers can access and use.
Over time, your Altium Concord Pro instance 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 Concord Pro installation caters for the archival of your Server 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 Concord Pro\Tools\BackupTool folder, for a default installation of Altium Concord Pro.