NEO — Sector Quantum Cost FAQ

Understand the computational complexity and token costs associated with each domain sector's quantum optimization pipeline.

Tap any sector to open its dedicated hub: upload files, save reusable portfolios, and wire connectors to the apps you already use.

Problem type	Typical n	Classical solve	Quantum shots	Token cost
Markdown optimisation	8–14	<1ms	256	~40
Store-level assortment	12–22	5–20ms	512	~90
Promo allocation (network)	20–32	>100ms → QAOA	1024	~160

Problem type	Typical n	Classical solve	Quantum shots	Token cost
Table-mix optimisation	8–16	<1ms	256	~45
Shift rostering	14–24	10–60ms	512	~100
Group-booking allocation	20–30	100ms → QAOA	1024	~170

Problem type	Typical n	Classical solve	Quantum shots	Token cost
Planting plan	10–18	<5ms	256	~60
Irrigation schedule	12–20	5–20ms	512	~90
Harvest sequencing	18–28	50–300ms	1024	~150

Problem type	Typical n	Classical solve	Quantum shots	Token cost
Weekly timetable	16–26	10–60ms	512	~100
Exam-slot allocation	20–32	100ms → QAOA	1024	~170
Cohort/section split	12–20	<10ms	256	~70

Problem type	Typical n	Classical solve	Quantum shots	Token cost
Traffic light scheduling	10–16	<1ms	256	~50
Energy grid allocation	12–20	2–8ms	512	~80
Service zone assignment	8–14	<1ms	256	~40

Problem type	Typical n	Classical solve	Quantum shots	Token cost
Portfolio mix optimisation	6–12	<1ms	256	~45
Storage dispatch scheduling	10–18	2–5ms	512	~70
Grid stability (QAOA)	12–20	5–15ms	1024	~120

Problem type	Typical n	Classical solve	Quantum shots	Token cost
Pick-route sequencing	16–28	20–100ms	512	~120
Last-mile VRP	24–40	>500ms → QAOA	1024	~220
Multi-depot dispatch	32–50+	QAOA only	2048	~380

Problem type	Typical n	Classical solve	Quantum shots	Token cost
Theatre scheduling	14–22	20–80ms	512	~110
Bed-flow allocation	18–30	100ms → QAOA	1024	~180
Care-pathway design	24–36	QAOA	2048	~280

Problem type	Typical n	Classical solve	Quantum shots	Token cost
Counter/window scheduling	12–20	10–40ms	512	~95
Benefit-allocation pass	20–32	100ms → QAOA	1024	~180
Capital-project sequencing	24–40	QAOA	2048	~260

Problem type	Typical n	Classical solve	Quantum shots	Token cost
Line balancing	14–22	10–50ms	512	~110
Job-shop scheduling	20–32	100ms → QAOA	1024	~190
Supply-chain re-route	28–45	QAOA	2048	~300

Problem type	Typical n	Classical solve	Quantum shots	Token cost
Mean-variance portfolio	10–20	5–30ms	512	~110
Risk-parity allocation	16–28	30–150ms	1024	~180
Combinatorial hedging	24–40	QAOA	2048	~310

Problem type	Typical n	Classical solve	Quantum shots	Token cost
Gate/slot scheduling	16–24	10–50ms	512	~100
Crew assignment	20–30	50–500ms	1024	~150
Trajectory optimisation	24–36	>1s → QAOA	2048	~250

Problem type	Typical n	Classical solve	Quantum shots	Token cost
Asset allocation	20–32	100ms–2s	1024	~160
Threat priority ranking	24–40	>2s → QAOA	2048	~300
Logistics route (full)	32–50+	QAOA only	4096	~500

Frequently Asked Questions

How are token costs calculated for quantum operations?

Each QUBO solve consumes tokens from your plan allowance. The cost depends on the number of variables (n) and shots. Classical brute-force (n ≤ 22) is inexpensive. QAOA (n > 22) uses more shots and consumes proportionally more tokens. IBM Quantum jobs (Enterprise only) are billed separately by IBM.

When does NEO switch from classical to quantum solving?

Automatically when n > 22 variables. Classical brute-force is exact but exponential: at n=22 it evaluates ~4M combinations. Beyond that threshold NEO uses QAOA which finds near-optimal solutions in polynomial time. You can also force quantum via the Advanced Parameters panel.

What is the "recommended solver" and how is it chosen?

After both solvers run, NEO compares their energy (cost function) values. If quantum finds a lower energy (better solution) it becomes the recommended solver. For n ≤ 22 classical is typically recommended unless quantum clearly outperforms it.

Can I limit which sectors consume my quota?

Yes — only sectors you activate in the Advanced Parameters → Active Sectors panel are eligible for sector analysis on each query. Deactivating a sector prevents it from running its quantum pipeline and consuming additional tokens.

Why is Defence always in suggest-only mode?

Defence-sector recommendations carry significant real-world risk if acted upon autonomously. NEO enforces human review (suggest-only) for all defence queries regardless of account autonomy level. This cannot be overridden.

Are Multi-Sector (cross-domain) queries more expensive?

Yes. Multi-sector QUBO merges constraint matrices from all selected sectors, resulting in a larger combined problem (n = sum of sector variables). A 3-sector query may have n = 40–70, forcing QAOA and consuming 2–3× more tokens than a single-sector query.

What is a portfolio?

A portfolio is a named bundle of uploaded files (catalogs, history, constraints) + external connectors + sector settings you can re-use across optimisation runs. Build it once on the sector page, then launch /optimize directly from the portfolio card.

How do connector configs differ per sector?

Each connector is keyed by (sector, platform_id). The same vendor token across multiple sectors must be entered separately so credentials never bleed across domains.

Do uploaded files live in my tenant?

Files are stored under your account, indexed for retrieval, and never used to train shared models. Deleting a portfolio removes its file references but does not auto-delete the underlying uploads — purge those from Settings → Files if required.

Why are Aerospace and Defence missing app connectors?

Both sectors are ITAR / dual-use sensitive. NEO provisions integrations for these sectors manually with appropriate compliance review — open a ticket via /support to start the process.

Can I use one portfolio across multiple sectors?

Portfolios are sector-scoped. For cross-sector runs, use /optimize → ⊞ Multi-Sector Optimizer and pass each sector's portfolio as a layer.

Does the per-sector page replace /workspace?

Yes — the old single-page Workspace is retired. Its weekly-review and business-memory features live inside each sector page so context is always sector-aware.

⚛️ Sector Quantum Costs & FAQ

Frequently Asked Questions