<node id="414531">
  <nid>414531</nid>
  <type>news</type>
  <uid>
    <user id="27787"><![CDATA[27787]]></user>
  </uid>
  <created>1434357115</created>
  <changed>1475896717</changed>
  <title><![CDATA[Upcoming SEVIS Outage: Friday, June 26-Sunday, June 28]]></title>
  <body><![CDATA[<p>The federal database for F and J student and scholar records in the U.S., SEVIS, is undergoing a major software upgrade process. The planned database outage starts 8 pm&nbsp; Friday, June 26 and is expected to end 8 pm Sunday, June 28. The federal systems that will be affected during the outage include:&nbsp;</p><ul type="disc"><li>SEVIS Fee Payment: The I-901 System will not be able to process SEVIS fee payments. </li><li>Visa Applications: U.S. Consulates may experience delays in issuing visas until the SEVIS data feed is restored.</li><li>Ports of Entry: CBP may send F and J visa holders to secondary inspection for processing. If you can avoid traveling during these days, please do so or be ready for long waits.</li><li>SAVE:&nbsp; Social Security Number and driver's license eligibility may be delayed.</li><li>E-Verify: Verification of employment eligibility of F and J visa holders may experience delays.<br /><br /></li></ul><p>If the outage lasts longer than the scheduled time, then there may be delays in OIE's ability to process any changes in SEVIS and could cause a delay in our normal five business day processing time. Please be assured that OIE will continue to process requests as soon as possible and we request your patience during this time of software upgrades.<br /><br /></p><p>You can find detailed information about the outage at <a href="http://studyinthestates.dhs.gov/2015/06/be-prepared-for-the-june-26-sevis-outage">Study in the States</a> website.</p>]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2015-06-15T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[SEVIS, the federal database for F and J students and scholars in the U.S., will be receiving software upgrades.]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_media>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[]]></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>1297</item>
      </og_groups>
  <og_groups_both>
      </og_groups_both>
  <field_categories>
      </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>1297</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Office of International Education]]></item>
      </og_groups_both>
  <field_keywords>
      </field_keywords>
  <field_userdata>
      <![CDATA[]]>
  </field_userdata>
</node>
