Once installed on a device and configured by a user with "create" permissions for Stations, it can run the set of apps and versions that are determined by the "Shop Floor" Page.
The Tulip Player is meant for "production" use cases, in other words, for running the published versions of apps in order to store production data.
Here are the environments that can run the Tulip Player:
|Windows||Downloadable Application from Tulip Website||Windows 10, 64 bit processor, 4 GB RAM|
|Windows||Chrome Browser||Windows 10, 64 bit processor, 4 GB RAM|
|MacOS||Downloadable Application from Tulip Website||64 bit processor, 4 GB RAM|
|MacOS||Chrome Browser||64 bit processor, 4 GB RAM|
|iPadOS||Safari browser||Recommend testing for each class of device you intend to use.|
|iOS||Safari browser||Recommend testing for each class of device you intend to use.|
|Android||Downloadable Application from Google Play Store||Android OS 5.1 or later. Recommend testing for each class of device you intend to use.|
|Thin Clients||Downloadable Application from Tulip Website||Recommend testing for each class of device you intend to use.|
It supports the following devices on Windows with no external configuration:
It supports the following devices on Android, macOS, iOS, iPadOS:
The Tulip Player can be opened via two methods:
This method does not require authentication. The Player is automatically authenticated when it is installed on the machine, and can be opened via a URL string through other programs on the machine that the user has the appropriate credentials to access.
There are two ways to initialize the Player via human input- either via the credentials of a Tulip user or via a single-use link that is provided by a Tulip user.
Tulip User Authentication
The Tulip Player collects data from applications that were originally created by Tulip users. App data is stored in the Tulip database when the app is "completed". An app is "completed" when a Trigger with the "Complete App" transition is executed.
Once data is stored from an application, it cannot be modified or deleted. The main components of the Tulip Player:
The Tulip Player Menu can be accessed by pressing the "Menu" button within any running Tulip app.
Here's how apps run in the Player can manipulate different Models in the Tulip system.
These are the details associated with each unique install of the Player.
|Language||Choose the language for all the text in the Player Menu. Choices include English, German, Spanish, French, Italian and Japanese|
|App Version||The installed version of the Tulip Player|
|Device||The name of this install of Tulip Player when referenced within Tulip|
|Serial Number||The unique identifier for this install of the Tulip Player|
|Navigation Audio||A boolean value to turn default navigation sounds on or off|
|Device Input Language||Choose whether barcode scanners should attempt to output in English or the keyboard's default language|
|Clear All Data||When a user chooses this option, all configuration settings will be discarded and a Tulip user will need to reauthenticate the Player as if it had just been installed for the first time|
|PLAT-8741 (462)||Ability to view and display the material history record for a specific batch/lot and material|
|PLAT-8780 (105)||Support of Tulip operation on mobile devices|
|PLAT-8792 (56)||Apps can be used without external keyboard and mouse.|
|PLAT-8799 (75)||Ability to send notifications from any content screen. Ie. email, txt message, alarms.|
|PLAT-8807 (32)||All Users have to be uniquely identified|
|PLAT-8811 (255)||Ability to verify that equipment (room, suite, area, etc.) meets routine cleaning requirements and prevent process start if cleaning status requirement is not met prior to start of processing.|
|PLAT-8874 (848)||The ability to discern invalid or altered records. Ability to annotate data is changed. For GMP or critical data changes annotation can be configured as required.|
|PLAT-8883 (814)||Ability to view, display and and print accurate and complete records, including any attachments, electronic signatures and their associated audit trails.|
|PLAT-8888 (811)||All records, electronic signatures, and audit trails must be protected to ensure they are readily retrievable throughout a pre-configured retention period.|
|PLAT-8920 (802)||All records shall be Original; all originally recorded data shall be maintained.|
|PLAT-8939 (35)||Automatic logout user from system after a configurable amount of inactivity time|
|PLAT-8943 (807)||All records shall be Available and can be accessed for review, audit or inspection over the lifetime of the record (retention period).|
|PLAT-8946 (806)||All records shall be Enduring, ie. store, managed and unalterable for the full retention period.|
|PLAT-8984 (244)||Ability to view and print a version of App that define a specific Master Batch Record (MBR) or Master Device Record (MDR)|