USA Department of Energy(DOE) created an interesting document named Smart Grid: An introduction. Worth reading.
During my career which is mainly done in a company which creates software for smart grid solution, and in a power distribution utility, most of the time I have been working with database aspects of that story. The purpose of this blog is to give an insight into general database aspects, with reference to smart grid specifics. Also, I am going to discuss other interesting Smart Grid subjects.
Thursday, August 16, 2012
Thursday, August 9, 2012
Peak time in network and price of energy
According to this Smart Grid IEEE article peak time in Sacramento is between 4 and 7 PM, in summer, for, probably, residential consumers. Knowing customer load patterns is very useful thing.
Also interesting information is that supplied energy is 10 times more costly in peak time than in non - peak time. And this is not without reason. It is because the whole power system - from generation to distribution - suffers big problems which are the results of the peak load. So reducing peak load, through several tactics, is the ultimate goal for overloaded networks.This is why they are charging ten times more money for energy used in peak load. They are telling their customer - please, reduce Your load :-)
Also interesting information is that supplied energy is 10 times more costly in peak time than in non - peak time. And this is not without reason. It is because the whole power system - from generation to distribution - suffers big problems which are the results of the peak load. So reducing peak load, through several tactics, is the ultimate goal for overloaded networks.This is why they are charging ten times more money for energy used in peak load. They are telling their customer - please, reduce Your load :-)
Monday, August 6, 2012
SME
This is one very important abbreviation and a role hiding under these 3 letters. It means Subject of Matter Specialist. In software development, this is a person whose role is very important, especially in huge companies, with many horizontal layers of software. This person, SME, should know the some specific functionality - what were the requirements for that functionality, how does it work, how should it work, theoretical background of functionality, what customer wants to see in this functionality, what are the competitors solution looks like, which software components are used in this functionality, what are the components interfaces, how these components are set (configured) in order to provide this functionality, what is the flow of data, where are the logs of all components, how they can be read. Someone who can point in a component and said - this component has an error. Person who can orchestrate bug resolving, new features development.
And this person is very valuable in a fast growing company, where documentation can not follow the pace of the growth.
And this person is very valuable in a fast growing company, where documentation can not follow the pace of the growth.
Subscribe to:
Posts (Atom)