SRO attribute inheritance and planning the templates and instances
- Last UpdatedNov 04, 2024
- 2 minute read
You can create derived templates and instances in your System Platform IDE equipment model.
When you configure any information in a derived SRO template on the Characteristic tab in the System Platform Object Editor, the configured information is automatically propagated to all the child instances of the SRO template. This saves you time in configuring the same information for different entities to capture the same characteristic results.
Note that inherited attribute values that are locked in the parent template cannot be modified in a child template or instance.
If you modify an SRO instance directly or indirectly through a template, an invalid
indicator
appears adjacent to the SRO icon in the System Platform IDE, which indicates that
the SRO object is not synchronized with the MES database. You must run the Entity
Model Builder to update the entity in the MES database as per the changes in the SRO
instance.
You must deploy the System Platform IDE equipment model to use the updated entity at run time. You must also deploy the SRO OnScan to use the defined SRO configurations at run time.
-
For more information about derived templates and instances, and managing System Platform objects, see the System Platform IDE help.
-
For more information about building and deploying MES entities from SROs, see Build the MES entity model from SROs.
-
For information about the run-time behavior of the SRO, see SRO run-time behavior.