Breaking Large Projects into Subsystem and Component Specific Models
When working with very large projects, it is not always practical to model the complete system in a single model, because the size of the resulting model can result in performance problems.
Typically, a large system comprises a number of subsystems and components, and those subsystems can be modeled in separate models. It is good practice to consider how best to allocate subsystems to different models before starting a project. If a model becomes too large and it contains two or more subsystems, you can move one or more subsystems to a different model.
Usage
If you want to move a subsystem or component to a different model, use Package Import/Export or the Component Sharing Wizard to move the subsystem or component Package to a different model. The Component Sharing Wizard has the advantage of identifying any dependencies that the Package has.
Benefits
Model size: Breaking large projects into subsystem and component specific models results in smaller more manageable models.
Scalability: Large projects can be modeled without individual models becoming too large.
User access: When a model contains only a subsystem or component, access to that subsystem or component can be controlled at the model level.
Recommendations
Ensure that each subsystem or component has its own Package.
When deciding how to assign subsystems to models, you should consider the following factors:
• How large each subsystem is likely to be.
• Which users require access to the different subsystems.
• How connected the different subsystems have to be. You cannot create Modeler links between subsystems that are in different models.
When a subsystem or component is likely to be reused:
• Ensure that the subsystem or component is modeled in its own Package, so that it can be easily copied or moved.
• Consider using PTC Integrity Asset Library to create the subsystem or component as a reusable asset. For more information about PTC Integrity Asset Library, see the PTC website.
When breaking down a model that has become too large, consider moving subsystems that have the fewest links to other subsystems first. When using the Component Sharing Wizard to move a Package, the Component Sharing Wizard can identify links to items that are outside of the Package.
When a system and its subsystems are modeled in more than one model, it is good practice to version all the models at the same time. Failure to do so can result in version skew.