Energy Power Company will supply changeless, dependable service to all clients whether residential, commercial or industrial. We will supply up to day of the month information to our clients sing their outage which will include timely information on Restoration attempts and cause of outage. Our client base will be over 95 % satisfied with our Restoration attempts. In add-on to our reactive response clip, we will work to go a member of the community in which our clients reside. This will include community outreach and instruction.
Requirements stage was done by all 3 members of the squad by spliting up undertakings, so working with each other to finalise the demands. Final undertaking work was divided up by holding the database created and populated by Birendra, processs and maps developed by Mark and the undertaking certification and presentation done by Philip with each squad member working to finalise all aspects of the undertaking.
Energy Power Company provides electricity and natural gas service to clients across the province.
Customers can use either electrical service, gas service, or both services from Energy Power Company. Energy Power has regional location throughout the province, which contain call centres to track client outages. Each regional location consists of one to many service centres that are used to despatch crews to analyse and mend outages or intensify fixs to progress crews based on complexness, jeopardies, or environing concerns.
Rapid growing in residential places and commercial office infinites coupled with enhanced coverage demands for authorities bureaus are turn outing Energy Power Company ‘s current file based outage system needs to be replaced.
Mission Statement
The intent of Outage Management System ( OMS ) is to keep the informations related to clients power outages, outage frequence and declarations.
Mission Aims
Insert, update and delete informations on outages
Insert, update and delete informations on employees
Insert, update and delete informations on outage crews
Insert, update and delete informations on clients
Insert, update and delete informations on service centres
Perform hunts and study on outages
Perform hunts and study on employees
Perform hunts and study on outage crews
Perform hunts and study on clients
Perform hunts and study on service centres
Path position on outages
Track location on outage crews
Path outages by clients
Track size of service centres
Track outage recovery times by crews
Application Background
The database system being created is to back up an application for power outage direction. OMS is responsible for tracking the happenings and fixs of power outages. Anyone can name in to describe an outage. The outage is tracked one clip, nevertheless all calls to describe an outage must be recorded. While entering the outage, the user will garner information to help the public-service corporation company in deciding the outage such as the specific outage location, down lines, fires, fallen trees, and neighbours constructing observations. This information is used to make despatch records for field crews that they receive on remote laptops within their vehicles.
Choice users for the OMS system use specially designed positions of the informations to find the order in which crews are dispatched to outages every bit good as which type of crew is dispatched to each outage. Fires, fallen trees and down lines all must be categorized as jeopardies to let for specialised crews to be contacted and dispatched. Most outages require a trouble shooter to make the initial analysis. The trouble shooter can either repair the outage or make an order for another crew if the outage is beyond their ability to fix.
OMS needs to track all clients and their references. Each client reference is associated with a service centre. Crews are dispatched from each service centre and several service centres are contained in a part.
After the outage has been restored, the crew updates the record on their laptop. Another set of employees will so verify the information entered by the crew and supply extra inside informations based upon their cognition of the electrical grid and assorted other inside informations. This information is used subsequently to bring forth studies.
Data Definitions
Region
A defined country of the province that represents a big service country
Service centre
A defined country of a part that is serviced by a specific aggregation of crews
Outage Call Center
Department within the organisation that replies outage calls and opens initial outage item
Outage
Any event that obstruct power line to the client.
Employee
A individual employed in the OMS company in assorted functions
Dispatch record aka Outage Assignment
A record is created for any outage that was reported which is given to field crew for fix intent.
Troubleshooter
An employee who performs initial analysis of an outage. The trouble shooter can either repair the outage or make an order for another crew if the outage is beyond their ability to fix.
Field crew
An employee who performs the fix of an outage that could non be performed by a trouble shooter.
Customer
A individual that has an history with the power company but may besides be classified as a non-customer
Calls
A call received by a client that has been made to describe an outage or risky status
Outage Crew aka Crew
A specialised employee that has been trained to reconstruct power to clients and turn to the assorted jobs that may be
Troubleshoot Crew
Typically initial crew sent to find the ground for the outage and able to mend choice outage types.
Line Crew
Specific crew used to turn to downed lines
Forestry Crew
Specific crew used to turn to downed trees
Hazard
A status associated with an outage that requires specialised crews and/or equipment to fix.
Wire Hazard
Contains specific inside informations approximately jeopardies as it relates to toss off wires, etc
Transformer Hazard
Contains specific inside informations approximately jeopardies as it relates to transformers affected or impacting jeopardies such as transformer information on a fire.
Pole Hazard
Contains specific inside informations approximately jeopardies as it relates to poles. Pole information gathered will help in finding crews to despatch to mend downed/broken poles.
Customer Outages
Detailss that tracks the clients impacted by outages
Call Detail
Detailss about each call from assorted clients about outages.
This plan will be a departmental application. This plan excludes the endeavor related informations and the application. This plans tracks all the calls related to the outages within the part every bit good as all related outage informations. OMS will non track HR related maps, client payments, nor regional company informations.
Business Functions/Rules
OMS will track power outages.
Anyone can name in to describe an outage.
An outage is tracked one clip.
All calls to describe an outage must be recorded.
Outage location, down lines, fires, fallen trees, and neighbours edifice observations are tracked.
Fires, fallen trees and down lines all must be categorized as jeopardies.
OMS needs to track all clients and their reference.
Each client reference is associated with a service centre.
Crews are dispatched from each service centre and several service centres are contained in a part.
Outages can non be closed when it has unfastened jeopardies.
Enterprise Data Model Entities
Outages
Many clients may be impacted by one outage. A client may hold many outages. An outage may incorporate jeopardies.
Customer
Many clients may describe one outage. Non-customers may describe an outage. One client may describe one outage many times.
Service Centers
One Service Center contains many employees. Many Service Centers belong in a part.
Employee
One employee belongs to a service centre. One employee may be a member of a crew. One employee may manage many outages.
Enterprise Data Model
Functional Decomposition
Business Function to data Entity Matrix
Data Entity Types
Business Functions
Calls
Hazards
Customer
Outages
Region
Service Center
Crews
Employee
Customer Calls
Ten
Ten
Ten
Ten
Ten
Enter Outage Data
Ten
Ten
Ten
Ten
Ten
Dispatch
Ten
Ten
Ten
Ten
Ten
Ten
Analyze Outage Cause
Ten
Ten
Ten
Ten
Repair Outage
Ten
Ten
Ten
Ten
Outage Confirmation
Ten
Ten
Ten
Ten
Outage Coverage
Ten
Ten
Ten
Ten
Outage Data Gathering
Ten
Ten
Ten
Ten
Datas Care
Ten
Ten
Manage Service Center
Ten
Ten
Region
RegionID
RegionName
Address
ServiceCenter
ServiceCenterID
ServiceCenterName
Address
RegionID
Employee
EmployeeID
EmployeeName
Address
ServiceCenterID
crewleader
Customer
CustomerID
CustomerName
Address
ServiceCenterID
Telephone
transforferID
Calls
CallID
CustomerID
CallerPhone
OutageID
ServiceCenterID
WorkDescription
EmployeeID
NotifiedDate
Crews
CrewID
EmployeeID
CrewType
Outages
OutageID
OutageLocation
RestorationDate
ServiceCenterID
OutageType
CustomerOutages
OutageID
CustomerID
NotifiedFixed
CrewAssignment
OutageID
CrewID
Active
MaterialsRequired
VehicleRequired
Hazards
HazardID
OutageID
HazardType
Arching
Fire
Restoration
Date
NotifyPolice
NotifyFire
Rescue
Badness
Pole
HazardID
PoleID
PoleType
PoleCapacity
PoleTagNumber
PoleOwner
WildlifeProtection
Description
Wire
HazardID
WireID
WireDown
WireInsulation
Phase
Description
Transformer
HazardID
TransformerID
TransformerType
TransformerKVA
TransformerFeederLine
Description
Model Differences
Additional properties
Service Center
Added RegionID column. Was in original 3NF, missed on diagram.
Customer
Service Center ID. Was in original 3NF, missed on diagram.
Transformer ID. Added to show a part of complex informations used to track clients on the public-service corporation grid.
Employee
Service Center ID. Was in original 3NF, missed on diagram.
Crew Leader. Added to let for tracking crew leaders and let for coverage.
Calls
Added Work Description and EmployeeID from Call Detail tabular array.
Hazards – combined with Outage Hazard. Many to Many without linker due to limited usage, higher articulation and faster public presentation as 1 tabular array.
Added Restoration Date
Added Notified Police
Added Notified Rescue
Added Hazard Type
Pole – Added item to let for complex connection to data grid ( outside of range ) to automatically include clients in outages
Added Description
Added PoleID
Outages
Added ServiceCenterID column. Was in original 3NF, missed on diagram.
Added Restoration Date to let for tracking outage clip length.
Added Outage Type. Allows for non-customers naming in.
Transformer
Added Transformer ID to demo complex grid calculations that will automatically add clients to outages based on locations.
Tables removed
Call Detail
Combined with Calls. No ground to maintain offprint.
Work Log
Undertaking Proposal
Mark McArthey
Subscriber
Undertaking Proposal
Biren Yonjon
Subscriber
Undertaking Proposal
Philip Hauser
Subscriber
Requirement Specification – Application Scope
Philip Hauser
Writer
Requirement Specification – Data Definitions
Biren Yonjon
Writer
Requirement Specification – Detailed Requirements
Biren Yonjon
Writer
Requirement Specification – Enterprise Data Model
Mark McArthey
Writer
Requirement Specification – Function Matrix
Mark McArthey
Writer
Requirement Specification – Functional Decomposition
Philip Hauser
Writer
Requirement Specification – Application Scope
Biren Yonjon
Subscriber
Requirement Specification – Enterprise Data Model
Biren Yonjon
Subscriber
Requirement Specification – Function Matrix
Biren Yonjon
Subscriber
Requirement Specification – Functional Decomposition
Biren Yonjon
Subscriber
Requirement Specification – Application Scope
Mark McArthey
Subscriber
Requirement Specification – Data Definitions
Mark McArthey
Subscriber
Requirement Specification – Detailed Requirements
Mark McArthey
Subscriber
Requirement Specification – Functional Decomposition
Mark McArthey
Subscriber
Requirement Specification – Data Definitions
Philip Hauser
Subscriber
Requirement Specification – Detailed Requirements
Philip Hauser
Subscriber
Requirement Specification – Enterprise Data Model
Philip Hauser
Subscriber
Requirement Specification – Function Matrix
Philip Hauser
Subscriber
Database Design – EER
Mark McArthey
Writer
Database Design – EER Properties
Philip Hauser
Writer
Database Design – Logical Model
Biren Yonjon
Writer
Database Design – Map ER to dealingss
Biren Yonjon
Writer
Database Design – EER Properties
Mark McArthey
Subscriber
Database Design – Logical Model
Mark McArthey
Subscriber
Database Design – Map ER to dealingss
Mark McArthey
Subscriber
Database Design – EER
Philip Hauser
Subscriber
Database Design – Logical Model
Philip Hauser
Subscriber
Database Design – Map ER to dealingss
Philip Hauser
Subscriber
Database Design – EER
Biren Yonjon
Subscriber
Database Design – EER Properties
Biren Yonjon
Subscriber
DML and DDL
Biren Yonjon
Writer
DML and DDL
Mark McArthey
Writer
DML and DDL
Philip Hauser
Writer
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
