Josh Rong and I spent a couple of hours evaluating the usage of altium concord pro hosted on A365. Technically we have wanted to use Concord Pro for a while, but we had no computer that could host the server. With the addition of Altium 365 - Altium’s online workspace integration with Concord pro, and our contact allowing us access to 20 licenses, we are able to use the concord server and have it hosted on A365. Another advantage about this is that it allows us to collaborate with Alitum’s component engineers and component libraries to integrate with our libraries and have fast access to new components not in our library.

Overview

What is concord pro?
”Altium Concord Pro® is a product to store and manage components, domain models, schematic sheets, projects, and design templates. Since it is fully-integrated with Altium Designer®, Altium Concord Pro easily handles component management making it easier to manage components across all of your designs. Altium Concord Pro provides secure data storage enabling the release of data as distinctly separate revisions with secure integrity.”

Main features that we care about:

Component Management
ECAD-MCAD Co-Design
Component Synchronization
Web Interface

Setup/Access

To connect to the workspace, your email must first be added by an administrator (Aashmika Mali or any hardware lead).

Then, you can either follow this guide or the next few screenshots - (https://www.altium.com/concord-guide/step_one_connect_to_concord_pro.html)

Our server link is https://university-of-waterloo-solar-car-team.365.altium.com:443

Press sign in

Once its done loading, you should see the workspace in designer like so:

A365 Workarea

This secrion

Components

Evaluating Migrating existing libraries

So Josh Rong migrated the schematics and footprint libraries to the server!! This is really cool because now whatever components were on josh’s power select branch have now been added to the server and can be accessed in Altium designer by anyone with access to the server.

We decided to test the extents of this migration function by adding a new component and migrating the library again. However, we unfortunately soon realized that it duplicated all the other components (though it still added test_concord). We are currently in the process of getting rid of all the

-want to go over migrating single component however, if by accident new ones remain in schematic diagrams on other branches