<?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>BCS Innovations</title>
	<atom:link href="http://www.bcsinnovations.com.au/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bcsinnovations.com.au</link>
	<description>Your partner in product development</description>
	<lastBuildDate>Mon, 30 Jan 2012 04:46:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>&#8216;InfoLithium&#8217; Batteries: Genuine .v. After-market</title>
		<link>http://www.bcsinnovations.com.au/1230/infolithium-batteries-genuine-v-after-market/</link>
		<comments>http://www.bcsinnovations.com.au/1230/infolithium-batteries-genuine-v-after-market/#comments</comments>
		<pubDate>Mon, 12 Dec 2011 05:30:50 +0000</pubDate>
		<dc:creator>Mac</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://www.bcsinnovations.com.au/?p=1230</guid>
		<description><![CDATA[Have you ever had to choose between brand name authentic batteries and apparently identical after-market alternatives? We recently designed a product that is compatible with the Info-Lithium protocol that the Sony Video Camera batteries use – so as part of product validation we reviewed the functionality with several alternative batteries. The results were quite a [...]]]></description>
			<content:encoded><![CDATA[<p><a class="lightbox" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;" title="SonyBatteryCompare" href="http://www.bcsinnovations.com.au/wp-content/uploads/2011/12/SonyBatteryCompare1-300x148.png"><img class="alignleft size-medium wp-image-1115" title="SonyBatteryCompare" src="http://www.bcsinnovations.com.au/wp-content/uploads/2011/12/SonyBatteryCompare1-300x148.png" alt="" width="300" height="148" /></a>Have you ever had to choose between brand name authentic batteries and apparently identical after-market alternatives? We recently designed a product that is compatible with the Info-Lithium protocol that the Sony Video Camera batteries use – so as part of product validation we reviewed the functionality with several alternative batteries.</p>
<p>The results were quite a surprise.<span id="more-1230"></span></p>
<p>We compared the product functionality with the Sony NP-QM91D (about $300 from the official local distributor and $30 from other sources) and cheaper after-market alternatives (about $10). All had allegedly identical specifications, and all used the Info-Lithium protocol. This protocol permits the battery to communicate with its device over I²C to better regulate the charging and power usage.  It also reports back additional information, such as internal temperature, which is useful for hazard reduction as the charger can stop charging when the battery starts overheating.</p>
<p>We found that some cheap after-market batteries are semi-compatible with the Info-Lithium technology.  While they appear to work with Sony video cameras and chargers, they don’t report their status like remaining capacity and internal temperature correctly. We monitored the reported capacity of a few types of after-market batteries versus Sony authentic batteries during full charge and discharge cycles. The official Sony battery reported capacity drops quite linearly when discharging at a constant current while the after-market ones drops sharply after a certain point.</p>
<p><a class="lightbox" title="DischargeGraph" href="http://www.bcsinnovations.com.au/wp-content/uploads/2011/12/DischargeGraph.png"><img class="size-medium wp-image-1264 alignnone" style="border-width: 1px; border-color: black; border-style: solid;" title="DischargeGraph" src="http://www.bcsinnovations.com.au/wp-content/uploads/2011/12/DischargeGraph.png" alt="" /></a></p>
<p>Another surprise was that some cheap after-market batteries simply <strong><span style="text-decoration: underline;">faked the reporting of their internal temperature</span></strong> as they lacked a temperature sensor at all.<br />
This meant that our product&#8217;s hazards analysis couldn&#8217;t rely on this feature being present – we had to take other precautions.</p>
<p><a class="lightbox" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;" title="100_3619 - With Caption" href="http://www.bcsinnovations.com.au/wp-content/uploads/2011/12/100_3619-With-Caption.jpg"><img class="alignleft size-medium wp-image-1262" style="border-width: 1px; border-color: black; border-style: solid;" title="100_3619 - With Caption" src="http://www.bcsinnovations.com.au/wp-content/uploads/2011/12/100_3619-With-Caption-300x225.jpg" alt="" width="300" height="225" /></a>When it comes to the mechanical strengths, the genuine Sony batteries also had better quality than the after-market ones we bought for test purposes. On one batch of after-market batteries the capacity indicator label fell off within a couple of weeks. We also disassembled a few after-market and genuine batteries to find out the differences inside the enclosure. We found that after-market batteries use glue and foams to hold the cells together while genuine ones have a plastic frame for this purpose which obviously can stand wider range of temperature change.</p>
<p>As a consumer, it is always up to you to decide on whether you will go with the more expensive choice of a genuine battery or risk an after-market battery.</p>
<p>As designers though, we need to be careful because no matter what warnings we put in the manual some users will put in incorrect batteries &#8211; and our products need to remain safe in those circumstances.</p>
<hr />
]]></content:encoded>
			<wfw:commentRss>http://www.bcsinnovations.com.au/1230/infolithium-batteries-genuine-v-after-market/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Analysis and Design of an Exoskeleton Arm &#8212; Dec 21, 2011</title>
		<link>http://www.bcsinnovations.com.au/1223/analysis-and-design-of-an-exoskeleton-arm-dec-21-2011/</link>
		<comments>http://www.bcsinnovations.com.au/1223/analysis-and-design-of-an-exoskeleton-arm-dec-21-2011/#comments</comments>
		<pubDate>Tue, 06 Dec 2011 22:56:07 +0000</pubDate>
		<dc:creator>jpouladi</dc:creator>
				<category><![CDATA[Seminar]]></category>

		<guid isPermaLink="false">http://www.bcsinnovations.com.au/?p=1223</guid>
		<description><![CDATA[The analysis and design of an exoskeleton arm with a non captive rotary joint. I looked at the range or motion for different exoskeleton configurations and based on my analysis, designed an elbow and rotary shoulder joint to prevent any restrictions to the user&#8217;s normal range of motion. Presentation by Trevor Sunderland When      [...]]]></description>
			<content:encoded><![CDATA[<p>The analysis and design of an exoskeleton arm with a non captive rotary joint. I looked at the range or motion for different exoskeleton configurations and based on my analysis, designed an elbow and rotary shoulder joint to prevent any restrictions to the user&#8217;s normal range of motion.</p>
<p><span id="more-1223"></span></p>
<p>Presentation by Trevor Sunderland</p>
<p><strong><strong><strong>When</strong>            </strong></strong>December 21, 2011, 12:45PM<strong><strong><br />
<strong>Location</strong>       </strong></strong>Unit 4, Level One, 2-6 Orion Road, Lane Cove NSW 2066 Australia</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bcsinnovations.com.au/1223/analysis-and-design-of-an-exoskeleton-arm-dec-21-2011/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Test Systems: The Intelligent Distributed Approach &#8212; Nov 30, 2011</title>
		<link>http://www.bcsinnovations.com.au/1213/test-systems-the-intelligent-distributed-approach-powered-by-ni-pxi-cvs-labview-teststand-nov-30-2011/</link>
		<comments>http://www.bcsinnovations.com.au/1213/test-systems-the-intelligent-distributed-approach-powered-by-ni-pxi-cvs-labview-teststand-nov-30-2011/#comments</comments>
		<pubDate>Tue, 15 Nov 2011 04:59:15 +0000</pubDate>
		<dc:creator>jpouladi</dc:creator>
				<category><![CDATA[Seminar]]></category>

		<guid isPermaLink="false">http://www.bcsinnovations.com.au/?p=1213</guid>
		<description><![CDATA[My experience with “Intelligent Distributed Test Systems” in the Medical Device Industry &#8211; using NI PXI, CVS, LabView &#38; TestStand. Presentation by Ralph Dick &#8211; General Manager (NVSI) When            November 30, 2011, 12:45PM &#8211; 30 minute quick seminar Location       Unit 4, Level One, 2-6 Orion Road, Lane Cove NSW 2066 Australia]]></description>
			<content:encoded><![CDATA[<div>
<p>My experience with “Intelligent Distributed Test Systems” in the Medical Device Industry &#8211; using NI PXI, CVS, LabView &amp; TestStand.</p>
<p><span id="more-1213"></span></p>
</div>
<p>Presentation by Ralph Dick &#8211; General Manager (NVSI)</p>
<p><strong><strong><strong>When</strong>            </strong></strong>November 30, 2011, 12:45PM &#8211; 30 minute quick seminar<strong><strong><br />
<strong>Location</strong>       </strong></strong>Unit 4, Level One, 2-6 Orion Road, Lane Cove NSW 2066 Australia</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bcsinnovations.com.au/1213/test-systems-the-intelligent-distributed-approach-powered-by-ni-pxi-cvs-labview-teststand-nov-30-2011/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>When Field Firmware upgrades go bad &#8230;</title>
		<link>http://www.bcsinnovations.com.au/1106/when-field-firmware-upgrades-go-bad/</link>
		<comments>http://www.bcsinnovations.com.au/1106/when-field-firmware-upgrades-go-bad/#comments</comments>
		<pubDate>Mon, 24 Oct 2011 08:00:51 +0000</pubDate>
		<dc:creator>Mac</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://www.bcsinnovations.com.au/?p=1106</guid>
		<description><![CDATA[The ability to update the firmware of an embedded device in the field has made a big difference to devices. New functions, bug corrections, improved functionality &#8211; it all can be done without having to rebuild the hardware or be on site to plug in a programming cable. If the device is on a network [...]]]></description>
			<content:encoded><![CDATA[<p><a class="lightbox" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;" title="CarTracking" href="http://www.bcsinnovations.com.au/wp-content/uploads/2011/10/CarTracking2.jpg"><img class="alignleft size-medium wp-image-1115" title="CarTracking" src="http://www.bcsinnovations.com.au/wp-content/uploads/2011/10/CarTracking2-219x300.jpg" alt="" width="219" height="300" /></a>The ability to update the firmware of an embedded device in the field has made a big difference to devices.</p>
<p>New functions, bug corrections, improved functionality &#8211; it all can be done without having to rebuild the hardware or be on site to plug in a programming cable.</p>
<div></div>
<div>If the device is on a network the customer doesn&#8217;t even need to be aware of the update &#8211; it can happen automatically without anyone even touching the device.</div>
<div></div>
<div>But what happens when one of those automatic field firmware upgrades goes bad?</div>
<div></div>
<div><a href="http://www.precisiontracking.com.au/" onclick="pageTracker._trackPageview('/outgoing/www.precisiontracking.com.au/?referer=');"><strong><span style="text-decoration: underline;">Precision Tracking</span></strong></a> recently had this happen to them.   They have a tracking &amp; security system for vehicles &#8211; if you want to see how much these systems have developed in the past few years just see the beauty of their web interface here:</div>
<div></div>
<div><span class="Apple-style-span" style="color: blue; font-family: verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif, serif; font-size: x-small;"><a href="http://interface.precisiontracking.com.au/?uid=ils" onclick="pageTracker._trackPageview('/outgoing/interface.precisiontracking.com.au/?uid=ils&amp;referer=');"><strong><span style="text-decoration: underline;">http://interface.precisiontracking.com.au/?uid=ils</span></strong></a></span></div>
<div></div>
<div>The data on that web interface is deliberately public &#8211; these are real vehicles set to make the data publicly available to demonstrate how truly impressive these kinds of systems are.</div>
<div>
<p>The hardware is fairly straight forward &#8211; it used  well characterised GPS modules that provide live updates via Telstra&#8217;s Next G network.  The hardware was chosen for reliability after a great deal of searching and comparison.</p>
</div>
<div>
<p>During the initial hardware evaluation a minor timing bug in the module was spotted &#8211; the signal lines to the engine immobiliser had a delay of 1 second &#8211; which prevented the proper operation of the immobilizer.  This was resolved by a simple hardware correction &#8211; wiring that signal into a different part of the circuit.</p>
</div>
<div>Then in April of 2011 disaster struck.  A firmware upgrade sent out over the Telstra network corrected the minor timing bug.   That meant that the hardware correction was now compensating for a bug that no longer existed &#8211; so the engine immobiliser function was disabled.</div>
<div>
<p><strong>A single invisible firmware update had broken the product for over 50 vehicles spread across NSW and the ACT &#8211; about 802,000 km².</strong></p>
</div>
<div>What can be done in cases like this?  Well, in the case of Precision Tracking, they did the only thing they could &#8211; visit every single affected unit and physically modify the hardware.</div>
<div></div>
<div>It took them 2 weeks to work through every installation to correct the issue, so I though I&#8217;d find out what they learned from this.</div>
<div></div>
<div>
<p>I spoke with Nathan Parrott (one of the founders of the company and an ex-BCS employee) and asked him a few questions about the experience :<strong>Question: What lessons did you learn from this?</strong></p>
<p>Answer:</p>
<p><a class="lightbox" title="quote_start" href="http://www.bcsinnovations.com.au/wp-content/uploads/2011/09/quote_start.png"><img class="alignleft size-full wp-image-781" title="quote_start" src="http://www.bcsinnovations.com.au/wp-content/uploads/2011/09/quote_start.png" alt="" width="16" height="16" /></a></p>
<blockquote><p><em>#1 &#8211; Don&#8217;t ever try to fix someone else&#8217;s problem with a work around.  When they get around to fixing their problem it could conflict with your &#8216;fix&#8217;</em></p>
<p><em>#2 &#8211; Acknowledge the fact that no Beta release will ever be problem free and it should take 6 months of solid testing for any piece of hardware</em></p>
<p><em>If you need a shorter turnaround to land a sale &#8211; make sure that it&#8217;s with worth the pain.  If you are going to do this &#8211; make sure the customer is in easy to access &amp; that they are aware that it is a Beta .. that there may be teething problems.  When things do go wrong, they will be more understanding.</em></p>
<p><em>#3 &#8211; Budget enough to sort out these issues out in the Beta release of your product  <a title="quote-end" href="http://www.bcsinnovations.com.au/wp-content/uploads/2011/09/quote-end.png"><img title="quote-end" src="http://www.bcsinnovations.com.au/wp-content/uploads/2011/09/quote-end.png" alt="" width="16" height="16" /></a><a class="lightbox" title="quote-end" href="http://www.bcsinnovations.com.au/wp-content/uploads/2011/09/quote-end.png"><br />
</a></em></p></blockquote>
<p><strong>Question: What did you feel Precision Tracking did right for this issue?</strong></p>
<p>Answer:</p>
<p><a title="quote_start" href="http://www.bcsinnovations.com.au/wp-content/uploads/2011/09/quote_start.png"><img title="quote_start" src="http://www.bcsinnovations.com.au/wp-content/uploads/2011/09/quote_start.png" alt="" width="16" height="16" /></a></p>
<blockquote><p><em>#1 -Don&#8217;t try and cover up problems &#8211; the moment you become aware of it you need to inform the affected customers.</em></p>
<p><em>#2 &#8211; Consider the ways a product can fail and ensure that it fails safe.  It is tempting in vehicle security systems to have the product fail &#8216;secure&#8217; rather than fail &#8216;safe&#8217;.  If a product fails &#8216;secure&#8217; then a firmware failure could lock all the car doors and turn off the engine while you are barrelling down the freeway at 110 km/hr.  We made sure our product would fail &#8216;safe&#8217; &#8211; so when the firmware upgrade caused problems then people still had use of their cars &#8211; that reduced the impact and made customers a lot more patient.</em></p>
<p><em>#3 &#8211; Have fall-back options. In this case the fall-back option was to roll back the firmware fix and then incrementally update the firmware only on units as we correct the hardware.   This wasn&#8217;t necessary, though, as the system failure still meant customers had use of their vehicles &#8211; and so were willing to be patient and have the real update rolled out to them.  <a title="quote-end" href="http://www.bcsinnovations.com.au/wp-content/uploads/2011/09/quote-end.png"><img title="quote-end" src="http://www.bcsinnovations.com.au/wp-content/uploads/2011/09/quote-end.png" alt="" width="16" height="16" /></a></em></p></blockquote>
<div>I think the main thing I learned from this discussion is how much work we need to be prepared for issues in initial Beta releases of products.Even after beta testing is complete the initial rollout can cause major headaches simply because the beta testers weren&#8217;t representative of a major group of users.  For example &#8211;  one <a href="http://johnaugust.com/2011/fdx-reader-1-0-2" onclick="pageTracker._trackPageview('/outgoing/johnaugust.com/2011/fdx-reader-1-0-2?referer=');"><strong><span style="text-decoration: underline;">iPad application</span></strong></a> with hundreds of happy beta users had a major issue that was never noticed &#8211; simply because all the Beta users were in the USA and so the software had never been used with the page size set to A4 paper.</div>
</div>
<div></div>
<div>
<hr />
<p><span class="Apple-style-span" style="font-size: xx-small;">This blogpost can be freely republished under the <a href="http://creativecommons.org/licenses/by-sa/3.0/" onclick="pageTracker._trackPageview('/outgoing/creativecommons.org/licenses/by-sa/3.0/?referer=');">CC Sharealike</a> license, with appropriate credit to BCS Innovations.</span></p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.bcsinnovations.com.au/1106/when-field-firmware-upgrades-go-bad/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PLC Systems &#8212; Nov 2, 2011</title>
		<link>http://www.bcsinnovations.com.au/1024/plc-systems-3/</link>
		<comments>http://www.bcsinnovations.com.au/1024/plc-systems-3/#comments</comments>
		<pubDate>Mon, 10 Oct 2011 04:09:48 +0000</pubDate>
		<dc:creator>jpouladi</dc:creator>
				<category><![CDATA[Seminar]]></category>

		<guid isPermaLink="false">http://www.bcsinnovations.com.au/?p=1024</guid>
		<description><![CDATA[My experience with PLCs and what I’ve learned about them, and why I like Omron over Allen-Bradley systems. Presentation by Trevor Sunderland When            November 2, 2011, 12:45PM Location       Unit 4, Level One, 2-6 Orion Road, Lane Cove NSW 2066 Australia]]></description>
			<content:encoded><![CDATA[<p>My experience with PLCs and what I’ve learned about them, and why I like Omron over Allen-Bradley systems.<img src="http://www.bcsinnovations.com.au/wp-includes/js/tinymce/plugins/wordpress/img/trans.gif" alt="" /><span id="more-1024"></span></p>
<p>Presentation by Trevor Sunderland</p>
<p><strong><strong><strong>When</strong>            </strong></strong>November 2, 2011, 12:45PM<strong><strong><br />
<strong>Location</strong>       </strong></strong>Unit 4, Level One, 2-6 Orion Road, Lane Cove NSW 2066 Australia</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bcsinnovations.com.au/1024/plc-systems-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PCB Encapsulation &#8212; Oct 20, 2011</title>
		<link>http://www.bcsinnovations.com.au/1071/pcb-encapsulation-oct-18-2011/</link>
		<comments>http://www.bcsinnovations.com.au/1071/pcb-encapsulation-oct-18-2011/#comments</comments>
		<pubDate>Thu, 06 Oct 2011 05:35:10 +0000</pubDate>
		<dc:creator>jpouladi</dc:creator>
				<category><![CDATA[Seminar]]></category>

		<guid isPermaLink="false">http://www.bcsinnovations.com.au/?p=1071</guid>
		<description><![CDATA[Making waterproof prototypes: Pattern making, moulding, and encapsulation of PCBs. Presentation by Valerie Kuo When            October 20, 2011, 12:45PM Location       Unit 4, Level One, 2-6 Orion Road, Lane Cove NSW 2066 Australia]]></description>
			<content:encoded><![CDATA[<p>Making waterproof prototypes: Pattern making, moulding, and encapsulation of PCBs.<br />
<span id="more-1071"></span></p>
<p>Presentation by Valerie Kuo</p>
<p><strong><strong><strong>When</strong>            </strong></strong>October 20, 2011, 12:45PM<strong><strong><br />
<strong>Location</strong>       </strong></strong>Unit 4, Level One, 2-6 Orion Road, Lane Cove NSW 2066 Australia</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bcsinnovations.com.au/1071/pcb-encapsulation-oct-18-2011/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Updating Operating Systems on Medical Devices</title>
		<link>http://www.bcsinnovations.com.au/766/updating-operating-systems-on-medical-devices/</link>
		<comments>http://www.bcsinnovations.com.au/766/updating-operating-systems-on-medical-devices/#comments</comments>
		<pubDate>Thu, 29 Sep 2011 09:00:27 +0000</pubDate>
		<dc:creator>Mac</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Firmware]]></category>
		<category><![CDATA[Medical Devices]]></category>
		<category><![CDATA[Operating Systems]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://www.bcsinnovations.com.au/?p=766</guid>
		<description><![CDATA[Operating systems have made a big difference to embedded devices &#8211; they improve the sharing of data and add substantial functionality. But medical devices have very strict validation &#38; verification systems &#8211; so when we find issues with our medical device we have to ensure that the updates are suitably validated before being released to the [...]]]></description>
			<content:encoded><![CDATA[<p><img style="margin-right: 1em; margin-bottom: 1em; clear: left; float: left;padding: 0 30px 30px 0;" src="http://www.bcsinnovations.com.au/wp-content/uploads/2011/09/263616669_9b4f46a375_m1.jpg" alt="(Image of Medical Monitor)" width="240" height="192" />Operating systems have made a big difference to embedded devices &#8211; they improve the sharing of data and add substantial functionality.</p>
<p><span style="color: #000000;">But medical devices have very strict validation &amp; verification systems &#8211; so when we find issues with our medical device we have to ensure that the updates are suitably validated before being released to the clinical settings.</span></p>
<p><span style="color: #000000;">That&#8217;s fine for the firmware we create &#8211; but what about the operating system?</span></p>
<p><span id="more-766"></span>Every operating system has a list of patches that are continually being updated.  It isn&#8217;t just Microsoft Windows &#8211; Ubuntu, OS-X and Android  all have a continual stream of updates.  It also applies to support software that is running on the device &#8211; including Antivirus software and database updates.</p>
<p>How much validation needs to be done on those updates?</p>
<p>This isn&#8217;t just a theoretical risk &#8211; one supermarket here in Australia had <a href="http://www.smh.com.au/technology/enterprise/botched-antivirus-knocks-out-10-of-coles-registers-20100422-teif.html" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.smh.com.au/technology/enterprise/botched-antivirus-knocks-out-10-of-coles-registers-20100422-teif.html?referer=');">1100 of their cash registers shutdown</a> because of an automatic update to the antivirus program.  What if, instead of cash registers, they had been patient monitoring equipment at a hospital?</p>
<p>The obvious solution is for the medical equipment manufacturer to lock down the operating system entirely and prevent any updates from being made.  All updates (including Operating system hotfixes, updated virus patterns etc) would then be validated by the medical equipment manufacturer before being released.</p>
<p>That seems like a tempting option &#8211; in theory it gives full control.  However there are some major downsides &#8211; the device is vulnerable to issues and bugs for much a longer period.  <a href="http://www.qualys.com/docs/Laws-Report.pdf" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.qualys.com/docs/Laws-Report.pdf?referer=');">One study</a> found that, on average,  devices on internal networks took 48 days for half of the threats to be patched.</p>
<p>Given the incredible rate of updates (McAfee has daily virus pattern updates) the burden for validating every single update appears impractical.  Some side affects of updates aren&#8217;t obvious either &#8211; some operating system updates appear to have <a href="http://www.cio.com/article/682526/BlackBerry_PlayBook_Battery_Life_Weakened_by_OS_Update" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.cio.com/article/682526/BlackBerry_PlayBook_Battery_Life_Weakened_by_OS_Update?referer=');">dramatically decreased battery life</a>.</p>
<p>Another option (used by <a href="http://www.cardiacscience.com/services-support/service-announcements-and-upgrades/notice-regarding-microsoft-operating-system-security-patches-updates-antivirus-software.htm" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.cardiacscience.com/services-support/service-announcements-and-upgrades/notice-regarding-microsoft-operating-system-security-patches-updates-antivirus-software.htm?referer=');">one manufacturer</a>) is to recommend that the customer applying all critical updates &amp; security patches as soon as they become available.</p>
<p>Which is correct?  To find out the answer, it&#8217;s probably best to consult an expert &#8211; so I spoke with <strong><a href="http://www.ausbiotech2009.com.au/uploads/Peter%20Havel.pdf" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.ausbiotech2009.com.au/uploads/Peter_20Havel.pdf?referer=');">Dr Peter Havel</a></strong>.  Peter is Senior Vice President for Medical &amp; Health Services (MHS) at <a href="http://www.tuev-sued.com/home_com" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.tuev-sued.com/home_com?referer=');">TÜV</a> and is responsible for auditing many medical products.</p>
<p>His response was that it depended entirely on the <strong>hazards analysis</strong> you have done for the product:</p>
<blockquote><p><em><img title="quote_start" src="http://www.bcsinnovations.com.au/wp-content/uploads/2011/09/quote_start.png" alt="" width="16" height="16" /> If the product is designed so that the operating system can fail without causing an injury to the patient then you can accept any windows update.</em></p>
<p><em>However, if the product is designed so that an operating system failure can endanger the safety of a patient then:</em></p>
<ul>
<li><em>You have to set up safety measures to identify every kind of failure that can significantly affect patient safety. This identification then has to set the system to a state that is safe for the patient within the so-called &#8216;failure tolerance time&#8217;.</em></li>
</ul>
<ul>
<li><em>In this case you have to validate every windows update to ensure that it doesn’t disable the capability of your safety measure to identify the unsafe state and that it still has the capability to set the system to a safe state. </em></li>
</ul>
<ul>
<li><em>Alternatively you have to freeze windows in a state that guarantees that your safety measures are still effective and not <em>allow windows update away from that state. </em> <img class="size-full wp-image-783 alignright" title="quote-end" src="http://www.bcsinnovations.com.au/wp-content/uploads/2011/09/quote-end.png" alt="" width="16" height="16" /></em></li>
</ul>
</blockquote>
<p>As always, then, it comes down to good system design in the first place &#8211; ensuring that the product has been designed with sufficient division of functionality so that an operating system failure does not cause a direct hazard to the patient.</p>
<div></div>
<hr />
<span style="font-size: xx-small;">Image credit: <a href="http://www.flickr.com/photos/rwr/263616669/" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.flickr.com/photos/rwr/263616669/?referer=');">Richard Robertson</a>.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.bcsinnovations.com.au/766/updating-operating-systems-on-medical-devices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using the Lantronix Matchport &#8212; Sept 28, 2011</title>
		<link>http://www.bcsinnovations.com.au/1062/using-the-lantronix-matchport-sept-28-2011/</link>
		<comments>http://www.bcsinnovations.com.au/1062/using-the-lantronix-matchport-sept-28-2011/#comments</comments>
		<pubDate>Tue, 20 Sep 2011 05:03:30 +0000</pubDate>
		<dc:creator>jpouladi</dc:creator>
				<category><![CDATA[Seminar]]></category>

		<guid isPermaLink="false">http://www.bcsinnovations.com.au/?p=1062</guid>
		<description><![CDATA[Building embedded web server and TCP/IP applications on Lantronix Matchport AR module. Presentation by Eric Huang When            September 28, 2011, 12:45PM Location       Unit 4, Level One, 2-6 Orion Road, Lane Cove NSW 2066 Australia]]></description>
			<content:encoded><![CDATA[<p>Building embedded web server and TCP/IP applications on Lantronix Matchport AR module.<br />
<span id="more-1062"></span></p>
<p>Presentation by Eric Huang</p>
<p><strong><strong><strong>When</strong>            </strong></strong>September 28, 2011, 12:45PM<strong><strong><br />
<strong>Location</strong>       </strong></strong>Unit 4, Level One, 2-6 Orion Road, Lane Cove NSW 2066 Australia</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bcsinnovations.com.au/1062/using-the-lantronix-matchport-sept-28-2011/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Practical RF Issues &#8212; July 6, 2011</title>
		<link>http://www.bcsinnovations.com.au/952/practical-rf-issues/</link>
		<comments>http://www.bcsinnovations.com.au/952/practical-rf-issues/#comments</comments>
		<pubDate>Fri, 01 Jul 2011 02:35:39 +0000</pubDate>
		<dc:creator>jpouladi</dc:creator>
				<category><![CDATA[Seminar]]></category>

		<guid isPermaLink="false">http://www.bcsinnovations.com.au/?p=952</guid>
		<description><![CDATA[Practical RF circuit design: the challenges, techniques and pitfalls to avoid. Presentation by Mike Batty When            July 6, 2011, 12:45PM Location       Unit 4, Level One, 2-6 Orion Road, Lane Cove NSW 2066 Australia]]></description>
			<content:encoded><![CDATA[<p>Practical RF circuit design: the challenges, techniques and pitfalls to avoid.<span id="more-952"></span></p>
<p>Presentation by Mike Batty</p>
<p><strong><strong>When</strong>            </strong>July 6, 2011, 12:45PM<strong><br />
<strong>Location</strong>       </strong>Unit 4, Level One, 2-6 Orion Road, Lane Cove NSW 2066 Australia<strong><br />
</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.bcsinnovations.com.au/952/practical-rf-issues/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Establishing a Design Gold Standard for your Product</title>
		<link>http://www.bcsinnovations.com.au/195/establishing-a-design-gold-standard-for-your-product/</link>
		<comments>http://www.bcsinnovations.com.au/195/establishing-a-design-gold-standard-for-your-product/#comments</comments>
		<pubDate>Wed, 22 Jun 2011 13:04:56 +0000</pubDate>
		<dc:creator>scohen</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Electronic Design]]></category>
		<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://www.bcsinnovations.com.au/?p=195</guid>
		<description><![CDATA[When you are in the process of bringing your new electronic design into reality, whether it is related to cars, medical equipment, computers and consumer electronics, and so on, you want to be assured that your creation is of the highest quality, while remaining economical to produce. Making quality products is one of the signs [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.bcsinnovations.com.au/wp-content/uploads/2011/06/blog_post_01.jpg" alt="Establishing a Design Gold Standard for your Product" class="img_left" />When you are in the process of bringing your new electronic design into reality, whether it is related to cars, medical equipment, computers and consumer electronics, and so on, you want to be assured that your creation is of the highest quality, while remaining economical to produce. Making quality products is one of the signs of an ethical, professional business, and it is also a generally prudent move from a practical standpoint as well. </p>
<p>High quality products are useful to your company in a variety of ways. They give you an invaluable edge in reputation, for one thing. Although it has been said that “it doesn&#8217;t matter what they say about you, as long as they say it in print”, the power of positive reviews far outweighs that of negative press, and one of the best ways to gain positive exposure is to offer something that is worthy of it. </p>
<p>Part of our mission in offering electronic design services to you is to create a “gold standard” from which all of your subsequent products will be based. This benchmark item will serve as a guideline and parameter for all of the copies of it that will be fabricated and, ultimately, offered for sale either to other companies or to the general public, depending on the type of electronics you are producing. </p>
<p>Our supply network extends to every corner of the globe, meaning that we can draw on sources of electronic components from the manufacturers located in dozens of different countries. With such an array of material at our fingertips, we can easily furnish you with components that will ensure the quality and functionality of your finished product, yet also meet the standards of affordability that you need in order to be able to carry out commercial manufacturing. </p>
<p>Modern communications and the interconnectedness of the global economy make efficient use of scores of different services possible in a way that could not have been dreamed of only a couple of decades ago. You can make use of this potential, through us, in order to establish an electronic design gold standard for your electronics item that will ensure all future examples of the device will meet or exceed the necessary parameters of function, yet remain an economically feasible part of your overall production and business strategy. </p>
<p>Our engineers can also help you develop your product in ways that you might not yet have envisioned, or perhaps thought possible. Whether you need a minimal amount of assistance in clearing a few technical hurdles on the way to full production, or if you have only a hazy inspiration and need it to brought into concrete reality from the top down – from full abstraction all the way down through development, building, testing, refining, and finishing – then our engineers are capable of giving you exactly the help you want. Your product&#8217;s gold standard will soon be established and you can move on to producing and marketing your innovation at the soonest convenient moment. </p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bcsinnovations.com.au/195/establishing-a-design-gold-standard-for-your-product/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

