This has no bearing on the content of the folder - releasing a component will always result in a corresponding Component Item. When creating the folder in which to store Component Items, you can specify the folder's type. Once a Component Item has been created (and data released into a revision of it), and its lifecycle state set to a level that the organization views as ready for use at the design level, it can be reused in the creation of one or more designs. For more information, see Adding Supply Chain Information to a Managed Component.Ĭomponent Items are created directly from within the server. Part choices can also be made outside of editing the component itself.

Part choices can be made while defining the component, prior to its release to the server, and can be modified at any time thereafter by editing that managed component. This is the process of nominating which 'real-world' part(s) can be used for the design component when the product is physically assembled. To do so requires that Part Choices be made for that component. This document focuses on bringing the required pieces together to define and release a component into a managed content server.Ī component can be extended to include real-world physical component information, creating a component that spans, or rather unifies, the Design and Supply Chain arenas - a truly Unified Component. Revision-controlled and lifecycle-managed, a company can authorize a set of such Component Items - or Managed Components - that can be formally used by their designers. Once all prerequisite domain models have been created and released into your managed content server, a design component can be defined and released into that server for reuse in design projects. Parent page: Working with Managed Components Impact on Component Models and Parameters when using a Component Template.Inherited from the Components Server Folder.Manually from within the Component Editor.

Altium unified components