1. Define the nodes for the structure, starting from the bottom. See the N command.
2. Set the boundary conditions using the D command
3. Define the groups and elements using the GROUP and E commands
4. Check the elements by opening a Model Plot window by using the Plot > Model > Element menu or the Model
6. Define the materials, soil layers, and beam properties using the M, L, and R command
7. Assign materials and properties to the elements using the MSET and RSET command
8. Check the assigned materials and properties in the Model Plot window by showing the elements in their material / property color (see sections and ) and comparing their color with the material / property color shown when selecting the Options > Colors menu or the Color Command.
9. Set the element integration order for SOLID elements using the EINT command.
10. Define the nodal masses (MT and MR Commands) and set the mass units option (MUNITS Command)
11. Check the masses by displaying them in the Plot>Model>Nodes which opens the node plot window
12. Set the model options by selecting the Options > Model Menu
13. Define the analysis frequency set (FREQ Command)
14. Define the analysis options by selecting the Options / Analysis menu command
15. Run the AFWRITE command to write the analysis files for the selected modules
16. Run the desired modules for the simulation

The Submodeler has a single two level database structure for the users computer. The single database replaces the multiple user-defined databases in the Main Prep work-flow. The single database is in a location cached by the system so the user will never have to search the directory structure to find old databases that have not been used in some time. The 2 level structure will allow the user to organize all of the models on a computer account by project much similar to how the multiple database model in the Main/Prep work-flow was intended. Finally, the database is now considered to be a convenience feature and is no longer required to use any functionality in the Submodeler.

When the user attempts to open a model for the first time in the Submodeler the Load Model Window tree structure will be empty. At this time the user must add a group. All models must reside within a group. If the user attempts to define a model without a group the model will not be saved in the database structure. After the user defines a group the user must select the group he/she wants to add the model to in the tree window. One the group is selected the user can press the add model button and provide the model information as they would in Prep. Once the user clicks OK the Tree will update with the added model. Then the user can select the model and open it if desired. If the user has a model selected and attempts to add a new model that model will be added to the group in which the selected model resides.

When the user opens the model there may be errors about files not existing, this is to be expected when creating a new model. The Database expects the model to exist and attempt to load the model when the open button is pressed. The database is setup to allow user to reorganize the models on there system and to add models to the database that have been created without the database in previous Submodeler execution. For this reason, the database no longer creates the files that the model loading code is trying to load before the loading sequence which causes the error messages.

As stated earlier, the database is no longer required in the use of the Submodeler. If the user is only going to use a model for a single analysis the database will only add additional steps to the process. For that reason the user can directly use the prep file Input (INP command or the File>Input menu) or one of the converters to load a model into the Submodeler. If the user uses this method to input the SAVE, RESUME & AFWRITE commands will not work because the Input file does not specify the model name and model path. (These command may actually run but there is no way to tell where the models will be written) If the user wishes to use any of this functionality There is a new command MDL which specifies the model name and path. Once the MDL command is used on a model the Save, Resume and Afwrite commands will work properly. The MDL command can be issued before or after the model input without problems.

The Input in Prep Echos all of the commands entered to the screen. This take a large amount of time and for any useful model that is not for validation the output overwhelms screen and will eliminate any chance of the user finding an error in the .pre file. Due to this fact is was decided that only comments, warning, error and the model information text will be echoed to the screen. This change in sped input of a .Pre file from 25-30 minutes using Prep to under 1 minute for the submodeler on the same computer.

If the user has create and saved the model in a previous Submodeler run the user use the MDL to specify the model and then use the resume command to load the model. The internal storage format that the save and resume commands use is not compatible with ACS-SASS Prep the user cannot specify the location of a model save using Prep and load it using resume in the Submodeler

The save and resume and Afwrite commands work in the same way as they work in ACS-SASSI Prep. These command do not update the database. If the user wants to add a saved model to the database the user can use the Model Open popup window to modify the database and add the loacation of the saved model.