<node id="57489">
  <nid>57489</nid>
  <type>news</type>
  <uid>
    <user id="27279"><![CDATA[27279]]></user>
  </uid>
  <created>1252972800</created>
  <changed>1475895982</changed>
  <title><![CDATA[Aircraft Talking]]></title>
  <body><![CDATA[<p>
</p><p><em>Aviation Today</em> - September 2009<br />Engineers are devising new ways of monitoring the health and predicting the longevity of aircraft mechanical, avionics systems to prevent failures. . .  .Now, recent advances in sensor technology and wireless communications are improving our hearing, making failure prognostication possible. As a result, new ways of indirectly monitoring the health and predicting the longevity of aircraft mechanical and avionics systems are being devised. One university prognostication system is on the ready ramp. Engineers at GEORGIA TECH have devised models called adaptive prognostics that use data from real-time sensor measurements to calculate and continuously revise the amount of remaining useful life of various aircraft systems based on their current condition and health status. The predictions are then integrated with aircraft maintenance operations and supply chain policies as part of what the researchers call an "autonomous sense-and-respond logistics paradigm." "The system can be adapted to constantly monitor any moving part, from a ball bearing to aircraft electronics, sending out electronic alerts well in advance of a breakdown," said Georgia Tech engineer Nagi Z. Gebraeel.  <a href="http://www.aviationtoday.com/av/issue/feature/34484.html">Read more&gt;&gt;&gt;&gt;<br /></a></p>]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2009-09-15T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_media>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[bchristopher@isye.gatech.edu]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[<strong>Barbara Christopher</strong><br />Industrial and Systems Engineering<br /><a href="http://www.gatech.edu/contact/index.html?id=bt3">Contact Barbara Christopher</a><br /><strong>404.385.3102</strong>]]></value>
    </item>
  </field_contact>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <!--  TO DO: correct to not conflate categories and news room topics  -->
  <!--  Disquisition: it's funny how I write these TODOs and then never
         revisit them. It's as though the act of writing the thing down frees me
         from the responsibility to actually solve the problem. But what can I
         say? There are more problems than there's time to solve.  -->
  <links_related> </links_related>
  <files> </files>
  <og_groups>
          <item>57458</item>
      </og_groups>
  <og_groups_both>
          <item>
        <![CDATA[Engineering]]>
      </item>
          <item>
        <![CDATA[Research]]>
      </item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>145</tid>
        <value><![CDATA[Engineering]]></value>
      </item>
          <item>
        <tid>135</tid>
        <value><![CDATA[Research]]></value>
      </item>
      </field_categories>
  <core_research_areas>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>57458</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[ISyE External News]]></item>
      </og_groups_both>
  <field_keywords>
      </field_keywords>
  <field_userdata>
      <![CDATA[]]>
  </field_userdata>
</node>
