No Code Integration Types
  • 09 Nov 2022
  • 2 Minutes to read
  • Dark
    Light

No Code Integration Types

  • Dark
    Light

Name Description Supported Data Types Use Case
OPC UA OPC is the interoperability standard for the secure and reliable exchange of data in the industrial automation space and in other industries. It is platform independent and ensures the seamless flow of information among devices from multiple vendors. The OPC Foundation is responsible for the development and maintenance of this standard. Boolean, SByte, Byte, Int16, UInt16, Int32, UInt32, Int64, UInt64, Float, Double, String, DateTime (Read and Write) A user needs to read a value from a piece of field equipment connected to a control systems OPC UA server during a procedure step.
Ignition SCADA The ‘No Code Integration’ for Ignition SCADA Provides read and write access to the Ignition Tag Library, which includes the Active Ignition Project File, as well as devices and systems connected to Ignition directly. Boolean, Byte, Short, Integer, Long, Float, Double, String, DateTime (Read only) A user needs to read a value from a piece of field equipment connected to an Ignition SCADA during a procedure step.
OSIsoft (Now AVEVA) PI The purpose of this integration is to allow any aspect of the PI System to be both read or written to from the Apprentice Suite. In addition, the option to automatically create PI Event Frames for both individual procedures and entire batch operations is configurable via a simple checkbox during authoring. Digital, Float16, Float32, Float64, Int16, Int32, String A user needs to read a value from a piece of field equipment connected to a PI System during a procedure step.
Veeva The purpose of this integration is to allow for Exceptions in the Apprentice MES platform to be sent to Veeva QMS as Deviations, which will then report Summary/CAPA data back to Apprentice as quality investigations are performed. This will allow Apprentice MES users to monitor the progress of a Veeva quality investigation and have quick access to when it is appropriate to approve the exception in Apprentice. In addition, Apprentice supports the transfer of Technique Media (images/videos) both to and from the Veeva platform, which allows them to be leveraged in procedure authoring and execution. (1) A user needs to send a MES Exception to Veeva for issue investigation prior to approving the exception in MES. (2) A user needs to leverage images or videos located in Veeva within a Apprentice procedure. (3) A user needs to send captured Technique Media in Apprentice into the Veeva Platform.
Ganymede Ganymede is an equipment integration platform that allows for a robust integration of on prem equipment to Tempo for Weigh and Dispense. A user wants to integrate their on prem scales to Tempo to support Weigh and Dispense Operations.
DeltaV A&E The purpose of this integration is to allow for connectivity to a DeltaV Alarm & Event Database (or replicated server). A user wants to ingest alarms & events from DeltaV based on dynamic trigger conditions to view directly within Tempo Exceptions.
TetraScience The purpose of this integration is to allow for robust integration of on prem equipment to Tempo. (1) A user wants to connect directly to on prem equipment at site to capture results data as part of the LES process. (2) A user wants to collect overall equipment results, detailed equipment sample results, or sample plate results.

Was this article helpful?