Attachment - FTC Presentation
Upcoming SlideShare
Loading in...5
×
 

Attachment - FTC Presentation

on

  • 315 views

 

Statistics

Views

Total Views
315
Views on SlideShare
315
Embed Views
0

Actions

Likes
0
Downloads
2
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Mention: NERC joint Operating Subcommittees in October / going to FERC & NAESB later in November / Maybe WECC and TVA
  • Summary of presentation Note change DEMONSTRATION to DISPLAYS
  • Checkout is on everyone’s seams list / Physical vs financial problems / volume issue one into many / only submit one half
  • NO LONGER CHECK ONLY NETS / Phone calls, ID’s MW amounts Etc. / shear volume
  • Protocol only, not an application / Doesn’t replace phone call but facilitates the call
  • ISO displays / integration / Operators don’t need new application, keep it within existing tool sets
  • Simply presents MW interchange by tag ID
  • TAG ID is critical
  • Save time and confusion, focus narrowed for Operator, saves Operator for other activities
  • No Changes in markets / move industry forward
  • No Steal IT thunder by / No application to buy / no vendor / No fees / WECC $$
  • Talk about ISO savings
  • Pre checkout
  • Post checkout
  • NYISO
  • IMO
  • TE note columns
  • FTC is built on top of WEB Services. WEB Services is currently the evolutionary path that is being used by many organizations to provision on demand electronic services. Other NERC data exchanges (SDX) are adopting WEB Services as their standard for data exchange. WEB Services allows for the exchange of information between heterogeneous technology platforms. This means that each ISO can develop the business objects required to support the data exchange in any technology (i.e. Dot Net, J2EE). WEB Services can be hosted on most Web Application Servers (i.e. WEBSphere) and is available a FreeWare through APACHE. Information Security can be supported by different methods: Encryption of data stream using HTTPS Different methods for identifying the user (simple sign on, client side certificates).
  • The process of developing the messages required to support FTC took significantly longer then expected. Also, the quality of the resulting message and its conformance to industry standards is suspect. A pilot project was sponsored by the ITC to produce a methodology that could be applied to future data collaboration efforts. The results of the pilot was MDI. MDI is integrated with of the CIM data model which includes the NERC functional model. MDI ensures that future data messages will incorporate attributes that are defined in CIM or as agreed on extensions to CIM. Messages will have a standard structure. MDI includes a process for managing evolution of the data messages that are required to support the business processes. The result of the MDI process is a standard set of documentation describing new business process and the messages that are required to support it.
  • The process of developing the messages required to support FTC took significantly longer then expected. Also, the quality of the resulting message and its conformance to industry standards is suspect. A pilot project was sponsored by the ITC to produce a methodology that could be applied to future data collaboration efforts. The results of the pilot was MDI. MDI is integrated with of the CIM data model which includes the NERC functional model. MDI ensures that future data messages will incorporate attributes that are defined in CIM or as agreed on extensions to CIM. Messages will have a standard structure. MDI includes a process for managing evolution of the data messages that are required to support the business processes. The result of the MDI process is a standard set of documentation describing new business process and the messages that are required to support it.

Attachment - FTC Presentation Attachment - FTC Presentation Presentation Transcript

  • Facilitated Transaction Checkout Improving Operational Efficiency
  • Outline
    • Why Facilitated Transaction Checkout (FTC)?
    • What is Facilitated Transaction Checkout?
    • Operational Benefits
    • Displays
    • Technology Considerations
    • Implementation Status
    • Questions
  • Why Facilitated Transaction Checkout ?
    • The Northeast Market Operators are having increasing problems performing inter-control area checkout in real-time
      • Each market is prone to having its own unique rules and timelines for clearing external transactions
      • The volume and complexity of transactions significantly increased time required for manual checkout
      • Marketers were learning how to arbitrage the markets
  • Why Facilitated Transaction Checkout ?
    • These problems increase the likelihood of real-time discrepancies in inter-control area schedules affecting transaction data accuracy.
  • What is Facilitated Transaction Checkout ?
    • A tool for data exchange to support real-time transaction checkout
    • Each Control Area provides a “service” that enables neighboring CAs to view their current transaction stack prior to verbal checkout
  • What is Facilitated Transaction Checkout ?
    • Individual Control Areas can integrate this data into their existing displays to meet the unique needs of their Operators
    • Changes made on FTC ‘screen’ seamlessly carry into current scheduling software
    • Supplemental data (e.g Ramp info) may be added for one Control Area and available for all without it being required for all.
    • Current implementation allows Neighboring Control Area to compare, in real-time, transaction information for scheduling on common interfaces
      • Tag ID
      • MW value
    What is Facilitated Transaction Checkout?
    • Seamless integration for all markets that require the NERC E-tag as a common identifier
      • Physical or Financial transmission
      • Schedule or Tag based markets
    What is Facilitated Transaction Checkout?
  • System Operator Benefits
    • Operators can improve overall efficiency in real-time
      • Streamline communication between Operators thereby reducing overall checkout time
      • Allow the Operator to focus on the discrepancies in transaction schedules between Control Areas
      • Flexible enough to allow the Operator to access transaction schedules for future hours
      • Results in fewer failed transactions
      • Reduced administrative burden allows more time for System Operators to operate the system
  • Additional Benefits
    • No requirement for changing Market Rules
      • Business as usual up to the point of inter-control area checkout
      • The ‘Markets’ continue to independently clear transactions for next hour
    • Provides a solution for moving towards 15 minute transaction scheduling
  • Additional Benefits
    • Financial Benefits
      • Open Architecture (free code sharing)
      • No monthly fee or upgrade costs to third party
      • Total Project cost is limited to internal development time and server costs
        • (45 to 60K US dollars)
      • Project Costs are quickly recovered with reductions in ‘additional’ staff required for checkout
  • Time Savings Utilizing FTC *Based on production or test usage As much as 15 minutes / hour with full implementation 10 minutes 15 – 25 minutes NYISO Under review NB / NS As much as 20 minutes / hour with full implementation 5 – 20 minutes 10 – 40 minutes HQTE Under review PJM Under review MISO 8 - 18 minutes / hour with full implementation 2 minutes 10 – 20 minutes ISO-NE 20 minutes / hour each with NYISO, HQ 1 min. each with NYISO, HQ 40 minutes IMO Time Savings FTC* Manual Checkout Control Area
  • Displays ISO New England view into New York Transactions
  • 15:16:32 NY Checkout ready
  • 15:17:09 Checkout Complete 35 seconds
  • NYISO CA View
  • IMO CA View
  • HQT CA View
  • Technology Requirements
    • Must be standards based
    • Technology independent
    • Cost effective implementation
    • Scalable for other collaboration efforts
    • Secure information transfer
    • Led to a “Service Oriented” approach
  • Service Oriented Architecture
    • Established a repeatable, collaborative process
      • Model Driven Integration (MDI)
        • Driven by the CIM and the NERC Functional Model
        • Standards-based messages and predictable processes
      • Efficiency gains will minimize cost and accelerate schedule going forward
    • Implemented a scalable Web Services Architecture for Control Area data exchange
      • Can be leveraged for future initiatives
      • Will maximize return on investment
    Technology Benefits
  • Best Practice Technology
    • Drafting the Service-Oriented Architecture Blueprint
    • Gestalt - Energy Excerpts Volume 1 issue 3
    • “ It is this need for better data flow between members of the utility grid that is driving the migration to an SOA [ service-oriented architecture] and Web Services. If every power system operator, independent system operator and regional transmission organization implemented Web Services, the opportunity for efficient data sharing would be increased.”
    • The entire article can be found at:
    • http://www.rsvpnow.com/gestalt/gnl.asp?id=265&nlid=12
  • Implementation Status - NPCC
    • HQTE
      • Checkout Service and Control Room Integration: Testing with ISO-NE
    • IMO
      • Checkout Service and Control Room Integration: In service
      • Utilizing NY checkout service in production.
    • ISO-NE
      • Checkout Service and Control Room Integration: In service
      • Utilizing NY checkout service in production. Testing with HQTE
    • NB / NS
      • Checkout Service and Control Room Integration: Expected in-service in spring 2005.
    • NYISO
      • Checkout Service: In service
      • Control Room Integration: Deployment scheduled for early 2005 to follow SMD2 implementation.
  • Implementation Status - Other
    • MISO
      • Checkout Service and Control Room Integration: Expected in-service in early 2005.
    • PJM
      • Under review.
  • Questions?
  • Contact Information
    • General Questions
      • Jim Hartwell
      • [email_address]
      • 212-840-4904
    • Operational / Scheduling Questions
      • Mike Zeoli
      • [email_address]
      • 413-535-4349
    • Technical Questions
      • Michael Martin
      • [email_address]
      • 518-356-7617