<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>TRUSYS, Inc.</title>
	<atom:link href="https://trusys.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://trusys.com</link>
	<description>Protecting Your Value</description>
	<lastBuildDate>Fri, 12 Apr 2019 14:57:18 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.7.1</generator>
	<item>
		<title>Design Tip #2:  3D Design Tools</title>
		<link>https://trusys.com/3d-design-tools/</link>
					<comments>https://trusys.com/3d-design-tools/#respond</comments>
		
		<dc:creator><![CDATA[Mike Strong]]></dc:creator>
		<pubDate>Wed, 10 Apr 2019 18:34:38 +0000</pubDate>
				<category><![CDATA[Design Tip Videos]]></category>
		<category><![CDATA[Physical Security Design]]></category>
		<category><![CDATA[3D tools]]></category>
		<category><![CDATA[AXIS]]></category>
		<category><![CDATA[physical security]]></category>
		<category><![CDATA[REVIT]]></category>
		<category><![CDATA[security design]]></category>
		<category><![CDATA[SketchUp]]></category>
		<guid isPermaLink="false">https://trusys.com/?p=2675</guid>

					<description><![CDATA[We hope these design tips will enhance your projects and deliver more value to your clients. As promised, we will do a deeper dive into using 3D design tools for physical security in Revit and SketchUp. In our first example of a reception area, I am using the AXIS plug-in for Revit 2019. For this [&#8230;]]]></description>
		
					<wfw:commentRss>https://trusys.com/3d-design-tools/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Design Tip #1:  Operational Requirements</title>
		<link>https://trusys.com/operational-requirements/</link>
					<comments>https://trusys.com/operational-requirements/#comments</comments>
		
		<dc:creator><![CDATA[Mike Strong]]></dc:creator>
		<pubDate>Fri, 01 Mar 2019 13:59:09 +0000</pubDate>
				<category><![CDATA[Design Tip Videos]]></category>
		<category><![CDATA[Physical Security Design]]></category>
		<category><![CDATA[AXIS]]></category>
		<category><![CDATA[physical security]]></category>
		<category><![CDATA[pixel density]]></category>
		<category><![CDATA[REVIT]]></category>
		<category><![CDATA[security cameras]]></category>
		<category><![CDATA[security design]]></category>
		<category><![CDATA[SketchUp]]></category>
		<guid isPermaLink="false">https://trusys.com/?p=2607</guid>

					<description><![CDATA[This is the first in a series of design tips that we hope will enhance the security design of your projects, and help you deliver more value to your clients. The camera imager size (2 MP, 4 MP, 5 MP, etc.) and lens focal length should always align with the viewing requirements, to ensure performance [&#8230;]]]></description>
		
					<wfw:commentRss>https://trusys.com/operational-requirements/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>
