<?xml version="1.0"?>
<report>
  <agency>OPM</agency>
  <generated>2013-02-12 14:53:26</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>We initially identified 5 possible customer facing services with high-value data or content: the OPM Website, Searchable Frequently Asked Questions, FedScope, Federal Government Operating Status, and USAJOBS. Based on feedback we received through engagement with various stakeholders &#x2013; communities of practice, blogs, social media, and workgroups &#x2013; we selected the following two existing major customer-facing systems for milestone 2.1:  (1) USAJOBS and (2) Federal Government Operating Status. We selected these two systems because of public demand for more flexible access to the information they provide. Throughout five open government teams, we have regularly engaged stakeholders from throughout the agency, our union, other agencies, good government groups, and academia on the OPM data that interest them the most. In choosing USAJOBS and the federal government operating status as the first candidates to make compliant with new open data, content, and web API policy, we drew on our many conversations with those stakeholders. We also looked at social media to see what the public is most interested in knowing more about; federal jobs and the operating status consistently draw attention.  To prioritize future systems, we will work with the Big Data Community of Practice we recently established, which has a similar makeup to our open government teams. We will also continue to monitor feedback via social media.</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>USAJOBS</value>
            <value>Federal Government Operating Status</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>2-1-2-description</name>
          <label>System Description</label>
          <options/>
          <value>
            <value>Website to post and find federal jobs. By providing an API for USAJOBS, we will make it easier for third parties to (1) provide customized access to job postings (e.g., only those that would be of interest to members of a particular professional organization) or (2) combine job posting with other services or applications (e.g., discussion boards or other social media around federal jobs).</value>
            <value>Provides information on the operating status of federal agencies. Not only do federal employees need to know the operating status of their offices, but also many businesses and other organizations base their operating status decisions on ours. The API for the operating status will make it easier for those organizations and even other federal agencies to make full use of operating status data. </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>
        </field>
        <field>
          <type>text</type>
          <name>2-1-2-customer</name>
          <label>Main Customer</label>
          <options/>
          <value>
            <value>General public</value>
            <value>General public</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>2-1-2-uii</name>
          <label>Unique Investment Identifier</label>
          <options/>
          <value>
            <value>027-000000053&#x2014;USAJOBS</value>
            <value>027-XXXXXXXXX--New Investment for FY 2014 Budget</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>We first identified 5 possible customer facing services for potential optimization for mobile use: the OPM Website, Searchable Frequently Asked Questions, FedScope, Federal Government Operating Status, and USAJOBS. Based on feedback we received through engagement with various stakeholders &#x2013; communities of practice, blogs, social media and workgroups &#x2013; we selected the following two existing major customer-facing systems for milestone 7.1:  (1) USAJOBS and (2) Federal Government Operating Status. We selected these two systems because (1) there is significant public demand and (2) the full range of functionality for the mobile user community does not exist, since the existing mobile options are toward one operating system. We hear from our stakeholders that USAJOBS is one of the best places to find Federal employment and they would like to be able to access the site through any device, anywhere and anytime. USAJOBS launched an iOS (iPhone &amp; iPad) application several months ago. However, nothing currently exists for users of Android phones or tablets; our goal is to provide equal access to users of both major mobile platforms. As technologies evolve, we may need to add other platforms. for the USAJOBS application to be device agnostic so it is available for all users. More than 5,000 people have downloaded the iOS application, and many have asked for an Android app through the USAJOBS Facebook page. Likewise, our stakeholders often provide feedback regarding how great it would be to have an application &#x2013; again for any device, anywhere &#x2013; to quickly find out about the operating status of the federal government. To prioritize future systems for mobile applications or mobile-friendly delivery via web browsers, we will work with the Big Data Community of Practice we recently established, which has a similar makeup to our open government teams. We will also continue to monitor feedback via social media.</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>USAJOBS</value>
            <value>Federal Operating Status</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>7-1-2-description</name>
          <label>System Description</label>
          <options/>
          <value>
            <value>Website to post and find federal jobs. By keeping our popular iOS mobile app up-to-date and creating an Android version, we will better serve more people seeking federal employment.</value>
            <value>Provides information on the operating status of federal agencies. Not only do federal employees use this information whenever there is bad weather or an unexpected major event such as an earthquake, but local businesses and other organizations often make their own operating status decisions based on the federal government&#x2019;s decision. Although OPM has never created an application for the operating status, one exists for iOS devices and is sold by a private entity for $0.99. We will make this freely available information also more freely accessible with a mobile application for both iOS and Android 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>both</value>
            <value>both</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>7-1-2-customer</name>
          <label>Main Customer</label>
          <options/>
          <value>
            <value>General public</value>
            <value>General public</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>7-1-2-uii</name>
          <label>Unique Investment Identifier</label>
          <options/>
          <value>
            <value>027-000000053&#x2014;USAJOBS</value>
            <value>027-XXXXXXXXX--New Investment for FY 2014 Budget</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>in-progress</value>
        </field>
        <field>
          <type>textarea</type>
          <name>4-2-policy</name>
          <label>Paragraph on Governance</label>
          <options/>
          <value>Approach to Governance of Digital Services: OPM has long had three boards that govern the acquisition and use of information technology (IT) assets, but these boards have not been integrated. Rather than create another, separate board, we are creating a Data Governance Board (DGB) to which the other three will report. All of the members of the DGB already sit on one or more of the existing three boards; the DGB&#x2019;s main function is to ensure enterprise-wide coordination, cooperation, and collaboration on all aspects of digital assets.</value>
        </field>
        <field>
          <type>textarea</type>
          <name>4-2-link</name>
          <label>URL to Governance Document</label>
          <options/>
          <value>http://www.opm.gov/digitalstrategy/governance/ </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/>
        </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/>
        </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>6 months</due>
      <due_date>2012/11/23</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>in-progress</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="8.2.1">
      <parent>8.2</parent>
      <text>Implement performance measurement tool</text>
      <due>6 months</due>
      <due_date>2012/11/23</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>yes</value>
        </field>
        <field>
          <type>textarea</type>
          <name>8-2-1-implementation</name>
          <label>If Not, Describe Implementation</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>text</type>
          <name>8-2-1-percent</name>
          <label>Percent of websites covered</label>
          <options/>
          <value>13</value>
        </field>
        <field>
          <type>text</type>
          <name>8-2-1-url</name>
          <label>URL of performance data</label>
          <options/>
          <value>To be determined; working with GSA.</value>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="8.2.2">
      <parent>8.2</parent>
      <text>Implement customer satisfaction tool</text>
      <due>6 months</due>
      <due_date>2012/11/23</due_date>
      <fields>
        <field>
          <type>textarea</type>
          <name>8-2-2-implementation</name>
          <label>Describe Implementation</label>
          <options/>
          <value>We are researching this.</value>
        </field>
        <field>
          <type>text</type>
          <name>8-2-2-url</name>
          <label>URL of performance data</label>
          <options/>
          <value>To be determined.</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/>
        </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>text</type>
          <name>1-2-1-url</name>
          <label>URL of policy</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>textarea</type>
          <name>1-2-1-description</name>
          <label>Describe policy</label>
          <options/>
          <value/>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="1.2.2">
      <parent>1.2</parent>
      <text>Operationalize /developer page</text>
      <due>12 months</due>
      <due_date>2013/05/23</due_date>
      <fields>
        <field>
          <type>text</type>
          <name>1-2-2-url</name>
          <label>URL of 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/>
        </field>
      </fields>
      <multiple/>
    </item>
    <item id="2.2.1">
      <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-1-url</name>
          <label>URL of page</label>
          <options/>
          <value/>
        </field>
      </fields>
      <multiple>1</multiple>
    </item>
    <item id="2.2.2">
      <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>text</type>
          <name>2-2-2-system</name>
          <label>Name of system</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>textarea</type>
          <name>2-2-2-description</name>
          <label>Description of system</label>
          <options/>
          <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-url</name>
          <label>Endpoint URL</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>textarea</type>
          <name>2-2-2-compliance</name>
          <label>Summary of policy compliance</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/>
        </field>
        <field>
          <type>textarea</type>
          <name>5-3-policy</name>
          <label>Paragraph on policy</label>
          <options/>
          <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/>
        </field>
        <field>
          <type>textarea</type>
          <name>6-3-policy</name>
          <label>Paragraph on policy</label>
          <options/>
          <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/>
        </field>
        <field>
          <type>textarea</type>
          <name>7-2-url</name>
          <label>URL of plan</label>
          <options/>
          <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/>
        </field>
        <field>
          <type>textarea</type>
          <name>7-2-1-name</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-url</name>
          <label>URL of service</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>textarea</type>
          <name>7-2-1-optimizations</name>
          <label>Summary of optimizations</label>
          <options/>
          <value/>
        </field>
      </fields>
      <multiple>1</multiple>
    </item>
  </items>
</report>
