Steel design using STAAD

Hi,

I seem to have a problem while performing steel design in STAAD.Pro... Kinldly correct me if my approach is wrong..

I've given two sets of steel design parameters.. Set 1 for Design.. Set 2 primarily for deflection checking with DFF, DJ1, DJ2  commands..

I've used LOAD LIST command to ensure Design is done with factored load combinations & deflection checking is done for service load combinations..

But once I run the analysis & check, both design & deflection check is done for the latest set of parameters & load list that is specified. By this I mean, if Load List 10 to 13(Factored Loads) with relevant design parameters is specified at the end, both deflection check & design is done for the same.

 

I've attached the STAAD file for your reference.

Kindly Clarify.

 

Regards,

Arun.

Metering Platform.zip
Parents
  • Please check output file thoroughly. 2-sets of steel design outputs are available, one for loads 10 to 13 and another for 20 to 23.
  • Hi..

    Thanks for your posting.. I failed to notice it.

    But if u double click on a member & see the Steel Design tab, there the design ratio & the critical load specified are for the latest set of parameters. Isn' it??

    I  generally check the interaction ratio n the governing load case this way.. so was cught unaware..

    Anyway is this right.. the value in the steel design tab should be the critical case in the sense if design governs, it should be showing load case 10 to 13 & if deflection governsit should be showing load case 20 to 23..

     

    Regards,

    Arun.

  • Arun,

    Your implementation of the LOAD LIST commands is correct.  Your are performing a code check (WITHOUT deflection checking) for your loads 10 to 13.  Then you are performing another code check (INCLUDING deflection checking for the specified beams) for loads 20 to 23.

    The thing to keep in mind is that code checking will ALWAYS be evaluating stresses.  The only decision we have is whether or not to include a deflection check IN ADDITION TO evaluating stresses.

    In your particular situation, the result was very easy to interpret, because the second CHECK CODE ALL command only revealed four failing members, and they all failed on the basis of deflection.  So you got a clean result that you can address, for instance, by increasing the moments of inertia of the four failing members and then rerunning your model to verify that the new sizes work for stress on the basis of factored loads and for deflection on the basis of service loads.

    Keep in mind that the Prot Processor will always indicate the results of the LAST analysis (in a multiple analysis model) and the last CHECK CODE or SELECT command if more than one exists in the model.  That's why you are currently seeing beam design results that are all based on load conditions 20 to 23 in the post processor.

    Cheers,

    Chris



Reply
  • Arun,

    Your implementation of the LOAD LIST commands is correct.  Your are performing a code check (WITHOUT deflection checking) for your loads 10 to 13.  Then you are performing another code check (INCLUDING deflection checking for the specified beams) for loads 20 to 23.

    The thing to keep in mind is that code checking will ALWAYS be evaluating stresses.  The only decision we have is whether or not to include a deflection check IN ADDITION TO evaluating stresses.

    In your particular situation, the result was very easy to interpret, because the second CHECK CODE ALL command only revealed four failing members, and they all failed on the basis of deflection.  So you got a clean result that you can address, for instance, by increasing the moments of inertia of the four failing members and then rerunning your model to verify that the new sizes work for stress on the basis of factored loads and for deflection on the basis of service loads.

    Keep in mind that the Prot Processor will always indicate the results of the LAST analysis (in a multiple analysis model) and the last CHECK CODE or SELECT command if more than one exists in the model.  That's why you are currently seeing beam design results that are all based on load conditions 20 to 23 in the post processor.

    Cheers,

    Chris



Children
  • Thanks Chris !!!

    Till this date after every analysis, i used to check the members which have failed by using the SELECT| BY SPECIFICATION| ALL FAILED BEAMS option.

    This is a good knowhow. So in a multiple anlaysis model, we'll have to evaluate the design stresses by checking the output file only right?

    I thought the post processor would always give the results for the most critical case, considering both service & design load combinations.. Is there any way by which this can be achieved?? It'd save considerable time..

    Or is it possible to include two list commands for different parameters within the same set say PARAMETER 1?? Sorrry if I'm wrong, but just curious..

    Regards,

    Arun.

  • Arun,

     

    These are some excellent points, so let's expand on this just a bit for the benefit of others who may not be aware of some of these concepts.

    First, to reiterate from the last post, in a multiple analysis model, all results in the Post Processor will always be based on the last analysis.  If there is ever a need to observe results from analyses other than the last analysis, those results can be viewed in the output file.

    Second, the Unity Check sub-tab of the Beam tab in the Post Processor always reports the results of the last CHECK CODE or SELECT command in the model.  Again, if there is ever a need to observe design results from code checks other than the last check, those results can be viewed in the output file.

    Next, be aware that SELECT > BY SPECIFICATION > ALL FAILED BEAMS selects all members whose utilization ratio exceeds the upper limit on the "Pass" range as established by the user.  (The "Pass" range is range #2 in the Basic Diagram version of the Design Results tab of the Diagrams dialog.)  The important thing to understand here is that this gives the user the flexibility to alter the interpretation of the unity check ratio values.  This means that if the user establishes a value of 0.95 as the upper limit on the "Pass" range on the Design Results tab, then SELECT > BY SPECIFICATION > ALL FAILED BEAMS will select members with unity check values that exceed 0.95.  This is fundamentally different than viewing the design results in the output file, which always base the PASS/FAIL indication on a comparison of the actual unity ratio with an upper limit of 1.0 (potentially modified by parameters such as RATIO and OVR).

    Finally, since there is significant value in being able to use the Post Processor to review design results, it may be more effective to separate a multiple analysis run into a series of single analysis runs by remming out selected portions of the model at a time.

    Cheers ,

    Chris



  • Chris !!! 

    You threw a lot of light into the subject of using post processor!! Thanks !!

    I have a clear picture now about the options.

    I'd like to put in one more point, pertinent to my case atleast!!

    Most of times I require a multiple analysis model, to check for deflection & evaluation of design stresses.

    So in lieu of this, if a specific tab or option dedicated to check deflection alone for the specified members in a model is available, it'd do a lot of good. Because deflection check is done for service (unit) load combinations almost all the time. So Irrespective of a multiple analysis model for evaluating stresses (with factored load combinations), deflection check can be taken care of separately every time.

    In such a case I'd use the post processor all the times to check for stresses, and a dedicated sub tab for cheking deflection under the BEAM tab in post processor can be used for deflection checking.

    It'd ensure that DESIGN can be used to evaluate just stresses and the option of whether to have deflection cheeck or not, in the same is eliminated & done separately.

     Just a thought !! 

     Thanks again for your wonderful posting !!

     

    Regards,

    Arun.

  • Glad to hear that we may have shed some light with this thread.

    Feel free to submit that enhancement request, too.  You can use the Service Ticket manager, and choose the option near the top of the ST form to indicate that you are submitting the ticket to "Request Change / New Feature".

    Cheers,

    Chris



  • Hello Chris/Arun,

    Thank you for this post, it looks really interesting. I have just one question and problem:

    Question:
    This is similar to Arun's question - "Is it possible to include two list commands for different parameters within the same set say PARAMETER 1" - I need to do both design check and deflection check under the same sets of loads, so I think it should be fine.

    Problem:
    I am using the Select/Group commands to have STAAD design steel members for a conveyor system. After Select/Group I have included a Perform Analysis and Design Check Commands, which the program does against the new set of cross sections that it itself picked. But still the design check in Post Processor/Beams/Unity Check shows Failing members, and not just by a little. Some members have ratios over 2.0! How can sections chosen by Staad itself not pass the design check, while Staad could have chosen even higher sections.

    I did run the commands twice like below, but still nothing:
    *First cycle
    SELECT ALL
    GROUP MEMB 1 3 4
    GROUP MEMB 5 6 7
    PERFORM ANALYSIS
    CHECK CODE ALL
    *
    *Second Cycle
    SELECT ALL
    GROUP MEMB 1 3 4
    GROUP MEMB 5 6 7
    PERFORM ANALYSIS
    CHECK CODE ALL

    Could you check if my design commands are in the right order? Please find the file in this dropbox link as I did not know how to upload it:

    https://dl.dropboxusercontent.com/u/44309793/PCR%203D%20%20-%20Comb%20TH%20Loads%20(D-drive).rtd

    I would very appreciate any help!

    Many Thanks,

    Skerdi