Category reference
Decision Infrastructure
Your forecasting model flagged the stockout three weeks out. The alert reached a shared channel. Nobody owned it. Stock ran out anyway. The intelligence worked. The decision never got made.
Definition
Decision infrastructure is the governance layer that gives every operational decision a named owner, an approval threshold, a direct write to the system of record, and a permanent audit entry.
It governs what happens after the signal arrives. Decision intelligence produces the signal and the recommendation. Decision infrastructure produces the executed decision and the record of who made it.
Most mid-market manufacturers and distributors have already bought the first layer. Demand forecasting, anomaly detection, inventory risk scoring, supplier alerts. The signals fire. Then a person has to translate the signal into an email, a meeting, a spreadsheet, and eventually a purchase order. That translation step is where the operation loses two to three days, and where accountability dissolves.
Provenance. IntelliConnectQ Analytics has used this definition since May 2026 and adopted Decision Infrastructure as its sole category term on 13 July 2026. The term describes an architecture, not a product. OpsGrid, AskOps, and TradeFlow Crew are IntelliConnectQ's implementations of it.
The five layers
A decision either passes through all five or it stalls at the layer that is missing. Most operations that describe themselves as data-driven have layers 1 and 2 and nothing after that.
-
Signal
The condition is detected. Stock cover falls under threshold, a PO passes its promise date, a machine logs an anomaly, an invoice fails three-way match. This is the layer the market has already solved.
-
Route
The signal reaches one named person under a stated response SLA. Not a channel. Not a distribution list. A person, with the data context attached, in the tool they already work in.
-
Approve
Someone with authority at that value threshold approves or overrides, and records why. Thresholds are defined in advance rather than negotiated per incident.
-
Execute
The approval writes to the ERP. No rekeying, no second person, no gap between the decision and the transaction. The approval is the trigger.
-
Audit
The decision, the approver, the data they saw, and the timestamp are logged permanently. Six months later, someone can reconstruct why the $40,000 expedite was authorised.
These five stages are what the Decision Latency Diagnostic scores. A score is a measure of how many of the five your operation actually completes without human improvisation.
Decision infrastructure compared to what you already run
Four categories get conflated in vendor conversations. They do different jobs and fail in different places.
| Business Intelligence | Workflow Automation | Decision Intelligence | Decision Infrastructure | |
|---|---|---|---|---|
| What it produces | A dashboard | A completed task | A ranked recommendation | An executed decision with an owner |
| Who decides | Whoever opens it | Nobody. The rule decides | Whoever reads the recommendation | The named owner for that decision category |
| Handles exceptions | Displays them | Breaks on anything unmodelled | Flags and ranks them | Routes them to an owner under a response SLA |
| Writes to the ERP | No | Yes, with no human approval | No | Yes, after approval at the right threshold |
| Audit record | Query logs | Run history | None | Decision, approver, data context, timestamp |
| Where it fails | Nobody opens it | The exception was not in the rule | The recommendation lands nowhere | Ownership was never assigned |
The fourth column does not replace the other three. It depends on them. BI supplies the numbers, automation handles the volume that needs no judgement, and decision intelligence ranks what deserves attention. Decision infrastructure is what turns the ranked item into a transaction somebody signed for.
ARC Advisory Group named supply chain decision intelligence as a category in its 2026 research and framed the challenge precisely: "the goal is no longer generating intelligence. The goal is compressing time between signal and coordinated action." Compressing that time takes governance, not a better model. The full comparison of the two categories covers where each one stops.
Five questions that tell you whether you have it
Answer these about your largest site. Hesitation on any one of them is the layer that is missing.
- Name the person accountable for stockout decisions at that site. Do they know they own it?
- A purchase order above your approval threshold needs sign-off at 9 PM on a Friday. What happens?
- Someone authorised emergency freight in March. Where is the record of the data they saw when they decided?
- Between approving a supplier change and the ERP reflecting it, how many manual steps run?
- Your last AI pilot produced recommendations. How many of them became ERP transactions?
Score it properly
The Decision Latency Diagnostic is 12 questions and scores your operation across all five layers. Scoring runs server-side, so the band you get is the band you have.
How IntelliConnectQ implements it
Three products, three operating environments, one architecture.
Dynamics 365 Business Central
OpsGrid
Monitors BC continuously, ranks operational exceptions, and routes each one to its named owner inside Microsoft Teams. Approval triggers the BC write. Nothing executes without a human signing for it, enforced in the architecture rather than in a policy document. Two-week deployment.
See OpsGrid →Any ERP
AskOps
The signal layer for teams whose ERP data is unreachable without a ticket. Plain-language questions against live SAP, NetSuite, Dynamics, Odoo, or custom systems, answered in WhatsApp, Teams, or Slack in seconds. Solves layer one so layers two through five have something to govern.
See AskOps →FMCG trade operations
TradeFlow Crew
A five-stage order pipeline replacing WhatsApp coordination between buyers, sales, and factory. Each stage has an owner and a state, so an order that stalls is visible as a stalled decision rather than an unanswered message.
See TradeFlow Crew →The decision infrastructure library
Longer analysis on each layer, written from mid-market manufacturing, distribution, and managed services engagements.
The category
Ownership and approval
Frequently asked questions
What is decision infrastructure?
Decision infrastructure is the governance layer that gives every operational decision a named owner, an approval threshold, a direct write to the system of record, and a permanent audit entry. It operates across five layers: Signal (the condition is detected), Route (it reaches a named owner under a response SLA), Approve (a person with authority at that threshold approves or overrides), Execute (the approval writes to the ERP with no second manual step), and Audit (the decision, approver, data context, and timestamp are logged permanently).
How is decision infrastructure different from decision intelligence?
Decision intelligence produces a ranked recommendation. Decision infrastructure produces an executed decision with an accountable owner. Intelligence answers what should happen; infrastructure governs who decides it, at what threshold, how it reaches the ERP, and what record survives. An organisation can run a strong decision intelligence layer and still take three days to act, because nothing in the intelligence layer assigns ownership or connects an approval to a transaction.
Does decision infrastructure replace our ERP or BI stack?
No. It sits between them and the people who act. The ERP stays the system of record and receives every write. BI keeps reporting. Decision infrastructure adds the routing, approval, and audit layer that neither one provides: which named person owns this exception, what they are authorised to approve, and how their approval becomes an ERP transaction without anyone rekeying it.
How long does it take to put decision infrastructure in place?
For a single decision category in a Dynamics 365 Business Central environment, IntelliConnectQ deploys OpsGrid in two weeks: connect to BC, define the decision categories and their owners, set approval thresholds, and route to Microsoft Teams with human approval before any write. Broadening to additional categories such as supplier exceptions or production scheduling is incremental. The governance model itself, meaning who owns what and at what threshold, is the part that takes longest, and it is organisational rather than technical.
Your ERP already knows. The question is who acts.
If your operations team is running three or more disconnected systems for one workflow, or if the last thing you implemented did not hold, the gap is at layers two through five. Bring one decision category and we will map it against the five layers on the call.