<?xml version="1.0"?>
<report>
  <agency>EPA</agency>
  <generated>2013-01-22 07:25:29</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>in-progress</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>EPA is encouraging engagement with external parties regarding its data holdings through several forums. The Data and Developer Forum encourages the public and developers to tell EPA what data assets they want. In addition, the Developer Central encourages feedback from developers about how they can use EPA&#x2019;s APIs to make apps. During the Apps for the Environment Challenge, the public submitted over 100 ideas for apps. EPA will encourage people to tell us which apps they want most. For each idea, EPA will identify the associated EPA data assets so developers can more easily convert the ideas into apps. Finally, EPA is using agency blog, It&#x2019;s Our Environment, to encourage feedback about the Digital Government Strategy and EPA&#x2019;s data holdings. We will review this feedback to identify data needs on an ongoing basis.</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>Data and Developer Forum and Developer Central</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>2-1-2-description</name>
          <label>System Description</label>
          <options/>
          <value>
            <value>The Data and Developer Forum encourages the public and developers to tell EPA what data assets they want. Developer Central encourages feedback from developers about how they can use EPA&#x2019;s APIs to make apps. In addition, EPA has encouraged people to provide feedback about data on EPA&#x2019;s blog, It&#x2019;s Our Environment. </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>
        </field>
        <field>
          <type>text</type>
          <name>2-1-2-customer</name>
          <label>Main Customer</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>text</type>
          <name>2-1-2-uii</name>
          <label>Unique Investment Identifier</label>
          <options/>
          <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>in-progress</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/>
        </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/>
        </field>
        <field>
          <type>text</type>
          <name>7-1-2-description</name>
          <label>System Description</label>
          <options/>
          <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/>
        </field>
        <field>
          <type>text</type>
          <name>7-1-2-customer</name>
          <label>Main Customer</label>
          <options/>
          <value/>
        </field>
        <field>
          <type>text</type>
          <name>7-1-2-uii</name>
          <label>Unique Investment Identifier</label>
          <options/>
          <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>The Agency is leveraging existing governance structures and bodies to develop and implement the Strategy &#xD;
requirements. Many of the goals and objectives of the Strategy align and complement the direction EPA &#xD;
established to implement the Open Government Directive (OGD). Where both efforts emphasize cross-agency &#xD;
coordination, the existing governance structure supporting OpenGov will be used. For other aspects of Digital &#xD;
Government where a milestone falls within the responsibilities of an established EPA organization or body, their &#xD;
existing governance structure will guide their efforts.</value>
        </field>
        <field>
          <type>textarea</type>
          <name>4-2-link</name>
          <label>URL to Governance Document</label>
          <options/>
          <value>http://epa.gov/digitalstrategy/usepa-ds-governance.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>in-progress</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>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>in-progress</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>no</value>
        </field>
        <field>
          <type>textarea</type>
          <name>8-2-1-implementation</name>
          <label>If Not, Describe Implementation</label>
          <options/>
          <value>Implemented the Analytics Tool Provided by GSA: Alternative Implementation&#xD;
Describe Implementation: In order to preserve the integrity and effectiveness of EPA&#x2019;s performance metrics, EPA is working with GSA to implement a custom modification to EPA&#x2019;s existing Google Analytics implementation.  This modification will allow GSA to leverage the methodology used at EPA by sending a copy of all EPA performance metrics to a duplicate account maintained by GSA.  EPA will work with GSA to ensure that the proper configurations are maintained in both accounts.&#xD;
The GSA tracking code does not include cross-domain tracking for sub- and alternate-domains, which is necessary in order to collect accurate visit-based metrics for websites that have more than one domain and/or sub-domains, as EPA does.  For example, if a visitor to www.epa.gov clicks on a link to www.water.epa.gov or www.urbanwaters.gov, our custom implementation allows that the session, or Visit, to continue, and visit-based metrics are not adversely affected.  The GSA code considers sub- and alternate-domains to be separate websites, which would skew all visit-based metrics, including Bounce Rate, Visits, Visit Duration, Pages per Visit, etc, for the EPA website.  For example, if someone visited www.epa.gov and immediately clicked on a link to www.water.epa.gov, the GSA code would record a Bounce (a Visit that includes only one Pageview) and a Visit of only a few seconds, when the Visit should actually include all EPA pages, regardless of the domain.</value>
        </field>
        <field>
          <type>text</type>
          <name>8-2-1-percent</name>
          <label>Percent of websites covered</label>
          <options/>
          <value>98</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>EPA has implemented the American Customer Satisfaction Index (ACSI) ForeSee survey tool to measure customer satisfaction on its public websites.   The Agency uses ACSI results to identify which elements have the greatest influence on satisfaction and future customer behavior.  Annual and quarterly reports are published by Foresee as "Satisfaction Indexes."</value>
        </field>
        <field>
          <type>text</type>
          <name>8-2-2-url</name>
          <label>URL of performance data</label>
          <options/>
          <value>http://www.foresee.com/research-white-papers/research-by-industry.shtml#government</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>in-progress</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>in-progress</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>
            <value>http://www.epa.gov/enviro/</value>
            <value>http://www.regulations.gov</value>
          </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>in-progress</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>
            <value>How&#x2019;s My Waterway</value>
            <value>The direct local access by mobile geolocation, simplicity, and plain English tone of the &#x201C;How&#x2019;s My Waterway?&#x201D; application aims to remove complexity barriers and better inform more people on how water issues affect them locally, thereby improving their awareness and support of efforts to protect and restore the nation&#x2019;s waters under the Clean Water Act.</value>
            <value>EPA.gov </value>
            <value>EPA is considering replacing the limited mobile access currently available for home page content with a more fully featured page using responsive design.</value>
            <value>FRS Mobile Facility Data Collection</value>
            <value>EPA will release a prototype application for field inspectors and emergency response personnel, which retrieves facility data and displays it with aerial photography and GIS base mapping, and which allows updates to be captured in the field via GPS and submitted back to EPA via Exchange Network web services.</value>
          </value>
        </field>
        <field>
          <type>textarea</type>
          <name>7-2-1-name</name>
          <label>Service Description</label>
          <options/>
          <value>
            <value>How&#x2019;s My Waterway</value>
            <value>The direct local access by mobile geolocation, simplicity, and plain English tone of the &#x201C;How&#x2019;s My Waterway?&#x201D; application aims to remove complexity barriers and better inform more people on how water issues affect them locally, thereby improving their awareness and support of efforts to protect and restore the nation&#x2019;s waters under the Clean Water Act.</value>
            <value>EPA.gov </value>
            <value>EPA is considering replacing the limited mobile access currently available for home page content with a more fully featured page using responsive design.</value>
            <value>FRS Mobile Facility Data Collection</value>
            <value>EPA will release a prototype application for field inspectors and emergency response personnel, which retrieves facility data and displays it with aerial photography and GIS base mapping, and which allows updates to be captured in the field via GPS and submitted back to EPA via Exchange Network web services.</value>
          </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>
            <value>external</value>
            <value>external</value>
            <value>both</value>
            <value>external</value>
          </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>
            <value>http://watersgeo.epa.gov/mywaterway/</value>
          </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>
