Update an online area model

Area model configurations are composed of a set of elements that define the functions of the area. A subset of these elements cannot be changed when the model is running. After modifying an online area model you must verify it to confirm that the elements modified are permitted to be updated and can be deployed at runtime.
When you make updates to the area model when the batch server is running you use the
Verify/Deploy
feature in either the
FactoryTalk Batch Equipment Editor
or the
FactoryTalk Batch
Service Manager to check that the changes made will not adversely affect the runtime area model.
Verify Area Model
  • In this step, the changes to the area model are compared to the currently loaded area model configuration file. The purpose of this comparison is to determine whether the set of differences between the two area models, combined with the current state of the FactoryTalk Batch Server, permit deploying of the new area model configuration file.
  • The results of this comparison are written into the Compare/Update log file created when the request is processed. After reviewing the content of the log file you update the area model as needed to resolve any runtime conditions before you continue on to deploy the permitted changes to the area model. These conflicts are created when that portion of the area model that was planned to be updated was in use at the time the deployment occurred. These conditions could be resolved by running the verification again at a later stage in the process.
Deploy Area Model
  • After verification is complete and all errors have been addressed the updated area model can be deployed to the currently running batch server. The Update log file is created that records the details of the updates performed.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal