# 🚚 We've moved
As you may have heard AWF is now part of ADP family
# 🤷♀️ What is happening
AWF is being migrated into the Arup Data Platform (ADP) Environment. In essence this means we are re-launching AWF under the ADP umbrella. AWF will therefore be moved to a new urls
# 🌐 New URL
# 🤷♂️ Why is it happening
As Arup continually works towards our mission to be the digital leaders in the built environment, workflow automation and working with data at scale is a large part of this. In order to reduce duplication, share resources and focus our collective efforts towards data centric engineering, AWF is joining ADP to provide more benefit to our users and enable further development of the data ecosystem.
# ⌚ When is it happening
The new AWF environment will go live on December 13
# 🙋♂️ How will this effect me
As a standard user you will barely notice any difference in using the AWF platform aside from the new urls that are used see new urls.
For worker and workflow owners (i.e. editors) there may be some additional updates needed to get your workers and workflows up and running again.
- Existing workers will need to re-register them and update the worker configuration file.
- Workflow configurations may need to be updated, as Arup has moved to migrate from GitLab to GitHub you will need to update the models url in your workflow configuration(this issue is not due to the migration)
- 3rd Party integrations will need to resubmit their info to the AWF team and reconfigure their message queues see here
- awfpy users will need to install the latest version of awfpy (opens new window) and potentially update their scripts.
💡 TIP
We have put together a FAQ to answer standard questions that may arise.
🙄 FAQ →