1 / 19

SMT Update To AMWG

SMT Update To AMWG. March 24, 2014. Update on Approved AMWG Change Requests Under Development AMWG CR017 Interim Processes for Historical Backfill Requests and Subscription for New Customer History. AMWG Change Request 2013-17. Requirements outlined in Change Request approved by RMS

dyani
Download Presentation

SMT Update To AMWG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SMT Update To AMWG March 24, 2014

  2. Update on Approved AMWG Change Requests Under Development AMWG CR017 Interim Processes for Historical Backfill Requests and Subscription for New Customer History

  3. AMWG Change Request 2013-17 • Requirements outlined in Change Request approved by RMS • Backfill of Historical Usage Data for Existing Customers - Ability for the REP of Record to request a one-time retrieval of historical interval usage data (up to 12 months) for some or all of its existing customer base (backfill requests) • Delivered December 18, 2013 • Fulfilled 3 Requests to Date • In Process of Fulfilling an Additional 3 Requests in the Queue • Subscription for New Customer Historical Usage -Ability for the REP of Record to subscribe to automatically receive a one-time report of historical interval usage data (up to 12 months) for customers/ESIIDs that are newly served by them (new enrollments) • Development and System Testing Complete • In Process of User Acceptance Testing and Production Testing • Target Delivery First Week in April

  4. Review and Clarify Long Term Permanent Solution Requirements for AMWG Change Request 2013 017

  5. Update on Approved AMWG Change Requests Under Development AMWG CR016 Capability for RORs to Grant Access to SMT APIs and SMT FTPS to Vendors on Their Behalf

  6. API & FTP Access to Multiple Entities - Requirements • Ability for the RORs to allow API access for unlimited multiple entities in addition to retaining their own access, with appropriate approval mechanism. • Ability for the RORs to allow FTP access for multiple entities in addition to retaining their own access, with appropriate approval mechanism. • Background - • These multiple entities are typically Billing, EDI or Demand Response partners working on behalf of the REPs. • Currently only one entity can have access to API and FTP of one DUNS entity

  7. Solution Approach • API Access • Each entity uses its own security certificate • ROR creates a portal user (non-admin) for the new entity • SMT shares ROR’s API account access details to the new entity • SMT works with the new entity to configure and accomplish integration • FTPS Access • Each entity uses its own security certificate • SMT enables additional FTP access for the new entity on the existing FTPS account and shares the details • SMT works with the new entity to configure and accomplish integration • ROR has to share their PGP decryption key to new entity • This is the least effort and less resource consuming alternative. The other option is to create a new FTP account for new entity with their own PGP key, however it will require the files to be processed twice and a duplicate copy of the files with separate encryption to be stored at FTPS which requires processing power as well as space. • SMT restricts DELETE permission to all FTP accounts, to avoid deletion of files by one entity while the other has not downloaded it. The deletion will be performed by SMT as per the 10 days retention rule. There will be minor storage impact to retain more files as the immediate deletion that some entities are doing currently will be stopped.

  8. Request and Provisioning Process – API Access Day 0 ROR activity Raise request by sending the request form* to support@smartmetertexas.com Create non-admin portal user for the new entity under ROR account START SMT activity Business days from previous milestone x days Perform request information completeness validation 1-5 days Share portal user information and new entity’s SSL security certificate to SMT 1-10 days Send access authorization e-mail request to ROR admin, CC to SMT Operations Manager SMT shares ROR’s API account access details to new entity Authorized? YES NO 5-10 days 5-10 days SMT conducts initial configuration and troubleshooting session to complete integration 1st Reminder e-mail (after 5 business days) 2nd follow up by phone call / Operations Manager intervention END * Note: API access request form will be shared by SMT to Market. Suggested form attached at the end of this presentation.

  9. Request and Provisioning Process – FTP Access Day 0 ROR activity Raise request by sending the request form* to support@smartmetertexas.com Share PGP decryption key with new entity START SMT activity Business days from previous milestone x days Perform request information completeness validation 1-5 days New entity shares SSL Security Certificate 1-10 days Send access authorization e-mail request to ROR admin, CC to SMT Operations Manager Enable additional access for new entity to existing FTPS of ROR Authorized? YES NO 5-10 days 5-10 days SMT conducts initial configuration and troubleshooting session to complete integration 1st Reminder e-mail (after 5 business days) 2nd follow up by phone call / Operations Manager intervention END * Note: FTP access request form will be shared by SMT to Market. Suggested form attached at the end of this presentation.

  10. Pre-Requisites from RORs / New Entities • API Access – Certification Authority (CA) signed security certificate – ROR to create a non-admin portal user under them • FTP Access – Certification Authority (CA) signed security certificate – ROR to share their PGP decryption key to new entity – SMT will restrict DELETE permissions on FTPS server, this may cause a few ROR’s FTPS scripts to fail/throw errors if they try to delete files after downloading. Those scripts need to be modified to avoid such errors.

  11. FTPS Access - Multiple DUNS Scenario The access can be restricted at DUNS/folder level and content level. e.g. If a ROR want its partner to have access to only a subset of folders or only for specific type of content (i.e. interval usage LSE, adhoc reports, enrollment reports etc.) it can be provisioned accordingly.

  12. Implementation Timeline

  13. Status Update of AMWG Change Requests Approved by Retail Market Subcommittee (RMS)

  14. AMWG / RMS Change Requests

  15. AMWG / RMS Change Requests (Cont.)

  16. Update on SMT’s 3rd Party Access System Development

  17. Project Schedule 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 2014 2013 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter Third-Party Design AMIT / SMT DO Third-Party Security Independent Review SMT Design Assessment Security Validation Security Validation Third-Party Customer Experience Review Additional Solution Requirements SMT Customer Experience Changes Third-Party Technical Design & Development Third-Party Volunteer Testers Technical Integration Sessions and Testing Third-Party Market Integration / Instruction Webinars Legend Third-Party Testing Future Task In Process Completed Third-Party Implementation

  18. Project Time LineThird-Party Participants Testing Working Timeline

  19. SMTDO – Third Party Updates SMT DO Webinar Schedule April 25th – 10:00 – 11:00 a.m. May 23rd – 10:00 – 11:00 a.m. June 20th – 10:00 – 11:00 a.m.

More Related