No Code Integration Types
- 28 Apr 2025
- 4 読む分
- 印刷する
- 闇光
No Code Integration Types
- 更新日 28 Apr 2025
- 4 読む分
- 印刷する
- 闇光
The content is currently unavailable in Ja - 日本語. You are viewing the default English version.
記事の要約
この要約は役に立ちましたか?
ご意見ありがとうございます
| Name | Description | Use Case | Supported Data Types | Tempo Release Version |
|---|---|---|---|---|
| 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. This integration allows reading and writing values to OPC UA tags. | 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. | Boolean, SByte, Byte, Int16, UInt16, Int32, UInt32, Int64, UInt64, Float, Double, String, DateTime (Read and Write) | 6.5 |
| 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. | A user needs to read a value from a piece of field equipment connected to an Ignition SCADA during a procedure step. | Boolean, Byte, Short, Integer, Long, Float, Double, String, DateTime (Read only) | 6.5 |
| Aveva (OSIsoft) 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. | A user needs to read a value from a piece of field equipment connected to a PI System during a procedure step. | Digital, Float16, Float32, Float64, Int16, Int32, String | 6.5 |
| 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. Finally, in Tempo 7.5, users can add linked external content from Veeva to be opened up during execution, allower authors to ensure their operators are opening the latest effective documents in Veeva. | (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. (4) A user needs to allow for operators to open linked Veeva content (such as SOPs) during execution. | N/A | 6.5 |
| Blue Mountain RAM | The purpose of this integration is to allow syncing of calibration data between Blue Mountain RAM Assets and Tempo Equipment Instances. | A user wants to keep calibration events in Blue Mountain RAM in sync on Tempo Equipment Instances. | N/A | 7.5 |
| Custom App | The purpose of this integration is to provide the ability to create an API Key and Secret for use with the Tempo Public API. This also provides a user to be referenced from with other integration types such as the DCS to Tempo Batch integration (for audit purposes). | A user needs to integrate and send data to Tempo via the Public API and needs authentication credentials. | N/A | 6.5 |
| QMS | The purpose of this integration is to provide the ability for the end user to send Tempo Exceptions to a Generic Quality Management System(QMS) via the Tempo Event Queue. | A user needs to generate a deviation in their QMS from an exception generated within Tempo in order to follow their CAPA process. | N/A | 7.0 |
| DCS to Tempo Batch | The purpose of this integration is to provide the ability to create a Tempo Batch Run from a third party system such as a Distributed Control System. | A user needs to create a batch run in MES directed from their automation system in order to assist with the workflow. | N/A | 7.0 |
| Ganymede (Deprecated) | Ganymede is an equipment integration platform that allows for a robust integration of on prem equipment to Tempo for Weigh and Dispense, Output, and Consumption Operations. | A user wants to integrate their on prem scales to Tempo to support Weigh and Dispense, Output, and Consumption Operations. | N/A | 6.5 |
| TetraScience (Deprecated) | 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. | N/A | 6.5 |