Rev. 09-19-2014
FPL OASIS Business Practices
General Practices
FPL’s general OASIS business practices such as products offered, requirements for
submittal, qualifications for service, creditworthiness, etc. are contained within FPL’s
Open Access Transmission Tariff (OATT) posted on the OASIS website. Additional
practices are those specified within FERC’s Business Practice Standards for Open Access
Same-Time Information Systems (OASIS). Business practices that are not specifically
addressed within either FPL’s OATT or FERC’s Business Practice Standards for OASIS
are noted below or are posted separately within the OASIS Business Practices folder on
FPL’s OASIS site.
Revisions to FPL’s Business Practices
A message alerting all users of any proposed changes to the business practices listed
below will be posted on FPL’s OASIS home page for a two week period prior to
implementation of the change. The new business practice(s) will become effective at the
end of the two week period.
Application of Creditworthiness Standards
Transmission Customers who do not satisfy the criteria for creditworthiness set forth in
Attachment L to FPL's OATT pursuant to a credit review by FPL or have not provided
the financial assurances required by FPL in accordance with Attachment L are classified
as "Inactive" on OASIS and may not request Transmission Service through the OASIS.
Potential Transmission Customers whose creditworthiness has not been reviewed by FPL
also may not request Transmission Service through the OASIS. In the event a request for
Transmission Service on the FPL Transmission System cannot be made through the
OASIS, please contact FPL at TransmissionService@fpl.com and the matter will be
addressed during the next business day.
Specific Business Practices
1) FPL allows only a fixed day for daily requests, i.e., clock hour midnight to clock
hour midnight. This business practice also applies to requests to
designate/undesignated a Network Resource.
2) FPL allows a sliding week for weekly requests, e.g., a reservation can run from
Friday to Friday or Monday to Monday. This business practice also applies to
requests to designate/undesignated a Network Resource.
3) FPL allows only a fixed month for monthly requests, e.g., January 1 to January
31st. This business practice also applies to requests to designate/undesignated a
Network Resource.
4) On Fridays, FPL allows the submittal of requests for hourly service for Saturday,
Sunday and Monday. If the following Monday is a holiday, requests for the
following Tuesday may also be submitted. Requests for hourly service submitted
on a day preceding a holiday, or a day when a holiday is observed may also
include the day of the holiday (or day of observance) and the following day.
Example: If July 4th falls on a Wednesday, requests submitted on Tuesday may
include service for both Wednesday and Thursday. If a holiday falls on a
Rev. 09-19-2014
Saturday, the holiday will be observed on the previous business day and if the
holiday falls on a Sunday, the holiday will be observed on the following business
day. With respect to this Business Practice, holidays are: New Year's Day, Martin
Luther King's Birthday, Memorial Day, July 4th, Labor Day, Thanksgiving Day,
the Friday after Thanksgiving Day, Christmas Eve and Christmas Day. This
business practice also applies to requests to designate/undesignated a Network
Resource.
5) FPL generally adheres to the timing requirements of NAESB WEQ 001-4.13 with
the following adjustments. For hourly transactions FPL allows an eight minute
customer response time before unconfirmed requests are retracted. For day ahead
hourly requests the customer response time is 30 minutes. FPL defines a day
ahead request as one that is submitted 10 or more hours earlier than the
transaction start time.
6) FPL accepts Daily Firm transmission service requests only if the start and stop
time of the request are within the Daily posting window of 60 days. Similarly,
FPL accepts Weekly Firm transmission service requests only if the start and stop
time of the request are within the Weekly posting window of 10 weeks.
7) FPL accepts OASIS transmission service requests based on conditions at the time
of the request. If conditions change, new ATC will be posted. If ATC becomes
available that could be used for transmission service that was previously refused,
FPL does not re-offer such available ATC. It is the customer’s responsibility to
monitor the OASIS and submit a new request if the previously refused
transmission service is still desired.
8) FPL processes most Transmission Service Requests (TSRs) automatically, as
outlined in section 9, using the OATI webTrans system. The following actions
will be taken by the system in accordance with NAESB WEQ 013-2.2:
a. The TSR will be set to INVALID if the system identifies an invalid field
in the request, such as improper POR, POD, Source, Sink, etc.
b. The TSR will be set to REFUSED in the event that the service request has
been denied due to lack of ATC.
c. The TSR will be set to ACCEPTED to indicate the service request at the
designated price and capacity has been approved/accepted.
d. The TSR may be automatically set to other states such as SUPERSEDED,
DISPLACED, etc. to indicate competition procedures as outlined in
NAESB WEQ 013-2.4 and NAESB WEQ 001-4.14 through 001-4.27
9) FPL automatically processes all Non-Firm TSRs and Hourly Network Secondary
Service Requests (as outlined in the Operating Procedures for Network Secondary
Service). Weekly and Monthly Network Priority Secondary Service Requests
along with all Network Resource Requests will be processed manually to allow
for receipt and review of attestation. Daily and Weekly Firm requests are
automatically processed while all Monthly and Yearly Firm requests are evaluated
manually.
Rev. 09-19-2014
10) FPL adheres to the negotiation requirements of NAESB WEQ 001-4.14 through
4.27 when dealing with competing bids for constrained resources. Additionally, in
order to allow for proper processing FPL will allow for new requests to compete
for constrained resources if they meet the following conditions:
a. New requests will compete only if the competition will result in granting
the full capacity requested.
b. New requests will compete only if all lower priority requests to whom
Right of First Refusal must be extended (as per NAESB WEQ 001 Table
4-3) can be accommodated.
c. New requests will compete only if submitted prior to the following
deadlines before the start of the transaction, to allow for sufficient
processing time.
i. All Non-Firm and Secondary Network Service requests shall have
a deadline equal to the greater of, 2 hours or, the sum of the
Provider Evaluation Time Limit and the Customer Confirmation
Time Limit (NAESB WEQ 001 Table 4-2) rounded upwards to the
nearest hour or day, if greater than 24 hours.
ii. All Firm requests shall have a deadline equal to the greatest
allowed Customer Confirmation Time Limit in NAESB WEQ 001
Table 4-2.
Table 1. TSR Timing Requirements.
Service
Hour Non-Firm
Day Non-Firm
Week Non-Firm
Month Non-Firm
Hour Secondary
Week Secondary
Month Secondary
Day Firm
Week Firm
Month Firm
Year Firm
Day Network Resource
Week Network
Resource
Month Network
Resource
1
Maximum TSR
Lead Time
12:00 PM Day
Prior
2 Days
2 Weeks
2 Months
10:30 AM Day
Prior2
2 Weeks
2 Months
60 Days
10 Weeks
N/A
N/A
60 Days
10 Weeks
N/A
TSR Submission
Deadline
Competition Lead
Time
Automatic
Processing
20 Min
2 Hours
Yes
1 Hour
1 Hour
1 Hour
3 Hours
2 Days
3 Days
Yes
Yes
Yes
20 Min
2 Hours
Yes
1 Hour1
7 Days1
1 Hour
1 Hour
7 Days
60 Days
1 Hour1
2 Days
3 Days
1 Day
2 Days
4 Days
N/A
1 Day
No
No
Yes
Yes
No
No
No
1 Hour1
2 Days
No
7 Days1
4 Days
No
Requests will be processed following the receipt and review of attestation during Business Hours. Business
Hour are Monday-Friday, between 8:00 AM – 4:00 PM, excluding holidays.
2
TSRs may be submitted starting at midnight the day before the transaction is to start, however TSRs will
be evaluated at 10:30 AM.
Rev. 09-19-2014
11) In the event that FPL is required to offer Rights of First Refusal (ROFR), FPL
will automatically submit, to the customer being offered ROFR, a transaction in
the COUNTEROFFER state, with type MATCHING.
a. All MATCHING requests will be submitted with the same Transmission
Service as the higher priority request.
b. All MATCHING requests will be submitted extending the lower priority’s
end date to match the required duration.
c. All MATCHING requests will be submitted with additional capacity equal
to the amount conflicting with the higher priority request.
d. All MATCHING requests that are allowed to expire, or are withdrawn,
indicate to FPL that the customer is declining its ROFR.
12) Transactions that cannot compete or do not meet requirements for competition are
evaluated as normal and shall be counteroffered/refused depending on ATC
availability.
13) When requesting firm transmission service from FPL, the transmission customer
generally may request a control area to control area transfer provided that the
generating resources involved do not materially change system flows so as to
materially reduce transmission capability. Where transmission capability might
be materially reduced, FPL may need more detailed information about the
proposed transaction and the specific sources and sinks involved in order to
accurately model the request. The transmission customer will supply requested
information as necessary to complete the application under the terms of FPL’s
OATT. This business practice pertains to FPL’s requirement for a complete
transmission service request and does not address any regulatory requirements for
designation/un-designation of network resources.
14) FPL has specific business practices that govern the submittal and processing of
Network Secondary Service Requests. These business practices are posted
separately under FPL’s OASIS Business Practices folder on OASIS. Other
specific practices associated with Network Integration Transmission Service are
also posted in that folder Network Customer Guide.
15) Following the declaration of an Energy Emergency Alert Level 3, the entity that is
requesting ATC for reliability purposes shall submit an EMERGENCY–NONFIRM request. The Reliability Coordinator shall evaluate the request based on
real-time system conditions, and grant authority to the System Operator to
approve the request.
16) All OASIS requests to designate or undesignated Network Resources must be
supported by the required attestation on the Designation of Network Resource
(DNR) Application Form. All OASIS requests for Network Priority Secondary
service must contain an attestation that the resource meets the requirement as a
Network Resource in the customer comments field of the OASIS reservation.
17) All requests to designated Network Resources shall follow the same submission
and competition timing requirements as Firm Point-to-Point Transmission Service
Requests as outlined in Table 1.
Rev. 09-19-2014
18) Section 13.8 of FPL’s OATT provides that FPL customers must submit schedules
for their Firm Point-to-Point Transmission Service no later than 10:00 AM the
day prior to the commencement of the service. Schedules submitted after the
10:00 AM deadline will preempt confirmed lower priority reservations provided
the request is submitted at least two hours prior to the scheduled start time.
19) Sections 17.4 and 29.2 of FPL’s OATT provide that FPL will attempt to remedy
minor deficiencies in the Application (for Transmission Service) through informal
communications with the Transmission Customer. In such cases, it is FPL’s
practice to provide the customer specific notice of any deficiency and provide 15
calendar days to remedy such deficiencies, after which time the reservation
request, if still deficient, will be terminated (changed to INVALID state on
OASIS).
20) Third parties that desire to post an offer of congestion relief may do so by posting
such an offer in the Category “Other” under the Notices tab on the FPL OASIS.
21) Any requests for Interconnection Service for Photo Voltaic (PV) or other
generating facilities utilizing Inverter based technologies, including those greater
than 10kW processed under the Small Generation Interconnection Agreement
(SGIA) procedures and those over 20 MW which will be processed under the
Large Generation Interconnection Agreement (LGIA) procedures, must complete
the Application for a Certified Inverter-Based Small Generating Facility form
(Attachment 5 to Attachment N of the OATT) and submit it with the SGIA or
LGIA Application.
22) FPL does not grant waivers for NERC Reliability Standard VAR-001 to
generating units connected to FPL's bulk power system.
23) FERC Order No. 693 requires all generators to ride through the same set of
Reliability Standard TPL-002 Category B and C contingencies as required for
wind generators in FERC Order No. 661, or for the Planning
Authority/Transmission Planner to simulate those generators that cannot ride thru
as tripping (Paragraph 1797 (3) of Order 693).
a. An Interconnection Customer (FPL or other entity) pursuant to the
OATT of FPL as Planning Authority/Transmission Planner may on an
interim basis request that an inverter based Generating Facility (up to
25 MW) be modeled as tripping for fault conditions (inability to ridethrough faults) in FPL's planning and operational contingency analysis
models for reasons beyond the Interconnection Customer's specific
control (e.g., lack of current equipment capability).
b. In evaluating this request FPL will consider the specific impacts that
the loss of the Generating Facility may have on FPL’s Transmission
System and FPL’s ability to simulate such contingencies. In the event
a temporary waiver is granted FPL will require a specific schedule
from the Interconnection Customer as to when such capability will be
available, and the installation in-service date. FPL will not grant a
permanent waiver of this requirement and the Interconnection
Rev. 09-19-2014
Customer must use due diligence to have the manufacturer provide the
equipment to meet this requirement as soon as reasonably practicable.