25 - MANUFACTURING ENGINEERING
ICS 25 Details
MANUFACTURING ENGINEERING
MASCHINENBAU
TECHNIQUES DE FABRICATION
IZDELAVNA TEHNIKA
General Information
Frequently Asked Questions
ICS 25 is a classification code in the International Classification for Standards (ICS) system. It covers "MANUFACTURING ENGINEERING". The ICS is a hierarchical classification system used to organize international, regional, and national standards, facilitating the search and identification of standards across different fields.
There are 13111 standards classified under ICS 25 (MANUFACTURING ENGINEERING). These standards are published by international and regional standardization bodies including ISO, IEC, CEN, CENELEC, and ETSI.
The International Classification for Standards (ICS) is a hierarchical classification system maintained by ISO to organize standards and related documents. It uses a three-level structure with field (2 digits), group (3 digits), and sub-group (2 digits) codes. The ICS helps users find standards by subject area and enables statistical analysis of standards development activities.
e-Library Subscription
Create subscription and get permanent access to documents within 25 - MANUFACTURING ENGINEERING
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
- Amendment7 pagesEnglish languagee-Library read for1 day
- Amendment9 pagesEnglish languagee-Library read for1 day
This part of EN 61326 is a product family standard specifying requirements for immunity and emissions regarding electromagnetic compatibility (EMC) for electrical equipment, operating from a supply or battery of less than 1 000 V AC or 1 500 V DC or from the circuit being measured. Equipment intended for professional, industrial-process, industrial-manufacturing and educational use is covered by this part. It includes equipment and computing devices for - measurement and test; - control; - LABORATORY use; - accessories intended for use with the above (such as sample handling equipment), intended to be used in industrial and non-industrial locations.
- Draft16 pagesEnglish languagee-Library read for1 day
- Amendment9 pagesEnglish languagee-Library read for1 day
IEC 62264-2:2026 specifies interface content exchanged between manufacturing control functions and other enterprise functions as interrelated information models. The information models are represented as an interrelated collection of conceptual object models which can be used for the implementation of applications with logical data and physical data models. The data exchanges in interfaces are scoped as between Level 3 manufacturing operations and Level 4 business systems in the hierarchical model defined in IEC 62264-1. The purpose of this document is to reduce the risk, cost, and errors associated with interface implementation. Since this document covers many manufacturing operations and enterprise domains and there are many different standards for those domains, the semantics of this data exchange standard are described at a conceptual level intended to enable the other standards to be mapped to these semantics. To this end, this document defines a set of elements contained in the generic interface, together with a mechanism for extending the interface content for implementations. The scope is limited to the definition of object models and attributes of the exchanged information defined in the IEC 62264-1. This third edition cancels and replaces the second edition published in 2013. It is published as a double logo standard. This edition constitutes a technical revision. Due to the extent of the changes and updates, this document cannot ensure backward compatibility to implementations based on older editions. This edition includes the following significant technical changes with respect to the previous edition and ANSI/ISA 95.00.02-2018 (ED3): a) object models are added for the use of interactive communications to notify subscribers about the occurrence of events and to provide context information about the event, making the information exchange more efficient and consistent. The added object models were the operations event model and operations record model. b) operations location model and spatial definition attribute added to allow the description of operation locations. c) operations test model added to define how test specifications and test results are related to testable objects, operations test requirements, actual resource, and work definitions. d) definition of possible measurement uncertainty sub-attributes for all value, quantity and duration attributes defined in this document. e) updated hierarchy scope model. f) removed as separate models in this edition were the models for product definition, production schedule, production performance, and production capability. Their content is covered for all manufacturing operations management categories under operations models. g) object model was added for the operations segment capability as a collection of resources related to other operations models. h) updated relationship name and role name conventions established in 3.3.4 and implemented across all models and associated tables. i) updated all objects’ relationship role table with explicit source and target names. j) updated common header attributes for objects and property objects established in 4.5 and implemented across all models and associated tables. k) updated explanation of the ‘relationships between resource reference objects in operations management information models and resource models. These additional resource relationships are added to all operations management models. l) added an annex explanation for implementation options for specifying values in unit of measurement a
- Draft476 pagesEnglish languagee-Library read for1 day
IEC 62841-3-16:2025 applies to transportable belt sanders, disc sanders and belt/disc sanders which are equipped with – a sanding belt; or – a sanding disc; or – a sanding belt and a sanding disc for sanding solid materials. This document does not apply to hand-held disc-type sanders. NOTE 101 Hand-held disc-type sanders are covered by IEC 62841-2-3. This document does not apply to hand-held belt sanders. NOTE 102 Hand-held belt sanders are covered by IEC 62841-2-4. This Part 3-16 is to be used in conjunction with the first edition of IEC 62841-1:2014 and IEC 62841-1:2014/AMD1:2025. This Part 3-16 supplements or modifies the corresponding clauses in IEC 62841-1:2014, so as to convert it into the IEC Standard: Particular requirements for transportable belt sanders, disc sanders and belt/disc sanders. Where a particular subclause of IEC 62841-1:2014 is not mentioned in this Part 3-16, that subclause applies as far as relevant. Where this document states "addition", "modification" or "replacement", the relevant text in IEC 62841-1:2014 is to be adapted accordingly. NOTE The attention of National Committees is drawn to the fact that equipment manufacturers and testing organizations can need a transitional period following publication of a new, amended or revised IEC publication in which to make products in accordance with the new requirements and to equip themselves for conducting new or revised tests. It is the recommendation of the committee that the content of this publication be adopted for implementation nationally not earlier than 36 months from the date of publication.
- Draft19 pagesEnglish languagee-Library read for1 day
IEC 62541-9:2026 specifies the representation of Alarms and Conditions in the OPC Unified Architecture. Included is the Information Model representation of Alarms and Conditions in the OPC UA address space. Other aspects of alarm systems like alarm philosophy, life cycle, alarm response times, alarm types and many other details are captured in standards such as IEC 62682 and ISA 18.2. The Alarms and Conditions Information Model in this document, is designed in accordance with IEC 62682 and ISA 18.2. Annex C specifies a recommended mapping between OPC Classic Alarm & Events (A&E) servers to the model described in this document. Annex A describes recommended localized names for Alarm states. Annex B describes examples (e.g. Event sequences, Alarm areas in AddressSpace). This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of "Comment" parameter to Alarm shelving methods;
b) addition of method that allows a client to get the members of a group, since it is possible that the AddressSpace does not expose instances of alarms;
c) addition of deadband properties for all limits in the limit AlarmType (from which all other types described in this issue are derived);
d) addition of text explaining the disabling of alarms is no longer supported in ISA 18.2 and that it is maintained in this document for backward compatibility, but that it is recommended that Alarm not be disabled;
e) addition of optional severities for limit alarms;
f) addition of new AlarmState variable type that can be used to collect alarm information for displays on graphics;
g) addition of SupportsFilterRetain property to improve Client filtering;
h) removal of ConditionSubClassId and ConditionSubClassNames from the conditiontype definition since they are now defined in BaseEventType.
- Standard337 pagesEnglish languagesale 15% off
- Standard330 pagesEnglish and French languagesale 15% off
- Standard330 pagesEnglish and French languagesale 15% off
- Amendment16 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 is part of the overall OPC Unified Architecture (OPC UA) standard series and defines the information model associated with Data Access (DA). It particularly includes additional VariableTypes and complementary descriptions of the NodeClasses and Attributes needed for Data Access, additional Properties, and other information and behaviour.
The complete address space model, including all NodeClasses and Attributes is specified in IEC 62541-3. The services to detect and access data are specified in IEC 62541-4.
Annex A specifies how the information received from OPC COM Data Access (DA) Servers is mapped to the Data Access model.
- Standard96 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 is part of the overall OPC Unified Architecture specification series and defines the information model associated with Aggregates.
Programmatically produced aggregate examples are listed in Annex A.
- Standard68 pagesEnglish languagee-Library read for1 day
This document supplements or modifies the corresponding clauses in IEC 62841-1, so as to convert it into the IEC Standard: Particular requirements for hand-held die grinders and small rotary tools. IEC 62841-1:2014, Clause 1 is applicable, except as follows:
This document applies to hand-held die grinders and to small rotary tools for mounted accessories not exceeding 55 mm in diameter and for mounted sanding accessories not exceeding 80 mm in diameter such as:
- threaded cones and plugs that are threaded on a mandrel with an unrelieved shoulder flange,
- mandrel mounted wheels, and
- rotary files
with a rated speed not exceeding a peripheral speed of the accessory of 80 m/s at rated capacity.
This document does not apply to straight and vertical grinders utilizing flanges for driving an abrasive accessory.
NOTE 101 Straight and vertical grinders are covered by IEC 62841-2-3.
- Standard28 pagesEnglish languagee-Library read for1 day
This part of IEC 62541, the IEC standards series dedicated to the OPC Unified Architecture, defines an Information Model. The Information Model describes the basic infrastructure to model file transfers.
NOTE In the previous version, File Transfer was in IEC 62541-5:2020, Annex C.
- Standard30 pagesEnglish languagee-Library read for1 day
IEC 62541-100:2025 defines the information model associated with Devices. This document describes three models which build upon each other as follows:
• The (base) Device Model is intended to provide a unified view of devices and their hardware and software parts irrespective of the underlying device protocols.
• The Device Communication Model adds Network and Connection information elements so that communication topologies can be created.
• The Device Integration Host Model finally adds additional elements and rules required for host systems to manage integration for a complete system. It enables reflecting the topology of the automation system with the devices as well as the connecting communication networks.
This document also defines AddIns that can be used for the models in this document but also for models in other information models. They are:
• Locking model – a generic AddIn to control concurrent access,
• Software update model – an AddIn to manage software in a Device.
This second edition cancels and replaces the first edition published in 2015. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a a ComponentType that can be used to model any HW or SW element of a device has been defined and a SoftwareType has been added as subtype of ComponentType;
b the new OPC UA interface concept and defined interfaces for Nameplate, DeviceHealth, and SupportInfo has been added.
c) a new model for Software Update (Firmware Update) has been added;
d) a new entry point for documents where each document is represented by a FileType instance has been specified;
e) a model that provides information about the lifetime, related limits and semantic of the lifetime of things like tools, material or machines has been added.
- Standard156 pagesEnglish languagee-Library read for1 day
IEC 62541-16:2025 defines an Information Model. The Information Model describes the basic infrastructure to model state machines.
NOTE State Machines were dealt with in IEC 62541‑5:2020, Annex B. In newer versions of IEC 62541‑5 this Annex B was removed and replaced by this document
- Standard39 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 defines the OPC Unified Architecture (OPC UA) Services. The Services defined are the collection of abstract Remote Procedure Calls (RPC) that are implemented by OPC UA Servers and called by OPC UA Clients. All interactions between OPC UA Clients and Servers occur via these Services. The defined Services are considered abstract because no particular RPC mechanism for implementation is defined in this document. IEC 62541-6 specifies one or more concrete mappings supported for implementation. For example, one mapping in IEC 62541-6 is to UA-TCP UA-SC UA-Binary. In that case the Services described in this document appear as OPC UA Binary encoded payload, secured with OPC UA Secure Conversation and transported via OPC UA TCP.
Not all OPC UA Servers implement all of the defined Services. IEC 62541-7 defines the Profiles that dictate which Services must be implemented in order to be compliant with a particular Profile.
A BNF (Backus-Naur form) for browse path names is described in Annex A.
- Standard249 pagesEnglish languagee-Library read for1 day
IEC 62541-19: 2025 defines an Information Model of the OPC Unified Architecture. The Information Model describes the basic infrastructure to reference from an OPC UA Information Model to external dictionaries like IEC Common Data Dictionary or ECLASS.
- Standard19 pagesEnglish languagee-Library read for1 day
IEC 62541-1:2025 presents the concepts and overview of the OPC Unified Architecture (OPC UA). Reading this document is helpful to understand the remaining parts of the IEC 62541 series. Each of the other parts is briefly explained along with a suggested reading order. This first edition cancels and replaces IEC TR 62541-1 published in 2020
- Standard33 pagesEnglish languagee-Library read for1 day
IEC 62541-5:2026 This edition includes the following significant technical changes with respect to the previous edition:
a) Annex B has been removed and used to create IEC 62451-16;
b) Annex C has been removed and used to create IEC 62451-20;
c) currency information model has been added;
d) information model for Interfaces and AddIns has been added;
e) information model for Method Metadata has been added;
f) MaxSessions, MaxSubscriptions, and MaxMonitoredItems have been added to capabilities;
g) information model for ordered list of objects has been added;
h) PortableQualifiedName and PortableNodeId DataTypes have been added;
i) UriString DataType has been added;
j) SemanticVersionString DataType has been added;
k) AssociatedWith Reference Type has been added;
l) ConfigurationVersion Property has been added to NamespaceMetadataType;
m) AuditClientEventType and AuditClientUpdateMethodResultEventType have been added;
n) ModelVersion has been added to NamespaceMetadataType;
o) NoTransparentBackupRedundancyType has been added to support a Primary/Standby use case;
p) BitFieldType and BitFieldDefinitionType have been added.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
- Standard193 pagesEnglish languagee-Library read for1 day
IEC 62541-7: 2025 specifies value and structure of Profiles in the OPC Unified Architecture.
OPC UA Profiles are used to segregate features with regard to testing of OPC UA products and the nature of the testing. The scope of this document includes defining functionality that can only be tested. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are covered by this document.
Most OPC UA applications will conform to several, but not all of the Profiles.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Profiles and ConformanceUnits are not part of this document, but are solely managed in a public database as described in Clause 1.
- Standard165 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 defines the Information Model associated with Programs in OPC Unified Architecture (OPC UA). This includes the description of the NodeClasses, standard Properties, Methods and Events and associated behaviour and information for Programs.
The complete AddressSpace model including all NodeClasses and Attributes is specified in IEC 62541-3. The Services such as those used to invoke the Methods used to manage
Programs are specified in IEC 62541-4.
An example for a DomainDownload Program is defined in Annex A.
- Standard46 pagesEnglish languagee-Library read for1 day
IEC 62541-21:2026 defines the life cycle of Devices and Composites and mechanisms to verify their authenticity, set up their security and maintain their configuration.
The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the NamespaceUri for all NodeIds and the actual NodeIds.
- Standard58 pagesEnglish languagee-Library read for1 day
IEC 62541-24:2026 specifies an OPC UA information model to expose information, at what dates and times specific actions are executed by the OPC UA Server. Those schedules can optionally also be manipulated via the information model.
The schedule defines on which dates they are active, and can also reference global calendars representing specific dates, for example public holidays. In addition, the schedule defines times and actions that will be executed at that time. The model defines writing Variables and calling Methods but can be extended to other actions as well.
The NamespaceUri for all NodeIds defined in this document is defined in Annex A.
- Standard34 pagesEnglish languagee-Library read for1 day
IEC 62841-4-4:2020 This document applies to hand-held and walk-behind lawn trimmers and lawn edge trimmers, used by a standing operator for cutting grass, weeds or similar soft vegetation, and grass trimmers, brush cutters and brush saws used by a standing operator for cutting grass, weeds, brush, bushes, saplings and similar vegetation.
This document does not apply to
– hand-held machines having a mass of 18 kg or greater;
– self-propelled lawn trimmers or lawn edge trimmers;
– scissors type lawn trimmers and lawn edge trimmers;
– machines equipped with metallic cutting accessories consisting of more than one piece, e.g. pivoting chains or flail blades;
– edgers with rigid and/or metallic cutting devices.
Annex EE provides an informative summary of characteristics for lawn trimmers, lawn edge trimmers, grass trimmers, brush cutters and brush saws.
Brush cutters and brush saws covered by this document are designed only to be operated with the machine to the right of the operator.
- Standard116 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 belongs to the OPC Unified Architecture standards series and defines the Information Model associated with Historical Access (HA). It particularly includes additional and complementary descriptions of the NodeClasses and Attributes needed for Historical Access, additional standard Properties, and other information and behaviour.
The complete AddressSpace Model including all NodeClasses and Attributes is specified in IEC 62541-3. The predefined Information Model is defined in IEC 62541-5. The Services to detect and access historical data and events, and description of the ExtensibleParameter types are specified in IEC 62541-4.
This document includes functionality to compute and return Aggregates like minimum, maximum, average etc. The Information Model and the concrete working of Aggregates are defined in IEC 62541-13.
Conventions for Historical Access Clients are informatively provided in Annex A.
- Standard77 pagesEnglish languagee-Library read for1 day
IEC 62541-23:2025 defines ReferenceTypes commonly used in industrial Information Models. They are more specific than the ReferenceTypes in IEC 62541‑3 which are an inherent part of the OPC UA Address Space Model.
- Standard28 pagesEnglish languagee-Library read for1 day
IEC 62541-6:2025 specifies the mapping between the security model described in IEC 62541‑2, the abstract service definitions specified in IEC 62541‑4, the data structures defined in IEC 62541‑5 and the physical network protocols that can be used to implement the OPC UA specification.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of support for ECC to UA Secure Conversation;
b) use of the AuthorityKeyIdentifier extension in Certificate Revocation Lists;
c) enhancement of JSON mapping of Unions;
d) addition of Decimal data type encoding.
e) description of ECC keyUsage rules;
f) addition of Media assigned by IANA to UANodeSet definition;
g) addition of requirements for user and issuer Certificates;
h) addition of rules which specify what happens when DateTime precision is lost;
i) addition of rules to allow for the truncation of strings containing embedded nulls.
J) definition of a normative string representation for NodeId, ExpandedNodeId and QualifiedName for JSON mapping.
k) requirement that TAI times be converted to UTC;
l) new possibility to omit Symbol if unknown in JSON encoding;
m) addition of fields needed to support RolePermissions to the UANodeSet
- Standard144 pagesEnglish languagee-Library read for1 day
IEC 62541-22:2025 specifies an OPC UA Information Model for a basic set of network related components used in other Information Models.
The initial version of this document defines parameter sets for TSN Talkers and Listeners as well as network interfaces and ports as shown in Figure 1. A future version of this document is expected to have a broader scope of other network technologies than Ethernet only.
- Standard43 pagesEnglish languagee-Library read for1 day
IEC 62541-12:2025 specifies how OPC Unified Architecture (OPC UA) Clients and Servers interact with DiscoveryServers when used in different scenarios. It specifies the requirements for the LocalDiscoveryServer, LocalDiscoveryServer-ME and GlobalDiscoveryServer. It also defines information models for Certificate management, KeyCredential management and AuthorizationServices.
Annex A informatively discusses deployment and configuration aspects.
Annex B defines NodeSet and numeric NodeIds.
Annex F provides installation rules for the LDS.
Annex H compares the Certificate management defined in this document with IETF RFC 7030.
This second edition cancels and replaces the first edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of a "Quantity Model" which can be referenced from EngineeringUnit Properties. The model defines quantities and assigned units. In addition it provides alternative units and the conversion to them;
b) addition of rules for ValuePrecision Property:
• can also be used for other subtypes like Duration and Decimal.
• additional rules when ValuePrecision has negative values.
- Standard147 pagesEnglish languagee-Library read for1 day
IEC 62541-14:2026 defines the PubSub communication model. It defines an OPC UA publish subscribe pattern which complements the client server pattern defined by the Services in IEC 62541-4. See IEC 62541-1 for an overview of the two models and their distinct uses.
PubSub allows the distribution of data and events from an OPC UA information source to interested observers inside a device network as well as in IT and analytics cloud systems.
This document consists of
• a general introduction of the PubSub concepts,
• a definition of the PubSub configuration parameters,
• mapping of PubSub concepts and configuration parameters to messages and transport protocols,
• and a PubSub configuration model.
This second edition cancels and replaces the first edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Addition of a “Quantity Model” which can be referenced from EngineeringUnit Properties. The model defines quantities and assigned units. In addition it provides alternative units and the conversion to them.
b) Addion of rules for ValuePrecision Property:
• can also be used for other subtypes like Duration and Decimal.
• rules have been added when ValuePrecision has negative values.
- Standard320 pagesEnglish languagee-Library read for1 day
IEC 62541-17:2025 provides a definition of AliasNames functionality. AliasNames provide a manner of configuring and exposing an alternate well-defined name for any Node in the system. This is analogous to the way domain names are used as an alias to IP addresses in IP networks. Like a DNS Server, an OPC UA Server that supports AliasNames provides a lookup Method that will translate an AliasName to a NodeId of the related Node on a Server. An aggregating Server can collect these AliasNames from multiple Servers and provide a lookup Method to allow Client applications to discover NodeIds on a system wide basis. An aggregating Server could also define AliasNames for Nodes in other Servers that do not support AliasNames. A GDS can be constructed that would automatically aggregate all AliasNames that are defined on any Server that has registered with the GDS. In this case, the GDS also provides the lookup mechanism for Clients at a well-known endpoint and address.
- Standard28 pagesEnglish languagee-Library read for1 day
IEC 62541-3: 2025 describes the OPC Unified Architecture (OPC UA) AddressSpace and its Objects. This specification is the OPC UA meta model on which OPC UA information models are based. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of the concept and modelling elements for Interfaces and AddIns;
b) addition of Currency;
c) addition of Method Meta Data to define additional attributes for Method Arguments;
d) addition of ApplyRestrictionToBrowse bit to AccessRestrictionType;
e) addition of a Non-Volatile Storage bit to AccessLevelExType;
f) addition of a Constant bit and ConfigurationConstant bit to AccessLevelExType;
g) the View NodeClass has been changed to define the EventNotifier as an EventNotifierType in the same way the Object NodeClass defines it;
h) correctition of HasNotifier, HasEventSource, and Organizes, to include ObjectType as valid source node;
i) NamingRules have become deprecated;
j) addition of AssociatedWith ReferenceType.
- Standard143 pagesEnglish languagee-Library read for1 day
2022-01-05: This prAA includes common mods to EN IEC 62841-2-23 (PR=75431)
DOW=DOR+48 months is applied to all parts in EN IEC 62841 series
- Amendment9 pagesEnglish languagee-Library read for1 day
This document specifies requirements and provides guidance for the preparation for axial force compression testing of additively manufactured (AM) metallic lattice specimens for validation purposes.
- Standard13 pagesEnglish languagee-Library read for1 day
The document offers guidance on the selection of an appropriate method(s) to measure the flow properties of powders for powder feedstock based additive manufacturing processes. This document offers several definitions and parameters that affect powder flowability, in addition to several references for additional definitions and parameters.
It is intended that the guidance provided in this document not only applies to the virgin condition of the powder but also the used powder as a result of any number of successive builds. It is well known that the physical behaviour of the powder is also affected by the manufacturing process itself during the recovery and sieving cycles of the powder during the production processes. This condition of the powder going back into the system can be called out and monitored from successive builds to detect any drift of the powder properties.
This document applies to:
— the conditions that have an influence on flow properties, and
— the necessary information in a test report.
This document is aimed for test equipment manufacturers, material suppliers, additive machine manufacturers, and additive manufacturing machine users.
- Technical report15 pagesEnglish languagee-Library read for1 day
This document specifies the execution, validation, verification and documentation of a numerical welding simulation within the field of computational welding mechanics (CWM) and performed with a scientific computational tool (SCT).
This document is applicable to the thermal and mechanical finite element analysis (FEA) of arc, laser and electron beam welding processes for the purpose of calculating the effects of welding processes, and in particular, residual stresses and distortion, in support of structural integrity assessment.
- Standard56 pagesEnglish languagee-Library read for1 day
This document specifies the classification of imperfections possibly generated during an additive manufacturing process by PBF-LB (laser beam powder bed fusion) or PBF-EB (electron beam powder bed fusion) for metallic parts.
This document also indicates the most probable causes of the formation of imperfections and includes illustrations.
This can be extended to other additive manufacturing process categories, nevertheless, the indication of probable causes is process specific.
Acceptance criteria and dimensional description or scale for imperfections are not included in this document.
- Standard50 pagesEnglish languagee-Library read for1 day
This document applies to hand-held and walk-behind lawn trimmers and lawn edge trimmers, used by a standing operator for cutting grass, weeds or similar soft vegetation, and grass trimmers, brush cutters and brush saws used by a standing operator for cutting grass, weeds, brush, bushes, saplings and similar vegetation.
- Amendment12 pagesEnglish languagee-Library read for1 day
This document specifies the characterization of ceramic slurry for use as feedstock in vat photopolymerization additive manufacturing (AM) processes. The characterization includes the composition and properties of the slurry, such as solids content, dynamic viscosity, particle size distribution, chemical composition, and solid dispersion stability. This document also provides available methods on sampling and preparing slurry samples for testing.
This document does not deal with safety aspects.
- Standard17 pagesEnglish languagee-Library read for1 day
1.1 This document is intended to be used to assign part classifications across the aviation industries that use AM to produce parts.
1.2 This document is applicable to all AM technologies defined in ISO/ASTM 52900 used in aviation.
1.3 This document is intended to be used to establish a metric for AM parts in downstream documents.
1.4 This document is not intended to establish criteria for any downstream processes, but rather to establish a metric that these processes can use.
1.5 The part classification metric could be utilized by the engineering, procurement, non-destructive inspection, testing, qualification, or certification processes used for AM aviation parts.
1.6 The classification scheme in this document establishes a consistent methodology to define and communicate the consequence of failure associated with AM aviation parts.
1.7 This document is not intended to supersede the requirements and definitions of the applicable regulations or policies, including but not limited to the ones listed in Annex A1.
1.8 Tables A.1.1-A.1.3 align the existing regulations and guidance with the four part classes established herein. However, this alignment should not be construed as an alignment of the existing regulations to each other.
1.9 The material or process, or both, in general does not affect the consequence of failure of a part, therefore the classification scheme defined in this document may be used outside AM.
1.10 The user of this document should not assume regulators’ endorsement of this document as accepted mean of compliance.
1.11 This document does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this document to establish appropriate safety, health, and environmental documents and determine the applicability of regulatory limitations prior to use.
1.12 This document was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.
- Standard19 pagesEnglish languagee-Library read for1 day
This document specifies minimum content to be reported in material data sheets to justify the published material property values. This document does neither aim to define compulsory test quantities nor to define any basis for qualification purposes. Individual additions and extensions are permissible. This document is intended for use by organisations throughout the additive manufacturing supply-chain, e.g., manufacturers of PBF-LB/M or PBF-EB/M machines or comparable metal-powder-bed equipment, powder suppliers, service providers and users of the additively manufactured components.
- Standard22 pagesEnglish languagee-Library read for1 day
IEC 61512-1:2026 applies to systems, specifications, and their use for implementing batch and related procedure-oriented manufacturing controls in the process industries. This document establishes a reference model framework for procedure-oriented control, defines terms to help explain the model relationships and usage, and describes general criteria for evaluating conformance. This follows the principle of separation between recipe procedural elements and equipment procedural elements enabling operations to define recipes without the need of changes in equipment procedures. This second edition cancels and replaces the first edition published in 1997. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) Models and text are modified to provide more detail and clarity. Key clarifications are: 1) Two types of equipment modules are defined: generic and recipe-aware. All recipe-aware equipment modules contain procedural control and can be used as phases in the recipe. 2) Execution of all procedural control contained directly in units is part of the Unit Supervision activity. 3) The relationships between types of recipes, recipe components, and equipment control are more fully described and illustrated. 4) Entity relationship diagrams have been replaced with more intuitive UML instance diagrams, except for the equipment entity model. 5) The transition diagram for the procedural states example has been updated with a more intuitive and complete UML state diagram. 6) References to other standards in the series and to IEC 62264 are included to provide direction for further clarification of selected topics. 7) Activity names are capitalised to help prevent confusion with similar terms, such as their underlying functions. b) Previous Clauses 4 through 6 (now Clauses 4 through 8) were rearranged to provide a clearer top-down organisation of the document. Key changes are: 1) Removing the lower levels of the physical (role-based equipment) model (see 4.4.2) to eliminate redundancy because their groupings are defined by the associated functionality in the equipment entity model and are not meaningful for batch control without those associations. 2) Describing equipment control and the equipment entity model immediately after the physical (role-based equipment) model and describing each level as completely as possible without excessive use of forward references (see 4.4.3). 3) Combining the descriptions of basic, procedural, and coordination control with their usage in each type of equipment entity, providing a single consolidated discussion of each type of control (see Clause 5) 4) Additional considerations to support application of the models have been grouped in Clause 7 to clarify their supporting relationship to the core models. c) Clause 9 was added to define completeness, compliance, and conformance in relation to this document. d) Annex B was added to provide a more expansive procedural state reference model. The model found in Clause 7 can be considered a collapsed version of this more general model. e) Annex C was added to clarify a number of points concerning the models, their application, and the new Clause 9 on conformance and compliance. f) Annex E was added to more fully describe the changes in this update to IEC 61512-1:1997.
- Draft144 pagesEnglish languagee-Library read for1 day
This document specifies guidelines for periodic inspections of gas equipment for welding, cutting and allied processes placed downstream of the gas cylinder’s valve as shown in Figure 1 or, in the case of centralized distribution, downstream from the tapping point, since commissioning.
NOTE In some cases, gas cylinders can be replaced by cylinder bundles. Acetylene cylinder bundle systems upstream of the tapping point are excluded.
This document applies to gas welding equipment intended for professional use which utilizes compressed gases up to 300 bar (30 MPa), acetylene, liquefied petroleum gas (LPG), methylacetylene-propadiene mixtures (MPS) and carbon dioxide (CO2) and related mixtures.
This document does not apply to automatic applications of gas welding, cutting and allied processes.
- Standard16 pagesEnglish languagee-Library read for1 day
This document defines two performance levels for welded joints, namely Basic Demand and Critical Demand, for longitudinal tensile strength of weld metals, impact toughness of weld metals and heat affected zones (HAZ) to suit the level of seismic performance specifications required for welded steel structures. This document supplements the provisions of the standards or codes for welding procedure qualification in the application of new steel materials, welding consumables, or complex joints, for welds that require the performance of Basic or Critical Demands as specified by the engineer in the contract.
- Standard30 pagesEnglish languagesale 15% off
- Amendment5 pagesEnglish languagee-Library read for1 day
This document supplements or modifies the corresponding clauses in IEC 62841-1, so as to convert it into the IEC Standard: Particular requirements for hand-held strapping tools. Where a particular subclause of IEC 62841-1 is not mentioned in this document, that subclause applies as far as reasonable. Where this document states "addition", "modification" or "replacement", the relevant text in IEC 62841-1 is to be adapted accordingly. This document applies to hand-held strapping tools.
- Standard18 pagesEnglish languagee-Library read for1 day
This document describes the basic characteristics of fluoroethylene vinyl ether copolymer (FEVE) type fluoropolymer topcoats and their coating systems. Information on the weathering performance of the fluoropolymer topcoats and associated coating systems for over 30 years is also provided.[1]],[[4]]-[[12] This document covers: weathering data of FT (FEVE fluoropolymer topcoat); chemical analysis of outdoor exposed coated panels focusing on the paint surface and their cross-sections. This document does not include FEVE type waterborne fluoropolymer topcoats and their coating systems.
- Technical report17 pagesEnglish languagesale 15% off
IEC 62541-2:2026 describes the OPC Unified Architecture (OPC UA) security model. It describes the security threats of the physical, hardware, and software environments in which OPC UA is expected to run. It describes how OPC UA relies upon other standards for security. It provides definition of common security terms that are used in this and other parts of the IEC 62541 series. It gives an overview and concept of the security features that are specified in other parts of the series. It references services, mappings, and Profiles that are specified normatively in other parts of the 62541 series. It provides suggestions or best practice guidelines on implementing security. Any seeming ambiguity between this document and one of the other normative parts does not remove or reduce the requirement specified in the other normative part. There are many different aspects of security that are addressed when developing applications. However, since OPC UA specifies a communication protocol, the focus is on securing the data exchanged between applications. This does not mean that an application developer can ignore the other aspects of security like protecting persistent data against tampering. It is important that the developers look into all aspects of security and decide how they can be addressed in the application. Common security features for industrial Controls are defined in IEC 62443-4-2 and OPC UA defined a relationship to them in Annex A. This document is directed to readers who will develop OPC UA applications. It is also for end Users that wish to understand the various security features and functionality provided by OPC UA. It also offers some recommendations that can be applied when deploying systems. These recommendations are generic in nature since the details would depend on the actual implementation of the OPC UA applications and the choices made for the site security. This edition cancels and replaces the third edition of IEC TR 62541-2, published in 2020.This edition constitutes a technical revision.
- Draft44 pagesEnglish languagee-Library read for1 day
IEC 60245-6:2026 defines the particular requirements for rubber insulated arc welding electrode cables of rated voltages up to and including 450/750 V which apply in addition to the general requirements specified in IEC 60245-1, which apply to all cables.
The tests for cables specified in the IEC 60245 series are described in IEC 63294.
IEC 60245-6:2026 includes the following significant technical changes with respect to the previous edition:
a) reference to IEC 60245-2 for the tests has been deleted and replaced by IEC 63294
b) reference to lift cable according to IEC 60254-5 has been deleted
c) normative references have been updated
This document is to be used in conjunction with IEC 60245-1.
- Standard8 pagesEnglish languagesale 15% off
This document specifies requirements for high chromium white cast iron grit, as supplied for blast-cleaning processes. It specifies ranges of particle sizes, together with corresponding grade designations. Values are specified for hardness, density, defect/structural requirements, metallographic structure and chemical composition.
The requirements specified in this document apply to abrasives supplied in the new condition only. They do not apply to abrasives either during or after use.
High chromium white cast iron grits are used in both static and site blasting equipment. They are most often selected where there is a possibility for the recovery and re-use of the abrasive.
NOTE 1 Although this document has been developed for preparation of steelwork, these materials are predominantly used for non-ferrous substrates. The properties specified will generally be appropriate for use when preparing other material surfaces, or components, using blast-cleaning techniques, and can be used for applications where no subsequent coating is applied.
NOTE 2 Whenever dissimilar metals are used together, galvanic corrosion can occur.
- Draft8 pagesEnglish languagee-Library read for1 day