Input Data Guide

---

Overview

The Delivery Schedule Optimization application requires several input data tables to function. All data should be provided in Excel format using the provided template.

Required Input Tables

1. Settings

Contains global planning parameters:

• plan_start_date: Start date of the planning horizon
• plan_horizon_length: Number of days to plan for
• shipping_rules: JSON configuration for different order types

2. Demand

Contains customer order information:

• demand_id: Unique identifier for each order
• site_name: Customer location
• product_name: Product ordered
• demand_date: Date when order was received
• demand_quantity: Order quantity
• demand_type: Type of order (e.g., "urgent", "batch")

3. Product

Contains product information:

• product_name: Product identifier
• unit_measure: Unit of measurement
• unit_volume: Volume per unit

4. Outbound Site (Warehouses)

Contains warehouse information:

• site_name: Warehouse identifier
• capacity_ub: Daily capacity upper bound
• latitude: Warehouse latitude
• longitude: Warehouse longitude

5. Inbound Site (Customers)

Contains customer location information:

• site_name: Customer identifier
• latitude: Customer latitude
• longitude: Customer longitude

6. Transportation Policy

Contains shipping rules and costs:

• origin_site_name: Warehouse identifier
• destination_site_name: Customer identifier
• transportation_mode: Mode of transportation
• cost: Cost per unit
• moq: Minimum order quantity for this route

7. BOH Inventory (Optional)

Contains beginning-of-horizon inventory:

• site_name: Warehouse identifier
• product_name: Product identifier
• inventory_quantity: Available quantity

8. En Route Inventory (Optional)

Contains in-transit inventory:

• site_name: Warehouse identifier
• product_name: Product identifier
• eta_date: Expected arrival date
• inventory_quantity: Quantity in transit

Data Requirements

General Rules

1. All identifiers must be unique within their respective tables
2. Dates must be in YYYY-MM-DD format
3. Numeric values must be non-negative
4. All required fields must be filled

Specific Requirements

1. Demand

   • demand_type must match types defined in shipping rules
   • demand_date must be within planning horizon
   • demand_quantity must be positive

2. Transportation Policy

   • cost must be non-negative
   • moq must be non-negative
   • All warehouse-customer pairs must have a policy

3. Sites

   • Coordinates must be valid (latitude: -90 to 90, longitude: -180 to 180)
   • Warehouse capacities must be positive

Excel Template

A template file (input_sample_delivery_schedule.xlsx) is provided with:

• Pre-formatted sheets for each input table
• Example data
• Data validation rules
• Required column headers

Common Issues

1. Missing required fields
2. Invalid date formats
3. Duplicate identifiers
4. Invalid coordinates
5. Negative quantities or costs
6. Missing transportation policies

Best Practices

1. Validate data before upload
2. Use consistent naming conventions
3. Keep product and site master data up to date
4. Review transportation policies regularly
5. Include all relevant inventory information