<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01716nab a2200205   4500</leader>
  <controlfield tag="005">20260520000805.0</controlfield>
  <controlfield tag="008">260224s2009    xxu                      </controlfield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">The evolving design of RTO ancillary service markets</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">ene. 2009</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">26/02/2009 ; 26/02/2009</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">7 p. ; 150-157</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del res&#xFA;men publicado por el autor: Although the markets for ancillary services at the North American Independent System Operators are often structured in quite different ways there is an emerging set of core design elements that represent a rough consensus as to what the optimal design configuration for ancillary services should be, albeit with some regional variation. This paper looks back at how the design of ancillary services markets has recently evolved to put this development in context. Thereafter it examines the methods by which ancillary services are procured by highlighting the procurement practices at a number of different Independent System Operators, principally those in California, New York, New England, Texas and the PJM Interconnection, in an attempt to tease out the remaining reasons why the ancillary service markets are still so different. This is important as there are many innovations that are not rooted in regional differences but reflect genuine technical advances and economic efficiency gains and can be replicated across other ISOs to produce more efficient designs, greater reliability and lower costs.</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">1</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">Energy Policy</subfield>
    <subfield code="g">37</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Isemonger, Alan G.</subfield>
    <subfield code="9">40440</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Electricidad</subfield>
    <subfield code="9">5978</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Reservas</subfield>
    <subfield code="9">21839</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">169159</subfield>
    <subfield code="d">169159</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="9">236978</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-05</subfield>
    <subfield code="j">200043951</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200043951</subfield>
    <subfield code="r">2026-03-05 15:11:22</subfield>
    <subfield code="w">2026-03-05</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
