GB/T 18757-2025Enterprise modelling and architecture - Requirements for enterprise-referencing architectures and methodologies (English PDF)

Foreword

This 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".

Introduction

1 Scope

This 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 references

This document has no normative references.

3 Terms and definitions

The following terms and definitions apply to this document.

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.

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.