Integration of Multiple Systems and a Unified Architecture — Practical Path from Multiple Layers to a Single System
One, Why Multiple Systems Become Fragmented
Before understanding the integration of multiple systems, it's important to understand how fragmentation occurs. Most companies implement management systems in a "standard-responsive" manner: when a customer demands ISO 9001 certification, the company builds a system according to ISO 9001 clauses; when the government requires environmental compliance, another system is built according to ISO 14001; and when export is needed, ISO 45001 is added. Each system's implementation is often led by different departments—Quality Department for 9001, EHS Department for 14001 and 45001, and each business unit has its own customer-specific requirements. Similar situations arise with the introduction of ISO 50001 for energy management and ISO 27001 for information security. Each additional management system brings another set of documents, processes, and training.
This "system-by-system" approach has inherent flaws. First, the documents for each system are independent—quality manuals, environmental manuals, and safety manuals are separate, and procedures like "document control procedure," "training management procedure," and "internal audit procedure" are duplicated across systems. For example, in a medium-sized manufacturing company, the total number of procedure files can exceed sixty when systems are implemented independently, with nearly 30% of them being highly repetitive. Second, in terms of operations, the same activity is required by multiple systems from different perspectives, forcing on-site personnel to switch between systems. A single equipment maintenance activity, for instance, involves calibration and process confirmation from the quality system, waste disposal from the environmental system, and lockout/tagout and protective equipment from the safety system, requiring the review of three different work instructions. Finally, in the audit phase, external audit organizations operate independently, with overlapping audit times but repetitive content, leaving the company struggling to cope.
A deeper issue is that management often falls into a cognitive trap: they believe that multiple systems mean more documents, more records, and more audits. In reality, the essence of a management system is the structured management of "what needs to be managed" in the company's operations, and "what needs to be managed" is a single set of tasks for the company—quality, environment, safety, energy, and information security are different aspects of risk and requirements that the same company faces, and they should be managed uniformly. Quality management guru Deming stated that the core of management is understanding and optimizing systems, not building a separate system for each requirement.
Two, The Three-Tier Framework for Integrating Multiple Systems
Through years of industry practice, a mature three-tier framework for integrating multiple systems has been developed. The core idea of this framework is: high-level unification, mid-level integration, and low-level compatibility.
The first tier is the strategic level. This tier addresses the question "why do we need to manage," corresponding to the content of management manuals. The company's quality policy, environmental policy, and safety policy can be merged into a single "integrated management policy," reflecting the top management's commitment to all management systems. Management objectives can also be integrated—instead of setting separate quality objectives, environmental objectives, and safety objectives, these indicators can be broken down hierarchically under the company's overall business objectives. This level of integration does not change any requirements of the standard clauses but is purely a change in organizational approach, making it the easiest to implement.
The second tier is the process level. This tier addresses "how we manage," corresponding to procedure files and process norms. This is the core battlefield for integration. Although ISO 9001, ISO 14001, and ISO 45001 have different clauses for resource management (7.1), the management objects are the same—people, machines, materials, methods, and environment. The company can use a single "human resource management procedure" to cover training, capability, and awareness requirements; and a single "infrastructure management procedure" to cover equipment maintenance and work environment requirements. Integration at the process level requires the company to move away from the "categorization by standard clauses" mindset and return to the "categorization by business processes" logic. Many companies struggle to advance at this level due to functional barriers—quality departments are often unwilling to share their procedure files with other departments, fearing a loss of control. This requires top management to step in and drive the process.
The third tier is the record level. This tier addresses "how well we manage," corresponding to forms, records, and evidence. This level is the easiest to show results but also the easiest to make mistakes. On the surface, different systems require different record formats, but if viewed from the perspective of "what management problem this record solves," many records can be merged. For example, an equipment inspection form can include quality parameters, safety parameters, and environmental parameters, rather than having separate forms for each department. Integration at the record level requires cross-departmental consensus on record design and a unified approval process.
Three, Methodology for Integration: Process-Centric
The essence of integrating multiple systems is to switch from "standard clause-driven" to "process-driven." The traditional approach is to organize the document directory according to the clause numbers of ISO 9001; the integrated approach is to organize the document system according to the actual operational processes of the company.
The specific operations can be divided into four steps. The first step is to map out the company's core business processes. Do not list items according to standard clauses but start from the entire value chain from order to delivery, identifying core processes, support processes, and management processes. Tools like the turtle diagram or SIPOC diagram can be used to comprehensively describe the objectives, inputs, outputs, resources, methods, and performance indicators of each process. The second step is to align the requirements of different systems with these processes. The design and development requirements of ISO 9001, the operational control requirements of ISO 14001, and the operational planning requirements of ISO 45001, if all implemented in the "product realization process," are no longer three separate requirements but three dimensions of the same process. The third step is to unify document formats and numbering rules. Do not call ISO 9001 documents QP-01 and ISO 14001 documents EP-01. It is recommended to use a document coding system centered on process numbers, such as "PR-03" representing the procedure file for the third process, with the applicable system standards noted in the file header. The fourth step is to establish an integrated internal audit mechanism. Internal audits are no longer divided into quality audits, environmental audits, and safety audits but are conducted by process—auditing a process covers quality, environment, safety, and other dimensions simultaneously.
A process-centric integration method has a key advantage: it naturally aligns with the company's daily operational management. Processes are what managers manage every day, and a system based on processes is a "living" system, whereas a system based on standard clauses is a "hanging" system. From the high-level structure (HLS) released by ISO, it is clear that major management system standards such as ISO 9001, ISO 14001, and ISO 45001 have adopted the same clause structure (Chapters 4 to 10), providing a natural institutional foundation for the integration of multiple systems. Companies can fully leverage this commonality to achieve one planning effort that covers multiple standards at the process level.
Four, Common Pitfalls in the Integration Process
During the practical implementation of integrating multiple systems, several pitfalls are common and need to be avoided.
The first pitfall is "document consolidation equals system integration." Some companies, for convenience, combine three manuals into one book and simply concatenate similar procedure files, declaring the integration complete. This is formalism. True integration is the unification of management logic—using the same process, the same standards, and the same platform for the same management activity, rather than binding three documents into one. After integration, the goal should be to eliminate redundant process nodes, not to retain three sets of processes in a single folder.
The second pitfall is "over-simplification to reduce workload." The purpose of integration is to eliminate redundancy, not to weaken requirements. The emergency preparedness and response requirements of ISO 14001 are mandatory and cannot be relaxed just because they are combined with the safety system's emergency requirements. The integrated documents must meet the minimum requirements of all applicable standards. The practical approach should be to take the union (meeting the highest requirement among all standards) and implement it with more efficient processes.
The third pitfall is "ignoring the acceptance of certification bodies." Although external audit organizations are becoming more open to integrated systems, there are still differences in understanding among different certification bodies and auditors. Companies need to retain a "standard clause to process mapping matrix" that maps each standard's requirements to the corresponding company processes. This matrix serves as a roadmap for internal auditors and as evidence during external audits. When auditors ask about the correspondence of clauses, the matrix can provide quick answers.
The fourth pitfall is "a one-time, comprehensive rollout." Integrating multiple systems is a gradual process, and a phased approach based on priority is more feasible than a comprehensive rollout. It is recommended to start with the integration of support processes—document management, training management, internal audit management, and management review—where the requirements overlap significantly across systems, making integration easier and faster. The integration of core business processes can be done in the second phase, and the integration of records often requires a longer period of historical data accumulation.
Five, Advanced Path from Integration to Unification
After the integration of multiple systems, companies can further advance towards a "unified" management system. Integration and unification are two distinct levels. Integration involves running multiple systems under a single framework, where requirements remain identifiable and traceable; unification, on the other hand, completely breaks down the boundaries of systems, forming a unified, strategy-oriented management system.
The framework of a unified management system typically includes six core elements. A strategic orientation—driven by the company's vision and strategic goals rather than certification requirements. A process system—covering all core processes of the company's operations, without distinguishing between "quality processes" and "safety processes," as all management activities are components of the company's operational processes. An audit team—internal auditors are grouped by process rather than by system, and each auditor has the capability to audit multiple systems. An improvement platform—all nonconformities, corrective actions, and continual improvement activities are managed in a closed loop on a single platform, providing management with a comprehensive view of improvement activities. A performance indicator system—management sees an integrated dashboard that simultaneously displays quality indicators, environmental indicators, safety indicators, and business indicators, rather than multiple disconnected reports. A single management review—top management reviews the operation of all management systems once a year, rather than holding three separate management review meetings.
Companies that achieve a unified management system do not need to prepare for each standard separately during certification audits. Certification bodies can adopt an "integrated audit" approach, covering multiple standards in a single audit. The IAF MD 11 guideline issued by the International Accreditation Forum has provided a framework for integrated audits. This not only significantly reduces the company's management costs but also helps the management team shift from "managing multiple systems" to "managing the company well"—which is the ultimate goal of management system construction. In the long term, a unified management system is also the foundation for the company's digital transformation—unified processes, unified data, and a unified platform are essential for the successful implementation of digitalization.
The core of integrating multiple systems is process-centric, not standard-centric
Knowledge Number: 2.1.3
Version: v20260713
Author: Quality Excellence Think Tank Quality Excellence Think Tank is dedicated to providing systematic knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously improve their quality capabilities.