GB/T 18757-2025 English PDFUS$1419.00 · In stock
Delivery: <= 8 days. True-PDF full-copy in English will be manually translated and delivered via email. GB/T 18757-2025: Enterprise modelling and architecture - Requirements for enterprise-referencing architectures and methodologies Status: Valid GB/T 18757: Historical versions
Basic dataStandard ID: GB/T 18757-2025 (GB/T18757-2025)Description (Translated English): Enterprise modelling and architecture - Requirements for enterprise-referencing architectures and methodologies Sector / Industry: National Standard (Recommended) Classification of Chinese Standard: N10 Classification of International Standard: 25.040.01 Word Count Estimation: 70,712 Date of Issue: 2025-04-25 Date of Implementation: 2025-11-01 Older Standard (superseded by this standard): GB/T 18757-2008 Issuing agency(ies): State Administration for Market Regulation, China National Standardization Administration GB/T 18757-2025: Enterprise modelling and architecture - Requirements for enterprise-referencing architectures and methodologies---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order. ICS 25.040.01 CCSN10 National Standard of the People's Republic of China Replace GB/T 18757-2008 Enterprise Modeling and Architecture Requirements for Enterprise Reference Architecture and Methodology (ISO 15704.2019, IDT) Released on 2025-04-25 2025-11-01 Implementation State Administration for Market Regulation The National Standardization Administration issued Table of contentsPreface III Introduction V 1 Scope 1 2 Normative references 1 3 Terms and Definitions 1 4 Abbreviations 4 5 Requirements for the Enterprise Reference Architecture and Model 5 5.1 General requirements 5 5.2 Applicability and coverage of enterprise architecture 5 5.3 Basic Concepts of Enterprise Reference Architecture 6 6 Components of an Enterprise Reference Architecture11 6.1 Enterprise Reference Model 11 6.2 Modeling Language 13 6.3 Model Representation 14 6.4 General purpose effects 18 6.5 Enterprise Views and Perspectives 19 6.6 Enterprise Reference Modeling Framework 21 6.7 Tools 21 6.8 Module 21 6.9 Enterprise Operation System 22 6.10 Expression 22 Appendix A (Informative) Key Principles for Enterprise Integration and Interoperability 23 A.1 Overview 23 A.2 Enterprise Applicability23 A.3 Corporate identity and mission definition 23 A.4 Division of mission execution and mission control functions 23 A.5 Process structure identification 23 A.6 Process content identification 24 A.7 Life cycle identification 24 A.8 Enterprise Integration 24 A.9 Modularity 25 A.10 Stakeholder Concerns25 Appendix B (Informative) Generic Enterprise Reference Architecture and Methodology (GERAM) 26 B.1 Introduction 26 B.2 Enterprise Structure and Enterprise Integration Framework 27 B.3 GERAM Framework Component Specifications 30 Appendix C (Informative) Relationship between this document and other international standards related to enterprise system architecture 53 C.1 Relationship between international standards related to enterprise system architecture 53 C.2 Important relationships with other standards 53 References 55ForewordThis document is in accordance with the provisions of GB/T 1.1-2020 "Guidelines for standardization work Part 1.Structure and drafting rules for standardization documents" Drafting. This document replaces GB/T 18757-2008 "Requirements for enterprise reference architecture and methodology for industrial automation systems" and Compared with GB/T 18757-2008, in addition to structural adjustments and editorial changes, the main technical changes are as follows. --- Changed the scope of application of the document (see Chapter 1, Chapter 1 of the.2008 edition); --- Deleted the terms "activity" (see 3.1 of the.2008 edition), "attribute" (see 3.3 of the.2008 edition), "behavior" (see 3.4), “Master Plan” (see 3.13 of the.2008 edition), “Methodology” (see 3.14 of the.2008 edition), “Structure” (see 3.19 of the.2008 edition), “system” (see 3.20 of the.2008 edition); --- Changed the terms "architecture" (see 3.1, 3.2 of the.2008 edition), "enterprise" (see 3.4, 3.6 of the.2008 edition), "enterprise model" "Model" (see 3.6, 3.8 of the.2008 edition), "Framework" (see 3.10, 3.9 of the.2008 edition), "Universality" (see 3.11, 3.10 of the.2008 edition), “life cycle” (see 3.12, 3.11 of the.2008 edition), “life course” (see 3.13, 3.12 of the.2008 edition), “use mission” (see 3.14, 3.15 of the.2008 edition), “model” (see 3.15, 3.16 of the.2008 edition), “organization” (see 3.18, 3.17 of the.2008 edition), the definition of “resources” (see 3.21, 3.18 of the.2008 edition); --- Added the terms "level" (see 3.2), "enterprise reference" (see 3.7), "entity" (see 3.8), "environment" (see 3.9), "model-based "of" (see 3.16), "modeling dimensions" (see 3.17), "viewpoints" (see 3.19), "reference benchmarks" (see 3.20), "stakeholders" (see 3.22), "view" (see 3.23), "perspective" (see 3.24); --- Added a chapter on "Abbreviations" (see Chapter 4); --- Deleted the general description of the applicability and coverage of business entity types (see 4.1 of the.2008 edition); --- Added general requirements for enterprise reference architecture and model requirements (see 5.1); --- Added the description of enterprise types (see 5.2.1); --- Added the description of the characteristics of the enterprise architecture (see 5.2.2); --- Added the description of the methodology of enterprise engineering and architecture (see 5.2.3); --- Changed the expression of enterprise design (see 5.2.4, 4.1.2 of the.2008 edition); --- Changed "Concept" to "Basic concepts of enterprise reference architecture" (see 5.3, 4.2 of the.2008 edition); --- Deleted "Overview" (see 4.1.1 of the.2008 edition); --- Added the expression "the span of concept positioning" (see 5.3.1); --- Added the concepts of "interoperability-oriented" (see 5.3.4) and "decision-oriented" (see 5.3.5); --- Changed the concepts of "mission-oriented" (see 4.2.5 of the.2008 edition) and "mission-oriented control" (see 4.2.6), added the sub-concept "economic-oriented" (see 5.3.6.3), and merged the three into the concept "realization-oriented" (see 5.3.6); --- Added the concepts of "technology-oriented" (see 5.3.7) and "environment-oriented" (see 5.3.8); --- Changed the concept of "life cycle" (see 4.2.8 of the.2008 edition) to "life cycle oriented" (see 5.3.9.1), changed the concept of "life cycle" The.2008 edition changed the “life course” to “life course” (see 4.2.9), adding “the interaction between life cycle and life course”. The three are combined to form “life cycle oriented” (see 5.3.9); --- Added the concepts of "stakeholder-oriented" (see 5.3.10), "perspective-oriented" (see 5.3.122), "model-oriented" (see 5.3.122), "Model view oriented" (see 5.3.13), "Enterprise interoperability oriented" (see 5.3.14), "Verification and validation oriented" (see 5.3.15); --- Changed "Components of Enterprise Reference Architecture" to an independent chapter (see Chapter 6, 4.3 of the.2008 edition), deleted "Engineering Methodology" (see 4.3.1 of the.2008 edition), added "Enterprise Reference Model" (see 6.1), changed the structure of the modeling language The requirements for structure, expression, etc. (see 6.2, 4.3.2 of the.2008 edition) and the description of "model representation" are added (see 6.3); --- Changed "common elements" to "common enterprise elements" (see 6.4.1, 4.3.3 of the.2008 edition), changed "partial common model" to "Partial enterprise model" (see 6.4.2, 4.3.4 of the.2008 edition), change "specific model" to "specific enterprise model" (See 6.4.3, 4.3.5 of the.2008 edition); --- Added descriptions of enterprise views and perspectives (see 6.5) and enterprise reference modeling framework (see 6.6); --- Changed "Tools" (see 6.7, 4.3.6 of the.2008 edition), "Modules" (see 6.8, 4.3.7 of the.2008 edition), "Enterprise Operation System" "System" (see 6.9, 4.3.8 of the.2008 edition) and other expressions; --- Deleted the expression "vocabulary" (see 4.5 of the.2008 edition); --- Deleted the chapter "Integrity and Consistency" (see Chapter 5 of the.2008 edition). This document is equivalent to ISO 15704.2019 "Enterprise modeling and architecture – Requirements for enterprise reference architecture and methodology". For ease of use, the following minimal editorial changes have been made to this document. --- The term numbering in 3.4 of the original international standard is incorrect. It is corrected from "3.13" to "3.14". Please note that some of the contents of this document may involve patents. The issuing organization of this document does not assume the responsibility for identifying these patents. This document was proposed by the China Machinery Industry Federation. This document is under the jurisdiction of the National Automation System and Integration Standardization Technical Committee (SAC/TC159). This document was drafted by. Beijing Institute of Automation of the Mechanical Industry Co., Ltd., Tsinghua University, China Machinery Industry Federation, Zhejiang University China University of Posts and Telecommunications, Weichai Power Co., Ltd., Zhejiang Tianneng New Energy Co., Ltd., China University of Metrology, Kingdee Software (China) Co., Ltd., Tianneng New Energy (Huzhou) Co., Ltd., Beijing Dipu Technology Co., Ltd., Jiuke Information Technology (Shenzhen) Co., Ltd., Jiangxi Telecom Information Industry Co., Ltd. Limited company. The main drafters of this document are. Tang Cong, Liu Xin, Huang Shuangxi, Yu Kuo, Gong Yuping, Yang Shuping, Wang Yiqin, Wang Haidan, Yang Qiuying, Du Yichao, Gao Jing, Zhong Xiao, Li Qing, Tang Bo, Zhu Wenguang, Qin Xiugong, Jiang Jiang, Zhou Yan, Wang Yezhong, He Sheng, Li Linhe, Zhao Jiehui, Wan Zhengyong, Wu Junzhuo. This document was first published in.2002 as GB/T 18757-2002, first revised in.2008, and this is the second revision.Introduction0.1 Principles of Enterprise Architecture and Models In the Industrial and Information Age, companies improve their local and global marketing by innovating and improving their manufacturing and business operations. In the operational phase, they employ a variety of resources such as human resources, information systems, automated machinery, and business services, which individually and collectively provide Provides the various functions required to promote the business process and its combined activities. The deployment of these resources, target markets, and coordinated operations are required to complete the enterprise Mission requires appropriate operating rules and organizational structure to enable the company to provide customers with products and services consistent with agreed standards. Enterprises operate in uncertain and changing market and environmental conditions, making the continuous development of enterprise engineering beneficial. In a heterogeneous environment, multiple components are working together using different models and systems. In addition, most enterprises interact with other The company operates in the context of a business, such as a supply chain or a parent company. Therefore, the company's personnel are in the company's mission, operating rules, manufacturing and operations There are various responsibilities for the concept and ongoing development of processes, organizational structures, and supporting resources and services. Given the complexity of these projects, it is necessary to adopt means to assess, build, coordinate and support these engineering activities, including means of collaborative support and interoperability. The broad enterprise reference architecture concerns and enterprise modeling components form a reference foundation for preparing and coordinating enterprise By adopting and adapting such a reference base, Based on the enterprise's engineering project progress, enterprise personnel will improve the enterprise, improve communication with stakeholders and utilize enterprise resources. With the right toolset, business people will be able to use clear business designs and models repeatedly and more practically, achieving business success on a continuous basis. Continuous improvement of industrial engineering and enterprise operations. The reference benchmark needs to include the following capabilities. --- Attract stakeholders who fulfill the corporate mission (manufacturing, transportation, service providers, etc.) and operational stakeholders; ---Describe appropriate solutions to problems identified within the enterprise; ---Model the entire life cycle of an enterprise integration project, from initial concept to development, operation, and finally retirement or elimination; ---Includes the people, processes, resources and organizations involved in executing, managing and controlling the corporate mission. From an enterprise engineering perspective, the differences include. ---Enterprise architecture refers to the development, implementation and operation of a project (such as enterprise integration or other enterprise-related projects, usually A configuration of the physical components, logical relationships, and human interactions involved in a project process; ---System architecture refers to the configuration of the physical components and logical relationships of the systems that form part of an enterprise; for example, the entire enterprise or The computer control system part of the product. This document does not propose or adopt a specific approach to creating or using an enterprise architecture or model. The focus is on establishing a It is a reference benchmark for defining enterprise solutions rather than a design to meet stated requirements. This document identifies a broad set of potential artifacts for expressing enterprise reference architectures and their associated methodologies. Not all Artifacts are applicable to all architectural design work, and not all artifacts are necessary or even desirable. The identification of these artifacts ensures that this document meets the needs of as many enterprise reference architectures and methodologies as possible. Users need to assess not only the value of producing a certain artifact, but also the value of that artifact in the context of changing reference enterprises. The maintenance value of the product. 0.2 Rationale of this document In the area of enterprise integration and modeling, well-designed standards provide enterprise architects and designers with a reference point, thereby significantly reducing Low investment risk. In cases where silos do exist, these standards help architects or designers create the necessary transformations to make the silos The Enterprise Reference Model standard enhances interoperability by establishing the elements required to support enterprise architecture models. Acting nature. This document defines the concepts, rules, and requirements for describing an enterprise architecture, most commonly in the form of a model, with the purpose of guiding Therefore, this document specifies the requirements for building the enterprise reference architecture (see Chapter 5) and the enterprise reference model. This document provides a reference baseline for enterprise architecture and models for enterprise activity personnel modeling. Guidelines and constraints. 0.3 Advantages of this document The requirements for enterprise reference architecture and model reference benchmarks in this document allow for the development of enterprise architecture and related methodologies and languages. The completeness of the project is assessed to meet current and future architectural work. This document will help guide the development of the proposal. This document uses the same technical field terminology for designs of compliant implementations to facilitate information sharing. This document will help guide enterprise infrastructure selection or the creation of an applicable reference architecture and use related terminology. The user of this document is expected to be. ---Enterprise planners, builders, improvers, and analysts use requirements to check the integrity of their activities; ---Enterprise reference model builders use these requirements to ensure consistency between models to achieve model interoperability; --- Developers of relevant enterprise standards shall use these requirements to ensure the consistency of their standards with this document. NOTE. Although the requirements set out in this document cover a wide range of enterprise considerations, many users find it more beneficial to develop a specific framework. The framework is a methodological choice by the user and is beyond the scope of this document. Annex B discusses a framework consistent with this document. Other international standards provide Provides further framework guidance. Enterprise Modeling and Architecture Requirements for Enterprise Reference Architecture and Methodology1 ScopeThis document specifies the reference baseline of enterprise architecture concepts and principles to guide enterprise development, enterprise integration, enterprise interoperability, human This document further specifies the requirements for models and languages created to express such enterprise architectures. This document defines the terminology, concepts, and principles necessary for enterprise architecture to address stakeholder concerns and execute enterprise innovation. This document is the basis for creating or adjusting the enterprise architecture and modeling The basis of standards. This document does not define a standard enterprise, a standard organizational structure, standard enterprise processes, or standard enterprise data. Additionally, this document does not specify Enterprise modeling process.2 Normative referencesThis document has no normative references.3 Terms and definitionsThe following terms and definitions apply to this document. 3.1 Architecture conceptualization of the form, function and fitness for purpose of an enterprise (3.4) within its environment (3.9) in terms of its elements, the relationships between them, the relationship between the enterprise and the environment, and the principles guiding the design and development of enterprises. Note 1 to entry. Since architecture in an enterprise context (e.g., enterprise architecture) is always conceptual, the expression of architecture as an architectural description This is achieved through a model of the enterprise reality to which the architecture applies. The detailed design that conforms to the enterprise architecture description is close to the enterprise reality. Often takes a less abstract form. Note 2 to entry. The concept of fitness for purpose distinguishes architecture from other features of design by adding aspects of efficiency and effectiveness to the form and function of a design. Obligation - This is a distinguishing characteristic that combines the temporary components necessary to manage the enterprise with the components required to achieve and maintain superior enterprise performance. The intentional composition of the elements is distinguished. [Source. ISO /IEC /IEEE42010.2011,3.2, modified] 3.2 aspect Distinctive features projected from the content of the integrated enterprise model (3.6). NOTE In this document, this term generally refers to a collection of problems that can be better solved by looking at different views (3.23), that is, by views that span other model views. A single model representation cannot handle the size and scope of these sets of concerns well, but it can be solved by drawing on existing model view content. Select compound views to render efficiently. 3.3 Business Process Partially ordered, often nested, set of enterprise (3.4) activities that can be performed to achieve specific objectives of the enterprise or part of it The desired result. ......Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 18757-2025_English be delivered?Answer: Upon your order, we will start to translate GB/T 18757-2025_English as soon as possible, and keep you informed of the progress. The lead time is typically 5 ~ 8 working days. The lengthier the document the longer the lead time.Question 2: Can I share the purchased PDF of GB/T 18757-2025_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 18757-2025_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to Sales@ChineseStandard.net. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.Question 5: Should I purchase the latest version GB/T 18757-2025?Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version GB/T 18757-2025 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically. |
