| |
| AutoScheduler Functions: |
| |
 |
| |
| AutoScheduler Functions: Collect Data: |
| |
- Connect to the host inventory and order systems
- Minimize impact on “live” system
- Extract data in the format AutoScheduler is expecting
- Makes AutoScheduler somewhat host-independent
- Stable during system changes
|
| |
| AutoScheduler Functions: Knowledge Base: |
| |
- All inputs and outputs are stored locally
- Need feeds from OMS and planning system
- AutoScheduler uses a standard database
- ODBC / SQL access for other applications (OMS and RTCIS)
|
| |
| AutoScheduler Functions: Conflict Resolution: |
| |
- Re-allocate resources, or increase resource level at critical times
- Cut or substitute “short” items
- Allow increased work-ahead buffer or deadline stretching
- Re-organize warehouse space
|
| |
| AutoScheduler Functions: Suggested Activities: |
| |
- Project plan for all tasks
- Loading and unloading
- Trailer moves
- Suggested doors and staging locations
- Extra inventory required
- Dual task & cross-dock opportunities
|
| |
| AutoScheduler Functions: Resource Usage Summaries: |
| |
- Comparison of available resources to planned usage for all resources
- Case pickers
- Loaders & unloaders
- Trailer moves
- Warehouse space
- Doors
|
| |
| AutoScheduler Functions: Problems Needing Resolution: |
| |
- Early warning system
- Need more resources
- Inventory missing
- No trailer
- Need more space
- The operator can change inputs or “rules” and re-run to see if problem is resolved
|
| |
 |
 |
