1. Implementing Manufacturing and Supply Chain Materials Management
  2. About Operational Commands

About Operational Commands

Operational commands can send set points and program information to be configured on the equipment, or request for asset meter readings.

Smart Operations currently support the following standard command types:

Set Operational Parameters: Lets you send set points and any program information, such as the program file name, to the equipment before starting the operation or during the operation for better control. The parameters include one or more of the predefined operational parameters.

Note: See Create and Use Process Operational Parameters in Work Definitions in the Using Manufacturing guide for more information on creating operational parameters.

Request Meters: Lets you request an asset meter reading on demand. The meters include one or more of the predefined meters.

Note: See How You Create Meters for an Asset in the Using Maintenance guide for more information on creating asset meters.

To transmit commands to your IIoT environment or external system, you must use Message Queuing Telemetry Transport (MQTT) integration. The command data publishes to the MQTT topic using the following syntax, which contains metadata about the command and the connected equipment or asset that should receive the command: 

command/<assetNumber>/<commandTypeCode>

Here:

  • command: Required string. Default syntax on the topic to illustrate that the commands are being published.
  • assetNumber: Required string. The asset number for the equipment that should receive the command.
  • commandTypeCode: Required string. The code for the command type, as described in the Fusion application. Possible values are CA_SET_OPERATIONAL_PARAMETERS or CA_REQUEST_METERS corresponding to the standard command type.
  • data: Required string. The data that needs to be transmitted to the connected equipment or asset. Here’s a sample payload: 
    {
    "data": {
        "parameters" : {
            "NZ_PRESSURE": 100,
            "TEMP_AMB": 30
        }
    }
}

Your IIoT environment or external system requires the following to receive the commands:

  • Should be subscribed to the publicly reachable MQTT broker for the topic syntax:

    command/<assetNumber>/<commandTypeCode>.

    The MQTT broker integration should be added under Smart Operations Configurations in Work Execution.

  • Should have been configured to map the relevant equipment or asset attributes to the incoming command payload attributes specification. This includes the following:
    • Direct mapping for attributes that can be written back to or requested from the connected asset or machine:

      Parameter Codes (Number/String): Various operational parameter codes

      Meter Codes (String): Various meter codes

    • Additional optional mappings if required.

      For example, if your application configures the Temperature attribute in Fahrenheit, but one of your plants expects it in Celsius, you may need to convert the Unit of Measure (UoM) before writing back onto the connected asset or machine attributes.

Related Topics