GB/T 47688-2026General requirements for product lifecycle management (PLM) systems (English PDF)
产品生命周期管理(PLM)系统通用要求
Open the GB/T 47688-2026 preview as PDF
This is a limited preview
Buy now to download the full PDF (37 pages)
Issued by
SAMR; SAC
Level / Type
National · Recommended
Issue date
May 25, 2026
Implementation date
December 1, 2026
Scope
GB/T 47688-2026 is the English-translated version of 产品生命周期管理(PLM)系统通用要求.
GB/T 47688-2026 is the Chinese national standard covering what a PLM system has to do - the product structure and its configurations, the documents and their revisions, the change process, the release states, the integration with design and manufacturing systems and the access control over all of it. First edition, in force from 1 December 2026. It was issued on 25 May 2026 and takes effect on 1 December 2026, as a first edition. The document is under the responsibility of the China Machinery Industry Federation. This page is published from the official record of the 2026 edition; the clause text of a standard this recent is not yet in circulation, and the figures, limits and tables it contains are those of the document itself, delivered in full with the English translation.
Document preview — GB/T 47688-2026
National Standard of the People's Republic of China
- ICS
- 35.240.50
- Classification
- L 67
Issued by: State Administration for Market Regulation; Standardization Administration of the PRC
Contents
- 5 Reference Architecture
- 6 Business Function Requirements
- 6.2 Product Architecture Management
- 6.4 Design Management
- 6.5 Process Management
- 6.6 Experimental Verification
- 6.8 Maintenance Services
- 6.9 Project Management
- 6.11 Quality Management
- 7 Data Requirements
- 8 Platform Requirements
- 8.1 General Component Requirements
5 Reference Architecture
5.1 Architecture Composition A PLM system should include a resource layer, platform layer, data layer, business layer, front-end application layer, and integration layer to provide industry application services. The task is shown in Figure 1.
5.2 Resource Layer The PLM system should be based on hardware and software resource layers and run in a local area network or Internet environment. The resource layer consists of the following components.
a) Hardware resources. including networks, storage, computing, terminals, etc., providing physical support for system operation and data processing, transmission, storage, and applications. support.
b) Software resources. including operating systems, databases, middleware, runtime frameworks, etc., providing the basic software environment for system operation.
5.3 Platform Layer The platform layer should consist of the following.
a) Basic Support. Provides basic engine services, including business modeling engine, visualization engine, message engine, process engine, and transaction management. The system includes a management framework, rules engine, AI engine, log management, and integration interfaces to support the operation of system business functions and to standardize PLM (Product Lifecycle Management). The definition of various objects and business functions in the system ensures the stable operation of the system.
b) General Components. Provides basic management component services, including code management, part management, document management, BOM management, and category management. It includes functions such as data management, product portfolio management, change management, WBS management, task management, process management, and report management to support system data management. And business function applications.
Note. "Part" is a collective term for product components, which can be a single unit or a combination of any complexity, including but not limited to. finished products, semi-finished products, components, parts, and raw materials. Materials, molds, software, services, middleware, virtual components.
5.4 Data Layer The data layer provides system data definition and state management, including data models and data management.
a) Data Model. Defines different elements of the product lifecycle, including demand data, product data, part data, BOM data, and documents. Data, process data, quality data, cost data, change data, test data, simulation data, maintenance data, and resource libraries, etc., are used for... The system provides data support for business operations.
b) Data Management. Provides system business data function services.
5.5 Business Layer Based on the enterprise's product lifecycle planning and demonstration, core businesses such as R&D design, production planning, testing and verification, manufacturing, and maintenance services are included. To meet management needs, the business layer consists of business management and project management.
5.6 Front-end Application Layer The front-end application layer provides entry points for different roles to access the system, mainly including desktop applications, web applications, and mobile applications.
5.7 Integration Layer The integration layer consists of the following components.
6 Business Function Requirements
6.1 Requirements Management Requirements management should include the following functions.
a) Structured definition management;
b) Categorized management;
c) Hierarchical management;
d) Market-oriented and product-oriented demand package management;
e) Status and version management of requirements and requirement packages;
f) Traceability management;
g) Verify closed-loop management;
h) Change management;
i) Distribution and collaborative management;
j) Statistical analysis;
k) Import/Export.
6.2 Product Architecture Management
6.2.1 General Requirements General product architecture management should include the following functions.
a) Classification and management of architectural models;
b) Structured management of architectural models such as functional models, logical models, and physical models;
c) Integration with architecture design tools to support collaborative architecture design;
d) Architecture model check-in and check-out;
e) Electronic approval and management of architectural models;
f) Architecture model change management and impact analysis;
g) Architecture model lifecycle status and version management.
6.2.2 Extended Functionality Product architecture management should be expanded to include the following functionalities.
a) Management of the relationship between the architecture model and the upstream requirements model and downstream design model;
b) Management of the general metamodel and standard model of the architecture;
c) Architecture model review and release.
6.3 Product Management Product management should include the following functions.
a) Product definition management;
6.4 Design Management
6.4.1 General Requirements General design management should include the following functions.
a) EBOM management;
b) Design document management;
c) Management of the association between EBOM and design changes and design model data;
d) Integrates with ECAD and MCAD design systems to support design model management;
e) Visual management of design models;
f) Electronic approval and management of design models;
g) Design data model changes and impact analysis;
h) Structural design collaboration;
i) Collaborative design of electromechanical and software systems;
j) Design data status and version management, including documents, models, and EBOM;
k) Design data import and export;
l) Management of upstream and downstream data relationships;
m) Product configuration management.
6.5 Process Management
6.5.1 General Requirements General process management should include the following functions.
a) PBOM management;
b) Integration with 3D process design and simulation tools to support process model management;
c) Process document management;
d) PBOM management in conjunction with process changes, process models, and process documents;
e) Structured process management;
f) Process changes and impact analysis;
g) Status and version management of process data (including documents, models, PBOM);
h) Visualized work instruction generation and management;
i) Management of the relationship between upstream design and downstream production data;
j) Importing and exporting process documents.
6.5.2 Extended Functionality Process management should be expanded to include the following functions.
a) Integrate with process design tools to achieve consistent model data management between tools and systems;
b) Integration with the process resource library for selection functionality.
6.6 Experimental Verification
6.6.1 General Requirements The test verification should include the following functions.
a) Structured management of test information;
b) Structured management of experimental data;
c) Trial BOM management;
d) Test data package management;
e) Experimental data analysis and management;
f) Management of the integration of testing with functions such as tasks, plans, and product management.
6.6.2 Extended Functionality The experimental verification should be expanded to include the following functions.
a) Integration with other experimental data management systems;
b) Experimental data envelopment analysis.
6.7 Production and Manufacturing Management Production management should include the following functions.
a) Integration with ERP/MES systems to support production data management, including production planning data, manufacturing process data, and manufacturing data. Source data, production material data, quality control data, inspection and testing data, etc.;
b) MBOM management;
c) Management of the association between MBOM and production plan changes and manufacturing model data;
6.8 Maintenance Services
6.8.1 General Requirements General maintenance services should include the following functions.
a) Maintenance BOM management;
b) Maintenance data visualization;
c) Structured management of maintenance information;
d) Maintenance document management;
e) Maintenance plan management, including plan templates and structured standard operating procedures (SOPs);
f) Maintenance records and traceability;
g) Fault and knowledge base management.
6.8.2 Extended Functionality The maintenance service should be expanded to include the following functions.
a) Functionality for managing the association between maintenance and project tasks;
b) Cost-related management functions.
6.9 Project Management
6.9.1 General Requirements General project management should include the following functions.
a) Project library management;
b) Collaborative development of multi-level plans;
c) Project plan approval and issuance;
d) Project plan execution and feedback;
e) Project plan changes;
f) Project execution monitoring;
g) Project schedule calculation;
h) Project deliverables management;
i) Project resource management;
j) Project risk management.
6.9.2 Extended Functionality Project management should be expanded to include the following functions.
a) Statistical analysis of project data;
b) Project planning baseline management;
6.11 Quality Management
6.11.1 General Requirements General quality management should include the following functions.
a) Quality target management;
b) Quality system audit management;
c) Quality review management;
d) Quality problem management;
e) Management of corrective actions for quality problems;
f) Quality issue case management;
g) After-sales quality management;
h) Production process quality control;
i) Comprehensive display of quality information.
6.11.2 Extended Functionality Quality management should be expanded to include the following functions.
a) Quality data package management;
b) Statistical analysis of quality data;
c) Quality data is linked to MBOM for management.
7 Data Requirements
7.1 General Requirements The general data requirements are as follows:
a) Single data source. Ensures the uniqueness of data transmission;
b) Unified coding rules. Establish an enterprise-level coding system with consistent identification rules throughout the entire data lifecycle to ensure data traceability;
c) Scalability, with data exchange and expansion capabilities with ERP, MES, OA and other systems;
d) Verification, supporting the identification of abnormal data and providing early warning prompts.
8.1 General Component Requirements
8.1.1 Coding Management Coding management shall comply with the requirements of section
5.13 of GB/T 33222-2016. Code management should include the following functions.
a) Assign a unique code to each data object;
b) Custom encoding rules.
8.1.2 Part Management Part management should include the following functions.
a) Part attribute definition and management;
b) The Part is associated with the document;
c) Part version and lifecycle control.
8.1.3 Document Management Document management shall comply with the requirements of section
5.1 of GB/T 33222-2016. Document management should include the following functions.
a) Document classification and management;
b) Document version management;
c) Document types are bound to templates and workflows;
d) Visual management of documents;
......
This preview omits tables, figures, formulas and parts of the technical clauses. The complete document — 37 pages — is available in the English PDF.
How to Buy GB/T 47688-2026
- 1Add to cart. Click the "Buy GB/T 47688-2026" button on this page. You can add more standards before checkout.
- 2Checkout. Enter your email and billing details. Payment is processed securely by Stripe (cards, Apple Pay, Google Pay supported).
- 3Instant delivery (0–9 sec). Delivery is automatic: within seconds of payment you'll receive an email with a secure download link. The link stays valid for 72 hours.
- 4Invoice included. A tax invoice is attached to the confirmation email. Need a custom invoice? Contact us.
Related Standards
GB/T 47310-2026 — Determination of total silicon, aluminium, iron, potassium, sodium, calcium, magnesium, manganese, phosphorus, titanium and sulfur in soil - Monochromatic excitation energy dispersive X-ray fluorescence spectrometry
GB/T 47321-2026 — Specification for the warning data exchange of the national emergency early warning dissemination system
GB/T 47293-2026 — Determination of available mercury in soil
Secure payment via Stripe
Payments accepted
GB/T 47688-2026
$305.00