Projectplan 2

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 6

University of Northern Iowa Electric Distribution Modeling: Project Plan rev 2

Group#: May14-33 Client: University of Northern Iowa Advisor: Professor Colin Christy
Members: Justin Craig John Hanke Chris Hankey Darin Lamos

1. Problem/need statement

The problem is UNI has no way to quickly realize their distribution system. They are currently relying on a notebook and the experience of their electricians. The need is a program to model and show an up to date view of their system. The main feature requested is a switch conditions view. This program needs to be streamlined and user friendly.

2. Main Concept Sketches Basic Map/Editor Concept

3. System block diagram

4. System description

The user will start by entering a username and password into the University of Northern Iowas system. This will bring them to a screen where they can select between an overhead map view, editor, switch manager, and meter viewer. The overhead map view will consist of five color-coded circuits with zooming features and a visual representation of switch conditions. The editor panel will be able to modify the circuits as needed. The switch manager will show a list of the switches and their current states. Users can easily change the switch conditions from this page. There will be a real-time meter view with live reading data pulled from UNIs system. From this meter view, users will be able to check historical meter usage including daily high/low recordings.

5. Operating environment Our project will be developed

6. User interface description

The users we expect to have with our program include the high voltage electricians, management, IT specialists, and potential a 3rd party cad technician. It is important that our program have a streamlined and user friendly interface. Our intent is to have a GUI overlaying our code so anyone without an understanding of a programming language will have no problems using our program. It is also important how we will organize and present the data from the meters. We intend to include documentation on our program so that someone would be able to learn how to use it.

7. Functional requirements

1. 2. 3. 4. 5. 6.

Clearly be able to identify each individual circuit Be able to recognize individual switches within each circuit The condition of the switches is obvious to the user Power flow calculations must be accurate for simulation Real-time power is integrated into the system Ability to manipulate circuits, for the purpose of load transfer modeling

8. Nonfunctional requirements 1. 2. 3. 4. 5. 6. 7. Client needs to easily understand graphics from the software design New updates for the software should be easy to preform Training manual for new employees that will need to work with interface Code needs description so it can be easily explained All different circuit branches need to be distinguished To change real life switch positions there needs to be password protection Simply navigation from real conditions to what if conditions

9. Market and literature survey

Software Research: ETAP - etap.com has some more advanced software circulating in the market. Etap is the most viable option if we were to choose to use a commercial software. The best thing about the software is that you can buy modules of the program. Both reducing cast and maximizing utility of the program. Microsoft Visual Studio This application would make the visual aspect of our program easier to create, but the power flow simulation program would be a lot tougher. Not a great option.

NetBeansIDE This platform allows applications to be developed from a set of modular software components. NetBeans has an application platform framework for Java desktop applications. This is a great option for our integrated development environment.

Adobe Flex SDK- This option seems best for more visual intensive designing. It would be difficult to program the power flow applications. Not a cost effective option.

10. Deliverables:

The following is the refined and approved deliverables set forth for by our client for the coming semesters.

Fall: - After a semester of research we will present or findings to UNI for them to choose which path we should pursue. The paths being integrating ETAP to their system or developing our on program.

Spring: - Switch condition simulation: The model will have the ability to change the circuits in order to simulate new power flow and verify circuit would not experience too much power load. - Real-Time power integrated into the model. The model will show real time power flow within each circuit.

11. Work plan: Work breakdown: Darin - Interact with client, Learn Java in relation to this project, Help with power equations, Bitch-tits John- Power equations lead, Learn applicable Java, Real-Time liaison to Schneider Electric Justin - Quality control, Program hierarchy development, Real-Time integration planning Chris - Master coder, Approve all code files Resource requirements Youtube tutorials for visual basic Etap representatives Power Professors Com Sci Professors Industry Contacts The Clients

Project Schedule - Fall Semester September 23rd - Project scope is due. September 27th - Website roughly done. October 4th - Project plan is due November 1st Decide two paths for our project December 2nd presentations and two samples are ready for the client December 6th - Rough draft of the program and a presentation to UNI about the different choices. December 9th - Start of dead week December 16th - Finals week

Project Schedule - Spring Semester January 13th - Spring semester starts. January 31st - Reach ability to pull real-time data from power meters. February 28th - Editor function complete. March 17-23 - Spring break March 28th - Code is nearing completion April 25th - Finishing touches on the code and have user documents done. May 2nd - Present program to UNI

You might also like