90 likes | 262 Views
ESS and ITS Meeting November 17 – 18, 2004 Washington, D.C. NERC / NAESB Subcommittee Coordination Gordon Scott – NERC Staff. NERC Market and Operating Committee Actions.
E N D
ESS and ITS MeetingNovember 17 – 18, 2004Washington, D.C. NERC / NAESB Subcommittee Coordination Gordon Scott – NERC Staff
NERC Market and Operating Committee Actions • John Anderson moved that the Operating Committee accept the Market Committee’s recommendation to disband and ask the joint Executive Committees, before the February BOT meeting, to recommend to the Board how to continue coordination between NERC and NAESB. • Friendly amendment – Ed Riley moved that the NERC OC subcommittees continue their coordination with NAESB. • Both motions were Approved.
OC Subcommittee Officers Meeting • NERC and NAESB subcommittee coordination continues to be vital • Examples are CI Standards groups - TLR joint group – Maintain TSIN Letter • Assigned all NERC subcommittees new tasks and responsibilities
OASIS 1A and II Jagjit Singh, chairman of the JOITF, will draft an email on forming a Registry Team. Those at the meeting agreeing to be part of the team are: Jagjit Singh, Larry Stone, Paul Sorenson, Andy Rodriquez, and Monroe Landrum. The NAESB Registry Team leadership will request a meeting with NERC staff and the TISWG’s Registry Task Force, on what may be needed to implement • OASIS II – Stage 1, 2, and 3.
TSIN Registry • Formation of a NERC / NAESB Registry Task Forces that will meet jointly as the NERC / NAESB Task Force to coordinate the TSIN Registry. • For NERC the group reports to the TISWG. • For NAESB the group reports to the ITS. • Note: NERC and NAESB groups may need to revise their scopes and visions • See NAESB Registry Standards Request
E-Tagging • Potential Enhancements • Version 0 and Version 1 revisions • Son of E-Tag • Electronic Scheduling • Is NERC / NAESB “Maintain E-Tag” letter needed?
Functional Model functions • IA • TSP • PSE for Interchange • MO for Interchange Coordinate Interchange Continue coordination with CI groups
V0 Business Practices and Reliability Stds. Operator Manual • Is manual needed for Version 0? • For Version 1? • What group should develop? • Timeline • Training
Industry System Development • What needs to be developed? • What is being developed? • Redundant development? • No group is overseeing, coordinating, cataloging, and providing guidance for system development.