Using the Standalone Workflow, the user has the option to work independently with OpenBridge Modeler, LEAP Bridge Concrete, LEAP Bridge Steel or RM Bridge Enterprise.
In Standalone Workflow:
- Analytical components have physical modeling tools, unlike the components under BIM Workflow
- User does not need to have an OBM model to start with. User can directly create or open an existing analytical file (LEAP Bridge Concrete, LEAP Bridge Steel and RM Bridge Enterprise files)
- First, user switches to
Standalone Workflow. Then;
- User can create as many standalone groups as desired
- User selects a standalone group and then select either "Modeling" or "Analysis" tab
- If "Modeling" tab is selected, OBM can be launched. User may open an existing OBM file or create a new one. Note that OBM files are still external files (outside .obdx) file and OpenBridge Designer keeps the directory of the file and launches it when prompted.
- If "Analysis" tab is
selected, LEAP Bridge Concrete, LEAP Bridge Steel or RM Bridge Enterprise can
be launched. User may open an existing analytical file or create a new one.
- For LEAP
Bridge Concrete or LEAP BRIDGE Steel:
- Note that analytical files are stored in .obdx file (unlike OBM files)
- When an existing file is opened, OBD saves a copy of the file in .obdx file without changing the name of the file. This file gets added in the Standalone Group tree. From this point forward, all changes made to this file will be saved in .obdx file and not saved in the external existing analytical file.
- When user creates a new analytical file or attempts to save an analytical file sent from OBM (in Standalone Workflow), user is asked to enter a name for the file. This file gets added in the Standalone Group tree. All changes to be made to this file will be saved in .obdx file (not as an external file)
- For RM Bridge: The user needs to select the appropriate Setting from the File menu (as shown below) then start the program.
- For LEAP Bridge Concrete or LEAP BRIDGE Steel:
- Standalone groups may have multiple files belonging to different component or the same component.