1 – ProtaStructure Data File Structure & Modeling Flowchart

1. Caption evidence
   Observation

   Slide text: “Project Data Folder must be correctly chosen”; diagram labels the path as the parent folder.

2. Audio
   Observation

   Narrator discusses opening projects and warns against manually renaming the Project Folder in Windows Explorer.

Project Data Folder

The parent directory that contains one or more project folders for ProtaStructure.

File-system path used by ProtaStructure.

1. Caption evidence
   Observation

   Diagram annotation: “Project Code = Project Folder”; slide text: “Do not manually rename the Project Folder in Windows Explorer.”

2. Audio
   Observation

   Narrator says renaming the project folder in Windows Explorer will make it disappear from the Open Project dialog.

Project Folder

The folder whose name is the project code; it stores all files required for a ProtaStructure model.

Directory inside the Project Data Folder.

1. Caption evidence
   Observation

   Slide text: “Use Save Project As function in ProtaStructure.”

2. Audio
   Observation

   Narrator recommends using Save Project As to rename a project instead of renaming the folder externally.

Save Project As

ProtaStructure command used to save a project under another name or location while preserving internal file links.

Software menu/function name.

1. Caption evidence
   Observation

   Slide text: “Alternatively, go to File > Archive Project to create a compact project zip file of the model files only.”

2. Audio
   Observation

   Narrator describes Archive Project as creating a compact zip file of the model files only.

Archive Project

ProtaStructure command that packages the model files into a compact ZIP archive.

Software menu/function name.

1. Caption evidence
   Observation

   Slide text: “Automatic backup is created every hour which can be restored using Open Previous Backup in the Building Setout tab.”

2. Audio
   Observation

   Narrator states automatic backups are created hourly and can be restored with Open Previous Backup.

Open Previous Backup

ProtaStructure function used to restore an earlier automatically saved version of the project.

Software function located in the Building Setout tab.

1. Audio
   Observation

   The narrator names the method as FE floor analysis.

2. Caption evidence
   Observation

   The lower-right diagram is labeled FE Floor Analysis Gravity Load Chasedown.

FE floor analysis

A structural analysis method that considers only one story at a time and analyzes the members and slabs of that particular story.

Structural engineering modeling workflow for building floors.

1. Audio
   Observation

   The narrator says this unique analysis considers only one story at a time and calls it sub-frame analysis.

2. Caption evidence
   Observation

   The bullet list includes Analyze 1 floor at a time (sub-frame).

sub-frame analysis

Analysis restricted to one story, including only the members and slabs of that story.

Applied structural analysis method.

1. Audio
   Observation

   The narrator describes accumulating gravity loads of columns and walls by starting from the top to bottom story separately and in sequence, in process called gravity load chasdown.

2. Caption evidence
   Observation

   The bullet list states Gravity Chasedown must be performed to correctly accumulate gravity loads.

3. Caption evidence
   Observation

   The lower-right diagram title reads FE Floor Analysis Gravity Load Chasedown.

gravity load chasdown

A sequential top-to-bottom procedure used to accumulate gravity loads of columns and walls when analyzing one story at a time.

Load accumulation procedure in FE floor analysis.

1. Audio
   Observation

   The narrator says lateral load results must be obtained from building analysis and recommends using building analysis first preference because it analyzes gravity and lateral loads using a single consistent analytical model.

2. Caption evidence
   Observation

   The upper-right diagram is labeled Building Analysis without floor slab meshed.

3. Caption evidence
   Observation

   The lower-left diagram is labeled Building Analysis with floor slabs meshed.

4. Caption evidence
   Observation

   The final text box says Overall, consider using Building Analysis as first choice as it analyzes gravity and lateral loads using a single consistent analytical model.

building analysis

The whole-building analytical method used here for lateral load results and recommended as the first-choice overall analysis approach.

Structural analysis workflow comparison.

1. Audio
   Observation

   The narrator states that for lateral load results must be obtained from building analysis.

2. Caption evidence
   Observation

   The bullet list states Lateral load results must be from Building analysis.

lateral load results

Results associated with lateral loading, which the video assigns to building analysis rather than FE floor analysis.

Structural load response category.

1. Audio
   Observation

   The narrator says this chasdown can only provide gravity load result.

2. Caption evidence
   Observation

   The bullet list states Only gives gravity load results.

gravity load results

The type of result produced by FE floor analysis with gravity load chasdown in this workflow.

Structural load response category.

1. Caption evidence
   Observation

   The upper-left 3D model is labeled Physical Model.

Physical Model

The source 3D building model from which the different analysis paths are derived in the flowchart.

Diagram object label.

1. Audio
   Observation

   The narrator explains the course format, mentioning modules of 5 to 10 minutes, step-by-step guides, and recommendations for viewing and hands-on practice.

2. Caption evidence
   Observation

   Slide titled 'Format of e-learning' lists bullet points corresponding to the narration.

The course is structured into short modules of 5 to 10 minutes each. It provides a step-by-step guide to build a simple model from scratch and uses pre-constructed models to demonstrate specific functions. The recommended learning path is to first view a module without hands-on practice, and then repeat it with hands-on application.

1. Modules are related and should be followed in order.

1. Audio
   Observation

   The narrator describes how ProtaStructure manages model data using Project Folders and Project Data Folders.

2. Caption evidence
   Observation

   Slide titled 'ProtaStructure Data File Structure' lists rules for naming and organizing folders, accompanied by a diagram showing the hierarchy.

ProtaStructure stores all files for a project in a 'Project Folder'. This folder's name must exactly match the 'Project Code' (or Project Name) and cannot contain spaces. The Project Folder is created within a parent directory called the 'Project Data Folder'. A user can have multiple Project Data Folders, but it is recommended for new users to use just one for simplicity.

1. Spaces are not permitted for the Project Code.

2. Project Folder name must match the Project Code.

1. Audio
   Observation

   The narrator explains how to open a project by correctly choosing the Project Data Folder in the Open Project dialog.

2. Caption evidence
   Observation

   Slide shows screenshots of the 'Open Project' dialog and Windows Explorer, with arrows pointing to the 'Project Data Folder' and 'Project Code = Project Folder'.

To open a project, the correct Project Data Folder must be selected in the software's 'Open Project' dialog. Users can change this folder by clicking 'Choose / Create Folder'. The default Project Data Folder is typically named 'ProtaData' followed by the release version number. Inside this folder, project subfolders (like Quick Start Guides) are created, and their names must match the project codes used in the software.

1. Do not manually rename the project folder in Windows Explorer.

1. ProtaStructure Data File Structure

1. Caption evidence
   Observation

   Slide lists three rules: choose the correct Project Data Folder, do not manually rename the Project Folder, and do not delete any files inside the Project Folder.

2. Diagram
   Observation

   Windows Explorer screenshot shows Data Folder as parent folder and Project Code as Project Folder.

3. Audio
   Observation

   Narrator explains that renaming the folder externally breaks the Open Project dialog and that all files inside the folder are essential.

A ProtaStructure project is stored as a folder named by its project code inside a selected Project Data Folder. The software relies on this exact naming and on the presence of all internal files. Renaming the folder in Windows Explorer or deleting internal files prevents the project from being opened correctly. To rename a project, use the Save Project As function inside ProtaStructure instead.

1. Project Data Folder must be correctly chosen before opening a project.

2. Project Folder name must match the project code.

3. No files inside the Project Folder may be deleted.

4. Renaming must be done via Save Project As, not via OS file explorer.

1. Caption evidence
   Observation

   Slide bullets recommend storing projects on local hard drive, warn against external drives/servers for large models, and advise against auto-sync with Dropbox/OneDrive.

2. Audio
   Observation

   Narrator explains performance impacts due to large file sizes and additional memory resources from sync software.

For optimal performance, ProtaStructure projects should be stored on a local hard drive. External hard disks and network servers are discouraged because large structural models generate very large files containing analysis results, design data, reports, and drawings. Automatic synchronization services such as Dropbox or OneDrive are also not recommended because they consume extra memory and can degrade software performance.

1. Applies to large structural models with extensive analysis/design outputs.

2. Local storage preferred over external/network storage.

3. Third-party auto-sync should be disabled for the project folder.

1. ProtaStructure project folder integrity rules

1. Caption evidence
   Observation

   Slide lists manual backup via File > Save Project As, archiving via File > Archive Project, and hourly automatic backups restorable via Open Previous Backup.

2. Audio
   Observation

   Narrator details each method and notes the default retention of three hourly backups allowing restoration of approximately three hours of work.

Users should regularly back up their models. Manual backup is performed using File > Save Project As to save a copy under another name. Alternatively, File > Archive Project creates a compact ZIP containing only the model files. ProtaStructure also creates an automatic backup every hour; these can be restored using Open Previous Backup in the Building Setout tab. By default, three hourly backups are retained, permitting recovery of roughly the last three hours of work.

1. Manual backup requires choosing a new filename/location.

2. Archive Project produces a ZIP of model files only.

3. Automatic backups occur hourly and are limited to three by default.

1. ProtaStructure project folder integrity rules

1. Caption evidence
   Observation

   Flowchart box 2 reads “Derive Beam Loads using the ‘Yield Line’ (tributary area) approach.” Box 2a reads “FE Load Decomposition: Derive Beam Loads by meshing slabs in FE model.”

2. Audio
   Observation

   Narrator states beam loads are automatically derived using the default yield line or tributary area method, and that FE load decomposition is the alternative method deriving loads by meshing slabs in the FE model.

After building the 3D physical model, beam loads must be derived from slab loads. The default approach uses the Yield Line (tributary area) method. An alternative is FE Load Decomposition, which derives beam loads by meshing the slabs within the finite element model. These two methods represent different computational strategies for transferring slab loads to supporting beams.

1. Requires a completed 3D physical model with beams and slabs.

2. Yield Line/Tributary Area is the default method.

3. FE Load Decomposition requires slab meshing in the FE model.

1. Audio
   Observation

   The speaker says this method captures localized effects of slab openings and concentrated slab loads such as slab line loads, and that it can be used on selected or all beams in selected stories or for the whole model.

2. Diagram
   Observation

   Box 2a is titled "FE Load Decomposition" and states "Derive Beam Loads by meshing slabs in FE model" and "Choose whether to use these loads selectively or on all beams in a storey or all storeys".

This method derives beam loads by meshing slabs in a finite element model. It is presented as able to capture localized effects of slab openings and concentrated slab loads such as slab line loads. The user may apply the resulting loads selectively or to all beams in one storey or all storeys.

1. Requires meshing slabs in an FE model.

2. Can be applied selectively or globally across beams and storeys.

1. Audio
   Observation

   The speaker says the general building analysis can be run to generate column, wall and beam design forces, and that by default floor slabs are not meshed in building analysis, with an option to mesh slabs of all or selected stories.

2. Diagram
   Observation

   Box 3 reads "Run the general building analysis - 3D frame analysis of full model" and "Option to mesh floor slab by 'Include Slab in Building Model'".

The general building analysis is a 3D frame analysis of the full model used to generate design forces for columns, walls, and beams. By default, floor slabs are not meshed in this analysis, but there is an option to include slab meshing for all or selected stories.

1. Used after beam loads have been derived.

2. Slab meshing is optional and controlled by "Include Slab in Building Model".

1. Audio
   Observation

   The speaker says to check and verify the analytical model, identify error or warning messages such as large deformation or unstable joints, check that deflection and member forces are reasonable, and check the axial load comparison report to ensure no gravity load is lost.

2. Diagram
   Observation

   Boxes 4 and 5 read "Check & verify 'Building Analytical Model'", "Identify & resolve error or warning messages, e.g. large deformation / unstable joints", "Check Axial Load Comparison Report", and "Ensure gravity Load input = Load Output".

After the building analysis is completed, the analytical model must be checked and verified. This includes identifying and resolving error or warning messages such as large deformation or unstable joints, checking that deflections and member forces are reasonable, and reviewing the axial load comparison report so that gravity load input equals load output.

1. Performed after successful completion of building analysis.

2. Required before proceeding to member design.

1. General building analysis

1. Audio
   Observation

   The speaker says that after verifying the analytical model is satisfactory, you can proceed to design the beams, columns, walls and foundation elements.

2. Diagram
   Observation

   Boxes 6.1, 6.2, and 6.3 appear as "Beam Design", "Column/Wall Design", and "Foundation Design".

Once the analytical model has been verified as satisfactory, the workflow proceeds to design beams, columns/walls, and foundations.

1. Requires satisfactory verification of the analytical model.

1. Verification of the building analytical model

1. Audio
   Observation

   The speaker introduces FE Floor Analysis as an alternative to building analysis, useful for flat slab where there are no beams to support the slabs, and also for beam and slab layout where sub-frame behavior or single story analysis is preferred.

2. Diagram
   Observation

   Box 3a reads "FE Floor Analysis (Flat Slab / Sub-frame)", "Use sequential FE floor analyses to chase gravity loads down the structure", "Check & verify FE analytical model", and "Merge column and / or beam forces with lateral results from Building Analysis".

FE Floor Analysis is an alternative to the general building analysis. It is particularly useful for flat slab systems where there are no beams supporting the slabs, and it can also be used for beam-and-slab layouts when sub-frame behavior or single-storey analysis is preferred. Because the analysis is done one floor at a time, sequential FE floor analyses are required to accumulate column and wall loads from top to bottom story. After merging, the FE floor analysis results are used in member design.

1. Alternative to general building analysis.

2. Requires sequential analysis floor by floor to chase gravity loads down the structure.

3. Results must be merged with lateral results from building analysis before member design.

1. General building analysis

1. Audio
   Observation

   Narrator: “Otherwise, you will not be able to open it, as it will disappear from the Open Project dialog.”

2. Caption evidence
   Observation

   Slide text: “Do not manually rename the Project Folder in Windows Explorer.”

If a ProtaStructure Project Folder is renamed manually in Windows Explorer, the project will no longer appear in the Open Project dialog and cannot be opened normally.

1. The folder was originally created and recognized by ProtaStructure.

2. The rename operation occurs outside ProtaStructure's Save Project As function.

Universal for projects managed by ProtaStructure's standard file structure.

1. Caption evidence
   Observation

   Slide text: “Do not delete any files inside the Project Folder – all are essential.”

2. Audio
   Observation

   Narrator: “All files are essential to the model.”

Every file contained within a ProtaStructure Project Folder is necessary for the proper functioning and integrity of the model.

1. The folder corresponds to a valid ProtaStructure project.

2. Files have not been corrupted or replaced by non-project data.

Universal quantification over all files in the Project Folder.

1. Caption evidence
   Observation

   Slide text: “By default, there will be 3 backups, which means you can restore approximately 3 hours of work.”

2. Audio
   Observation

   Narrator confirms three hourly backups allow restoring previous three hours of work.

ProtaStructure retains exactly three automatic hourly backups by default, enabling restoration of approximately three hours of prior work.

1. Default settings have not been modified.

2. Backups are generated consistently every hour during active sessions.

Existential/default quantification regarding software configuration.

1. Caption evidence
   Observation

   Flowchart box 2a labeled “FE Load Decomposition” connected as alternative to box 2 “Yield Line”.

2. Audio
   Observation

   Narrator: “FE load decomposition is the alternative method to yield line slab load calculation.”

FE Load Decomposition serves as a valid alternative to the Yield Line (tributary area) method for deriving beam loads from slabs in ProtaStructure.

1. The structural model includes slabs suitable for FE meshing.

2. The user selects or configures the FE Load Decomposition option.

Conditional existence of alternative workflow path.

1. Audio
   Observation

   The speaker says to check the axial load comparison report to ensure no gravity load is lost, load input equals to load output.

2. Diagram
   Observation

   Box 5 states "Ensure gravity Load input = Load Output".

For a valid building analysis, the axial load comparison report should show that gravity load input equals load output, indicating that no gravity load is lost.

1. A building analysis has been completed.

2. The axial load comparison report is available.

For the analyzed model, the total gravity load input should equal the total load output.

1. Audio
   Observation

   The speaker says, "By default, floor slabs are not meshed in building analysis."

2. Diagram
   Observation

   Box 3 includes "Option to mesh floor slab by 'Include Slab in Building Model'".

By default, floor slabs are not meshed in building analysis; slab meshing is an option controlled by "Include Slab in Building Model".

1. Using the general building analysis workflow.

Default setting for the building analysis.

1. Audio
   Observation

   The speaker states that for a flat slab model, this analysis method is wrong because slab loads cannot be captured by the columns and walls, meaning the loads will be completely lost.

If a flat slab system is analyzed using a frame-only model without meshing the slabs, the gravity loads from the slabs will not be transferred to the supporting columns and walls, resulting in a structurally invalid analysis.

1. The structure is a flat slab system (slabs supported directly by columns/walls without beams)

2. The analytical model excludes slab meshing

For all flat slab systems analyzed with frame-only models

1. Audio
   Observation

   The narrator states that this unique analysis considers only one story at a time and that only members and slabs of that particular story are considered and analyzed.

2. Caption evidence
   Observation

   The bullet list states Analyze 1 floor at a time (sub-frame).

In FE floor analysis, only one story is analyzed at a time, and the analysis includes only the members and slabs of that particular story.

1. The method being discussed is FE floor analysis / sub-frame analysis.

For the FE floor analysis method described in the clip, the restriction applies to each analysis step: exactly one story is considered at a time.

1. Audio
   Observation

   The narrator says analysis must start from the top to bottom story separately and in sequence, in process called gravity load chasdown.

2. Caption evidence
   Observation

   The bullet list states Gravity Chasedown must be performed to correctly accumulate gravity loads.

To accumulate gravity loads of columns and walls in FE floor analysis, the analysis must be performed separately for each story in sequence from the top story to the bottom story.

1. FE floor analysis is being used.

2. Gravity loads of columns and walls need to be accumulated correctly.

The claim is stated as a required procedure for the FE floor analysis workflow described.

1. Audio
   Observation

   The narrator says this chasdown can only provide gravity load result and that lateral load results must be obtained from building analysis.

2. Caption evidence
   Observation

   The bullet list states Only gives gravity load results and Lateral load results must be from Building analysis.

The gravity load chasdown in FE floor analysis provides only gravity load results; lateral load results must be obtained from building analysis.

1. The analysis path is FE floor analysis with gravity load chasdown.

The statement is universal for the described FE floor analysis output in this clip.

1. Audio
   Observation

   The narrator says hence, the need to run building analysis first, before performing FE floor analysis.

Because lateral load results must come from building analysis, building analysis needs to be run first before performing FE floor analysis.

1. The workflow requires both lateral load results and FE floor analysis.

The claim is presented as a workflow consequence for cases using FE floor analysis after building analysis.

1. Audio
   Observation

   The narrator recommends building analysis as first preference as it analyzes gravity and lateral loads using a single consistent analytical model.

2. Caption evidence
   Observation

   The final text box states Overall, consider using Building Analysis as first choice as it analyzes gravity and lateral loads using a single consistent analytical model.

Building analysis is recommended as the first choice because it analyzes gravity and lateral loads using a single consistent analytical model.

1. The comparison is between building analysis and the previously described FE floor analysis workflow.

The claim is stated as an overall recommendation for the modeling workflow shown.

1. Diagram
   Observation

   Flowchart shows Step 1 (Build Model) leading to Step 2 (Derive Beam Loads), with Step 2a branching as an alternative method.

2. Audio
   Observation

   Narrator explains sequence: build 3D model first, then derive loads using either yield line or FE decomposition.

1. Expression

   $$$$
   Explanation

   Construct the 3D physical geometry including beams and slabs.

   Justification

   Flowchart Step 1 precedes Step 2; loads cannot exist without defined structural elements.

   Shown in the video
2. Expression

   $$$$
   Explanation

   Apply load derivation algorithm to transfer slab loads to beams.

   Justification

   Flowchart Step $2/2a$ depends on completed geometry; narrator states loads are derived 'as you model beams and slabs'.

   Shown in the video

Beam load derivation is logically dependent on prior completion of the 3D physical model; neither Yield Line nor FE Decomposition can execute without defined slab-beam connectivity.

1. Diagram
   Observation

   The flowchart boxes appear sequentially and are connected by arrows showing the order of steps.

2. Audio
   Observation

   The narration follows the same sequence from load derivation to analysis, verification, design, and alternative paths.

1. Expression

   $$$$
   Explanation

   Start from step 2, derive beam loads using the Yield Line (tributary area) approach, with optional step 2a FE Load Decomposition.

   Justification

   Shown as the first active branch in the visible flowchart and described in the opening narration.

   Shown in the video
2. Expression

   $$$$
   Explanation

   Proceed to step 3, run the general building analysis (3D frame analysis of full model), with optional slab meshing.

   Justification

   Box 3 follows box 2 in the diagram and the speaker describes running the general building analysis next.

   Shown in the video
3. Expression

   $$$$
   Explanation

   Then perform steps 4 and 5, check and verify the building analytical model and check the axial load comparison report.

   Justification

   Boxes 4 and 5 are placed below box 3 and the narration explicitly says to verify the model after analysis.

   Shown in the video
4. Expression

   $$$$
   Explanation

   If verification is satisfactory, continue to member design branches 6.1 Beam Design, 6.2 Column/Wall Design, and 6.3 Foundation Design.

   Justification

   These boxes appear after the verification step and the speaker says design can proceed after verification.

   Shown in the video
5. Expression

   $$$$
   Explanation

   In parallel, step 3a FE Floor Analysis is introduced as an alternative to building analysis, requiring sequential floor-by-floor analysis and merging with lateral results before member design.

   Justification

   Box 3a appears later in the flowchart and the narration explains it as an alternative path.

   Shown in the video
6. Expression

   $$$$
   Explanation

   Step 6.4 Slab Design can also be reached directly after model build using tabulated code coefficients or yield line method, or via step 3b using the same FE models with slab meshed.

   Justification

   Box 6.4 and the label "Slab design based on tabulated code coefficients" appear near the end, and the final narration describes these alternatives.

   Shown in the video

The clip presents a branching structural analysis and design workflow: beam load derivation leads to building analysis and verification, then member design, while FE floor analysis and direct slab design provide alternative routes.

1. Audio
   Observation

   The narrator links the one-story nature of the analysis to the need to accumulate gravity loads by moving from top to bottom story separately and in sequence.

1. Expression

   $$$$
   Explanation

   FE floor analysis is restricted to one story at a time.

   Justification

   Stated directly in the narration and reinforced by the bullet Analyze 1 floor at a time (sub-frame).

   Shown in the video
2. Expression

   $$$$
   Explanation

   Columns and walls carry accumulated gravity loads from multiple stories above.

   Justification

   This is the reason given in the narration for why accumulation is needed when analyzing one story separately.

   Shown in the video
3. Expression

   $$$$
   Explanation

   Therefore, to accumulate those gravity loads correctly, the stories must be processed separately and in sequence from top to bottom.

   Justification

   Explicitly stated by the narrator as the process called gravity load chasdown.

   Shown in the video

The one-story restriction of FE floor analysis leads to the need for a sequential top-to-bottom gravity load chasdown procedure.

1. Audio
   Observation

   The narrator first states the limitation of FE floor analysis results and then concludes there is a need to run building analysis first before performing FE floor analysis.

1. Expression

   $$$$
   Explanation

   FE floor analysis with gravity load chasdown provides only gravity load results.

   Justification

   Directly stated in the audio and in the bullet list.

   Shown in the video
2. Expression

   $$$$
   Explanation

   Lateral load results must be obtained from building analysis.

   Justification

   Directly stated in the audio and in the bullet list.

   Shown in the video
3. Expression

   $$$$
   Explanation

   Hence, if both result types are needed, building analysis must be run before FE floor analysis.

   Justification

   Explicitly drawn by the narrator with Hence, the need to run building analysis first, before performing FE floor analysis.

   Shown in the video

The result limitation of FE floor analysis implies that building analysis should precede FE floor analysis in the workflow.

1. Audio
   Observation

   The speaker introduces the example physical model as a flat slab model supported by columns and a lift core wall, with a beam between the lift core walls.

2. Diagram
   Observation

   A 3D rendering of a multi-story building with octagonal floor plates, central core, and perimeter columns is shown.

Identify the structural system of the provided physical model to determine appropriate analysis methods.

1. Multi-story building with octagonal floor plates

2. Supported by perimeter columns and a central lift core wall

3. A beam exists between the lift core walls

Classify the structural system (e.g., flat slab vs. beam-slab).

1. Explanation

   Observe the primary vertical supports for the floor slabs.

   Justification

   Visual inspection of the 3D model.

   Shown in the video
2. Explanation

   Note that the slabs rest directly on columns and the core wall without a surrounding grid of beams.

   Justification

   Visual inspection of the 3D model.

   Shown in the video
3. Explanation

   Conclude that the system is a flat slab model.

   Justification

   Definition of a flat slab system.

   Derived from the video

The physical model represents a flat slab system.

The visual evidence of slabs supported directly by columns and walls confirms the flat slab classification.

1. Audio
   Observation

   The narrator gives an example: FE floor analysis may be useful to analyze and design slabs by meshing of one particular story, as slab design is usually designed only to gravity loads.

1. The clip does not show a numerical slab example, only a verbal use case.

Identify a situation in which FE floor analysis is useful despite being more complicated and longer.

1. FE floor analysis can mesh one particular story.

2. Slab design is usually designed only to gravity loads.

Explain why a one-story sub-frame method can still be appropriate.

1. Expression

   $$$$
   Explanation

   Use FE floor analysis when sub-frame analysis is required or preferred.

   Justification

   Stated by the narrator as the general condition for using the method.

   Shown in the video
2. Expression

   $$$$
   Explanation

   Apply it to analyze and design slabs by meshing one particular story.

   Justification

   Given explicitly as the example in the narration.

   Shown in the video
3. Expression

   $$$$
   Explanation

   This is suitable because the stated design target is gravity loads only.

   Justification

   The narrator says slab design is usually designed only to gravity loads.

   Shown in the video

The example is slab analysis and design for one particular story using meshed FE floor analysis, justified by the claim that slab design is usually governed by gravity loads only.

No numerical verification is shown in the clip; the example is presented verbally as a use case.

1. Diagram
   Observation

   A tree diagram appears showing 'Data Folder "1"' branching into 'Project Folder "a"', '"b"', '"c"', and 'Data Folder "2"' branching into '"m"', '"n"', '"o"'.

1. Data Folder

2. Project Folder

1. Diagram illustrates the parent-child relationship between Data Folders and Project Folders.

1. Multiple Project Folders can exist within a single Data Folder.

Visualizes the concept that a Project Data Folder acts as a parent container for multiple individual Project Folders.

1. Diagram
   Observation

   Screenshots of the 'Open Project...' dialog and Windows Explorer are shown side-by-side with red arrows connecting corresponding elements.

1. Open Project Dialog

2. Windows Explorer

1. Arrows highlight the 'Project Data Folder' path and the 'Project Code' list items.

1. The folder names in Windows Explorer match the project codes in the software dialog.

Demonstrates the direct link between the software's project selection interface and the underlying operating system file structure.

1. Diagram
   Observation

   Split-screen graphic showing ProtaStructure Open Project dialog on left and Windows Explorer folder tree on right, with red arrows linking 'Data Folder = Parent Folder' and 'Project Code = Project Folder'.

1. Open Project dialog window

2. Windows Explorer folder view

3. Red annotation arrows

4. Text labels for Data Folder and Project Code

1. Static display throughout segment 0–23s

1. Parent-child relationship between Data Folder and Project Folder remains visually fixed

2. Project Code equals Project Folder name equivalence is constant

Visualizes the strict naming convention and directory nesting required for ProtaStructure to locate and validate projects.

1. Animation
   Observation

   Blue box labeled '1. Build the Model' appears at top-left of flowchart slide.

1. Blue rectangular node

2. Text '1. Build the Model'

3. Subtext about progressive Building Model Check

1. Node fades/appears into view at ~90s

1. Position anchored at start of workflow sequence

Establishes the foundational prerequisite step before any load analysis can occur.

1. Animation
   Observation

   Second blue box '2. Derive Beam Loads...' appears below step 1, followed by dashed arrow to side box '2a. FE Load Decomposition'.

1. Main load derivation node

2. Alternative FE decomposition node

3. Connecting arrows

1. Sequential appearance of nodes and connectors between 103s and 110s

1. Hierarchical relationship: Step 2 is primary, Step 2a is optional alternative

Illustrates the decision point in the engineering workflow where users choose between traditional tributary area methods and modern FE-based load transfer.

1. Diagram
   Observation

   A slide titled "Modelling, Analysis & Design flowchart" progressively reveals boxes 2, 2a, 3, 4, 5, 6.1, 6.2, 6.3, 3a, 6.4, and 3b with connecting arrows.

1. Title text "Modelling, Analysis & Design flowchart"

2. Box 2 "Derive Beam Loads using the 'Yield Line' (tributary area) approach"

3. Box 2a "FE Load Decomposition"

4. Box 3 "Run the general building analysis - 3D frame analysis of full model"

5. Box 4 "Check & verify 'Building Analytical Model'"

6. Box 5 "Check Axial Load Comparison Report"

7. Boxes 6.1, 6.2, 6.3 for Beam, Column/Wall, and Foundation Design

8. Box 3a "FE Floor Analysis (Flat Slab / Sub-frame)"

9. Box 6.4 "Slab Design"

10. Box 3b "Use same FE models (with slab meshed) to generate alternative slab design forces"

1. At about 14 seconds, box 3 appears below box 2.

2. At about 29 seconds, boxes 4 and 5 appear below box 3.

3. At about 54 seconds, boxes 6.1, 6.2, and 6.3 appear at the bottom.

4. At about 63 seconds, box 3a appears to the right of boxes 3 and 4.

5. At about 110 seconds, box 6.4 and the label "Slab design based on tabulated code coefficients" appear.

6. At about 119 seconds, box 3b appears below box 3a.

1. The slide title remains visible throughout.

2. Boxes 2 and 2a remain visible after they appear.

3. The overall left-to-right and top-to-bottom flowchart structure remains consistent.

The animation visually constructs a workflow map for structural modelling, analysis, verification, and design, showing both the main sequential path and alternative branches for FE floor analysis and slab design.

1. Animation
   Observation

   Red boxes sequentially highlight different sections of the flowchart, specifically step 3b ('Use same FE models...') and step 3 ('Run the general building analysis...').

1. Flowchart boxes

2. Red highlight rectangles

1. Red boxes appear around specific flowchart steps to draw attention to them as the speaker discusses those parts of the workflow.

1. The overall structure and text of the flowchart remain static.

The animation guides the viewer's focus to the relevant steps in the structural analysis workflow being discussed by the narrator.

1. Diagram
   Observation

   The screen splits into four quadrants showing: top-left the physical model, top-right the frame-only analytical model, bottom-left the fully meshed analytical model, and bottom-right the FE floor analysis load chase-down.

2. Animation
   Observation

   Red boxes and text overlays appear sequentially next to the top-right and bottom-left models to explain their characteristics and limitations.

1. Physical 3D model

2. Frame-only wireframe model

3. Fully meshed surface model

4. FE floor analysis diagram

5. Text overlay boxes

1. Text boxes detailing the pros and cons of each modeling approach appear and disappear in sync with the narration.

1. The four base images representing the different models remain visible throughout the segment.

This visual setup allows for a direct comparison between the physical reality and the two distinct analytical simplifications, highlighting how load paths differ based on whether slabs are meshed or excluded.

1. Diagram
   Observation

   The slide shows four panels connected by blue arrows: upper-left Physical Model, upper-right Building Analysis without floor slab meshed, lower-left Building Analysis with floor slabs meshed, and lower-right FE Floor Analysis Gravity Load Chasedown.

2. Caption evidence
   Observation

   Labels visible include Physical Model, Building Analysis without floor slab meshed, Building Analysis with floor slabs meshed, and FE Floor Analysis Gravity Load Chasedown.

1. Physical Model 3D building

2. Building Analysis without floor slab meshed frame model

3. Building Analysis with floor slabs meshed model

4. FE Floor Analysis Gravity Load Chasedown stacked slab model

5. blue directional arrows

1. The slide is initially static with all four panels visible.

1. The physical model remains the source node at upper left.

2. The arrows indicate branching from the physical model to the other analysis representations.

The visual establishes a comparison among different analysis paths derived from the same physical building model.

1. Animation
   Observation

   A white text box with a red border appears over the upper-right area.

2. Caption evidence
   Observation

   The box lists Analyze 1 floor at a time (sub-frame), Column, wall, beam & slab meshed, Only gives gravity load results, Gravity Chasedown must be performed to correctly accumulate gravity loads, and Lateral load results must be from Building analysis.

1. Exact frame of appearance is approximate because the sampled images show the box absent at 3 seconds and present at 4 seconds.

1. White text box with red border

2. five bullet points

1. The bullet list appears over the upper-right portion of the flowchart.

2. The rest of the diagrams remain visible underneath and around the box.

1. The underlying four-panel flowchart structure does not change.

2. The listed bullets summarize the method being narrated.

The animation converts the spoken explanation into explicit criteria and limitations of FE floor analysis.

1. Diagram
   Observation

   The lower-right panel shows stacked cyan floor slabs with black downward arrows and red vertical lines connecting across levels.

2. Caption evidence
   Observation

   The panel is titled FE Floor Analysis Gravity Load Chasedown.

1. The exact numerical magnitude represented by arrows is not labeled.

1. Stacked cyan floor slabs

2. black downward arrows

3. red vertical lines

4. yellow highlighted regions on some slabs

1. The panel remains visually static while the narration explains sequential accumulation from top to bottom.

1. Downward arrows consistently indicate gravity-direction loading.

2. Red vertical lines connect levels, visually suggesting load transfer through vertical elements.

The diagram illustrates one-story-at-a-time slab analysis with gravity loads being transferred downward through the building height.

1. Diagram
   Observation

   The upper-right panel shows a blue frame without slab mesh, while the lower-left panel shows cyan meshed floor slabs around a central frame.

2. Caption evidence
   Observation

   Labels distinguish Building Analysis without floor slab meshed and Building Analysis with floor slabs meshed.

1. Upper-right blue frame model

2. lower-left cyan meshed slab model

3. blue arrows from Physical Model

1. No animation changes the geometry during the main explanatory segment.

1. Both panels are presented as building analysis variants derived from the same physical model.

2. The key visual difference is presence or absence of meshed floor slabs.

The side-by-side diagrams distinguish modeling representations within building analysis, separate from the one-story FE floor analysis path.

1. Audio
   Observation

   Narrator states: 'Spaces are not permitted for Project Code.'

2. Caption evidence
   Observation

   Bullet point: 'Spaces are not permitted for Project Code (Project Name)'

Users might try to include spaces in their project names or codes.

The software explicitly forbids spaces in the Project Code, which dictates the Project Folder name.

1. Audio
   Observation

   Narrator warns: 'Do not manually rename the project folder in Windows Explorer.'

2. Caption evidence
   Observation

   Bullet point: 'Do not manually rename the project folder in Windows Explorer.'

Users might think they can rename project folders directly in the OS file manager.

Manual renaming breaks the link between the software's project code and the file system, so it is prohibited.

1. Audio
   Observation

   Narrator explicitly warns against manual renaming in Windows Explorer.

2. Caption evidence
   Observation

   Bullet point: “Do not manually rename the Project Folder in Windows Explorer.”

Users may assume renaming a project folder via Windows Explorer is equivalent to renaming within the software and will not affect functionality.

Manual renaming breaks the link between the software's registry/dialog and the actual folder name, causing the project to vanish from the Open Project list. Always use Save Project As.

1. Caption evidence
   Observation

   Bullet point: “Do not delete any files inside the Project Folder – all are essential.”

2. Audio
   Observation

   Narrator emphasizes all files are essential to the model.

Engineers might think auxiliary files inside the project folder are temporary caches that can be safely deleted to save space.

ProtaStructure treats every file in the Project Folder as integral to the model definition. Deletion compromises data integrity and may prevent reopening or correct analysis.

1. Caption evidence
   Observation

   Bullet point advises against auto-synchronising with third party software like dropbox/onedrive.

2. Audio
   Observation

   Narrator cites performance impact due to additional memory resources.

Users often believe automatic cloud synchronization enhances collaboration and safety without downsides for heavy engineering software.

For large structural models, background sync processes compete for memory and $I/O$ bandwidth, significantly degrading ProtaStructure performance. Local storage with manual/archived backups is superior.

1. Audio
   Observation

   The speaker explicitly says, "By default, floor slabs are not meshed in building analysis."

2. Diagram
   Observation

   Box 3 states "Option to mesh floor slab by 'Include Slab in Building Model'".

One might assume that floor slabs are always meshed in the general building analysis.

The video states that by default floor slabs are not meshed in building analysis; slab meshing is optional and enabled through "Include Slab in Building Model".

1. Audio
   Observation

   The speaker says that since analysis is done one floor at a time, a sequential FE floor analysis is required to accurately accumulate column and wall loads from top to bottom story.

2. Diagram
   Observation

   Box 3a states "Use sequential FE floor analyses to chase gravity loads down the structure".

One might think a single FE floor analysis is sufficient to obtain all gravity load effects for columns and walls.

The video explains that FE floor analysis is done one floor at a time, so sequential analyses are required to chase gravity loads down the structure and accurately accumulate column and wall loads.

1. Audio
   Observation

   The speaker explicitly warns that using building analysis without slab meshing is 'wrong for flat slab model' because 'slab loads will be completely lost'.

Believing that a standard 3D frame analysis (columns, beams, walls only) can accurately model a flat slab system.

In a flat slab system, there are no beams to collect and transfer slab loads to the columns. If the slab is not meshed in the analytical model, its weight and live loads have no path to the vertical supports, leading to a fundamentally flawed analysis.

1. Audio
   Observation

   The narrator explicitly contrasts gravity load results from chasdown with lateral load results that must be obtained from building analysis.

2. Caption evidence
   Observation

   The bullet list states Only gives gravity load results and Lateral load results must be from Building analysis.

One might infer that because FE floor analysis models a story with meshed members and slabs, it can also deliver lateral load results directly.

The video states the opposite: FE floor analysis with gravity load chasdown gives only gravity load results, and lateral load results must come from building analysis.

1. Audio
   Observation

   The narrator says Hence, the need to run building analysis first, before performing FE floor analysis.

A user might think the one-story FE floor analysis can be run independently first and the missing lateral information added later.

The clip presents building analysis as the necessary preceding step because it is the source of lateral load results.

1. Audio
   Observation

   The narrator says FE floor analysis is more complicated and longer and is usually used for specific reasons, then recommends building analysis as the first preference.

2. Caption evidence
   Observation

   The final text box recommends Building Analysis as first choice.

Because FE floor analysis meshes columns, walls, beams, and slabs, one might assume it should be the default analysis choice for the whole building workflow.

The video describes it as more complicated and longer, suited to specific sub-frame cases such as slab design, and recommends building analysis as the first overall choice.

1. Audio
   Observation

   Narrator explains the Project Folder is created in a parent folder called Project Data Folder.

Understanding the folder hierarchy (Project Data Folder containing Project Folders) is necessary to correctly navigate the 'Open Project' dialog.

1. Audio
   Observation

   Narrator transitions from warning about folder integrity to recommending Save Project As and Archive Project as safe alternatives.

The constraint that folders cannot be manually renamed necessitates the use of internal software functions (Save Project As, Archive Project) for legitimate renaming and backup operations.

1. Diagram
   Observation

   Box 2a branches off Box 2 with label 'FE Load Decomposition' described as alternative.

2. Audio
   Observation

   Narrator: 'FE load decomposition is the alternative method to yield line slab load calculation.'

Within the load derivation step, the Yield Line (tributary area) approach and FE Load Decomposition represent mutually exclusive computational strategies for the same engineering task.

1. Diagram
   Observation

   Arrows from box 3 to boxes 4 and 5 show the sequence.

2. Audio
   Observation

   The speaker says to check and verify the analytical model after building analysis is successfully completed.

The general building analysis must be completed before the analytical model can be checked and verified.

1. Diagram
   Observation

   Arrows from boxes 4 and 5 to boxes 6.1, 6.2, and 6.3 show the sequence.

2. Audio
   Observation

   The speaker says that after verifying the analytical model is satisfactory, you can proceed to design beams, columns, walls and foundation elements.

Satisfactory verification of the analytical model is required before member design can proceed.

1. Diagram
   Observation

   Box 3a is placed as a side branch connected around boxes 3 and 4.

2. Audio
   Observation

   The speaker says, "There is an alternative to building analysis which is the FE Floor Analysis."

FE Floor Analysis is presented as an alternative to the general building analysis, especially for flat slab or sub-frame behavior.

1. Audio
   Observation

   The speaker contrasts the applicability of the unmeshed method, stating it should 'only be used for beam slab layout'.

The choice between meshing and not meshing slabs depends entirely on the structural system: unmeshed is for beam-slab layouts (where beams carry slab loads), while meshed is mandatory for flat slabs (where columns/walls carry slab loads directly).

1. Audio
   Observation

   The narrator introduces gravity load chasdown as the process needed within FE floor analysis to accumulate gravity loads.

Gravity load chasdown is the procedure applied inside FE floor analysis to handle the accumulation of gravity loads when only one story is analyzed at a time.

1. Audio
   Observation

   The narrator says this chasdown can only provide gravity load result.

2. Caption evidence
   Observation

   The bullet list states Only gives gravity load results.

The output limitation follows from the described chasdown procedure: because the method is built around one-story gravity accumulation, the clip states it yields only gravity load results.

1. Audio
   Observation

   The narrator states lateral load results must be obtained from building analysis and therefore building analysis should be run first.

2. Caption evidence
   Observation

   The bullet list states Lateral load results must be from Building analysis.

Building analysis is contrasted with FE floor analysis by covering lateral loads, which FE floor analysis does not provide in the described workflow.

1. Audio
   Observation

   The narrator explicitly connects the need for lateral results from building analysis to the instruction to run building analysis first before FE floor analysis.

The workflow ordering is derived from the limitation that FE floor analysis does not supply lateral load results.

1. Audio
   Observation

   The narrator gives slab design as an example and justifies it by saying slab design is usually designed only to gravity loads.

The gravity-only output limitation makes FE floor analysis suitable for the stated slab-design use case, because the example is framed around gravity-load-driven design.

1. Audio
   Observation

   Mentions modules are around 5 to 10 minutes each.

1. E-learning Course Format

1. Audio
   Observation

   Explains Project Folder name matches Project Code and no spaces are allowed.

1. ProtaStructure Data File Structure

1. Audio
   Observation

   States default folder is ProtaData plus release version number.

1. Opening a Project in ProtaStructure

1. Audio
   Observation

   Narrator discusses disappearance from Open Project dialog upon renaming.

1. ProtaStructure project folder integrity rules
2. External renaming invalidates project discovery
3. Belief that OS-level renaming is harmless

1. Caption evidence
   Observation

   Slide bullets regarding local hard drive and external/server limitations.

1. Storage and synchronization best practices
2. Expectation that cloud sync improves workflow

1. Caption evidence
   Observation

   Slide text detailing Save Project As, Archive Project, and Open Previous Backup.

1. Manual, archive, and automatic backup procedures
2. Default automatic backup capacity

1. Diagram
   Observation

   Flowchart boxes 2 and 2a describing Yield Line vs FE Load Decomposition.

1. Beam load derivation approaches in modeling workflow
2. FE Load Decomposition as alternative method
3. s120-rel-yieldline-vs-fe

1. Audio
   Observation

   Opening narration explains what FE Load Decomposition captures and where it can be applied.

2. Diagram
   Observation

   Box 2a text is visible.

1. FE Load Decomposition

1. Audio
   Observation

   Speaker states default slab meshing behavior in building analysis.

2. Diagram
   Observation

   Box 3 includes the option text.

1. General building analysis
2. Default slab meshing in building analysis

1. Audio
   Observation

   Speaker lists checks after building analysis.

2. Diagram
   Observation

   Boxes 4 and 5 summarize the checks.

1. Verification of the building analytical model
2. Gravity load balance condition

1. Audio
   Observation

   Speaker explains when FE Floor Analysis is useful and why sequential analysis is needed.

2. Diagram
   Observation

   Box 3a text summarizes the method.

1. FE Floor Analysis

1. Audio
   Observation

   Final narration describes direct slab design options.

2. Diagram
   Observation

   Box 6.4, the coefficient label, and box 3b are visible.

1. Direct slab design path