I load it with my Project Defaults. But my Project Defaults load by variables.
In my Project Defaults, in the "default" project, in the XIN field, it contains $(_InRoads_XIN)
Actually, every one of my fields look like that, except for the XML Reports Style Sheet Path - that has to be hard coded to a real folder.
In my CFG files - Standards, Project & my own Client CFG files, I define these variables, some using even more variables. When my users select a project - which on our setup, is more of a client (and sometimes a version and/or workflow) these all work together and define all of my custom InRoads variable for the Project Defaults. So when they look at the XIN or go to load a RWK or DTM, it already has default locations and/or files.
If I need a special XIN for a project that is unique to that project, I would put it in the RWK. Generally, the special XIN would be a copy of a standard XIN but with additional items for that project. So until the RWK is loaded one of the standard XIN files would load and when the RWK is loaded, the custom one would than get loaded.
In my standards folder are three CFG files, one for MicroStation, one for InRoads and one for special plotting variables. In the InRoads one is this assignment:
_InRoads_XIN = $(_AB_IRXM_CLIENT)data/$(_AB_CLIENT_XIN) #XM or later one XIN file.
The two variables used there, are defined in a Client PCF file. It defines the path to the clients inRoads data folder and the name of the XIN file.
This process is repeated for the Storm and Sanitary structures and rainfall files, quantity manager files, drafting notes files and many of the path variables so the file open dialog boxes default to a project location. Some of this requires a VBA macro to build some variables, but many can come simply from CFG files.
When we use InRoads with AutoCAD, we manually change to different Project Defaults, but for MicroStation projects, we have only one project in the Project Defaults.