Integration and Unified Architecture of Multiple Systems —— Practical Path from Multiple Layers to a Single System

Many quality management practitioners face the same challenge: their company has successively passed the ISO 9001 Quality Management System (QMS), ISO 14001 Environmental Management System (EMS), and ISO 45001 Occupational Health and Safety Management System (OHSMS). Later, they introduced the IATF 16949 automotive industry system requirements. Each year, they have to deal with three to four external audits, each requiring the preparation of three different sets of documents, records, and kanbans. Internal auditors have to create three audit plans and write three audit reports. Employees complain that "forms outnumber products," and managers question whether "the systems are helping us or just complicating our work." The root of this issue is not that the systems themselves are flawed, but that the fragmentation between multiple systems causes significant management waste. Integrating multiple systems is not an option but a necessity for companies at a certain stage of management system maturity.

1. Why Fragmentation Occurs in Multiple Systems

Before understanding how to integrate multiple systems, it's essential to understand how fragmentation arises. Most companies implement management systems in a "standard-responsive" manner: if a customer requires ISO 9001 certification, they build a system according to ISO 9001 clauses; if the government demands environmental compliance, they build another system according to ISO 14001; if export is necessary, they add ISO 45001. 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 occur with the introduction of the ISO 50001 Energy Management System and ISO 27001 Information Security Management System. Each additional management system means more documents, more processes, and more training.

This "system-by-system implementation" approach has inherent flaws. First, each system operates independently at the document level. The quality manual, environmental manual, and safety manual are separate documents, and procedure documents are redundantly written—such as "document control procedure" in all three systems, "training management procedure," and "internal audit procedure." For a medium-sized manufacturing company, the total number of procedure documents often exceeds sixty when the systems are independent, with nearly 30% of them being highly repetitive. Second, at the operational level, the same activity is required by multiple systems from different perspectives, forcing on-site personnel to switch between different systems. For example, a equipment maintenance activity is concerned with calibration status and process confirmation by the quality system, waste disposal by the environmental system, and lockout/tagout and protective equipment by the safety system, requiring on-site personnel to consult three different work instructions. Finally, at the audit level, external audit agencies operate independently, with overlapping audit times but repetitive content, causing the company to struggle to keep up.

A deeper issue is that company 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 a structured approach to managing the "things that need to be managed" in the company's operations, and there is only one set of "things that need to be managed" for a company—quality, environment, safety, energy, and information security are different aspects of the same company's risks and requirements, and should be managed uniformly. Quality management guru Deming said that the core of management is understanding and optimizing systems, not building a separate system for each requirement.

2. Three-Layer Framework for Integrating Multiple Systems

After years of industry practice, a mature three-layer 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 layer is the strategic layer. This layer answers the question "why do we need to manage," corresponding to the content of the management manual. The company's quality policy, environmental policy, and safety policy can be merged into a single "integrated management policy," reflecting the highest management's commitment to all management systems. Management objectives can also be integrated—instead of setting separate quality, environmental, and safety objectives, they can be broken down into various indicators under the company's overall business objectives. This level of integration does not change any requirements of the standard clauses; it is purely a change in organizational approach, which is the easiest to implement.

The second layer is the process layer. This layer answers the question "how do we manage," corresponding to procedure documents and process norms. This is the core battlefield for integration. ISO 9001's clause 7.1 (resource management), ISO 14001's clause 7.1 (resources), and ISO 45001's clause 7.1 (resources) belong to different standards but manage the same objects—people, machines, materials, methods, and environment. A company can use a single "human resource management procedure" to cover training, capability, and awareness requirements; 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 "classification by standard clauses" mindset and return to the "classification by business processes" logic. Many companies struggle to advance at this level, primarily due to functional barriers—quality departments are unwilling to share their procedure documents with other departments, fearing a loss of control. This requires the highest management to step in and drive the process.

The third layer is the record layer. This layer answers the question "how well are we managing," corresponding to forms, records, and evidence. This level of integration is the easiest to show results but also the easiest to fall into pitfalls. On the surface, different systems require different record formats, but if viewed from the perspective of "what management problem does this record solve," many records can be merged. For example, a equipment inspection form can include quality parameters, safety parameters, and environmental parameters, rather than having separate forms for the equipment department and the EHS department. Integration at the record level requires a cross-departmental consensus on record design and a unified approval process.

3. Methodology for Integration: Process-Centric Approach

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 company's actual operational processes.

The specific operations can be divided into four steps. The first step is to identify the company's core business processes. Instead of listing them according to standard clauses, start from the entire value chain from order to delivery, and identify the company's core processes, support processes, and management processes. Tools such as the turtle diagram or SIPOC diagram can be used to fully describe the objectives, inputs, outputs, resources, methods, and performance indicators of each process. The second step is to map the requirements of different systems to 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 the document format and numbering rules. Do not use QP-01 for ISO 9001 documents and EP-01 for ISO 14001 documents. It is recommended to adopt a document coding system centered on process numbers, such as "PR-03" representing the procedure document for the third process, with the applicable system standards marked in the document 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 simultaneously covers quality, environmental, and safety requirements.

This 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, while a system based on standard clauses is a "hanging" system. From the high-level structure (HLS) released by ISO, ISO 9001, ISO 14001, and ISO 45001, among other major management system standards, have adopted the same clause structure (Chapters 4 to 10), providing a natural institutional foundation for integrating multiple systems. Companies can fully leverage this commonality to achieve one-time planning and multi-standard coverage at the process level.

4. Common Pitfalls in the Integration Process

In practical implementation, integrating multiple systems can easily fall into several pitfalls, which need to be avoided.

The first pitfall is "document consolidation equals system integration." Some companies take shortcuts by combining three manuals into one book and simply merging procedure documents with the same theme, then declaring the integration complete. This is formalism. True integration is the unification at the management logic level—using the same process, the same set of standards, and the same platform for the same management activity, rather than binding three sets of documents into one. After integration, the goal is 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 reduced just because they are merged with the safety system's emergency requirements, such as lowering the frequency of environmental emergency drills. 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 then implement it with more efficient processes.

The third pitfall is "ignoring the acceptance of certification bodies." Although external audit agencies are becoming more open to integrated systems, there are still differences in understanding among different certification bodies and different auditors. Companies need to retain a "standard clause and process mapping matrix" that maps each standard's requirements to the corresponding company processes. This matrix serves as a roadmap for internal auditors and proof material during external audit receptions. When auditors ask about the clause correspondence, the company can quickly provide answers.

The fourth pitfall is "a one-time, all-encompassing rollout." Integrating multiple systems is a gradual process, and it is more feasible to proceed step-by-step according to priority rather than a full-scale rollout. It is recommended to start with support processes—document management, training management, internal audit management, and management review—these processes have highly overlapping requirements in different systems, making integration easier and more effective. The integration of core business processes can be done in the second stage, and the integration at the record level often requires a longer period of historical accumulation.

5. Advanced Path from Integration to Unification

After integrating multiple systems, companies can further advance towards a "unified" management system. Integration and unification are two distinct levels. Integration places multiple systems under the same framework, where each requirement remains identifiable and traceable; unification, on the other hand, completely breaks down the boundaries of systems, forming a single, unified management system oriented towards the company's strategic goals.

The framework of a unified management system typically includes six core elements. One strategic orientation—driven by the company's vision and strategic goals, not by certification requirements. One process system—covering all core processes of the company's operational management, without distinguishing between "quality processes" and "safety processes"; all management activities are components of the company's operational processes. One audit team—internal auditors are grouped by processes, not by systems, and each auditor has the capability to audit multiple systems. One improvement platform—all nonconformities, corrective actions, and continuous improvement activities are managed in a closed loop on the same platform, allowing management to see the full picture of improvement activities. One set of performance indicators—management sees an integrated management dashboard that simultaneously displays quality indicators, environmental indicators, safety indicators, and business indicators, rather than multiple unrelated reports. One management review—the highest management conducts a single review of all management systems' operations 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 already 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, data, and platforms are the true basis for the implementation of digitalization.

The core of integrating multiple systems is a process-centric approach, not a standard-centric approach.

Knowledge code: 2.1.3

Version: v20260713

Author: Quality Think Tank Quality Think Tank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously improve their quality capabilities.