<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Iris Automation - Medium]]></title>
        <description><![CDATA[Unlocking the potential of your drones to fly beyond visual line of sight. - Medium]]></description>
        <link>https://medium.com/iris-automation?source=rss----1fabdab22a78---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Iris Automation - Medium</title>
            <link>https://medium.com/iris-automation?source=rss----1fabdab22a78---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:01:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/iris-automation" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Looking Beyond to Skies full of Piloted and Unpiloted Aircraft]]></title>
            <link>https://medium.com/iris-automation/looking-beyond-to-skies-full-of-piloted-and-unpiloted-aircraft-27d00c0848e3?source=rss----1fabdab22a78---4</link>
            <guid isPermaLink="false">https://medium.com/p/27d00c0848e3</guid>
            <category><![CDATA[aviation]]></category>
            <category><![CDATA[aircraft]]></category>
            <category><![CDATA[drones]]></category>
            <dc:creator><![CDATA[Jon Damush]]></dc:creator>
            <pubDate>Mon, 17 May 2021 19:30:25 GMT</pubDate>
            <atom:updated>2021-05-17T19:30:25.837Z</atom:updated>
            <content:encoded><![CDATA[<p>How Collaboration and Transparency are Shaping the Future of our Skies</p><figure><img alt="A yellow xCub airplace against a blue background" src="https://cdn-images-1.medium.com/max/1024/1*Ihi7mYe4GkQI8QyANWECWQ.jpeg" /><figcaption>Iris Automation’s xCub aircraft in the field</figcaption></figure><p>For those of us who have worked in the aerospace business for significant parts of their careers, there is a genuine excitement about our industry today. <strong>We are at an amazing junction of technology and opportunity that promises to usher in a second century of aviation that brings the benefits of aviation to even more people with much higher levels of convenience and much lower environmental impact.</strong> Regional and local electrically propelled flights are on the near horizon and private capital has been the fuel driving this amazing period of aviation technology development. But getting to the finish line also requires creating some new concepts of operation and operational guidelines and rules that will help make this second century of aviation safer than the first. These are not trivial issues, and many very smart, experienced people have been working them for many, many years. Historically, the community has seen similar challenges, from adjusting airspace design to support higher density traffic, to the introduction of GPS systems on-board, to technically advanced aircraft cockpits. The community has collaborated successfully in the past to push through these challenges and unlock new capabilities for aviation — improving efficiency, enjoyment and most importantly, safety. But that community was relatively small, and was populated by people who had spent most of their life in aviation, sharing similar educational backgrounds, experience levels, and visions of outcomes. Today’s aviation community is growing rapidly and is nowhere near as homogenous as yesterday’s community. We have new entrants to the industry coming from fields like artificial intelligence, logistics, software as a service, rideshare and ecommerce.</p><p>As I mentioned above, <strong>one of the foundational tenets of the aviation ecosystem is collaboration, because it is only through collaboration that we can achieve the levels of safety the public has come to expect.</strong> Many might not know this, but even Boeing and Airbus collaborate closely on a number of global initiatives to advance the state of the art in aviation as well as the level of safety globally. Safety data is shared, accident information is shared, certification data is shared, even software interfaces to critical systems is shared (otherwise you would not see an Airbus with Jeppesen charts aboard). Through this level of collaboration, the industry is able to learn from each other and incorporate those learnings into system designs, manufacturing processes, concepts of operation, training, and many other areas. It is in everyone’s best interest to share to ensure safety, reliability and predictability.</p><p>I wanted to make a quick post to share some updates on the collaborative work Iris Automation has been doing to help regulators enable safe Unmanned Aircraft Systems (UAS) flights, and particularly Beyond Visual Line of Sight (BVLOS) flight. And to give an overview of our participation in the FAA’s BEYOND Program, a public-private sector initiative to evaluate UAS air safety capabilities toward the establishment of BVLOS guidance and ultimately rules and regulations.</p><figure><img alt="A multirotor drone against a blue sky" src="https://cdn-images-1.medium.com/max/1024/1*GpAFCSFv_JDWRjkp8PmxPg.jpeg" /></figure><p>While technology, including our Detect-and-Avoid (DAA) product line <a href="https://www.irisonboard.com/casia/">Casia®</a>, has matured and offers great promise to enable safe BVLOS missions, regulators are still determining how to enable widespread BVLOS safely. This is a critical job and can’t be rushed! We are working with Civil Aviation Authorities (CAA) worldwide to <a href="https://www.irisonboard.com/how-to-get-a-bvlos-waiver/">make this happen</a>. Between 2017 and 2020, we were participants in several of the FAA’s UAS Integration Pilot Programs (IPPs), exploring use cases, complementary technologies, concepts of operation, and <a href="https://35l4dy1qshws7yrw73y2cegc-wpengine.netdna-ssl.com/wp-content/uploads/2020/12/Kansas-IPP-Case-Study-Iris-Automation.pdf">real-world challenges</a> involved with deploying unpiloted systems into the national airspace. The FAA’s BEYOND program is the next phase of these programs, and so far we have partnered with four lead participants — the City of Reno, Kansas Department of Transportation, University of Alaska-Fairbanks (ACUASI), and the Choctaw Nation of Oklahoma, all of whom we previously partnered with in the IPPs. BEYOND is designed to increase the use of drones safely, beyond the current limitations on remaining <a href="https://www.irisonboard.com/what-is-visual-line-of-sight-vlos-the-rules-to-know/">within the visual line of sight</a> of ground pilots. This is important for two main reasons: 1) It will allow for unpiloted systems to fly longer, more distant missions and 2) It will allow for an increased aircraft to operator ratio, i.e. one operator managing multiple aircraft — a key value proposition of unpiloted aircraft in the first place. These partnerships help the FAA collect data and lessons learned to inform future standards for BVLOS drone operations across the United States.</p><figure><img alt="A man in a wheat field holds a drone" src="https://cdn-images-1.medium.com/max/1024/1*fH__CIaEjMUq8sI4Hwlo2A.jpeg" /><figcaption>A member of the Iris Automation Flight Operations team in the field during testing</figcaption></figure><p>It’s a great pathway to determining regulatory standards and we love working with the FAA and partners who are all committed to safety, regulatory compliance, and transparency. Iris Automation is committed to developing critical detection technologies and working closely with global policymakers and regulators to develop appropriate BVLOS safety standards. For commercial drone use to become widespread, clear standards for incorporating onboard DAA capabilities will be necessary to ensure a high degree of air safety. DAA technology was also identified by the U.S. Congress <a href="https://www.irisonboard.com/congress-recognizes-onboard-daa-for-drone-integration/">as a priority</a> for the FAA’s ongoing efforts to enable safe commercial BVLOS operations. In fact, it is through our work with the FAA in the IPP program that we learned the critical safety concerns of the regulator, the public, and of operators to inform our product roadmap for our newest product, Casia X, which is capable of detecting non-cooperative aircraft over a 360-degree horizontal field of view.</p><blockquote>The entire industry must be committed to researching and defining these standards, and there are a number of pathways to achieve this throughout the world.</blockquote><p>In the USA, in addition to the FAA’s direct efforts, NASA has shown leadership in the space through a number of open trial programs; Iris has previously participated in some of these programs, including Technical Capacity Level (TCL). The Drone Advisory Committee<strong> </strong>continues to provide the FAA with critical input from industry and other critical stakeholders in the aviation ecosystem. More broadly, standards bodies like ASTM, RTCA, and SAE are working hard to help define means of compliance to ensure safety of the next generation of our global aviation systems. Iris Automation is an active participant in the standards development process. This process ensures that community agreed standards are compatible with industry needs and regulator requirements. As we look outside the USA, EASA has certainly been a leading voice with several initiatives that have led thinking in the unpiloted space. JARUS’ Automation Working Group, a group of experts,<strong> </strong>including Iris Automation, gathering regulatory expertise from all around the world is a significant contributor. The World Economic Forum’s Global Innovators Community for Shaping the Future of Mobility is exploring key use cases that have maximum impact on the human condition. <a href="https://www.irisonboard.com/world-economic-forum-global-innovators-community/">As part of the Shaping the Future of Mobility platform</a>, Iris Automation supports compatible projects adopted by the Drone Innovators Network (DIN), and partners with DIN to advance progressive air safety policy frameworks. We have also been consulting with regulators in Brazil, Mexico, Canada, UK, France, Latvia, South Africa, New Zealand, and Australia and others, who are all sharing information and exploring use cases, technologies and concepts of operations to get the global unpiloted community into the air flying BVLOS.</p><figure><img alt="A man and a young girl in the cockpit of an airplane" src="https://cdn-images-1.medium.com/max/1024/1*ahZy5Db4Er8iAQChekyprA.jpeg" /><figcaption>Iris Automation CEO Jon Damush and his daughter</figcaption></figure><p>Working in a highly regulated industry can be daunting to new entrants. As a business, we have been working closely with regulators since 2017, and have amassed a significant amount of knowledge and developed processes to help others navigate the complexities of waivers, exemptions, existing rules, certification, and many other areas. Last year, we established our <a href="https://www.irisonboard.com/regulatory-resource-center/">Regulatory Resource Center</a> (RRC), creating a robust risk assessment, mitigation, and Concept of Operations (CONOP) package for BVLOS flights for the safest flight operations program possible. The RRC provides a structured workflow to help address regulatory and safety concerns that the Civil Aviation Authority (CAA) require, with an online portal to build, test, and audit complex and advanced <a href="https://35l4dy1qshws7yrw73y2cegc-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/APS-Success-Story-Iris-Automation.pdf">operational approvals</a> supported by a team of UAS regulatory experts.</p><p>As we look forward to a world reopened, and redefine new ‘normals,’ we are excited to be in this position at this transformative point in time in aviation and technology. We look forward to continued and new collaborations with global regulators and industry peers as we all push forward to define new standards for safe aviation. Together we can define regulatory frameworks that safely expand the applicability and accessibility of aviation around the world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27d00c0848e3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iris-automation/looking-beyond-to-skies-full-of-piloted-and-unpiloted-aircraft-27d00c0848e3">Looking Beyond to Skies full of Piloted and Unpiloted Aircraft</a> was originally published in <a href="https://medium.com/iris-automation">Iris Automation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Avoiding Drone-Related Mid-Air Collisions]]></title>
            <link>https://medium.com/iris-automation/avoiding-drone-related-mid-air-collisions-e82582021a79?source=rss----1fabdab22a78---4</link>
            <guid isPermaLink="false">https://medium.com/p/e82582021a79</guid>
            <category><![CDATA[drones]]></category>
            <category><![CDATA[drone-week]]></category>
            <category><![CDATA[fly-safe]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[drones4good]]></category>
            <dc:creator><![CDATA[Jon Damush]]></dc:creator>
            <pubDate>Fri, 20 Nov 2020 13:05:27 GMT</pubDate>
            <atom:updated>2020-12-29T00:51:23.436Z</atom:updated>
            <content:encoded><![CDATA[<h4>Insights from a commercial pilot, certified flight instructor, and Chief Executive Officer of Iris Automation, Inc.</h4><figure><img alt="Mountain landscape with a lake and trees in the foreground, with a helicopter, drone, and airplane in near proximity" src="https://cdn-images-1.medium.com/max/1024/1*RHaTCx0eCYRqanR8Z-tjDw.png" /><figcaption>Crowded airspace via the Iris Automation in-house simulator</figcaption></figure><p>It has been just over 100 years since the Wright Brothers flew their infamous first flight. In those 100 years, we as a society have enjoyed the benefits of flight across multiple use cases. Air travel is the most obvious, but cargo and logistics aircraft make ‘next day’ deliveries possible as well. Agricultural yields are improved by aircraft spraying crops. Critical infrastructure is kept in top condition because of inspections that happen from the air at regular frequencies. As the world explored and perfected these various use cases, the number and variety of aircraft in the skies has proportionally increased. To give a sense of the scale, in 2019 (just prior to the COVID-19 pandemic), the average number of daily airline flights in the United States was over 45,000. Add to that the non-airline flights that include business aviation, law enforcement, and general aviation and you start to see a picture of increasingly crowded skies.</p><p><strong>As we look ahead to the pending increase of air traffic due to unpiloted systems, ie drones, the community has been working to envision and create a system where the increased traffic does not meaningfully increase the mid-air collision risk between drones or worse, between a drone and a piloted or passenger carrying aircraft. </strong>The engineers among us (guilty as charged) immediately start thinking about how to solve the problem with technology. You can hear us now saying ‘there has to be a way to do that perfectly…’ But the most likely way forward is not dissimilar to the way aircraft remain separated in today’s piloted aircraft world.</p><p>It is useful to understand how the current system works so we can see how the future system might work. To those of us who have been trying to solve this problem for the last few years, this will not be groundbreaking at all, but to those of us who are relatively new to the aviation community, I hope this might help — if for no other reason than to give us a common lexicon for the ideation and discussion of new concepts.</p><h4>The current airspace system</h4><p>The ugly truth is that the current system does not prevent all mid-air collisions from happening. According to the Nall report, we still have a ‘single digit’ number of mid-air collisions in the USA each year, typically accounting for 10–20 fatalities. Considering the number of daily flights, however, this is an impressive feat. So how does it work?</p><blockquote><strong>There is essentially a ‘stack’ of layers of mitigation that operate in conjunction with one another to filter out the collision risk.</strong></blockquote><p>First of all, there is no single piece of technology that keeps aircraft separated. Instead, we employ a system of systems and multiple layers of mitigation to avoid mid-air collisions. It starts with planning. The way a flight is planned, the altitudes chosen, the route plotted, the airspace transited all contribute to keeping one’s own airplane (what we call the ‘ownship’) away from other traffic and terrestrial and environmental hazards (i.e. the ground and weather). Once we get in the airplane, we use a variety of tactical methods to avoid other aircraft, including talking to air traffic control, using ADS-B, ground-based radars, and transponder equipped aircraft. Finally, we come to the last line of defense — the human pilot. There is essentially a ‘stack’ of layers of mitigation that operate in conjunction with one another to filter out the collision risk. But no system is perfect, and that is why FAR part 91.113(b) states “The pilot….shall see and avoid other aircraft.”</p><h4><strong>So what happens when there is no ‘pilot’ on board?</strong></h4><p>We have effectively lost our last line of defense. The good news is that we have the ability through regulation, technology, and collaboration with each other to have all drones be considered ‘cooperative.’ That means that they report where they are and what their intentions are so that all other users of the airspace are aware of where the drone is operating and what it plans to do. Systems like UTM (Unmanned Traffic Management) offer great promise to help the low altitude drone community avoid mid-air collisions due to the ‘cooperative’ nature of the drones.</p><p>Our main challenge comes from the desire to start performing use cases that push the flight plan outside of the boundaries of the current regulations, namely Part 107 in the USA, which allows for commercial drone operations below 400 feet above the ground, within visual line of sight, and a host of other restrictions. If you think of applications like long-linear infrastructure inspections, large area mapping, search and rescue, logistics, and passenger transit you can start to see where this new class of aircraft offers value and needs to fly ‘beyond the visual line of sight’ (BVLOS). Quick aside: there is a part of me that doesn’t like the acronym, as it implies that the desire is always to fly farther than someone can see, but perhaps the bigger economic value is that solving the BVLOS problem actually allows you to invert a critical ratio — the operator to aircraft ratio, which for drones right now is 1 (or more) to 1. That’s right, in many cases, operating a single drone requires more than one human operator. In my humble opinion, we will see rapid adoption of drone technology not because they can fly far, but rather because one person can fly multiple drones. This is where the economic value lies with robotic aircraft.</p><h4><strong>So as we push these aircraft into regimes where they will have to mix with piloted aircraft, why can’t we just do the same thing we do with piloted aircraft?</strong></h4><p>If you remember, it is the pilot in the aircraft that provides the last line of defense for collision avoidance in piloted aircraft operations. To date, we have not had an equivalent system on drones that can provide the same ‘last line of defense.’ This is precisely where Iris Automation is focusing its energy. <strong>We have worked very hard to develop a system that uses a combination of computer vision, artificial intelligence, and machine learning to detect, classify, and compute the relative position of an aircraft in flight. </strong>We call this system Casia, and we have successfully flown it on-board many different types of drones and even tested it on piloted aircraft. We have been collaborating with partners and regulators to explore how our system can be used in conjunction with other technologies and concepts of operations to mitigate the mid-air collision risk as well, if not better than we do today in piloted aircraft. The exciting part of our approach is that by using computer vision, we are able to use relatively low-cost, readily available, and small off the shelf hardware components. This helps us keep our size, weight and power (SWAP) low enough to be placed on-board the aircraft without negatively impacting that aircraft’s ability to perform its mission and carry its revenue-generating payloads. Improvements in performance in the future will be provided through software updates, including constantly improving our machine learning database, allowing for use in more diverse environments and detecting and classifying an ever-increasing number of aircraft and other obstacles.</p><h4><strong>So, how are we doing?</strong></h4><p>Pretty good I would say. We have achieved waiver approvals in Alaska, Kansas, South Africa, and Canada for BVLOS flight trials. While these are not yet to the point where we can ‘cut and paste’ the operation to unlock everyone’s commercial BVLOS operations, they are an important stepping stone and one that leads us into the FAA’s BEYOND program, where we are excited to continue to collaborate with regulators to explore additional use cases and expand the envelope of performance. Are we as good as humans yet? Not quite, but we are getting there fast. One thing to remember about our system — it does not get distracted, tired or bored of doing its job. It can see all of the airspace around it and is not occluded by cockpit structure, passengers, or cargo. Considering this, I believe we are a critical part of the system of systems that includes UTM, radar, ADS-B, and other strategic mitigations. Analogous to the human pilot, we are in a great position to provide the ‘last line of defense’ for collision avoidance to the drone community. At the end of the day, it is about raising the level of safety for unpiloted systems, and our goal is making sure our users never have a mid-air collision if they have a Casia system on-board.</p><p><em>Learn more about Casia at </em><a href="http://www.irisonboard.com/casia."><em>www.irisonboard.com/casia</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e82582021a79" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iris-automation/avoiding-drone-related-mid-air-collisions-e82582021a79">Avoiding Drone-Related Mid-Air Collisions</a> was originally published in <a href="https://medium.com/iris-automation">Iris Automation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Visual Flight Rules for Drone Computer Vision]]></title>
            <link>https://medium.com/iris-automation/visual-flight-rules-for-drone-computer-vision-232c8102698a?source=rss----1fabdab22a78---4</link>
            <guid isPermaLink="false">https://medium.com/p/232c8102698a</guid>
            <category><![CDATA[simulation]]></category>
            <category><![CDATA[computer-vision]]></category>
            <category><![CDATA[drones-technology]]></category>
            <category><![CDATA[drones]]></category>
            <category><![CDATA[aviation]]></category>
            <dc:creator><![CDATA[Eric Schafer]]></dc:creator>
            <pubDate>Mon, 14 Sep 2020 21:46:40 GMT</pubDate>
            <atom:updated>2020-09-24T20:23:32.848Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Low-altitude airspace simulation at Iris." src="https://cdn-images-1.medium.com/max/1024/1*Shxh28vRvtHT7j2msXSTug.png" /></figure><p>When human pilots fly aircraft using Visual Flight Rules (VFR), this means they are flying using external cues (vision), not instruments, and avoiding other aircraft by visually spotting them while they are still “well clear” (maintaining a minimum distance of 2000 feet apart)<strong>, </strong>rather than using Air Traffic Control. Flying VFR is allowed when the weather is good enough to meet minimum Visual Meteorological Conditions [1].</p><p>Iris Automation’s collision avoidance system for Unmanned Aircraft Systems (UAS), <a href="http://www.irisonboard.com/casia/">Casia</a>, operates in the same daytime conditions as human pilots flying VFR, so it needs to be able to detect “non-cooperative” planes that don’t broadcast their location using an ADS-B transmitter. However, drones normally fly below 400 feet (122 m) above ground level [3], where fog and birds can be problems for planes and helicopters flying low, especially when they need to land.</p><p>Drones compound the risk of manned aircraft flying in low-altitude airspace, so Casia directs the unmanned aircraft’s onboard autopilot to get out of the way.</p><p>The low-altitude Visual Meteorological Conditions (VMC) in which Casia operates span a vast gamut of weather conditions. In the US, for example, below 1200 feet (366 m), VMC means visibility of at least 1 statute mile (1600 m) and no clouds closer than that. Though these minima vary from country to country, generally more visibility is required in ATC controlled airspace (e.g., Class B) than uncontrolled airspace (e.g., Class G). Within those flying conditions is a wide variety of landscape photography to challenge a drone’s autonomous vision system.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FCPnT4EXXRNw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DCPnT4EXXRNw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FCPnT4EXXRNw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/40d9050d8ea3f18ed3115d661c83004a/href">https://medium.com/media/40d9050d8ea3f18ed3115d661c83004a/href</a></iframe><p>Spotting a tiny plane or helicopter on the horizon without getting tricked by a fluffy cloud or tree, and while jiggling around in the sky, takes practice. Here’s what practice looks like to Casia.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F9lhkD1INOjQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D9lhkD1INOjQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F9lhkD1INOjQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/28d39d1d8f01e9e0a5b785135f18b46d/href">https://medium.com/media/28d39d1d8f01e9e0a5b785135f18b46d/href</a></iframe><p>Avoiding Well Clear Breaches and Near Mid-Air Collisions (NMACs) takes practice. Although Iris Automation regularly tests Casia’s collision avoidance maneuvers in response to real Well Clear Breaches, flying real-world NMAC test cases is both dangerous and illegal. So simulation is an important component of giving autopilot AI risky training examples for collision avoidance, as well as sufficient data to get good at it.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhYOPZyPHGdc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhYOPZyPHGdc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhYOPZyPHGdc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6de29ac917ae1aca3f15bd06eb14edf9/href">https://medium.com/media/6de29ac917ae1aca3f15bd06eb14edf9/href</a></iframe><p>As new real-world environments within VFR conditions challenge <a href="http://www.irisonboard.com/casia/">Casia</a>, simulation must evolve to train it to be better and better in both similar conditions and harder conditions with more dangerous scenarios. And it turns out that virtual drone photography is an enjoyable hobby.</p><h4>Further Reading</h4><p><em>[1] VMC vs VFR: What’s technically legal isn’t necessarily safe, Plane and Pilot Magazine, 2016<br>https://www.planeandpilotmag.com/article/vmc-vs-vfr/</em></p><p><em>[2] Operating BVLOS: FAA Proposes Guidance on Staying “Well Clear” — The Hockey Puck of Clearance<br>https://www.uasinsights.com/2018/12/13/156/</em></p><p><em>[3] FAA Fact Sheet–Small Unmanned Aircraft Regulations (Part 107)<br>https://www.faa.gov/news/fact_sheets/news_story.cfm?newsId=20516</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=232c8102698a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iris-automation/visual-flight-rules-for-drone-computer-vision-232c8102698a">Visual Flight Rules for Drone Computer Vision</a> was originally published in <a href="https://medium.com/iris-automation">Iris Automation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Commercial BVLOS Flight in 2021]]></title>
            <link>https://medium.com/iris-automation/commercial-bvlos-flights-in-2021-a259f47029fe?source=rss----1fabdab22a78---4</link>
            <guid isPermaLink="false">https://medium.com/p/a259f47029fe</guid>
            <category><![CDATA[flying-cars]]></category>
            <category><![CDATA[airtaxi]]></category>
            <category><![CDATA[autonomous-vehicles]]></category>
            <category><![CDATA[drones]]></category>
            <dc:creator><![CDATA[Jason Hardysmith]]></dc:creator>
            <pubDate>Thu, 03 Sep 2020 19:58:58 GMT</pubDate>
            <atom:updated>2020-09-03T19:59:33.025Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to get truly off the ground</h4><p>In the recent Season 3 of HBO series “Westworld,” we’re bombarded with a variety of autonomous urban air mobility vehicles (so-called “air taxis”). The wealthy elite use these to move around Los Angeles, bypassing gridlocked traffic.</p><p>Weirdly enough, the scenes shot in LA are actually shot in Singapore, which had opened up regulations around urban air taxis in 2019. This further blurred the lines between fiction and reality — which was the whole point behind Westworld’s theme of artificial intelligence and fictional technology, i.e. just plausible enough to make it feasible to create in the real world.</p><figure><img alt="A lit up autonomous air taxi against a black sky with lit up city skyline" src="https://cdn-images-1.medium.com/max/1024/0*Cj-AcwqXW4ICygI-" /><figcaption><em>Autonomous urban air mobility vehicles in “Westworld” (above) and a real-world version in Singapore (below)</em></figcaption></figure><p>What’s truly interesting about the new reality we live in is <strong>not</strong> how far along autonomous air vehicles have come technologically, but how far we have yet to go in building the regulatory environment to make commercial drone usage truly scalable.</p><figure><img alt="A multirotor autonomous helicopter in the sky above the Singapore skyline" src="https://cdn-images-1.medium.com/max/768/1*BZqWx8XhXhkESbci8Xo7Lw.jpeg" /></figure><p><strong>In short, the tech exists — but we’re waiting on the regulatory framework to support the industry commercially.</strong></p><p>That is the fundamental nature of the drone industry; while other tech industries treat regulatory compliance as an afterthought<strong>, </strong>it is front-and-center in the world of unmanned aviation, and is often the main roadblock, <em>rather than the tech itself</em>.</p><p>Unblocking true Beyond Visual Line of Sight (BVLOS) flight will unlock a multi-billion dollar market that is currently held back by the lack of a fully formed regulatory environment. This requires several key technology components to work together harmoniously within the nascent regulatory framework being championed by the FAA and NASA in the United States.</p><h3>How do we get BVLOS drones truly off the ground?</h3><p>A truly autonomous drone should meet the requirements of these four quadrants:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/304/1*K4-v4uP7BUvA39zDoTAPsQ.png" /></figure><ol><li>Air Risk Mitigation: Autonomously detect and stay well clear of cooperative and non-cooperative manned aircraft</li><li>Operational Reliability: Operative using a reliable aircraft and aircraft systems, with well trained staff and well defined procedures</li><li>C2 Reliability: Remain in command and control of the aircraft throughout the entirety of flight</li><li>Ground Risk Mitigation: Minimize the chance of injury/damage to persons/property on the ground</li></ol><h4><strong>Air Risk Mitigation</strong></h4><p>Autonomous drones must remain well clear of all other air traffic to ensure safety in the air. Around 30–40% of manned aircraft are considered cooperative — they have Automatic dependent surveillance–broadcast (ADS-B) broadcasting their location at all times. This leaves 60–70% of manned aircraft noncooperative, as well as numerous other airborne objects that must be accounted for, e.g. hot air balloons and hang gliders.</p><p>The solution is onboard <strong>Detect-and-Avoid</strong>. This allows a drone to ‘see’, sense, or detect conflicting traffic<strong> </strong>or other hazards and take the appropriate action. This capability aims to ensure the safe execution of a Remotely Piloted Aircraft (RPA) flight and to enable full integration in all airspace classes with all airspace users.</p><h4><strong>Operational Reliability</strong></h4><p>Questions to ask yourself include, “Do I have a reliable platform?” “Am I maintaining it properly?” and “Is my team properly trained and following strict standards of operation?”</p><p>Reliable technology, personnel, concept of operations, and reliable airframes are all required for safe operations. <a href="http://jarus-rpas.org/sites/jarus-rpas.org/files/jar_doc_06_jarus_sora_v2.0.pdf">JARUS provides guidelines</a> and a standardized format on Specific Operations Risk Assessment (SORA) to follow when creating a CONOPs.</p><p>The industry is far along when it comes to ensuring reliable airframes through type certification — a type certificate is issued by a regulatory authority after oversight of the design and production has been determined to be airworthy. Once issued, any design changes would need to be reassessed by the issuing authority.</p><h4><strong>Command and Control (C2)</strong></h4><p>Command and control (C2) communications must be maintained between the aircraft and RPIC throughout the entirety of flight. This means that the pilot is in active control of their drone at all times, understands range and any obstructions in the flight, and where there might be communication dead points. Real world testing of C2 links therefore must be conducted.</p><p>For most of the applications we’ve been working with, normal line of sight radio has been more than enough. Very likely, over the next couple years as package delivery scales up, increased airborne connectivity will come from network connectivity, satellite communications, and LTE. There’s a desire to overlap communications systems and move to LTE, which can be built into pretty much any product; it will be cheaper and have higher bandwidth, lower latency, and much better size, weight, and power tradeoff.</p><h4><strong>Ground Risk Mitigation</strong></h4><p>Whenever an unmanned aircraft system is in flight, there is risk of failure resulting in a crash. The risk of injury or damage to property can be significant: If a drone flying above a crowd of people crashes, the results could be fatal. Operators of unmanned aerial systems (UAS) need to effectively mitigate this risk, especially in BVLOS operations where the operator is less likely to be aware of a sudden loss in altitude or power.</p><figure><img alt="A multirotor drone against a blue sky with an inflated red parachute attached to it" src="https://cdn-images-1.medium.com/max/800/0*CC9e_mi39yVhbz15" /><figcaption>Source: UAV Coach</figcaption></figure><p>Ground risk mitigation can take various forms. For example, the operator could focus on operations in remote/rural areas with very low population density. Alternatively, they could leverage on-board technologies that prevent high velocity descent such as an on-board parachute system that deploys automatically when an aircraft failure is detected.</p><p><a href="https://www.astm.org/Standards/F3322.htm">The recent publication of the ASTM standards for drone parachute deployments</a> provides a standardized path to adding on-board ground risk mitigation for drone manufacturers that would help operators get successful FAA BVLOS waivers in the United States.</p><p><strong>A note about UTM and remote ID: </strong>Achieving BVLOS today requires the four quadrants outlined here for the scenarios that we have been focusing on — lower airspace and population density and relatively low risk missions, but the broader integration of drones in airspace as the industry scales will likely require UTM and Remote ID.</p><p>Unmanned Traffic Management (UTM) refers to a proposed system of air traffic control for autonomously controlled operations of unmanned aerial systems (UAS) by the FAA, NASA, other federal partner agencies, and the industry.</p><p>Remote ID refers to the ability of a UAS to broadcast its identification information that can be received by all parties and helps the FAA, law enforcement, security agencies, and other aircraft to quickly identify UAS aircraft that are flying in an unsafe manner or in an area where drone flights are prohibited. It is also a valuable tool in unmanned traffic management to help aircraft avoid each other.</p><h3><strong>Summary</strong></h3><p>In summary, these are the four main components that support a truly autonomous drone platform. At Iris Automation, we encourage collaboration— both government and industry — to help build the regulatory and technological pathways needed to make this industry a true source of economic growth. By focusing efforts on building technology products to address these quadrants, we hope that the regulatory framework will naturally align itself with these core considerations.</p><p>While there are many tech companies out there that work on various pieces of the puzzle, Iris Automation can help you address the technical challenge of Detect-and-Avoid. <a href="https://www.irisonboard.com/casia/">Our new Casia 360 system </a>is the first commercially available 360 degree radial computer vision Detect-and-Avoid system for UAS. As an integrated onboard hardware and software solution, Casia systems are small, lightweight, and low power. Casia enables safe Beyond Visual Line of Sight (BVLOS) operations that drastically reduce cost. Our system has been designed and built from the ground up by a team of computer vision and deep learning scientists, and has been tested extensively, with thousands of real world and simulated aircraft encounters.</p><p>Sources</p><p><a href="https://evtol.com/features/hbo-westworld-evtol-aircraft/"><em>Westworld eVTOL concept</em></a></p><p><a href="https://www.faa.gov/uas/research_development/traffic_management/media/UTM_ConOps_v2.pdf"><em>UTM Concept of Operations — 2.0</em></a></p><p><a href="https://www.faa.gov/uas/research_development/traffic_management/"><em>FAA UTM Overview</em></a></p><p><a href="https://www.faa.gov/uas/research_development/remote_id/"><em>Remote ID — FAA</em></a></p><p><a href="https://www.federalregister.gov/documents/2019/12/31/2019-28100/remote-identification-of-unmanned-aircraft-systems#h-64"><em>FAA Notice of Proposed Rule Making — Remote ID</em></a></p><p><a href="https://www.icao.int/safety/UA/Documents/ICAO%20RPAS%20CONOPS.pdf"><em>Remotely Piloted Aircraft Systems — Concept of Operations (ICAO document)</em></a></p><p><a href="https://uavcoach.com/drone-parachute-system/"><em>UAV Coach — Drone Parachutes</em></a></p><p><a href="https://www.astm.org/Standards/F3322.htm"><em>Standard Specification for Small Unmanned Aircraft System (sUAS) Parachutes</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a259f47029fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iris-automation/commercial-bvlos-flights-in-2021-a259f47029fe">Commercial BVLOS Flight in 2021</a> was originally published in <a href="https://medium.com/iris-automation">Iris Automation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Innovation at Iris Automation]]></title>
            <link>https://medium.com/iris-automation/innovation-at-iris-automation-ada575c59938?source=rss----1fabdab22a78---4</link>
            <guid isPermaLink="false">https://medium.com/p/ada575c59938</guid>
            <category><![CDATA[ada]]></category>
            <category><![CDATA[auvsi]]></category>
            <category><![CDATA[bvlos]]></category>
            <category><![CDATA[drones]]></category>
            <category><![CDATA[faa]]></category>
            <dc:creator><![CDATA[Alexander Harmsen]]></dc:creator>
            <pubDate>Mon, 29 Jun 2020 17:59:45 GMT</pubDate>
            <atom:updated>2020-06-29T17:59:45.538Z</atom:updated>
            <content:encoded><![CDATA[<h3>A quick look at where we’re at in June 2020</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U7OHAUW4q_KLMO_Tak65FA.jpeg" /></figure><p>In light of Iris Automation’s selection as a finalist for the <a href="https://www.auvsi.org/our-impact/auvsi-xcellence-awards">2020 AUVSI XCELLENCE Awards</a> in two categories, including the top prize — XCELLENCE in Innovation, I want to share an overview of the current state of affairs and innovation at Iris. And although 2020 has proven a tricky cat, we’re continuing to make incredible headway here at Iris Automation.</p><p>Late last year we introduced a long-range version of our Detect-and-Avoid (DAA) system, <a href="https://www.irisonboard.com/casia/">Casia</a>, and we’ve recently launched an additional version, <a href="https://www.irisonboard.com/introducing-casia-360/">Casia 360</a>, which achieves 360 degree radial vision built to meet the highest regulatory standards for performance risk-ratios. While the capabilities of our Casia systems have already been acknowledged by the <a href="https://www.irisonboard.com/iris-and-kdot-historic-bvlos-flight/">FAA</a> and other <a href="https://www.irisonboard.com/first-canada-bvlos-approval/">CAAs</a> for enabling true BVLOS flight, we are working to make our onboard DAA even more accessible to customers.</p><p>To support our product growth and maturation, we’ve continued to build our rigorous <a href="https://www.crowdcast.io/e/casia-testing-program">testing program</a> to bring Casia safely to market, to date logging over 14,000 real-world encounters and 600 terabytes of flight data that we use to continuously improve our software.</p><p>Our Flight Operations team continues to work tirelessly in the field, and we’re fortunate that the work allows them to social distance in the vast deserts of Nevada, where they are based.</p><p>And, to support organizations in the application and acceptance of BVLOS permissions, we’ve rolled out the Waiver Resource Center to make BVLOS accessible to everyone. We currently support permissions applications in the United States and Canada, with more CAAs coming soon, including the UK and South Africa. Our aviation policy specialists have thousands of man-hours assessing operational risk and establishing compliant BVLOS flight operations with and without a DAA system.</p><p>We’ve also launched an <a href="https://www.crowdcast.io/irisautomation">Ask Me Anything (AMA) series</a> to give you access to the experts at Iris Automation and share our knowledge.</p><p>For more access to our team and others in the BVLOS space, join us on <a href="http://bvlosirisautomation.slack.com/">BVLOS &amp; Beyond</a>, a Slack workspace to host collective conversations with others interested in BVLOS, Casia integrations, navigating regulations, and more.</p><p>I look forward to sharing additional innovations with you by October’s XPONENTIAL conference, and I truly hope you are staying safe and healthy out there,</p><p><em>Alexander Harmsen, CEO &amp; Cofounder Iris Automation</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ada575c59938" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iris-automation/innovation-at-iris-automation-ada575c59938">Innovation at Iris Automation</a> was originally published in <a href="https://medium.com/iris-automation">Iris Automation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What It Takes To Fly ‘True’ Beyond Visual Line of Sight]]></title>
            <link>https://medium.com/iris-automation/what-it-takes-to-fly-true-beyond-visual-line-of-sight-fd8303af9b4d?source=rss----1fabdab22a78---4</link>
            <guid isPermaLink="false">https://medium.com/p/fd8303af9b4d</guid>
            <category><![CDATA[uav]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[bvlos]]></category>
            <category><![CDATA[drones]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Gabrielle Wain]]></dc:creator>
            <pubDate>Wed, 20 Nov 2019 17:39:12 GMT</pubDate>
            <atom:updated>2019-11-20T17:39:12.305Z</atom:updated>
            <content:encoded><![CDATA[<h3>Flying ‘True’ Beyond Visual Line of Sight</h3><h4>How Iris enabled the first true BVLOS missions</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SpS1ZFWsPOpSzpUA" /><figcaption>Flying over a field in Salina, Kansas</figcaption></figure><p>Recently, Iris Automation’s team of pilots traveled from Reno to rural Salina, Kansas to conduct field testing, which has become a routine trip for them this year. But this time something monumental happened: they flew ‘true’ Beyond Visual Line of Sight (BVLOS). In partnership with Kansas State Polytechnic and the Kansas Department of Transportation, our team flew BVLOS for over 150 miles, mapping out electric company Evergy’s power lines, which stretch across the state and beyond.</p><p>What is this ‘true’ Beyond Visual Line of Sight, you ask? It is a mission in which a drone flies Beyond Line of Sight of its pilot⁠ — either farther than the eye can see, or obstructed from sight in some way⁠⁠ — using only technological means, rather than any human intervention, to stay safely separated from other aircraft. Until recently, all missions that required a drone to be out of the field of view of the pilot required a visual observer to track the drone and radio back to warn the pilot if another aircraft came into view.</p><p>Not anymore; for <a href="https://www.auvsi.org/industry-news/kdot-ipp-team-conduct-landmark-bvlos-uas-flight-leveraging-only-onboard-detect-and">our mission in Kansas</a>, we only used Casia, our onboard Detect and Avoid (DAA) technology, after receiving permission to do so from the Federal Aviation Administration (FAA) under a waiver from Part 107 (small unmanned aircraft regulations) that allows us to fly BVLOS under certain circumstances, so long as Casia is onboard the drone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*naipeytyGRKrje8e" /><figcaption>The Iris Casia system</figcaption></figure><p>This wasn’t the first time Casia has enabled a ‘true’ Beyond Visual Line of Sight mission. Back in August, our team traveled to Alaska to support the University of Alaska-Fairbanks’ ACUASI team perform a <a href="https://www.auvsi.org/industry-news/university-alaska-fairbanks-team-completes-first-faa-approved-bvlos-mission-us">pipeline inspection mission</a> for Alyeska Pipeline Service Company, in partnership with the high-endurance drone company Skyfront and radar technology company Echodyne. This mission was the first to prove that these operations could be flown without a human — even in a brand new environment that presented additional stressors and challenges to our system.</p><p>The word I have heard the most since we received these permissions is <strong>how</strong>, as in, how did we get these groundbreaking permissions? Like anything in aviation, there is no simple answer. Here’s my take on how we got there.</p><h4>We took things step by step</h4><p>Anyone who has worked with the FAA knows the phrase “Crawl, Walk, Run,” their approach to any technological advancement or regulatory change. With both of these projects, we first meticulously demonstrated our technology’s performance and reliability. Hence the many deployments of our Flight Operations team to Kansas, as well as to Alaska, to fly demonstration missions to collect data, which was then rigorously processed and analyzed.</p><p>This methodical and rigorous approach is part of Iris’ DNA — it’s why our Flight Operations team based in Reno, Nevada tests every element of our technology on daily, ‘real world’ missions, using a drone against a manned aircraft. And it’s why we built an in-house simulator to test our technology in thousands of simulated encounters between drone and manned aircraft which are too dangerous to replicate in real life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FHS9qFWAwu0hRSOD" /><figcaption>Flight testing in Kansas</figcaption></figure><h4>We have the right technology</h4><p>Iris’ Detect and Avoid technology is specifically designed to enable true BVLOS operations. We’re starting small in remote areas like rural Kansas and Alaska to demonstrate its capabilities and potential, with the ultimate goal of enabling BVLOS operations across any distance and in any location. Unlike most missions that require ground-based sensors to detect aircraft, our customers only need to equip their drones with Casia. In addition to the extensive testing we conduct, our team of expert engineers continually build on its capabilities and features.</p><h4>We partner with fantastic organizations</h4><p>Iris’ Casia is a key enabling technology for any company who wants to improve the efficiency and safety of their operations by flying BVLOS. In Kansas and Alaska we have worked in partnership with bold, innovative, and⁠⁠ — most importantly — safety focused organizations and teams to demonstrate what flying true BVLOS really means to the world. We could not have achieved these monumental permissions without our partnerships with the FAA’s Integration Pilot Program projects in Kansas and Alaska, and, of course, the FAA itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItZ5hUtsm_KWeImOxoRQxQ.jpeg" /><figcaption>Members of the Iris Flight Operations Team, Kansas State Polytechnic, and Kansas Department of Transportation</figcaption></figure><p>If you have a mission you’d like to fly true Beyond Visual Line Of Sight and are aligned with the approach I’ve laid out above, please get in touch. Getting BVLOS permissions isn’t an easy path, but by taking things step by step, using the right technology, and working in partnership, it becomes far more achievable and moves us towards increased innovation and safety in our national airspace.</p><p><em>Iris is hiring! Browse our open positions at </em><a href="https://www.irisonboard.com/careers/?utm_source=Medium&amp;utm_medium=Link%20at%20end%20of%20blog%20posts&amp;utm_campaign=Recruiting%20from%20blog"><em>www.irisonboard.com/careers</em></a></p><p><em>Originally published at </em><a href="https://www.irisonboard.com/2019/10/25/what-it-takes-to-fly-true-beyond-visual-line-of-sight/"><em>https://www.irisonboard.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd8303af9b4d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iris-automation/what-it-takes-to-fly-true-beyond-visual-line-of-sight-fd8303af9b4d">What It Takes To Fly ‘True’ Beyond Visual Line of Sight</a> was originally published in <a href="https://medium.com/iris-automation">Iris Automation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 3-legged “Safety Stool” of Drone Safety]]></title>
            <link>https://medium.com/iris-automation/the-3-legged-safety-stool-of-drone-safety-c09cbce67d47?source=rss----1fabdab22a78---4</link>
            <guid isPermaLink="false">https://medium.com/p/c09cbce67d47</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[drones]]></category>
            <category><![CDATA[safety]]></category>
            <category><![CDATA[aviation]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Ricky Gonzalez]]></dc:creator>
            <pubDate>Mon, 04 Nov 2019 18:57:59 GMT</pubDate>
            <atom:updated>2019-11-05T23:52:20.479Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*67jRZLAOljt7ARLopLnW6Q.gif" /></figure><h3>The 3-legged “Safety Stool”</h3><h4>The key safety principles that drive the success of the Flight Operations team at Iris Automation</h4><p>Iris Automation relies on the testing of our Detect and Avoid technology, Casia, through real-world field tests conducted by our Flight Operations team. The team is based in Reno, NV, but they have traveled to various parts of the country and conducted missions across different environments. The data collected from these flights is valuable for the verification and improvement of our computer vision-based Casia. With each new update and integration, there is a team of pilots and technicians out in the field flying our fleet of unmanned aircraft, testing the validity of the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*bAAMQfACO3iyErmr0WuMTQ.jpeg" /><figcaption><strong>Mark Genung</strong>, Director of Flight Operations</figcaption></figure><p>The team is led by Mark Genung, Director of Flight Operations. With over 30 years of military experience operating Navy ships and aircraft at sea, Mark knows the importance of safety and efficiency. He is responsible for the safe execution of the flight missions, from routine technical tests to planning intercepts between our Casia-equipped drones and General Aviation aircraft. Mark has determined that the continued success of the Flight Ops team is due to following what he calls <strong>The 3-Legged Safety Stool</strong>. We will break down each “leg” seen as an essential component of this policy.</p><blockquote>“Like any three-legged stool, if one leg is removed or cut off — the stool is compromised”</blockquote><h3>1 | Highly Trained and Qualified Personnel</h3><p>The success of the team is dependent on each individual bringing the best of their training and experience. Iris seeks responsible and passionate members who are comfortable with adapting to situations prone to environmental or technological change. All Iris pilots are certified by the FAA, which includes both our General Aviation (GA) and Remote Pilots. General Aviation handles the flying of small private aircraft used for the intercept testing of Casia, while Remote Pilots operate the various drones in the Iris fleet and the systems they run on (including Casia).</p><blockquote>Mark explains, “All our pilots are also Remote Pilots who receive sUAS training and must qualify on each aircraft model Iris flies. Finally all receive advanced training in how to use our DAA technology and fly our data collection test patterns.”</blockquote><p>Our Chief Pilot, Ryan McMaster, is a qualified Remote Pilot and flight instructor who has developed a curriculum for GA high density altitude flight operations while safely flying precise flight paths. This provides a guideline and ensures safety for both our personnel and equipment when we have tests designed to have drones in very close proximity to low-flying aircraft. The drone industry has grown and adapted according to regulations and innovation. The Iris Flight Ops team is constantly working to keep up with the latest developments, as seen in their participation in historic FAA-approved flight tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uUaY2nxEdt80aAsRi0cg7A.jpeg" /><figcaption><strong>Gregory Bowe II</strong>, Senior Flight Operations Technician</figcaption></figure><h3>2 | Well Maintained Equipment</h3><p>Casia has flexible integration with unmanned vehicles, meaning that it can be attached to any drone according to the needs of the user. In some situations one might need a multi-rotor drone and in others, a fixed-wing drone. The Flight Ops team is trained to operate and maintain multiple small unmanned aircraft system (sUAS) models. This provides validation for Casia’s application across a wide-range of functions, as there is no requirement for what aircraft our partners and customers choose to integrate with.</p><blockquote>“Each of our qualified pilots is assigned a sUAS model to maintain, upgrade and integrate. Our first line of defense is our robust pre-flight checks that ensure all aircraft subsystems are working properly before flight.”</blockquote><p>Many of the field tests are conducted in remote locations, therefore it’s crucial that the equipment is up to capacity so that reliable data is collected. To keep a high operational availability, the team brings two or more models of the same aircraft to the field in case there is a failure with one sUAS. The team usually flies about three days a week, and this routine allows time for preventive and corrective maintenance. When a test is completed, the team immediately logs and plans to fix any equipment errors so that they can be addressed in time for future flights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TVTIwKBaEicQVhYQScUlww.jpeg" /><figcaption>The Flight Ops team participating in the Kansas UASIPP</figcaption></figure><h3>3 | Validated and Proven Operating Procedures</h3><p>It is pivotal that the team conducts operations according to our Iris Flight Operations Manual (FOM). This brings a proven and tested structure so that current members have the necessary guidelines to follow. This also becomes a resource for future team members so they can easily adapt. When dealing with different systems, environments and personnel, it’s important that there are procedures to follow so that the operational mechanism continues forward in a safe and detailed manner. Mark explains just how in-depth the procedures are:</p><blockquote>“The FOM lays out personnel requirements, equipment lists, communication protocols, operational risk management, general and emergency procedures. Each aircraft model has an individual set of Standard Operating Procedures. These procedures include sUAV capabilities and limitations, pre-flight and post-flight procedures, and specified emergency procedures.</blockquote><p>Before any drone takes off, there are strict protocols that the pilots and technicians must follow. Many procedures follow those provided by the Original Equipment Manufacturer (OEM), as well as those applicable to the Iris mission goals. There are Ground Control Stations used across our fleet to assist in training and to also minimize any confusion across sUAV models. Having a regular schedule of flight tests allows for the team to learn new situations and environmental conditions. Procedures are updated and revised as new information is available and developments occur.</p><p>Our safety program is based on focusing on all three of these components. Iris Automation is committed to safety, not just in the sense-and-avoid function of Casia, but in the flight testing operations that make it all possible.</p><p><em>Iris is hiring! Browse our open positions at </em><a href="https://www.irisonboard.com/careers/?utm_source=Medium&amp;utm_medium=Link%20at%20end%20of%20blog%20posts&amp;utm_campaign=Recruiting%20from%20blog"><em>www.irisonboard.com/careers</em></a></p><p><em>Originally published at </em><a href="https://www.irisonboard.com/2019/11/04/the-3-legged-safety-stool/"><em>https://www.irisonboard.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c09cbce67d47" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iris-automation/the-3-legged-safety-stool-of-drone-safety-c09cbce67d47">The 3-legged “Safety Stool” of Drone Safety</a> was originally published in <a href="https://medium.com/iris-automation">Iris Automation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leaving a Floral-Printed Mark on Iris Culture]]></title>
            <link>https://medium.com/iris-automation/leaving-a-floral-printed-mark-on-iris-culture-3be451f6fe06?source=rss----1fabdab22a78---4</link>
            <guid isPermaLink="false">https://medium.com/p/3be451f6fe06</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[casual-fridays]]></category>
            <dc:creator><![CDATA[Angelo Stekardis]]></dc:creator>
            <pubDate>Tue, 08 Oct 2019 22:41:06 GMT</pubDate>
            <atom:updated>2019-10-08T22:41:06.347Z</atom:updated>
            <content:encoded><![CDATA[<h4>How Aloha Fridays became an Iris tradition</h4><blockquote>“Every revolution was first a thought in one man’s mind” — Ralph Waldo Emerson</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*CwZJs27T8o4JT9v_" /><figcaption>Aloha Friday at the 2019 Iris Retreat</figcaption></figure><p>One of the most exciting things about joining an early stage start-up is the opportunity to make an impact outside of your area of expertise. For some at Iris, it’s getting involved in product management despite being a production engineer. For others, it’s helping to write regulatory waivers despite being a UAS pilot. For me, it was wanting to leave my mark on Iris culture despite working as a computer vision software engineer. I didn’t know how I would, but I knew that I wanted Iris to always feel like a fun place to work, especially when the team was building the early version of our product.</p><p>When I joined the team in May of 2017, Fridays always seemed a little dull. At the time, Fridays felt like one last exhausting push to get all of our tasks completed before the weekend. Hoping to make the end of the week a little more fun for the team, I had the idea of bringing Aloha Fridays to Iris — encouraging my teammates to throw on their best Hawaiian shirt and come into work in a more relaxed state of mind. In college and in previous jobs, Aloha/casual Fridays always seemed to make people a little more positive on Friday — giving them something fun to look forward to at the end of each week. However, the Iris team was more than a little hesitant to adopt the idea. In fact, it took about a year of being the only participant for others to join the movement.</p><blockquote>It wasn’t until the summer of 2019 when the movement started to become a revolution</blockquote><p>During the summer of 2018, two of our software engineering interns finally embraced the Aloha mindset. This was enough to convince a couple other Irisians to temporarily join the movement, but after the interns left, participation was low (one colleague did institute his own version, Feline Friday, of which he remains the sole participant). A couple others and I still donned a Hawaiian shirt every Friday, but it wasn’t until the summer of 2019 when the movement started to become a revolution. I’m still not sure what caused this massive wave of adoption, but at a certain point, around half of the company began regularly participating in Aloha Fridays.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*rAVi_13-acrmkicH" /><figcaption>Here I am sandwiched by our two like-minded interns</figcaption></figure><p>All of this peaked at our recent 2019 company retreat; I asked the organizers if we could take our Aloha Friday tradition to the next level, from which our first annual “Aloha Parade” was born. Groups of Iris team members took turns parading/Hula dancing around the balcony as “It’s Five O’Clock Somewhere” played in the background. Team members were also competing for prestigious honors such as “Best parade performance” and “Best style.”</p><p>Almost everyone brought or borrowed a Hawaiian shirt and showed off their uniqueness, style, and overall Aloha spirit to the rest of the company — proof that the Iris’ Aloha Friday revolution had reached its full potential!</p><p>After everyone had so much fun during the parade, I genuinely believe that Aloha Fridays are here to stay. It is so gratifying to know that my small contribution well outside my technical role’s wheelhouse has made a positive and permanent impact on Iris’ culture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*NOorA_hiKm14YK5T5naMyw.gif" /><figcaption>Aloha Parade (featuring Feline Friday)</figcaption></figure><p><em>Iris is hiring! Browse our open positions at </em><a href="https://www.irisonboard.com/careers/?utm_source=Medium&amp;utm_medium=Link%20at%20end%20of%20blog%20posts&amp;utm_campaign=Recruiting%20from%20blog"><em>www.irisonboard.com/careers</em></a></p><p><em>Originally published at </em><a href="https://www.irisonboard.com/2019/10/08/my-way-or-the-hawaii-way/"><em>https://www.irisonboard.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3be451f6fe06" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iris-automation/leaving-a-floral-printed-mark-on-iris-culture-3be451f6fe06">Leaving a Floral-Printed Mark on Iris Culture</a> was originally published in <a href="https://medium.com/iris-automation">Iris Automation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Journey to Casia: Part One]]></title>
            <link>https://medium.com/iris-automation/the-journey-to-casia-part-one-faea27491f02?source=rss----1fabdab22a78---4</link>
            <guid isPermaLink="false">https://medium.com/p/faea27491f02</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[drones]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[electrical-engineer]]></category>
            <dc:creator><![CDATA[Zack Goyetche]]></dc:creator>
            <pubDate>Tue, 09 Jul 2019 23:48:34 GMT</pubDate>
            <atom:updated>2019-10-24T22:18:45.288Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Journey to Casia</h3><p>My experience developing hardware for an AI start-up</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*aOWlU_BsllRWttP6ETcNLw.png" /><figcaption>The Iris Casia module.</figcaption></figure><p>As an electrical engineer who is obsessed with creating the physical, I delightedly jumped at the opportunity to design and build hardware for Iris Automation when it presented itself one year ago.</p><p>This opportunity was unique in that I would single-handedly own everything under the umbrella of electronic hardware design, gaining a first-hand holistic understanding of what it takes to design and build electronics that are capable of meeting the demands of today’s problems.</p><p>In May of 2018 I found myself on a plane to Iris Automation’s headquarters in the Financial District of San Francisco. I would be on-boarding and meeting with the CTO to learn about the present state of Iris’ technology and the direction the hardware needed to go to support artificial intelligence on the edge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*rd8b4C_AszjG8iSyCFTQIg.jpeg" /><figcaption>My first time visiting San Francisco.</figcaption></figure><p>Iris Automation is creating a vision and AI based sense-and-avoid technology that will give drones the ability to fly, what the FAA calls, “beyond visual line of sight.” To put it simply, Iris’ technology would eliminate the FAA’s requirement of a human observer maintaining a visual line of sight with the drone at all times. Solving this problem will provide immense value to society by allowing drones to be utilized for tasks that are too dangerous, dirty, or dull for humans to do.</p><p>After spending two days in a meeting room white-boarding a rough plan of action, I set out to begin the hardware design for Iris’ compute module, later named ‘Casia’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*mTtibMGk4zSG73GiJI4uHA.jpeg" /><figcaption>Day one of white boarding and coming up to speed.</figcaption></figure><p>My first order of business was to create templates for schematics, stack-ups, bill-of-materials, fabrication drawings, and assembly drawings. These documents are the distilled result of all of the design efforts, containing all of the information required to manufacture and build the hardware.</p><blockquote><em>“Organization will set you free.” — Alton Brown</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*FhqY5okkFbqqaVj2k-BxFw.jpeg" /><figcaption>My work station at the Iris Reno office.</figcaption></figure><p>It is important to get documentation right from the get-go, as playing catch up will undoubtedly result in mistakes that waste time, energy, and money. I have developed a keen appreciation for organization, as it is an excellent weapon to combat complexity. As Alton Brown put it, “Organization will set you free.”</p><p>Once the templates were in place, the real work could begin. For those unfamiliar with electronic design, there are three major elements that go into producing the design files required for creating printed circuit boards:</p><ol><li>Individual components</li><li>Schematic</li><li>Layout</li></ol><p>In large companies, these tasks are generally performed by three different people. A librarian will create digital representations of the components and manage the company’s parts library, a design engineer will create the schematic, and the CAD (computer aided design) group will combine both of these into a physical representation of what will actually be fabricated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*VcTgSIr71PQ69y7UzNwyCA.jpeg" /><figcaption>Casia’s main printed circuit board layout.</figcaption></figure><p>As the only electrical engineer at Iris, I became intimately familiar with all of these tasks, leveraging my past experiences and observations at larger companies to figure out how to best fill these roles with one mind.</p><p>There are some serious advantages and disadvantages to having one person perform all of these tasks.</p><p>The greatest advantage is speed. If I need something, I can just do it. I can assume the role of the librarian, design engineer, layout engineer, firmware engineer, test engineer, compliance engineer, component engineer, buyer, and project manager, without having to waste a single minute in meeting rooms conveying information back and forth.</p><p>This increase in agility and speed is only a net gain so long as it doesn’t result in a mistake or set back that could have otherwise been avoided by simplifying and compartmentalizing these tasks into specialized individuals or groups. At start-ups, speed is generally favored over avoiding mistakes.</p><p>There is also something to be said for having numerous minds to bounce ideas off of and gain perspective when stuck on challenging problems or decisions. This is perhaps the biggest down side to working as a one man team.</p><blockquote><em>“If you want to go fast, go alone. If you want to go far, go together.” — African Proverb</em></blockquote><h3>The Balancing Act</h3><p>Casia needs to not only perform its intended functions, but to do so in a manner that is both efficient and compact, as energy and weight are scarce resources on small aircraft. To achieve this, choosing the right components became a multidimensional balancing act.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*nmQfMs6M2eVJsINn7CoXmA.jpeg" /></figure><p>Because different drones utilize varying amounts of battery cells connected in series, Casia needed to be able to accept a wide voltage input range which could then be regulated to the six different voltage levels required by all of the peripherals within the module.</p><p>This meant that switching regulators had to be used, as their efficiency over a wide input range far outperforms their linear counterparts. This increase in power efficiency comes at the expense of additional components (cost, size, and weight).</p><p>The regulators’ switching frequencies would then be fine tuned in simulation to reduce the amount of inductance and capacitance required to operate. In general, higher switching frequencies allow for a smaller inductor and filter capacitors, but this comes at the expense of both increased switching losses and potential electromagnetic interference issues.</p><p>There is a saying in economics that, “There is no such thing as a free lunch,” and this is also true in engineering. Every decision comes at a cost and it is up to the designer to spend their design choices wisely.</p><p>The next challenge was to accommodate for the immense amount of data being moved into, out of, and within Casia. Cameras produce a lot of data, and this data needs to be moved as quickly as possible into the on-board GPU, as well as being stored in non-volatile memory. To achieve this, Casia utilizes many high speed interfaces, such as MIPI CSI-2, USB 3, GMSL, and SATA to name a few.</p><p>Accommodating for circuits at this speed (rise time) isn’t a trivial task, so I turned to some well-known resources such as, “High Speed Digital Design: A Handbook of Black Magic,” by Howard Johnson and Martin Graham.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*-Hrurxqo5YcpyvcKnS44eQ.jpeg" /><figcaption>Knowledge = power.</figcaption></figure><p>Additionally, I utilized Iris’ professional development stipend to attend <a href="https://www.pcbwest.com/">PCB West</a>, a four day conference in Santa Clara with classes focused around high speed design, electromagnetic compatibility, and manufacturing.</p><p>Beyond being electrically functional, Casia had to be user friendly and robust. This meant that connectors should be logically placed in such a way that they would be accessible by a human hand once installed on a drone, and that the hardware would contain a redundant microcontroller that would serve as a watchdog over the main processor in the event that it malfunctions.</p><p>All of this aforementioned work simply allows for the module to be powered and for data to be moved and operated on. While all of this ground work is necessary, it is yet to make for an interesting and useful product.</p><p>What makes Casia interesting is the software and machine learning that brings it to life, allowing it to act on the data it gathers in order to prevent its host from colliding with other aircraft.</p><p>After hundreds of hours of focused design effort, I was finally ready to send off all of my files to the contract manufacturer. Completing a PCB design is a lot like packing for a very long and distant trip, you only get one shot and there’s no turning back to grab a forgotten item.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*ngAUTH2uKal9TCdHIsh2uA.jpeg" /><figcaption>Bon voyage!</figcaption></figure><p>For the software folk, it’s akin to writing code for an entire application and only getting to compile once you’re finished. As you can imagine, attention to detail and relentless foresight is critical. Oh, and it costs thousands of dollars each time you compile.</p><p>In the click of a button, the files are sent to the contract manufacturer, and your bank account appears as if you had just purchased a nice used car.</p><p>In the coming days, I would serve as a point of contact to address any discrepancies discovered by the contract manufacturer.</p><p>Each email or phone call sent my heart racing with fear that I had made a mistake. Majority of these issues were minor, such as ceramic capacitors being out of stock. The lack of supply of ceramic capacitors would become a recurring theme throughout 2018 and early 2019.</p><p>One evening, during my commute home from work, I received a phone call that nearly gave me a heart attack. The person on the phone told me that they were having trouble soldering a connector to our boards, and that they suspected the footprint was incorrect. If that wasn’t bad enough, they followed up by saying that they had already soldered the other 428 components onto each of the boards.</p><p>I immediately felt nauseous. This was easily the most important component on the board, as it is used to interface to Casia’s main compute module, an NVIDIA Jetson TX2. If this component could not be soldered onto the boards, the entire prototype run would have been a waste.</p><p>I rushed home and fired up my computer to begin checking the design files and datasheets. After combing over the connector in question, I convinced myself that I had not made a mistake. The contract manufacturer was closed so I would have to wait until morning to get more information.</p><p>After a restless night, I would come to find out that the assembler had the wrong connector and that they would be overnighting the correct one to finish assembly. The confirmation was relieving, but I wouldn’t feel content until I had the boards in hand.</p><p>A few days later, still on edge, I received the boards in the mail and the moment of truth commenced.</p><p>I carefully cut into the box and began unpacking the boards from their protective ESD packaging. My mind was playing out scenarios where the boards would not power up and I would look like a complete fool.</p><p>I reluctantly applied power to the input.</p><p>To my delight, I was greeted by the welcoming green glow of the LED whose function is to indicate that power has been applied. This was good. Nothing was on fire, nothing was hot to the touch.</p><p>I began probing test points with a multimeter and read the correct voltages on each of the six voltage regulators’ outputs. The current draw from the power supply seemed reasonable based on my power calculations. It was now safe to begin testing the numerous sub-circuits with Casia.</p><p>I flashed some test firmware that I had written onto the microcontroller that is responsible for booting up the Jetson TX2. I then connected the TX2 to the 400 pin connector on the carrier board. Its alignment with the stand-offs and mounting holes was perfect.</p><p>I reapplied power and noticed that the current draw from the power supply had increased. The TX2 was active and was drawing power. I plugged in an Ethernet cable and anxiously waited for a new IP address to appear on the local network. I SSH’d into the newfound device and was greeted by the Linux terminal. A feeling of relief swept over me.</p><p>Over the coming weeks, I would go on to perform a laundry list of checks and tests on Casia’s interfaces and peripherals. Mistakes were made on the first prototype, but nothing an X-ACTO knife, 30 gauge wire, and some out of place resistors couldn’t fix.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*_YWb0XQtjaHYNm-MMxGywA.jpeg" /><figcaption>A few modifications…</figcaption></figure><p>I reworked the hardware into a state where I was comfortable putting it on a drone for field testing, where it would be flown against a Cessna 172 — Iris Automation has a Flight Operations team consisting of both remote and commercial pilots who fly drones against manned aircraft regularly in order to collect data and prove out our technology.</p><p>The field testing on the first prototype couldn’t have gone better. Casia was communicating with the autopilot, and its camera was capturing data and storing it to its solid state hard drive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*RoYnvnVFJCHcBie3jeJonQ.jpeg" /><figcaption>Iris’ Chief Pilot, Ryan McMaster (left) and myself.</figcaption></figure><p>At this point, the lessons learned could be wrapped into a second revision, and passing compliance testing would be my next focus before proceeding with a production run.</p><p>If you found this story interesting, stay tuned for part two where I will share my experience with compliance testing, our first major production run, feedback from AUVSI XPONENTIAL 2019, and my feelings surrounding our first official customer sale!</p><p><em>Iris is hiring! Browse our open positions at </em><a href="https://www.irisonboard.com/careers/?utm_source=Medium&amp;utm_medium=Link%20at%20end%20of%20blog%20posts&amp;utm_campaign=Recruiting%20from%20blog"><em>www.irisonboard.com/careers</em></a></p><p><em>Originally published at </em><a href="https://www.irisonboard.com/2019/07/09/the-journey-to-casia-part-one/"><em>https://www.irisonboard.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=faea27491f02" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iris-automation/the-journey-to-casia-part-one-faea27491f02">The Journey to Casia: Part One</a> was originally published in <a href="https://medium.com/iris-automation">Iris Automation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Look Inside the Iris Reno Office]]></title>
            <link>https://medium.com/iris-automation/a-look-inside-the-iris-reno-office-4705a273b6f0?source=rss----1fabdab22a78---4</link>
            <guid isPermaLink="false">https://medium.com/p/4705a273b6f0</guid>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[drones]]></category>
            <category><![CDATA[office]]></category>
            <dc:creator><![CDATA[Taylor Westerman]]></dc:creator>
            <pubDate>Tue, 30 Apr 2019 22:25:49 GMT</pubDate>
            <atom:updated>2019-05-24T21:46:28.237Z</atom:updated>
            <content:encoded><![CDATA[<p>Behind the scenes at our Flight Ops and Hardware headquarters</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*im1gxE6RKk8iDy6v" /></figure><p>In the midtown area of the ‘Biggest Little City’ sits the University of Nevada, Reno’s In<strong>nev</strong>ation Center. Today I’m excited to take you on a tour of our Reno office and perhaps in doing so will have you asking, “where can I sign up?”</p><p>Four months ago I moved to Reno and joined Iris, and I had no idea what I was walking into. From the outside, the UNR Innevation Center is an unappealing run-of-the-mill office space surrounded by businesses and a law office. Something you might expect a standard no-frills company to operate out of. Well, think again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y_gUo1MhlVpvN53j" /><figcaption>9The Reno Innevation Center, where the Iris Reno office is located.</figcaption></figure><p>From the moment you walk into the Innevation Center you are greeted with colorful and inspiring wallpaper, the friendliest staff (mostly students) you could imagine and…endless opportunities. You may say, why endless opportunities? Well, just stay with me as we go on a tour of this incredible facility.</p><p>The third floor hosts the greatest company in the Innevation Center, and I might be a little biased, but I will let you decide- Iris Automation! As you enter the secure door, our promotional banner lets you know that Iris Automation will unlock your drones! That one little word ‘drone,’ seems to stop everyone passing through in their tracks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Jfe1tiOa6BFIQqWc" /><figcaption>The Flight Operations work area, featuring our drone, Albus Dumbletross.</figcaption></figure><p>Upon entering the Iris office you are greeted with the organized chaos of our Flight Operations team’s work space. Here they work daily on building and repairing Unmanned Aircraft Vehicles (UAVs) as well as integrating Iris’ hardware into the UAVs. This area is also shared with the greatest invention for open work spaces- our phone booth! I honestly don’t think it can go an hour without being used; does that say we have too many meetings or is it just a great place to getaway during the day?</p><p>As we snake around the office you are next greeted by, well, me! Being in the middle of our work space allows me to be easily accessible to our whole Reno team and it works out quite well. Continuing around the corner is our storage area. Right now it is very well organized (I love organizing), with little in it, but I know it is just a matter of time before that all changes. The larger the company grows the more space we will need and I think it’ll be great when completing a total reorganization overhaul takes more than 20 minutes, that means we are bigger and better!</p><p>As we continue out of the storage space and into the production area (known internally as the forbidden work space) we see all of the details that go into packaging our hardware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IVsL1S12Sh4fmlegMk-lBA.jpeg" /><figcaption>Seedlings in the process of becoming new plant friends!</figcaption></figure><p>As we continue, we make our way through the vegetable and succulent garden (planted as group during a Friday evening ‘Afterhours social’) to get to the Engineering and Flight Operations desks. The first employees in the Reno office were Flight Operations and made up the majority of the office until just the beginning of this year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TG9NhtJ4J7M_jmeA" /><figcaption>Taking a break from Smash Bros for a meeting.</figcaption></figure><p>Now we follow the plants as they lead to my favorite part about our office…our social space! This was my first major accomplishment in the office and I really enjoy the way it has been received and how often we use it. Here we play games, mostly Smash Bros on the Nintendo Switch, and conduct our Afterhours socials and team lunches. If you feel like working in this space, which I often do, or you just need to take a breather from your desk, you can sit in the incredibly comfortable bean bag chairs or couch we were outfitted with by our Chief Pilot, Ryan McMaster. Although we share this floor with 3 other companies, there is one thing we don’t share — our snacks! This area is dedicated to providing our employees tasty, sometimes healthy, but always substantial snacks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eaLjZW0HNh9xwW7Q" /><figcaption>An award from the Iris 2018 Company Retreat, made in the Innevation Center’s Makerspace.</figcaption></figure><p>Next our tour takes us to our final location, my favorite part about the Innevation Center- the basement, aka the Makerspace. This floor is full of nearly every gizmo, gadget and thingamabob you could imagine and is available to students and members nearly all free of charge, including laser cutters and 3D printers!</p><p>If gizmo, gadgets and thingamabobs aren’t your thing, then perhaps the ping pong table, bicycles, or entertainment room will get you excited. In addition to having an incredible work space we also get to support our local college by renting it from them. They have the greatest staff and are providing resources for startups like us to succeed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-pluP2-SfdgQk5Ij" /><figcaption>Open seating at the Innevation Center.</figcaption></figure><p>Now, let’s move on to the second floor, a collaborative work space with a combination of unassigned desks and assigned company work space- it used to be home to Iris. When the Reno office opened in 2017, we occupied just two desks, but we’ve expanded quickly and will continue to do so — there’s been four hires at Iris just since I started writing this post!</p><p>I hope you enjoyed following me on this tour of our Reno Office; until next time!</p><p><em>Originally published at </em><a href="https://www.irisonboard.com/2019/04/22/a-look-inside-the-iris-reno-office/"><em>https://www.irisonboard.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4705a273b6f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iris-automation/a-look-inside-the-iris-reno-office-4705a273b6f0">A Look Inside the Iris Reno Office</a> was originally published in <a href="https://medium.com/iris-automation">Iris Automation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>