Introduction
Schantt is a production scheduling software designed for flowshop manufacturing environments such as food, beverage, pharmaceutical, and textile industries. The software helps you create optimized production schedules that minimize production time while meeting operational constraints.
Optimized schedules translate directly into operational benefits: reduced idle time, lower work-in-process inventory, and improved on-time delivery—supporting your continuous improvement initiatives.
Key Capabilities
- Create and manage production schedules with different levels of automation
- Visualize schedules through interactive Gantt charts
- Support multiple users working together in teams
- Share schedule Gantt charts with stakeholders via secure links
Prerequisites & Preparation
Setting up Schantt requires information about your production process. Gathering this data before you start will make configuration faster and more accurate. This section provides a comprehensive checklist and time estimates.
Information Checklist
Use this checklist to prepare before your first session. Items marked Required are needed for basic functionality; Recommended items improve schedule accuracy.
Production Flow (Required)
| ☐ | Item | Example | Notes |
|---|---|---|---|
| ☐ | List of production stages in sequence | Mixing → Filling → Labeling → Packaging | Include all stages products pass through |
| ☐ | Production type for each stage | Mixing (Batch), Filling (Flow) | Batch = fixed quantity/time; Flow = continuous rate |
| ☐ | Position/order of each stage | 1, 2, 3, 4... | Determines production flow direction |
Equipment (Required)
| ☐ | Item | Example | Notes |
|---|---|---|---|
| ☐ | Machine names at each stage | Mixer-A, Mixer-B, Filler-1, Filler-2 | Use identifiers your team recognizes |
| ☐ | For batch stages: batch size per machine | Mixer-A: 500 kg capacity | Maximum quantity per batch cycle |
| ☐ | For batch stages: cycle duration per machine | Mixer-A: 30 minutes per batch | Time to complete one batch |
| ☐ | For flow stages: throughput rate per machine | Filler-1: 1,200 bottles/hour | Units processed per hour |
Products (Required)
| ☐ | Item | Example | Notes |
|---|---|---|---|
| ☐ | Product class categories | "Soft Drinks", "Juices", "Waters" | Groups of products with similar characteristics |
| ☐ | Individual product names | Cola 500ml, Orange Juice 1L, Spring Water 330ml | Specific items you manufacture |
| ☐ | Unit of measure per product class | Liters, bottles, kg, units | Consistent unit for quantity tracking |
| ☐ | Stage routing per product class | "Soft Drinks" uses stages 1, 2, 3, 4 | Which stages each product class requires |
Timing Data (Recommended)
| ☐ | Item | Example | Notes |
|---|---|---|---|
| ☐ | Changeover times between product classes | Cola → Juice: 20 min; Juice → Cola: 15 min | Per machine, directional (A→B may differ from B→A) |
| ☐ | Transfer times between stages | Mixing → Filling: 10 minutes | Time to move material between stages |
| ☐ | Partial transfer quantities (if applicable) | Transfer 200 bottles at a time | For overlapping stage operations |
Time Investment Estimates
Plan your setup time based on facility complexity:
| Activity | Small Facility (3 stages, 5 products) | Medium Facility (5 stages, 15 products) | Large Facility (8+ stages, 30+ products) |
|---|---|---|---|
| Data Gathering | 30-60 minutes | 1-2 hours | 2-4 hours |
| Initial Configuration Stages, machines, products |
30-45 minutes | 1-2 hours | 2-4 hours |
| Parameter Setup Processing times, changeovers |
30-60 minutes | 1-2 hours | 2-4 hours |
| First Test Schedule | 15-30 minutes | 15-30 minutes | 30-60 minutes |
| Total Initial Setup | 2-3 hours | 4-6 hours | 8-12 hours |
Who Should Be Involved
Different team members contribute different knowledge:
Production Manager / Process Expert
- Process flow knowledge
- Equipment capabilities
- Changeover requirements
- Product routing decisions
Production Planner / Scheduler
- Current scheduling practices
- Pain points and constraints
- Product demand patterns
- Schedule validation
IT / Data Support
- Extracting data from existing systems
- API integration (Enterprise)
- Account administration
Preparation Checklist Summary
Before your first session, ensure you have:
- ☐ Production stage list with sequence positions and types (batch/flow)
- ☐ Machine list for each stage (equipment names)
- ☐ Processing parameters for each machine (batch size/cycle time or throughput rate)
- ☐ Product class and product list with units of measure
- ☐ Stage routing for each product class
- ☐ Changeover time estimates (at minimum)
- ☐ 1-2 hours of uninterrupted time for initial setup
- ☐ Access to production manager or process expert
Creating Your Team
When you sign up for Schantt, you can create a Team which serves as your organization's workspace. A team contains all your production data—stages, machines, products, and schedules—completely isolated from other teams.
To create a team:
- Sign up for an account at the registration page
- Enter your team name (or leave blank to use your email prefix)
- Accept the terms and conditions
- Click Sign Up
Your team will have a unique URL identifier (slug) automatically generated from your team name.
Understanding Subscriptions
Your capabilities in Schantt depend on your plan tier. Each tier determines:
- How many teams you can create
- How many users can join each team
- Resource limits for stages, machines, product classes, products, and schedules
Available Plans
| Feature | Demo (Free) | Standard | Premium | Enterprise |
|---|---|---|---|---|
| Teams per user | 1 | 1 | 5 | Custom |
| Users per team | 1 | 5 | 10 | Custom |
| Stages per team | 5 | 10 | 20 | Custom |
| Machines per team | 5 | 20 | 50 | Custom |
| Product Classes per team | 2 | 10 | 20 | Custom |
| Products per team | 5 | 100 | 200 | Custom |
| Schedules per team | 5 | Unlimited | Unlimited | Unlimited |
- The Demo tier is free and available for evaluation purposes.
- Contact sales for current pricing details on paid tiers.
- Standard subscriptions can only be assigned to one team at a time.
- Premium subscriptions can be used across multiple teams.
Team Settings
Access your team settings by clicking on your team name in the navigation menu.
Basic Settings
- Team Name: Your organization or workspace name displayed throughout the application
- Team ID (Slug): A unique URL-friendly identifier for your team (no spaces allowed). This appears in all your team's URLs.
- Select Subscription: Assign one of your purchased subscriptions to this team. Only team administrators can change this setting.
Team Preferences
Team preferences control how schedules are displayed in forms and Gantt charts. All team members share these preferences.
Gantt Chart Display Options:
- Initial Zoom: Default zoom level when viewing Gantt charts (Hour, Day, Week, or Month)
- Date Format: How dates are displayed in forms and Gantt charts
- Tasks Group Type: How tasks within a stage are grouped (Standard or Combine)
- Show Columns: Toggle visibility of Quantity, Machine, Start Date, End Date, and Duration columns
- Show Task Order: Display the production sequence number on Gantt chart bars
- Show Detail Box: Enable hover tooltips showing detailed task information
Managing Team Members
Teams support multiple users with role-based access control.
User Roles
| Role | Permissions |
|---|---|
| Administrator | Full access to all team features. Can manage stages, machines, products, product classes, and schedules. Can invite new members and manage team settings. |
| Member | Can create, view, update, and delete schedules. Cannot modify production setup (stages, machines, products, product classes). |
Inviting Team Members
- Navigate to your team's settings page
- Go to the "Team Members" section
- Enter the email address of the person you want to invite
- Select their role (Administrator or Member)
- Click "Invite"
The invited user will receive an email with a link to join your team. If they don't have a Schantt account, they will be prompted to create one.
Removing Team Members
Administrators can remove team members from the Team Members section. Removed users lose access to all team data immediately.
Switching Between Teams
If you belong to multiple teams (with Premium or Enterprise subscriptions), you can switch between them:
- Click on your current team name in the navigation menu
- Select the team you want to switch to from the dropdown
- You'll be redirected to that team's dashboard
Each team maintains completely separate data—stages, machines, products, and schedules are not shared between teams.
Deleting a Team
Only team administrators can delete a team. To delete:
- Navigate to team settings
- Scroll to the danger zone section
- Confirm the deletion
Understanding the Data Structure
Before creating schedules, you need to configure your production environment. Schantt uses a hierarchical data model to represent your production environment:
Team
├── Stages (production steps in sequence)
├── Machines (equipment at each stage, linked to Stages)
│ └── Machine Downtime (ad-hoc unavailability periods)
├── Calendars
│ ├── Calendar (weekly shift patterns per day)
│ └── Calendar Exceptions (team-wide date overrides)
│ └── Calendar Downtimes (date ranges of machines unavailability)
├── Product Classes (categories with shared characteristics)
│ └── Products (individual items to manufacture)
├── Production Parameters
│ ├── Processing Times / Throughput Rates (per Machine × Product Class)
│ ├── Changeover Times (per Machine × Product Class pair)
│ └── Transfer Times (per Stage pair)
└── Schedules
├── Calendar Periods (working calendar per date range)
└── Schedule Details (individual production tasks)
Stages
Stages represent the sequential steps in your production process. Each stage has a unique position number that determines its order in the production flow.
Creating a Stage
- Navigate to the Stages page from the main menu
- Click "Create" or use the "+" button
- Fill in the stage details:
- Name: A descriptive name (e.g., "Mixing", "Filling", "Packaging")
- Description: Optional notes about this stage
- Position: The order of this stage in your production sequence (1, 2, 3, etc.)
- Production Type: Choose between Batch or Flow (see below)
Production Types
| Type | Description | Example Equipment | Key Parameter |
|---|---|---|---|
| Batch | Processes fixed quantities in fixed time periods | Mixing tanks, fermentation vessels, autoclaves | Cycle duration (minutes per batch) and batch size |
| Flow | Material flows continuously at a rate | Filling lines, packaging lines, labeling machines | Throughput rate (units per hour) |
Examples:
- A mixing tank that processes 500kg batches in 30 minutes → Batch stage
- A filling line running at 1,200 bottles per hour → Flow stage
Machines
Machines are the equipment at each stage that perform the actual production work. Each machine belongs to exactly one stage.
Creating a Machine
- Navigate to the Machines page from the left navigation menu
- Click the "Create" button
- Fill in:
- Name: Equipment identifier (e.g., "Mixer-01", "Filler-A")
- Stage: Select which production stage this machine belongs to
- Description: Optional equipment notes
- Click "Save" to create the machine
Managing Machine Parameters
After creating a machine, you can configure its production parameters from the machine detail page:
- Processing Times (for Batch stages): Batch size and cycle duration per product class
- Throughput Rates (for Flow stages): Production rate per product class
- Changeover Times: Time required to switch between product classes
Calendar Assignment
Each machine can use a custom working calendar instead of the team default. Set this via the Calendar dropdown in the machine form. Leave blank to inherit the team default. See Calendars for how to define working hours.
Calendars
Schantt's calendar system lets you restrict scheduling to your facility's actual working hours. Instead of scheduling 24/7, you can define calendars (shift patterns), mark holidays, assign a specific calendar to any machine, and block downtimes.
Calendar
A Calendar defines the weekly shift pattern for your facility or a specific machine. Each calendar specifies which days of the week are working days and what hours the shift runs.
- One Calendar per team is designated as the Default Calendar, automatically applied to all new schedules.
- Machines can individually override the default by having a calendar assigned directly.
Creating a Calendar
- Navigate to Calendars from the main menu
- Click "Create"
- Set the name, optional description, and whether it is the team default
- Configure each day of the week: mark as working or non-working, and set shift start/end times
Machine Calendar Assignment
Each machine can optionally be assigned a specific calendar. When a machine has its own calendar, it overrides the team's default calendar for that machine's tasks. This is configured directly on the Machine detail page:
- Navigate to Machines → select a machine
- In the machine form, find the Calendar dropdown
- Select a calendar or leave blank to use the team default
Common use case: a packaging line that runs an extended shift (06:00–22:00) while mixing equipment only runs a standard shift (08:00–17:00).
Exceptions
Exceptions are team-wide date overrides that apply to all calendars simultaneously. Use them for:
- Holidays: Mark a normally-working date as non-working (factory closure)
- Overtime: Mark a normally-non-working date as working (Saturday overtime)
- Extended shift: Change shift hours for a specific date
Exceptions take precedence over the regular weekly pattern for the specified date, across every calendar in the team.
Creating an Exception
- Navigate to Calendars → Exceptions
- Click "Add Exception"
- Set the date, whether it is a working day, and (if working) the shift hours
- Optionally add a reason (e.g., "National Holiday", "Q4 overtime")
Downtimes
Downtime blocks a specific time window during which a machine (or all machines) is unavailable. Unlike Calendar Exceptions (which override specific dates in Calendars), downtime is a precise datetime-range event:
- Per-machine downtime: Only that machine is affected
- Factory-wide downtime: Leave machine blank — all machines are affected during that window
- Categories: Maintenance, Breakdown, Cleaning, Other
Downtime periods are also visualized on the Gantt chart.
Creating Downtime
- Navigate to a Machine detail page → Downtime tab, or use the factory-wide Downtime management page
- Click "Add"
- Set start and end datetime, category, and optional reason
Calendar Resolution Order
- Downtime can make a machine unavailable regardless of calendar.
- Machine-specific calendar overrides both Schedule Calendar Period and the team default calendar.
- Matching Schedule Calendar Period applies next.
- Team default calendar is the fallback.
- If none exist, schedule is 24/7.
Calendar exceptions apply within calendar-driven steps (2-4) and override the day-of-week pattern for a specific date.
Preparing Calendar Data
Before creating your first schedule, gather:
| ☐ | Item | Example |
|---|---|---|
| ☐ | Shift start/end times per day | Mon–Fri 08:00–17:00 |
| ☐ | Which days are non-working | Saturday, Sunday |
| ☐ | Upcoming holidays | May 1 = National Holiday |
| ☐ | Machine-specific shift differences | Filler runs 06:00–22:00 |
| ☐ | Planned maintenance windows | Mixer-A offline Apr 20 08:00–12:00 |
Product Classes
Product Classes group products with similar characteristics. Products in the same class share the same production routing (which stages they pass through) and similar processing requirements.
Creating a Product Class
- Navigate to the Product Classes page
- Click "Create"
- Fill in:
- Name: Category name (e.g., "Beverages", "Tablets", "T-Shirts")
- Description: Optional notes
- Unit: The unit of measure for products in this class (e.g., "liters", "units", "pieces", "kg")
Setting Up Stage Routing (Required Stage Routing)
After creating a product class, you must specify which stages products in this class will pass through. This is called the Required Stage Routing.
- On the Product Class detail page, find the "Required Stage Routing" section
- Add each stage that products in this class should go through
- Configure partial transfer settings for each stage (see below)
- Product Class A might route through stages 1→3→5
- Product Class B might route through stages 2→4
- Product Class C might route through stages 3→5
The algorithm automatically handles these routing differences when creating schedules.
Partial Transfer Settings
For each stage in the routing, you can configure partial transfers:
- Allow Partial Transfer: Enable to allow material to move to the next stage before the current operation completes
- Partial Transfer Quantity: How many units transfer at a time (required if partial transfers are enabled)
When to use partial transfers:
- Flow stages where items can move individually (e.g., filled bottles moving to labeling)
- Batch stages where partial quantities can be released (e.g., cooling tanks releasing product incrementally)
When NOT to use partial transfers:
- Batch stages that must complete fully before any transfer (e.g., fermentation, sterilization)
- "No-wait" processes common in bakeries where timing is critical
Products
Products are the individual items you manufacture. Each product belongs to exactly one product class and inherits its routing and characteristics.
Creating a Product
- Navigate to the Products page
- Click "Create"
- Fill in:
- Name: Product name (e.g., "Cola 500ml", "Aspirin 100mg", "Blue T-Shirt XL")
- Description: Optional product notes
- Product Class: Select the class this product belongs to
- Color: Choose a display color for Gantt chart visualization
Production Parameters
Production parameters define how long operations take and setup times between products. These are configured per machine for each product class.
Processing Time (Batch Stages)
For batch-type stages, configure:
- Navigate to the Product Class detail page
- Find the "Processing Time" section
- Add entries specifying:
- Stage: Which batch stage
- Machine: Which machine at that stage
- Cycle Duration: Time in minutes to process one batch
- Batch Size: Number of units per batch
Example:
- Product Class "Beverages" at Stage "Mixing" on Machine "Mixer-01"
- Cycle Duration: 30 minutes
- Batch Size: 500 liters
This means mixing 500 liters of any beverage takes 30 minutes. Mixing 1,000 liters requires 2 batches = 60 minutes.
Throughput Rate (Flow Stages)
For flow-type stages, configure:
- Navigate to the Product Class detail page
- Find the "Throughput" section
- Add entries specifying:
- Stage: Which flow stage
- Machine: Which machine at that stage
- Throughput: Units processed per hour
Example:
- Product Class "Beverages" at Stage "Filling" on Machine "Filler-A"
- Throughput: 1,200 bottles per hour
This means filling 600 bottles takes 30 minutes, 1,200 bottles takes 60 minutes.
Changeover Time
Changeover time is the setup time required when switching from one product class to another on the same machine.
- Navigate to the Machine detail page (via Stage page)
- Find the "Changeover Times" section
- Add entries specifying:
- From Product Class: What was produced previously
- To Product Class: What will be produced next
- Duration: Setup time in minutes
Transfer Time
Transfer time is the time required to move material between stages in your facility. This is a property of your physical layout, not products.
- Navigate to the Stage detail page
- Find the "Transfer Times" section
- Add entries specifying:
- From Stage: Origin stage
- To Stage: Destination stage (must be later in sequence)
- Duration: Transport time in minutes
- Notes: Optional description (e.g., "Conveyor belt", "Forklift transport")
Example:
- From "Mixing" to "Filling": 15 minutes (pumping through pipes)
- From "Filling" to "Packaging": 5 minutes (conveyor belt)
Configuration Status and Scheduling Readiness
Before creating schedules, verify your configuration is complete. The application provides visual indicators:
Product Class Configuration Status
Each Product Class shows:
- Ready for Scheduling (green badge): All required stages have machine configurations
- Not Ready (yellow badge): Some stages are missing machine configurations
Click "More Details" to see exactly which stage-machine combinations need configuration.
Stage Configuration Status
Each Stage shows:
- Processes X/Y Product Classes: How many product classes can be processed at this stage
Click "More Details" to see which product classes are configured and which need attention.
Troubleshooting Common Setup Issues
This section addresses common problems you may encounter during setup and schedule creation, with step-by-step solutions.
Configuration Issues
"Product Class Not Ready for Scheduling"
Symptom: Product Class detail page shows "Not Ready" badge, and products in this class cannot be scheduled.
Cause: Missing processing time (for batch stages) or throughput rate (for flow stages) configuration for one or more stage-machine combinations in the product class routing.
Solution:
- Go to the Product Class detail page
- Click "More Details" in the Configuration Status section
- Review the stage-by-stage breakdown to identify missing configurations
- For each missing stage-machine combination:
- Batch stages: Add Processing Time (cycle duration and batch size)
- Flow stages: Add Throughput Rate (units per hour)
- Verify the badge changes to "Ready for Scheduling"
"No machines available at stage"
Symptom: Error when creating schedule, or certain products cannot be added.
Cause: The product class routing includes a stage that has no machines, or no machines with configured processing parameters for this product class.
Solution:
- Check the stage referenced in the error
- Navigate to that Stage's detail page
- Verify at least one machine exists at this stage
- If machines exist, verify the Product Class has processing parameters configured for at least one of them
- Add missing machines or processing parameters as needed
Stage doesn't appear in product class routing options
Symptom: When setting up Required Stage Routing for a Product Class, a stage you need is not listed.
Cause: The stage may not exist, or may have been deleted.
Solution:
- Navigate to the Stages list page
- Verify the stage exists and has the correct position number
- If the stage doesn't exist, create it
- Return to Product Class and add the stage to routing
Schedule Creation Issues
Schedule optimization fails or takes very long
Symptom: Progress bar stalls, timeout error, or extremely long processing time.
Possible Causes & Solutions:
- Too many products: Schedules with 30+ products take longer. Consider splitting into multiple schedules.
- Browser timeout: For large schedules, ensure you stay on the page during processing. Refreshing will cancel the operation.
- Missing configuration: Verify all products in the schedule have complete configuration (no "Not Ready" warnings).
Start time constraints cannot be satisfied (Semi-Auto mode)
Symptom: Error message indicating start time constraints conflict with each other or with schedule start time.
Cause: The specified start times are impossible to achieve given:
- Processing durations of earlier products
- Machine availability
- Transfer times between stages
Solution:
- Review your start time constraints for logical consistency
- Ensure constraint times are after the schedule start time
- Verify earlier products in the sequence can complete before constrained products must start
- Consider removing some constraints and letting the algorithm optimize timing
- If specific times are required, ensure sufficient time gaps between constrained products
Gantt chart shows unexpected gaps
Symptom: Large empty spaces appear in the Gantt chart where you expected continuous processing.
Explanation: Gaps are usually legitimate and reflect real-world constraints:
- Material waiting: A downstream stage cannot start until materials arrive from the upstream stage. This is realistic behavior.
- Changeover time: Setup time between different product classes. Verify your changeover times are accurate.
- Machine allocation: A machine may be idle while processing another product at a different stage.
If gaps seem excessive:
- Enable "Show Detail Box" in Team Preferences and hover over adjacent tasks to understand timing
- Consider enabling partial transfers to allow stage overlap
- Review if batch sizes are creating artificial delays
- Check if transfer times are overestimated
Changeover times not applying correctly
Symptom: Expected changeover time is not appearing between tasks, or wrong duration shows.
Possible Causes:
- Same product class: Changeover only applies when switching between different product classes. Same class = no changeover.
- Wrong direction: Changeover from A→B may differ from B→A. Check both directions are configured.
- Wrong machine: Changeover times are configured per machine. Verify the configuration is on the correct machine.
- Missing configuration: If changeover is not configured for a specific transition, it defaults to zero.
Solution:
- Navigate to the Machine detail page (via Stage)
- Find the Changeover Times section
- Verify the "From Product Class" and "To Product Class" match your schedule's product sequence
- Add missing changeover configurations as needed
Product not showing in schedule form dropdown
Symptom: A product you created doesn't appear in the product selection dropdown when creating a schedule.
Possible Causes:
- Wrong team: You may be logged into a different team. Check the team name in the navigation bar.
- Not saved: The product may not have been saved successfully. Check the Products list.
- Product class not ready: If the product's class is not ready for scheduling, the product may be filtered out.
Solution:
- Verify you're in the correct team
- Go to Products list and confirm the product exists
- Check the product's Product Class is "Ready for Scheduling"
- If not ready, complete the Product Class configuration first
Manual Mode Issues
Machine dropdown doesn't show expected machines
Symptom: In Manual mode, after selecting a product and stage, the machine dropdown doesn't show all machines at that stage.
Cause: Manual mode filters machines to only show those with processing parameters configured for the selected product's class.
Solution:
- Go to the Product Class detail page for the selected product
- Add processing time or throughput configuration for the missing machine
- Return to the schedule form—the machine should now appear
"End time must be after start time" error
Symptom: Validation error when saving a Manual mode schedule.
Cause: The end time specified for a task is the same as or earlier than the start time.
Solution:
- Review the start and end times for all tasks
- Ensure end time is later than start time for every task
- Pay attention to date changes (e.g., task spanning midnight)
"Why does my Gantt chart show shaded gray bands?"
Shaded overlays highlight calendar and downtime constraints applied to the schedule.
- Non-working calendar time (solid subtle gray)
- Downtime windows (factory-wide and machine-specific; muted striped overlays)
- Exception-added working time (green tint with dotted borders)
- Exception-removed working time (red dashed/striped overlay)
These bands are informational — tasks are already placed around them. If the bands seem wrong:
- Check the Calendar Periods assigned to this schedule (visible in the Schedule Summary)
- Verify the calendar's shift hours match your actual operation
- Check for any Machine Downtime entries that might be unexpected
- Remember overlays can come from either schedule calendar periods or the team default calendar fallback
Still Having Issues?
If you can't resolve your issue with the guidance above:
- Demo Plan Users: Review the Glossary and Production Scheduling Guide for additional context
- Standard/Premium Users: Contact support via the Contact page with details of the issue
- Enterprise Users: Reach out to your dedicated support contact
Understanding Scheduling Modes
Schantt offers three scheduling modes to accommodate different levels of automation and control:
| Mode | User Provides | System Determines | Best For |
|---|---|---|---|
| Auto | Products, quantities, start time | Optimal sequence, machines, timing | Maximum automation, trusting the algorithm |
| Semi-Auto | Products, fixed sequence, quantities, optional start times | Machines, timing within constraints | When you know the preferred order but want optimized machine selection |
| Manual | Everything: products, sequence, machines, start/end times | Validation only | Complete control, specific requirements |
Creating a Schedule
- Navigate to the Schedules page
- Click "Create" and select your preferred mode
- Fill in the schedule details (varies by mode)
- Add products to the schedule using the form
- Click "Save" to generate the schedule
Calendar Periods
Calendar Period assign a Calendar to a specific date range within a schedule. This tells the algorithm which shift hours apply for that portion of the schedule.
- You can define multiple non-overlapping calendar periods, each with a different calendar. Useful for schedules spanning a shift change or a holiday period.
- If no Calendar Periods are defined, the system checks your team's default calendar as a fallback.
- If no default calendar exists either, the schedule runs 24/7.
- Your team's default calendar is shown above the formset — click its name to view its configuration.
Typical setup:
- Add a single calendar period covering your entire schedule date range
- Assign your team's default calendar to it
- The algorithm will now respect shift hours when placing tasks
Auto Mode
You provide:
- Schedule name and description (optional)
- Schedule start date and time
- List of products with quantities (in any order)
The system:
- Determines the optimal production sequence
- Selects the best machine at each stage
- Calculates all start times, end times, and durations
- Creates a complete schedule minimizing total production time
Form fields:
- # (Position): Automatically assigned after optimization
- Product: Select from your configured products
- Quantity: Amount to produce
Semi-Auto Mode
You provide:
- Schedule name and description (optional)
- Schedule start date and time
- Fixed sequence of products with quantities
- Optionally: specific start times for any products in the sequence
The system:
- Preserves your specified sequence (no reordering)
- Enforces any start time constraints you specify
- Selects optimal machines within these constraints
- Calculates timing for all operations
Form fields:
- # (Position): Shows your specified sequence order
- Product: Select product for this position
- Quantity: Amount to produce
- Start Time: (Optional) When this product must start processing
Start Time Constraints:
- Leave blank for automatic timing
- If specified, the product MUST start at exactly that time
- If constraints create conflicts (impossible to achieve), the system will report an error
Manual Mode
You provide everything:
- Schedule name and description (optional)
- Position in production sequence (job number)
- Product selection for each position
- Quantity for each product
- Stage selection (from product's routing)
- Machine selection (from stage's machines)
- Start time and end time for each operation
The system:
- Validates your inputs (routing compatibility, machine availability)
- Stores your exact specifications
- Displays the Gantt chart exactly as you defined it
Form fields:
- Position: Job number in production sequence (you control this)
- Product: Select product
- Quantity: Amount to produce
- Stage: Select from product's required stages
- Machine: Select from stage's compatible machines
- Start: When this operation begins
- End: When this operation ends
Validation:
- End time must be after start time
- Product must be compatible with selected stage (from routing)
- Machine must be at the selected stage
Viewing Schedule Results
After creating or saving a schedule, you'll see:
- Schedule Summary: Name, mode, start time, duration, products included
- Schedule Details Table: All operations with products, quantities, stages, machines, and timing
- Gantt Chart: Visual timeline showing all operations
Gantt Chart Features
- Zoom Controls: View by hour, day, week, or month
- Task Bars: Color-coded by product, showing duration
- Hover Details: Mouse over a bar to see full operation details (if enabled in team preferences)
- Columns: Configurable display of quantity, machine, start/end times, duration
- Calendar components: Non-working periods (nights, weekends, holidays, machine downtime) are visualized on the Gantt chart. These reflect calendar constraints applied during scheduling.
Interpreting Your Gantt Chart
The Gantt chart is your primary tool for understanding and communicating production schedules. This section explains how to read the visual elements and identify patterns that indicate optimization opportunities.
Understanding Visual Elements
Task Bars
Each colored bar represents a single production task (one product at one stage on one machine):
| Visual Property | What It Represents | How to Read It |
|---|---|---|
| Bar Length | Processing duration | Longer bars = longer processing time. Compare relative lengths to identify time-intensive operations. |
| Bar Color | Product identity | Each product has a unique color (configurable). Same color = same product across stages. |
| Horizontal Position | When the task occurs | Left edge = start time; Right edge = end time. Use the timeline ruler at top for exact times. |
| Vertical Position (Row) | Stage and Machine | Each row represents a specific stage-machine combination. Tasks on the same row use the same machine. |
| Task Number (if enabled) | Position in production sequence | Shows the job's order (1st, 2nd, 3rd...). Useful for tracking specific products through stages. |
Gaps and Spaces
Empty space between bars provides important information about your schedule:
| Gap Type | Likely Cause | What to Consider |
|---|---|---|
| Small gap between tasks on same machine | Changeover time | This is normal when switching between different product classes. Verify changeover times are accurate. |
| Large gap before a task starts | Waiting for material from previous stage | The upstream stage hasn't finished yet. Consider partial transfers to overlap operations. |
| Gap at start of machine's timeline | Machine waiting for first job | May indicate a bottleneck elsewhere or suboptimal machine assignment. |
| Extended gap mid-schedule | Material flow constraint | Downstream stage waiting for upstream. Check if batch sizes or transfer settings need adjustment. |
Overlapping Bars (Different Rows)
Vertical overlap (bars at the same time on different rows) indicates parallel processing:
- Normal and desirable: Multiple machines working simultaneously improves throughput
- Shows good utilization: Idle machines indicate potential for improvement
- Cross-stage overlap: When enabled with partial transfers, stages can process simultaneously
Common Patterns and Their Meaning
Pattern 1: Bottleneck Stage
What it looks like: One stage shows all machines constantly busy with minimal gaps, while other stages have significant idle time.
What it means: This stage is limiting overall throughput. All other stages wait for this one.
Potential actions:
- Add another machine at the bottleneck stage
- Reduce batch sizes to improve flow
- Enable partial transfers to allow downstream stages to start sooner
- Review if processing times are accurate (might be overestimated elsewhere)
Pattern 2: Staircase Pattern
What it looks like: Tasks form a diagonal "staircase" from top-left to bottom-right, with each stage starting after the previous one completes.
What it means: Sequential processing with full transfers—each stage waits for complete material from the previous stage.
Potential actions:
- Consider enabling partial transfers where appropriate
- This pattern is correct for processes requiring full completion (e.g., sterilization)
Pattern 3: Frequent Small Gaps
What it looks like: Many small gaps between tasks on the same machine throughout the schedule.
What it means: Frequent changeovers between different product classes.
Potential actions:
- The algorithm already minimizes this—verify changeover times are accurate
- Consider if product classes can be grouped differently
- Review if some changeover times could be reduced operationally
Pattern 4: One Machine Heavily Loaded, Others Idle
What it looks like: At a multi-machine stage, one machine is constantly busy while others have significant idle time.
What it means: Possible causes include:
- Different machines have significantly different throughput rates
- Changeover optimization favoring one machine
- Product class restrictions limiting which machines can be used
Potential actions:
- Verify processing time/throughput configuration for all machines
- Ensure all product classes are configured for all capable machines
Using Hover Details
When "Show Detail Box" is enabled in Team Preferences, hovering over any task bar displays:
- Product name: Which product this task produces
- Quantity: How many units are being processed
- Stage: Which production stage
- Machine: Which specific machine
- Start time: When processing begins
- End time: When processing completes
- Duration: Total processing time
Adjusting the View
Customize your Gantt chart view for different purposes:
| Purpose | Recommended Settings |
|---|---|
| Detailed analysis | Hour zoom, all columns visible, detail box enabled |
| Production floor posting | Day zoom, show start/end times and machines, task order enabled |
| Management overview | Day or week zoom, hide detailed columns, focus on timeline |
| Schedule comparison | Same settings for both schedules, note total duration difference |
Key Metrics to Review
After creating a schedule, check these metrics in the Schedule Summary:
- Total Duration (Makespan): Time from schedule start to completion of last task. Lower is better.
- Number of Products: Verify all products you entered are included
- Start and End Times: Confirm these align with your operational requirements
Compare these metrics when evaluating different schedules or before/after configuration changes.
Editing Schedules
You can update existing schedules:
- Navigate to the schedule you want to edit
- Make your changes in the form
- Click "Save"
Mode-Specific Behavior:
- Auto/Semi-Auto modes: Changing products, quantities, or constraints triggers re-optimization
- Manual mode: Changes are saved directly without optimization
Basic field updates (name, description, share setting) do not trigger re-optimization in any mode.
Background Processing
For schedules with many products or complex constraints, optimization may take longer. During this time:
- A progress indicator shows the current status
- The system processes your schedule in the background
- You'll see the results when optimization completes
Progress phases:
- Preparing schedule data
- Optimizing production sequence (may show improvement percentage)
- Finalizing results
- Displaying schedule
Deleting Schedules
To delete a schedule:
- Open the schedule you want to delete
- Click the delete button (trash icon)
- Confirm the deletion
Glossary
| Term | Definition |
|---|---|
| Team | An organizational workspace containing all production data |
| Batch Stage | A production stage that processes materials in fixed-size batches with a set cycle time |
| Flow Stage | A production stage where materials flow continuously at a throughput rate |
| Throughput | Processing rate measured in units per hour (for flow stages) |
| Product Class | A category grouping products with similar routing and characteristics |
| Required Stage Routing | The sequence of stages a product class must pass through |
| Partial Transfer | Moving completed units to the next stage before the current operation fully completes |
| Changeover Time | Setup time required when switching production from one product class to another on a machine |
| Transfer Time | Time to move material between stages in your facility |
| Calendar | A named weekly shift pattern defining which days and hours each day are working time |
| Working Hours | The shift hours defined in a Calendar for a given day, within which production tasks are scheduled |
| Calendar Exception | A team-wide date override that replaces the regular weekly pattern for a specific date (e.g., holiday, overtime) |
| Calendar Downtime | An ad-hoc datetime window during which a specific machine (or all machines) is unavailable |
| Calendar Period | An assignment of a Calendar to a date range within a Schedule |
| Position | A job's place in the production sequence |
| Makespan | Total time from schedule start to completion of all operations |
| Gantt Chart | Visual timeline diagram showing production operations |
Frequently Asked Questions
General Questions
How long does it take to set up Schantt for my facility?
Two phases to consider:
Phase 1: Gathering Prerequisites (30 minutes to several hours)
Before using Schantt, you need to gather your production data. This includes documenting:
- Your production stages and equipment
- Products you manufacture
- Processing times and throughput rates
- Setup/changeover times between products
- Material transfer times
For a small facility with 3-5 stages and 5-10 products, this typically takes 30-60 minutes if you gather data efficiently. Larger facilities may require 2-4 hours. See Prerequisites & Preparation for a detailed checklist.
Phase 2: Configuration + First Schedule (approximately 60 minutes)
Once you have your production data ready, configuring Schantt and creating your first schedule takes about an hour:
- Creating stages and machines: 15-20 minutes
- Setting up product classes and products: 15-20 minutes
- Configuring production parameters: 15-20 minutes
- Creating your first schedule: 10-15 minutes
Total time with prerequisites: Expect 1-5 hours depending on your facility size and how quickly you can gather production data.
Can I try Schantt before committing to a paid plan?
Yes! Our Demo plan is completely free with no time limit. It includes limited capacity for stages, machines, product classes, products, and schedules—enough to evaluate the software with your actual production data. No credit card required to sign up.
What happens to my data if I cancel my subscription?
Your data remains in our system but editing becomes restricted. If you cancel:
- You revert to Demo plan limits
- Existing data is preserved but you cannot create new items beyond Demo limits
- You can upgrade again at any time to restore full access
We do not automatically delete any production data when you cancel.
Is my production data secure?
Yes, we take data security seriously:
- Encryption in transit: All data is transmitted over HTTPS (TLS 1.2+)
- Encryption at rest: Database storage is encrypted
- Isolation: Each team's data is completely isolated from other teams
- Access control: Only your team members can access your data
- No third-party sharing: We do not sell or share your production data
Can multiple people work on the same schedule?
Teams support multiple users, but for schedules:
- We recommend only one person edits a schedule at a time
- There is no real-time collaboration—if two people edit simultaneously, one may overwrite the other's changes
- Different team members can create and manage separate schedules simultaneously without conflict
Can Schantt integrate with my ERP system?
Integrations are a key part of our product roadmap. Please contact us with your specific needs and see how they fit into our development roadmap.
Scheduling Questions
How long does optimization take?
Optimization time depends on several factors including number of products, number of stages, number of machines, and processing complexity.
Simpler schedules optimize quickly (often under a minute), while more complex configurations may take several minutes.
Schantt provides a real-time progress indicator that shows optimization status and improvement percentage during processing.
Can I schedule the same product multiple times in one schedule?
Yes, you can add the same product multiple times with different quantities. Each entry is treated as a separate job in the production sequence.
Example: If you need to produce Cola at the start and end of the day with other products in between, add Cola twice with the appropriate quantities.
What if my products don't all go through the same stages?
Schantt fully supports flexible routing. Each Product Class can have its own Required Stage Routing that defines exactly which stages those products pass through.
- Products can skip stages in your facility's sequence
- Products can start at intermediate stages (not just the first)
- Products can end at earlier stages (not just the last)
The algorithm automatically handles these routing differences when creating schedules.
Can I set specific start times for certain products?
Yes, in Semi-Auto mode. You can specify start time constraints for any or all products in your schedule. The algorithm will:
- Respect your specified start times as hard constraints
- Optimize machine selection within those constraints
- Calculate timing for all other operations
Leave the start time field blank for products where you want the algorithm to optimize timing automatically.
Why does my schedule show gaps between tasks?
Gaps in the Gantt chart are usually legitimate and reflect real-world constraints:
- Changeover time: Setup time when switching between different product classes
- Material waiting: Downstream stage waiting for materials from upstream stage
- Machine availability: Machine processing another job at a different stage
Enable "Show Detail Box" in Team Preferences to hover over tasks and understand timing. See Interpreting Your Gantt Chart for more details.
Getting Help
For additional assistance:
- Demo Plan Users: Refer to this Documentation and Guides
- Standard/Premium Users: Email support available
- Enterprise Users: Dedicated support staff
Contact information is available on the Contact page.