When twenty machines share a block of logic, each project needs to identify the version it uses. TIA manages that relationship through a library of versioned types. Each released type has a version number, and a project can keep using its existing version until you choose to update it. The simulation follows a v1.0 → v2.0 release across several machines.
The shared type FB_Conveyor sits in the library above the three machines that use it. Press ⬆ Release v2.0 to add the simulated "jam detect" feature. The machines are now out of date, but their logic stays unchanged until you select Update for each machine. In this simulation, pinning a machine excludes it from the update. You can compare the released version with the version each machine still uses.
A versioned type keeps the relationship between the shared definition and its instances visible. You can see which version a machine uses before deciding to update it. Keep the machine in production on its accepted version, then plan the other updates for a service window when their changed behaviour can be checked.
🏷️ Type has managed versions. Editing and releasing the type creates a new version (V1.0 → V2.0). Instances retain their version relationship, so shared logic can be updated deliberately rather than copied into each project without a record of its origin.
📋 Master copy is a template you copy from. The copied object has no managed version relationship with the template. Later changes to the template do not update earlier copies, which makes it useful for a starting point but less suitable for maintaining shared machine logic.
📦 Project library belongs to one project and stores objects for reuse within that project. Use a global library when those objects need to be available to other projects or teams as well.
🌍 Global library stores reusable objects separately from an individual project. Teams can share a common FB_Conveyor definition through that library and manage which released version each project uses.
You need to fix a shared conveyor block once, then update all 20 machines when each is ready for the change. Would you use a library type or a master copy?