Why IoD Scheduling Requires a Strategy
Bandwidth scheduling sounds simple: drop the tier at night, raise it in the morning. But enterprise environments have complications — global teams across time zones, irregular workloads, maintenance windows, and month-end processing spikes. Without a deliberate approach, you end up with manual overrides, missed windows, and circuits running at the wrong tier.
This guide covers the scheduling patterns that work best for enterprise IoD deployments.
Pattern 1: Business Hours Baseline
The most common pattern. Define two bandwidth levels:
- • **Peak (on-peak):** Full provisioned tier during core business hours (e.g., 7:30am–6:30pm local time, Mon–Fri)
- • **Off-peak:** Reduced tier overnight and weekends (e.g., 25–30% of peak bandwidth)
Buffer your transitions by 15–30 minutes before the actual peak window starts. API orders take seconds to complete, but building in a buffer accounts for edge cases.
Pattern 2: Workload-Aligned Scheduling
More granular than business hours. Schedule around specific workloads:
- • **Nightly backups:** Spike to maximum tier from 11pm–3am, then drop back
- • **End-of-month batch jobs:** Raise tier on the last business day of each month
- • **Video conferencing peaks:** Raise tier for recurring all-hands or board meetings via M365 calendar sync
The M365 calendar sync in Apptifi’s Core + M365 plan makes the last point automatic — when a large meeting appears on your network calendar, the bandwidth tier is pre-staged.
Pattern 3: Maintenance Window Scheduling
IoD can be used to temporarily reduce bandwidth during planned maintenance windows to avoid unnecessary traffic. Schedule a low tier for the maintenance window duration and return to normal immediately after.
Common Pitfalls to Avoid
Pitfall 1: Overlapping orders. If a scheduled event and a manual order conflict, the most recent API submission wins. Always check for pending events before manual overrides.
Pitfall 2: Forgetting time zone alignment. If your scheduling tool is in UTC but your circuit is in Chicago, a 9am business hours schedule will fire at the wrong time. Confirm your scheduler’s time zone settings before going live.
Pitfall 3: Not testing in sandbox first. IoD providers offer sandbox environments. Test your scheduling logic against the test API before applying to production circuits. Apptifi includes built-in sandbox mode for exactly this purpose. The same sandbox mode covers [Lumen Ethernet on Demand](/features/ethernet-on-demand) (EoD) circuits, so you can validate Layer 2 EVC scheduling alongside IoD without touching production.
Pitfall 4: Under-provisioning during spikes. Scheduling a low overnight tier but forgetting about a 3am disaster recovery test or a global team working across time zones can cause performance issues. Build override rules for known exceptions.
Using M365 Calendar Sync
The Microsoft 365 calendar sync integration allows Apptifi to read events from designated calendars and pre-stage bandwidth changes. This is particularly powerful for:
- • Network-heavy events (video productions, all-hands meetings, large file transfers)
- • Known maintenance windows managed through IT service calendars
- • Conference room booking integrations where video conferencing bandwidth needs to scale
Configure which calendars to monitor and what bandwidth tier to pre-stage. The sync reads Calendars.Read permissions from your Azure Entra ID app registration — no write access required.
Monitoring and Iteration
After your first month of scheduling, compare your IoD bill against the previous month. The savings calculator on the Apptifi homepage can help you verify whether actual savings align with estimates. Adjust your schedule based on actual utilization data and iterate quarterly as your workload patterns evolve.