|
One-to-One
Scheduling
Paradigm
LabScheduler matches available
technologists with workstations that require their time.
|
The system supports a one-to-one
scheduling paradigm in which, at any given time, a single resource
can do only one activity, with the activity possibly (but not
necessarily) involving a resource of the other type. |
|
For example, during a
given time period, a single technologist is either working at
exactly one workstation, available to be scheduled, sick, or
on vacation. A work-station is either assigned to a technologist,
waiting to be assigned, down for repair, or down for maintenance.
(You can define these statuses to suit your own laboratory.)
Technologist and workstation
activities are stored in the schedule database as schedule events.
A single schedule event specifies a resource (a technologist
or a workstation, but not both), a time interval (start time
and end time or duration), a status (a name that describes the
type of event), and an event weight (priority).
To form a schedule, technologist
events are linked to appropriate workstation events. Appropriate
assignments are those in which both events occupy the same time
period and share compatible event statusessuch as available
for a technologist event and vacant for a workstation
event.
For
step-by-step information on "How LabScheduler Works",
click here. |