Smart Factory Audit: 30 Things to Check Before Your Industry 4.0 Project

A smart factory audit run before investment prevents the most common and expensive Industry 4.0 project failures, not by selecting better technology, but by confirming the factory is ready to deploy it.

Most projects that fail do not fail because of the platform chosen. They fail because the prerequisites were not in place: unclean data, unconnected machines, OT and IT teams with no shared governance, and a change management plan written after implementation had already started. A structured factory audit surfaces these gaps before budget is committed.

This smart factory readiness checklist covers 30 checks across six audit dimensions. Work through each before scoping your Industry 4.0 project.

Why a factory audit matters before you invest

The Smart Industry Readiness Index (SIRI), developed in Singapore and used across Southeast Asia, identifies three layers of Industry 4.0 readiness: process, technology, and organisation. Most manufacturers pass the technology layer. Most fail the process and organisation layers. The audit below is structured around all three.

According to BizTech Magazine, 91% of manufacturers experienced at least one cyber breach in their OT environments, the majority caused by integration projects that opened connections without adequate controls. The same audit that identifies readiness gaps also identifies security exposure.

What do I need to check before starting a smart factory or Industry 4.0 project?

The audit covers six dimensions: infrastructure and connectivity, data collection and quality, OT/IT integration, systems and software, cybersecurity and risk, and people, governance and leadership. A factory ready for smart manufacturing investment should be able to confirm the majority of these 30 checks.

Infrastructure and Connectivity

1. Network coverage on the shop floor. Can all target machines be reached by a stable wired or wireless network? Gaps in coverage mean sensor data will not reach the integration layer.

2. PLC and SCADA data output. Can existing PLCs output data via OPC-UA, MQTT, or REST APIs? If not, hardware upgrades must be scoped and costed before the project begins.

3. Edge computing capacity. Is there processing capability at the machine or line level? Without edge capacity, all data routes to a central server, creating latency and single-point failure risk.

4. Sensor coverage map. Which assets have no instrumentation? Map coverage gaps before scoping sensor deployment. Deploying analytics on unmonitored assets produces no output.

5. Connectivity redundancy. What happens to production if the network fails? OT should sit on a separate, resilient segment from corporate IT.

Data Collection and Quality

6. Current data sources. Which machines produce data today? Map every source, manual logs, PLCs, SCADA, MES, before defining the integration architecture.

7. Data format consistency. Are data outputs consistent across lines and shifts, or does every machine use a different schema? Inconsistent formats require transformation layers that add cost and maintenance overhead.

8. Automated capture rate. What percentage of production events are captured automatically? Manual data entry introduces errors and delays that undermine any analytics investment.

9. Data persistence. Is there a historian or time-series database in place? If data does not persist beyond the dashboard, there is no baseline for predictive maintenance or trend analysis.

10. Data ownership. Is there a named data owner with authority over quality standards? Ungoverned data produces unreliable outputs regardless of the analytics platform deployed on top of it.

OT/IT Integration

11. ERP and shopfloor connection. Does real-time production data reach the ERP, or are production orders updated manually? An unconnected ERP means planning decisions are made on lagged data.

12. OT protocol inventory. Does your IT team know which OT protocols, OPC-UA, Modbus, PROFINET, are in use on the production floor? Integration cannot be scoped without this inventory. The CDW IT/OT Convergence Readiness Checklist identifies this as the most commonly skipped prerequisite.

13. System of record definition. When shopfloor data and ERP data conflict, which is authoritative? If this is not defined, data disputes will delay every downstream decision.

14. Integration middleware. Is there an industrial IoT platform, middleware layer, or API gateway managing data flow between OT and IT? Without it, point-to-point integrations accumulate and become unmanageable.

15. OT change control. Are changes to OT systems subject to a defined change management process? Uncontrolled OT changes introduce security exposure and operational instability.

Systems and Software

16. MES status. Is a Manufacturing Execution System in place? If yes, is it integrated with the ERP? If no, determine whether one is required before analytics or AI can be meaningfully deployed.

17. ERP coverage. Does the ERP capture production orders, material movements, and quality events, or is it used primarily for finance? An ERP with partial production coverage cannot be the backbone of a digital factory.

18. Maintenance system maturity. Is maintenance tracked digitally? Predictive maintenance requires a baseline of historical work order data. A factory without a CMMS cannot deploy predictive capability without first building the data foundation.

19. Software support status. Are any production-critical software systems end-of-life or on unsupported versions? Legacy systems on unsupported software create both security risk and integration constraints.

20. Digital twin prerequisites. Is there a digital model of any production line or asset? If simulation-based optimisation is in scope, define the modelling requirements before committing to a platform.

Cybersecurity and Risk

21. OT/IT network segmentation. Are OT networks physically or logically separated from corporate IT? Lack of segmentation is the leading cause of OT breaches. An Industry 4.0 assessment that does not address segmentation is incomplete.

22. Remote access controls. Who has remote access to OT systems? All remote access should route through a secure, auditable gateway with multi-factor authentication.

23. Patch status. When were OT systems last patched? Legacy PLCs and SCADA systems often run on outdated firmware that cannot be patched without planned production downtime, this must be scheduled proactively.

24. OT incident response plan. Does the factory have an OT-specific incident response plan? General IT security playbooks do not account for production uptime constraints. The response to a ransomware event in OT differs fundamentally from an IT incident.

25. Third-party access audit. Do maintenance vendors or software providers have persistent access to OT systems? Map and audit all third-party connections before expanding the integration surface.

People, Governance and Leadership

26. Executive sponsor. Is there a named executive with budget authority and cross-functional accountability for the Industry 4.0 programme? Projects without a sponsor stall at the first decision that requires IT, production, and finance to agree.

27. OT/IT joint governance. Do OT and IT teams have a defined governance structure, or do they operate as separate silos? Convergence projects require joint ownership, without it, integration decisions escalate rather than resolve.

28. Digital skills baseline. What is the current digital skills level across the production workforce? A smart factory assessment should include a skills gap analysis. Deploying digital tools on a workforce not prepared to use them produces adoption failure, not operational improvement.

29. Change management plan. Is there a structured approach for communicating, training, and embedding new tools into daily production workflows? In most Industry 4.0 assessments, change management is the last item scoped and the first reason deployment stalls.

30. ROI definition. Are success metrics defined before the project starts, OEE improvement, downtime reduction, defect rate, with a baseline measured today? Undefined success criteria are the primary reason projects are extended indefinitely without delivering measurable value.

How to score your audit

Based on Gradion's factory assessment practice, readiness bands typically fall as follows:

0-10 confirmed checks: Infrastructure build required before investment.

11-20 confirmed checks: Pilot-ready on select assets; address gaps in parallel.

21-29 confirmed checks: Ready for scaled deployment; close remaining gaps in phase one.

30 confirmed checks: Strong readiness, proceed to roadmap and vendor selection.

An honest score below 20 does not mean the Industry 4.0 project should not happen. It means the project scope must include the prerequisite work, and the budget must reflect it.

What comes next

A completed smart factory readiness checklist produces three outputs: a gap register, a sequenced remediation plan, and a realistic project scope. These three documents prevent the most common cause of Industry 4.0 project overruns, the discovery of foundational gaps after the platform contract has been signed.

Gradion conducts structured factory audits and Industry 4.0 readiness assessments for manufacturers across DACH and Southeast Asia as part of our manufacturing automation software consulting practice. The audit runs before any technology recommendation. Contact us to start with a scoped assessment.