Introduction: Global Computer Solutions (GCS) is an information technology consulting company with many offices

through-out the United States. The GCS has contact us to design a database so GCS managers can keep track of their
customers, employees, projects, project schedules, assignments and invoices.

Writing by:

Sheila DeLaney, Rudy Draeger

Page 1
Detail information regarding reports | forms.

Forms

CUSTOMER INFORMATION FORM (Form to allow input new customers, customer id assigned with phone number
for new projects)

EMP SKILL FORM (Form to input employee names with skills and skill level)
EMPLOYEE INPUT FORM (Form to add new employees first, initial, last name plus hire date with region area)
PROJECT CONTRACT FORM (Form to assign project, company name, contract dates with budge)
PROJECTDETAIL FORM (Form to assign required task to specific project by ID number)
REGION INPUT FORM (Form allowing new input for region or change)
WORKLOG INPUT FORM (Form to allows employee to enter work log information regarding each project)

REPORTS

Bill to customer Report (Billing report for the customer)

Project Detail Report (Project Detail report showing the task that are done and when)
Project Report (Project report showing what type of skills needed and how many employees to assign)
Project task reports (Project task report show how much is completed)
Skills and Employee Name (Skills by employee name)

Page 2
Table CUSTOMER data

CUSTOMER table List of all the customers with GCS that has either a signed contract or possible contract to be signed. The
customer table provides detail for CUS_ID, CUS_NAME, CUS_PHONE, REGION_ID).

Customer table is used to assign projects to specific employees based on the skills required and level of skills plus region.
The primary key is the CUS_ID within this table.
Index is built on the CUSTOMER table, called CUSTOMERindex, the field name is CUS_NAME for faster search.

Page 3
Page 4
Table EMPLOYEE data

EMPLOYEE table - List of GCS employees and what region he/she works in to better assign for projects. The table includes the
following fields EMP_ID, EMP_LNAME, EMP_INITIAL, EMP_FNAME, EMP_HIRDATE, REGION_ID.

The EMPLOYEE table is a list of GCE employee names, with assigned employee id, and date hired including the region in which the
employee is located in.
The primary key is EMP_ID.
Index is built on the EMPLOYEE table, called EMPLOYEEindex, the field name is EMP_LNAME, EMP_FNAME, REGION_ID for faster
search.

Page 5
Page 6
Table REGION data

REGION table is a list of regions to allow the company to assign the correct employee with the right project. REGION table has
REGION_ID, REGION_NAME.

Contains a list of regions to allow the company to assign the correct employee with the right project.
REGION_ID as the primary key.
No index built on this table. Only have six regions for this company.

Page 7
Page 8
Table SKILL data

SKILL TABLE is a list of skills offered by the company GCS and the rate table based on the level of experience. The table has
SKILL_ID, SKILL_DESCRIPTION, SKILL_RATE.

The primary key is the SKILL_DESCRIPTION.

No index built on this table. Only have 23 SKILLS for this company.

Page 9


Page 10
Table EMPSKILLS data

EMPSKILLS table is a list of employee names, employee number and their skill levels. The table has EMPSKILLS_ID,
EMPSKILLS_SKILLIDNAME, EMPSKILLS_EMP_ID, and EMPSKILLS_EMPNU.

EMPSKILLS table is used to assign employees based on the skill level needed for a project. It can cross with the skill table to get the rate per
hour charge.
There is no primary key is this table, because an employee can have many skills, and a single skill can have many employees.
Index is built on the EMPSKILLS table, called EMPSKILLSindex, the field name is EMPSKILLS_SKILLIDNAME, EMPSKILLS_EMP_ID
for faster search.

Page 11
Page 12
Table PROJECTCONTRACTHEADER data information

PROJECTCONTRACTHEADER table has the information regarding the project and it will be used during the billing process.

The table has PROJECTCONTRACT_PROJECTID, PROJECTCONTRACT_DESCRIPTION, PROJECTCONTRACT_COMPANYID,

PROJECTCONTRACT_CONTRACTDATE, PROJECTCONTRACT_REGION, PROJECTCONTRACT_STARTDATE,
PROJECTCONTRACT_ENDDATE, PROJECTCONTRACT_BUDGE.

PROJECTCONTRACHEADER table is linked with the CUSTOMER table, by the PROJECTCONTRACT_PROJECTID and CUS_ID. It
contains header information and is linked to the PROJECTDETAIL table and BILL table for information needed.
The primary key being the PROJECTCONTRACT_PROJECTID.
No index built on this table.

Page 13
Page 14
Table PROJECTDETAIL data

Table PROJECTDETAIL has information of PROJECTID, PROJECTSTARTDATE, PROJECTENDDATE, PROJECTDESCRIPTION,

PROJECTSKILLS_REQUIRED1, PROJECT_QTYREQUIRED1, PROJECTSKILLS_REQUIRED2, PROJECT_QTYREQUIRED2,
PROJECTSKILLS_REQUIRED3, PROJECT_QTYREQUIRED3, PROJECTSKILLS_REQUIRED4, PROJECT_QTYREQUIRED4.

This table contains information about what the required skills are needed to complete the contract but also how many programmers need to be
assigned for the project. What are the start dates and project end date request?
No primary key because more than one employee is assigned to this project and also it is possible to have more than one employee working
on the same job skill for the same project.
Index is built on the PROJECTDETAIL table, called PROJECTDETAILindex, the field name is PROJECTTASKDESCRIPTION,
PROJECTSKILLS_REQUIRE1, PROJECTSKILLS_REQUIRED2, PROJECTSKILLS_REQUIRED3, PROJECTSKILLS_REQUIRED4 for
faster search.

Page 15
Page 16


Table WORKLOG data

The WORKLOG Table Table includes the following fields, WORKLOG_EMPID, WORKLOG_EMPLOYNAME, WORKLOG,
WEEKENDDATE, WORKLOG_PROJECTID, WORKLOG_TOTALHOURSWORKED, WORKLOG_BILLNU.

Contains information about specific information on who is working on what piece of the project, how many hours are worked. On the 15th
and 30th of each month billing cycle is run and will use information from the work log to determine what will be charged to the customer
based on completed work. Then the program will update the worklog file for the worklog_bill_nu field.
No primary key because more than one employee is working on the same job skills, and more than one employee is working on the same
project. After the 15th and the 30th of each month billing cycle is run, possible the WORKLOG_BILLNU is updated with a number stating it
was charged to the customer.
Index is built on the WORKLOG table, called WORKLOGindex, the field name is WORKLOG_IMPID, WORKLOG_BILLNU for faster
search.

Page 17
Page 18
Table PROJECTTASK data information

The PROJECTTASK table PROJECTTASK_IDNUMBER, PROJECTTASK_PROJECTTASK, PROJECTTAS_STARTDATE,

PROJECTTAST_ENDDATE, PROJECTTAST_SKILL1, PROJECTTASK_EMPLOYEE1, PROJECTTASK_EMPSTARTDATE,
PROJECTTASK_EMPENDDATE.

Contains information about specific employees working on specific pieces of projects at a given time. Note that one employee can only be
assigned to one assignment at a time.
No primary key
Index is built on the PROJECTTASK table, called PROJECTTASKindex, the field name is PROJECTTASK_IDNUMBER,
PROJECTASK_PROJECTASK, PROJECTASK_SKILL1 for faster search.

Page 19


Page 20
Table BILL data

The BILL table This table contains the following field information BILL_DATE, BILL_PROJECTID,
BILL_PROJECT_CONTRACTNAME, BILL_PROJECTIDNUMBER, BILL_PROJECT_NAME, BILL_SUBTITLE,
BILL_SUBTITLEEMPNAME, BILL_STARTDATE, BILL_ENDDATE, BILL_WEEKENDDATE, BILL_HOURSWORKED,
BILL_RATEBILLABLE, BILL_SKILLNAME, BILL_SUMAMTDUE, BILL_GRANDTOTAL
Contains billing information regarding during the billing cycle how much to charge the customer based on the progress of the completion of
the project.
No primary number
No index on table.

Page 21
Page 22