pg&e’s power database for self-generators team 4 salina cheung, tim lee, marc oman, avani...

PG&E’s Power Database

for Self-Generators

Team 4

Salina Cheung, Tim Lee, Marc Oman, Avani Shah, Ognen Stojanovski, Sam Wang, Lucas Yun-Nikolac

http://www.pge.com/index.shtml

BACKGROUND

California Energy Crisis• In 2000, demand for electricity grew far faster than expected, significantly outstripping supply

• A PG&E program that allows customers to install their own solar or wind energy generators

• Current paper-based application process is inefficient & potentially costly

• Key objectives: speed, accuracy, tracking

E-NET

BACKGROUND EER RELATIONAL SCHEMA NORMALIZATION FORMS QUERIES

ENHANCED ENTITY RELATIONSHIP

PersonBackup Contact

Contractor

Customer

o

Engineering & Planning

Employee

d

GIS Manager

GIS Clerical

Field Tester

Equipment

solarwind

o

Application PROJECTfor New meter

Manufacturer

approves inspects visitssets

deadline

manages schedules inspection

registers ascomplete

buys fromserves as

represented by

finds

contacts

submitsneeds

makes

made bymade by

sells

utilizes (0,N)

(1,N)

(1,1)

(0,N)

(0,1)

(0,1)

(0,1)

(1,N)

(1,N)

(0,1)(0,N)

(0,N)

(0,N)

(1,N)

(1,N)

(1,N)

(1,N)

(1,2)

(1,1)

(0,N)

(0,N)

(0,N)

(0,N)

(1,N)

(1,N)

(1,N)

(1,N)

(0,N) (0,N)

(1,1) (1,1)

(1,N)

(1,N)

(1,N)

(0,N)

(0,N)(0,N) (0,N)(0,N)

(1,N) (1,N)

Vendor

works with

(0,N)


RELATIONAL SCHEMA


NORMALIZATION


Sample Relation Currently in 1NF

WIND (windID15,made_by4, turbine_model, turbine_rating, no_turbines)

Possible Conversion to 3NF:WIND (windID15, made_by4, turbine_model)NO_TURBINES (windID15, no_turbines)TURBINE_RATING (made_by4, turbine_model, turbine rating)

TESTER_VISIT (project1, field_tester9, date_review_requested, actual_review_date, results, comments)

CONTACTS_WITH_CUSTOMER (manager6, customer11, date, reason_for_contact, means_of_contact)

Example Relations Currently in 3NF


FORMS

Purpose


APPLICATION FORECAST

SELECT 0.15*Count([APPLICATION_DATES]![Initial Component received])+(1-.15)*[ExpQuery]! [Expr1] AS [Forecast]

FROM APPLICATION_DATES, [Exp Query]

WHERE (((APPLICATION_DATES.[Initial Component received]) Between #5/1/2000# And

#5/31/2000#))

GROUP BY [Exp Query].Expr1;

SQL

Provides information to PG&E management to prepare for any necessary workforce addition and/or reallocation


Purpose

CUSTOMER SERVICE

Allows PG&E and its customers to identify the most popular generator type and manufacturer of installation in each region SQ

LSELECT [PROJECT].[Area], "SOLAR" AS TYPE, [SOLAR].[Made by], Count([SOLAR].[Made by]) AS [CountOfMade by]

FROM PROJECT INNER JOIN ((EQUIPMENT INNER JOIN SOLAR ON [EQUIPMENT].[Equipment ID]=[SOLAR].[Solar ID]) INNER JOIN PROJECT_USES_EQUIPMENT ON [EQUIPMENT].[Equipment ID] = [PROJECT_USES_EQUIPMENT].[Equipment]) ON [PROJECT].[Utility LogNumber]= [PROJECT_USES_EQUIPMENT].[Project]

GROUP BY [PROJECT].[Area], [SOLAR].[Made by];

UNION

SELECT [PROJECT].[Area], "WIND" AS TYPE, [WIND].[Made by],

Count([WIND].[Made by]) AS [CountOfMade by]

…..

…..

GROUP BY [PROJECT].[Area], [WIND].[Made by];


Provides important E-Net program statistic and trend illustration to PG&E management, policymakers, and consumers for future decision-making

Purpose

E-NET PROGRAM CONTRIBUTION

SQLSELECT DatePart("m",[Initial Component received]) AS [Month], DatePart("yyyy",[Initial

Component received]) AS [Year], Sum(EQUIPMENT.[Nameplate rating]) AS [SumOfNameplate rating]

FROM GIS_MANAGER_APPROVAL, (PROJECT INNER JOIN APPLICATION_DATES ON PROJECT.[Utility Log Number] = APPLICATION_DATES.[Project ID]) INNER JOIN (EQUIPMENT INNER JOIN PROJECT_USES_EQUIPMENT ON EQUIPMENT.[Equipment ID] = PROJECT_USES_EQUIPMENT.Equipment) ON PROJECT.[Utility Log Number] = PROJECT_USES_EQUIPMENT.Project

WHERE (((GIS_MANAGER_APPROVAL.Complete_date) Is Not Null))GROUP BY DatePart("yyyy",[Initial Component received]),

DatePart("m",[Initial Component received])ORDER BY DatePart("yyyy",[Initial Component received]) DESC ,

DatePart("m",[Initial Component received]) DESC;


Purpose

BOTTLENECK IDENTIFICATION

Identifies the greatest bottlenecks of the application process so PG&E may improve upon its greatest deficienciesSQ

LSELECT "GIS Clerical Completeness Check" as Process_Name, AVG(((Complete_date-Start_date)-1)/1) as Avg_Percentage_Deviation, (SUM(MeanTime)/10) as Mean_Processing_Time

FROM GIS_CLERICAL_COMPLETENESS_CHECKWHERE ((((Complete_date-Start_date)-1)/1)>0.3)UNION…..…..UNION SELECT "Tester Inspection Scheduling" as

Process_Name, AVG(((Complete_date-Start_date)-2)/2) as Avg_Percentage_Deviation, (SUM(MeanTime)/10) as Mean_Processing_Time

FROM TESTER_INSPECTION_SCHEDULINGWHERE ((((Complete_date-Start_date)-2)/2)>0.3);


Purpose

Allows PG&E to inform its applicants of the steps most likely resulting in application failure and how they could address these issues

SQL

INSPECTION FAILURE

SELECT PS.Step_Full_Name AS Process_Name, COUNT(PS.Step_Code) AS

Number_of_Failed_Application_at_each_ProcessFROM PROJECT AS P, PROCESS_STEPS AS PSWHERE P.Project_status="F" And PS.Step_Code=P.Failed_stepGROUP BY PS.Step_Full_NameORDER BY COUNT(PS.Step_Code) DESC;

Distribution of the Number of Application Failure in each Month

0

2

4

6

8

10

12

14

16

Jan Feb March April May June July Aug Sept Oct Nov Dec

Month

# o

f F

ail

ed

Ap

pli

ca

tio

n

INSPECTION FAILURE


pg&e’s power database for self-generators team 4 salina cheung, tim lee, marc oman, avani...

Documents