<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SPAN &amp;amp; Physical Member commands in SACS</title><link>https://communities.bentley.com/products/offshore/f/maxsurf-moses-sacs-forum/157563/span-physical-member-commands-in-sacs</link><description>Hello all, 
 There are some ambiguities for me about the use of SPAN and PHYSICAL MEMBER commands in SACS. Consider the following simple senario: 
 Imagine we have a main deck beam (say HEB600), on top of which stringer beams( say IPE200) are running</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: SPAN &amp; Physical Member commands in SACS</title><link>https://communities.bentley.com/thread/469471?ContentTypeID=1</link><pubDate>Fri, 06 Jul 2018 07:50:57 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:b99e664d-224d-446c-aa15-51792ee3e176</guid><dc:creator>Wen Meng</dc:creator><description>&lt;p&gt;I guess you need to do two separate analysis, one for beam design without SPAN definition and one for span deflection check. And what design code are you using?&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Normally physical member is generated&amp;nbsp;by SACS program for reference(commented line at bottom of model)&amp;nbsp;but it&amp;nbsp;has no&amp;nbsp;effect to member check. For example&amp;nbsp;for jacket all leg members along one pile will be combine to one physical member.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>