Standard No.:	GB/T 43201.3-2023
English Name:	Industrial automation systems and integration—Standardized procedures for production systems engineering—Part 3:Information flows in production planning processes
Chinese Name:	工业自动化系统与集成 生产系统工程的标准化程序 第3部分：生产计划过程中的信息流
Chinese Classification:	N10    Industrial automation and control device in general
Professional Classification:	GB    National Standard
ICS Classification:	25.040.40 25.040.40    Industrial process measurement and control 25.040.40
Source Content Issued by:	SAMR; SAC
Issued on:	2023-9-7
Implemented on:	2024-4-1
Status:	valid
Target Language:	English
File Format:	PDF
Word Count:	25000 words
Translation Price(USD):	900.0
Delivery:	via email in 1~3 business day

Robotics - Modularity for service robots-Part 1 : General requirements 1 Scope This document presents requirements and guidelines on the specification of modular frameworks, on open modular design and on the integration of modules for realising service robots in various environments, including personal and professional sectors. The document is targeted at the following user groups: - modular service robot framework developers who specify performance frameworks in an unambiguous way; - module designers and/or manufacturers who supply end users or robot integrators; - service robot integrators who choose applicable modules for building a modular system. This document includes guidelines on how to apply existing safety and security standards to service robot modules. This document is not a safety standard. This document applies to service robots, although the modularity principles presented in this document can be utilized by framework developers, module manufacturers, and module integrators from other fields not necessarily restricted to robotics. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO 9787 Industrial robots Coordinate systems and motion nomenclatures Note: GB/T 16977-2019 Robots and robotic devices - Coordinate systems and motion nomenclatures (ISO 9787: 2013, IDT) ISO 12100: 2010 Safety of machinery - General principles for design - Risk assessment and risk reduction Note: GB/T 15706-2012 Safety of machinery - General principles for design - Risk assessment and risk reduction (ISO 12100:2010, IDT) ISO/TR 22100-4 Safety of machinery - Relationship with ISO 12100 - Part 4 : Guidance to machinery manufacturers for consideration of related IT-security (cyber security) aspects ISO/IEC 27032 Information technology - Security techniques - Guidelines for cybersecurity IEC 61076-1 Connectors for electronic equipment - Product requirements - Part 1 : Generic specification IEC 61984 Connectors - Safety requirements and tests Note: GB/T 34989-2017 Connectors - Safety requirements and tests (IEC 61984:2008, MOD) IEC/TS 62443-1-1 Industrial communication networks - Network and system security - Part 1-1: Terminology, concepts and models Note: GB/T 40211-2021 Industrial communication networks - Network and system security - Terminology, concepts and models (IEC/TS 62443-1-1:2009, IDT) IEC 62443-2-1 Industrial communication networks - Network and system security - Part 2-1 : Establishing an industrial automation and control system security program Note: GB/T 33007-2016 Industrial communication networks - Network and system security - Establishing an industrial automation and control system security program (IEC 62443-2-1: 2010, IDT) IEC 62443-3-3 Industrial communication networks - Network and system security - System security requirements and security levels Note: GB/T 35673-2017 Industrial communication networks - Network and system security - System security requirements and security levels (IEC 62443-3-3: 2013, IDT) NIST SP800-154 Guide to data-centric system threat modelling NIST SP 800-160 vols 1 and 2 Systems security engineering considerations for a multidisciplinary approach in the engineering of trustworthy secure systems 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 General terms 3.1.1 abstraction layer interface to the system that allows some or all of the capabilities of the system to be accessed in a different and generally more abstract manner Note: An abstraction layer fora module is the same in the case where the system is the module. 3.1.2 connector physical mechanism that enables connection and disconnection between parts of the system Example: Communication, powering, mechanical linking. 3.1.3 electrical interface combination of connectors and the electrical properties for transmitting power, analogue or digital signals 3.1.4 execution life cycle finite state machine defining all stages of execution of a part's function 3.1.5 error discrepancy between a computed, observed or measured value or condition, and the true, specified or theoretically correct value or condition [Source: IEC 60050-192:2015, 192-03-02, modified] 3.1.6 failure loss of ability to perform as required [Source: IEC 60050-192:2015, 192-03-01, modified] 3.1.7 fault inability to perform as required, due to an internal state [Source: IEC 60050-192:2015, 192-04-01, modified] 3.1.8 function defined objective or characteristic action of a system or component or module [Source: ISO/IEC/IEEE 24765, 3.1206-5, modified.] 3.1.9 functional safety part of the overall safety relating to the equipment under control (EUC) and the EUC control system that depends on the correct functioning of the electrical, electronic and programmable electronic (E/E/PE) safety-related systems and other risk reduction measures [Source: GB/T 20438.4-2017, 3.1.12] 3.1.10 hardware abstraction layer HAL abstraction layer for a component/module that contains hardware aspects, with the abstraction layer providing control of the component/module via a software interface Note: The purpose of a HAL is usually so that different module implementations can be accessed through the same software interface. 3.1.11 information model abstraction and representation of the entities in a managed environment, their properties, attributes and operations, and the way that they relate to each other Note: The information model is independent of any specific repository, usage of software aspects, protocol, or platform. 3.1.12 security combination of confidentiality, integrity, and availability [Source: ISO/TR 17522:2015, 3.19] 3.2 Terms related to component 3.2.1 component part of something that is discrete and identifiable with respect to combining with other parts to produce something larger Note 1: Component can be either software or hardware. A component that is mainly software or hardware can be referred to as a software or a hardware component respectively. Note 2: Component does not need to have any special properties regarding modularity. Note 3: Component and module have been used interchangeably in general terms, but to avoid confusion the term module is used to refer to a component that meets the guidelines presented in this document. Note 4: A module is a component, whereas a component does not need to be a module. 3.2.2 software component component whose implementation consists of a computer programmed algorithm 3.2.3 hardware component component whose implementation consists of physical elements and possibly any embedded software necessary for its operation 3.3 Terms related to module 3.3.1 composability ability to assemble modules logically and physically (without need for adaptation of the modules or additional interfacing work) using various combinations into new modules Note : While “integration” generally implies significant effort, “composition” generally implies limited to no effort.