You are on page 1of 1


5/week WA 2011 Instructor: K. Natarajan Email: Tel:343-8657 Office: AT5003 Text: "Power System Analysis" by Grainger and Stevenson, McGraw-Hill. Objectives: To make the student proficient in applying standard mathematical techniques to power systems analysis. Week # 1 2-4 5 6 7 8-9 10 11-12 Topics Line and transformer impedances, per-unit system, safety measures related to high voltage transmission networks. Network analysis and load flow problem. Transformer configurations, power in sinusoidal steady-state, reactance of synchronous machines. Introduction to fault analysis (three phase faults). Symmetrical components and power system component representation in sequence networks. Analysis of various non-symmetrical faults. Power system stability including equal area criterion and the use of equations of motion to determine response to a fault. Power system relaying and protection; protective devices; protective relaying; differential relaying on transformers and buses. Direct current transmission.

Assignments: Bi-weekly problem assignments are given from the textbook and other sources PROJECT: Each group of three students (groups formed by instructor) is required to write, test and document a successful computer program in a language of their choice on one of the following areas: the (optimal) load flow problem, the fault analysis problem, the state estimation problem and the power system stability problem. The choice and scope of the project must be made with input from the instructor and an abstract of the project submitted by email to the instructor and work should begin after the instructors acceptance of the abstract by email correspondence. (This phase of abstract and acceptance should be completed by the end of week 4 of the course). Deliverables: i) Each group must submit a written report which should include: an abstract, introduction, theory, description of the computer program (flow charts, uml diagrams etc.), application to a standard power system, results, discussion and conclusions, references, and finally the well-commented program listing, in that order. The cover page of the report should show how the work and responsibilities of the project were split (equitably) amongst the members of the group. Each group member must sign on this sheet acknowledging their share of the work. ii) Each group must submit their source code by email along with any data files used and information on how to compile and run their programs. This information should be such that the instructor can run your code to test its functionality. iii) Each student in each group must appear for a 5 minute quiz on the project after the submission of the project code and report by email at a mutually convenient time to be scheduled in a sign up sheet circulated in class during the last two weeks of classes. iv) Marks in the project for each member will be based on the successful coding of the project, the report (including language, spelling and grammar) as well as the individual quiz. The maximum mark recorded in the course until the project is completely finished (report, working code, quiz) will be 38I subject to the rules in the Calendar. MARKS: Mid-term (closed book): 20% Term Project: 20% Final Exam (closed book): 60%