Download:
pdf |
pdfNORTH AMERICAN ENERGY STANDARDS BOARD
801 Travis, Suite 1675 • Houston, Texas 77002 • Phone: (713) 356-0060 • Fax: (713) 356-0067
email: [email protected] • Web Site Address: www.naesb.org
December 20, 2012
Filed Electronically
The Honorable Kimberly D. Bose
Secretary
Federal Energy Regulatory Commission
888 First Street N.E., Room 1A
Washington, D.C. 20585
RE:
Standards for Business Practices and Communication Protocols for Public Utilities (Docket Nos. RM05-5000, RM05-5-022)
Dear Ms. Bose:
The North American Energy Standards Board (NAESB) herewith submits this report to the Federal Energy
Regulatory Commission (“FERC” or “Commission”) regarding errata to Version 003 of the NAESB Wholesale
Electric Quadrant (“WEQ”) business practice standards provided to the Commission on September 18, 2012
(Docket No. RM05-5-022). 1 The minor corrections included in this report were adopted by the WEQ Executive
Committee on October 23, 2012. This report is submitted voluntarily.
The report is being filed electronically in Adobe Acrobat® Portable Document Format (.pdf). All of the documents
are also available on the NAESB web site (www.naesb.org). Should you have need of the filing in editable format,
we can provide it in Microsoft® Word® 2003. Please feel free to call me at (713) 356-0060 or refer to the NAESB
website (www.naesb.org) should you have any questions or need additional information regarding the errata to
Version 003 of the NAESB WEQ business practice standards.
Respectfully submitted,
Jonathan Booe
Mr. Jonathan Booe
Vice President, North American Energy Standards Board
1
The standards referenced and provided in this report are protected by federal copyright law. Reproduction of the standards in any form is
strictly prohibited without first obtaining the express permission of NAESB. ©2012 NAESB, all rights reserved.
NORTH AMERICAN ENERGY STANDARDS BOARD
801 Travis, Suite 1675 • Houston, Texas 77002 • Phone: (713) 356-0060 • Fax: (713) 356-0067
email: [email protected] • Web Site Address: www.naesb.org
December 20, 2012
cc:
Chairman Jon Wellinghoff, Federal Energy Regulatory Commission
Commissioner Tony Clark, Federal Energy Regulatory Commission
Commissioner Cheryl LaFleur, Federal Energy Regulatory Commission
Commissioner Philip D. Moeller, Federal Energy Regulatory Commission
Commissioner John R. Norris, Federal Energy Regulatory Commission
Mr. Michael Bardee, Director, Office of Electric Reliability, Federal Energy Regulatory
Commission
Mr. David Morenoff, Acting General Counsel, Federal Energy Regulatory Commission
Mr. Mason Emnett, Associate Director, Office of Energy Policy and Innovation, Federal
Energy Regulatory Commission
Mr. Michael Goldenberg, Senior Attorney, Office of General Counsel, Federal Energy
Regulatory Commission
Ms. Jamie L. Simler, Director, Office of Energy Policy and Innovation, Federal Energy
Regulatory Commission
Mr. Michael D. Desselle, Chairman and CEO, North American Energy Standards Board
Ms. Rae McQuade, President, North American Energy Standards Board
Mr. William P. Boswell, General Counsel, North American Energy Standards Board
Mr. Charles Berardesco, General Counsel, North American Electric Reliability
Corporation
Mr. Mark Lauby, Vice President and Director, Standards, North American Electric
Reliability Corporation
NORTH AMERICAN ENERGY STANDARDS BOARD
801 Travis, Suite 1675 • Houston, Texas 77002 • Phone: (713) 356-0060 • Fax: (713) 356-0067
email: [email protected] • Web Site Address: www.naesb.org
December 20, 2012
UNITED STATES OF AMERICA
FEDERAL ENERGY REGULATORY COMMISSION
Standards for Business Practices and
Communication Protocols for Public Utilities
)
)
Docket No. RM05-5-000
Docket No. RM05-5-022
REPORT OF THE NORTH AMERICAN ENERGY STANDARDS BOARD
The North American Energy Standards Board (“NAESB”) is voluntarily submitting this report to the Federal Energy
Regulatory Commission (“FERC” or “Commission”) in the above referenced docket to inform the Commission of
errata to the NAESB Wholesale Electric Quadrant (“WEQ”) Version 003 business practice standards. This report is
organized into appendices; the first four appendices reference the specific minor corrections as adopted by the WEQ
Executive Committee. The last three appendices reference the WEQ Executive Committee action approving the
minor corrections on October 23,2012, the notice to WEQ membership of the WEQ EC adoption of the minor
correction distributed on October 30, 2012, and the NAESB Operating Procedures for minor clarifications and
corrections to standards.
The list of appendices shown below in tabular form include the FERC docket number(s) for the amended
standard(s), the version(s) of standard(s) amended, and a description of the amendments:
Appendix No.
Minor Correction Description
Appendix 1
MC12032 applies to Docket No. RM05-5-022 and Version 003 of the NAESB WEQ business
practice standards
Minor Correction – make consistency changes for the movement of the NERC TSIN registry to
the NAESB EIR registry in the following NAESB WEQ Business Practice Standards, Version
003:
•
Business Practice Standards WEQ-000 Abbreviations, Acronyms, and Definitions of Terms
•
Business Practice Standards WEQ-001 Open Access Same-Time Information Systems
(OASIS), Version 2.0
Business Practice Standards WEQ-003 Open Access Same-Time Information Systems
(OASIS) Data Dictionary, Version 2.0
•
Page 1 of 4
Appendix No.
Minor Correction Description
Appendix 2
MC12034 applies to Docket No. RM05-5-022 and Version 003 of the NAESB WEQ business
practice standards
Minor Correction – to avoid confusion the acronym “ISO – International Organization for
Standardization” was deleted and spelled out as “International Organization for Standardization
Standard” and the acronym “VEE – Validation Editing and Estimation” was changed to “VEE –
Validating, Editing and Estimating” in the following NAESB WEQ Business Practice Standards,
Version 003:
Appendix 3
•
Business Practice Standards WEQ-000 Abbreviations, Acronyms, and Definitions of Terms
•
Business Practice Standards WEQ-019 Customer Energy Usage Information Communication
MC12035 applies to Docket No. RM05-5-022 and Version 003 of the NAESB WEQ business
practice standards
Minor Correction – make consistency changes (capitalization) based on terms documented in
NAESB WEQ Business Practice Standards WEQ-000 Abbreviations, Acronyms, and Definition
of Terms by changing “Firm” to “firm” and update references to NERC documents in the
following NAESB WEQ Business Practice Standards, Version 003:
•
Appendix 4
Business Practice Standards WEQ-008 Transmission Loading Relief (TLR) – Eastern
Interconnection
MC12036 applies to Docket No. RM05-5-022 and Version 003 of the NAESB WEQ business
practice standards
Minor Correction – make consistency changes in the use of “template” to the defined term
“OASIS Template” in the following NAESB WEQ Business Practice Standards, Version 003:
•
Business Practice Standards WEQ-001 Open Access Same-Time Information Systems
(OASIS), Version 2.0
•
Business Practice Standards WEQ-002 Open Access Same-Time Information Systems
(OASIS) and Communication Protocol (S&CP), Version 2.0
•
Business Practice Standards WEQ-003 Open Access Same-Time Information Systems
(OASIS) Data Dictionary, Version 2.0
•
Business Practice Standards WEQ-013 Open Access Same-Time Information Systems
(OASIS) Implementation Guide, Version 2.0
Appendix 5
NAESB WEQ Executive Committee notational ballot results approving NAESB WEQ minor
corrections.
Appendix 6
Notice to WEQ members of Executive Committee adoption of minor corrections.
Appendix 7
NAESB operating procedures for minor clarifications and corrections to standards.
Page 2 of 4
Appendix 1 – Minor Correction MC12032
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
Appendix 1 contains Minor Correction MC12032, minor correction to NAESB WEQ Business Practice
Standards, Version 003: Business Practice Standards WEQ-000 Abbreviations, Acronyms, and Definitions
of Terms, Business Practice Standards WEQ-001 Open Access Same-Time Information Systems (OASIS),
Version 2.0, and Business Practice Standards WEQ-003 Open Access Same-Time Information Systems
(OASIS) Data Dictionary, Version 2.0 as approved by the WEQ EC on October 23, 2012.
Appendix 1 - Page 1 of 8
Appendix 1 – Minor Correction MC12032
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
MC12032
Approved by the WEQ Executive Committee on October 23, 2012
North American Energy Standards Board
Request for Minor Correction/Clarification of a NAESB Business Practice Standard, Model
Business Practice or Electronic Transaction
Date of September 12, 2012
Request:
1. Submitting Entity & Address:
JT Wood
Southern Company Services, Inc.
600 North 18th Street
Birmingham, AL 35291-8210
2. Contact Person, Phone #, Fax #, Electronic Mailing Address:
Name:
Title:
Phone:
Fax:
Email:
JT Wood
Reliability Standards Project Manager
205-769-7328
205-769-7344
[email protected]
3. Version and Standard Number(s) suggested for correction or clarification:
NAESB WEQ Business Practice Standards, Version 003:
NAESB Business Practice Standards WEQ-000 Abbreviations,
Acronyms, and Definitions of Terms
NAESB Business Practice Standards WEQ-001 Open Access Same-Time
Information Systems (OASIS), Version 2.0
NAESB Business Practice Standards WEQ-003 Open Access Same-Time
Information Systems (OASIS) Data Dictionary, Version 2.0
Appendix 1 - Page 2 of 8
Appendix 1 – Minor Correction MC12032
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
4. Description of Minor Correction/Clarification including redlined standards
corrections:
NAESB Business Practice Standards WEQ-000 Abbreviations, Acronyms, and
Definitions of Terms
WEQ-000-1 ABBREVIATIONS AND ACRONYMS
TSIN
Transmission System Information Network
NAESB Business Practice Standards WEQ-001 Open Access Same-Time
Information Systems (OASIS), Version 2.0
001-2.1
A Transmission Provider shall use the values and definitions below for the
service period attributes, SERVICE_INCREMENT and TS_W INDOW for all
Transmission Services offered on OASIS, or shall registerpost alternative
service period values and associated definitions in the EIRon the OASIS
Home Page at http://www.tsin.com, or shall use existing attribute values and
definitions registeredposted by other Transmission Providers. (See
Business Practice Standard WEQ-001-3 for registration requirements.)
001-2.2
A Transmission Provider shall use the values and definitions below to
describe the service class, TS_CLASS, for Transmission Services offered on
OASIS, or shall registerpost alternative TS_CLASS attribute values and
associated definitions in the EIRon the OASIS Home Page at
http://www.tsin.com, or shall use the attribute values and definitions
registeredposted by other Transmission Providers. (See Business Practice
Standard WEQ-001-3 for registration requirements.)
001-2.3
A Transmission Provider shall use the values and definitions below to
describe the service type, TS_TYPE, for Transmission Services offered on
OASIS, or shall registerpost alternative attribute values and associated
definitions in the EIRon the OASIS Home Page at http://www.tsin.com, or
shall use the attribute values and definitions registeredposted by other
Transmission Providers. (See Business Practice Standard WEQ-001-3 for
registration requirements.)
001-2.4
A Transmission Provider that has adopted NERC TLR procedures shall use
the Curtailment priority definitions contained in those procedures for all
Transmission Services offered on OASIS. A Transmission Provider that has
adopted alternative Curtailment procedures shall registerpost its alternative
Appendix 1 - Page 3 of 8
Appendix 1 – Minor Correction MC12032
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
attribute values and associated definitions in the EIRon the OASIS Home
Page at http://www.tsin.com, or shall use attribute values and definitions
registeredposted by another Transmission Provider. (See Business Practice
Standard WEQ-001-3 for registration requirements.)
001-2.5
A Transmission Provider shall use the definitions below to describe the
AS_TYPEs offered on OASIS, or shall registerpost alternative attribute
values and associated definitions in the EIRon the OASIS Home Page at
http://www.tsin.com, or shall use attribute values and definitions
registeredposted by another Transmission Provider. (See Business Practice
Standard WEQ-001-3 for registration requirements.)
001-3.1
All entities or persons using OASIS shall register the identity of their
organization (including DUNS number) or person in the EIRat the OASIS
Home Page at http://www.tsin.com. Registration identification shall include
the parent entity (if any) of the registrant. Registration shall be a prerequisite
to OASIS usage and renewed annually and whenever changes in
identification occur and thereafter. An entity or person not complying with
this requirement or providing false information may be denied access by a
Transmission Provider to that Transmission Provider’s OASIS Node.
The registration requirement applies to any entity logging onto OASIS for the
purpose of using or updating information, including Transmission Providers,
Transmission Customers, Observers, Control Areas, Security Coordinators,
and Independent System Operators.
Process to Register Non-Standard Service Attribute Values
Business Practice Standard WEQ-001-2 addresses the use of standard
terminology in defining services on OASIS. These standard definitions for
service attribute values will be registeredposted publicly in the EIRon the
OASIS Home Page at http://www.tsin.com and may be used by all
Transmission Providers to offer Transmission Services and ancillary services
on OASIS. If the Transmission Provider determines that the standard
definitions are not applicable, the Transmission Provider may register new
attribute values and definitions in the EIRon the OASIS Home Page. Any
Transmission Provider may use the attribute values and definitions
registeredposted by another Transmission Provider.
001-3.2
Providers of Transmission Services and ancillary services shall use only
attribute values and definitions that have been registered in the EIRon the
OASIS Home Page at http://www.tsin.com for all Transmission Services and
ancillary services offered on their OASIS.
001-3.3
Providers of Transmission Services and ancillary services shall endeavor to
use on their OASIS Nodes attribute values and definitions that have been
registeredposted by other Transmission Providers in the EIRon the OASIS
Appendix 1 - Page 4 of 8
Appendix 1 – Minor Correction MC12032
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
Home Page at http://www.tsin.com whenever possible.
Registration of PORs and PODs
In order to improve coordination of path naming and to enhance the
identification of commercially available connection points between
Transmission Providers and Regional Entities, the Business Practice for
OASIS requires that:
I.
Transmission Providers register in the EIRat the OASIS Home Page
at http://www.tsin.com, all service points (PORs and PODs) for which
Transmission Service is available over the OASIS.
II.
Each Transmission Provider would then indicate on its OASIS Node,
for each Posted Path on its OASIS Node, the PORs and PODs to
which each path is connected.
A Transmission Provider is not required to register specific generating
stations as PORs, unless they were available as service points for the
purposes of reserving Transmission Service on OASIS. The requirement
also does not include registration of regional Flowgates, unless they are
service points for the purposes of reserving Transmission Service on OASIS.
001-3.4
A Transmission Provider shall register and thereafter maintain in the EIRon
the OASIS Home Page at http://www.tsin.com all PORs and PODs to and
from which a Transmission Customer may reserve and schedule
Transmission Service.
001-3.5
For each reservable Posted Path on their OASIS Nodes, Transmission
Providers shall indicate the available PORs and PODs for that path. These
PORs and PODs shall be from the list registered in the EIRon the OASIS
Home Page at http://www.tsin.com.
001-6.4
A Transmission Provider may designate a sub-level for PORs and PODs.
For example, a Transmission Customer reserves a path to POD AAAA. The
ultimate load may be indeterminate at the time. Later, the Transmission
Customer schedules energy to flow to a particular load that may be
designated by the Transmission Provider as a sub-level POD. This option is
necessary to ensure certain Transmission Providers are not precluded from
using more specific service points by the inclusion of the POR/POD in the
path name. All sub-level PORs and PODs must be registered as such in the
EIRon http://www.tsin.com.
001-101.12.1 For customer-owned or customer-leased generation, the Eligible Customer
or Transmission Customer shall use the EIRTSIN-registered Source name.
001-101.13.1 For all requests to designate Network Load, the Eligible Customer or
Appendix 1 - Page 5 of 8
Appendix 1 – Minor Correction MC12032
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
Transmission Customer shall use the EIRTSIN-registered Sink name.
NAESB Business Practice Standards WEQ-003 Open Access Same-Time
Information Systems (OASIS) Data Dictionary, Version 2.0
Delete first
occurrence of
ASTYPE
1{ALPHANUMERIC}20
Valid Values:
SC
RV
RF
EI
SP
SU
GI
DT
TL
BS
{Registered}
ASTYPE
1{ALPHANUMERIC}20
Valid Values:
SC
RV
RF
EI
SP
SU
GI
DT
TL
BS
{Registered}
AS_TYPE
AS_TYPE
SC – Scheduling,
system Control and
Dispatch
RV – Reactive
Supply and Voltage
Control
RF – Regulation
and Frequency
Response
EI –
Energy
Imbalance
SP – Spinning
Reserve
SU –
Supplemen
tal Reserve
GI –
Generator
Imbalance
DT –
Dynamic
Transfer
TL –
Real power
Transmission Loss
BS – System
Black Start
Capability
{Registered} – must
be registered with
www.tsin.com and
listed in the
ancserv Template
SC – Scheduling,
system Control and
Dispatch
RV – Reactive
Supply and Voltage
Control
RF – Regulation
and Frequency
Response
EI –
Energy
Imbalance
SP – Spinning
Reserve
SU –
Supplemen
tal Reserve
GI –
Generator
Imbalance
DT –
Dynamic
Transfer
TL –
Real power
Appendix 1 - Page 6 of 8
Appendix 1 – Minor Correction MC12032
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
CUSTOMER_CODE
CUST
1{ALPHANUMERIC}6
Unique value,
registered in the
EIRon
www.tsin.com
PRIMARY_PROVIDER
_CODE
PROVIDER
1{ALPHANUMERIC}4
Unique code
SERVICE_INCREMENT
SRVINCR
1{ALPHANUMERIC}8
Valid Values:
HOURLY
DAILY
WEEKLY
MONTHLY
YEARLY
{Registered}
TS_CLASS
TSCLASS
1{ALPHANUMERIC}20
Valid Values:
FIRM
NON-FIRM
TTC
SECONDARY
{Registered}
Transmission Loss
BS – System
Black Start
Capability
{Registered} – must
be registered in the
EIRwith
www.tsin.com and
listed in the
ancserv Template
Any entity that is
eligible to view
OASIS information,
to execute a service
agreement, and/or
to receive
Transmission
Service.
Unique code for
each Transmission
Provider. Used by
PATH_NAME and
in URL. Registered
as part of URL in
the EIRat
www.tsin.com.
The Transmission
Service increments
provided. Five are
pre-defined, while
additional
increments can be
used if they are
registered in the
EIRon
www.tsin.com and
shown in the
Transmission
Provider's list
Template.
The Transmission
Service classes
provided. Four are
pre-defined, while
additional classes
can be used if they
are registered in the
EIRon
www.tsin.com and
shown in the
Transmission
Provider's list
Template page.
SECONDARY is
defined as alternate
PORs or PODs for
POINT_TO_POINT,
or as nondesignated
Appendix 1 - Page 7 of 8
Appendix 1 – Minor Correction MC12032
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
resources for
NETWORK service.
TS_PERIOD
TSPER
1{ALPHANUMERIC}20
Valid Values:
ON_PEAK
OFF_PEAK
FULL_PERIOD
{Registered}
TS_TYPE
TSTYPE
1{ALPHANUMERIC}20
Valid Values:
POINT_TO_POIN
T
NETWORK
ATC
{Registered}
TS_WINDOW
TSWIND
1{ALPHANUMERIC}20
Valid Values:
FIXED
SLIDING
EXTENDED
NEXT_INCREME
NT
{Registered }
TTC is retained as
a Valid Value for
historical purposes
only.
The Transmission
Service periods
provided. Three are
pre-defined, while
additional periods
can be used if they
are registered in the
EIRon
www.tsin.com and
shown in the
Transmission
Provider's list
Template.
The Transmission
Service types
provided. Three are
pre- defined, while
additional types can
be used if they are
registered in the
EIRon
www.tsin.com and
shown in the
Transmission
Provider's list
Template.
ATC is retained as
a Valid Value for
historical purposes
only.
The Transmission
Service windows
provided. Four are
pre-defined, while
additional windows
can be used if they
are registered in the
EIRon
www.tsin.com and
shown in the
Transmission
Provider's list
Template.
5. Reason for of Minor Correction/Clarification:
To make consistency changes to the NAESB OASIS Business Practice Standards for the
movement of the NERC TSIN registry to the NAESB EIR registry.
Appendix 1 - Page 8 of 8
Appendix 2 – Minor Correction MC12034
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
Appendix 2 contains Minor Correction MC12034, minor correction to NAESB WEQ Business Practice
Standards, Version 003: Business Practice Standards WEQ-000 Abbreviations, Acronyms, and Definitions
of Terms, and Business Practice Standards WEQ-019 Customer Energy Usage Information Communication
as approved by the WEQ EC on October 23, 2012.
Appendix 2 - Page 1 of 3
Appendix 2 – Minor Correction MC12034
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
MC12034
Approved by the WEQ Executive Committee on October 23, 2012
North American Energy Standards Board
Request for Minor Correction/Clarification of a NAESB Business Practice Standard, Model
Business Practice or Electronic Transaction
Date of September 19, 2012
Request:
3. Submitting Entity & Address:
Ed Skiba
MISO
P.O. Box 4202
Carmel IN 46082-4202
4. Contact Person, Phone #, Fax #, Electronic Mailing Address:
Name:
Title:
Phone:
Fax:
Email:
Ed Skiba
Consulting Advisor
317-249-5377
317-249-5358
[email protected]
3. Version and Standard Number(s) suggested for correction or clarification:
NAESB WEQ Business Practice Standards, Version 003:
NAESB Business Practice Standards WEQ-000 Abbreviations,
Acronyms, and Definitions of Terms
NAESB Business Practice Standards WEQ-019 Customer Energy Usage
Information Communication.
4. Description of Minor Correction/Clarification including redlined standards
corrections:
WEQ-000-1 Abbreviations and Acronyms
ISO
Independent System Operator
ISO
International Organization for Standardization
VEE
Validating, Editing &and Estimating
VEE
Validation Editing and Estimation
Appendix 2 - Page 2 of 3
Appendix 2 – Minor Correction MC12034
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
WEQ-000-2 Definitions of Terms
Power Plant Gas Coordinator
(PPGC)
Validation Editing and
Estimation
Validating, Editing and
Estimating (VEE)
The entity(ies) responsible for acquiring natural gas to meet a
PPGC Facility’s operating requirements and for scheduling
the delivery of said natural gas to the PPGC Facility that has
responsibility for gas requirements for a natural gas-fired
electric generating facility(ies) and is responsible for
coordinating natural gas deliveries with the appropriate
Transportation Service Provider(s) to meet those
requirements. The PPGC may perform some or alls a number
of the following coordinated activities, including, but not
limited to, power plant operations, unit dispatch, natural gas
procurement and/or gas transportation arrangements.
Because each PPGC is structured differently, specific
responsibilities within each PPGC should be determined by
the PPGC and the point of contact for the PPGC should be
communicated to the Transportation Service Provider(s).
(Note: This also applies to NAESB WGQ Standard Nos. 0.2.1,
0.2.2, 0.3.11, 0.3.12, 0.3.13, 0.3.14, and 0.3.15)
The process of confirming the accuracy of raw
meter data and, if necessary, replacing corrupt or
missing data. VEE guidelines are published in the
Edison Electric Institute’s Uniform Business
Practices for Unbundled Electricity Metering.
WEQ-019 Sections
019-3.1.1
019-3.1.8
ISO International Organization for Standardization
Standard ISO
019-3.1.42
5. Reason for of Minor Correction/Clarification:
There are two different meanings for ISO currently in WEQ-000: a)
Independent System Operator and b) International Organization for
Standardization. To avoid confusion it is recommended that the acronym for
International Organization for Standardization should not be used. Rather, it
should be spelled out. Conforming changes are required for WEQ-019.
After reviewing the WEQ Demand Response/Energy Subcommittee co-chairs
reviewed the Edison Electric Institute’s standards it was recommended that
VEE be changed to Validating, Editing and Estimating. Conforming changes
are also being made to WEQ-000-2.
Correct a typographical error in definition of Power Plant Gas Coordinator.
Appendix 2 - Page 3 of 3
Appendix 3 – Minor Correction MC12035
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
Appendix 3 contains Minor Correction MC12035, minor correction to NAESB WEQ Business Practice
Standards, Version 003: Business Practice Standards WEQ-008 Transmission Loading Relief (TLR) –
Eastern Interconnection as approved by the WEQ EC on October 23, 2012.
Appendix 3 - Page 1 of 5
Appendix 3 – Minor Correction MC12035
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
MC12035
Approved by the WEQ Executive Committee on October 23, 2012
North American Energy Standards Board
Request for Minor Correction/Clarification of a NAESB Business Practice Standard, Model
Business Practice or Electronic Transaction
Date of September 19, 2012
Request:
5. Submitting Entity & Address:
Ed Skiba
MISO
P.O. Box 4202
Carmel IN 46082-4202
6. Contact Person, Phone #, Fax #, Electronic Mailing Address:
Name:
Title:
Phone:
Fax:
Email:
Ed Skiba
Consulting Advisor
317-249-5377
317-249-5358
[email protected]
3. Version and Standard Number(s) suggested for correction or clarification:
NAESB WEQ Business Practice Standards, Version 003:
NAESB Business Practice Standards WEQ-008 Transmission Loading
Relief (TLR) – Eastern Interconnection
4. Description of Minor Correction/Clarification including redlined standards
corrections:
NAESB WEQ-008 Transmission Loading Relief
Redline:
008-2.2.1.1 The RC shall consider the entire Interchange Transaction non-firm if
the transmission link (i.e. a segment on the Contract Path) on the
Constrained Facility or Flowgate is Non-Firm Transmission Service,
even if other links in the Contract Path are Firm firm.
Clean:
008-2.2.1.1 The RC shall consider the entire Interchange Transaction non-firm if
the transmission link (i.e. a segment on the Contract Path) on the
Constrained Facility or Flowgate is Non-Firm Transmission Service,
even if other links in the Contract Path are firm.
Appendix 3 - Page 2 of 5
Appendix 3 – Minor Correction MC12035
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
Minor correction for Business Practice Standard WEQ-008-3.3.1 to delete “(as
found in current version of NERC IRO-006-4)” This is not the current version of
the standards, and IRO-006-5 no longer includes anything about Reallocation.
Redline:
008-3.3.1
The RC shall allow those Interchange Transactions using Firm
Transmission Service that have been submitted prior to the NERCapproved Tag submission deadline for Reallocation (as found in
current version of NERC IRO-006-4) to be initiated as scheduled.
Clean:
008-3.3.1
The RC shall allow those Interchange Transactions using Firm
Transmission Service that have been submitted prior to the NERCapproved Tag submission deadline for Reallocation to be initiated as
scheduled.
Minor correction for Business Practice Standard WEQ-008-3.3.1.2 to change INT004.1 to INT-004.2.
Redline:
008-3.3.1.2 Reallocations for Dynamic Schedules are as follows: If an Interchange
Transaction is identified as a Dynamic Schedule and the
Transmission Service is considered firm according to the constrained
path method, then it will not be held by the IDC during TLR level 4 or
lower. Adjustments to Dynamic Schedules in accordance with
current version of NERC INT-004-1INT-004-2 will not be held under
TLR level 4 or lower.
Clean:
008-3.3.1.2 Reallocations for Dynamic Schedules are as follows: If an Interchange
Transaction is identified as a Dynamic Schedule and the
Transmission Service is considered firm according to the constrained
path method, then it will not be held by the IDC during TLR level 4 or
lower. Adjustments to Dynamic Schedules in accordance with
current version of NERC INT-004-2 will not be held under TLR level 4
or lower.
Redline
008-A Appendix A – Examples of On-Path and Off-Path Mitigation
…
Case 1: E is a Non-Firm non-firm monthly path,
B
C
C Non-Firm non-firm hourly; E has
A
DNon Firm
Constraint at #2.
1
•
•
Network
Non Firm
Weekly
E may call RC for TLR procedure to relieve
overload at Constraint #2.
Interchange Transaction A-D may be
curtailed by TLR action as though it was
being served by Non-Firm non-firm
monthly PTP, even though it was using
Non-Firm non-firm hourly PTP from C. That
E
2
Non Firm
Monthly
Non Firm
Hourly
F
Contract path
Appendix 3 - Page 3 of 5
Appendix 3 – Minor Correction MC12035
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
is, it takes on the priority of the link with the Constrained Facility or Flowgate along the
Contract Path. (See Business Practice Standard WEQ-008-2.2.)
Case 2: E is a Non-Firm non-firm hourly path, C is firm; E has Constraint at #2.
•
•
•
Although C is providing Firm Transmission Service, the Constraint is not on C’s system;
therefore, E is not obligated to treat the Interchange Transaction as though it was being
served by Firm Transmission Service.
B
E may call RC for TLR procedure to
C
A
relieve overload at Constraint #2.
DNon Firm
1
Interchange Transaction A-D may be
Network
Non Firm
Weekly
curtailed by TLR action as though it was
Firm
being served by Non-Firm non-firm hourly
Non Firm
PTP, even though it was using Firm
2 Hourly
E
Transmission Service from C. That is,
when the Constraint is on the Contract
Path, the Interchange Transaction takes
on the priority of the link with the Contract path
F
Constrained Facility or Flowgate. (See
Business Practice Standard WEQ-008-2.2.)
Case 3: E is a Non-Firm non-firm hourly path, C is firm, B has Constraint at #1.
•
•
B may call RC for TLR procedure to
relieve overload at Constraint #1.
Interchange Transaction A-D may be
curtailed by TLR action as though it was
being served by Non-Firm non-firm hourly
PTP, even if it was using Firm
Transmission Service elsewhere on the
path. When the Constraint is off the
Contract
Path,
the
Interchange
Transaction takes on the lowest priority
reserved on the Contract Path. (See
Business Practice Standard WEQ-0082.3.)
…
Clean
008-A Appendix A – Examples of On-Path
and Off-Path Mitigation
…
Case 1: E is a non-firm monthly path, C nonfirm hourly; E has Constraint at #2.
•
•
E may call RC for TLR procedure to relieve
overload at Constraint #2.
Interchange Transaction A-D may be
curtailed by TLR action as though it was
B
A
C
D
1
Non Firm
Network
Non Firm
Weekly
Firm
E
2
Non Firm
Hourly
F
Contract path
B
A
C
D
1
Non Firm
Network
Non Firm
Weekly
E
2
Non Firm
Monthly
Non Firm
Hourly
F
Contract path
Appendix 3 - Page 4 of 5
Appendix 3 – Minor Correction MC12035
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
being served by non-firm monthly PTP, even though it was using non-firm hourly
PTP from C. That is, it takes on the priority of the link with the Constrained Facility or
Flowgate along the Contract Path. (See Business Practice Standard WEQ-008-2.2.)
Case 2: E is a non-firm hourly path, C is firm; E has Constraint at #2.
•
•
•
Although C is providing Firm Transmission Service, the Constraint is not on C’s system;
therefore, E is not obligated to treat the Interchange Transaction as though it was being
served by Firm Transmission Service.
B
E may call RC for TLR procedure to
C
A
relieve overload at Constraint #2.
DNon Firm
1
Interchange Transaction A-D may be
Network
Non Firm
Weekly
curtailed by TLR action as though it was
Firm
being served by non-firm hourly PTP, even
Non Firm
though it was using Firm Transmission
2 Hourly
E
Service from C. That is, when the
Constraint is on the Contract Path, the
Interchange Transaction takes on the
priority of the link with the Constrained Contract path
F
Facility or Flowgate. (See Business
Practice Standard WEQ-008-2.2.)
Case 3: E is a non-firm hourly path, C is firm, B has Constraint at #1.
•
•
B may call RC for TLR procedure to
relieve overload at Constraint #1.
Interchange Transaction A-D may be
curtailed by TLR action as though it was
being served by non-firm hourly PTP, even
if it was using Firm Transmission Service
elsewhere on the path. When the
Constraint is off the Contract Path, the
Interchange Transaction takes on the
lowest priority reserved on the Contract
Path. (See Business Practice Standard
WEQ-008-2.3.)
B
A
C
D
1
Non Firm
Network
Non Firm
Weekly
Firm
E
Contract path
2
Non Firm
Hourly
F
5. Reason for of Minor Correction/Clarification:
Changes are being submitted to reflect updates references to NERC documents
and to make conforming changes based on terms documented in WEQ-000
Appendix 3 - Page 5 of 5
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
Appendix 4 contains Minor Correction MC12036, minor correction to NAESB WEQ Business Practice
Standards, Version 003: Business Practice Standards WEQ-001 Open Access Same-Time Information
Systems (OASIS), Version 2.0, Business Practice Standards WEQ-002 Open Access Same-Time
Information Systems (OASIS) and Communication Protocol (S&CP), Version 2.0, Business Practice
Standards WEQ-003 Open Access Same-Time Information Systems (OASIS) Data Dictionary, Version 2.0
and Business Practice Standards WEQ-013 Open Access Same-Time Information Systems (OASIS)
Implementation Guide, Version 2.0 as approved by the WEQ EC on October 23, 2012.
Appendix 4 - Page 1 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
MC12036
Approved by the WEQ Executive Committee on October 23, 2012
North American Energy Standards Board
Request for Minor Correction/Clarification of a NAESB Business Practice Standard, Model
Business Practice or Electronic Transaction
Date of September 19, 2012
Request:
7. Submitting Entity & Address:
JT Wood
Southern Company Services, Inc.
600 North 18th Street
Birmingham, AL 35291-8210
8. Contact Person, Phone #, Fax #, Electronic Mailing Address:
Name:
Title:
Phone:
Fax:
Email:
JT Wood
Reliability Standards Project Manager
205-769-7328
205-769-7344
[email protected]
3. Version and Standard Number(s) suggested for correction or clarification:
NAESB WEQ Business Practice Standards, Version 003:
NAESB Business Practice Standards WEQ-001 Open Access Same-Time
Information Systems (OASIS), Version 2.0
NAESB Business Practice Standards WEQ-002 Open Access Same-Time
Information Systems (OASIS) and Communication Protocol (S&CP),
Version 2.0
NAESB Business Practice Standards WEQ-003 Open Access Same-Time
Information Systems (OASIS) Data Dictionary, Version 2.0
NAESB Business Practice Standards WEQ-013 Open Access Same-Time
Information Systems (OASIS) Implementation Guide, Version 2.0
4.
Description of Minor Correction/Clarification including redlined standards
corrections:
Appendix 4 - Page 2 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
NAESB Business Practice Standards WEQ-001 Open Access Same-Time Information Systems (OASIS), Version 2.0
001-22.2 The Transmission Provider shall post all scheduled use of CBM and any Curtailments of those schedules in accordance with
NAESB Business Practice Standards WEQ-002 and WEQ-013 such that these schedules may be queried, viewed
and audited using the scheduledetail OASIS Ttemplate.
NAESB Business Practice Standards WEQ-002 Open Access Same-Time Information Systems (OASIS) and
Communication Protocol (S&CP), Version 2.0
002-4.2.7.4
Data Records
Data records immediately follow the standard input or response header records. With the exception of data records
grouped together as a single "logical record" through the use of Continuation Records, each data record in a CSV
formatted input message represents a single, complete execution of the associated OASIS Template. That is,
sending five CSV formatted input messages for a given OASIS Template to the same
PRIMARY_PROVIDER_CODE with a single data record per message shall be handled in exactly the same fashion
as sending a single CSV formatted input message for the same OASIS Template and
PRIMARY_PROVIDER_CODE which contains five data records. Each field (column) within each data record
defines the value to be associated with the corresponding Data Element defined in the COLUMN_HEADERS record.
The number of data records in the message is defined by the DATA_ROWS header record. The data values
associated with each column Data Element are interpreted based on the Data Element type as defined in the OASIS
Data Dictionary:
002-4.2.10.4
Use of Comments
PTP and ancillary service reservation OASIS Ttemplates support the following text Data Elements to be used to
communicate information between parties (i.e., Transmission Provider, Reseller, and Transmission Customer) to a
transaction:
002-4.3.1
Template Summary
The following table provides a summary of the process areas, and OASIS Templates to be used by users to query
information that will be downloaded or to upload information to the Transmission Provider’s OASIS. These
processes define the functions that must be supported by an OASIS Node related to the general OASIS, PTP and
related ancillary service information.
002-4.3.4.3
Transmission Reservation Reduction (reduction)
…..
If required by tariff or regulations, this OASIS Ttemplate is also used to document the periods of time when the
Transmission Provider reduces the service Curtailment priority for CCO Reservation (i.e., System Impact Study
CCO) due to either a change in system conditions or service term over which the priority of service is reduced from
Firm Transmission Service priority 7, to Non-Firm Transmission Service priority 6.
…...
In response to a reduction OASIS Template query, each primary record returned (CONTINUATION_FLAG = N)
shall include the ASSIGNMENT_REF, CAPACITY_GRANTED and CAPACITY_AVAILABLE in MWs over the
interval from START_TIME to STOP_TIME. CAPACITY_GRANTED is derived from the transmission reservation's
CAPACITY_GRANTED. CAPACITY_AVAILABLE is derived from the transmission reservation’s
CAPACITY_GRANTED less all reductions (if any) in reserved capacity (if any) over the interval from START_TIME
to STOP_TIME as specified in the CAPACITY_REDUCED (as negative valued MWs) Data Element.
REDUCTION_TYPE, REDUCTION_REASON, IMPACTING_REF, CAPACITY_REDUCED, and
NERC_CURTAILMENT_PRIORITY shall be null in each primary record returned in the reduction OASIS Ttemplate
response; these Data Elements shall be reported in Continuation Records, as appropriate, documenting all
Appendix 4 - Page 1 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
reductions in capacity and/or service Curtailment priority that are in effect over the START_TIME/STOP_TIME
Interval.
002-4.3.4.4
System Data (systemdata)
….
Narratives related to specific changes in posted TTC/TFC and/or ATC values shall be denoted by the
SYSTEM_ATTRIBUTE of ZERO_FATC_NARRATIVE, ZERO_NFATC_NARRATIVE,
FATC_CHANGES_NARRATIVE, or NFATC_CHANGE_NARRATIVE, and the specific narrative corresponding to
the TTC/TFC/ATC postings shall be placed in the ANNOTATION Data Element. The specific values for TTC and/or
ATC are posted under the systemdata OASIS Ttemplate for the SYSTEM_ATTRIBUTES of TTC, FATC and
NFATC, etc.
002-4.3.6.2.1
Renewal Provisions (rollover)
The Renewal Provisions (rollover) OASIS Ttemplate provides users with additional information related to the
specific provisions for exercising the right to renewal/rollover the associated Transmission Service reservation.
….
If there is no additional renewal/rollover information associated with a reservation selected via the query parameters,
there will be no record returned in the OASIS Ttemplate response for that reservation.
The query parameters below are to be applied in the same way as to the associated reservation Data Elements as
defined in the transstatus OASIS Ttemplate to select the specific reservations whose renewal/rollover information is
to be returned.
002-4.3.6.2.2
CCO Provisions (cco)
The CCO provisions (cco) OASIS Ttemplate provides users with additional information related to the specific
provisions of a CCO Reservation.
The query parameters associated with this OASIS Ttemplate may be specified by the user to limit the set of service
reservations whose CCO provisions are to be returned in the OASIS Ttemplate response.
….
The query parameters below are to be applied in the same way as to the associated reservation Data Elements as
defined in the transstatus OASIS Ttemplate to select the specific reservations whose CCO Reservation information
is to be returned.
002-4.3.6.2.3
Coordinated Group Status (cgstatus)
The Coordinated Group Status (cgstatus) query OASIS Ttemplate provides users with additional information related
to a Coordinated Request’s associated transmission requests and any reservations, if applicable, that have been
submitted as the Coordinated Group.
The query parameters associated with this OASIS Ttemplate may be specified by the user to limit the set of service
requests or reservations whose Coordinated Group information is to be returned in the OASIS Ttemplate response.
If there is no Coordinated Group information associated with the request(s) or reservation(s) selected via the query
parameters, no records will be returned in the OASIS Ttemplate response for that request/reservation.
Appendix 4 - Page 2 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
002-4.3.10.4
Personnel Transfers (personnel)
The Personnel Transfers (personnel) OASIS Template is used to post a notice of a transfer of a transmission
function employee to a position as a marketing function employee, or a transfer of a marketing function employee to
a position as a transmission function employee, as described in 18 CFR Part 358. The personnel OASIS Ttemplate
is an optional OASIS Ttemplate to be implemented at the Transmission Provider’s discretion.
002-4.3.10.5
Discretion (discretion)
The Discretion (discretion) OASIS Template is used to post a notice of a waiver of a tariff provision that a
Transmission Provider grants in favor of an Affiliate, as described in 18 CFR Part 358. The discretion OASIS
Ttemplate is an optional OASIS Ttemplate to be implemented at the Transmission Provider’s discretion.
002-4.3.10.6
Standards of Conduct (stdconduct)
The Standards of Conduct (stdconduct) OASIS Template indicates when information is disclosed in a manner
contrary to the Standards of Conduct, as described in 18 CFR Part 358. The stdconduct OASIS Template is an
optional OASIS Ttemplate to be implemented at the Transmission Provider’s discretion.
002-4.3.11
OASIS Audit Log
….
*A Transmission Provider is only required to implement the audit log OASIS Ttemplates personnelaudit,
discretionaudit, and stdconductaudit if and when the Transmission Provider also uses the personnel,
discretion, stdconduct OASIS Ttemplates for posting Standards of Conduct information required under 18 CFR
Part 358.
002-4.3.11.3.1
CSV Response Header Records
….
Immediately following the MODIFYING_NAME column header, each of the standard non-audit counterpart OASIS
Template's Data Elements shall be listed in the exact sequence defined for that non-audit OASIS Template.
Finally, OASIS implementations may include additional Data Elements identified by unique column headers
appended after the fixed audit and standard OASIS Template Data Elements. These additional Data Elements may
be used to convey implementation specific information maintained in the OASIS database in association with the
data being audited.
002-4.3.11.5
Special Audit OASIS Template Considerations
Transoffering
….
For those OASIS implementations that handle TTC/ATC information separately from the posting of commercial
offers of service, audit reports generated by the transofferingaudit OASIS Template may be limited to only
reporting changes to the Data Elements associated with the commercial aspects of the offer (e.g., OFFER_PRICE,
OFFER_START_TIME, etc.), and may return a null value for the CAPACITY Data Element. These OASIS Nodes
shall use the systemdataaudit OASIS Template audit reporting facility to allow for the full auditing of changes made
to TTC and ATC postings as required under FERC regulations.
Scheduledetail
Appendix 4 - Page 3 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
The scheduledetail OASIS Template combines information from one or more transmission reservations and
transmission security event postings (e.g., TLRs) with information posted on actual scheduled use of the
transmission system. Audit information related to changes made to a given transmission reservation shall be
auditable using the transstatusaudit OASIS Template. Audit information related to the posting of transmission
security events that led to a Curtailment or interruption of service, or the denial of a request to schedule service shall
be auditable using the securityaudit OASIS Template. Therefore, the scheduledetailaudit OASIS OASIS
Template shall only be required to report changes to the following Data Elements associated with the
scheduledetail OASIS Template:
002-4.5.1
INFO.HTM
When a regulatory order requires informational postings on OASIS and there is no OASIS S&CP OASIS Ttemplate
to support the postings or it is deemed inappropriate to use a OASIS Ttemplate, or the location of the posting has
not been specified in Business Practice Standard WEQ-001-13, there shall be a reference in INFO.HTM to the
required information, including, but not limited to, references to the following:
NAESB Business Practice Standards WEQ-003 Open Access Same-Time Information Systems (OASIS) Data
Dictionary, Version 2.0
AS_TYPE
ASTYPE
1{ALPHANUMERIC}20
Valid Values:
SC
RV
RF
EI
SP
SU
GI
DT
TL
BS
{Registered}
CATEGORY
CAT
0{ALPHANUMERIC}25
Valid name from
CATEGORY in
list OASIS
Template
COLUMN_HEADERS
HEADERS
1{ALPHANUMERIC}
Limited to all the Data
Elements names in one
OASIS Template
Headers
separated by
commas. Limited
to valid OASIS
Template Data
Element names.
Must use full
Data Element
SC – Scheduling, system
Control and Dispatch
RV – Reactive Supply
and Voltage Control
RF – Regulation and
Frequency Response
EI –
Energy Imbalance
SP – Spinning Reserve
SU – Supplemental
Reserve
GI –
Generator
Imbalance
DT –
Dynamic Transfer
TL –
Real power
Transmission Loss
BS – System Black Start
Capability
{Registered} – must be
registered in the EIR and
listed in the ancserv
OASIS Template
A name to be used to
categorize messages. Valid
names would include:
want-ad, Curtailment,
Outage,
OASIS_Maintenance_Outa
ge.
Example:
COLUMN_HEADERS=PAT
H_NAME,POI
NT_OF_RECEIPT,POINT_
OF_DELIVERY,
SOURCE,SINK
Appendix 4 - Page 4 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
DATA
DATA
0{ALPHA}50
DISCRETION_DESCRIPTION
DISCDESC
0{ALPHANUMERIC}1000
ELEMENT_NAME
ELEMENT
1{ALPHANUMERIC}40
EMPLOYEE_NAME
EMPNAME
1{ALPHANUMERIC}25
FACILITY_CLASS
FACLASS
0{ALPHANUMERIC}25
FACILITY_LIMIT_TYPE
FACLIMTYP
0{ALPHANUMERIC}25
FACILITY_LOCATION
FACLOC
0{ALPHANUMERIC}8
FORMER_COMPANY
FORMCO
1{ALPHANUMERIC}25
name and not
alias.
Valid values:
Any of the valid
NITS
Query/Response
OASIS Data
Template names
as specified in
WEQ-002
Free form text
Valid OASIS
Template
element name
Free form text
Free form text, for
example:
TRANSFORMER,
LINE,
FLOWGATE
or as defined in
the list OASIS
Template
Free form text, for
example: thermal,
stability, voltage
or as defined in
list OASIS
Template
Free form text, for
example:
INTERNAL
EXTERNAL
Or as defined in
the list OASIS
Template
Free form text
Query variable specifying a
valid NITS
Query/Response OASIS
Data Template name
whose associated Data
Elements are to be
returned in the query
template response.
A detailed description of
the waiver being posted.
The discretion OASIS
Ttemplate and the related
DISCRETION_DESCRIPTI
ON Data Element are an
optional implementation at
the Transmission Provider’s
discretion.
OASIS Template element
name as indicated in
OASIS Data Dictionary.
Name of person who is
transferring from one
position to another. The
personnel OASIS
Ttemplate and the related
EMPLOYEE_NAME Data
Element are an optional
implementation at the
Transmission Provider’s
discretion.
Type of limiting device such
as ‘transformer’, ‘line’ or
‘Flowgate’
For example: thermal,
stability, voltage
Location of facility that
caused the interruption,
either internal to the TP or
external to the TP grid.
Former company of the
person who is transferring.
The personnel OASIS
Ttemplate and the related
FORMER_COMPANY Data
Element are an optional
implementation at the
Appendix 4 - Page 5 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
FORMER_DEPARTMENT
FORMDEPT
1{ALPHANUMERIC}52
Free form text
FORMER_POSITION
FORMPOS
1{ALPHANUMERIC}25
Free form text
INPUT_STATUS
INSTATUS
1{NUMERIC}3
Error number
MODIFYING_COMPANY_CODE
MODCODE
1{ALPHANUMERIC}6
Registered
company code for
a TP, SC or CA
MODIFYING_NAME
MODNAME
0{ALPHANUMERIC}25
Free form text
NERC_CURTAILMENT_PRIORITY
NERCURT
1{INTEGER}1
Integer
NEW_COMPANY
NEWCO
1{ALPHANUMERIC}25
Free form text
NEW_DEPARTMENT
NEWDEPT
1{ALPHANUMERIC}52
Free form text
Transmission Provider’s
discretion.
Former department of the
person who is transferring.
The personnel OASIS
Ttemplate and the related
FORMER_DEPARTMENT
Data Element are an
optional implementation at
the Transmission Provider’s
discretion.
Former position held by the
person who is transferring.
The personnel OASIS
Ttemplate and the related
FORMER_POSITION Data
Element are an optional
implementation at the
Transmission Provider’s
discretion.
Value indicating
success/failure of OASIS to
process the submitted NITS
OASIS INPUT Template;
200 = Success. Failure
indicates that some portion
of the uploaded OASIS
INPUT Ttemplate was
malformed.
Contains the registered
company code that
modified the transaction,
used in the audit OASIS
Templates.
Contain the name of the
person that modified the
transaction, used in the
audit OASIS Templates.
One of the NERC
Curtailment priorities,
documented in list OASIS
Template.
New company of the
person who is transferring.
The personnel OASIS
Ttemplate and the related
NEW_COMPANY Data
Element are an optional
implementation at the
Transmission Provider’s
discretion.
New department of the
person who is transferring.
The personnel OASIS
Ttemplate and the related
NEW_DEPARTMENT Data
Element are an optional
implementation at the
Transmission Provider’s
discretion.
Appendix 4 - Page 6 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
NEW_POSITION
NEWPOS
1{ALPHANUMERIC}25
Free form text
OTHER_CURTAILMENT_PRIORITY
OTHCUR
0{ALPHANUMERIC}8
Valid Values:
{Registered}
PRECONFIRMED
PRECONF
2{ALPHA}3
Valid Values:
YES
NO
RECORD_TYPE
RECTYPE
1{ALPHA}1
Valid Values:
I
U
D
REQUEST
REQ
0{ALPHA}50
RESPONSIBLE_PARTY
_NAME
PARTNAME
1{ALPHANUMERIC}25
Valid values:
Any of the valid
NITS
Input/Response
OASIS Request
Template names
as specified in
WEQ-002
Free form text
New position held by the
person who is transferring.
The personnel OASIS
Ttemplate and the related
NEW_POSITION Data
Element are an optional
implementation at the
Transmission Provider’s
discretion.
Other than NERC
Curtailment priorities, such
as regional Curtailment
priorities. Suggested format
region+number, for
example MRO4, WECC7.
Documented in list OASIS
Template and registered
with central EIR.
Used by Transmission
Customer to preconfirm
sale in OASIS Templates
transrequest or
ancrequest. If
Transmission Customer
indicates sale is
preconfirmed, then the
response is YES and the
Transmission Customer
does not need to confirm
the sale.
Indicates the type of
information reported in a
response record generated
by an audit OASIS
Template. "I" designates
information as it was
initially inserted (posted) on
OASIS; "U" designates
information updated
(modified) on OASIS; "D"
designates deleted
information as it appeared
on OASIS just prior to
being deleted (as
appropriate).
Query variable specifying a
valid NITS Input/Response
OASIS Request Template
names whose associated
Data Elements are to be
returned in the query
template response.
The name of the person
responsible for granting the
waiver. The discretion
OASIS Ttemplate and the
related
RESPONSIBLE_PARTY_N
AME Data Element are an
Appendix 4 - Page 7 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
SECURITY_REF
SECREF
1{ALPHANUMERIC}10
Unique value
SERVICE_INCREMENT
SRVINCR
1{ALPHANUMERIC}8
Valid Values:
HOURLY
DAILY
WEEKLY
MONTHLY
YEARLY
{Registered}
STANDARDS_OF_CONDUCT_ISS
UES
STDISSUE
0{ALPHANUMERIC}800
Free form text
START_TIME
STIME
16{ALPHANUMERIC}16
Valid date and
time to seconds:
yyyy+mo+dd+hh
+mm+ss+tz
STOP_TIME
SPTIME
16{ALPHANUMERIC}16
Valid date and
time
yyyy+mo+dd+hh
+mm+ss+tz
optional implementation at
the Transmission Provider’s
discretion.
Unique value generated by
company initiating the
security for each security
event in the security
OASIS Template.
The Transmission Service
increments provided. Five
are pre-defined, while
additional increments can
be used if they are
registered in the EIR and
shown in the Transmission
Provider's list OASIS
Template.
Information disclosures that
were in violation of the
FERC Standards of
Conduct described in 18
CFR, Part 358. This text
may include a reference
pointer to a more detailed
description. The
stdconduct OASIS
Template and the related
STANDARDS_OF_CONDU
CT_ISSUES Data Element
are an optional
implementation at the
Transmission Provider’s
discretion.
Start date and clock time of
a service. When used as a
Query Variable, it requires
the return of all items
whose Stop time is after
the Start time.
Note that for some OASIS
Templates when used as a
Query Variable the time
may be only valid up to the
hour, day or month. If more
data is given than is valid,
the hour, day or month will
be used to make the date
and time inclusive, i.e. date
or time will be truncated to
valid hour, day or month.
Stop date and clock time.
When used as a Query
Variable, it requires the
return of all items which
start before the stop time.
Note that for some OASIS
Templates when used as a
Query Variable the time
may be only valid up to the
hour, day or month. If more
Appendix 4 - Page 8 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
SYSTEM_ATTRIBUTE
SYSATTR
0{ALPHANUMERIC}20
Valid Values:
CBM
FTRM
NFTRM
TTC
FATC
NFATC
FGF
NFGF
ATC_ANNOTATI
ON
ZERO_FATC_NA
RRATIVE
ZERO_NFATC_N
ARRATIVE
FATC_CHANGE
_NARRATIVE
NFATC_CHANG
E_NARRATIVE
ZONE_FORECA
STED_LOAD
SYSTEM_FORE
CASTED_LOAD
NATIVE_FOREC
ASTED_LOAD
ZONE_ACTUAL_
LOAD
SYSTEM_ACTU
AL_LOAD
NATIVE_ACTUA
L_LOAD
{Registered}
data is given than is valid,
the hour, day or month will
be used to make the date
and time inclusive, i.e. date
or time will be increased to
include STOP_TIME.
Type of system data
viewed by systemdata
OASIS Ttemplate:
CBM
FTRM – TRM for use in
FATC
NFTRM – TRM for use in
NFATC
TTC – Total Transmission
Capability
FATC – Firm Available
Transmission
Capability
NFATC – Non-firm
Available
Transmission
Capability
FGF – Firm Grandfathered
firm
Transmission
Service
NFGF – Non-firm
Grandfathered
Transmission
Service
ATC_ANNOTATION –
Annotation for a
change in
monthly or yearly
posted ATC (no
longer used
replaced by
ZERO_FATC_N
ARRATIVE,
ZERO_NFATC_
NARRATIVE,
FATC_CHANGE
_NARRATIVE,
NFATC_CHANG
E_NARRATIVE)
ZERO_FATC_NARRATIVE
– Narrative when
a posted firm
monthly or yearly
ATC value
remains
unchanged at a
value of zero
ZERO_NFATC_NARRATIV
E – Narrative
when a posted
non-firm monthly
or yearly ATC
value remains
Appendix 4 - Page 9 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
TEMPLATE
TEMPL
1{ALPHANUMERIC}20
TS_CLASS
TSCLASS
1{ALPHANUMERIC}20
TS_PERIOD
TSPER
1{ALPHANUMERIC}20
Valid name of
Template from
Business Practice
Standard WEQ002-4.3.1 or from
list OASIS
Template
Valid Values:
FIRM
NON-FIRM
TTC
SECONDARY
{Registered}
Valid Values:
ON_PEAK
OFF_PEAK
FULL_PERIOD
unchanged at a
value of zero
FATC_CHANGE_NARRAT
IVE – Narrative
when a posted
firm monthly or
yearly ATC
changes as a
result of a 10
percent change
in TTC/TFC
NFATC_CHANGE_NARRA
TIVE – Narrative
when a posted
non-firm monthly
or yearly ATC
changes as a
result of a 10
percent change
in TTC/TFC
ZONE_FORECASTED_LO
AD – Anticipated
Forecasted Daily
Zonal Load
SYSTEM_FORECASTED_
LOAD –
Anticipated
Forecasted Daily
System-Wide
Peak Load
The name of a logical
collection of
DATA_ELEMENTS in a
user's interaction with an
OASIS Node.
The Transmission Service
classes provided. Four are
pre-defined, while
additional classes can be
used if they are registered
on www.tsin.com and
shown in the Transmission
Provider's list OASIS
Template page.
SECONDARY is defined as
alternate PORs or PODs
for POINT_TO_POINT, or
as non-designated
resources for NETWORK
service.
TTC is retained as a Valid
Value for historical
purposes only.
The Transmission Service
periods provided. Three are
pre-defined, while
additional periods can be
Appendix 4 - Page 10 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
{Registered}
TS_TYPE
TS_WINDOW
TSTYPE
TSWIND
1{ALPHANUMERIC}20
1{ALPHANUMERIC}20
Valid Values:
POINT_TO_POI
NT
NETWORK
ATC
{Registered}
Valid Values:
FIXED
SLIDING
EXTENDED
NEXT_INCREME
NT
{Registered }
used if they are registered
on www.tsin.com and
shown in the Transmission
Provider's list OASIS
Template.
The Transmission Service
types provided. Three are
pre- defined, while
additional types can be
used if they are registered
on www.tsin.com and
shown in the Transmission
Provider's list OASIS
Template.
ATC is retained as a Valid
Value for historical
purposes only.
The Transmission Service
windows provided. Four are
pre-defined, while
additional windows can be
used if they are registered
on www.tsin.com and
shown in the Transmission
Provider's list OASIS
Template.
NAESB Business Practice Standards WEQ-013 Open Access Same-Time Information Systems (OASIS)
Implementation Guide, Version 2.0
WEQ-013-3
Specific OASIS Template Implementation
Pages 47-61
013-2 OASIS TRANSACTION PROCESSING
….
a. The transrequest and ancrequest OASIS Ttemplates shall be used by the Transmission
Customer to enter a transaction request for specific Transmission Services or ancillary
services from a specified Seller. All pertinent transaction-specific information must be
provided in the OASIS Ttemplate Data Elements.
b. The transstatus and ancstatus OASIS Ttemplates shall be used by both Transmission
Customer and Seller to query for the current transaction information (e.g., STATUS).
Alternatively, the Transmission Customer may request dynamic notification per Business
Practice Standard WEQ-002-4.2.10.3 whenever the transaction data is changed.
c. The transsell and ancsell OASIS Ttemplates shall be used by the Seller to indicate to
the Transmission Customer whether the request is acceptable or not by setting the
transaction STATUS to one of RECEIVED, INVALID, STUDY, COUNTEROFFER,
CR_COUNTEROFFER, ACCEPTED, CR_ACCEPTED, REFUSED, SUPERSEDED,
DECLINED, DISPLACED, ANNULLED, or RETRACTED. A Transmission Provider as
the Seller may use the transsell and ancsell OASIS Ttemplates to act on requests or
may use proprietary software solutions to perform this function in a similar manner.
Appendix 4 - Page 11 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
d. The transcust and anccust OASIS Ttemplates shall be used by the Transmission
Customer to indicate to the Seller whether they wish to negotiate, confirm or withdraw the
transaction by setting the transaction STATUS to one of REBID, CONFIRMED, or
WITHDRAWN.
e.
The transassign and ancassign OASIS Ttemplates shall be used by the Seller to notify
the Transmission Provider of the transfer of rights from the Seller to the Transmission
Customer consummated off the OASIS Node.
Exhibit 1 Transaction OASIS Template Usage Diagram
013-2.1
TRANSACTION REQUEST TYPES
The following are the valid OASIS transaction request types (OASIS Ttemplate Data Element
REQUEST_TYPE) that may be submitted by the Transmission Customer unless otherwise
noted, along with a brief description of their intended use:
013-2.3
BASIC OASIS TRANSACTION HANDLING
Requests to reserve or purchase Transmission Service or ancillary service shall be submitted
to OASIS by the Transmission Customer via the transrequest or ancrequest OASIS
Ttemplates.
….
Once successfully submitted on OASIS, the Seller may take any of the following actions via the
transsell/ancsell OASIS Ttemplates:
• Acknowledge receipt by setting STATUS to RECEIVED or STUDY
• Deny the request by setting STATUS to INVALID, DECLINED, or REFUSED
• Approve the request by setting STATUS to ACCEPTED, CR_ACCEPTED,
COUNTEROFFER or CR_COUNTEROFFER
….
Once the Seller approves the request, the Transmission Customer may take any of the
following actions via the transcust/anccust OASIS Ttemplates:
• Withdraw the request
• Continue negotiation of the request by setting STATUS to REBID
• Complete the request by setting STATUS to CONFIRMED
013-2.4.1
Displacement – No Right of First Refusal
….
If only a portion of the confirmed reservation's capacity is required to accommodate the higher
priority request, the Transmission Provider shall document the recall of reserved capacity from
Appendix 4 - Page 12 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
the lower priority confirmed reservation by incrementing the IMPACTED counter on that
reservation and posting on OASIS the amount and time frames over which that reservation's
capacity was reduced, i.e., a partial displacement. The Transmission Customer may view all
impacts to existing Transmission Service reservations (e.g., partial displacements, secondary
sales, etc.) using the reduction OASIS Ttemplate.
013-2.4.2
Displacement – With Right of First Refusal
….
If the existing Transmission Customer elects to meet the terms and conditions of the
competing request, that Transmission Customer shall submit a new MATCHING reservation
request using the transrequest OASIS Ttemplate. The specific requirements associated with
submission of MATCHING requests are detailed in Business Practice Standard WEQ-0132.6.3.
013-2.5
TRANSMISSION PROVIDER RECALLS
….
The Transmission Provider shall provide a mechanism to post on OASIS any such reductions
or recalls in reserved capacity. The Transmission Customer shall be notified of any and all
such reductions in reserved capacity by the incrementing of the IMPACTED counter in
association with those reservations that are reduced; the IMPACTED flag is viewable with the
transstatus OASIS Ttemplate. Specific information regarding the exact nature of each
reduction in the reserved capacity under a given Transmission Service reservation shall be
posted and viewable with the reduction OASIS Ttemplate.
A specific example of a Transmission Provider initiated recall of reserved capacity is the
implementation of a partial displacement of a Transmission Service reservation. In this
instance, the Transmission Customer has not elected (or was not required to be offered) to
match the terms of a higher priority, competing request. The Transmission Provider recalls that
capacity necessary to accommodate the higher priority request from the existing lower priority
reservation. The IMPACTED counter of that reservation is incremented, and a query using the
reduction OASIS Ttemplate for that reservation would show the Transmission Customer the
amount and time-frame over which the Transmission Customer's reserved capacity was
recalled by the Transmission Provider.
Interruption of Transmission Service, where that interruption directly impacts the rights of the
Transmission Customer to schedule any service under that reservation, is another example of
an impact to reserved capacity that would be posted as a Transmission Provider initiated recall
of reserved capacity.
Secondary market sales of Transmission Service rights are not
examples of a Transmission Provider initiated recall of reserved capacity, but the impact of any
such sales shall also be returned in response to execution of the reduction OASIS Ttemplate.
The Transmission Provider may elect to post recalls of reserved capacity using the OASIS
REQUEST_TYPE of RECALL. Documenting Transmission Provider initiated recalls of
capacity with a recall request is optional; posting the impacts of those recalls to be made
available under the reduction OASIS Ttemplate is mandatory. If the recall request is used by
Appendix 4 - Page 13 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
the Transmission Provider, its use must be implemented in compliance with the Business
Practices for recall requests.
013-2.6
TRANSACTION SPECIFIC HANDLING
The following Business Practice Standards WEQ-013-2.6.1 through WEQ-013-2.6.4.1 identify
specific OASIS Data Elements and processing requirements that must be implemented by
OASIS and/or associated back-end support systems. The results of all transaction processing
shall be viewable by all appropriate entities via the transstatus/ancstatus OASIS Ttemplates
and corresponding OASIS user interface.
013-2.6.1
ORIGINAL Requests
….
ROLLOVER_WAIVED
If the Transmission Customer does not
wish a Long-Term Firm Point-to-Point
Transmission Service request to be
evaluated for conveyance of rollover
rights, the Transmission Customer must
submit the request with the
ROLLOVER_WAIVED data element set to
‘Y’ in the transrequest OASIS Ttemplate.
CG_STATUS
If the Transmission Customer
wishes this request to be a
Coordinated Request associated
with a Coordinated Group, the
Transmission Customer must
submit the request with the
CG_STATUS data element set
to PROPOSED in the
transrequest OASIS Ttemplate.
….
The Transmission Customer may submit a time varying profile of capacity as allowed by the
Transmission Provider’s Business Practice by repeating the OASIS Ttemplate Data Elements
of BID_PRICE, CAPACITY_REQUESTED, START_TIME and STOP_TIME in template
continuation records. The segments of any submitted profile must not overlap in time.
,…
If the Transmission Customer does not wish a long-term firm PTP Transmission Service
request to be evaluated for conveyance of rollover rights, the Transmission Customer must
submit the request with the ROLLOVER_WAIVED data element set to Y in the transrequest
OASIS Ttemplate.
Appendix 4 - Page 14 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
If the Transmission Customer wishes this request to be a Coordinated Request associated with
a Coordinated Group, the Transmission Customer must submit the request with the
CG_STATUS data element set to “PROPOSED” in the transrequest OASIS Ttemplate.
Additional requirements for handling Coordinated Requests are specified in Business Practice
Standard WEQ-013-2.6.9.
013-2.6.1.1
Offering of Partial Service
….
The Transmission Customer shall recognize the offer of Partial Service by
CAPACITY_GRANTED not being equal to CAPACITY_REQUESTED and the request
STATUS of COUNTEROFFER or CR_COUNTEROFFER. The Transmission Customer may
elect to set the request STATUS to CONFIRM, WITHDRAW, or REBID for the Partial Service
using the transcust OASIS Ttemplate.
To rebid for Partial Service the Transmission
Customer shall specify the revised START_TIME, STOP_TIME, CAPACITY_REQUESTED
and BID_PRICE values and set the request STATUS to REBID using the transcust OASIS
Ttemplate. OASIS shall restrict CAPACITY_REQUESTED on a rebid to not exceed the
Seller’s most recent CAPACITY_GRANTED over time.
013-2.6.1.2
Negotiation of Price
Negotiation of price is initiated by the Transmission Customer submitting a service request
(via transrequest/ancrequest OASIS Ttemplates) with a BID_PRICE that is different (higher
or lower) from the currently posted offer price, or the tariff rate, for that service. The following
negotiation process is required where the Seller is the Transmission Provider. Resales or
Transfers between Transmission Customers may use this process, but there is no obligation
on the (Re)Seller to offer a negotiated rate to other Transmission Customers.
If the Seller determines that the BID_PRICE is acceptable, the following actions must be
taken (via transsell/ancsell OASIS Ttemplates):
• Update the currently posted offer price for the service requested and all other
applicable services offered as dictated by current discounting policy (e.g., all
unconstrained paths to the same POD) to match BID_PRICE;
• Update the request’s NEGOTIATED_PRICE_FLAG to L or H if the BID_PRICE was
lower than or higher than, respectively, the posted price when the request was
submitted;
• Set the OFFER_PRICE equal to the BID_PRICE;
• Set the CAPACITY_GRANTED appropriately (if left null or undefined, OASIS shall
set CAPACITY_GRANTED equal to CAPACITY_REQUESTED when STATUS is set
to ACCEPTED or CR_ACCEPTED);
• Set the request STATUS to ACCEPTED or CR_ACCEPTED (or COUNTEROFFER
or CR_COUNTEROFFER if offering Partial Service)
The Transmission Customer may then confirm the purchase or withdraw the request by
updating the request STATUS (via transcust/anccust OASIS Ttemplates).
If the Seller determines that the BID_PRICE is unacceptable, and negotiation of price is not
going to be entertained, the Seller shall set the request STATUS to DECLINED (via
Appendix 4 - Page 15 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
transsell/ancsell OASIS Ttemplates):
If the Seller elects to enter into price negotiation, the following actions must be taken (via
transsell/ancsell OASIS Ttemplates):
• If the price to be counter offered by the Transmission Provider to the Transmission
Customer is different than the currently posted offer price:
o Update the currently posted offer price for the service requested and all other
applicable services offered as dictated by current discounting policy (e.g., all
unconstrained paths to the same POD) to match the price to be
counteroffered;
o Update the request’s NEGOTIATED_PRICE_FLAG to L or H if the price to be
counter offered is lower than or higher than, respectively, the posted price
when the request was submitted;
• Set the OFFER_PRICE and CAPACITY_GRANTED appropriately;
• Set the request STATUS to COUNTEROFFER or CR_COUNTEROFFER.
The Transmission Customer may then confirm the purchase, withdraw the request, or
propose a new BID_PRICE by performing the following (via transcust/anccust OASIS
Ttemplates):
• Update the request BID_PRICE appropriately;
Set the request STATUS to REBID or CONFIRMED.
013-2.6.1.3
Rollover Rights
For Transmission Services that have ongoing rollover or renewal rights, the Transmission
Provider shall document those rights and any limitations over time through the rollover
OASIS Ttemplate Data Elements RENEWAL_DUE_TIME, ROLLOVER_ELIGIBLE,
ROLLOVER_START_TIME, ROLLOVER_STOP_TIME, and ROLLOVER_CAPACITY. The
Transmission Provider must also flag that the Transmission Service request/reservation has
associated
rollover
rights
by
setting
the
transstatus
OASIS
Ttemplate
PRIMARY_PROVIDER_PROVISIONS Data Element to Y. The ROLLOVER_ELIGIBLE Data
Element is equivalent to the Capacity Eligible for Rollover or conveyance of rollover rights to
a qualified Redirect on a Firm basis; the ROLLOVER_CAPACITY Data Element is equivalent
to the remaining Unexercised Rollover Rights available over time.
Continuation records shall be used if the ROLLOVER_CAPACITY value changes as a
function of time by listing each applicable time interval and capacity eligible for
rollover/renewal in the ROLLOVER_START_TIME, ROLLOVER_STOP_TIME and
ROLLOVER_CAPACITY Data Elements. The first value for ROLLOVER_START_TIME shall
be set to the value of the latest STOP_TIME value associated with the request/reservation as
shown in the transstatus OASIS Ttemplate response, (i.e., rollover OASIS Ttemplate
response records begin at the end of the Transmission Service requested/reserved). If there
is no limitation on rollover rights, ROLLOVER_STOP_TIME shall be null and the
ROLLOVER_CAPACITY shall indicate the capacity eligible for rollover for all future time.
On confirmation of any Renewal request or request to Redirect on a Firm basis with rollover
rights,
the
values
for
the
ROLLOVER_ELIGIBLE,
ROLLOVER_START_TIME,
ROLLOVER_STOP_TIME, and ROLLOVER_CAPACITY Data Elements shall be updated and
returned in response to the rollover OASIS Ttemplate query.
Appendix 4 - Page 16 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
013-2.6.1.4
CCO
For Transmission Services that are subject to a CCO Reservations, the Transmission
Provider shall set the PRIMARY_PROVIDER_PROVISIONS Data Element to Y and provide
documentation on the nature of the CCO such that this information may be queried and
viewed using the cco OASIS Ttemplate. Prior to or upon confirming a Transmission Service
reservation with a CCO, the Transmission Provider shall make available the information
required in the cco OASIS Ttemplate CONDITIONAL_CURTAILMENT_OPTION,
SERVICE_DESCRIPTION
and
REASSESSMENT_END_TIME_Data
Elements.
REASSESSMENT_END_TIME must reflect the date and time that the current CCO
conditions may be subject to change as a result of a Biennial Reassessment performed by
the Transmission Provider.
If the CCO Reservation is not subject to a Biennial
Reassessment or is shorter than two years in duration, REASSESSMENT_END_TIME shall
be null.
If
the
CCO
Reservation
is
subject
to
the
Number-of-Hours
Criteria
(CONDITIONAL_CURTAILMENT_OPTION = “HOURS”), the Transmission Provider must
indicate the maximum number of actual hours that service may be curtailed at the
Conditional Curtailment Priority Level over a specified measurement interval set by the
CONDITIONAL_START_TIME/CONDITIONAL_STOP_TIME Data Elements. If there is
more than one such interval during the current service period up to the next
REASSESSMENT_END_TIME, each such interval shall be returned in cco OASIS
Ttemplate
continuation
records
containing
the
CONTINUATION_FLAG,
ASSIGNMENT_REF,
CONDITIONAL_START_TIME,
CONDITIONAL_STOP_TIME,
MAXIMUM_HOURS and ACCUMULATED_HOURS Data Elements.
The Transmission Provider shall update the ACCUMULATED_HOURS Data Element with
the current cumulative number of hours service under the CCO Reservation was actually
curtailed at the Conditional Curtailment Priority Level for that interval. Once the accumulation
CONDITIONAL_START_TIME/CONDITIONAL_STOP_TIME interval has expired, the final
ACCUMULATED_HOURS over that interval shall be retained and returned in the cco OASIS
Ttemplate response as the historical record of Curtailments made against the CCO
Reservation over time.
For CCO Reservations subject to Biennial Reassessment, the Transmission Provider shall
update any new accumulation interval and/or change in maximum Curtailment hours through
the end of the next reassessment interval by updating the REASSESSMENT_END_TIME,
CONDITIONAL_START_TIME, CONDITIONAL_STOP_TIME, MAXIMUM_HOURS and
ACCUMULATED_HOURS Data Elements returned in the response to a query issued for the
cco OASIS Ttemplate. This information shall be provided at the same time that the
reassessment study report is issued to the Transmission Customer,
If
the
CCO
Reservation
is
subject
to
the
System-Conditions
Criteria
(CONDITIONAL_CURTAILMENT_OPTION = “CONDITIONS”), the Transmission Provider
may, at their option, return information on the accumulated number of hours service was
actually curtailed using the corresponding cco OASIS Ttemplate Data Elements. For these
CCO Reservations, the MAXIMUM_HOURS Data Element will be returned as a null value.
Each confirmed PART_ TRANSFER or FULL_TRANSFER reservation made against a CCO
Reservation shall also be a CCO Reservation. Upon acceptance of a full Transfer of a CCO
Reservation, the Transmission Provider shall set the PRIMARY_PROVIDER_PROVISIONS
Appendix 4 - Page 17 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
Data Element to “Y” for the Transfer, populate the cco OASIS Ttemplate and assign the
ACCUMULATED_HOURS of the Parent Reservation to the Transfer. Each subsequent
Curtailment shall be accumulated against the Transfer only. Upon acceptance of a partial
Transfer of a CCO Reservation, the Transmission Provider shall set the
PRIMARY_PROVIDER_PROVISIONS Data Element to “Y” for the Transfer, populate the
cco OASIS Ttemplate and copy the ACCUMULATED_HOURS of the Parent Reservation to
the Transfer. Each subsequent Curtailment shall be accumulated against the Parent
Reservation and the Transfer.
If the CCO Reservation is subject to a Resale or a short-term Redirect on a firm basis where
the CCO criteria is to be applied to the Redirect service, all Curtailment accounting information
shall be accumulated against Parent Reservation which was resold or redirected as if all
service scheduled under the resold or redirected reservation(s) were scheduled against the
Parent
Reservation.
The
Transmission
Provider
shall
set
PRIMARY_PROVIDER_PROVISIONS to “Y” in each confirmed Resale or Redirect, if
applicable, reservation made against capacity granted under a CCO Reservation. In response
to a query issued for the cco OASIS Ttemplate, the cco OASIS Ttemplate response shall be
identical for each of the applicable Redirect and/or Resale reservations as that returned for the
Parent CCO Reservation.
013-2.6.2
RENEWAL Requests
….
ROLLOVER_WAIVED
If the Transmission Customer does not
wish a Long-Term Firm Point-to-Point
Transmission Service request to be
evaluated for conveyance of rollover
rights, the Transmission Customer must
submit the request with the
ROLLOVER_WAIVED data element set to
‘Y’ in the transrequest OASIS Ttemplate.
CG_STATUS
If the Transmission Customer
wishes this request to be a
Coordinated Request associated
with a Coordinated Group, the
Transmission Customer must
submit the request with the
CG_STATUS data element set
to PROPOSED in the
transrequest OASIS Ttemplate.
….
If the Transmission Customer does not wish a long-term firm PTP Transmission Service
request to be evaluated for conveyance of rollover rights, the Transmission Customer must
submit the request with the ROLLOVER_WAIVED Data Element set to ‘Y’ in the transrequest
OASIS Ttemplate.
Appendix 4 - Page 18 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
If the Transmission Customer wishes this request to be a Coordinated Request associated with
a Coordinated Group, the Transmission Customer must submit the request with the
CG_STATUS data element set to “PROPOSED” in the transrequest OASIS Ttemplate.
Additional requirements on the handling of Coordinated Requests are specified in Business
Practice Standard WEQ-013-2.6.9.
013-2.6.3
MATCHING Requests
….
CG_STATUS
If the Transmission Customer
wishes this request to be a
Coordinated Request associated
with a Coordinated Group, the
Transmission Customer must
submit the request with the
CG_STATUS data element set
to PROPOSED in the
transrequest OASIS Ttemplate.
If the Transmission Customer wishes this request to be a Coordinated Request associated with
a Coordinated Group, the Transmission Customer must submit the request with the
CG_STATUS data element set to “PROPOSED” in the transrequest OASIS Ttemplate.
Additional requirements on the handling of Coordinated Requests are specified in Business
Practice Standard WEQ-013-2.6.9.
013-2.6.5.1
Redirect on a Firm Basis
A Transmission Customer holding confirmed firm PTP rights may request the use of those
rights on alternate PORs and/or PODs on a firm basis by submission of a Redirect request to
the Transmission Provider as Seller. The following information must be submitted by the
Transmission Customer in the Redirect request via the transrequest OASIS Ttemplate.
….
CG_STATUS
If the Transmission Customer
wishes this request to be a
Coordinated Request associated
with a Coordinated Group, the
Transmission Customer must
submit the request with the
CG_STATUS data element set
to PROPOSED in the
Appendix 4 - Page 19 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
transrequest OASIS Ttemplate.
….
The impact of the Redirect transaction on the reservation(s) identified by RELATED_REF
shall be posted and viewable using the reduction OASIS Ttemplate.
OASIS or Transmission Provider procedures shall also apply any outstanding conditions that
may exist from the Parent CCO Reservation to the Redirect reservation, if applicable, (e.g.,
Number-of-Hours Criteria or System-Conditions Criteria) in accordance with Business
Practice Standards WEQ-001-21.5.2.2.1 and WEQ-013-2.6.1.4 and any outstanding
conditions shall be viewable using the cco OASIS Ttemplate.
If the Redirect is eligible for the conveyance of rollover/renewal rights, these rights shall be
communicated
through
the
rollover
OASIS
Ttemplate
Data
Elements
RENEWAL_DUE_TIME,
ROLLOVER_ELIGIBLE,
ROLLOVER_START_TIME,
ROLLOVER_STOP_TIME, and ROLLOVER_CAPACITY. Conveyance of rollover rights to
the Redirect request/reservation may have an impact on those rights held on the
RELATED_REF reservation. These impacts on the RELATED_REF reservation shall be
documented through an update to the rollover OASIS Ttemplate Data Elements
ROLLOVER_ELIGIBLE, ROLLOVER_START_TIME, ROLLOVER_STOP_TIME, and
ROLLOVER_CAPACITY associated with the RELATED_REF.
If the Transmission Customer does not wish a firm request to Redirect on a firm basis to be
evaluated for conveyance of rollover rights, the Transmission Customer must submit the
request with the ROLLOVER_WAIVED Data Element set to ‘Y’ in the transrequest OASIS
Ttemplate.
If the Transmission Customer wishes this request to be a Coordinated Request associated with
a Coordinated Group, the Transmission Customer must submit the request with the
CG_STATUS data element set to “PROPOSED” in the transrequest OASIS Ttemplate.
Additional requirements on the handling of Coordinated Requests are specified in Business
Practice Standard WEQ-013-2.6.9.
013-2.6.5.2
Redirect on a Non-Firm Basis
A Transmission Customer holding confirmed firm PTP rights may request the use of those
rights on alternate PORs and/or PODs on a non-firm basis by submission of a Redirect request
to the Transmission Provider as Seller. The following information must be submitted by the
Transmission Customer in the Redirect request via the transrequest OASIS Ttemplate.
….
The impact of the Redirect transaction on the reservation(s) identified by RELATED_REF shall
be posted and viewable using the reduction OASIS Ttemplate.
013-2.6.6
Relinquish Requests
Appendix 4 - Page 20 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
The Relinquish request is submitted in association with a Redirect on a non-firm basis to
indicate the Transmission Customer’s desire to return the capacity rights held on the Redirect
to the Parent Reservation specified in the RELATED_REF of that Redirect request. The
following are the specific requirements for the Relinquish request submitted via the
transrequest OASIS Ttemplate.
013-2.6.7.1
Resale on OASIS
Resale transactions conducted on OASIS shall adhere to the basic OASIS request
processing requirements where the Reseller is identified as the Seller and the Assignee
identified as the Transmission Customer.
The Assignee (Transmission Customer) initiates the Resale of scheduling rights by submitting
the following required information on OASIS via the transrequest OASIS Ttemplate. Data
Elements not listed are optional. There shall be no requirement imposed by OASIS that the
Reseller post any corresponding offer of Transmission Service for sale on that OASIS.
….
The impact of the Resale transaction on the reservation(s) identified by REASSIGNED_REF
shall be posted and viewable using the reduction OASIS Ttemplate.
OASIS or Transmission Provider procedures shall also apply any outstanding conditions that
may exist from the Reseller’s reservation to the Assignee’s reservation (e.g., Number-of-Hours
Criteria or System-Conditions Criteria) in accordance with Business Practice Standard WEQ013-2.6.1.4 and any outstanding conditions shall be viewable using the cco OASIS Ttemplate.
013-2.6.7.2
RESALE off OASIS
Resale transactions arranged between Reseller and Assignee off OASIS must be documented
on OASIS by the Reseller using the transassign OASIS Ttemplate. Transactions arranged off
OASIS do not follow the basic request processing steps and shall be posted directly as
confirmed transactions.
….
The impact of the Resale transaction on the reservation(s) identified by REASSIGNED_REF
shall be posted and viewable using the reduction OASIS Ttemplate.
OASIS or Transmission Provider procedures shall also apply any outstanding conditions that
may exist from the Reseller’s reservation to the Assignee’s reservation (e.g., Number-of-Hours
Criteria or System-Conditions Criteria) in accordance with Business Practice Standard WEQ013-2.6.1.4 and any outstanding conditions shall be viewable using the cco OASIS Ttemplate.
013-2.6.8.1
FULL_TRANSFER - Transfers of All Capacity
….
The Transmission Provider may post a FULL_TRANSFER request directly on OASIS on
Appendix 4 - Page 21 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
behalf of the original Transmission Customer and Assignee after confirming the transaction
with both parties using the transassign OASIS Ttemplate. The information required to be
posted shall be identical to that posted for FULL_TRANSFERs conducted on OASIS.
On confirmation of the FULL_TRANSFER, the IMPACTED attribute will be incremented for
each of the Reseller’s reservations referenced by the REASSIGNED_REF Data Elements and
the resulting impacts on each REASSIGNED_REF’s reserved capacity will be viewable with
the reduction OASIS Ttemplate. OASIS must also update all subordinate Resale, Redirect,
etc., transactions impacting the REASSIGNED_REF transaction(s) to reflect the transfer of
those obligations to the Assignee under the new FULL_TRANSFER reservation.
013-2.6.8.2
PART_TRANSFER - Transfer of Partial Capacity
….
On confirmation of the PART_TRANSFER, the IMPACTED attribute will be incremented for
each of the original Transmission Customer’s reservations referenced by the
REASSIGNED_REF Data Elements and the resulting impacts on each REASSIGNED_REF’s
reserved capacity will be viewable with the reduction OASIS Ttemplate.
013-2.6.9
Coordinated Requests
….
First, the Transmission Customer must submit each transmission request to be considered
as a Coordinated Request using the transrequest OASIS Ttemplate with the CG_STATUS
data element set to the value of PROPOSED. On successful submission, OASIS shall set
the CG_DEADLINE data element to QUEUE_TIME plus 24 hours which may be viewed
using the transstatus OASIS Ttemplate. This deadline timestamp reflects the time the
Transmission Customer has to submit all transmission requests for consideration to the
various Transmission Providers that service is to be coordinated on, and to identify those
requests as a Coordinated Group associated with each individual Coordinated Request. All
Coordinated Requests must be submitted with PRECONFIRMED set to YES.
The identity of each Coordinated Request that comprises the Coordinated Group is
submitted by the Transmission Customer via the cgupdate OASIS Ttemplate. One or more
Coordinated Requests may be specified in the cgupdate OASIS Ttemplate submission using
continuation records. Multiple submissions of the cgupdate OASIS Ttemplate may be made
on OASIS to successively add additional Coordinated Requests to the Coordinated Group.
Up to the CG_DEADLINE timestamp or when the Transmission Customer sets the
Coordinated Request CG_STATUS to ATTESTED, the Transmission Customer may add,
modify, or delete Coordinated Requests from the Coordinated Group. For a given
Coordinated Request on a given Transmission Provider, as identified by the OASIS assigned
ASSIGNMENT_REF data element, the Coordinated Group consists of all other Coordinated
Requests submitted to the same or other Transmission Provider’s within the 24 hour
submission deadline. That is, the Coordinated Group associated with a given Coordinated
Request will not include that Coordinated Request; submission of a record to the
Transmission Provider where the ASSIGNMENT_REF refers to the same request as the
CR_PRIMARY_PROVIDER_CODE and CR_ASSIGNMENT_REF data elements will be
Appendix 4 - Page 22 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
returned as an error.
The identification of the Coordinated Requests that comprise the Coordinated Group are
added to the group by specifying the request’s CR_DISPOSITION with a value of PENDING.
A request that has already been added to the Coordinated Group by mistake or that is
withdrawn from consideration as a Coordinated Request prior to the CG_DEADLINE may be
deleted from the group by submitting the cgupdate OASIS Ttemplate with the
CR_PRIMARY_PROVIDER_CODE and CR_ASSIGNMENT_REF set to refer to the
Coordinated Request to be deleted and specifying CR_DISPOSITION with the value of
DELETED.
To meet the contiguity requirements for a Coordinated Group, existing reservations may be
associated with the Coordinated Group by specifying the CR_DISPOSITION of CONFIRMED
on submission of the reservation’s identification via the cgupdate OASIS Ttemplate.
Once all Coordinated Requests are submitted to their respective Transmission Provider’s
OASIS nodes, and each Coordinated Request has their associated Coordinated Group
information set in OASIS, the Transmission Customer must set each Coordinated Request’s
CG_STATUS to ATTESTED using the transcust OASIS Ttemplate. This action must be
performed prior to expiration of the CG_DEADLINE, and indicates that the Transmission
Customer has attested that the Coordinated Group meets the contiguity requirements specified
in Business Practice Standard WEQ-001-23.2.1.
013-3 SPECIFIC OASIS TEMPLATE IMPLEMENTATION
013-3.1
013-3.2
REGISTERED OASIS TEMPLATE DATA ELEMENTS
scheduledetail
The scheduledetail OASIS Ttemplate shall be used to query specific information posted by
the Transmission Provider related to the scheduled usage of reserved Transmission Service.
….
SECURITY_REF
Optional; If the reliability adjustment was
the result of a security event that is posted
on OASIS via the security OASIS
Ttemplate, this shall be set to the OASIS
unique identifier assigned to that posting
INITIATING_PARTY
Optional; If the reliability adjustment was
the result of a security event that is posted
on OASIS via the security OASIS
Ttemplate, these Data Elements will be
reported as they appear in that associated
security event posting
RESPONSIBLE_PARTY
PROCEDURE_NAME
PROCEDURE_LEVEL
FACILITY_LOCATION
FACILITY_NAME
FACILITY_CLASS
FACILITY_LIMIT_TYPE
Appendix 4 - Page 23 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
ANNOTATION
013-3.3
systemdata
The systemdata OASIS Ttemplate is designed to present time series data in an efficient form.
It is an extensible template as the Data Elements SYSTEM_ELEMENT_TYPE and
SYSTEM_ATTRIBUTE may take on Transmission Provider specific registered values for
posting of data that is not already defined in the OASIS Data Dictionary.
013-3.3.1
ATC Related Query/Response Requirements
….
Posting of ATC component data and narratives via the systemdata OASIS Ttemplate shall
comply with all applicable regulations and Business Practices.
The following are the systemdata OASIS Ttemplate Data Element requirements for providing
ATC component data, i.e., TTC, CBM, FTRM, NFTRM, FATC or NFATC, FGF, or NFGF to the
user:
….
The following are the systemdata OASIS Ttemplate Data Element requirements for providing
a brief, but specific, narrative explanation of the reason for a change in the monthly or yearly
firm or non-firm ATC value on a constrained Posted Path when the monthly or yearly ATC
value changes as a result of a 10 percent or greater change in the related posted TTC or TFC.
….
The following are the systemdata OASIS Ttemplate Data Element requirements for providing
a brief, but specific, narrative associated with yearly or monthly ATC values when either the
posted firm or non-firm ATC remains unchanged at a value of zero (0) for six (6) months or
longer.
013-3.3.2
System Load Related Query/Response Requirements
….
The following table shows an example of the systemdata OASIS Ttemplate Data Element
usage for providing information on load related data:
013-3.4
security
The security OASIS Ttemplate is used to provide information related to changes in the
transmission system that may impact reliability. The bulk of the Data Elements that comprise
this template are identified as free-form text in the OASIS Data Dictionary to provide
Transmission Providers with flexibility in posting different types of information in a structured
fashion compatible with their operations and Business Practices. .Usage of the Data Elements
within the security OASIS Ttemplate for providing information that may be made available by
Appendix 4 - Page 24 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
the Transmission Provider are provided as examples only.
013-3.4.1
Outage Query/Response Requirements
The following is an example of the suggested usage of the security OASIS Ttemplate Data
Elements for providing information related to Transmission Provider posting of outages. Note
that posting of transmission related outages on OASIS is at the discretion of the Transmission
Provider.
013-3.4.2
Curtailment Event Query/Response Requirements
The following is an example of the suggested usage of the security OASIS Ttemplate Data
Elements for providing information related to Transmission Provider posting of system
conditions that may result in the Curtailment or interruption of Transmission Service. The
example shown illustrates the data provided for a NERC TLR related event. Note that the
actual Curtailment or impact of these events on schedules or Transmission Service
reservations will be posted on OASIS and made available via the scheduledetail or reduction
OASIS Ttemplates.
013-3.5
transoffering
The transoffering OASIS Ttemplate allows the Transmission Customer to selectively query
for Transmission Service offers posted by both the Transmission Provider and Resellers.
Resellers control how their offerings are presented to the Transmission Customer through
the specification of an OFFER_INCREMENT. Transmission Provider postings shall always
have OFFER_INCREMENT set equal to SERVICE_INCREMENT.
Transmission Service rights sold by the Reseller must correspond with the original rights
acquired from the Transmission Provider.
There is, however, no restriction on the
term/increment of service that may be resold. The OFFER_INCREMENT Data Element
controls when a Resellers capacity posted for Resale will be presented to the Transmission
Customer via the transoffering OASIS Ttemplate.
….
When queried by the Customer with a specified SERVICE_INCREMENT query parameter,
OASIS shall return in the transoffering OASIS Template response all posted offers where
SERVICE_INCREMENT or OFFER_INCREMENT matches any of the specified
SERVICE_INCREMENT query values.
013-3.6
transpost/transupdate
The transpost/transupdate OASIS Ttemplates allows a Transmission Customer (Reseller)
to post or modify an offer to resell their reserved capacity on OASIS in a manner comparable
to the offerings posted by the Transmission Provider. The service offered for Resale is
dictated by the service held by the Transmission customer as defined in the
SERVICE_INCREMENT, TS_CLASS, TS_TYPE, TS_PERIOD, TS_WINDOW, and
TS_SUBCLASS Data Elements. However, the Transmission Customer may offer that
service in any arbitrary increment of whole hours from hourly, to daily, to monthly, etc.
Appendix 4 - Page 25 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
The OFFER_INCREMENT Data Element controls when the Reseller’s Transmission Service
offering will be returned to a user submitting the transoffering OASIS Ttemplate. For
example, to post MONTHLY FIRM service reserved from the Transmission Provider as an
HOURLY offering, the SERVICE_INCREMENT Data Element will be MONTHLY to
correspond to the reserved service being resold and the OFFER_INCREMENT would be
submitted as HOURLY. When queried by a user with SERVICE_INCREMENT=HOURLY,
the transoffering OASIS Ttemplate would return all qualifying posted offerings from the
Transmission Provider where SERVICE_INCREMENT=HOURLY and any resale offerings
posted by Resellers where the OFFER_INCREMENT=HOURLY. To post that monthly
capacity on a daily basis, the Reseller would submit another Transmission Service offering
specifying the OFFER_INCREMENT=DAILY.
The following table shows the specific
transpost/transupdate OASIS Ttemplates:
013-3.7
template
Data
Element
usage
for
the
transstatus
The transstatus OASIS Ttemplate provides the Transmission Customer with a view of
transactions submitted on OASIS. OASIS shall be responsible for merging any transaction
profile data submitted by the Transmission Customer (START_TIME, STOP_TIME,
CAPACITY_REQUESTED, and BID_PRICE) or the Seller (START_TIME, STOP_TIME,
CAPACITY_GRANTED, and OFFER_PRICE) into a single set of time profile data records
consisting of START_TIME, STOP_TIME, CAPACITY_REQUESTED, BID_PRICE,
CAPACITY_GRANTED, OFFER_PRICE, and CEILING_PRICE to be returned in the
transstatus OASIS Ttemplate response.
013-3.8
reduction
The reduction OASIS Ttemplate provides the Transmission Customer with a view of
transactions or Transmission Provider actions which impact either the capacity available on a
given Transmission Service reservation or the service Curtailment priority in effect for the
reservation. Capacity impacts are due to transactions such as Redirects, Resales,
Transfers, recalls, etc.; Curtailment priority impacts are due to criteria established in granting
long-term firm service where firm Curtailment priority cannot be granted for all periods or
under certain specific operating conditions as specified in the Transmission Customer’s
service agreement.
For a given Transmission Service request, there may never be two reduction OASIS
Ttemplate response records that overlap in time. For any given interval in time, all transactions
or Transmission Provider actions that impact the Transmission Service request over that
interval shall be returned in one or more continuation records.
….
If the Transmission Provider uses a Transmission Provider specific registered value for
REDUCTION_TYPE, the registered value and a full description of how the value is used and
the information returned in the reduction OASIS Ttemplate response must be posted on the
Transmission Provider’s OASIS Home Page.
Appendix 4 - Page 26 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
An example of the reduction OASIS Ttemplate response is provided in Business Practice
Standard WEQ-013-C Example 8.
Example 4 - Example of Aggregating Purchased Services for Resale using Reassignment
The following examples do not show the complete OASIS Ttemplate information, but only
show the values assigned to those Data Elements in the OASIS Ttemplate that are important
to the example.
a. Transmission Customer #1, "BestE" requests the purchase of 20 MW DAILY FIRM PTP
for May 7th and 8th for $1.00/MWday from Transmission Provider AAA (transrequest
OASIS Template).
TEMPLATE=transrequest
CUSTOMER_CODE=BestE (Implied by the registered entity submitting the OASIS Ttemplate)
….
b. Transmission Customer #1 purchases an additional 70 MW of DAILY FIRM PTP on the
same path for May 8th for $1.05/MWday (transrequest OASIS Template).
TEMPLATE=transrequest
CUSTOMER_CODE=BestE (Implied by the registered entity submitting the OASIS Ttemplate)
….
c. Transmission Customer #1 becomes Reseller #1 and posts an offer of Transmission
Service of 50 MW of their DAILY FIRM PTP rights purchased above for Resale on an
Hourly basis on May 8th from 7 a.m. to 11 p.m. at $.90/MW-hour.
TEMPLATE=transpost
SELLER_CODE=BestE (Implied by the registered entity submitting the OASIS Ttemplate)
….
d. Transmission Customer #2 “Whlsle” then requests purchase of 35 MW firm from Reseller
#1 from 8 a.m. to 5 p.m. for $0.90/MW-hour (transrequest OASIS Template).
TEMPLATE=transrequest
CUSTOMER_CODE=Whlsle
SELLER_CODE=BestE (Implied by the registered entity submitting the OASIS Ttemplate)
….
e. Seller (Reseller #1) informs the Transmission Provider of the reassignment of the
previous Transmission Service rights when the Seller accepts the Transmission
Customer purchase request (transsell OASIS Template).
TEMPLATE=transsell
Appendix 4 - Page 27 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
SELLER_CODE=BestE (Implied by the registered entity submitting the OASIS Ttemplate)
Example 5 - File Examples of the Use of Continuation Records
a. Basic Continuation Records
The first example of the use of Continuation Records is for the transrequest OASIS Ttemplate
submitted by a Transmission Customer, “MOP” for purchase of a Transmission Service
reservation spanning 16 hours from 06:00 to 22:00 with "ramped" demand at beginning and
end of time period. Two additional reservation requests are also submitted in this request prior
to and following the profile to demonstrate the handling of ASSIGNMENT_REF by the OASIS
Node. The last request is for a purchase from a Reseller, “EFG”.
….
b. Submission of Reassignment Information - Case 1:
In the prior example (last Data Record in transrequest OASIS Template) a Resale reservation
request was submitted to the Reseller “EFG” by the Transmission Customer for 20MW of
DAILY FIRM PTP scheduling rights from 04:00 to 16:00. Assume that the Reseller has
previously reserved service for the CEF-ECS path for DAILY FIRM PTP in amount of 50 MW
on 4/23 under ASSIGNMENT_REF=23877019, and another 10 MW on April 23, 2007, under
ASSIGNMENT_REF=23877880. Reseller must designate which Transmission Service rights
are to be reassigned to Transmission Customer to satisfy the 20MW from 04:00 to 16:00. This
reassignment information is conveyed by Reseller using the transsell OASIS Ttemplate when
the reservation request is accepted. At the Seller's discretion, rights are assigned for the first
four hours of the Resale from the first reservation (ASSIGNMENT_REF=23877019). The
balance of the Resale is supported by 10 MWs from the second reservation first
(ASSIGNMENT_REF=23877880) with the balance taken up by the first reservation
(ASSIGNMENT_REF=23877019). This split of reassignment information is conveyed in
"continuation"
records via the transsell
OASIS Ttemplate Data Elements
REASSIGNED_REF,
REASSIGNED_CAPACITY,
REASSIGNED_START_TIME,
and
REASSIGNED_STOP_TIME.
….
c. Submission of Reassignment Information - Case 2:
If the Resale transaction from the previous example were conducted off-OASIS, the Seller,
“EFG”, would use the transassign OASIS Ttemplate to post the transaction to OASIS.
….
d. Query of Transmission Service Reservation Status:
The following is a hypothetical response to a transstatus OASIS Template query that might be
delivered for reservations starting on April 23, 2007.
Example 6 - Examples of Negotiation of Price and Partial Service Offer
Appendix 4 - Page 28 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
Example 6a - Negotiation with Preconfirmation
a. The Transmission Customer submits a preconfirmed Transmission Service request using
the transrequest OASIS Ttemplate. Initially, the STATUS is set to QUEUED by the
OASIS Node.
b. The Seller has the option of setting STATUS via the transsell OASIS Ttemplate to one of
the
following:
INVALID,
RECEIVED,
STUDY,
COUNTEROFFER,
CR_COUNTEROFFER, ACCEPTED, CR_ACCEPTED, DECLINED, or REFUSED.
c. The Seller has the option of entering a CAPACITY_GRANTED and setting the STATUS
to COUNTEROFFER or CR_COUNTEROFFER via the transell OASIS Ttemplate if the
Seller can only provide Partial Service.
d. If the Seller sets STATUS to ACCEPTED or CR_ACCEPTED (and, as required by
Business Practice Standard WEQ-013-2.2, the OASIS Node forces the Seller to set
OFFER_PRICE equal to BID_PRICE as a condition to setting STATUS to ACCEPTED or
CR_ACCEPTED) and CAPACITY_GRANTED is equal to CAPACITY_REQUESTED, the
OASIS Node will immediately set STATUS to CONFIRMED, except where the STATUS
is CR_ACCEPTED the OASIS Node shall wait to set the transaction’s STATUS to
CONFIRMED. (Business Practice Standard WEQ-013-2.2 requires the OASIS Node to
set a null CAPACITY_GRANTED equal to CAPACITY_REQUESTED when STATUS is
set to ACCEPTED or CR_ACCEPTED.)
e. The Transmission Customer may withdraw request via transcust OASIS Ttemplate at
any time up to point where the Seller sets STATUS to ACCEPTED or CR_ACCEPTED.
f.
Once the STATUS is CONFIRMED, the OFFER_PRICE and CAPACITY_GRANTED
officially becomes the terms of the reservation.
Example 6b - Negotiations without Preconfirmation
a. The Transmission Customer submits a Transmission Service reservation request with the
BID_PRICE less than the CEILING_PRICE via the transrequest OASIS Ttemplate.
Initially the STATUS is set to QUEUED by the OASIS Node.
b. The Seller has the option of setting the STATUS via the transsell OASIS Ttemplate to
one of the following: INVALID, RECEIVED, STUDY, ACCEPTED, DECLINED,
COUNTEROFFER, or REFUSED. If the STATUS is set to INVALID (due to invalid entries
in the request), DECLINED (due to the Seller determining that the proposed price is not
acceptable and further negotiations are not desired), or REFUSED (due to the
unavailability of the requested service), the Transmission Service reservation request is
terminated.
c. The Seller has the option of entering a CAPACITY_GRANTED and setting the STATUS
to COUNTEROFFER via the transell OASIS Ttemplate if the Seller can only provide
Partial Service.
Appendix 4 - Page 29 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
d. If the Seller set the STATUS to RECEIVED or STUDY, and determines that the
BID_PRICE is too low, the Seller sets the OFFER_PRICE to the price desired, and sets
the STATUS to COUNTEROFFER via the transsell OASIS Ttemplate.
e. The Transmission Customer agrees to the OFFER_PRICE, sets the BID_PRICE equal to
the OFFER_PRICE, and sets the STATUS to CONFIRMED via the transcust OASIS
Ttemplate.
f.
The OFFER_PRICE and CAPACITY_GRANTED with the STATUS of CONFIRMED
locks in the terms of the reservation.
Example 6c - Multiple Step Negotiations
a. The Transmission Customer submits a Transmission Service reservation request with the
BID_PRICE less than the CEILING_PRICE via the transrequest OASIS Ttemplate.
Initially the STATUS is set to QUEUED by the OASIS Node.
b. The Seller has the option of setting the STATUS via the transsell OASIS Ttemplate to
one of the following: INVALID, RECEIVED, STUDY, ACCEPTED, CR_ACCEPTED,
DECLINED, COUNTEROFFER, CR_COUNTEROFFER, or REFUSED. If the STATUS is
set to INVALID, DECLINED, or REFUSED, the Transmission Service reservation request
is terminated.
c. The Seller has the option of entering a CAPACITY_GRANTED and setting the STATUS
to COUNTEROFFER or CR_COUNTEROFFER via the transell OASIS Ttemplate if the
Seller can only provide Partial Service. If ATC changes before the request reaches the
STATUS of CONFIRMED, Seller may change the CAPACITY_GRANTED.
d. The Seller determines that the BID_PRICE is too low, sets the OFFER_PRICE to the
desired value, and sets the STATUS to COUNTEROFFER or CR_COUNTEROFFER via
the transsell OASIS Ttemplate.
e. The Transmission Customer responds to the new OFFER_PRICE with an updated
BID_PRICE and sets the STATUS to REBID for re-evaluation by the Seller.
f.
The Seller determines that the BID_PRICE now is acceptable, and sets the STATUS to
ACCEPTED or CR_ACCEPTED via the transsell OASIS Ttemplate. The transition to
ACCEPTED or CR_ACCEPTED state requires the OFFER_PRICE to be set to the
BID_PRICE: accepting a reservation with an OFFER_PRICE different from BID_PRICE
would require the STATUS be set to COUNTEROFFER or CR_COUNTEROFFER rather
than ACCEPTED or CR_ACCEPTED (see Business Practice Standard WEQ-0134.1.6.3.c).
g. The Transmission Customer agrees to the OFFER_PRICE and sets the STATUS to
CONFIRM via the transcust OASIS Ttemplate.
h. The OFFER_PRICE and CAPACITY_GRANTED with the STATUS as CONFIRMED
locks in the terms of the reservation.
Appendix 4 - Page 30 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
Example 6d - Negotiations Declined by Seller
a. The Transmission Customer submits a Transmission Service reservation request with the
BID_PRICE less than the CEILING_PRICE via the transrequest OASIS Ttemplate.
Initially the STATUS is set to QUEUED by the OASIS Node.
b. The Seller has the option of setting the STATUS via the transsell OASIS Ttemplate to
one of the following: INVALID, RECEIVED, STUDY, ACCEPTED, CR_ACCEPTED,
DECLINED, COUNTEROFFER, CR_COUNTEROFFER, or REFUSED. If the STATUS is
set to INVALID, DECLINED, or REFUSED, the Transmission Service reservation request
is terminated.
c. The Seller determines that the BID_PRICE is too low, sets OFFER_PRICE to his desired
value, and sets STATUS to COUNTEROFFER or CR_COUNTEROFFER via the
transsell OASIS Ttemplate.
d. The Transmission Customer responds to OFFER_PRICE with updated BID_PRICE and
sets the STATUS to REBID via the transcust OASIS Ttemplate for re-evaluation by
Seller.
e. The Seller breaks off all further negotiations by setting the STATUS to DECLINED,
indicating that the price is unacceptable and that he does not wish to continue
negotiations.
Example 6e - Negotiations Withdrawn by Transmission Customer
a. The Transmission Customer submits a Transmission Service reservation request with the
BID_PRICE less than the CEILING_PRICE via the transrequest OASIS Template.
Initially the STATUS is set to QUEUED by the OASIS Node.
b. The Seller has the option of setting the STATUS via the transsell OASIS Ttemplate to
one of the following: INVALID, RECEIVED, STUDY, ACCEPTED, CR_ACCEPTED,
DECLINED, COUNTEROFFER, CR_COUNTEROFFER, or REFUSED. If the STATUS is
set to INVALID, DECLINED, or REFUSED, the Transmission Service reservation request
is terminated.
c. The Seller has the option of entering a CAPACITY_GRANTED and setting the STATUS
to COUNTEROFFER or CR_COUNTEROFFER via the transell OASIS Ttemplate if the
Seller can only provide Partial Service.
d. The Seller determines that the BID_PRICE is too low, sets the OFFER_PRICE to his
desired value, and sets the STATUS to COUNTEROFFER or CR_COUNTEROFFER via
the transsell OASIS Ttemplate.
e. The Transmission Customer responds to the OFFER_PRICE with an updated
BID_PRICE and sets the STATUS to REBID for re-evaluation by Seller.
f.
The Seller determines that the BID_PRICE is still too low, sets the OFFER_PRICE to
Appendix 4 - Page 31 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
another value, and sets STATUS to COUNTEROFFER or CR_COUNTEROFFER via the
transsell OASIS Ttemplate.
g. The Transmission Customer breaks off all further negotiations, either because the
OFFER_PRICE or CAPACITY_GRANTED are unacceptable, by setting STATUS to
WITHDRAWN (or the Transmission Customer/Seller could go through additional
iterations of REBID/COUNTEROFFER/CR_COUNTEROFFER until negotiations are
broken off or the reservation is confirmed).
Example 6f - Negotiations Superseded by Higher Priority Reservation
a. The Transmission Customer submits a Transmission Service reservation request with the
BID_PRICE less than the CEILING_PRICE via the transrequest OASIS Ttemplate.
Initially the STATUS is set to QUEUED by the OASIS Node.
b. The Seller has the option of setting the STATUS via the transsell OASIS Ttemplate to
one of the following: INVALID, RECEIVED, STUDY, ACCEPTED, CR_ACCEPTED,
DECLINED, COUNTEROFFER, CR_COUNTEROFFER, or REFUSED. If the STATUS is
set to INVALID, DECLINED, or REFUSED, the Transmission Service reservation request
is terminated.
c. If the Seller determines that another reservation has higher priority and must displace this
request, he sets the STATUS of this request to SUPERSEDED and the negotiations are
terminated.
d.
However, if desired and permitted by the tariff, the Seller may set the STATUS of a
request in any of these previous states (including COUNTEROFFER, CR_COUNTEROFFER,
ACCEPTED, and CR_ACCEPTED) to COUNTEROFFER or CR_COUNTEROFFER with an
OFFER_PRICE which could avoid the request being superseded, thus allowing the
Transmission Customer the choice of being SUPERSEDED or accepting the proposed
OFFER_PRICE.
Example 7 - Audit OASIS Template Examples
The following examples are included to show the general type of audit report responses that
could be expected to be returned by implementations of the audit reporting OASIS Ttemplates
as documented above.
….
Example 7b – Reservations
….
First, this example shows the handling of continuation records which conveyed a time varying
demand of 50 MW on August 1, 2007, 75 MW on August 18, 2007, and 100 MW on August 19,
2007. This demand profile was initially entered with the original reservation request
(transrequest OASIS Ttemplate) at 12:15 on August 15, 2007, by Alan Trader.
Appendix 4 - Page 32 of 33
Appendix 4 – Minor Correction MC12036
Errata for NAESB Wholesale Electric Quadrant Business Practice Standards, Version 003
December 20, 2012
Example 8 - Reservation Reductions
The following is an example of the reduction OASIS Ttemplate response format for a
reservation, 123456, for one day of service at 50 MWs. Assume that 1) the Transmission
Customer has redirected 20 MWs for that day on reservation 987654, 2) resold 10 MWs during
the off-peak hours on reservation 345678, and 3) had service starting at 16:00 reduced in
priority for two hours.
5. Reason for of Minor Correction/Clarification:
To make consistency changes to the NAESB OASIS Business Practice
Standards.
Appendix 4 - Page 33 of 33
Appendix 5 – NAESB WEQ Executive Committee Meeting Minutes
Approving NAESB Wholesale Electric Quadrant Minor Corrections
December 20, 2012
Appendix 5 contains the meeting minutes of the NAESB Wholesale Electric Quadrant Executive Committee and the
action taken by the Wholesale Electric Quadrant Executive Committee to approve the following minor corrections:
Appendix No.
NAESB WEQ Executive Committee Meeting Minutes
Appendix 5
MC12032, MC12034, MC12035 and MC12036 as approved by the WEQ Executive
Committee on October 23, 2012.
Meeting Minutes: http://www.naesb.org/weq/weq_ec.asp
Appendix 5 – Page 1 of 1
Appendix 6 – Notice to WEQ Members of Executive Committee Adoption of Minor Corrections
December 20, 2012
Appendix 6 contains the correspondence sent to all Wholesale Electric Quadrant members notifying them of the
Executive Committee action taken on the minor corrections, requesting comments that opposed the minor
corrections, and informing them of future actions and timelines related to the minor corrections.
Appendix No.
Correspondence/Notice
Appendix 6
Minor Corrections MC12032, MC12034, MC12035 and MC12036 – Request for
Comments due November 12, 2012:
http://www.naesb.org/pdf4/weq_mc103012reqcom.doc
No Comments Received
Appendix 6 – Page 1 of 1
Appendix 7 – NAESB Operating Procedure for Minor Clarifications and Corrections to Standards
December 20, 2012
Appendix 7 contains the excerpt from the NAESB Operating Procedures detailing the procedures to be followed for
minor clarifications and corrections to existing NAESB WEQ Business Practice Standards.
Procedures for Minor Corrections as excerpted from the NAESB Operating Procedures
D. Minor Clarifications and Corrections to Standards
Minor clarifications and corrections to existing standards include: (a) clarifications or corrections made by a
regulatory agency to standards that are of a jurisdictional nature, or by the American National Standards Institute or
its successor; (b) clarifications or corrections to the format, appearance, or descriptions of standards in standards
documentation; (c) clarifications or corrections to add code values to tables; and (d) clarifications and corrections
that do not materially change a standard. Any request for a minor clarification or correction to an existing standard
should be submitted in writing to the executive director. This request shall include a description of the minor
clarification or correction and the reason the clarification or correction should be implemented.
1. Processing of Requests
The executive director shall promptly notify the EC and any appropriate subcommittee(s) of the receipt of the
request. The members of the applicable quadrant’s EC shall promptly determine whether the request meets the
definition of a minor clarification or correction. Through the decision of the vice chair of the applicable quadrant,
this determination may be delegated to one of the quadrant’s subcommittees, with the concurrence of the
subcommittee chair, in which case the subcommittee shall make a prompt decision.
If the request is determined to meet the definition of minor clarification or correction, the applicable quadrant’s EC,
with input from any subcommittee(s) to which the request has been forwarded, shall act on the request within one
month of its receipt. A meeting to discuss the request is not required; the decision may be made by notational vote.
A simple majority of the votes received shall determine the outcome. The members of the applicable quadrant’s EC
shall be given at least three working days to consider and vote on the request.
2. Public Notice
The results of the vote on the request for a minor clarification or correction shall be posted on the NAESB website
and the members of the applicable quadrant shall be notified of the request by e-mail. If the request has been
approved by the applicable quadrant’s EC, the notification shall include a brief description of the request, the contact
name and number of the requester so that further information can be obtained, and the proposed effective date of the
clarification or correction. Any interested party shall have an opportunity to comment on the request, and the
comments shall be posted on the NAESB website. The comment period is two weeks.
3. Final Disposition of Approved Requests
If no comments are received on an approved request, the standard shall be clarified or corrected as specified in the
approved request on the effective date proposed. If comments are received, they shall be forwarded to the members
of the applicable quadrant’s EC for consideration. Each comment requires a public written response from the
applicable quadrant’s EC. The applicable quadrant’s EC shall determine whether changes are necessary as a result of
the comments. Members of the applicable quadrant’s EC shall be given three working days to consider the
comments and determine the outcome, which shall be decided by a simple majority of the votes received. A meeting
to discuss the request is not required; the decision may be made by notational vote. The standard shall be clarified or
corrected in accordance with the outcome of the vote, effective with the completion of voting, and notice thereof
shall be posted on the NAESB website. In the case of minor corrections which are discovered during the editorial
Appendix 7 – Page 1 of 1
Appendix 7 – NAESB Operating Procedure for Minor Clarifications and Corrections to Standards
December 20, 2012
review process of publication of a new version and are categorized as clarifications under (b) or (c) above 2, the
proposed effective date may be (i) two weeks from the date of public notice, following simple majority approval by
the applicable Quadrant(s) EC(s) of the shortened effective date, or (ii) one month from the date of the public notice
For all others, the proposed effective date of the minor clarification or correction shall normally be one month from
the date of the public notice upon simple majority approval of the applicable Quadrant(s) EC(s).
2
Minor clarifications and corrections to existing standards include: (a) clarifications or corrections made by a regulatory agency
to standards that are of a jurisdictional nature, or by the American National Standards Institute or its successor; (b) clarifications
or corrections to the format, appearance, or descriptions of standards in standards documentation; (c) clarifications or corrections
to add code values to tables; and (d) clarifications and corrections that do not materially change a standard.
Appendix 7 – Page 2 of 1
| File Type | application/pdf |
| File Title | May 28, 2002 |
| Author | NAESB |
| File Modified | 2012-12-20 |
| File Created | 2012-12-20 |