<?xml version="1.0"?>
<report>
  <agency>NRC</agency>
  <generated>2013-05-14 14:26:10</generated>
  <items>
    <item id="2.1">
      <parent/>
      <text>Engage with customers to identify at least two existing major customer-facing services that contain high-value data or content as first-move candidates to make compliant with new open data, content, and web API policy.</text>
      <due>90 Days</due>
      <due_date>2012/08/21</due_date>
      <fields>
        <field>
          <type>select</type>
          <name>2-1-status</name>
          <label>Overall Status</label>
          <options>
            <option>
              <label>Not Started</label>
              <value>not-started</value>
            </option>
            <option>
              <label>In Progress</label>
              <value>in-progress</value>
            </option>
            <option>
              <label>Completed</label>
              <value>completed</value>
            </option>
          </options>
          <value>completed</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="2.1.1">
      <parent>2.1</parent>
      <text>Paragraph on customer engagement approach</text>
      <due>90 days</due>
      <due_date>2012/08/21</due_date>
      <fields>
        <field>
          <type>textarea</type>
          <name>2-1-1-customer-engagement-approach</name>
          <label>Paragraph on customer engagement approach</label>
          <options/>
          <value>To provide customers with the opportunity to comment on proposed choices for systems to open via web APIs, we will use our social media facilities (http://www.nrc.gov/public-involve/open/social-media.html). We have used Twitter and Blog posts in the past, to advise customers of specific initiatives and to solicit their feedback. For example, we used this approach to obtain feedback as we worked to publish the Addendum to our Open Government Plan and in developing our Customer Service Plan.&#xD;
Provided OMB with prioritized list of systems and proposed customer engagement approach on August 6, 2012. Invited the public to Tell Us Your Thoughts (http://www.nrc.gov/public-involve/open/digital-government/your-thoughts.html)through the NRC Blog, a web-based comment form, traditional mail, email, phone, or fax. Engaged customers with a Blog posting (http://public-blog.nrc-gateway.gov/2012/08/22/taking-the-next-step-building-a-21st-century-digital-government/) and related &#x201C;tweet&#x201D; on August 22, 2012. Also used our RSS Feeds (http://www.nrc.gov/public-involve/listserver.html#rss) on August 15 and 22, 2012, to notify site visitors of the opportunity to provide feedback.</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="2.1.2">
      <parent>2.1</parent>
      <text>Prioritized list of systems (datasets)</text>
      <due>90 days</due>
      <due_date>2012/08/21</due_date>
      <fields>
        <field>
          <type>text</type>
          <name>2-1-2-name</name>
          <label>System Name</label>
          <options/>
          <value>
            <value>Reactor Operating Status Reports</value>
            <value>Power Reactor Daily Event Reports</value>
            <value>Operating Reactor Inspection Reports</value>
            <value>Part 21 (Component Defect Reports)</value>
            <value>Public Affairs Daily News Releases</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>2-1-2-description</name>
          <label>System Description</label>
          <options/>
          <value>
            <value>A web-based system that allows the NRC to report on the operating status and power output of commercial power reactors located within the continental United States</value>
            <value>A web-based system that allows the NRC to report on the daily events and activities occurring at commercial power reactors located within the continental United States</value>
            <value>A web-based system that allows the NRC to report on observations and findings of inspections  occurring at commercial power reactors located within the continental United States</value>
            <value>A web-based system that allows the NRC to report on  licensed facilities, activities, or basic component that fail to comply with NRC regulations</value>
            <value>A web-based system that allows the NRC to communicate with the public daily on our regulatory activities and events</value>
          </value>
        </field>
        <field>
          <type>select</type>
          <name>2-1-2-scope</name>
          <label>System Scope</label>
          <options>
            <option>
              <label>Internal</label>
              <value>internal</value>
            </option>
            <option>
              <label>External</label>
              <value>external</value>
            </option>
            <option>
              <label>Both</label>
              <value>both</value>
            </option>
          </options>
          <value>
            <value>both</value>
            <value>both</value>
            <value>both</value>
            <value>both</value>
            <value>both</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>2-1-2-customer</name>
          <label>Main Customer</label>
          <options/>
          <value>
            <value>General public and agency stakeholders</value>
            <value>General public and agency stakeholders</value>
            <value>General public and agency stakeholders</value>
            <value>General public and agency stakeholders</value>
            <value>General public and agency stakeholders</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>2-1-2-uii</name>
          <label>Unique Investment Identifier</label>
          <options/>
          <value>
            <value>429-000002005</value>
            <value>429-000002005</value>
            <value>429-000001014</value>
            <value>429-000001014</value>
            <value>429-000002070</value>
          </value>
        </field>
      </fields>
      <multiple>1</multiple>
    </item>
    <item id="7.1">
      <parent/>
      <text>Engage with customers to identify at least two existing priority customer-facing services to optimize for mobile use.</text>
      <due>90 Days</due>
      <due_date>2012/08/21</due_date>
      <fields>
        <field>
          <type>select</type>
          <name>7-1-status</name>
          <label>Overall Status</label>
          <options>
            <option>
              <label>Not Started</label>
              <value>not-started</value>
            </option>
            <option>
              <label>In Progress</label>
              <value>in-progress</value>
            </option>
            <option>
              <label>Completed</label>
              <value>completed</value>
            </option>
          </options>
          <value>completed</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="7.1.1">
      <parent>7.1</parent>
      <text>Paragraph on customer engagement approach</text>
      <due>90 days</due>
      <due_date>2012/08/21</due_date>
      <fields>
        <field>
          <type>textarea</type>
          <name>7-1-1-customer-engagement-approach</name>
          <label>Paragraph on customer engagement approach</label>
          <options/>
          <value>To provide customers with the opportunity to comment on proposed choices of services to optimize for mobile use, we will use our social media facilities (http://www.nrc.gov/public-involve/open/social-media.html). We have used Twitter and Blog posts in the past, to advise customers of specific initiatives and to solicit their feedback. For example, we used this approach to obtain feedback as we worked to publish the Addendum to our Open Government Plan and in developing our Customer Service Plan.&#xD;
Provided OMB with prioritized list of services and proposed customer engagement approach on August 6, 2012. Invited the public to Tell Us Your Thoughts (http://www.nrc.gov/public-involve/open/digital-government/your-thoughts.html)through the NRC Blog, a web-based comment form, traditional mail, email, phone, or fax. Engaged customers with a Blog posting (http://public-blog.nrc-gateway.gov/2012/08/22/taking-the-next-step-building-a-21st-century-digital-government/) and related &#x201C;tweet&#x201D; on August 22, 2012. Also used our RSS Feeds (http://www.nrc.gov/public-involve/listserver.html#rss) on August 15 and 22, 2012, to notify site visitors of the opportunity to provide feedback.</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="7.1.2">
      <parent>7.1</parent>
      <text>Prioritized list of systems (datasets)</text>
      <due>90 days</due>
      <due_date>2012/08/21</due_date>
      <fields>
        <field>
          <type>text</type>
          <name>7-1-2-name</name>
          <label>System Name</label>
          <options/>
          <value>
            <value>Public Meeting Feedback System</value>
            <value>Top 5 Most-Accessed Agency Web Pages</value>
            <value>Regulatory Information Conference (RIC)</value>
            <value>Bring Your Own Device (BYOD)</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>7-1-2-description</name>
          <label>System Description</label>
          <options/>
          <value>
            <value>A web-based system that allows the NRC to collect public meeting feedback from meeting attendees</value>
            <value>A web-based system that allows the NRC to communicate with the public on our regulatory activities and events</value>
            <value>The NRC plans to implement the agency&#x2019;s first mobile solution for the 2013 RIC, which will be held on March 12 &#x2013; 14. This solution will allow RIC attendees to access the conference agenda and download conference publications from their own mobile devices. The solution will also enhance the attendees&#x2019; information access experience by incorporating the use of quick response (QR) codes throughout the conference facility (for details, see p. 2 of the NRC&#x2019;s Customer Service Plan, http://www.nrc.gov/public-involve/open/customer-service/nrc-customer-service-plan.pdf).</value>
            <value>Web-based access to NRC email, calendaring, and contacts on personally owned mobile devices.</value>
          </value>
        </field>
        <field>
          <type>select</type>
          <name>7-1-2-scope</name>
          <label>System Scope</label>
          <options>
            <option>
              <label>Internal</label>
              <value>internal</value>
            </option>
            <option>
              <label>External</label>
              <value>external</value>
            </option>
            <option>
              <label>Both</label>
              <value>both</value>
            </option>
          </options>
          <value>
            <value>external</value>
            <value>both</value>
            <value>both</value>
            <value>internal</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>7-1-2-customer</name>
          <label>Main Customer</label>
          <options/>
          <value>
            <value>General public and agency stakeholders</value>
            <value>General public and agency stakeholders</value>
            <value>General public and agency stakeholders</value>
            <value>NRC staff</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>7-1-2-uii</name>
          <label>Unique Investment Identifier</label>
          <options/>
          <value>
            <value>N/A</value>
            <value>429-000002070</value>
            <value>N/A</value>
            <value>1012A-J1500 (ITISS)</value>
          </value>
        </field>
      </fields>
      <multiple>1</multiple>
    </item>
    <item id="4.2">
      <parent/>
      <text>Establish an agency-wide governance structure for developing and delivering digital services</text>
      <due>6 months</due>
      <due_date>2012/11/23</due_date>
      <fields>
        <field>
          <type>select</type>
          <name>4-2-status</name>
          <label>Overall Status</label>
          <options>
            <option>
              <label>Not Started</label>
              <value>not-started</value>
            </option>
            <option>
              <label>In Progress</label>
              <value>in-progress</value>
            </option>
            <option>
              <label>Completed</label>
              <value>completed</value>
            </option>
          </options>
          <value>completed</value>
        </field>
        <field>
          <type>textarea</type>
          <name>4-2-policy</name>
          <label>Paragraph on Governance</label>
          <options/>
          <value>The NRC has leveraged our existing Information Technology/Information Management (IT/IM) processes and governance structure to ensure that the Digital Government Strategy (DGS) is addressed when considering new or modernized digital services. We will govern the implementation of this governance for DGS through our IT/IM Portfolio Executive Council (IPEC, http://pbadupws.nrc.gov/docs/ML1229/ML12298A151.pdf) and our IT/IM Board (ITB, http://pbadupws.nrc.gov/docs/ML1209/ML12094A174.pdf). The interdependencies of our IPEC and ITB are illustrated in the Governance strawman of the NRC IT/IM Portfolio Rationalization Program (http://pbadupws.nrc.gov/docs/ML1232/ML12321A336.pdf). The goal of the ITB is to help align the NRC&#x2019;s IT/IM investments and technology standards with the agency&#x2019;s mission, and to ensure that IT investments are consistent with the agency priorities established by the IPEC. Roles and responsibilities are clearly defined and decisionmaking is founded on a core set of common IT measures. The DGS has been added as a responsibility for the Enterprise Architect in the NRC&#x2019;s Project Management Methodology (PMM), and we are incorporating additional DGS-related PMM guidance regarding the responsibilities of the business sponsor and project manager. This additional guidance will be posted to the agency&#x2019;s internal website by December 31, 2012.</value>
        </field>
        <field>
          <type>text</type>
          <name>4-2-link</name>
          <label>URL to Governance Document</label>
          <options/>
          <value>http://pbadupws.nrc.gov/docs/ML1232/ML12321A336.pdfhttp://pbadupws.nrc.gov/docs/ML1229/ML12298A151.pdfhttp://pbadupws.nrc.gov/docs/ML1209/ML12094A174.pdf</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="5.2">
      <parent/>
      <text>Develop an enterprise-wide inventory of mobile devices and wireless service contracts</text>
      <due>6 months</due>
      <due_date>2012/11/23</due_date>
      <fields>
        <field>
          <type>select</type>
          <name>5-2-status</name>
          <label>Overall Status</label>
          <options>
            <option>
              <label>Not Started</label>
              <value>not-started</value>
            </option>
            <option>
              <label>In Progress</label>
              <value>in-progress</value>
            </option>
            <option>
              <label>Completed</label>
              <value>completed</value>
            </option>
          </options>
          <value>completed</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="5.2.1">
      <parent>5.2</parent>
      <text>Develop wireless and mobile inventory</text>
      <due>6 months</due>
      <due_date>2012/11/23</due_date>
      <fields>
        <field>
          <type>text</type>
          <name>5-2-1-component</name>
          <label>Bureau/Component</label>
          <options/>
          <value>
            <value>Nuclear Regulatory Commission</value>
          </value>
        </field>
        <field>
          <type>select</type>
          <name>5-2-1-inventory-status</name>
          <label>Inventory Status</label>
          <options>
            <option>
              <label>Not Started</label>
              <value>not-started</value>
            </option>
            <option>
              <label>In Progress</label>
              <value>in-progress</value>
            </option>
            <option>
              <label>Completed</label>
              <value>completed</value>
            </option>
          </options>
          <value>
            <value>completed</value>
          </value>
        </field>
      </fields>
      <multiple>1</multiple>
    </item>
    <item id="8.2">
      <parent/>
      <text>Implement performance and customer satisfaction measuring tools on all .gov websites</text>
      <due>8 months</due>
      <due_date>2013/1/22</due_date>
      <fields>
        <field>
          <type>select</type>
          <name>8-2-status</name>
          <label>Overall Status</label>
          <options>
            <option>
              <label>Not Started</label>
              <value>not-started</value>
            </option>
            <option>
              <label>In Progress</label>
              <value>in-progress</value>
            </option>
            <option>
              <label>Completed</label>
              <value>completed</value>
            </option>
          </options>
          <value>completed</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="8.2.1">
      <parent>8.2</parent>
      <text>Implement performance measurement tool</text>
      <due>8 months</due>
      <due_date>2013/1/22</due_date>
      <fields>
        <field>
          <type>select</type>
          <name>8-2-1-tool</name>
          <label>Implemented Digital Analytics Program</label>
          <options>
            <option>
              <label>Yes</label>
              <value>yes</value>
            </option>
            <option>
              <label>No</label>
              <value>no</value>
            </option>
          </options>
          <value/>
        </field>
        <field>
          <type>textarea</type>
          <name>8-2-1-implementation</name>
          <label>If Not, Describe Implementation</label>
          <options/>
          <value>The NRC has implemented the GSA-sponsored hosted tool to gather web performance metrics (http://www.howto.gov/web-content/digital-metrics#web-performance-metrics) for our public site.</value>
        </field>
        <field>
          <type>text</type>
          <name>8-2-1-percent</name>
          <label>Percent of websites covered</label>
          <options/>
          <value>100</value>
        </field>
        <field>
          <type>text</type>
          <name>8-2-1-url</name>
          <label>URL of performance data</label>
          <options/>
          <value/>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="8.2.2">
      <parent>8.2</parent>
      <text>Implement customer satisfaction tool</text>
      <due>8 months</due>
      <due_date>2013/1/22</due_date>
      <fields>
        <field>
          <type>textarea</type>
          <name>8-2-2-implementation</name>
          <label>Describe Implementation</label>
          <options/>
          <value>The NRC solicits and carefully considers customer feedback through optional online surveys of visitors to our public website. These surveys are administered by ForeSee Results using the American Customer Satisfaction Index (ACSI) methodology, consistent with the guidance developed by GSA&#x2019;s Office of Citizen Services </value>
        </field>
        <field>
          <type>text</type>
          <name>8-2-2-url</name>
          <label>URL of performance data</label>
          <options/>
          <value>http://www.nrc.gov/public-involve/open/evaluating-progress/site-satisfaction-survey-results.xls</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="1.2">
      <parent/>
      <text>Ensure all new IT systems follow the open data, content, and web API policy and operationalize agency.gov/developer pages</text>
      <due>12 months</due>
      <due_date>2013/05/23</due_date>
      <fields>
        <field>
          <type>select</type>
          <name>1-2-status</name>
          <label>Overall Status</label>
          <options>
            <option>
              <label>Not Started</label>
              <value>not-started</value>
            </option>
            <option>
              <label>In Progress</label>
              <value>in-progress</value>
            </option>
            <option>
              <label>Completed</label>
              <value>completed</value>
            </option>
          </options>
          <value>completed</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="1.2.1">
      <parent>1.2</parent>
      <text>Document policy for architecting new IT systems for openness by default</text>
      <due>6 months</due>
      <due_date>2012/11/23</due_date>
      <fields>
        <field>
          <type>textarea</type>
          <name>1-2-1-description</name>
          <label>Describe policy</label>
          <options/>
          <value>The NRC Information Technology/Information Management Strategic Plan covers all of the NRC&#x2019;s IT/IM resources agency-wide, including our networks, computers, and telecommunications devices, our information and records management, our cyber security operations, and all of our applications, ranging from mission-essential systems, such as those supporting licensing and emergency response, to systems required for support functions such as payroll, personnel, and accounting.  The most important goal of the NRC&#x2019;s IT/IM program is effective information access-enabling both the NRC staff and the public to quickly and easily obtain the information they need.&#xD;
&#xD;
On December 4, 2012, we responded to a request for comments on the draft Open Data policy. We are currently awaiting issuance of government-wide open data, content, and web API policy [Milestone 1.1]. Implementation instructions for 12-month agency deliverables have been deferred to January 2013.</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="1.2.3">
      <parent>1.2</parent>
      <text>Operationalize Enterprise Data Inventory</text>
      <due>17 months</due>
      <due_date>2013/10/23</due_date>
      <fields>
        <field>
          <type>text</type>
          <name>1-2-3-datasets-in-inventory</name>
          <label>Number of datasets in the Enterprise Data Inventory</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>text</type>
          <name>1-2-3-systems-in-inventory</name>
          <label>Number of systems whose datasets are in the Enterpirse Data Inventory</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>text</type>
          <name>1-2-3-datasets-potential-public</name>
          <label>Number of datasets that can be made publicly available</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>text</type>
          <name>1-2-3-datsets-listed</name>
          <label>Number of datasets listed on the /data page</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>text</type>
          <name>1-2-3-released-datasets-listed</name>
          <label>Number of released datasets listed on the /data page</label>
          <options/>
          <value/>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="2.2">
      <parent/>
      <text>Make high-value data and content in at least two existing, major customer-facing systems available through web APIs, apply metadata tagging and publish a plan to transition additional high-value systems</text>
      <due>12 months</due>
      <due_date>2013/05/23</due_date>
      <fields>
        <field>
          <type>select</type>
          <name>2-2-status</name>
          <label>Overall Status</label>
          <options>
            <option>
              <label>Not Started</label>
              <value>not-started</value>
            </option>
            <option>
              <label>In Progress</label>
              <value>in-progress</value>
            </option>
            <option>
              <label>Completed</label>
              <value>completed</value>
            </option>
          </options>
          <value>completed</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="2.2.1">
      <parent>2.1</parent>
      <text>Publish plan on future activity</text>
      <due>12 months</due>
      <due_date>2013/05/23</due_date>
      <fields>
        <field>
          <type>textarea</type>
          <name>2-2-1-describe</name>
          <label>Describe policy</label>
          <options/>
          <value/>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="2.2.2">
      <parent>2.1</parent>
      <text>Make 2+ systems (datasets) available via web APIs with metadata tags</text>
      <due>12 months</due>
      <due_date>2013/05/23</due_date>
      <fields>
        <field>
          <type>text</type>
          <name>2-2-2-system</name>
          <label>Name of system</label>
          <options/>
          <value>
            <value>Not yet available</value>
          </value>
        </field>
        <field>
          <type>textarea</type>
          <name>2-2-2-description</name>
          <label>Description of system</label>
          <options/>
          <value>
            <value>The NRC uses web analytics to determine the most requested official agency information to further enhance the delivery of that information via mobile solution and web API's.  Additional inputs to identify, scope, and prioritize other opportunities are obtained by reaching out to stakeholders across functional, programmatic, and geographic areas.  The opportunities are prioritized using the following factors: strategic alignment, opportunity scope, efficiencies generated, solution complexity, development time, enterprise applicability, and implementation costs.  The top mobile opportunities will be implemented by the agency. &#xD;
&#xD;
The NRC has leveraged our existing IT/IM processes and governance structure to ensure that the Digital Government Strategy (DGS) is addressed when considering new or modernized digital services. The DGS has been added as a requirement in the NRC&#x2019;s Project Management Methodology (PMM) to ensure the solution architecture complies with the OMB policies.&#xD;
&#xD;
Future Plans will be noted in the agency&#x2019;s Enterprise Roadmap.&#xD;
&#xD;
OMB reviewed and endorsed the NRC&#x2019;s prioritized list of systems and proposed customer engagement approach [Milestone 2.1]. (For details, see Taking the Next Step, http://www.nrc.gov/public-involve/open/digital-government/roadmap.html#next-step. Customer feedback and related NRC responses are available in comments on the related Blog posting, http://public-blog.nrc-gateway.gov/2012/08/22/taking-the-next-step-building-a-21st-century-digital-government/#comments.) On October 22, 2012, the NRC confirmed that these systems (data feeds) are targeted to be made available via web APIs by May 23, 2013. In addition, on October 31, we published an article, entitled &#x201C;Digital Government and Technology Enhancements,&#x201D; in the NRC Reporter (our staff newsletter) to provide staff with an update on the status of the NRC&#x2019;s Digital Government program and an overview of the work being done to leverage our current infrastructure. The article also invited staff to share their thoughts on systems (data feeds) that should be given priority to be made available via web APIs. Staff ideas will aid in development of our plan for future activity. On December 4, 2012, we responded to a request for comments on the draft Open Data policy. Implementation instructions for 12-month agency deliverables have been deferred to January 2013.  On February 11, 2013, we released an API for Web-Based ADAMS (WBA), which is ahead of the May 23, 2013 deliverable date.  </value>
          </value>
        </field>
        <field>
          <type>select</type>
          <name>2-2-2-scope</name>
          <label>Scope of system</label>
          <options>
            <option>
              <label>Internal</label>
              <value>internal</value>
            </option>
            <option>
              <label>External</label>
              <value>external</value>
            </option>
            <option>
              <label>Both</label>
              <value>both</value>
            </option>
          </options>
          <value/>
        </field>
        <field>
          <type>text</type>
          <name>2-2-2-customers</name>
          <label>Main Customers</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>text</type>
          <name>2-2-2-uii</name>
          <label>Unique Investment Identifier</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>text</type>
          <name>2-2-2-url</name>
          <label>API Link</label>
          <options/>
          <value/>
        </field>
      </fields>
      <multiple>1</multiple>
    </item>
    <item id="5.3">
      <parent/>
      <text>Evaluate the government-wide contract vehicles in the alternatives analysis for all new mobile-related procurements</text>
      <due>12 months</due>
      <due_date>2013/05/23</due_date>
      <fields>
        <field>
          <type>select</type>
          <name>5-3-status</name>
          <label>Overall Status</label>
          <options>
            <option>
              <label>Not Started</label>
              <value>not-started</value>
            </option>
            <option>
              <label>In Progress</label>
              <value>in-progress</value>
            </option>
            <option>
              <label>Completed</label>
              <value>completed</value>
            </option>
          </options>
          <value>completed</value>
        </field>
        <field>
          <type>textarea</type>
          <name>5-3-policy</name>
          <label>Describe Implementation</label>
          <options/>
          <value>The environmental assessment that preceded the development of this Strategic Plan highlighted the progress the agency has made in such areas as mobile computing, Web-based applications, and IT security, but it also emphasized the challenges we face over the next five years with tighter budgets, rapidly changing security threats, and an ever-increasing reliance on technology to accomplish our mission. The assessment also identified some key opportunities, such as system modernization, further improvements in mobile computing, and more effective use of social media and advanced Web technologies that can help us achieve our goals.&#xD;
&#xD;
The following Strategy Measures were identified in the Strategic Plan:&#xD;
&#xD;
&#x2022;	Increase in the number of user-identified high-priority functions made available for access on mobile devices &#xD;
&#x2022;	Develop and implement an agency-wide mobile computing strategy, including devices (Government-supplied and personal), infrastructure, applications, and security. &#xD;
&#x2022;	Expand mobile and remote access to agency applications. &#xD;
&#x2022;	Implement a communications plan to encourage application sponsors to make their applications useful on portable devices using enterprise contracts and standards. &#xD;
&#x2022;	Enhance mobile device capabilities and support to the staff. &#xD;
&#xD;
Note: NRC has centralized all mobile devices on a six year contract. Every year of the contract, NRC will receive a built in cost reduction.&#xD;
&#xD;
Tasking underway. Implementation instructions for 12-month agency deliverables have been deferred to January 2013.</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="6.3">
      <parent/>
      <text>Ensure all new digital services follow digital services and customer experience improvement guidelines</text>
      <due>12 months</due>
      <due_date>2013/05/23</due_date>
      <fields>
        <field>
          <type>select</type>
          <name>6-3-status</name>
          <label>Overall Status</label>
          <options>
            <option>
              <label>Not Started</label>
              <value>not-started</value>
            </option>
            <option>
              <label>In Progress</label>
              <value>in-progress</value>
            </option>
            <option>
              <label>Completed</label>
              <value>completed</value>
            </option>
          </options>
          <value>completed</value>
        </field>
        <field>
          <type>textarea</type>
          <name>6-3-policy</name>
          <label>Describe Implementation</label>
          <options/>
          <value>Effective IT Business solutions says that the NRC&#x2019;s IT Business solutions are easy to use, are cost  effective, and strengthen agency performance.  Several strategies were identified including Strengthen enterprise planning and standards, strengthen planning for NRC business area processes and their supporting IT and strengthen project selection, execution and control.&#xD;
&#xD;
The following Strategy Measures were identified:&#xD;
&#xD;
&#x2022;	Increase in the number of user-identified high-priority functions made available for access on mobile devices &#xD;
&#x2022;	Develop and implement an agencywide mobile computing strategy, including devices (Government-supplied and personal), infrastructure, applications, and security. &#xD;
&#x2022;	Expand mobile and remote access to agency applications. &#xD;
&#x2022;	Implement a communications plan to encourage application sponsors to make their applications useful on portable devices using enterprise contracts and standards. &#xD;
&#x2022;	Enhance mobile device capabilities and support to the staff. &#xD;
&#xD;
Pending release of improvement guidance from GSA [Miestone 6.2]. Implementation instructions for 12-month agency deliverables have been deferred to January 2013.</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="7.2">
      <parent/>
      <text>Optimize at least two existing priority customer-facing services for mobile use and publish a plan for improving additional existing services</text>
      <due>12 months</due>
      <due_date>2013/05/23</due_date>
      <fields>
        <field>
          <type>select</type>
          <name>7-2-status</name>
          <label>Overall Status</label>
          <options>
            <option>
              <label>Not Started</label>
              <value>not-started</value>
            </option>
            <option>
              <label>In Progress</label>
              <value>in-progress</value>
            </option>
            <option>
              <label>Completed</label>
              <value>completed</value>
            </option>
          </options>
          <value>completed</value>
        </field>
        <field>
          <type>textarea</type>
          <name>7-2-policy</name>
          <label>Describe Implementation</label>
          <options/>
          <value>The NRC uses web analytics to determine the most requested official agency information to further enhance the delivery of that information via mobile solution and web API's.  Additional inputs to identify, scope, and prioritize other opportunities are obtained by reaching out to stakeholders across functional, programmatic, and geographic areas.  The opportunities are prioritized using the following factors: strategic alignment, opportunity scope, efficiencies generated, solution complexity, development time, enterprise applicability, and implementation costs.  The top mobile opportunities will be implemented by the agency. &#xD;
&#xD;
The NRC has leveraged our existing IT/IM processes and governance structure to ensure that the DGS is addressed when considering new or modernized digital services. The DGS has been added as a requirement in the NRC&#x2019;s PMM to ensure the solution architecture complies with the OMB policies.&#xD;
&#xD;
Future Plans will be noted in the agency&#x2019;s Enterprise Roadmap.&#xD;
&#xD;
OMB reviewed and endorsed the NRC's prioritized list of services and proposed customer engagement approach [Milestone 7.1]. (For details, see Taking the Next Step, http://www.nrc.gov/public-involve/open/digital-government/roadmap.html#next-step. Customer feedback and related NRC responses are available in comments, http://public-blog.nrc-gateway.gov/2012/08/22/taking-the-next-step-building-a-21st-century-digital-government/#comments, on the related Blog posting, http://public-blog.nrc-gateway.gov/2012/08/22/taking-the-next-step-building-a-21st-century-digital-government/.) On October 22, 2012, the NRC confirmed that these customer-facing services are targeted to be optimized for mobile use by May 23, 2013. The NRC will also publish a plan for improving additional existing services by the scheduled date. Then, on January 23, 2013, we added mobile services in support of the 2013 Regulatory Information Conference (RIC), http://www.nrc.gov/public-involve/conference-symposia/ric/, to the list of mobile services previously identified to be available by May 23, 2013. We also augmented the list to include services to support web-based staff access to email, calendaring, and contacts using personally owned mobile devices. This replaced the existing item to provide a mobile optimization for the top 5 most-accessed agency web pages.&#xD;
&#xD;
Also, on October 31, we published an article, entitled &#x201C;Digital Government and Technology Enhancements,&#x201D; in the NRC Reporter (our staff newsletter) to provide staff with an update on the status of the NRC&#x2019;s Digital Government program and an overview of the work being done to leverage our current infrastructure. The article also invited staff to share their thoughts on services that should be given priority to be optimized for mobile use. Staff ideas will aid in development of our report on services.&#xD;
&#xD;
In addition, on December 4, 2012, we responded to a request for comments on the draft Open Data policy. Implementation instructions for 12-month agency deliverables have been deferred to January 2013.</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="7.2.1">
      <parent>7.2.</parent>
      <text>Report on services</text>
      <due>12 months</due>
      <due_date>2013/05/23</due_date>
      <fields>
        <field>
          <type>text</type>
          <name>7-2-1-name</name>
          <label>Service Name</label>
          <options/>
          <value>
            <value>Not yet available</value>
          </value>
        </field>
        <field>
          <type>textarea</type>
          <name>7-2-1-description</name>
          <label>Service Description</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>select</type>
          <name>7-2-1-scope</name>
          <label>System Scope</label>
          <options>
            <option>
              <label>Internal</label>
              <value>internal</value>
            </option>
            <option>
              <label>External</label>
              <value>external</value>
            </option>
            <option>
              <label>Both</label>
              <value>both</value>
            </option>
          </options>
          <value/>
        </field>
        <field>
          <type>text</type>
          <name>7-2-1-customers</name>
          <label>Primary customers</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>text</type>
          <name>7-2-1-uii</name>
          <label>Unique Investment Identifier</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>text</type>
          <name>7-2-1-url</name>
          <label>URL of service</label>
          <options/>
          <value/>
        </field>
      </fields>
      <multiple>1</multiple>
    </item>
  </items>
</report>
