Skip to content

Create Automation Controller#

For a new controller to be available to use, it is necessary to create a new Automation Controller, within the automation environment.

By being a versioned entity, the information created will persist while present and used in the system; it is not possible to change it, unless a new version is created.

This section explains how to create a completely new Automation Controller.

Similar to what happens with the other entities of the system, the creation is done using a wizard.

Sequence of Steps#

There are several ways to create a new versioned object. Depending on the level, follow these steps to get started:

  • Entity - In the landing page of this entity type in the Business Data menu or in the details page of an existing entity of the same type, select New on the top ribbon. For more information see Creating Entity Objects.
  • Revision - If you want to create a new revision, go to the New dropdown button on the top ribbon and select Revision. For more information, see Revisions.
  • Version - If you want to create a version associated to an existing revision, go to the New dropdown button on the top ribbon and select Version. For more information, see Versions.

Change Set#

On the first page, it is required that the Change Set field is defined (or bypassed if such setting is already defined in the Entities' Administration).

Wizard1

General Data#

The main configuration settings for the Automation Controller are edited in this panel:

  • Name

  • Revision Name

    Info

    If you are creating a new version, the revision that was selected when you started the process will be the revision to which this version will be associated. If you are creating a new entity or revision (with a new version associated to it), provide a name for the revision or it will be automatically generated for you. For more information on revision naming, see Revision Naming.

  • Description

  • Type
  • Scope:
    • Connect IoT - allowing usage within the realm of the Automation Controller and Connect IoT.
    • Enterprise Integration - allowing the execution of workflows in response to events of the same Scope that are posted by Integration Entries.
    • Factory Automation - allowing the creation and execution of automation jobs to be managed in the Monitoring section of the Automation panel.
  • If the Scope is Connect IoT, select the version of the package to be used and the Entity Type that will be used as a context for this implementation.
  • If the Scope is Enterprise Integration, select the timeout value for the connection to the devices.
  • If the Scope is Factory Automation, select the timeout value for the connection to the devices.
  • Link Connector:
    • Normal - default simple connector.
    • Smooth - connector interpolated as a bezier curve (default).
    • Rounded - connector with rounded edges.
    • Jumpover - connector with bridges over link intersections.
  • Link Router:
    • Normal - default simple router (default).
    • Orthogonal - basic orthogonal router.
    • Manhattan - smart orthogonal router.
    • Metro - smart octolinear router.
  • The system configuration value for link connector/router is automatically loaded (if it has any value). If these values are changed, the page should be closed and opened again, so that the workflow could be redefined.

Wizard2

Driver Definitions#

On the third page, one or more Driver Definitions should be entered. Once the sign is selected, a new line will be added to the grid and the property data should be filled in.

  • If the Scope is Connect IoT, select from the available Automation Driver Definitions. The following attributes should also be added:
    • Name - a unique name should be entered; this name corresponds to the driver's identification in the workflow configuration pages, so it should be an easy-to-remember name in order to easily identify it.
    • Driver Definition - select one of the created Drivers Definitions.
    • Color - A color to easily identify the driver in the workflow configurations' pages.

Wizard3

  • If the Scope is Enterprise Integration, select from the available IoT Driver Definitions.

create_automation_controller

  • If the Scope is Factory Automation, select from the available IoT Driver Definitions.
    • Select an Event Filter to select which events must be parsed and handled.

Wizard3iot

Tasks and Converters#

On the fourth page, one or more Package of Tasks can be selected.

This will allow the selection (and filter out) the amount of tasks that will become available during the workflow design phase.

  • At least Core Tasks package must be selected.
  • During Edit step, more packages can be added, but the ones selected during this phase cannot be removed.

The tasks loaded by the Automation Controller are set in metadata through a ControllerEngineFilter structure, making the packages and tasks visible and/or selected and mandatory according to the loaded information. These filters can indicate mandatory and or dependency status and there are several rules that dictate the proper functioning:

  • If a package matches the mandatory filters, it will be selected in the package list and cannot be unselected. All others will be unselected;
  • If a tasks package is listed with a dependency and doesn't match the filter, it should appear as disabled in the list of packages available for selection. Specific tasks follow the same rules, meaning that the system can have a configured package with some tasks that only work along with specific drivers and scopes;
  • The GUI sorts the available package in the list by the following order:
    • Mandatory (and selected)
    • Available for selection
    • Disabled
  • Depending on the scope, one or more Automation Tasks Libraries will be displayed and available for selection (or mandatory when defined) in this section.
  • If the Scope is Connect IoT, only the Core tasks package will be automatically selected and cannot be unselected.
  • If the Scope is Enterprise Integration the same packages as Factory Automation are available.
  • If the Scope is Factory Automation, along with the Core tasks package, the Factory Automation tasks package will be automatically selected and cannot be unselected.

Select the Create button to complete the operation and create the Automation Controller. The workflow designer will be shown and two task blocks will be automatically placed on the workflow. Depending on the scope, they will be:

  • Connect IoT scope:
    • On Equipment Setup
    • Equipment Setup Result
  • Enterprise Integration scope:
    • On Job Start
    • Jot End
  • Factory Automation scope:
    • On Job Start
    • Job End

image-20191106181234945

The status of the Automation Controller will now be Created.

Entity