Glossary

ATP Horizon

The future time window over which the Available-to-Promise calculation projects inventory and capacity availability to make order commitments.

Get in touch Learn more

Stylish WeWork-like workspace with hot desks and document wall, professional searching through enterprise knowledge base on a mounted ultrawide display, warm industrial pendants overhead.

What is ATP Horizon?

The ATP Horizon defines the future time window over which the Available-to-Promise calculation projects inventory and capacity availability to make order commitments.

The ATP Horizon is the specific future time window over which the Available-to-Promise (ATP) engine projects inventory receipts, production output, and demand consumption to determine if a customer order can be fulfilled. It establishes the boundary of visibility for the order promising logic; any requested delivery date falling beyond this horizon cannot be reliably committed against planned supply because the planning data is considered too uncertain or not yet generated.

Setting the ATP Horizon involves balancing computational performance against planning confidence. A longer horizon, often aligned with the cumulative lead time of the product, provides greater visibility for quoting distant delivery dates but increases data processing load. A shorter horizon limits the promise window but ensures commitments are made only against firm, near-term supply schedules, reducing the risk of rescheduling and protecting On-Time In-Full (OTIF) performance.

TIME WINDOW PARAMETERS

Key Characteristics of the ATP Horizon

The ATP Horizon defines the temporal boundary for order promising calculations. It dictates how far into the future the system projects inventory positions and capacity availability to make reliable commitments.

Finite Time Boundary

The ATP Horizon is a finite, configurable window extending from the current date to a defined future point. Beyond this boundary, the system lacks the detailed supply and demand data required for precise promising. It typically spans the cumulative lead time of the product plus a planning buffer. Setting it too short risks uncommittable orders; setting it too long introduces forecast inaccuracy.

Cumulative Lead Time

Minimum Horizon Length

Supply Visibility Window

Within the horizon, the ATP engine has full visibility into all scheduled receipts and planned orders. This includes:

On-Hand Inventory: Current stock in warehouses.
In-Transit Inventory: Goods shipped but not yet received.
Firm Planned Orders: Approved production or purchase orders.
Planned Orders: System-generated supply suggestions from the master schedule. Outside this window, only high-level forecast data exists, making precise order promising impossible.

EXPLORE

Demand Consumption Logic

The horizon is divided into distinct zones by the Demand Time Fence (DTF). Inside the DTF, the forecast is ignored, and only actual customer orders consume supply. Between the DTF and the horizon's end, a mix of forecast and actual orders is used. This prevents double-counting demand and ensures that a spike in real orders doesn't get hidden by an outdated statistical forecast.

DTF

Forecast Ignored Zone

Horizon-Specific Netting

The ATP Netting calculation behaves differently depending on the time bucket's position within the horizon. In near-term daily buckets, netting is precise. In future weekly or monthly buckets, it becomes more aggregated. The horizon's granularity directly impacts the accuracy of the delivery date quote. A horizon with daily buckets for the first 4 weeks provides far more reliable promises than one using only monthly buckets.

Daily Buckets

Optimal Near-Term Granularity

Dynamic Horizon Extension

For products with long lead times or high variability, the ATP Horizon can be dynamically extended using predictive lead time analytics. Instead of a static 90-day window, the system can automatically push the horizon out when it detects supply constraints or demand surges. This ensures the promising engine always has a complete view of the total supply required to fulfill a potential order, even for make-to-order environments.

EXPLORE

Global ATP Horizon Synchronization

In a multi-site Global ATP deployment, each plant or distribution center may have a different planning horizon. The global promising engine must synchronize these disparate horizons to create a unified view. A failure to align horizons can lead to a 'promising gap' where one site shows available supply that another site has already committed because its local horizon is shorter.

Unified View

Synchronized Horizon Goal

ATP HORIZON CLARIFIED

Frequently Asked Questions

Clear, technical answers to the most common questions about the ATP Horizon, its calculation, and its critical role in order promising logic.

The ATP Horizon is the future time window over which the Available-to-Promise (ATP) calculation projects inventory and capacity availability to make reliable order commitments. It is defined by the span of time for which the system has detailed, time-phased supply and demand data. This horizon typically extends from the current date through the cumulative lead time of all procured and manufactured components, plus any Demand Time Fence (DTF) . Within this boundary, every scheduled receipt from purchase orders and production runs is netted against every known demand, such as sales orders and forecasts, to generate a precise, period-by-period Projected Available Balance. Beyond the ATP Horizon, the system lacks the granular data required for a deterministic promise and must rely on rougher capacity checks or aggregate forecasts.

Enabling Efficiency, Speed & Accuracy

Intelligent Analysis, Decision & Execution

We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.

Talk to Us

Search across company data

Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.

Useful when people spend too long searching or get different answers from different systems.

Enterprise searchRAGPermissions

Automate internal workflows

Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.

Useful when repetitive work moves across multiple tools and teams.

AI agentsWorkflow automationGovernance

Add AI to products and internal tools

Build assistants, guided actions, or decision support into the software your team or customers already use.

Useful when AI needs to be part of the product, not a separate tool.

AI integrationDecision supportModel routing

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.

Limited slotsGet a Free AI Consultation

How We Work

Custom AI workflows for your Business

One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.

Talk to Us

ATP Horizon

What is ATP Horizon?