SG-Systems WG by zdr9nek


(Smart Grid – Operational Applications Integration)
“Boot Camp” Overview
           Brent Hodges,         Greg Robinson,
           Chair, SG-Systems     Co-Chair, SG-Systems
   Introductions and Brief Overview of SG-Systems
   Requirements Gathering – Use Cases and System Requirements
    Overview with AMI-Ent example
   OpenADE
   OpenADR
   OpenHAN
   EIM Task Force
   General discussion, questions & answers
   Adjourn
                                          Open Smart Grid
                                             (OpenSG)                         EEI, UTC
                                            Technical Committee

SG Communications     SG Conformity    SG Security          SG Simulations   SG Systems
   Working Group       Working Group   Working Group        Working Group     Working Group

     SG Network            Edge          AMI-Security                          AMI-Enterprise
      Task Force        Conformance        Task Force                            Task Force

                                                                               Enterprise Info
    Network Interop      Enterprise    CyberSec-Interop                            Mgmt
      Task Force        Conformance        Task Force                            Task Force

                          Security     Usability Analysis                        Task Force
                        Conformance        Task Force

                                                                                 Task Force

                                                                                 Task Force

                                                                                Interest Group
NIST Conceptual Model

                        [Source: NIST Interim Roadmap]
[Source: NIST Interim Roadmap]
     Business Drivers
   Interoperability requires many standards in a profile stack
   The SDO process is relatively slow & needs more user input
        Work collaboratively with SDOs to ensure common user requirements are addressed
        Facilitate standards development by proposing potential solutions for addressing gaps
         in existing standards.
              The SDO ultimately determines when and how its standards are updated based on input.
   For Information Standards, resolve (don’t add to) semantic chaos
        Avoid having the same information defined with different names, varying definitions, etc.
        Ensure same information standards can be used across different communication
        While mapping to other standards will be unavoidable, strive to use, correct and extend
         one information model standard:
              The IEC TC57 Common Information Model (CIM) is the default information model for this
   There is substantial information overlap among AMI, ADE, HAN and
        While requirements and services vary significantly, they can be built using the same
         information model.
The CIM is the Basis for a Common Systems
Language for Utilities
   The same dictionary is used for
    multiple forms of human
        Letters
        Phone calls
        Conversations
        Emails
        Etc.

   In similar manner, the same CIM is
    used for multiple forms of computer
        XML
        RDF
        OWL
        DDL
                                                            One Dictionary
        Etc.
                                                            Supports Many
                                                            Forms of Communication

                                          Proprietary and Confidential
SG-Systems Working Group
   Charter:
       The SG-Systems Working Group defines requirements,
        policies, and services, based on utility industry standards
        such as the Common Information Model (CIM), required for
        information exchange from and to utility enterprise back
        office systems and between these back office systems and
        data acquisition and control servers (e.g., MDMS, AMI
        Head Ends, SCADA, OMS, GIS, CIS, work management,
            Task forces are established on an as needed basis to accomplish
             these goals for specific functional areas.
SG-Systems WG Process Overview
         Use Cases           HomePlug        IEC TC57 WG14,                      EPRI,
                              & ZigBee                         NIST
         From SCE                              OASIS, IEEE                     MultiSpeak
                               SE 2.0          Other SDOs
         and others

                                         Task Forces
System Requirements                        Use Case               Business-Oriented,
 Specification (SRS)
                                          Development             Common Format
                                                                  Use Cases Based on
                   SG-Security                                    SRS Reference Model
                                         Service Definitions
                                         (supporting SDOs)
                                                                 •Integration Requirements
  Recommendations to IEC
  TC57 WG14:                                                     •Sequence Diagram
  •Proposed CIM Extensions                                       •Services
  •Message Schemas Updates                                       •WSDL
  •Requirements Updates
  Recommendations to other
  SDOs                                         WG
Key Collaboration Concept for the
SG-Systems Working Group
       Standard building blocks are defined by IEC, other
        Standards Development Organizations, and industry
             e.g., OAISIS, Open Applications Group (OAG), MultiSpeak, OGC
       Requirements (use cases) are gathered from helpful
             Utilities
             Industry initiatives
       The SG-Systems WG articulates Industry Best Practices
        (see next slide) that satisfy requirements through the use
        of industry standard building blocks.
             Ideas for recommended extensions and changes to standard
              building blocks are provided back to appropriate standards
  February 2010                                                 SG-Systems WG
                               Our Focus: Finding/Developing Best
                               Practices & Making Them into Vetted
                               “Industry Best Practices”
             - Design &                         Local Utility Projects
             Utility’s                          Consortiums & User
                                                 Groups like OpenSG
           Architecture                          (business requirements) &
         -----------------------                 CIMug (optimization &
     Industry Best Practices                     implementation support)
     Interoperability Testing
                                                Standards Development
Industry Best Practices                          Organizations (SDOs) like
------------------------------------------       IEC TC57 Working Group 14
   Standards Conformance &                       for the IEC 61968 series of
      Interoperability Testing                   standards      SG-Systems WG
   Introductions and Brief Overview of SG-Systems
   Requirements Gathering – Use Cases and System Requirements
    Overview with AMI-Ent example
   OpenADE
   OpenADR
   OpenHAN
   EIM Task Force
   General discussion, questions & answers
   Adjourn
   Introductions and Brief Overview of SG-Systems
   Requirements Gathering – Use Cases and System Requirements
    Overview with AMI-Ent example
   OpenADE
   OpenADR
   OpenHAN
   EIM Task Force
   General discussion, questions & answers
   Adjourn
   Introductions and Brief Overview of SG-Systems
   Requirements Gathering – Use Cases and System Requirements
    Overview with AMI-Ent example
   OpenADE
   OpenADR
   OpenHAN
   EIM Task Force
   General discussion, questions & answers
   Adjourn
Scope of HAN SRS in the NIST conceptual model

OpenHAN - Scope

                                                         )                                                                                                                   Ex
                                                     red                   D                                                                                                   ter
                                                   cu                   Ge istrib                                                                                               (In l Inte
                                                (Se                       ne
                                                                             rat uted                                                                                              ter
                                            ice                                                                                                                                       ne rface
                                         ev                 Plu                 ion                                                                                                     t)
                                     e rD                      g-I
                                 nsum                             nH
                               Co                A                    rid
                            ed               Ho dvan
                         ter                    me ce                                                    Pre
                      gis                                dI                                                 mis                                                   Se
                    Re                              Dis
                                                       pla n                                                   eE
                                  Lo                       y                                                     MS                                                         Bo
                                    ad                                                                                                                                        x
                                       Co                                                                                                               S
                                         ntr                                                                                                          Ap mar
                                            ol                                                                                                          plia t
                           PC                                                                                                                               nc
                             T                                                                                                          He                    e
                                                                Ele Pre                                                       Lig
                                                                   ctr mis
                                                                      ic M e                                                 Co hting                                     e
                                                                                                                               ntr                                     vic
                                                      Pre                 ete                                                     ol                                 De
                                                          m                  r                                   In                                               er
                                                      (e. ise M                                                Dis Hom                                           m
                                                             Ga eter                                              pla e                                       nsu
                                                                                                                     y                                      Co
                                                                               y D d)
                                                                          tilit cure
                                                                         U e

     AM                           erg
       IB                            yS
         ac                            erv
           kh                             ice                                                                           el
             au                              s In                                                                     nn
               lN                                ter                                                                ha
                 etw                                fac                                                         t C al)
                    ork                                e                                                      as ign
                                                                                                          oa rice s
                                                                                                    blic nd p
                                                                                                  Pu ts a
                                                                                              ity    n
                                                                                          Util (Eve

                   OpenHAN History
  2007             2008                   2009                      2010
OpenHAN TF is    August 2008       June 2009                    Jan – July 2010
formed to        UtilityAMI 2008   Utility AMI 2008 HAN SRS     OpenHAN 2.0 collaboration
develop system   HAN SRS           v1.04 selected as a          effort
requirements     v1.04 released    customer domain standard
for the HAN                        in the NIST Smart Grid       August 30, 2010
                                   Interoperability Standards   UCAIug HAN SRS v2.0
                                   Roadmap                      ratified and released

                                   October 2009
                                   OpenHAN 2.0 formed to
                                   develop the next version
                                   of the HAN SRS

                                   OpenHAN 2.0 Effort
   Over 130 individuals representing over 80 companies participated in the
    development of the HAN SRS v 2.0 over a 10 month period
                                                              Participating Companies
            4home                   DTE Energy                         I’m in Control                  Proto6

            Aclara                  Duke                               Infineon Technologies           PSU

            AEP                     Eaton                              Invaluable Technologies         Reliant Energy

            APS                     Ecologic Analytics, LLC            Itron                           RIM

            Aridhio Technologies    Emerson /White-Rogers              Kaapco / ASR Systems            Sacramento Municipal Utility District

            AT&T                    emeter                             KCP&L                           SCE

            BC Hydro                Enernex                            Konnected Universe LLC          Schneider Electric

            BGE                     EPRI                               LG Electronics USA. Inc.        Southern Company

            BSH                     FPL                                LonMark International           Subzero

            CPUC                    Ford                               MicroSoft                       SunSpec Alliance

            Capgemini               GE                                 MultiSpeak                      Tendril

            Carrier                 General Motors                     NextGEN Consultancy Pvt. Ltd.   Trilliant

            CenterPoint             Georgia Power Co.                  N-Dimensions Solutions          UISOL

            Cisco                   google                             NV Energy                       U-SNAP Alliance

            Coincident, Inc         Granitekey                         Oncor Electric Delivery         Visible Energy

            Comverge, Inc.          Gridata Inc                        PA Consulting         

            Consumers Energy        heyCoop, LLC                       Panasonic                       ZigBee Alliance

            Certicom Corp           Home Automation, Inc               Pentair Water Pool & Spa

            Deloitte Consulting     Honeywell                          People Power

            DotUI                   HP                                 PG&E

            Drummond Group          Hypertek Inc                       Portland General Electric

            DS2                     IBM                                Progress Energy
                     Documents Reviewed
   Industry use cases were reviewed to identify any gaps
      o   ZigBee+HomePlug SEP MRD
      o   SAE J2836/1™ J2836/2™ and J2836/3™ Use Cases
      o   NAESB Draft Requirements Specifications for NIST PAP03, PAP04, and PAP09
      o   EIS Alliance Customer Domain Use Cases v1.0
      o   CEC Requirements Engineering for the Advance Metering Infrastructure and the
          Home Automation Network (AMI-HAN) interface – February 2008
      o   AHAM Smart Grid White Paper
      o   DER Contribution to OpenHAN; EPRI/DOE PV/Storage Communication Project
      o   Summary of Use Cases: For Demand Response Appliances Interface (EPRI
   February 2010 NISTIR 7628 Smart Grid Cyber Security
    Strategy and Requirements
             UCAIug HAN SRS v2.0
     Define the system requirements for an open standard Home
      Area Network system
     Promote open standards-based HANs that are interoperable
     Provide the vendor community with a common set of principles
      and requirements around which to build products
     Ensure reliable and sustainable HAN platforms
     Support various energy policies in a variety of states,
      provinces, and countries
     Empower consumers to manage their electricity consumption
      by giving them the information and control they need to make
      decisions on their energy use
                  UCAIug HAN SRS v2.0
Architectural Considerations
        HAN SRS applies from the edge of the AMI System, where the
         Energy Services Interface (ESI) resides, to all relevant HAN
         Devices in the premises
        Energy Services Interface (ESI)
           o   An interface which enables communication between authorized parties
               and HAN devices that are registered to it
           o   There may be more than one ESI in the premise (e.g. Utility ESI, 3rd
               party ESI)
           o   Utility ESI – provides interface between the Utility AMI network and HAN
               devices, including the AMI meter
           o   Other ESI – provides interface between other communication media
               (e.g. internet, cell phone, EMS, etc.) and HAN devices registered to it

                 UCAIug HAN SRS v2.0
Architectural Considerations, continued
         Commissioning, Registration, Enrollment
           o   Commissioning is the process by which a HAN device obtains
               access to a specific physical network and allows the device to be
               discovered on that network
           o   Registration is the process by which a Commissioned HAN device
               is authorized to communicate on a logical network by exchanging
               security credentials with an ESI
           o   Enrollment is the process by which a Consumer enrolls a
               Registered HAN device in a Service Provider program (e.g. demand
               response, energy management, PEV program, etc.)

                                                                      Enrolled HAN Device
                                                                      (must be Registered)

                                                                                            Registered HAN Device
                                                                                            (must be Comissioned)

This figure shows the type                                                                                        Commissioned
of communication a HAN                                                                                             HAN Device
Device may engage in,
which is dependent upon its
relationship with the ESI and              Energy Services
the Service Provider.                       Interface (ESI)

                            Service Provider Network
                        (e.g. AMI Network, Internet, etc.)

                                                                  Communication Types

                                           Service Provider Messages including Control Signals (Two-way
                                           communications between Service Provider and Enrolled HAN Devices)

                                           Consumer Specific Information (One-way and Two-way communications between ESI
                                           and Registered HAN Devices as well as among Registered HAN Devices)

                                           Public Information (One-way communications to Commissioned HAN Devices)

                                           Service Provider to ESI (Two-way communications to the ESI which may elicit further
                                           communication between the ESI and Registered HAN devices and Public Information from   23
                                           the ESI to Commissioned HAN devices)
             UCAIug HAN SRS v2.0
Architectural Considerations, continued
      HAN SRS is agnostic to device ownership
      Some HAN devices may reside on more than one ESI
      HAN SRS is agnostic to electric market structure and is
       applicable to both integrated utility markets as well as
       consumer choice electric markets
      There may be multiple communication paths into the HAN
       (e.g. Utility AMI, internet, cell phone network, EMS, etc.)
      HAN SRS addresses the following special applications
         o   Plug-in-Electric Vehicle (PEV)
         o   Energy Management System (EMS)
         o   Distributed Energy Resources (DER)

                 UCAIug HAN SRS v2.0
HAN System Requirements
     Application Requirements
         Control applications respond to control signals
         Measurement and Monitor applications provide internal data and status
         Processing applications consume, process, and act on external and
          internal data
         Human Machine Interface (HMI) provides Consumers a means to
          provide input into an application or to view information from an
     Communication Requirements
         Commissioning is the network process of adding a HAN device on the
          HAN to allow the device to communicate with other devices and
          involves network scanning, selection, admission, and configuration
         Control of a node involving self-organization, path selection, mitigation

                 UCAIug HAN SRS v2.0
HAN System Requirements, continued
     Security Requirements
         Access Controls and Confidentiality address data protection for data-at-
          rest and data-in-transit
          Registration is the network process to authenticate and authorize HAN
          device participation with an ESI and includes initialization, authentication,
          correlation, authorization, and de-register
         Enrollment is the process by which a Consumer enrolls a HAN device in a
          Service Provider’s program (e.g. demand response, energy management,
          pre-pay, PEV programs, distributed generation, pricing, messaging, etc.)
          and gives certain rights to the Service Provider to communicate with their
          HAN device
         Integrity preserves the HAN operating environment through resistance
          and recovery
         Accountability will allow for monitoring malicious activities through audit
          and non-repudiation
             UCAIug HAN SRS v2.0
HAN System Requirements, continued
     Performance Requirements
         Ensure applications or other factors do not limit the performance of the
          system, which is dependent upon availability, reliability, maintainability,
          scalability, upgradeability, quality and latency

     Operations, Maintenance, and Logistics Requirements
         Manufacturing and Distribution - Vendor’s pre-installation activities
          including pre-Commissioning settings, application configuration,
          labeling, support for multiple distribution channels
         Installation – Documentation for the physical placement of the device
          and support systems
         Manage, Maintain – ensure HAN device diagnostic, management and
          trouble shooting capabilities including alarming, logging, testing, device
          reset, and monitoring


UCAIug HAN SRS v2.0 is located on the OpenHAN sharepoint:

   Introductions and Brief Overview of SG-Systems (Greg)
   Requirements Gathering – Use Cases and System Requirements
    Overview with AMI-Ent example (Mark)
   OpenADE (Steve or Dave)
   OpenADR (Bruce)
   OpenHAN (Erich)
   EIM Task Force (Jim)
   General discussion, questions & answers
   Adjourn
Smart Grid Interoperability
        Ability of systems to operate in coordination
            Ability to exchange and use information appropriately
        Requires standard interface definitions
            Governed by open industry working groups

        Provides Benefits
            Promotes loosely-coupled integration
                 Allows incremental functional enhancements
                 Creates market for reusable, compatible components
            Only one integration instead of many
                 To an open, public, standard interface
                       Instead of each proprietary vendor or utility interface
Smart Grid Challenges
       Requires Integration – LOTS of integration
           Onslaught of new applications and technologies
                AMI, MDMS, HAN, DR, ADE, etc.
       In a complex IT environment
           Many custom systems, legacy technologies
           Typically departmentally controlled – within “silos”
                Need ability to govern, manage, and share resources
                      at the Enterprise level and beyond (external services)
           Aging / outsourced systems and IT workforce
           Historically, extremely low R&D expenditures
                Must ramp up capabilities quickly
           Each utility has its own Software Development Life
            Cycle (SDLC)
It’s More Than Just Technical Matters

           Driving Forces                                          Restraining Forces
1.   Consistent enterprise-wide data                      1.   Lack of stable industry standard definitions
2.   One version of the truth                             2.   Vendor’s way = lower project costs
3.   Access to data regardless of source                  3.   Vendors pushing for ‘proprietary lock-in’
4.   Business transformation agility                      4.   Consultants pushing to be ‘thought leaders’

                                            Status Quo
5.   Reduced project implementation costs                 5.   Hours-sold revenue driving System Integrators
6.   Reduced maintenance costs                            6.   Internal system experts want to remain experts
7.   Reduced IT risks                                     7.   Project managers striving for control
8.   Availability of external services                    8.   Inertia – why change?
9.   Scalable business process automation                 9.   Our situation’s unique – standards hinder us
10. Scalable business activity monitoring
11. Accurate reporting – regulatory, KPIs                For further information, please refer to the article on page 56
                                                         of the January issue of Utility T&D Automation & Engineering:
12. Mergers and acquisitions                              
Defining EIM (Gartner)
  Enterprise Information Management (EIM) is:
         An organizational commitment to structure, secure
          and improve the accuracy and integrity of
          information assets,
         to solve semantic inconsistencies across all
         and support the technical, operational and
          business objectives within the organization's
          enterprise architecture strategy.
     A commitment to EIM is recognition that
      information in the enterprise is as important as
      process (application development) and
      infrastructure (technology)
Overall EIM Framework
                                       Enterprise           Enterprise
Enterprise Vision     Enterprise                                                 Enterprise
                                      Business & IT        Business & IT
   & Strategy        Architecture                                              Infrastructure
                                     Core Processes        Organizations

  EIM Vision &                           EIM Core                                   EIM
                    EIM Governance                        EIM Organization
    Strategy                            Processes                              Infrastructure

                                       Data Quality                             Information
     Vision          Sponsorship                            CSFs & KPIs         Architecture
                                       Data Integrity                            Blueprint
                                      Data Security &         Structure
    Mission          Stewardship        Protection             (Virtual,
                                       Data Lifecycle        Hybrid……)          Technologies
                                       Management                              (DBMS, Content
                      Policies,                                                Mgmt, ETL, EAI,
                                     Data Movement            Roles &              EII, Data
    Strategy         Principles &
                                                           Responsibilities   Modeling, BI/DW,
                        Tenets          Semantics
    Goals &                             Database             Functional
   Objectives                          Management             Services
                                       Master Data                            and Repositories
     Value                                                 Business Value
                      Structure         Information
  Propositions                                            and Relationship
                                          Services                            Standards & Best
                                     Services & Support                           Practices
EIM Charter
   Identify and articulate common EIM requirements:
        Use cases
             Activity Diagrams
        EIM Requirements Specification
   Develop common EIM Framework that satisfies requirements, taking
    advantage of other relevant industry work as appropriate (e.g., vision,
    governance, processes, etc.)
   Develop requirements for an OpenSG generic semantic model to be used by
    members as a starting point for their enterprises.
        Collaborate with SGAC of the NIST SGIP
   Provide a forum for exchanging information so that all members can benefit
    from lessons learned.
   Collaborate with Standards Development Organizations (SDOs), NIST SGIP,
    and/or consortiums so that needed advancements are accomplished in the
    most appropriate organizations in the most efficient manner.

                                          Slide 35
   Introductions and Brief Overview of SG-Systems (Greg)
   Requirements Gathering – Use Cases and System Requirements
    Overview with AMI-Ent example (Mark)
   OpenADE (Steve or Dave)
   OpenADR (Bruce)
   OpenHAN (Erich)
   EIM Task Force (Jim)
   General discussion, questions & answers
   Adjourn

To top