ER Diagram Help

[ranasingh1984]

I was wondering if you could help me with a current issue I am having whilst developing an ER diagram. The problem I am having is with identifying the correct Entities. The scenario I am trying to complete is given below. I have also included a list of entities which I think are needed, however I do not know if these are correct, could you suggest any possible entities and whether the ones I have identified are correct. I have also suggested a few possible relationships please could you assist me in determining whether these are correct.

SCENARIO
A heavy equipment hire company wishes to create a database to monitor the hiring of equipment to clients. The company has two types of equipment: power tools, such as drills and vacuum cleaners, and plants such as excavators and rollers. Power tools are described by their model and the voltage they use, whereas plants are classified by their model and their size in tonnes. The company has various outlets and each outlet has staff including a Manager and several Senior Technicians who are responsible for supervising the work of allocated groups of Technicians. Each outlet has a stock of equipment for hire that may be hired by clients for various periods of time, from a minimum of four hours to a maximum of six months. Each hire agreement between a client and the company is uniquely identified by using a hire number. The company insists that a client must take out an insurance cover for each equipment hire period. Each piece of equipment is checked for faults when it is returned by the client.

The Entities I have identified are as follows:

Equipment
Power Tools
Plants
Company
Outlets
Manager
Senior Technician
Technicians
Client
Hire
Hire agreement
Insurance

Company has * (many) equipment
Equipment has *(many) plants
Equipment has * power tools
Company has 1..* (many) outlets
Outlet has 1..1 manager
Outlet has * (many) senior technicians
Outlet has * (many) technicians
Outlet has for hire * (many) equipment
Outlet has * (many) clients
Client can hire 1..* (one to many) Equipment
Client can have 1..* (one to many) Hire Agreements
Client can have 1..* (one to many) insurance
Hire can have * (many) Hire Agreements
Hire Agreement has * (many) Insurance

As you may have established I am new to the field of ER Diagrams so I apologise for waffling on.

I will be grateful for any help

Regards

[schumaj]

The business rules listed are not the structural ones and have to be programmed in by the implementer of the database, you just have to list them.

Business rules:
The company insists that a client must take out an insurance cover for each equipment hire period.
Each piece of equipment is checked for faults when it is returned by the client.
Each outlet has a stock of equipment for hire that may be hired by clients for various periods of time, from a minimum of four hours to a maximum of six months.

Your entities are:

EQUIPMENT
PEOPLE
LOG (which is an intersection entity between EQUIPMENT and CLIENT)
OUTLET
LOCATION
JOB

In EQUIPMENT:
#ID
*Model
SUBTYPES:
POWER_TOOLS
*Voltage
PLANTS
*Size

In PEOPLE:
#ID
*lname
*fname
*DOB
manager_id
job_id (fk References job_id of JOB)
location_id (fk References id of LOCATION)

In LOCATION:
#id
*name

In JOB:
#id
* name

In LOG:
# hire_number
* client_ID
* equipment_ID

If you need help with the relationships, ask, but the one between the subtypes in the EQUIPMENT entity will go to the LOG entity as an arc. It would be easier for me to draw it rather than type it all out.

[lich]

The business rules listed are not the structural ones and have to be programmed in by the implementer of the database, you just have to list them.

Business rules:
The company insists that a client must take out an insurance cover for each equipment hire period.
Each piece of equipment is checked for faults when it is returned by the client.
Each outlet has a stock of equipment for hire that may be hired by clients for various periods of time, from a minimum of four hours to a maximum of six months.

Your entities are:

EQUIPMENT
PEOPLE
LOG (which is an intersection entity between EQUIPMENT and CLIENT)
OUTLET
LOCATION
JOB

In EQUIPMENT:
#ID
*Model
SUBTYPES:
POWER_TOOLS
*Voltage
PLANTS
*Size

In PEOPLE:
#ID
*lname
*fname
*DOB
manager_id
job_id (fk References job_id of JOB)
location_id (fk References id of LOCATION)

In LOCATION:
#id
*name

In JOB:
#id
* name

In LOG:
# hire_number
* client_ID
* equipment_ID

If you need help with the relationships, ask, but the one between the subtypes in the EQUIPMENT entity will go to the LOG entity as an arc. It would be easier for me to draw it rather than type it all out.

wow. this gives more info about ER. even im learning about it. thanks a lot

[emadali]

hi every one , this is intersted scenario , so can any one help to drow the ERD and make the normalization? , quicly plzzzzzzzz

[cjcorbet]

I have the same problem...
i am stuck on this big ERD and cant figure it out... and help will be greatly appreciated...
Thank You

Adamco Property Management manages rental property for the owners of the properties. Adamco manages all types of property ranging from small commercial properties to apartments to houses. In each case, the owner of property signs a contract for each individual property with Adamco which Adamco will manage. Someone wishing to lease a particular property from Adamco will sign a lease for a specific period of time. Adamco refers to the person leasing the property as a client.

Adamco has multiple offices in the Southeastern United States and each property is assigned to a particular office. Each office has a staff that includes an office manager, one or more assistant managers, and a varying number of agents. Some of the offices are quite large and but others are quite small. Adamco opens new offices as needed but also sometimes closes an office that is not sufficiently busy. Each employee of Adamco has a unique employee number and is assigned to a specific office and has a designated supervisor unless the employee is an office manager. In addition, Adamco maintains the usual information about each agent (name, address, SSN, etc.).

Each owner whose property Adamco manages is assigned a unique identification number and contact information about the owner is kept. A single owner may have more than one property that they will want Adamco to manage and there will be a separate contract for each property.. Each property is also given a unique identified and is assigned to a specific office for management. Details of the property (type, description, status, address, current rental price, etc.) are kept for each property.

Every client of Adamco also has a unique identifier. Adamco keeps other relevant data (name, contact information, etc.) about the client. Each lease that a client signs for a property will have a beginning and ending lease date, and lease price. Each lease also is associated with the particular Adamco employee who set up and manages the lease. The leases follow a standard format with all client and Adamco responsibilities clearly specified.

[ashwaa]

The business rules listed are not the structural ones and have to be programmed in by the implementer of the database, you just have to list them.

Business rules:
The company insists that a client must take out an insurance cover for each equipment hire period.
Each piece of equipment is checked for faults when it is returned by the client.
Each outlet has a stock of equipment for hire that may be hired by clients for various periods of time, from a minimum of four hours to a maximum of six months.

Your entities are:

EQUIPMENT
PEOPLE
LOG (which is an intersection entity between EQUIPMENT and CLIENT)
OUTLET
LOCATION
JOB

In EQUIPMENT:
#ID
*Model
SUBTYPES:
POWER_TOOLS
*Voltage
PLANTS
*Size

In PEOPLE:
#ID
*lname
*fname
*DOB
manager_id
job_id (fk References job_id of JOB)
location_id (fk References id of LOCATION)

In LOCATION:
#id
*name

In JOB:
#id
* name

In LOG:
# hire_number
* client_ID
* equipment_ID

If you need help with the relationships, ask, but the one between the subtypes in the EQUIPMENT entity will go to the LOG entity as an arc. It would be easier for me to draw it rather than type it all out.

Ccould you help me to draw ER-modeling for this , please ?

[mtto44]

could you help me to draw ER-modeling for this , please ?