1. JESS May 7-8, 2013

2. JESS Action Items Review

3. e-Tag 1.8.1.1 Test Plan Test URLs Test Dates Set Roll-Over Date –June 3-4 00:00 CDT

4. e-Tag Interoperability Query Periodic Tests Facilitated Ad-Hoc Tests

5. e-Tag 1.8.2 Executive Committee Meeting Schema R13080 Market Operator Role Reliability Limit Profile Management Informal Discussion on INT-004-WECC- RBP-2

6. e-Tag 1.8.2 Executive Committee Meeting Schema – need to always post

7. e-Tag 1.8.2 R13080 Market Operator Role –Allow Registered MOs to be shown as: GPE position – first PSE is market path TSP LSE position – last PSE in market path –Consider terminology in specification separate from functional model

8. e-Tag 1.8.2 Reliability Limit Profile Management –Consider old proposal (5 years ago?) –Consider new service Informal Discussion on INT-004-WECC- RBP-2

9. e-Tag 1.8.2 Reliability Limit Profiles 5 Years Ago –Each physical segment has profile –Only adjustment requests from segment’s reliability entities –All services have to manage multiple profiles

10. e-Tag 1.8.2 Reliability Limit Profile Management Service Tag Agent Tag Approval Tag Authority Tag Reliability Profile Manager Maintains all submitted adjustments Composite profile

11. EIR Object Start/Stop Dates and e-Tag Should “expiring objects*” be allowed in e- Tags? Should the Tag Agent Service prevent the inclusion of expiring objects? Should the Tag Authority Service validate for expiring objects * Expiring objects are EIR entries that have a stop time before the Tagged Transaction’s stop time

12. EIR Object Start/Stop Dates and e-Tag 3.2 [Tag Authority] Registry Usage The Authority Service shall be responsible for maintaining an updated list of all registered entities whose identities must be uniquely specified in connection with the arrangement of a Tagged Transaction. The list of all such entities shall be maintained and available for downloading from the EIR web site. The Authority Service shall supply a procedure to allow updates from the EIR on demand or on a prescheduled interval. The EIR shall be in a format defined in a document posted on the EIR vendor’s web site. Each BA shall provide the necessary information to identify in the EIR who serves as their Authority Service when that particular BA is referenced as the Sink BA in an e-Tag.

13. EIR Object Start/Stop Dates and e-Tag 3.5 [Tag Authority] Data Validation The Authority Service shall ensure that all data elements in a communication are legitimate and that no syntax or validation rules have been broken.

14. EIR Object Start/Stop Dates and e-Tag Proposal The Authority Service shall ensure that all EIR objects in a new tag request and an extension request are active for the entire duration of the Tagged Transaction. The Authority Service shall ensure that all EIR objects in a new tag request and an extension request do not contain expiring objects.

15. EIR Business Practice Discussion Emergency Publications Company mergers/acquisitions

16. NERC Project 2008-12 CISDT Discussion

17. “Draft Tags” Concept Discussion

18. JESS Action Items Review

19. Other Business