Browse Prior Art Database

Method and System for Implementing Optimized Rolling Power Blackouts

IP.com Disclosure Number: IPCOM000202405D
Publication Date: 2010-Dec-15
Document File: 4 page(s) / 118K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system for implementing optimized rolling power blackouts is disclosed. The power blackouts may be implemented based on user preferences and priority for a time of blackout. Thus, the power blackouts are implemented considering user/community priorities as well as fairness across the users/communities.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 37% of the total text.

Page 01 of 4

Method and System for Implementing Optimized Rolling Power Blackouts

Disclosed is a method and system for implementing optimized rolling power blackouts. The power blackouts may be implemented based on user preferences and priority for a time of blackout. Thus, the power blackouts are implemented considering user/community priorities as well as fairness across the users/communities.

The figure shown below illustrates an environment in which a system for implementing the optimized rolling power blackouts operates.

(This page contains 00 pictures or other non-text object)

Figure

The environment includes a power grid for generating and supplying power to users and a distribution center (DC) for distributing the power generated. A preference database (PD) is provided that includes preferences of the users. In an instance, the users interact with the PD through a web based systems. A typical web-based user interface includes various fields such as, a userID, name, a time List, override(true/false), etc. The time List field includes, date, start time, end time and power priority (varying from 1 to 10). In the case of the power priority, 1 is considered the lowest and 10 is considered to be the highest. Further, a community interface includes various fields such as, a community ID, name, a time list, canOverride (true/false). The time list field includes, date, start time, end time and power priority (varying from 1 to 10).

In another instance, the user may enter their preferences to the PD using a Short Messaging Services (SMS) using a mobile device. In this instance, a mobile number of a user is saved in the PD. Thereafter, a SMS is sent by the user. The PD identifies a userID and the mobile number of the user. A format of the SMS may be as follows:

1


Page 02 of 4

Date

timeStart

timeEnd

priority

canOverride

For example, 15/03/2010

10 PM

12 PM

5

true

These details present in the SMS are saved in the PD. The PD confirms the message by sending an accept message to the user. Thereafter, the message is processed. In case there is an error in the details present in the message, the PD sends an error message to the user. Thus, the preferences of the users are saved in the preference database.

During operation, the DC sends a list of customers to a match maker prior to power blackout. The DC sends the list as a message to the match maker. The message includes totalPower (total amount of power that needs to be cut), duration and a list. The list includes, a communityId and a power usage. The power blackouts can be implemented based on the community specified in the list. The match maker then computes the solution to an optimization problem associated with the power blackouts. To perform optimization, a default priority considered for each user/community is 1. For each user/community, the match maker sorts the days by their priority in descending order. In the case of bottom 90% of the list of customers (lower priorities), each value is divided...