must accept agreement. Customer moves out of a premise The ESIID is removed from the Customer account. The ESIID is automatically removed from the ROR account and the REP will lose access to the Customer’s usage information. All Third Party agreements associated with that ESIID are automatically terminated and any In-Home Devices are removed from the HAN. Meter disconnect and reconnect The ESIID will still be associated with the Customer account but will show no usage during the period of disconnection. The ESIID will still be associated with the ROR account but show no usage during the period of disconnection. The ESIID will still be associated with any Third Party Agreements but will show no usage during the period of disconnection. Replacement of a smart meter The ESIID will remain the same but the meter number will change. SMT will automatically change the meter number associated with Customer’s account to reflect the current meter number. The Customer will continue to have access to the smart meter usage data and the SMT service will be uninterrupted. Existing Devices will automatically be re-added to the Customer HAN and the Customer notified. Customer may have to reboot the In-Home Device(s) to regain functionality. The ESIID will be linked with the new meter number and this association will be reflected in the ROR meter information. The ROR will continue to have access to the smart meter usage data and the SMT service will be uninterrupted. No change to the Third Party agreements. The Third Party does not have access to the meter number. Customer switches to another REP The ESIID and meter number are associated with the Customer premise and Customer will see no change in their access to usage The former REP will lose access to the Customer’s usage information and the new REP or ROR will gain No effect on the Third Party agreements.
BR- 017.016 Ability to require a user to change their temporary password after the first log-in with their temporary password. SG.AC-21 Passwords BR- 061 Ability to purge any user ID after a period of 13 months of inactivity (i.e., not logged on to the web portal). Includes all user ID types. SG.AC-3 Account Management BR- 028.024 Ability to restrict TDSP access only to data associated with the ESIIDs within that TDSPs territory (e.g., meter data, premise data, usage data) SG.AC-3 Account Management SG.AC-6 Separation of Duties SG.AC-7 Lease Privilege BR- 031 Ability to establish and maintain security controls associated with portal access for REP of Record. SG.AC-3 Account Management BR- 028.010 Ability to grant and/or block access to certain data based on security level (e.g. Customer role, REP role, Admin role, etc.) SG.AC-3 Account Management SG.AC-6 Separation of Duties SG.AC-7 Lease Privilege BR- 031.002 Ability to allow REP of Record access to usage data, meter attributes, and premise information for ESIIDS that are currently served by that REP. SG.AC-3 Account Management BR- 017.017 Ability to utilize security (e.g., CAPTCHA) procedures during the user’s initial registration. Includes the ability to cancel the registration process to the web portal requiring the user to start the registration process over, after 3 unsuccessful attempts to correctly enter the CAPTCHA. SG.AC-2 Remote Access Policy and Procedures SG.AC-15 Remote Access BR- 028 Ability to provide appropriate level of security depending on who is accessing the ESIID data on the common web portal. SG.AC-3 Account Management SG.AC-6 Separation of
Duties BR- 017.003 Ability to allow a minimum of at least 6 characters and no more than 24 characters letters and numbers, case sensitive, in the password. Additionally, the password cannot be the user name. SG.AC-21 Passwords BR- 017.007 Ability to set up and store a user specified password security question and answer SG.AC-2 Remote Access Policy and Procedures SG.AC-15 Remote Access BR- 017.002 Ability to allow up to a minimum of 5 and a maximum of 100 alphas / numbers / special characters, except slashes and single and double quotes, in the user id SG.AC-2 Remote Access Policy and Procedures SG.AC-15 Remote Access
6: Business Procedures Alignment between Operational Business Processes and Procedures AMIT SMT APIs, SMT FTPS site Lodestar Enhanced file format XML and CSV format Hardware and Software Technology Vendors The format for usage data to be received by ERCOT, REPs, Third Parties, and Customers is determined. TDSP’s use the LSE file format for Customer usage data files sent to ERCOT and REPS. A SMT FTPS site is set up for REPs and Third Parties to retrieve their Customer’s smart meter usage data. Standard usage APIs are created for REPs and Third Parties to request ad-hoc usage reports and for Third Parties to request scheduled usage reports. Standard HAN APIs are created for Third Parties to add/remove In-Home Devices on a Customer’s HAN and to communicate with those In-Home Devices. AMIT and the SMT team develop notification procedures and education materials. GUIs are developed and tested for the SMT web portal. Customers may export usage data in an XML or CSV format. INFORMATIONAL 5: Business Context Awareness of the business knowledge related to a specific interaction TDSPs Solution provider AMIT Consumer insights professional In 2008, AMIT agrees on the technical design for a common web portal. A competitive RFP process for the development of the common web portal results in the selection of a solution provider. Oncor and CenterPoint negotiate a Joint Development and Operation Agreement for the development and support of SMT.
systems. Science and Technology Policy initiated the Green Button Initiative, SMT incorporated the Green Button icon on Customer pages in the SMT web portal. If the ZigBee SEP 2.0 HAN communication protocol is adopted by the TDSPs in the future, the APIs may be modified to reflect this change. Additional innovation will be enabled when Third Parties are granted access to SMT functionality by the end of 2014. Scalability Architectures should include architectural elements that are appropriate for the applications that reside within them. The architectures must support development of massively scaled, well-managed, and secure systems with life spans appropriate for the type of system, which range from 5 to 30 years. SMT was initially developed as a common data repository for CenterPoint Energy and Oncor and was later expanded to include AEP Texas and TNMP. It is segregated so that each TDSP has access to only the meter data of their Customers. Access to usage information initially was only given to Customers and their ROR. By the end of 2014, SMT will be expanded to include Third Parties giving them the opportunity to offer innovative energy management products to Customers. Legacy Architectures should support legacy system integration and migration. SMT supports the use of the LodeStar Enhanced (LSE) file format for transmitting energy usage information since this format was currently in use by ERCOT and the TDSPs. Security Architectures should support the capability to resist unwanted intrusion, both physical and cyber. This support must satisfy all security requirements of the system components. SMT has the capability to resist unwanted cyber intrusion through the use of common information security technologies and practices and it satisfies the NIST IR security requirements for this type of system. (See Section 9)
Figure 25: Green Button PCI and NERC CIP Security Standards During the development of the SMT business requirements, AMIT created a task to evaluate both the Payment Card Industry Data Security Standard (PCI DSS) and the NERC Critical Infrastructure Protection (CIP) standards to determine which, if any, of these standards apply and what requirements applied to SMT. The NERC CIP standards have continued to evolve with the forthcoming version 5 being applicable to the bulk electric system which does not include SMT. The task group identified cyber security standards best practices and specific requirements for SMT from their review of these standards. At a high level, the requirements are: Build and maintain a secure network PCI Requirement – Install and maintain a firewall configuration to protect critical data PCI Requirement – Do not use vendor supplied system defaults for system passwords and other security parameters NERC CIP 005-1 – Electronic Security Perimeter Protect critical data PCI Requirement – Protect stored critical data PCI Requirement – Encrypt transmission of critical data across open, public networks Identify critical cyber assets NERC CIP 002-1 – Critical Cyber Asset Identification Maintain a vulnerability management program PCI Requirement – Use and regularly update anti-virus software PCI Requirement – Develop and maintain secure systems and applications NERC CIP 007-1 – Systems Security Management Implement strong access control measures PCI Requirement – Restrict access to critical data by business need-to-know PCI Requirement – Assign a unique ID to each person with computer access