![altium designer 18 bomdoc altium designer 18 bomdoc](http://i1.hdslb.com/bfs/archive/e988a2e9eb48366d2e72e12e1d9a53e6a9a3ac30.jpg)
Use of Component Templates ( not supported in Altium 365 Standard) - apply parameter and component taxonomy based templates, so each new component type automatically has the correct BOM-compliant parameter set, in addition to automating the correct naming, revision and lifecycle schemes.Real-time supply-chain information - fed back from the aggregate parts database of the Altium Parts Provider (which itself interfaces to, and gathers the parts from, enabled Suppliers), to let the designer know the current costing and availability of the chosen parts, and from all vendors that sell those chosen parts (as defined in the managed content server's local Part Catalog).Design-time choice of physical components - for any given managed component, you can choose which Manufacturer Parts can be used to implement that component when assembling the board.As such, this functionality will not be available when connected to an Altium 365 Workspace with this level of access to Altium 365. In short, a catalog of components implemented through server-based 'libraries'.Ĭomponent revision and lifecycle management is not supported in Altium 365 Standard. 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.
#Altium designer 18 bomdoc series#
A managed component (as it is then referred to) is stored as a series of revisions of a uniquely-identifiable Component Item.
![altium designer 18 bomdoc altium designer 18 bomdoc](https://www.allaboutcircuits.com/uploads/articles/ActiveBOM.jpg)
These components, along with their part choices, are stored in a managed content server. 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. This information is not defined as part of the component. Under this modeling paradigm, the design component, as seen by the designer, is separated from the Manufacturer and/or Vendor parts.
![altium designer 18 bomdoc altium designer 18 bomdoc](https://cdnimg.mr-wu.cn/wp-content/uploads/2018/01/Altium-Designer-18-修改主题颜色-8.jpg)
A truly 'Unified Component' model that not only represents the component in the different design domains (Schematic Capture, PCB Layout, Simulation) but also facilitates choices of the desired physical components - real-world manufactured parts - at design-time, offering a significant improvement in terms of procurement cost and time, when manufacturing the assembled product. This component model effectively maps the concept of a design component - in the traditional electronics design arena - to the component as seen by the rest of the organization in the bigger 'product arena'. This evolved object model is known as the Unified Component Model. However, to seamlessly fit the process of electronics design into the encapsulating product development process as a whole, this model needed 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.
![altium designer 18 bomdoc altium designer 18 bomdoc](https://i.ytimg.com/vi/KzBWMzurRwE/maxresdefault.jpg)
Altium Designer, with its unified design approach, has traditionally used a component model that extends across all aspects of the electronics design process.