<node id="620412">
  <nid>620412</nid>
  <type>news</type>
  <uid>
    <user id="34795"><![CDATA[34795]]></user>
  </uid>
  <created>1555342686</created>
  <changed>1555355331</changed>
  <title><![CDATA[Workday Go-Live Update]]></title>
  <body><![CDATA[<p>Financial System users,</p>

<p>As you know, we are rapidly approaching our Workday go live which is slated to launch on <strong>July 1, 2019</strong>. In preparation for go live, program leadership held the first of four go/no-go discussions earlier this week. In these discussions, we evaluate status, assess risks, and develop effective strategies to alleviate obstacles in our path. The goal of these sessions is to use metrics to review evaluation criteria and make determination our readiness for go live. We will send a communication following each of these checkpoints with our current status and highlighting areas that need focus between now and July.</p>

<p>After this first check point, <strong><em>we believe that we are on track to launch Workday on July 1<sup>st</sup></em></strong>. We recognize that there is still a lot of work to be done between now and then, and that there are several areas of particular focus, including:</p>

<ul>
	<li>Data Conversion &amp; FDM Mapping &ndash; additional validation needed to ensure data effectively converts over to Workday. We are developing and will communicate a schedule to continue FDM validation with campus units between now and go live (to be released the week of April 15<sup>th</sup>).</li>
	<li>End to End Testing &ndash; We are adding an additional End to End Cycle (April 15 to May 17<sup>th</sup>) to test any remaining functionality, integrations, robust scenarios and reports. In this cycle, it is critical to that ensure Extended Systems can properly integrate with Workday.</li>
	<li>Reporting &ndash; Reports still need to be built and tested (700 delivered reports will be available and 64 custom reports).</li>
</ul>

<p>Leadership will review status again in mid-May, and we will send an additional communication shortly afterwards.</p>

<p>Looking back over the last two years, we have come a long way in our Workday knowledge, identification and building of a team, and the design and building of our future Finance system. &nbsp;I want to extend sincerest thanks to the Georgia Tech community for supporting this program and ask that you continue to dedicate the necessary time and effort that is needed in order for the launch phase to run smoothly. I also want to remind you to continue visiting the Transformation website (<a href="http://www.transformation.gatech.edu">www.transformation.gatech.edu</a>) and sending your questions to the ERP helpdesk (<a href="mailto:erp.ask@gatech.edu">erp.ask@gatech.edu</a>). These resources are in place to support our end users and ensure Georgia Tech is ready for go live.</p>

<p>Jennifer Hubert</p>

<p>Associate Vice President, Institute Planning &amp; Resource Management</p>

<p>&nbsp;</p>

<p>Katie Crawford<br />
Financial Transformation project lead</p>
]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2019-04-15T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[In preparation for go live, program leadership held the first of four go/no-go discussions earlier this week.]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[<p>In preparation for go live, program leadership held the first of four go/no-go discussions earlier this week. In these discussions, we evaluate status, assess risks, and develop effective strategies to alleviate obstacles in our path. The goal of these sessions is to use metrics to review evaluation criteria and make determination our readiness for go live.</p>
]]></value>
    </item>
  </field_summary>
  <field_media>
          <item>
        <nid>
          <node id="620413">
            <nid>620413</nid>
            <type>image</type>
            <title><![CDATA[Workday is Coming]]></title>
            <body><![CDATA[]]></body>
                          <field_image>
                <item>
                  <fid>236232</fid>
                  <filename><![CDATA[workday is coming_sm3.png]]></filename>
                  <filepath><![CDATA[/sites/default/files/images/workday%20is%20coming_sm3.png]]></filepath>
                  <file_full_path><![CDATA[http://hg.gatech.edu//sites/default/files/images/workday%20is%20coming_sm3.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[erp.ask@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>602277</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>602277</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Enterprise Resource Planning]]></item>
      </og_groups_both>
  <field_keywords>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
