Looks like you don't have ESC button on your device
Download IronCAD DCS
Choose one of the following options
trial versionHas a license
Looks like you don't have ESC button on your device
Choose one of the following options
trial versionHas a license
Emil Rindell
Jonas Bryntesson
Henrik Andersson
2021-06-04
Emil Rindell
Jonas Bryntesson
Henrik Andersson
2021-06-04
From one and the same 3D scene, we can produce different types of lists, such as a shopping list or a spare parts list. How do you want your lists to be formatted and what should they contain? In this post, we'll go over just that! Here are examples of four different lists from a single assembly:
A variety of list types can be read from a IRONCAD file. By switching between several different settings, you can produce different lists containing several levels of parts and assemblys. In this document we read out 8 different lists from the same 3D model. The handling of the "Expand" or "Treat as Part" setting for a assembly is something that affects how it and its contents are listed.
To create a BOM, you need to choose both a BOM configuration (template with columns to load different values) and BOM type (how the tree structure should be loaded) and some other settings. The tools for the BOM can be found under the menu "BOM Creation".
In this post, the BOM configuration "BOM as ICD smst" is used , which corresponds to the columns loaded in the 2D drawing parts list. The settings of the BOM template are controlled via the "Open BOM Configuration Manager...".
The "Open Setting Dialog..." option controls all other settings listed in this document. The "Create BOM" option creates a BOM based on the settings made.
Displays only the top level of the tree, in this case the Engine assembly. All parallel assemblys and partners at the root of the tree are listed here.
Corresponds to the 2D drawing's parts list and does not show in-depth details in assemblys as they are set to "Treat as Part". So in this case it stays on the M4 BoltAssembly.
Get a complete overview of all components and their number in a flat list that includes all parts in all assemblys. Also counts the assembly in which the components are found. So in this case the smst M4 BoltAssembly is also included, even though its constituent parts are also listed.
Get a complete overview of all components and their number in a flat list that includes all parts in all assemblys. Does not count the assembly in which the components are found. So in this case the list exported does not include the smst M4 BoltAssembly. Can also be called Bill of Quantity.
Creates a structure list with one separating column per level in the tree - Level. The list does not show the components in the assemblies set to "Treat as Part".
Creates a structure list where the level separator is compact and appears in a separate column in the list - Level. The list does not show the components of assemblies set to "Treat as Part".
Creates a structure list with a separating column for each level in the tree - Level. The list forces the components of assemblies to be displayed.
Creates a structure list where the level separator is compact and displayed in a separate column in the list - Level. The list forces the components of assemblies to be displayed.
Answer: Here we publish tips, guides, news and solutions for those who work with IRONCAD and Design Data Manager (DDM). The blog covers everything from basic functions to advanced workflows, helping you to optimize your design work. You'll find examples of smart shortcuts, practical instructions, solutions to common problems, and best practices for product design, mechanical design, and product data management.
Answer: Our guides and tips are designed for both beginners and experienced CAD users. They are aimed at designers, engineers and project managers who want to work more efficiently with IRONCAD and DDM, improve the design process, reduce mistakes and save time in product development.
Answer: We regularly publish new articles when the software is updated, when new features are introduced, or when our users ask for solutions to specific problems. The blog is therefore a reliable source for keeping up to date and getting tips that make everyday CAD work easier.
Answer: Many of our instructions and tips work in multiple versions, but we clearly indicate if an article applies to a specific version. We strive to make the content useful for older versions as well, and also provide recommendations on how to adapt workflows to the version you are using.
Answer: Absolutely! If you can't find the solution in the blog, you can contact our technical support via solidmakarna.support. Our experts will help you with everything from installation and configuration to advanced features in IRONCAD and DDM, so you can solve problems quickly and efficiently.
Answer: Yes! We appreciate suggestions from our users. If you have questions, tips or want us to address a specific issue in IRONCAD or DDM , please contact us via our contact form and we will prioritize relevant topics in future posts.
Answer: The blog contains, among other things:
Practical step-by-step guides to help you use IRONCAD and DDM more effectively.
Productivity and workflow tips for faster design and construction.
Solutions to common problems encountered by users in CAD programs.
Updates and news on new features, versions and improvements.
Best practices for data management and project organization in DDM.
Answer: All tips and guides are directly applicable in daily work. For example, you can use shortcuts and smart features in IRONCAD to speed up modeling, structure files better in Design Data Manager, or follow our step-by-step solutions for specific problems that often come up in design projects.
Answer: We strive to ensure that all guides and tips are relevant to the latest versions of IRONCAD and DDM. We also clearly mark when a post applies to an older version, so you always know if the instruction is directly applicable to your system.
Answer: Yes! Many of our users share the articles with colleagues and use them as internal training materials. The blog is a great complement to formal training and helps teams learn features faster, avoid mistakes, and standardize workflows in IRONCAD and DDM.
