MAG OptiAI

SchedAI Input Specs

SchedAI Service Input Specs

Publish a reusable Service Profile, then prepare a dated Service Scenario manually or upload one guided Excel workbook. Travel values can be estimated from coordinates and a configurable average speed; supplied values and overrides are preserved.

Back to Input SpecsResources Hub

Overview

Use this guide to prepare valid input files for this workspace. Review the required files, exact column names, example rows, and common formatting rules before uploading.

Required files

2

Optional files

2

Spec sections

1

Upload section

One guided Excel planning workbook

Download the profile-specific workbook from Step 2 Bulk import. Customer Locations and Dated Visits require data rows. Travel Times and Availability Exceptions are optional. Instructions and Choices provide guidance and published reference names. CSV and multi-file bundles are not supported.

Open Service to download guided Excel

Required sheet

Customer Locations

One row per customer site in the dated Service Scenario. Depots come from the published Service Profile.

Requirements

Required columns

  • Location ID
  • Location Name

Conditionally required columns

  • Latitude
  • Longitude

Optional columns

No optional columns documented for this file.

Value rules and examples

  • Location ID must be unique and must not conflict with a published depot ID.
  • Latitude (-90 to 90) and Longitude (-180 to 180) are required for a site whose missing travel values will be estimated. Zero coordinates are valid.

Example CSV table

Location IDLocation NameLatitudeLongitude
CLINIC-1King Street Clinic43.6532-79.3832

Required sheet

Dated Visits

One row per dated job. Repeated visits can use the same customer location.

Requirements

Required columns

  • Visit ID
  • Visit Name
  • Location
  • Date
  • Earliest Start
  • Latest Start
  • Duration Minutes
  • Required Skills

Optional columns

  • Priority
  • Mandatory
  • Preferred Technicians
  • Disallowed Technicians
  • Maximum Tardiness Minutes

Value rules and examples

  • Location references a customer site in Customer Locations; skills and technicians reference the published profile Choices.
  • Use YYYY-MM-DD dates and HH:MM or AM/PM clocks. Start windows cannot cross midnight.
  • Duration Minutes must be positive whole minutes aligned with the profile resolution. Semicolons separate multiple skills or technicians.
  • Visit IDs must be unique.

Example CSV table

Visit IDVisit NameLocationDateEarliest StartLatest StartDuration MinutesRequired Skills
VISIT-1Electrical inspectionKing Street Clinic2026-10-1209:0011:0060Electrical

Optional sheet

Travel Times — optional overrides

Leave this sheet empty to estimate travel from coordinates after upload. Supplied directed values are preserved.

Requirements

Conditionally required columns

  • From Location
  • To Location

Optional columns

  • Travel Minutes
  • Travel Distance KM

Value rules and examples

  • A supplied row identifies From Location and To Location using IDs or names from the published depots or customer sites.
  • Travel Minutes and Travel Distance KM may be blank for estimation; supplied numbers must be finite and non-negative.
  • A→B and B→A are independent. Keep one row per direction; diagonal values must be zero.
  • Choose Estimate travel from coordinates, configure average speed, preview and apply before analysis. Generated values are estimates, not road or traffic times.

Example CSV table

From LocationTo LocationTravel MinutesTravel Distance KM
Central dispatchKing Street Clinic178.5
King Street ClinicCentral dispatch2712.5

Optional sheet

Availability Exceptions

Override normal availability for a specific technician and date. Do not repeat every technician here.

Requirements

Conditionally required columns

  • Technician
  • Date

Optional columns

  • Available Start
  • Available End
  • Ends Next Day

Value rules and examples

  • Use a technician from the published profile Choices and a date within the confirmed planning horizon.
  • Empty available times mean a full-day absence. If a window is supplied, fill both Available Start and Available End; Ends Next Day permits a single overnight window.

Example CSV table

TechnicianDateAvailable StartAvailable EndEnds Next Day
Alex Chen2026-10-1210:0018:00No

Common mistakes

  • Uploading the old multi-file CSV routing bundle instead of one guided Excel workbook.
  • Leaving coordinates blank for locations that need estimated travel.
  • Treating coordinate estimates as road-network or traffic predictions.
  • Repeating a travel direction or using unmatched location/skill/technician names.

Quick rules

  • Technicians, skills, depots and normal work rules belong to the published Service Profile, not separate upload files.
  • Set depot coordinates in Step 1 and customer coordinates in this workbook when estimating missing travel.
  • After import, configure average speed in km/h, preview and apply coordinate estimates. Missing coordinates leave unresolved travel values.
  • Changing speed updates only generated estimates; supplied values and manual overrides remain unchanged.
  • Save working draft preserves unfinished data. Analyze and validate checks all current planning inputs before Save ready creates an immutable scenario version.

Navigate

Keep the right guide close by

Pair this upload guide with the product page for workflow context or the resources hub for related public material.

Input Specs indexResources hub

Navigate

Keep the right input guide close

Return to the input-spec library for another upload contract, or go back to the resource hub for quickstarts, how-to guides, and use cases.

Back to Input SpecsBack to Resources