3rd Party Registration &Account Management3rd Party Registration &Account Management
SMT Update To AMWG
March 24, 2014
3rd Party Registration &Account Management3rd Party Registration &Account Management
Update on Approved AMWG Change Requests Under Development
AMWG CR017 Interim Processes for
Historical Backfill Requests and
Subscription for New Customer History
3rd Party Registration &Account Management3rd Party Registration &Account Management
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
3rd Party Registration &Account Management3rd Party Registration &Account Management
Review and Clarify Long Term Permanent Solution Requirements for
AMWG Change Request 2013 017
AMWG 2013 017
3rd Party Registration &Account Management3rd Party Registration &Account Management
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
3rd Party Registration &Account Management3rd Party Registration &Account Management
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
3rd Party Registration &Account Management3rd Party Registration &Account Management
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.
3rd Party Registration &Account Management3rd Party Registration &Account Management
8
Request and Provisioning Process – API Access
Raise request by sending the request form* to [email protected]
Perform request information completeness validation
Send access authorization e-mail request to ROR admin, CC to SMT Operations Manager
Authorized?
1st Reminder e-mail (after 5 business days)2nd follow up by phone call / Operations Manager intervention
Create non-admin portal user for the new entity under ROR account
Share portal user information and new entity’s SSL security certificate to SMT
SMT shares ROR’s API account access details to new entity
SMT conducts initial configuration and troubleshooting session to complete integration
START
END
YES
NO
* Note: API access request form will be shared by SMT to Market. Suggested form attached at the end of this presentation.
ROR activity
SMT activity
1-10 days
5-10 days
1-5 days
5-10 days
Day 0
x daysBusiness days from previous milestone
3rd Party Registration &Account Management3rd Party Registration &Account Management
9
Request and Provisioning Process – FTP Access
Raise request by sending the request form* to [email protected]
Perform request information completeness validation
Send access authorization e-mail request to ROR admin, CC to SMT Operations Manager
Authorized?
1st Reminder e-mail (after 5 business days)2nd follow up by phone call / Operations Manager intervention
Share PGP decryption key with new entity
New entity shares SSL Security Certificate
Enable additional access for new entity to existing FTPS of ROR
SMT conducts initial configuration and troubleshooting session to complete integration
START
END
YES
NO
* Note: FTP access request form will be shared by SMT to Market. Suggested form attached at the end of this presentation.
ROR activity
SMT activity
1-10 days
5-10 days
1-5 days
5-10 days
Day 0
x daysBusiness days from previous milestone
3rd Party Registration &Account Management3rd Party Registration &Account Management
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.
3rd Party Registration &Account Management3rd Party Registration &Account Management
11
FTPS Access - Multiple DUNS Scenario
FTPS Folder and its content ROR Partner1 Partner2 Partner3
DUNS1
√
√ √
X
DUNS2
√
X
√ √
DUNS3
√
X
√
X
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.
3rd Party Registration &Account Management3rd Party Registration &Account Management
12
Implementation Timeline
# Activity Planned Dates
1 Requirement, approach and process documentation 02/03/2014 - 02/21/2014
2 Approach documentation review 02/24/2014
3 Approach documentation updates 02/25/2014 – 02/28/2014
4 Present revised approach and clarifications to AMWG 03/24/2014
5 Revert back from RORs if any concerns about restricting DELETE permissions on FTPS and about sharing PGP decryption key with their partners or allowing access to FTPS to their partners
04/11/2013
6 Implement FTPS configuration changes at SMT 04/14/2014 – 04/18/2014
7 Pilot account setup for testing (need volunteer) 04/21/2014 - 05/05/2014
8 Final process document updates, request form updates etc. 05/05/2014 – 05/09/2014
9 Final Market communication to roll out the functionality (go-live) 05/12/2014
3rd Party Registration &Account Management3rd Party Registration &Account Management
Status Update of AMWG Change Requests Approved by Retail Market Subcommittee (RMS)
3rd Party Registration &Account Management3rd Party Registration &Account Management
14
AMWG Change RequestAMWG CR Document
StatusEstimated Delivery
DateEstimated
Cost
AMWG CR 2013 001 – Report for AMWG Data Monitoring – Data Completeness Measurements
JDOA Estimation
2014-2015 In Process
AMWG CR 2013 002 – Reports for AMWG Data Monitoring – Data Timeliness Measurements
JDOA Estimation
2014-2015 In Process
AMWG CR 2013 003 – Reports for AMWG Data Monitoring – Measurement of Percentage of Actual Meter Reads
JDOA Estimation
2014-2015 In Process
AMWG CR 2013 004 – Reports for AMWG Data Monitoring – Measurement of Estimates
JDOA Estimation
2014-2015 In Process
AMWG CR 2013 005 – Reports for AMWG Data Monitoring – Number of SMT Help Desk Tickets Monthly by Ticket Type
Prohibited by IBM Non-Disclosure
N/A N/A
AMWG CR 2013 006 – Reports for AMWG Data Monitoring – Availability of SMT API
Prohibited by IBM Non-Disclosure
N/A N/A
AMWG CR 2013 007 – Reports for AMWG Data Monitoring – Availability of SMT FTPS
Prohibited by IBM Non-Disclosure
N/A N/A
AMWG CR 2013 008 – Reports for AMWG Data Monitoring – Average Time to Deliver HAN Messages
JDOA Estimation
2014-2015 In Process
AMWG CR 2013 009 – Reports for AMWG Data Monitoring – Number of Accounts by Type
JDOA Estimation
2014-2015 In Process
AMWG CR 2013 010 – Reports for AMWG Data Monitoring – Number of Reports Requested by GUI (Portal) and Number of FTPS Accesses
JDOA Estimation
2014-2015 In Process
AMWG / RMS Change Requests
AMWG CR 2013 0001
AMWG 2013 0002
AMWG 2013 003
AMWG 2013 004
AWMG 2013 005
AMWG 2013 006
AMWG 2013 007
AMWG 2013 008
AMWG 2013 009
AMWG 2013 010
3rd Party Registration &Account Management3rd Party Registration &Account Management
15
AMWG Change RequestAMWG CR Document Status Estimated Delivery Date
Estimated Cost
AMWG CR 2013 011 – Average Time from HAN Provision Request to Meter Ready Status
JDOA Estimation
2014-2015 In Process
AMWG CR 2013 012 – Bypass redundant screen for Users with only one meter when accessing HAN device information
Development 2014Included in Third-Party
AMWG CR 2013 013 – Timeout on SMT takes user to “incorrect login” screen
Development 2014Included in Third-Party
AMWG CR 2013 014 – Allow SMT user to toggle between 15-Minute Reads and Daily Reads without having to reset the date range
Development 2014Included in Third-Party
AMWG CR 2013 015 – Expand Daily Usage Graph to show 35 days of daily usage on the SMT GUI
JDOA Estimation
2014-2015 In Process
AMWG CR 2013 016 – Capability for RORs to grant access to vendors on their behalf to the ROR’s customers via API (energy usage, HAN messaging , and HAN provisioning) and FTPS files
Development Q2 2014
In DevelopmentReady for AMWG Design Review
AMWG CR 2013 017 – REP API for Energy Usage on SMT (Backfill of Historical Usage Data for Existing Customers- “Interim”)
See Below CR 2013 017 Permanent
Complete(12-18-2013)
Q4 2013 Completed
AMWG CR 2013 017 – REP API for Energy Usage on SMT (Subscription for New Customer Historical Usage – “Interim”)
See Below CR 2013 017 Permanent Development Q1 2014 In Development
AMWG CR 2013 017 – REP API for Energy Usage on SMT – Permanent Solution to Replace Interim Solution
JDOA Estimation
2014-2015 In Process
AMWG / RMS Change Requests (Cont.)
AMWG 2013 011
AMWG 2013 012
AMWG 2013 013
AMWG 2013 014
AMWG 2013 015
AMWG 2013 016
AMWG 2013 017
3rd Party Registration &Account Management3rd Party Registration &Account Management
Update on SMT’s 3rd Party Access System Development
3rd Party Registration &Account Management3rd Party Registration &Account Management
Third-Party Security Independent Review
1st Quarter 2nd Quarter
20133rd Quarter 4th Quarter
2014
Third-Party Customer Experience Review
SMT Customer Experience Changes
Third-Party Technical Design & Development
Security Validation
Additional Solution Requirements
Third-Party Testing
Third-Party Implementation
Project Schedule
17
Third-Party Design AMIT / SMT DO
Third-Party Volunteer Testers Technical Integration Sessions and Testing
Security Validation
SMT Design Assessment
Legend
Completed In Process Future Task
1st Quarter 2nd Quarter 3rd Quarter 4th Quarter
Third-Party Market Integration / Instruction
Webinars
© 2013 IBM Corporation Smart Meter Texas (SMT) Confidential18
Project Time LineThird-Party Participants Testing Working Timeline
4 WksIdentify and Confirm Participation
3rd Party Tester Design
3rd Party Tester Build 14 Wks
2/10
8 Wks
Solution Deployment to Production
Post Deploy Support 2 Wks
3rd Party Tester UAT
6 Wks
3/10 4/18 7/4 8/30
9/5
5 WksMarket Participants Communication and Webinars (Overview and Technical)
8/4
Scheduled Meetings and Webinars:
March 12 – Kick Off and Overview
March 19 – Solution Detailed Work Session
March 24 thru April 4 – One on One Sessions for Planning
April thru June – Monthly Q and A Update Sessions
April thru July – One on One Integration Sessions As Needed
3rd Party Registration &Account Management3rd Party Registration &Account Management
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.