<?xml version="1.0"?>
<report>
  <agency>FERC</agency>
  <generated>2013-05-13 13:58:25</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>The FERC distributed a survey, through their digital government website, that asked the public to choose the systems they would like open through Web API. Using the survey results, the Digital Government Task Force then prioritized the systems, taking into consideration current and future IT project schedules. The task force made the decision to open the &#x201C;Decisions and Notices&#x201D; and eTariff data through Web API by the May23rd. The other systems will be made available based on IT project schedules. The progress of this initiative will be provided through FERC&#x2019;s digital government website http://www.ferc.gov/open.asp.</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>Decisions and Notices</value>
            <value>eTariff</value>
            <value>eLibrary</value>
            <value>eService</value>
            <value>Electric Quarterly Reports (EQR)</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>2-1-2-description</name>
          <label>System Description</label>
          <options/>
          <value>
            <value>Provides a monthly collection of Delegated Orders, Notices, and Commission Decisions from Commission Meetings or Notational Voting arranged by date.</value>
            <value>Allows for tariffs, tariff revisions and rate change applications to be filed electronically in the manner prescribed by Order No. 714. The affected regulated entities are:  &#x2022;	Public utilities and Power Marketing Administrations under Parts 35 and 300;  &#x2022;	Natural gas pipelines under Parts 154 and 284;  &#x2022;	Intrastate gas pipelines under Part 284; and  &#x2022;	Oil pipelines under Part 341.  </value>
            <value>eLibrary is a records information system that contains:  1.	Electronic versions of documents issued by FERC from 1989-Present;  2.	Documents received and issued by FERC: a.	A description of documents from 1981-Present;  b.	Microfilm and aperture cards of documents for 1981-1995;  c.	Scanned images of paper documents from 1995-Present; and  d.	Native files electronically submitted from November 2000-Present </value>
            <value>Provides users with official mailing list or service list for a docketed proceeding.</value>
            <value>Allows users to access data submitted by utilities and power marketers. Access is achieved through the following means: 1. Download Spreadsheets - Contract and transaction data by company by quarter in a structure similar to the one used for data import.  2. Summary Reports - Short summaries of each company's EQR filings (beginning Q1 2005) identifying the products they sell, the customers they sell to and the control areas where deliveries are made.  3. Filing Inquiries - EQR data can be retrieved using standard queries which can be customized by the user.  4. Selective Filings Download - Retrieves data on multiple companies and quarters with one request. Processed overnight and sent via email the next day.   5. Download Database - Provides for the download of the full EQR database. It should be used only by advanced users with several gigabytes of disk space. </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>external</value>
            <value>external</value>
            <value>both</value>
            <value>external</value>
            <value>external</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>2-1-2-customer</name>
          <label>Main Customer</label>
          <options/>
          <value>
            <value>Public</value>
            <value>Public</value>
            <value>Public and Commission staff</value>
            <value>Public</value>
            <value>Public</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>2-1-2-uii</name>
          <label>Unique Investment Identifier</label>
          <options/>
          <value>
            <value>505-00-01-02-01-1011-00</value>
            <value>505-00-01-02-01-1011-00</value>
            <value>505-00-01-02-01-1011-00</value>
            <value>505-00-01-02-01-1011-00</value>
            <value>505-00-01-02-01-1011-00</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>The FERC distributed a survey, through their digital government website, that asked the public to select which services they prefer be made available through mobile technology. Using the survey results, the Digital Government Task Force then prioritized the services, taking into consideration current and future IT project schedules. The task force made the decision to open the &#x201C;Decisions and Notices&#x201D; and &#x201C;What&#x2019;s New&#x201D; services using mobile technology by the May23rd. The other services will be made available based on IT project schedules. The progress of this initiative will be provided through FERC&#x2019;s digital government website http://www.ferc.gov/open.asp.</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>Decisions and Notices</value>
            <value>What&#x2019;s New</value>
            <value>eSubscription</value>
            <value>eFiling</value>
            <value>eRegistration</value>
            <value>Electric Quarterly Reports (EQR)</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>7-1-2-description</name>
          <label>System Description</label>
          <options/>
          <value>
            <value>Provides a monthly collection of Delegated Orders, Notices, and Commission Decisions from Commission Meetings or Notational Voting arranged by date.</value>
            <value>The &#x201C;What&#x2019;s New&#x201D; RSS feed provides news and information details about the events at FERC.</value>
            <value>Users subscribe or &#x2018;sign up&#x2019; for specific dockets and are notified via email about future correspondence. Users have immediate access to the correspondence or documents in eLibrary.</value>
            <value>Allows users to electronically submit qualified documents to FERC in lieu of paper filings.</value>
            <value>eRegistration provides the FERC customer an easy-to-use entry point to do business with all FERC Online applications. Think of eRegistration as a form of membership. By registering, the user will receive a single user id and password that allows them to transact all of their business with FERC.   eRegistration is valuable to any person who transacts business with the FERC on behalf of themselves or another organization (e.g. companies or corporations). It provides authentication support to the FERC Online applications that ensures safe and secure transactions, thereby protecting the integrity of your data. </value>
            <value>Allows all public utilities and power marketers to file EQRs for the most recent calendar quarter. The filings must summarize contractual terms and conditions for:  Market-based power sales,  Cost-based power sales, and  Transmission service.  </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>external</value>
            <value>external</value>
            <value>external</value>
            <value>both</value>
            <value>external</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>7-1-2-customer</name>
          <label>Main Customer</label>
          <options/>
          <value>
            <value>Public</value>
            <value>Public</value>
            <value>Public</value>
            <value>Public and Commission Staff</value>
            <value>Public and Commission Staff</value>
            <value>Public</value>
          </value>
        </field>
        <field>
          <type>text</type>
          <name>7-1-2-uii</name>
          <label>Unique Investment Identifier</label>
          <options/>
          <value>
            <value>505-00-01-02-01-1011-00</value>
            <value>505-00-01-02-01-1011-00</value>
            <value>505-00-01-02-01-1011-00</value>
            <value>505-00-01-02-01-1011-00</value>
            <value>505-00-01-02-01-1011-00</value>
            <value>505-00-01-02-01-1011-00</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 Commission has chosen to incorporate its digital services governance into its current Information Technology Capital Planning and Investment Control (CPIC) Process. This allows for a consolidated point of entry and ensures a consistent review process for all IT and digital service requests. The review process includes, but is not limited to, taking into consideration the potential data collection of the request, the possible benefit to the public, how the data can be provided to the public and, any security and privacy concerns for the data. </value>
        </field>
        <field>
          <type>text</type>
          <name>4-2-link</name>
          <label>URL to Governance Document</label>
          <options/>
          <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>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>yes</value>
        </field>
        <field>
          <type>textarea</type>
          <name>8-2-1-implementation</name>
          <label>If Not, Describe Implementation</label>
          <options/>
          <value>The Google Analytics tool will be implemented by 1/26/13. We are currently using another tool until the Google Analytics tool implementation is complete.</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>Survey is posted on the following sites&#xD;
1) http://www.ferc.gov/docs-filing/forms.asp &#xD;
2) http://www.ferc.gov/enforcement/enforcement.asp&#xD;
3) http://www.ferc.gov/industries/electric/indus-act/reliability.asp </value>
        </field>
        <field>
          <type>text</type>
          <name>8-2-2-url</name>
          <label>URL of performance data</label>
          <options/>
          <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>textarea</type>
          <name>1-2-1-description</name>
          <label>Describe policy</label>
          <options/>
          <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>not-started</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>Taking into consideration current resource constraints, and the Commission's current and future IT project timelines, FERC plans to release its first APIs in FY15.</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/>
        </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-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>not-started</value>
        </field>
        <field>
          <type>textarea</type>
          <name>5-3-policy</name>
          <label>Describe Implementation</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>not-started</value>
        </field>
        <field>
          <type>textarea</type>
          <name>6-3-policy</name>
          <label>Describe Implementation</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>not-started</value>
        </field>
        <field>
          <type>textarea</type>
          <name>7-2-policy</name>
          <label>Describe Implementation</label>
          <options/>
          <value>Taking into consideration current resource constraints, and the Commission's current and future IT project timelines, FERC plans to release its first Mobile Applications in FY15</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-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>
