Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→Implementation
From now on, any new design in which they will be used will integrate fully qualified instances. And what about the project developed by Bob and Mallory? At the end of the the design process, the DAVE team will take care of synchronizing the project with the database library in order to have all fully qualified instances. After this step, the project is ready to undergo post-design sanity checks and, finally, to generate the manufacturing documentation required to order the PCB's and assemble them.
Interestingly, updating the ERP database and the master database library is a process '''that leverages the same tools DAVE Embedded Systems adopted several years ago for software development/maintenance''': [https://gitlab.com/ GitLab] along with its [https://docs.gitlab.com/ee/ci/ CI/CD module]. TBDLikewise software build process, data merging between the ERP database and the database library need the execution of many commands, which are tedious, prone to errors, and can lead to a bugged library. Thanks to the CI/CD modules, we can guarantee that the merge is always executed by running exactly the same command chain.
Sharing the projects via Altium 365 is not only efficient when working with external engineers. It is also extremely convenient for those who do not work with Altium Designer. For instance, let's suppose that Charlie is a member of the R&D team and is a software developer. At some point, he needs to access the schematics of the board designed by Bob and Mallory to see how an I2C device for which he is writing a driver is connected to the application processor. Even though Charlie can not use Altium Designer, he can access the project schematics via web browser by accessing Altium 365 platform. Of course, the same approach can be used with other coworkers who are not even part of the R&D team such as Project Managers, executives, manufacturing engineers, etc.
