Changes

Unlike most of the Technical Notes (TN for short) available in this wiki, this one does not refer to any DAVE Embedded Systems' product. Instead, this article deals with one of the tools we use for hardware designing, namely [https://www.altium.com/altium-designer Altium Designer]. In particularMore specifically, this article TN describes how DAVE Embedded Systems conceived an Altium Designer-based design designing workflow, which is integrated with the existing company's IT infrastructure. The result is depicted in the following image. TBD

In order to implement a glueless integration towards all the company's departments, the workflow had to satisfy the following multiple requirements. The most important are:* Technical documents for manufacturing: At the end of the designing process, a set of standardized technical documents has to be generated automatically for the manufacturing department. This set must be equivalent to the ones produced by the other hardware designing workflows already in use, which are based on different tools.* Database interfacing: The hardware projects must be interfaced to the existing component's database, which is shared across all the company departments (purchasing, manufacturing, R&D, etc.). From this database, several data are retrieved and during the designing process. These data are stored in the project for each instantiated component such as . Examples are the manufacturer code, the operating temperature range, the nominal value in case of passive components, etc. This information is vital for bill of materials (BOM) management and post-design automatic checks.* Projects sharing: Nowadays, it is often necessary to share the hardware projects with other departments or partners outside the company even during the development of the projects themselves. In this regard, [https://www.altium.com/altium-365 Altium 365^®] platform does this job superbly therefore was included in the workflow.