<?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>FlowWorks &#187; ADS</title>
	<atom:link href="http://www.flowworks.com/tag/ads/feed" rel="self" type="application/rss+xml" />
	<link>http://www.flowworks.com</link>
	<description>know your data</description>
	<lastBuildDate>Wed, 18 Jan 2012 20:57:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Seattle Public Utilities Joins FlowWorks</title>
		<link>http://www.flowworks.com/blog/flowworks-joins-seattle-public-utilities</link>
		<comments>http://www.flowworks.com/blog/flowworks-joins-seattle-public-utilities#comments</comments>
		<pubDate>Fri, 10 Dec 2010 22:21:50 +0000</pubDate>
		<dc:creator>Craig Kipkie</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[CSO Monitoring]]></category>
		<category><![CDATA[Data Management]]></category>
		<category><![CDATA[ADS]]></category>
		<category><![CDATA[Data Analysis]]></category>
		<category><![CDATA[Flow Monitoring]]></category>
		<category><![CDATA[I&I Analysis]]></category>
		<category><![CDATA[Metadata]]></category>
		<category><![CDATA[Publishing Tools]]></category>
		<category><![CDATA[Rainfall IDF Analysis]]></category>
		<category><![CDATA[Real-time data]]></category>
		<category><![CDATA[Reports]]></category>
		<category><![CDATA[SCADA]]></category>
		<category><![CDATA[Seattle]]></category>
		<category><![CDATA[Secure]]></category>
		<category><![CDATA[Users]]></category>
		<category><![CDATA[Washington]]></category>

		<guid isPermaLink="false">http://www.flowworks.com/?p=1165</guid>
		<description><![CDATA[FlowWorks is proud to announce a new partnership with Seattle Public Utilities and ADS Environmental Services to provide the city’s new flow-monitoring services. As part of the new combined sewer overflow (CSO) program, we will work closely with the city &#8230; <a href="http://www.flowworks.com/blog/flowworks-joins-seattle-public-utilities">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.flowworks.com/blog/flowworks-joins-seattle-public-utilities/attachment/pr_picture1" rel="attachment wp-att-2664"><img src="http://www.flowworks.com/wp-content/uploads/PR_picture1.jpg" alt="" title="PR_picture1" width="491" height="339" class="alignnone size-full wp-image-2664" /></a></p>
<p>FlowWorks is proud to announce a new partnership with Seattle Public Utilities and ADS Environmental Services to provide the city’s new flow-monitoring services. As part of the new combined sewer overflow (CSO) program, we will work closely with the city and ADS to oversee flow monitoring and data management.</p>
<p>SPU chose FlowWorks because of our proven ability to gather data into one place so CSO events can be analyzed quickly, understood and communicated to all users. Operating in near-real time, SPU’s new FlowWorks service easily loads two years of 5-minute data from the server in under 6 seconds. Already the city is enjoying better collaboration, faster problem solving and quicker response times.</p>
<p>Other highlights our service brings to the new partnership include:</p>
<p>•	Secure, internet-based platform<br />
•	Used for gathering, analyzing and managing water, sewer, rainfall and other remote data Hardware neutral<br />
•	Accepts data from any flow meter or manufacturer&#8217;s data system, as well as SCADA, Historic and manual data<br />
•	Includes powerful graphing engine, storage for all forms of meta data, event alarms and analysis capabilities for I&#038;I and rainfall IDF</p>
<p>ADS develops and provides technology-based flow measurement products and services for the water, wastewater and hydroelectric industries. The firm is a veteran of working with SPU and has provided excellent flow servicing, engineering, and a high degree of data integrity to the utility for the past five years. When the contract came up for re-bid, SPU leadership recognized the need to add a robust data-delivery and work order management system to the program—FlowWorks was a natural choice. Already the team of FlowWorks and ADS has proven to be exactly what SPU was looking for and together we help to build on past success with SPU.</p>
<p>FlowWorks continually proves to be the platform of choice for municipalities, utilities and industrial clients seeking to manage, analyze and understand large quantities of remote data quickly, and securely communicate the results to a broad audience.</p>
<p>For more information, please visit our website at <a href="http://www.flowworks.com">www.flowworks.com</a> or to learn more about ADS visit <a href="http://www.adsenv.com">www.adsenv.com</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.flowworks.com/blog/flowworks-joins-seattle-public-utilities/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Data Loggers for Remote Data Collection Systems: Which One to Choose?</title>
		<link>http://www.flowworks.com/blog/data-loggers-for-remote-data-collection-systems-which-one-to-choose</link>
		<comments>http://www.flowworks.com/blog/data-loggers-for-remote-data-collection-systems-which-one-to-choose#comments</comments>
		<pubDate>Mon, 30 Nov 2009 18:25:53 +0000</pubDate>
		<dc:creator>Jason Vine</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Remote Monitoring]]></category>
		<category><![CDATA[Training]]></category>
		<category><![CDATA[ADS]]></category>
		<category><![CDATA[Campbell Scientific]]></category>
		<category><![CDATA[Climate Station]]></category>
		<category><![CDATA[Data Loggers]]></category>
		<category><![CDATA[Hach]]></category>
		<category><![CDATA[Isco]]></category>
		<category><![CDATA[Marsh McBirney]]></category>
		<category><![CDATA[Satellite]]></category>
		<category><![CDATA[Telemetry]]></category>
		<category><![CDATA[Telog]]></category>

		<guid isPermaLink="false">http://www.flowworks.com/?p=880</guid>
		<description><![CDATA[I am a practising Professional Egineer who does A LOT of data collection applications, both for my clients as well as for the 150 or so employee needs within my own firm. When someone asks me what kind of data &#8230; <a href="http://www.flowworks.com/blog/data-loggers-for-remote-data-collection-systems-which-one-to-choose">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.flowworks.com/wp-content/uploads/cassette-tape.jpg" alt="cassette tape" title="cassette tape" width="500" height="333" class="alignnone size-full wp-image-1867" /></p>
<p>I am a practising Professional Egineer who does A LOT of data collection applications, both for my clients as well as for the 150 or so employee needs within my own firm.  When someone asks me what kind of data logger they should use, I always start by asking them where the data logger will be located, and what it will be used for.  There are plenty of choices!  Here’s a few of the systems and applications that are currently connected to FlowWorks.</p>
<h2>Telog</h2>
<p>We have some small water and sewer treatment plants that talk to FlowWorks using Telog’s wireless 1XRTT modem.  We like the<a href="http://www.telog.com" target="_blank"> Telog products</a> (particularly the 3307 and 3314), as these units are very reliable and they have some very flexible telemetry options (including dialup phone, wireless, and direct Ethernet connections).</p>
<h2>ISCO</h2>
<p><a href="http://www.isco.com/" target="_blank">ISCO 2150 area-velocity meters</a> in sanitary sewers come in via ISCO’s wireless 1XRTT system.  The ISCO’s are purpose-built and hence not as flexible as the Telog wireless system, but the ISCO’s are compact units that generally get the job done well enough.</p>
<h2>Marsh McBirney</h2>
<p>There are a few <a href="http://www.marsh-mcbirney.com/p_oc_flodar.html" target="_blank">Marsh McBirney FloDar’s</a> connected to FlowWorks.  These units were plugged into the Telog RU33 product, which acts as a data recording and telemetry module for the FloDar.</p>
<h2>ADS</h2>
<p>There is an <a href="http://www.adsenv.com" target="_blank">ADS FlowShark</a> connected to FlowWorks.  We don’t have a lot of experience with these yet, but our client out East seems to be happy enough with the unit.  It uses wireless 1XRTT just like the Telog and ISCO systems.</p>
<h2>Satellite Stations</h2>
<p>We have remote stations that use satellite because there is no other option where these sites are located.  Right now we have <a href="http://www.campbellsci.ca/" target="_blank">Campbell Scientific</a> and <a href="http://www.unidata.com.au" target="_blank">Unidata Neon</a> systems connected.  We know that Campbell Scientific systems have been around for a long time and have a proven track record.  The Neons also seem to be holding up well.</p>
<p>The bottom line is that there are several ways you can do any particular data collection application.  We are always doing new applications, and we keep on top of what’s out there on the market, what works well and what doesn’t.  Feel free to <a href="../about/demo">ask us for a bit of advice</a> the next time you are looking to do a new data collection application!  We work with an expanding list of logger manufacturers, and we provide unbiased advice.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.flowworks.com/blog/data-loggers-for-remote-data-collection-systems-which-one-to-choose/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

