Brief
In this project I was asked to come up with an operational concept for a complex scheduling system client on a tight deadline.
The following System requirements was defined:
1. Tasks are requested from several coordinator level user and will be executed by operator level users, both need to be able to access the scheduler display
2. Each task requires personnel and resources (from a limited pool) in order to be accomplished
3. Both coordinators and operators can resolve scheduling conflicts (operators can only resolve conflicts that related to them)
1. Tasks are requested from several coordinator level user and will be executed by operator level users, both need to be able to access the scheduler display
2. Each task requires personnel and resources (from a limited pool) in order to be accomplished
3. Both coordinators and operators can resolve scheduling conflicts (operators can only resolve conflicts that related to them)
The assumption was that an existing smart scheduling solution will be used on the server side.
Working with this assumption I suggested a concept that automatic scheduling will be processed by the system based on available time spots resources and personnel.
The prototype below demonstrate the scenarios that will need user interaction with the system:
Requesting a task to be scheduled
Resolve conflicts in case the system cannot schedule the task automatically
If the prototype is not displayed it can also be seen here
Achievements
Using design system (that I was defining for another project) to quickly creating high detailed level concepts 
