precast concrete beam design for flexural capacity

huangyhg

precast concrete beam design for flexural capacity
using computer software to generate precast and prestressed concrete beam designs is a usefull tool, but it seems that for some particular cases the design becomes too conservative.
i've run across the following when designing simple span uniformly loaded beams,
&Oslash;mn < 1.2mcr and &Oslash;mn < 2.0mu
this case happens at in the first 1/4 of the beam span each end under a uniform dead and live loading.  i realize that the design is following the code, but does this take it a step too far.  when designing a beam by hand this condition would never be found, but the software finds it becuase it evaluates the loading at smaller length intervals.
i am creating beam tables for our sales department to use, and i've found that when looking at the maximum loading on varying spans for the same cross-section & same strand pattern that as the spans shorten this becomes an issue and limits the loading capacity when using prestress alone, or it requires that developed re-bar be added near end 1/4 spans to generate the capacity requried .  in my opinion this is conservative because you will never get a full uniform live load along the full length of the beam to create that exact loading scenario.
some progams to do not even take this into account (not sure why), but it is a real design issue i've been told by the software company. i am using concise beam (
astructurale,
looks like your approximate hand design methods have been wrong for years then. the checks are necessary.
are you (and the software co.) using aci? if so, what article(s) refers to that particular restraint and what does the code commentary say?  
while software for complex design is extremely useful and time saving, it is the design engineer's responsibility to ensure that the design is safe (and code compliant).  software is a human product and subject to human error.  i have received several updated software versions to fix "bugs" or code related errors.  the discovery of these "bugs" and errors are often the result of user research of the designs produced by the particular software.
i strongly suggest you review those prestressed code checks with which you are not familiar and develop your engineering experience and judgement.  i hope you will find an answer to your question and add to this thread again.
good luck.
rapt - i don't know anyone who would do a hand check for a beam at every 200th of section of a beam to find this.  and it is not really a case of right/wrong, but code intrepretation i think.
***
yes, i am using aci 318-02, and so does the software.  i also know that it is the designer's responsiblity to ensure the deisgn is safe and code compliant.  the designs are safe, and based on my research on the program it is also code compliant.
ok the rest is going to be long, but i want to more clearly explain what i am asking, and give a bit more detail into what i do already know,
i must add that &Oslash;mn > mu for these cases.  this is not an issue where the design could fail.  
from what i have found the applied moment, (wul^2)/8, rises faster  than the cracking moment, sbc[(p/a)+(pe/sb)+fr]-mnc[(sbc/sb)-1].  so there is a point in the beam where &Oslash;mn < 1.2mcr, and also &Oslash;mn < 2.0mu.  at  &Oslash;mn > 2.0mu the cracking moment criteria is waived.  in the beams i have run across this on &Oslash;mn is very close to 2.0mu, but does not exceed it.
also, pci 6th ed handbook states in 4.2.1.4 that the "code requires that the total prestressed and nonprestressed reinforcement be adequate to develop a design strength at least 1.2mcr" and that the "provision is genearlly assumed to apply only at critical flexural sections, and is waived for   
the basic cracking moment req'ment is a means of ensuring that cracking will occur before flexural strength is reached, and by a large enough margin (1.2mcr) so that significant deflection will occur to warn that the strength mn is being approached.
it doesn't matter where the max. flex. req'ment is in regard to this mcr req'ment. if the flexural strength mn is below mcr at any point, then there is no warning if mn is reached.  aci says it's ok if there is no warning crack if you reinforce the section for twice what is needed (2mu).
my opinion is that since the strength of the beam varies along its length, the requirement applies throughout the beam length.
good luck
good point rowe.
well, i have already heard back from technical support for the software. (one of the pluses of this program is fantastic techincal support). apparantely this is debated topic.  he pointed out that other codes (canadian for example) provide more explicit information on this check than aci.  since aci does not provide explicit informaiton pci has made some futher assumptions for designers, which i now belive allows me to consider my design as acceptable since my capacity is close to 2.0mu and the warning does not occur at critical sections as defined in 4.2.1.5 by pci.  in other codes, where it explicitly states that the check must be made for all sections instead of critical sections, the comparision is to 1.3mu or 1.5mu when 1.2mcr is exceeded, which is much less stringent than the 2.0mu set by aci.
thanks for the discussion.  i still welcome more comments.
"in my opinion this is conservative because you will never get a full uniform live load along the full length of the beam to create that exact loading scenario."
how do you know this for sure?

"i must add that &Oslash;mn > mu for these cases.  this is not an issue where the design could fail."
i'm not sure that is exactly true, you're abruptly going from an uncracked to a cracked section in a dynamic fashion. hence the 1.2mcr requirement.
"is it reasonable to say that since the non-compliance, &Oslash;mn < 1.2mcr and &Oslash;mn < 2.0mu, occurs at 0.20*l, and is not located at the point of maximum flexural requirement (the center of the beam), which would be  the "critical" flexural section, then the beam still satisfies the requirement of pci, and it therefore acceptable?"
i would say no, you should be satisfying aci, not a discussion in pci. in the pci quote, note the words "generally assumed".
be aware you are also required to check that your available shear strength is also > 2*vu to waive the 1.2mcr provision. and the critical location for shear is not going to be at midspan.
the interpretation i have received from the australkian code committee on this (it says to check at critical sections) is that any section where the capacity is less than 1.2 mcr is a critical section for minimum capacity and that it therefore needs to be chcecked at all points in a concrete   
yes, that is the way i think aci should be applied as well. i think he was trying to take the critical section as just being at midspan.
rapt
is it just me, or is that an illogical definition of critical section? they should then just state the minimum capacity is required for the full length of the member.
did you get an explaination where the clause 'this requirement may be waived at some critical sections .....provided....will not lead to sudden collapse...' is appropriate to use?
i have assumed that it could be appropriate in cases such as ground beams where the displacement of a member after cracking is limited.
i'll finish by quoting from as3600 supp1-1994;"the intention of this clause is to ensure overall ductile failure of the   
apsix,
i think the definition is logical if you consider why minimum reinforcement is required and the failure type it is trying to negate. yes, the clause probably should have said it was needed everywhere except for the need to define the extra part of the clause you then quote.
yes, the explanation for this part of the clause is that you do not need to supply minimum reinforcement on one face of the beam as long as reinforcement on the other face is sufficient to carry the full load. e.g. you do not need to supply minimum reinforcement over the columns as long as the beam can carry the full loading as a simply supported