Security Profile for Advanced Metering Infrastructure - Open Smart ...

Figure 1 shows one of the scenarios as an example. From diagrams of this kind, we extracted
• Components: each swim lane depicts a different entity involved in the business flow
captured in the scenario's activity diagram. Some components represent system
components, while others represent human actors. For our purposes, we restricted our
attention to system components. Additionally, some components were deemed outside
the scope of the AMI profile.
• Communication: arrows between nodes often represent some communication of
information or control signals between components. Other times, arrows simply represent
the sequence of activities. Some interpretation was necessary. The key information
extracted at this point was the nature of information and control exchanged between
components.
Some inconsistencies and oversights were encountered in analyzing the use cases and scenarios.
For example, in scenario 9 of use case B1, a meter is shown communicating with the MDMS
without going through a Head End. This was inconsistent with many other scenarios, and
assumed to be an oversight. Such corrections were made in several places to arrive at a
consistent logical architecture.
4.2 Logical architecture
A logical architectural view depicts logical components and their interactions. By logical
components, we refer to conceptual elements defined by common functionality. A logical
architectural view does not attempt to capture deployment information, such as allocation of
functionality to hosts or network segments. Nor does it attempt to capture all terminology and
physical configurations represented by different products.
The logical architectural components have only the meaning defined in this document,
regardless of how some other party may define the same terms.
As such, any product implementing the function of a logical component, shall satisfy all security
requirements identified in Section 5 that apply to that component—regardless of whether the
product uses that component's name or whether it implements the functions of multiple
components. Products that implement the functions of multiple components shall satisfy all
security requirements of each component whose functions it implements.
Security Profile for Advanced Metering Infrastructure Version 1.0
UtiliSec Working Group (UCAIug) December 10, 2009
9