IEC 62541-10-2015 pdf download.OPC Unified Architecture – Part 10: Programs.
This part of IEC 62541 is part of the overall OPC Unified Architecture (OPC UA) standard series and defines the information model associated with Programs. This includes the description of the NodeClasses, standard Properties, Methods and Events and associated behaviour and information for Programs. The complete address space 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.
2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
IEC TR 62541 -1 , OPC Unified Architecture – Part 1: Overview and Concepts
IEC 62541 -3:201 5, OPC Unified Architecture – Part 3: Address Space Model
IEC 62541 -4:201 5, OPC Unified Architecture – Part 4: Services
IEC 62541 -5:201 5, OPC Unified Architecture – Part 5: Information Model
IEC 62541 -7, OPC Unified Architecture – Part 7: Profiles
3 Terms, definitions and conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC TR 62541 -1 ,IEC 62541 -3, as well as the following apply.
3.1.1 function
programmatic task performed by a server or device, usually accomplished by computer code execution
3.1.2 Finite State Machine
sequence of states and valid state transitions along with the causes and effects of those state transitions that define the actions of a Program in terms of discrete stages
3.1.3 ProgramType
type definition of a Program and is a subtype of the FiniteStateMachineType
4 Concepts
4.1 General Integrated automation facilities manage their operations through the exchange of data and the coordinated invocation of system functions as illustrated in Figure 1 . Services are required to perform the data exchanges and to invoke the functions that constitute system operation. These functions may be invoked through Human Machine Interfaces, cell controllers, or other supervisory control and data acquisition type systems. OPC UA defines Methods and Programs as an interoperable way to advertise, discover, and request these functions. They provide a normalizing mechanism for the semantic description, invocation, and result reporting of these functions. Together Methods and Programs complement the other OPC UA Services and ObjectTypes to facilitate the operation of an automation environment using a client-server hierarchy.
Methods and Programs model functions typically have different scopes, behaviours, lifetimes, and complexities in OPC Servers and the underlying systems. These functions are not normally characterized by the reading or writing of data which is accomplished with the OPC UA Attribute service set. Methods represent basic functions in the Server that can be invoked by a Client. Programs, by contrast, model more complex and stateful functionality in the system. For example, a method call may be used to perform a calculation or reset a counter. A Program is used to run and control a batch process, execute a machine tool part program, or manage a domain download. Methods and their invocation mechanism are described in IEC 62541 -3 and IEC 62541 -4. This standard describes the extensions to, or specific use of, the core capabilities defined in IEC 62541 -5 as required for Programs.IEC 62541-10 pdf download.