# DPAS Rated Orders (DO and DX)

> Source: https://netray.co/glossary/dpas-rated-orders
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Glossary

## Short answer

A DPAS rated order is a government or prime contract order marked DO or DX under the Defense Priorities and Allocations System (15 CFR Part 700), which legally requires suppliers to accept and prioritise it ahead of unrated commercial work.

## Aliases

- DPAS
- Defense Priorities and Allocations System
- DO rating
- DX rating
- rated order

## Category

compliance

## Full Definition

DPAS gives the US government authority to prioritise national defense work in the supply chain. Orders carrying a priority rating of DO or DX must be accepted or rejected within set time frames, and a rating is flowed down to sub-tier purchase orders so that the whole chain schedules the work with priority. DX orders take precedence over DO orders, and both take precedence over unrated orders, though not over each other in a way that violates the regulation's own rules.

A rated order carries a rating such as DO-A1 or DX-A2, plus a required delivery date and the signature of an authorised official. A supplier must generally accept a rated order unless a defined exception applies, for example the item is not normally supplied or the buyer will not pay the usual terms. Acceptance or rejection must be communicated in writing, within 15 working days for DO and 10 working days for DX, and a rejection must give reasons.

The ERP implication is larger than it seems. Sales order and purchase order headers or lines need a rating field, planning must see the priority when scheduling capacity and material, and the rating must be printed on and flowed to sub-tier purchase orders. Without that, a rated job sits in the same queue as unrated work.

Compliance records matter as well. Acceptance dates, rejection notices and the flow-down of ratings to vendors need to be retrievable if the government or a prime asks. Companies often hold this in custom fields or attachments rather than a standard ERP feature.

## Why It Matters

- A rated order is a legal obligation, not a customer preference, so missing the acceptance window creates regulatory exposure.
- Priority must flow to sub-tier suppliers, or the delivery date cannot be protected.
- Capacity planning that ignores ratings can push critical defense work behind commercial orders.
- Audit trail of acceptance and rejection protects the company if priorities are later disputed.

## In Practice

Example: a machine shop receives a purchase order rated DO-A1 for 200 housings on Monday. The sales order is entered with the rating, the acceptance confirmation goes out within the allowed working days, and the production planner sees the priority flag. The raw material PO to the bar stock supplier carries the same DO-A1 rating. If the ERP does not carry the rating onto the material PO, the supplier treats it as routine. The gotcha is tracking the rating only in the order PDF and never in a searchable field.

## Faq

### What is the difference between DO and DX ratings?

**Answer:** Both are priority ratings on defense orders. DX has higher priority than DO and has a shorter acceptance window of 10 working days versus 15 for DO. Both outrank unrated orders.

### Can a supplier reject a rated order?

**Answer:** Only in limited circumstances defined in the regulation, such as the item not being normally supplied or the buyer not agreeing to usual terms. Rejections must be in writing with reasons.

### Must the rating be passed to my suppliers?

**Answer:** Yes, a supplier must place rated orders with its own suppliers to the extent needed to fill the order, and include the rating and required delivery dates.

## Search terms

DPAS rated order, DO rated order, DX rated order, Defense Priorities and Allocations System, 15 CFR 700, rated order flow down, DPAS acceptance 15 working days, DO-A1 rating

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json