employee scheduling database

[Guest]

I am trying to create a scheduling database for multiple locations. ex: I
have 10 locations. Not all locations are open all the time, it is event and
attendance driven. I know how to set an employee to a specific location. I
have set up an employee table, and a event information table, and a location
table.

How can I set a location to have a status of open for event "A" and schedule
employee "a" to work. I would also like to incorporate an employee
availability table.

any suggestions?

 

[Tom Ellison]

Dear Dan:

I think this is going to need a lot of clarification.

"Not all locations are open all the time"

You mean they open and close at various hours of various days? If so, what
does this have to do with the application?

"it is event and attendance driven."

So there are events occurring at various locations at irregular periods of
time?

"a[n] event information table"

So, are events "one time" things, with a start date and time, and an ending
date and time, or do the recurr?

Is one event something that occurs at only one location? Are employees
assigned to a location, or do they work at several, or all locations?

What do you expect a "status of open" to mean? If an event is scheduled at
a location, I would thing there is a beginning and ending date/time for the
event. It would be "open" between those times.

This is extremely fuzzy. I hope your thinking is very, very clear about
this. Don't start designing tables until you know what the mechanisms are
(unless you are very, very experienced and can take on a large project in
pieces, making sure all the parts will fit.)

Tom Ellison

 

[Guest]

Lets see if this clarifies: It is for a concession department for an NHL
arena. So for a NHL hockey game all locations are open, all staff work.
Thats the simple part. When there are other events such as a concert or
lacross, not all concession kiosks are open,not all staff work. It varies
based on projected attendance. The arena is not open all the time. Every
thing can be closed down for weeks at a time. Typically staff are assigned
to work a certain location, but some staff "float" and work where they are
needed. It is not a typical mon-fri 9-5 type job, days of the week vary as
well as the hours worked.

I am not concerned with overtime or other things which would affect a
typical schedule. I want to track employee information, kiosk information,
and event information. The 3 things seperate seem simple enough, but I am not
sure how to relate them .

Hopefully this clarifies what I want. Thanks for your help.
--
Dan

Dear Dan:

I think this is going to need a lot of clarification.

"Not all locations are open all the time"

You mean they open and close at various hours of various days? If so, what
does this have to do with the application?

"it is event and attendance driven."

So there are events occurring at various locations at irregular periods of
time?

"a[n] event information table"

So, are events "one time" things, with a start date and time, and an ending
date and time, or do the recurr?

Is one event something that occurs at only one location? Are employees
assigned to a location, or do they work at several, or all locations?

What do you expect a "status of open" to mean? If an event is scheduled at
a location, I would thing there is a beginning and ending date/time for the
event. It would be "open" between those times.

This is extremely fuzzy. I hope your thinking is very, very clear about
this. Don't start designing tables until you know what the mechanisms are
(unless you are very, very experienced and can take on a large project in
pieces, making sure all the parts will fit.)

Tom Ellison

I am trying to create a scheduling database for multiple locations. ex: I
have 10 locations. Not all locations are open all the time, it is event
and
attendance driven. I know how to set an employee to a specific location.
I
have set up an employee table, and a event information table, and a
location
table.

How can I set a location to have a status of open for event "A" and
schedule
employee "a" to work. I would also like to incorporate an employee
availability table.

any suggestions?

 

[Guest]

Looks like you need at least four tables: Events, EventLocations, Locations,
and Employees.

tbl_Events
EventID (PK)
EventInfo, etc.

tbl_Locations
LocationID (PK)
LocationInfo, etc.

tbl_Employees
EmployeeID (PK)
EmployeeInfo, etc.

tbl_EventLocations
EventLocationsID (PK)
EventID
LocationID
EmployeeID
EventLocationInfo, etc.

Each event will be a unique record, probably with date and time information.
Locations will just be a list of all possible kiosks. Employees are all of
your possible employees. These will all be tied to EventLocations, which
will have a record for each kiosk location that is tied to a particular
event, along with the employee who will be working the kiosk.

Lets see if this clarifies: It is for a concession department for an NHL
arena. So for a NHL hockey game all locations are open, all staff work.
Thats the simple part. When there are other events such as a concert or
lacross, not all concession kiosks are open,not all staff work. It varies
based on projected attendance. The arena is not open all the time. Every
thing can be closed down for weeks at a time. Typically staff are assigned
to work a certain location, but some staff "float" and work where they are
needed. It is not a typical mon-fri 9-5 type job, days of the week vary as
well as the hours worked.

I am not concerned with overtime or other things which would affect a
typical schedule. I want to track employee information, kiosk information,
and event information. The 3 things seperate seem simple enough, but I am not
sure how to relate them .

Hopefully this clarifies what I want. Thanks for your help.
--
Dan

Dear Dan:

I think this is going to need a lot of clarification.

"Not all locations are open all the time"

You mean they open and close at various hours of various days? If so, what
does this have to do with the application?

"it is event and attendance driven."

So there are events occurring at various locations at irregular periods of
time?

"a[n] event information table"

So, are events "one time" things, with a start date and time, and an ending
date and time, or do the recurr?

Is one event something that occurs at only one location? Are employees
assigned to a location, or do they work at several, or all locations?

What do you expect a "status of open" to mean? If an event is scheduled at
a location, I would thing there is a beginning and ending date/time for the
event. It would be "open" between those times.

This is extremely fuzzy. I hope your thinking is very, very clear about
this. Don't start designing tables until you know what the mechanisms are
(unless you are very, very experienced and can take on a large project in
pieces, making sure all the parts will fit.)

Tom Ellison

I am trying to create a scheduling database for multiple locations. ex: I
have 10 locations. Not all locations are open all the time, it is event
and
attendance driven. I know how to set an employee to a specific location.
I
have set up an employee table, and a event information table, and a
location
table.

How can I set a location to have a status of open for event "A" and
schedule
employee "a" to work. I would also like to incorporate an employee
availability table.

any suggestions?