1. Preemption-ROFR Notification
Concept for Incorporating a Template
March 2017

2. Preemption-ROFR Notification
The OASIS Subcommittee has discussed notifications for Preemption-ROFR and documented those discussions in 2014.
3/27/14 the consensus of the subcommittee would be to use the Dynamic Notification structures currently in the WEQ-002 standards for notification of the P&C process.
A redlined copy of all modifications made to the Customer Notifications document during the April 15-17, 2014 meeting is available at the following link:
March 2017

3. Preemption-ROFR Notification
In the current draft of the P&R standards:
The competition flags are set for all impacted requests and reservations when a valid P-R Process is started (x001-xx.4.4 INITIATION OF THE PREEMPTION-ROFR PROCESS)
The competition flags are reset at different times in the process for the Defender(s), resales and redirects of the Defender(s) and the Challenger
March 2017

4. Preemption-ROFR Notification
In 2014 we identified the following information to be communicated (dependent on the specific notification):
AREF of Challenger
Defender AREFS
challenger data
Challenger confirmation time limit
Matching request information (how to access)
Deadline for submitting matching request
Status change (SUPERSEDED, DISPLACED)
RECALL AREF
March 2017

5. Preemption-ROFR Notification
In 2014 we identified the following triggers for supplying a notification to the Challenger:
ROFR Challenger
Potential ROFR Challenger
Challenger Counteroffer (ROFR)
End of Competition – No longer a Challenger
March 2017

6. Preemption-ROFR Notification
In 2014 we identified the following triggers for supplying a notification to the Defender(s):
Defender (new single ROFR defender)
Defender (new multiple ROFR defenders)
End of competition (single ROFR defender)
End of competition (multiple ROFR defenders)
Defender – Request SUPERSEDED due to full capacity to Challenger
Defender – Reservation DISPLACED due to full capacity to Challenger
Defender - Reservation partially recalled due to full capacity to Challenger
Defender – Reservation subject to reduction – ROFR process underway
Defender – End of ROFR competition – no capacity taken
Defender - End of ROFR competition – capacity taken
March 2017

7. Preemption-ROFR Notification
Key Components of this proposal:
Establish an AREF for each P-R Process
Establish a preemption template similar to the CCO template to capture P-R Process information
Record specific information for reservations and requests that have competition flags set
March 2017

8. Preemption-ROFR Notification
preemption template data captured for Challenger:
Preemption AREF
Seller identification
P-R role: Challenger
P-R overall process status (Active or Completed)
P-R process status for the Challenger (Active or Completed)
Challenger Customer Code
Challenger AREF
Date and time the P-R Process was initiated
Date and Time the P-R Process was completed
March 2017

9. Preemption-ROFR Notification
preemption template data captured for a Defender:
Preemption AREF
Seller identification
P-R role: Defender
P-R overall process status (Active or Completed)
P-R process status for the Defender (Active or Completed)
Defender Customer Code
Defender AREF
Does the Defender have ROFR (Y,N)
When the Defender has ROFR
Matching Request AREF(includes both profiles)
Deadline for submitting a valid Matching Request
March 2017

10. Preemption-ROFR Notification
preemption template data captured for Resales and Redirects of a Defender:
Preemption AREF
Seller identification
P-R role: Dependent
P-R overall process status (Active or Completed)
P-R process status for the Dependent (on-Hold or Completed)
Dependent Customer Code
Dependent AREF
Defender Customer Code of the Dependent’s parent
Defender AREF of the Dependent’s parent
March 2017

11. Preemption-ROFR Notification
Various queries of the preemption template would be available
Query of the Preemption AREF would provide real-time information on all requests and reservations impacted by the a specific P-R Process
Query of specific Challenger, Defender or Dependent AREF would provide real-time information on the specific request or reservation
Query of all active P-R Processes would be available
Query of all completed P-R Processes would be available
Query of all P-R Processes would be available
March 2017

12. Preemption-ROFR Notification
Send notifications only when the P-R process status for the request or reservation is changed and include link to a preemption query
Status changes would be handled in the normal fashion because those changes would show the change and the reason
March 2017

13. Preemption-ROFR Notification
More detailed information is provided in additional work papers submitted to the OASIS Subcommittee
March 2017