Industrial
Independence
Alliance
The operational technology that underpins modern industry is at a critical juncture. A paradigm imported from enterprise IT has been imposed upon the physical world of production, creating architectures that are fragile, business models that are extractive, and systems that are unnecessarily complex and insecure.
This is not a declaration of war on IT, but a recognition that OT and IT are distinct disciplines with different imperatives. We seek collaboration based on mutual respect for these differences.
The Core Principles of Operational Technology
We hold these principles to be the foundation of sound industrial practice. They are not negotiable, as they are derived from the realities of controlling physical processes.
Availability is Paramount
The primary function of any OT system is to ensure the safe, continuous, and correct operation of a physical process. All other considerations must serve this primary directive.
Operational Reality Dictates Design
Industrial environments are not data centers. Network designs and architectures must be resilient to the specific constraints of the plant floor.
Complexity is the Enemy of Reliability
Robust OT systems are simple, predictable, and deterministic. We must aggressively simplify our architectures and eliminate unnecessary dependencies.
Security Through Deliberate Separation
The most effective security posture is intentional, managed separation from untrusted networks. True security is an architectural property, not a product.
Every Boundary Must Be Formalized
Data flows between OT and IT domains must be documented, limited, and governed by formal agreements. These conduits are security perimeters.
Empower the Practitioner
The most valuable asset is the knowledge of practitioners who design, implement, and maintain systems. We value practical experience over vendor certifications.
The Reality We Must Address
We recognize the legitimate business needs for operational visibility, efficiency improvements, and predictive analytics. These goals can and must be achieved through architectures that respect OT's operational imperatives rather than subordinating them to IT convenience.
Operational Visibility
Business systems need access to operational data for planning, optimization, and reporting. This can be achieved through secure, one-way data flows that don't compromise operational independence.
Efficiency Improvements
Advanced analytics and optimization algorithms can provide valuable insights for operational improvements, as long as they operate as advisory systems rather than control systems.
Predictive Analytics
Machine learning and AI can provide valuable intelligence to operations— predictive maintenance, advanced analytics—as IT systems subject to IT availability expectations, not OT requirements.
The Key Understanding
IT systems can provide valuable intelligence to operations as long as everyone understands these are IT systems subject to IT availability expectations, not OT systems required for production. The distinction is critical.
A Call for a New Approach
The prevailing vendor-driven model has failed to deliver on its promises of seamless integration and enhanced security. We advocate for a fundamental shift in how we design, procure, and manage operational technology.
We Will Champion Architectural Independence
Move away from proprietary, all-in-one ecosystems that lead to vendor lock-in. Design systems using open, interoperable standards.
- Select the best tool for the job, regardless of brand
- Primary allegiance to operational requirements, not vendor roadmaps
- Open standards enable true interoperability
We Will Champion Build for Resilience, Not Dependency
Design systems that can function indefinitely without external connectivity. Plant autonomy is non-negotiable.
- Operations must remain fully autonomous within plant walls
- External services consume copies of data when available
- Cloud services are tools for analysis, not operational requirements
We Will Champion Formal Integration Agreements
Reject informal IT/OT 'convergence' in favor of selective integration governed by explicit agreements.
- Data Exchange Agreements (DEA) defining what flows and when
- Service Level Agreements (SLA) establishing clear responsibilities
- RACI matrices clarifying ownership and change control
We Will Champion Restore Standards to Practitioners
Make standards like IEC 62443 practical and accessible, creating field-ready guidance for better security outcomes.
- Transform complex frameworks into practical guidance
- Empower practitioners without unnecessary cost or complexity
- Inter-zone conduits are critical security perimeters, not suggestions
We Will Champion Empower the Practitioner
The most valuable asset is the knowledge of practitioners who design, implement, and maintain systems.
- Foster community of practice for knowledge sharing
- Uphold high standards of engineering excellence
- Value practical experience over vendor certifications
Our Commitment to the Future of Industry
We are not Luddites resisting progress; we are the engineers, integrators, and asset owners demanding a more resilient, secure, and sustainable foundation for the future of manufacturing and critical infrastructure.
To Vendors
We invite you to join us, not as rulers, but as partners who respect the principles of our domain. Work with us to build solutions that serve operational reality.
To IT Colleagues
We invite collaboration as peers, recognizing the distinct and critical nature of our responsibilities. Clear communication requires mutual respect for our differences.
To Industry
We will no longer accept that "industrial" means "overpriced and insecure." We will build the future of OT on sound engineering and operational reality.