PA-DIM 1.01.00 Specifications Ballot  – Member Comments Requested
Notice and Call for Disclosure of Conflicting IPR 
Deadline: August 14, 2023 
FieldComm Group distributed a PA-DIM Specifications ballot to all voting members earlier today. While only your company's voting contact can submit a vote on this ballot, ALL FieldComm Group members are welcome to review and submit their comments. Please see the ballot summary and instructions on how to submit comments below.
The Process Automation Device Information Model is a specification that allows for protocol agnostic communication of common process automation instrument parameters, including semantic IDs as defined by IEC 61987, using OPC UA information modeling techniques. Eliminating automation protocol dependencies simplifies the integration of IT and OT systems. Including semantic device information enables unambiguous machine-to-machine (M2M) communication. Fieldbus-specific implementations are converted into the address space of the PA-DIM Information Model. 
Products using PA-DIM can easily support the NAMUR Open Architecture (NOA) use cases including automated as built, unique identification, device dimensioning, multivariable possibility check, read multivariable process values, device life cycle backup, health monitoring, and diagnosis. 
PA-DIM is a jointly owned Technical Specification. Each owner executes independent audit and approval processes, and  all comments are resolved prior to the new edition. 
PA-DIM 1.01.00 contains the following changes since 1.00.03:
  • New content for Process Analytical Technology devices
    The document is extended with data types, object types (including interface types) and variable types for PAT (Process Analytical Technology) devices. This regards ProcessAnalyserType and its subtypes, AnalyticalSignalType and its subtypes, PatMeasurementVariableType and ChemicalSubstanceDataType. 
  • New content for control purposes
    The document is extended with new discrete control signal types and discrete control variable types. This regards TwoStateDiscreteControlSignalType, MultiStateDiscreteControlSignalType, TwoStateDiscreteControlVariableType and MultiStateDiscreteControlVariableType.
  • Extended object types 
    Some object types are extended with additional components and properties. New components and properties are PADIMType.DefaultInstanceBrowseName, PADIMType.DeviceRevision and TemperatureMeasurementVariableType.SensorClass.
  • Extensions for calibration data, device condition data and signal condition data 
    Some object types instance declarations for calibration data, device condition data and signal condition data. This regards instance declarations of DeviceConditionSet, SignalConditionSet and <SignalCalibrationIdentifier> in various object types, and the new object types CalibrationPointSetType, CalibrationPointType and GeneralDeviceConditionSetType including their interfaces. 
  • Descriptions for all International Registration Data Identifier (IRDI) objects 
    For all IRDI objects in the IRDI nodeset description properties are added. These properties contain hyperlinks to the corresponding CDD entries. 
In addition, per our standard practice, editorial improvements, clarifications and corrections were made as part of the general review of the specifications.
In addition, this announcement also serves as the Official Notice and Call for Disclosure of “any Private Intellectual Property Rights, existing under the law of any nation, owned by either a member or non-member that would conflict, legally bar or adversely affect application or implementation of the proposed Specification in any commercial products.”

To report the existence of any IPR that may conflict with the proposed specification, please go to our Support Portal and submit a ticket (choose "IPR Notification" from the drop down menu) within a 90-day period.
While only your company's voting contact can submit a vote on this ballot, ALL FieldComm Group members are welcome to review and submit their comments. To submit your comments, please follow these simple steps:
  1. Review the proposed specifications. Download the specifications from:

    You will need to create an account on FieldComm Group Workspace if you don't have one, to access the specifications.
  2. Submit comments:
    While the Primary Voter is responsible for submitting an official ballot, anyone in your company can submit comments for the proposed technical specifications:

    Once you are on the page, please click on the arrow next to the DOWNLOAD button and choose ADD A COMMENT.

  3. Submit your comments by August 14, 2023!

Have questions?
Please contact us:
Review and Submit Comments