<node id="619543">
  <nid>619543</nid>
  <type>news</type>
  <uid>
    <user id="33067"><![CDATA[33067]]></user>
  </uid>
  <created>1553517965</created>
  <changed>1554829245</changed>
  <title><![CDATA[OneUSG — That Sounds Familiar...]]></title>
  <body><![CDATA[<div>
<div>
<p>It&rsquo;s been almost two&nbsp;years&nbsp;since Georgia Tech transitioned&nbsp;management of&nbsp;its health and wellness benefits from&nbsp;Georgia Tech&rsquo;s internal&nbsp;TechWorks&nbsp;platform&nbsp;to the new OneUSG Connect &ndash; Benefits portal. During that&nbsp;transition,&nbsp;Georgia Tech&nbsp;Human Resources&nbsp;introduced&nbsp; the&nbsp;OneUSG initiative and&nbsp;discussed&nbsp;what it means for Georgia Tech employees...but it&rsquo;s been a while.&nbsp;&nbsp;</p>
</div>

<div>
<p>OneUSG&nbsp;has been&nbsp;operating&nbsp;behind the scenes since 2014. By 2020, Georgia Tech employees will have experienced changes to their typical work day.&nbsp;&nbsp;</p>
</div>

<div>
<p><strong>What is OneUSG?&nbsp;&nbsp;</strong></p>
</div>

<div>
<p>OneUSG is&nbsp;a systemwide initiative to develop and implement a consistent approach to policies, procedures,&nbsp;and technology solutions&nbsp;beneficial to&nbsp;the University System of Georgia (USG)&nbsp;and its employees.&nbsp;</p>
</div>

<div>
<p><strong>What does that mean?&nbsp;&nbsp;</strong></p>
</div>

<div>
<p>First, remember Georgia Tech is one of 26 public, higher education institutions in Georgia. All 26 of these institutions are governed by the USG.&nbsp;&nbsp;</p>
</div>

<div>
<p>Governing boards like&nbsp;the USG&nbsp;vary from state to state. In Florida, North Carolina, and South Carolina each&nbsp;public&nbsp;institution has its own, independent&nbsp;governing board. But in&nbsp;states like&nbsp;Georgia, California, and Louisiana,&nbsp;all the public institutions are governed by one large system.&nbsp;&nbsp;</p>
</div>

<div>
<p>Before OneUSG,&nbsp;many&nbsp;of Georgia&rsquo;s public&nbsp;institutions&nbsp;operated&nbsp;with&nbsp;their&nbsp;own set of vendors and systems. The goal of OneUSG is to bring more consistency across the institutions, share knowledge, and make it easier to improve efficiencies.&nbsp;In the long-term, this will result in better technology and faster processes for&nbsp;all USG&nbsp;employees.&nbsp;&nbsp;</p>
</div>

<div>
<p><strong>What do you need to do now?&nbsp;&nbsp;</strong></p>
</div>

<div>
<p>First, visit&nbsp;<a href="https://transformation.gatech.edu/" rel="noreferrer" target="_blank">transformation.gatech.edu</a>&nbsp;and&nbsp;explore the initiatives connected to&nbsp;OneUSG&nbsp;. Second, take a look at article two to learn about upcoming OneUSG changes and how they will impact you.&nbsp;&nbsp;</p>
</div>

<div>
<p>&nbsp;</p>
</div>

<div>
<p><em>This article is the first in a four-part series titled&nbsp;Connecting Tech to OneUSG.&nbsp;</em></p>
</div>
</div>
]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[Connecting Tech to OneUSG Part 1/4]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2019-03-25T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[Connecting Tech to OneUSG Part 1/4: OneUSG has been operating behind the scenes since 2014. By 2020, Georgia Tech employees will have experienced a slew of changes to their typical work day.]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[<div>
<p>Connecting Tech to OneUSG Part 1/4:&nbsp;OneUSG&nbsp;has been&nbsp;operating&nbsp;behind the scenes since 2014. By 2020, Georgia Tech employees will have experienced a slew of changes to their typical work day.</p>
</div>
]]></value>
    </item>
  </field_summary>
  <field_media>
          <item>
        <nid>
          <node id="618773">
            <nid>618773</nid>
            <type>image</type>
            <title><![CDATA[OneUSG HCM Screenshot]]></title>
            <body><![CDATA[]]></body>
                          <field_image>
                <item>
                  <fid>235547</fid>
                  <filename><![CDATA[HCM Transformation.PNG]]></filename>
                  <filepath><![CDATA[/sites/default/files/images/HCM%20Transformation.PNG]]></filepath>
                  <file_full_path><![CDATA[http://hg.gatech.edu//sites/default/files/images/HCM%20Transformation.PNG]]></file_full_path>
                  <filemime>image/png</filemime>
                  <image_740><![CDATA[]]></image_740>
                  <image_alt><![CDATA[]]></image_alt>
                </item>
              </field_image>
            
                      </node>
        </nid>
      </item>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[ask.erp@gatech.edu]]></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>64319</item>
          <item>602277</item>
          <item>419211</item>
          <item>64303</item>
          <item>174291</item>
      </og_groups>
  <og_groups_both>
          <item>
        <![CDATA[Institute and Campus]]>
      </item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>129</tid>
        <value><![CDATA[Institute and Campus]]></value>
      </item>
      </field_categories>
  <core_research_areas>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
          <link>
      <url>https://hr.gatech.edu/hg/item/619541</url>
      <title></title>
      </link>
          <link>
      <url>https://hr.gatech.edu/news/oneusg-ive-heard-what-hcm</url>
      <title></title>
      </link>
          <link>
      <url>https://hr.gatech.edu/news/oneusg-you-said-things-were-changing</url>
      <title></title>
      </link>
          <link>
      <url>https://hr.gatech.edu/news/oneusg-what-expect</url>
      <title></title>
      </link>
          <link>
      <url>https://transformation.gatech.edu/hcm-transformation</url>
      <title></title>
      </link>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>64319</item>
          <item>602277</item>
          <item>419211</item>
          <item>64303</item>
          <item>174291</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Administration and Finance]]></item>
          <item><![CDATA[Enterprise Resource Planning]]></item>
          <item><![CDATA[Financial Services]]></item>
          <item><![CDATA[Human Resources]]></item>
          <item><![CDATA[OIT]]></item>
      </og_groups_both>
  <field_keywords>
          <item>
        <tid>174118</tid>
        <value><![CDATA[OneUSG]]></value>
      </item>
          <item>
        <tid>180875</tid>
        <value><![CDATA[HCM]]></value>
      </item>
          <item>
        <tid>180876</tid>
        <value><![CDATA[OneUSCG - Connect]]></value>
      </item>
          <item>
        <tid>173485</tid>
        <value><![CDATA[transformation]]></value>
      </item>
          <item>
        <tid>173048</tid>
        <value><![CDATA[erp]]></value>
      </item>
          <item>
        <tid>2775</tid>
        <value><![CDATA[human resources]]></value>
      </item>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
