<?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>#DhalionGuidelines Archives - Perceptual Robotics</title>
	<atom:link href="https://www.perceptual-robotics.com/tag/dhalionguidelines/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Automated wind turbine inspections</description>
	<lastBuildDate>Tue, 22 Jul 2025 09:05:31 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://www.perceptual-robotics.com/wp-content/uploads/2021/07/cropped-PR-Favicon-01-32x32.png</url>
	<title>#DhalionGuidelines Archives - Perceptual Robotics</title>
	<link></link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Dhalion Guidelines</title>
		<link>https://www.perceptual-robotics.com/dhalion-guidelines/</link>
		
		<dc:creator><![CDATA[Irenie Karachaliou]]></dc:creator>
		<pubDate>Tue, 22 Jul 2025 09:04:42 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[#bladeinspections]]></category>
		<category><![CDATA[#Dhalion]]></category>
		<category><![CDATA[#DhalionGuidelines]]></category>
		<category><![CDATA[#dji]]></category>
		<category><![CDATA[#djidrones]]></category>
		<category><![CDATA[#drone]]></category>
		<category><![CDATA[#EfficiencyUnlocked]]></category>
		<category><![CDATA[#energy]]></category>
		<category><![CDATA[#IndustryInsights]]></category>
		<category><![CDATA[#offshorewindenergy]]></category>
		<category><![CDATA[#OperationalEfficiency]]></category>
		<category><![CDATA[#operations]]></category>
		<category><![CDATA[#perceptualrobotics]]></category>
		<category><![CDATA[#robotics]]></category>
		<category><![CDATA[#uav]]></category>
		<category><![CDATA[ai]]></category>
		<category><![CDATA[artificialintelligence]]></category>
		<category><![CDATA[bladerepair]]></category>
		<category><![CDATA[blades]]></category>
		<category><![CDATA[droneinspection]]></category>
		<category><![CDATA[innovation]]></category>
		<category><![CDATA[offshorewind]]></category>
		<category><![CDATA[renewableenergy]]></category>
		<category><![CDATA[sustainability]]></category>
		<category><![CDATA[windenergy]]></category>
		<guid isPermaLink="false">https://www.perceptual-robotics.com/?p=86764</guid>

					<description><![CDATA[<p>Why have we developed our own guidelines after years of using the Bladena Standards?</p>
<p>Because we listen to our Customers!</p>
<p>The post <a href="https://www.perceptual-robotics.com/dhalion-guidelines/">Dhalion Guidelines</a> appeared first on <a href="https://www.perceptual-robotics.com">Perceptual Robotics</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><b>Why have we developed our own guidelines after years of using the Bladena Standards?</b></p>
<p><span style="font-weight: 400;">Because we listen to our Customers!</span></p>
<p><span style="font-weight: 400;">While the 5 severity categories ( see image)  were well-received, many users needed more granularity in how certain damage types and depths were classified. So, we’ve refined our standard to meet that need — without losing continuity.</span></p>
<p><span style="font-weight: 400;">All new classifications have been mapped to the existing system, ensuring alignment between past and future inspections.</span></p>
<p><b>Key improvements include:</b></p>
<p><b>🏴Simplified names:</b><span style="font-weight: 400;"> Type names are generally more concise and consistent (e.g. “45 Cracks on Surface (Cutting from Factory)”→ “Crack &#8211; 45°”)</span></p>
<p><span style="font-weight: 400;">🌍 </span><b>Location removed from types: </b><span style="font-weight: 400;">Terms like “TE-Trailing Edge” have been removed from damage type name. (e.g. “Open Bond Line in TE” becomes “Open bond line”) So from now on the type is attributable to any location.</span></p>
<p><span style="font-weight: 400;"><br />
</span><span style="font-weight: 400;">#️⃣</span><b>More specific damage types and depths:</b><span style="font-weight: 400;"> The number of types and depths has increased slightly. This improves tagging accuracy and downstream analysis.</span></p>
<p><span style="font-weight: 400;">(e.g. Other Cracks on Surface-&gt; becomes two : Crack &#8211; Longitudinal &amp;  Crack- Transvers;  and Depth passes from 6 options to a few more  options))</span></p>
<p><span style="font-weight: 400;">Our goal is to improve clarity, accuracy, and usability across all users, inspections and reports. This is an important step towards making the system able to support  various classification standards in the future.</span></p>
<p>The post <a href="https://www.perceptual-robotics.com/dhalion-guidelines/">Dhalion Guidelines</a> appeared first on <a href="https://www.perceptual-robotics.com">Perceptual Robotics</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
