Security Profile for Advanced Metering Infrastructure - Open Smart ...
Security Profile for Advanced Metering Infrastructure - Open Smart ...
Security Profile for Advanced Metering Infrastructure - Open Smart ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Line # Direction Summary of communication<br />
1 to AMI Meter Meter read requests, turn on/off commands, pricing data,<br />
provisioning requests, firmware updates, prepayment<br />
in<strong>for</strong>mation<br />
to AMI Head End Meter read data, various meter events (e.g., tampering,<br />
outage, and restoration), various confirmations (e.g., meter<br />
turn on/off, load shed start/end, and meter provisioning),<br />
HAN communication, error logs<br />
2 to MDMS Meter read data, various meter events and confirmations,<br />
HAN equipment responses, outage and restoration<br />
notifications, event logs<br />
to AMI Head End Meter read requests, load shed commands, planned outage<br />
in<strong>for</strong>mation, HAN equipment commands<br />
6 to AMI Head End Meter read data<br />
to Third Party<br />
Meter/Submeter<br />
Meter read requests<br />
9 to Field Tool/Device Stored meter data (including meter read data and ID) and<br />
logs, turn on/off confirmation, AMI system registration<br />
success, meter test results<br />
to AMI Meter Request <strong>for</strong> all meter data and logs, credentials <strong>for</strong> field<br />
person using Field Tool/Device, turn on/off commands,<br />
meter configuration data, request communication test and<br />
self-test results<br />
10 to MDMS Stored meter data<br />
to Field Tool/Device None identified<br />
11 to AMI Meter<br />
Problem meters report, meter service order request, meter<br />
Management System read data<br />
to MDMS Meter read requests, closed meter order status<br />
18 to AMI Meter<br />
Management System<br />
<strong>Security</strong> <strong>Profile</strong> <strong>for</strong> <strong>Advanced</strong> <strong>Metering</strong> <strong>Infrastructure</strong> Version 1.0<br />
UtiliSec Working Group (UCAIug) December 10, 2009<br />
Various meter events (e.g., intrusion, inversion, and<br />
customer load detected), meter status, meter location<br />
change or network disconnection, meter service order<br />
request, confirmation of firmware update download<br />
to AMI Head End Non-electric meter read requests, meter reconfiguration,<br />
updated firmware, command to execute firmware update,<br />
HAN device ping requests<br />
21 to AMI Network<br />
Management System<br />
Meter events, activity records<br />
to AMI Head End Non-electric meter read requests 4<br />
22 to AMI Head End Meter read data, establish connection confirmation, nonelectric<br />
meter events<br />
to Non Electric Meter Meter read requests, establish connection commands,<br />
meter event monitoring requests<br />
24 to MDMS Load shed control notification<br />
to DRAACS Load shed event end<br />
25 to DRAACS Load control request<br />
to Grid Control Center Load shed report<br />
4<br />
This probably shouldn't go from both AMI Management System and AMI Network Management System<br />
to Head End.<br />
11