Prove demand.
Then plant.
An Industry 4.0 file is not a free-zone unit and a ribbon. It is customers, specifications, a cost base that survives UAE electricity and labour, and an ICV story that a buyer will actually score. Assembly follows that. It does not precede it.
What this program is for
Industrial hardware
Lighting, electrical, automation and equipment that can enter through projects before a line is built.
Assembly and integration
SKUs that can be finished, configured or packed in the UAE once offtake is real.
After-sales and parts
Calibration, spares and service nodes — often the first localization that pays.
What we will not write on this page
We do not sell Operation 300bn
National industrial policy is context. It is not a cheque, and 360Disruption does not award MoIAT status.
We do not promise ICV points
ICV is scored on a real file: local spend, people, plant. We map the path. We do not invent the score.
We do not start with a factory
A line is a destination outcome. First: specification, vendor lists, price versus the home plant.
We do not force one emirate
Ajman if the file needs to prove then build. Abu Dhabi or Dubai if the buyer and scale already live there.
How an industrial file moves
Is there a UAE case
Priority SKUs, home cost base, certifications, target channels, likely emirate, ICV logic. Go / hold / redirect.
Proof, not presence
Project and contractor maps, specification work, distributor tests, import path, a first commercial read.
The footprint the file earned
Trading entity, warehouse, service bench — only the structure demand supports.
Assembly when the maths hold
Land, line, labour and incentives after volume and ICV justify them. Not before.
The method is Prove before you invest. The desk that owns the file is the FDI Execution Desk.
India or China cost is not a veto. It is the first number.
If the home plant has subsidised power, the UAE case has to beat it on access, ICV, logistics and regional offtake — not on slogans. Discovery exists to do that sum before anyone prices a shed.