The beam design process is categorized into two types: gravity beams and lateral beams. The design procedure for lateral beams differs from that of gravity beams due to the consideration of axial load effects as well.
...
In the context of beam design, the analysis source to be considered during the verification process is indicated in the corresponding cell labeled "Analysis Source". The selection and handling of the analysis source in the code check process are explained in detail in the section titled "Revisiting Code Check Templates with a Special Focus on Beams" section.
🔬 Revisiting Code Check Templates with a Special Focus on Beams
Under the "Design Criteria" section, you can navigate to the "Code Check Templates" subsection. Once there, you will find a spreadsheet that displays a collection of imported code check templates (as shown in Figure 3d).
...
For more detailed information about the code check compatibility checks, it is recommended to refer to the section “Basic Compatibility Checks” under “Code Check Objects: Main Considerations”.
The "Design State" cell in the spreadsheet displays the status of the beam design.
Design State: “No Reinforcement”: If it shows "No Reinforcement," it means that the beam rebar templates need to be defined in the "Reinforcements" section.
Design State: “Need Verification”: On the other hand, if all the rebar assignments have been completed, the design state will be shown as "Need Verification". This signifies that the beam is ready for further verification and code check procedures.
The up-to-dateness of the beam design is monitored and indicated through several indicators presented below:
Design State: “red-dotted cell: If the project data has been modified after the code check, a red-dotted cell serves as a reminder that the code check needs to be re-run.
The status label "No Changes" indicates that the code check report for the beam is up-to-date.
The spreadsheet cell labeled "Changes After Last Code Check" provides information on the modifications made to the model following the completion of a code check. It displays the updates or revisions implemented as a result of the code check analysis.
Figure 4 depicts the newly opened spreadsheet that appears when the "View Changes" cell button is clicked, displaying any changes that have been made.
...
If the changes made are not significant enough to require re-running the code check, you can click on the "Ignore Changes" button. This action will change the status of the button from "View Changes" to "No Changes".
The "Back" button (Figure 4) enables you to return to the previous spreadsheet window.
The spreadsheet cell named "Code Check Timestamp" records the time at which the last code check was conducted. It serves as a reference to indicate the specific moment when the code check analysis was performed on the model.
These two cells, "Changes After Last Code Check" and "Code Check Timestamp," offer valuable insights into the code check process, allowing users to track and review the alterations made to the model and refer to the timestamp for the most recent code check operation.
The analysis source that will be considered during the verification process is indicated in the column cell labeled "Analysis Source". The selection and treatment of the analysis source in the code check process are explained in detail in the part “Revisiting Code Check Templates with a Special Focus on Beams” under the "Beam Design" section.
By clicking on the cell-button labeled "Show" in the "Detailed Report" cell, you can access the corresponding detailed reports for each set of load combinations based on the selected analysis results. These detailed reports provide information such as design parameters, analysis results, section analysis and code checks with relevant references. Figures 5a-5d showcase some screenshots from the column code check detailed report, highlighting the available information.
...
Lateral Beam
...
Please refer to the section labeled "Gravity Beam" for the design parameters, as they are identical to the ones mentioned previously, except for the type of code check template used.
...