W E S T E R N E L E C T R I C I T Y C O O R D I N A T I N G C OU N C I L

Merchant Alert Protocol

Andy Meyers Market Interface Committee Meeting

October 2015

2

W E S T E R N E L E C T R I C I T Y C O O R D I N A T I N G C OU N C I L

Merchant Alert Protocol

• Peak RC will be implementing new communication tool – Reliability Messaging Tool– RMT Replaces WECCNet

• Once RMT is functional, MAP process would cease to be effective unless a mechanism was found to share MAP messages from OASIS bulletin board with RMT

3

W E S T E R N E L E C T R I C I T Y C O O R D I N A T I N G C OU N C I L

Merchant Alert Protocol

• MIC members have been working collaboratively with Peak to seek a solution to ensure that MAP remains a functional regional tool

• Peak & MIC members have been in discussions with OATI to have an interface developed to share the MAP messages with RMT

4

W E S T E R N E L E C T R I C I T Y C O O R D I N A T I N G C OU N C I L

Merchant Alert Protocol

• Peak has been willing to pay for the development of the interface with OATI, however they do not have a contract with OATI for the OASIS application

• Unique contracting solution is currently being worked out to fund the work – As a TP, Idaho Power does have an OASIS contract

with OATI. IPCO requested the necessary changes– Through proposed contract solution Peak will be

invoiced for the work

5

W E S T E R N E L E C T R I C I T Y C O O R D I N A T I N G C OU N C I L

Merchant Alert Protocol

• RMT has been updated and is ready to receive MAP messages

• Development work needed for OASIS will begin once the contract and invoice process are completed.

• MIC plans to work with Peak on testing – Peak will test on their servers first– MIC would like to help test once code is released

to RMT Beta version

6

W E S T E R N E L E C T R I C I T Y C O O R D I N A T I N G C OU N C I L

Merchant Alert Protocol

• Peak has begun beta testing of RMT• RMT is tentatively scheduled to implement in

Q1 of 2016