About Enventive Concept models and model instances
Enventive Concept's Smart Models™
An Enventive Concept model can be as simple as a single object, such as a piston, or as complex as a collection of interconnected mechanisms, such as an engine. Concept's models are complete, working representations of your parts, not just sketches of geometric objects.
You can embed equations and empirical data into models, so that they can compute their own functional properties. With Concept's models, bearings can compute their B-10 life, springs can compute their Force-Deflection curves—the computations you can devise for your models are virtually limitless.
Concept facilitates model reuse with model instances, which are like links to Concept models that can be included in other models. The original file being linked to is referred to as the master model. Changes to master models are propagated to all the instances of that model in other Concept files. Generally, a Concept file that is a collection of model instances is referred to as an assembly.
For example, say you draw a model of a hinge named Multi-use_Hinge.enb, which you want to use in many different assemblies. You can link to this master model in as many other models (assemblies) as you like. Any changes you make to Multi-use_Hinge.enb will automatically propagate to any assembly that contains a linked instance to it.
Models can be assembled both geometrically and functionally in order to simulate, optimize, and analyze system performance. Model functional outputs can be connected to the inputs of other models: for example, the force generated by a spring produces a load on a shaft, which in turn transmits the load to a bearing. Concept assemblies can also roll up costs, giving team members a running total on manufacturing cost estimates.
Nested assemblies allow for flexibility and facilitate model reuse
A file can include any number of model instances, and as many copies of model instances as needed. Model instances can be complex assemblies that contain instances. The ability to use assemblies as instances helps encourage and increase model reuse, further supporting collaborative work flows and making model construction more efficient and flexible. With nested assemblies, you can reuse existing assemblies as building blocks to create more intricate assemblies, which you can in turn reuse to build complete systems of any size and complexity.
For example, an assembly of an automobile engine may consist of many sub-assemblies: the cylinders, valve train, ignition and cooling systems, and so on. You can have various team members working in concert on the designs for each sub-assembly, which can then be independently integrated into a model of the complete engine.
Model instances support a collaborative team approach
Because changes to master models are propagated to all its instances, updating assemblies with the latest changes to a master model is virtually effortless. In this way, model instances facilitate collaborative modeling. Team members can work on master models independently and propagate the changes to the assembly as needed.
To learn how to create and work with assemblies, run the Assemblies Tutorial from the Enventive Concept Help menu.