Objects that are extremely far (millions of units) from the world origin suffer from display and precision problems due to the polygon mesh vertex locations being represented by a single precision number. This affects the appearance of shading and rendering and the appearance of polygon mesh objects.
One solution to this problem is to move all the existing geometry closer to the origin and make the model there. But, since the model may need to be placed to correspond to survey data that uses the very large numbers of units, this is not always possible. The following procedure can help fix the problem.
This linked block can be updated in the original when it is modified in the copy. The original always has the correct data in the correct location but since it is not the working model, the potential display, mesh and precision problems are not a big deal. The file can be saved as a different file format as needed for a client. The block instance could be exploded before exporting.
The original is now just a container file used to perform the scaling/transposing of the model. All the data in the original can be linked to outside sources. This can include the data from the original model if you will be receiving updates throughout the course of the project. You can update this outside data and have everything update in the original without having to go through the scale/translate process each time.
Thanks to Mike La Fon for outlining this process on the Rhino newsgroup.