Search
18 result(s) for Model
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.2 UANodeSetUANodeSet along with any dependencies these models have. ModelUri String The URI for the model. This URI shall be one of the entries in the NamespaceUris table. XmlSchemaUri String ... schema namespace used to serialize values of the DataTypes defined by the Model. The field is required if DataTypes are defined in the UANodeSet . The UA XML Encoding ( 5.3 ) rules
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.3 UANodeNode . This attribute is optional. If not specified the AccessRestrictions for the Model are applied. DisplayName LocalizedText [] A list of DisplayNames for the Node in different locales. There shall ... list is not specified or has zero length the default RolePermissions from the Model are used unless HasNoPermissions is TRUE. HasNoPermissions Boolean If TRUE, the UANode has no RolePermissions
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.16 UANodeSetChangesexisting Address Space. The UANodeSetChanges cannot be applied if the current version of the Model in the Address Space is higher. The RequiredModels sub-element (see Table F.1 ) specifies ... before the UANodeSetChanges file can be applied. When checking dependencies, the version of the Model in the existing Address Space must exactly match the required version. If a UANodeSetChanges file
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.14.1 Generalexpected from an OPC UA Server that is implementing the A & C Information Model . In particular this section describes specific behaviours that apply to various aspect ... Information Model
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access1 Scopedocument is part of 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 NodeClass ... Historical Access, additional standard Properties , and other information and behaviour. The complete AddressSpace Model including all NodeClass es and Attributes is specified in OPC 10000-3 . The predefined Information Model
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object SerializationSerializationScope and SerializationEntity A SerializationScope is a subset of Nodes in the Information Model which are mapped into the SerializationValue, and which shall take part in a SerializationProcess . A SerializationScope
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.3.2 FxAssetType definitionFxAssetType is considered an Asset . Additional References are defined as part of the model to show relationships between Assets , within Assets , and between Assets and FunctionalEntities and the overall AutomationComponent ... model (see 11.1 ). The FxAssetType is formally defined in Table 29 . Table 29 - FxAssetType definition Attribute Value BrowseName 3:FxAssetType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelConnectionManager can support . MonitorsLocalConnectionEndpoints, when true, describes the capability of the ConnectionManager Information Model to report the status of all the Connections created by this ConnectionManager that have a ConnectionEndpoint ... this Server. If this capability is not provided, or false, the ConnectionManager Information Model does not report the current status of Connections. NOTE In some cases, this status might include
-
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking5.6.4.4 System integrationVLAN interfaces can be created if necessary. a As no OPC UA Information Model mechanism today allows the assignment of priority information for UA Client Server messages ... configured, the System Commissioner may update the PubSubCommunicationFlowConfiguration Variable in the ConnectionManager's Information Model to adapt the Connection configurations for QoS settings and network settings such as setting destination
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringkinds of files (see Figure 6 ). It contains a Descriptor manifest file and Information Model file(s) and can contain attachment files, embedded Descriptors, or Common Services . Figure 6 - Organization ... version number for the content and a version number for the format. The Information Model files contain AML representations of UAFX Information Models . A worked-out example of the configuration
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringidentifier of type xs:ID (see ISO/IEC 29500-2:2021 clause 6.5.3.4). All Information Model attachments and embedded Descriptors in a Descriptor shall be the target of a relationship reference ... Graph with the Root AML files as the starting points and with all Information Model , attachments, and embedded Descriptors in a Descriptor referenced from the Root AML files either directly
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringexample This annex provides a worked-out example of the configuration of the Information Model of an AutomationComponent using the UAFX Information Model . This modelling process is described ... abstract way, without referencing tools or roles for the creation or editing of the model. In a concrete example, suitable or adapted engineering tools are expected to support the modelling
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles6.6.3.7 UAFX Station 2024 FacetUAFX component implementation, including an IA-station and network interface representation in the Information Model and its default configuration. Table 40 - UAFX Station 2024 Facet Group Conformance Unit / Profile Title ... Optional IA-station Facet LLDP Information Facet Base Network Model BNM Ethernet Base Info False Base Network Model BNM IETF Interface Base Info False Base Network Model BNM Entry Points
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profilesinformation required for configuring the Subscriber of an information flow in the ConnectionManager Information Model . Table 43 - UAFX SubscriberConfiguration Facet Group Conformance Unit / Profile Title Optional UAFX ConnectionManager UAFX ConnectionManager
-
OPC-10000-100 – OPC Unified Architecture - Part 100: DevicesHasProperty Variable 1:ManufacturerUri 0:String 0:PropertyType O 0:HasProperty Variable 1:Model 0:LocalizedText 0:PropertyType O 0:HasProperty Variable 1:ProductCode 0:String 0:PropertyType ... name; however, it can be a GUID or similar construct that ensures global uniqueness. Model provides the name of the product. ProductCode provides a unique combination of numbers and letters
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices4.8 SoftwareTypeHasProperty Variable 1:Manufacturer 0:LocalizedText 0:PropertyType M 0:HasProperty Variable 1:Model 0:LocalizedText 0:PropertyType M 0:HasProperty Variable 1:SoftwareRevision 0:String 0:PropertyType M Conformance ... subtype of ComponentType which means it inherits all InstanceDeclarations . The Properties Manufacturer , Model , and SoftwareRevision inherited from ComponentType are declared mandatory for SoftwareType instances
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.11 AddIn modelAddIn model To support an individual software update for the devices of a Server AddressSpace the software update model is defined using the AddIn model as it is described ... AddIn instance the fixed BrowseName "SoftwareUpdate" shall be used. This model gives any device, hardware- or software-component the opportunity to support SoftwareUpdate . With this mechanism
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.7.3 Package metadataStructure ProductCode 0:String ProductCode of the target Node on the device. False Model 0:String Model of the target Node on the device. False Table 123 - UpdateTarget definition Attribute