The URL can be used to link to this page

Home My WebLink AboutUntitled (138) IPM.Note Solaris Exit Passageway Matt Royer SMTP MRoyer@safebuilt.com Matt Royer SMTP MRoyer@safebuilt.com Martin Haeberle; Mike McGee Solaris Exit Passageway Guys, I have been looking into the passageway of contention that we met about earlier this week. I also spoke to John Plano this afternoon about why he called it a passageway and he response was "he never did". He said at one point he pushed it back to the design team and that's what they designated the space. The short story is that there is no reason for calling this space a passageway. It complies with the definition of "exit discharge". Aside from changing what we call the space, there are other possible implications. If we designate this space as exit discharge from this point on then it eliminates the requirements for opening protection within the space. The door exiting from the passageway leading from the stair would require a rating and that is all. I'm not sure how many "answers" you want to give them. We could have the design team evaluate the possibilities associated with exit discharge vs. passageway. The other option is to mention nothing about the openings protection and allow them to find the exception to opening protection on their own. I don't have the plans for the theater, but John Plano said there is a required exit from the theater that dumps into the passageway. He stated the occupant load from the theater is around 200. We'll have to verify with Chris Gunion. Thoughts on how you would like to respond to the design team? I'm open for suggestions or would be happy to discuss further if you wish. Let me know how you would like to proceed at this point. Thanks Matthew Royer Director of Regional Operations SAFEbuilt, Inc. Toll Free: 877-428-6412 Office: 970-328-1790 Cell: 970-904-0460 matt.royer@safebuilt.com<mailto:matt.royer@safebuilt.com> www.safebuilt.com<http://www.safebuiltcolorado.com> GUYS,IHAVEBEENLOOKINGINTOTHEPASSAGEWAYOFCONTENTIONTHATWEMETABOUTEARLIERTHISWEEKIALSOSPOKETOJOHNPLANO <html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA 00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/ TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel /2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoi nt/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://ww w.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/u dc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/200 6/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com /office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/ex change/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://micr osoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Guys,<o:p></o:p> <o:p> </o:p> I have been looking into the passageway of contention that we met about earlier this week.  I also spoke to John Plano this afternoon about why he called it a passageway and he response was “he never did”.  He said at one point he pushed it back to the design team and that’s what they designated the space.<o:p></o:p> The short story is that there is no reason for calling this space a passageway.  It complies with the definition of “exit discharge”.  <o:p></o:p> <o:p> </o:p> Aside from changing what we call the space, there are other possible implications.  If we designate this space as exit discharge from this point on then it eliminates the requirements for opening protection within the space.  The door exiting from the passageway leading from the stair would require a rating and that is all.  I’m not sure how many “answers” you want to give them.  We could have the design team evaluate the possibilities associated with exit discharge vs. passageway.  The other option is to mention nothing about the openings protection and allow them to find the exception to opening protection on their own.  <o:p></o:p> <o:p> </o:p> I don’t have the plans for the theater, but John Plano said there is a required exit from the theater that dumps into the passageway.  He stated the occupant load from the theater is around 200.  We’ll have to verify with Chris Gunion.<o:p></o:p> <o:p> </o:p> Thoughts on how you would like to respond to the design team?  I’m open for suggestions or would be happy to discuss further if you wish.  Let me know how you would like to proceed at this point.<o:p></o:p> Thanks<o:p></o:p> <o:p> </o:p> Matthew Royer<o:p></o:p> Director of Regional Operations<o:p></o:p> SAFEbuilt, Inc.<o:p></o:p> Toll Free: 877-428-6412<o:p></o:p> Office: 970-328-1790<o:p></o:p> Cell: 970-904-0460<o:p></o:p> <a href="mailto:matt.royer@safebuilt.com">matt.royer@safebuilt.com</a><o:p></o:p> <a href="http://www.safebuiltcolorado.com">www.safebuilt.com</a><o:p></o:p> <o:p> </o:p> </div> </body> </html> Martin Haeberle SMTP MHaeberle@vailgov.com MHaeberle@vailgov.com Martin Haeberle Mike McGee SMTP MMcGee@vailgov.com MMcGee@vailgov.com Mike McGee