CSP's CIO named the gap automotive manufacturers already feel: an ERP that logs every transaction perfectly and still leaves the next decision waiting for someone to notice, route, and act on it.
Category reference
Decision Infrastructure
A stockout. A credit hold. An SLA breach. Your systems flagged it. The alert reached a shared channel. Nobody owned it. 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, distributors, logistics operators, and managed services providers 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 system of record. 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.
| Decision Infrastructure | Business Intelligence | Workflow Automation | Decision Intelligence | |
|---|---|---|---|---|
| What it produces | An executed decision with an owner | A dashboard | A completed task | A ranked recommendation |
| Who decides | The named owner for that decision category | Whoever opens it | Nobody. The rule decides | Whoever reads the recommendation |
| Handles exceptions | Routes them to an owner under a response SLA | Displays them | Breaks on anything unmodelled | Flags and ranks them |
| Writes to the system of record | Yes, after approval at the right threshold | No | Yes, with no human approval | No |
| Audit record | Decision, approver, data context, timestamp | Query logs | Run history | None |
| Where it fails | Ownership was never assigned | Nobody opens it | The exception was not in the rule | The recommendation lands nowhere |
Decision infrastructure 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 system of record reflecting it, how many manual steps run?
- Your last AI pilot produced recommendations. How many of them became transactions in your system of record?
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 →Architecture, for your IT and security team
How the Execute layer actually works
The part a CIO signs off on before anything else: what OpsGrid reads from Business Central, the specific BC entities it can write to after approval, and the open-source LangGraph engine underneath, every node, edge, and state transition inspectable rather than a black box. OpsGrid operates within your BC permission model; it cannot elevate its own access.
See the architecture →Decision infrastructure by industry
The five layers are the same everywhere. What breaks first, and what a missed decision costs, differs by operation.
Decision Infrastructure for Manufacturing
The pain. A production line is two days from missing a customer commit because a fabric component fell below safety stock. The signal is already in Business Central. Nobody with the authority to reroute a supplier or approve an expedite has seen it: it's sitting in a report nobody opens until Thursday.
A $30M manufacturer running this pattern loses an estimated $480K a year to OTIF penalties alone, plus a 3.8× freight premium every time expediting is the only option left.
How the five layers close it. The material-shortage signal routes to a named production planner the moment BC flags it, not at the next ops review. Approval to expedite or substitute happens in Teams at a pre-agreed dollar threshold. The write lands in BC as a rescheduled production order or a draft PO. Who approved it, at what cost, and why is logged permanently.
Decision Infrastructure for Distribution
The pain. $47,200 in orders sits blocked on a credit hold for 72 hours. The credit controller already checked the account. Finance still has to approve the release, and nobody is tracking whose turn it is.
That's one customer. Add the 14 backorders already past their promised date ($31,000 exposed) and a stockout three days out on an $18,600 order, and a mid-market distributor is carrying six figures in decisions nobody owns at any given moment.
How the five layers close it. The credit hold routes to the named Credit Controller with a response SLA the moment it crosses your threshold. Approval releases the hold in Teams (no BC login required). Execution posts the release straight to BC, and CFO escalation fires automatically if the SLA lapses. Every release, every escalation, logged.
Decision Infrastructure for Logistics & 3PL
The pain. Monday morning: twelve exception threads across five systems, zero pallets moved. A $2,800 carrier invoice mismatch has sat in the finance queue for nine days. A purchase order is six days overdue and the carrier hasn't responded.
A $20M logistics operator absorbs roughly $18K per unresolved delivery exception; the SLA penalty clause activates whether or not anyone was assigned to act.
How the five layers close it. The delivery exception routes to the named account owner with revenue at risk attached, not a shared inbox. Approval to escalate, credit, or re-commit happens in Teams. The action posts to BC (updated order status, issued credit note), and the client-specific audit trail stays separated by account, even across 8+ clients on one BC environment.
Decision Infrastructure for Managed Services
The pain. One MSP ran employee offboarding as a 6pm batch job across 7 enterprise clients and 4,500 users. Access stayed live for hours after someone's last day, every time, because revoking it wasn't anyone's named responsibility until the end-of-day rush.
That's compliance exposure repeated on every departure, across every client tenant, absorbed by 3 full-time staff doing it by hand.
How the five layers close it. Termination is the signal. A named IT owner is the route. Revocation is the approved execution. The log is the audit. Applying that model to identity events took this MSP from 3 FTEs to 1 part-time, with the exposure gone. AskOps is IntelliConnectQ's signal layer for exactly this kind of any-ERP, any-tenant environment.
The decision infrastructure library
Longer analysis on each layer, written from mid-market manufacturing, distribution, logistics, and managed services engagements.
Spot rates are up 25% YoY with no relief in sight. Uber Freight's Bob Daymon and Coty's Graeme Carter both say the operators winning 2026 stopped waiting on forecast confidence. What a decision-speed operating model requires instead.
Payables Agent, Copilot, Agent Designer, Power Automate, and OpsGrid all touch Business Central now. A field guide to what each one actually governs, its real maturity status as of August 26, 2026, and the accountability gap between them.
A 2026 FDA warning letter cited a pharmaceutical and cosmetics manufacturer for cGMP violations after AI agents generated specifications, procedures, and compliance records with no human review. The output wasn't shown to be wrong. The missing approval was the violation.
Business Central's excise tax engine reached general availability May 8, 2026. Microsoft's own release notes say it directly: no compliance or statutory reports ship with it. What that means for tax managers at alcohol, tobacco, and fuel manufacturers.
Business Central's Sales Order Agent converts a customer's email reply into a posted order with nobody touching a screen. Microsoft built a real write-scope control for that. It isn't the same thing as an audit trail.
Lexful raised an oversubscribed $7M seed round in June 2026 to solve documentation capture for MSPs. MachineMetrics and Tulip are building similar reasoning layers for manufacturing. What OpsGrid's Audit stage already logs on every exception approval.
Gartner puts 56% of non-human identities outside structured governance. Most of that growth is AI agents nobody assigned an owner. Why agent risk is an identity problem, not a model problem, and how it extends the lifecycle automation MSPs already run for humans.
Three benchmarks, Carnegie Mellon's TheAgentCompany, WebArena, and MIT Project NANDA, put agent failure rates between 70 and 95%. What actually breaks a deployment, and why verification has to be a loop, not a launch-day test.
Sage's 2026 State of Supply Chain Report found 95% of supply chain leaders call AI vital, and 10% have it live, an 85-point gap. The readiness signals, ERP access, named ownership, sponsor authority, pilot scope, that separate the two before a vendor is ever picked.
A 2026 forecast puts a number on autonomous disruption resolution: 60% by 2031. The exception-category rollout, inventory risk first, then supplier exceptions, then production scheduling, that has to start now to get there.
A purchase order sits in approval limbo for six days because the Power Automate flow that routed it was built by someone who left in March. What BC's native approvals actually cover, what the workaround costs, and what a governed alternative looks like.
A May 2026 legal series flags novel liability, regulatory, and contractual risk from ungoverned AI in manufacturing. What a General Counsel needs from the audit trail that a CFO never asks for: a named approver, a timestamp, and an exportable record.
EU AI Act Article 14 names three human oversight capabilities, and an approval gate delivers one. The Bank of England has gone further, calling human sign-off on every agent action unrealistic and floating kill switches instead. What Business Central ships natively, and what has to be built.
Half of AI agent deployment failures by 2030 are forecast to trace to governance runtime enforcement, not model capability. What that reorders on a multi-year Business Central AI roadmap: write inventory, autonomy and scope tiering, then the model last.
A July 2026 ecosystem analysis and a verified Siemens-NVIDIA-Humanoid deployment at Erlangen both point the same direction: AI vendor selection is being decided on ERP embeddedness, not model benchmark scores. The 5-question scorecard that predicts a real deployment instead of a stalled pilot.
A July 2026 roundup names a shift already underway at Hitachi: engineers embedded on-site for physical AI deployments. Why remote delivery fails on a shop floor, and what a 2-week embedded deployment across Business Central, Epicor, and Infor actually requires.
Cross-training transfers skills. It doesn't transfer the record of every decision that shaped how your operation runs today. The institutional knowledge gap in manufacturing is a record problem, addressable without any documentation effort from your team.
IoT Analytics surveyed 120 process manufacturing leaders expecting 12% lower operating costs from AI. The ambition is real. This is what separates the plants that get there: it's a decision infrastructure problem, not a modeling problem.
Decision intelligence surfaces signals. Decision infrastructure governs what happens next: who owns the decision, who approves it, and what gets audited. Your supply chain probably has the first layer. Here is why it needs the second.
Every operations team has more AI alerts than they can act on. The problem is not the AI: it is the absence of an execution layer that turns signals into governed decisions with named owners, approval workflows, and audit trails.
Business Central has the data. The gap is the decision layer between the signal and an approved response. Here is what OpsGrid adds on top of what you already have.
Manufacturing pilots succeed technically and fail operationally. The 5 root causes behind the gap, and what the organizations that close it actually do differently.
83% of organisations are running supply chain AI pilots. Most won't scale. The gap is an operating model problem, not a technology problem, and three structural gaps determine which side of that line you're on.
Your on-time-in-full rate is not a supply chain metric. It is a decision timing metric. The alerts that break OTIF most often fire outside business hours, and the gap between signal and approved response is where the ship window closes.
When component supply falls short of combined plant demand, who decides which site gets priority? Without a pre-defined governance model, the answer is whoever escalates to the COO first. That is not a decision. It is a political outcome.
No tariff assumption is stable right now. The answer is not better forecasting: it is a decision governance layer that makes procurement decisions documented, auditable, and executable regardless of what policy does next.
When a shipping route closes, most operations teams discover their gaps in the wrong order. One framework for sequencing the decisions that matter, with named owners, numeric thresholds, and escalation paths. Draws on MIT resilience research and ASCM practice.
When a P1 incident ends and the compliance audit begins, can you reconstruct every decision made during the response? Who approved overtime? Who authorised vendor escalation? If the answer is "check the Slack channel," the MSP has a governance problem.
The financial case for vertical integration is compelling. The execution gap (SOPs, decision ownership, knowledge transfer, cross-plant coordination) is real and under-discussed. This is what operational readiness actually looks like.
The four-variable framework and interactive calculator we use to build a business case before any deployment starts. Most teams find the number higher than they expected.
Expedited shipping rarely appears as a line item anyone owns. It accumulates in the hours between a system flagging a shortage and a human authorising the response. What sits inside that budget, and how to measure the delay before committing to a fix.
Most mid-market manufacturers run 4–7 disconnected systems. Decisions stall because nobody has the full picture. A practitioner guide to unifying ERP, CRM, and operations data, built around decision choke-points, a unified data pipeline, embedded BI, and selective automation.
4 people. 20+ hours daily. Duplicate POs. No trail when fabric was damaged on the floor. Fitting orders over-committing stock. Here's the integrated supplier portal, and what the cutover actually took.
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 system of record, 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.
Does decision infrastructure learn or adapt its recommendations over time?
No. Thresholds and routing rules are configured by your team, not learned by a model. Every recommendation traces back to a rule someone set, not a weight that drifted. That is deliberate: when a $40,000 expedite has to be defensible six months later, auditable beats adaptive. An override is logged as a decision with a reason, not fed back into a model that changes its own behaviour.
Does decision infrastructure optimise trade-offs across departments, or the whole network?
No, not today. Each decision category has one named owner and one threshold. It governs execution within that category, it does not weigh transportation cost against inventory cost against customer service level and pick a winner across departments. Network-level trade-off optimisation is a different, more advanced problem than decision infrastructure solves. If that is what you need, decision infrastructure is still the right foundation, it is just not sufficient on its own.
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.