1. Michelle Mizumori Director of Reliability Coordination
Reliability Messaging Tool
ISAS
January 30, 2014
Michelle Mizumori Director of Reliability Coordination

2. Introduction Messaging Tool Name: What is this project all about?
Reliability Messaging Tool (RMT) or RMT
What is this project all about?
A single source messaging tool for real time operations;
Accessing variety of other useful information on PEAKRC.ORG
Support of NERC communication standards : 3-way handshake
Logging suitable for audit purposes
The WECC Reliability Coordinator Function or RCCo, soon to be known as Peak Reliability

3. High Level Requirements
RMT will be a Web application in PEAKRC.ORG.
Two-Factor authentication will be implemented for Internet. Simple Username/Password authentication will be for private WISP WAN.
System Access will be authorized by the Entity’s Site Administrator using PEAKRC.ORG tool.
Internet Explorer version 7.0 or higher is required.
Messages on WECCNET Outlook remains for a period of time and will not converted to RMT.
Bullet 2: User authentication is not firm yet

4. High Level Requirements
The current OATI messages (WIT, WEBSAS, MERCHANT ALERT) will be delivered and disseminate to the appropriate parties.
The Web site dashboard will be consists of ‘Incoming’ and ‘Outgoing’ message section.
All outgoing messages will also be in ‘Incoming’ section for your confirmation.
Users will be allowed to create all message types.
Users will be allowed to forward or reply to the sender of any message, including reply-to-all.
Bullet 10: WAV Alarm web part is source of the EMS data

5. High Level Requirements
Users will be able to subscribe alerts/alarms from RMT. To unsubscribe, Entity’s Site Administrator privilege is required.
Users will be able to create distribution lists from available member lists.
Users will be able to to the system defined distribution lists.
Users will be able to create message template.
Users will be able to create pre-defined text.
Users will be able to acknowledge a message if acknowledgment is required.
Users will be able to acknowledge all messages.
Bullet 12: User must register with WECCRC.ORG to get the
Bullet 15: For sender, no acknowledgment is required.
Bullet 17: for example, DCS event

6. High Level Requirements
Users will be able to set up auto acknowledgement. For some conditions, Peak RC can overrule auto acknowledgement & requires manual acknowledgement
Unread/Not-acknowledged messages will be bolded and highlighted.
Search messages allowed.
Support of Multi-Session on One Browser: One tab for incoming view and another tab for outgoing view.
Reduce Clicks : Display all information on the same screen by popping up windows. No redirection to another window if not necessary.

7. Data Retention
Messages will be archived for 7 years according to the Peak RC Record Retention policies.
Messages will be retrievable via the Search page in the system for up to 3 years less than the current date.
Requests to retrieve messages after 3 years will need to be made to the Peak RC.

8. What Messages will be available
Informational
Energy Emergency Alert
ICCP Outage
Local Transmission Emergency
Local System Emergency
Interchange Authority Emergency
Termination of Interchange Authority Emergency
Geo Magnetic Disturbance
More message types as needed

9. Application Mock-up

10. Tasks in Progress High level requirements being finalized;
Detail level requirements in progress;

11. Tentative Schedule 1st Quarter – System Development in progress
2nd Quarter – System Deployment / System available for UAT
Release – TBD expected early 2015
WECCNET will be available until the end of 2014(?)