There is currently not a way to remap the terrain model’s source path in ORD. This capability is needed to be able to push survey data updates via rewriting a .tin file to then update from source (sourcing back to the rewritten .tin file with survey data updates) the terrain model (in a separate .dgn file than the survey data). Updates can be pushed from the survey data to the terrain model (in a separate .dgn file) in this manner, but if the .tin file path changes over the life cycle of the project this source linkage is no longer intact, and updates cannot be pushed to the terrain model. Please enhance ORD to include a similar capability as the Browse tool under the Settings of a reference attachment when a user right clicks on a reference attachment’s file name. The Browse tool allows the user to remap the reference attachment file path in case the reference location changes over the life cycle of the project. This enhancement would provide the user the capability to heal this .tin file source linkage if the .tin file path changes over the life cycle of the project. This is an important need to not lose the civil rule dependencies on the terrain graphics in proceeding workflows (alignments, modeled utilities) and be able to push terrain updates, if the .tin file path location changes, when survey data is modified over the life cycle of the project.