Triggers are the core unit of user-definable logic in the Tulip system. Triggers wait for events to fire then they check various values and compare them inside clauses to determine whether to perform actions. This document describes triggers as they relate to Apps; Refer to Machine Triggers for triggers as they relate to machines.
|The event that the trigger executes in response to. See below for possible events.
|The logical operation the trigger performs before deciding if it should execute an action in response to the event. See below for possible clauses.
|Existing data inside the Tulip system. An example value could be: "if the Tulip variable
X is greater than 3" where
X is the value. See below for possible values.
|What the trigger does. Many actions are possible in the Tulip system. See below for possible actions.
An event can result from multiple sources. Possible sources and examples below:
|User interface interaction
|a user presses a virtual button inside of a Tulip App.
|60 seconds have elapsed since the App was started.
|A machine emits a state change event, e.g. The machine has stopped.
Clauses allow users to define a series of boolean logic expressions (if/then statements) that must all evaluate to true before a given action is performed in response to a trigger event. A user can define a series of comparisons and then decide to execute a number of actions if one of the statements evaluates to true of if all of the statements evaluate to true.
Values can be any data-store that is maintained in the context of an App execution. Values can come from a number of sources, including:
There are two categories of actions that triggers can cause: transition actions and regular actions. Transitions are changes to the flow state of the App. Transitions can occur by changing the current step, canceling the current App (resetting completion data) or completing the App. In a trigger there can only be one transition per action section. Once a transition has been executed by the App, any triggers for that same event will not fire. For example, if a user defines two separate triggers for a barcode scan and they both contain a transition, only the first to execute will be run.
|Variable Widget : 02 - Record View: Compound variables can be used with triggers
|Variable widget : 07 - Testing variables and compound variables in app
|Record Placeholders : 04 - Load Table Records Trigger, and Table Record Widget
|Record Placeholders : 05 - Create and Load Table Record Trigger
|Record Placeholders : 06 - Table Data Tab
|Machine Monitoring : 06 - Machine Outputs
|Connectors : 02 - Add Function to SQL Connector
|Triggers - Print Using System Dialog Trigger
|User Table : 01 - User Table
|Connectors : 04 - Add several functions to HTTP Connector
|Machine Monitoring : 08 - App Triggers For Machines
|Triggers - Basic Triggers App
|Table Links : 03 - Linking Records via App Triggers
|Schedules and Shifts : 02 - Applying shifts in apps
|Expression Editor : 01 - Create an expression in an app trigger
|Copying Triggers : 01 - Copying and pasting triggers between buttons
|Copying Triggers : 02 - Copying and pasting triggers between image widgets
|Copying Triggers : 03 - Copying and pasting triggers between Interactive Tables
|Copying Triggers : 04 - Copying and pasting Step Triggers
|Copying Triggers : 05 - Copying and pasting App Triggers between apps
|Master Layout - Widget triggers
|Master Layout - Step and App Triggers
|Expression Editor : 02 - Running the "Expressions" app
|Ability to assign and notify multiple users for a given approval workflow of all content.
|Tulip can be used in environment where operators wear gloves. i.e. sterile or clean areas where the operator is gowned up and has gloves on
|Ability to send notifications from any content screen. Ie. email, txt message, alarms.
|All contents have to guide operators thru the process steps in an easy intuitive manner. Ie. easy navigation between process steps
|Ability to configure signature to complete a process step.
|Ability for content to guide operator thru the execution of a process flow model
|Ability to designate certain content fields to be required for data entry
|Ability to configure alerts based on criteria of the entered data
|Ability to configure job aids for assistance. e. click on "help" to get instructions or show how-to procedure
|App has to provide navigation between process steps from external input. Ie. scanner, button, switch, I/O triggers, etc.
|Ability to display the acceptable quality limits to the operator during the execution with an indication of whether the current value is inside/outside the limits.
|Ability to retrieve, examine, and view batch/lot and material attributes used in the processing step (e.g. potency), from external source.
|Ability to configure steps and states for work on orders, materials or equipment in a workflow
|Ability to configure procedural elements for work on orders, materials or equipment in a workflow
|Ability to define procedural sequences with relevant process information that can guide an operator through task execution.
|Ability to define process flows that can be executed in parallel with one another
|Ability to define process and material workflows structures that can be executed in sequence with one another
|Ability to define procedural elements in process and material workflows that can be repeated in sequence, ie configurable number of iteration of the same step both min. and max. number of iterations.
|Ability to define conditions to route process between steps in the workflow. These conditions can be based on state change in other steps or time constraints, equipment status, critical alarms, completion of other steps or defined timers.
|Disallow completion of work until all required processing steps have been performed. i.e. disallow batch close when there are incomplete processing steps.
|Ability to parameterize a process and production model definitions. Ie. create generic definition using parameterization that are substituted by specific production order information prior to release to production.
|Ability to define steps and procedural elements that are triggered by time-based events such as timers or date-time.
|Ability to configure allowed overrides for steps and procedural elements. An override can be allowed for out of spec conditions and can require additional approval using e-signature
|Ability to use process values from previous process steps in any procedural element or step workflow.
|Ability to propagate material attributes to associated materials in the material tracking hierarchies. e.g. assigning material attributes to final product from intermediates.
|Ability to define a UoM and the conversion formulas and rules between UoMs
|Disallow steps from completing until the correct material, material quantity, has been consumed or identified
|Ability to complete steps with process values that are not within the predefined limits if appropriate exception/deviation information and approval is entered
|Ability to track equipment use in production execution by material unit and work order.
|Ability to track equipment substitution during process execution.
|Ability to start processing for work orders by starting to track material (batches, lots, units, etc.). Tracking information should respect tracking hierarchy (kits, trays, wells, flasks, jigs, etc.)
|Work order have to be approved and released for production before any material can be started. Ie starting batches/lots
|Ability to view dispatching list by equipment. Ie for any element of the equipment hierarchy such as area, machine, work center, etc.
|Dispatch priority of work orders and batches/lots can be controlled using predefined configurable dispatching strategies
|Ability to track dispatching of work orders and materials to production once they are released.
|Provide managed process execution that guides the user through the production process as defined in a Production Model including the workflow, process logic, validation requirements, process parameters, material inputs and material outputs.
|Provide sequence management of process steps so that Apps can get required information for execution of a specific process step
|Track process execution of the Production Models by Apps
|Verify that all required data has been entered and collected as prescribed by the step on completion. Disallow to progress on execution path if verification fails
|Ability to re-execute process step respecting any constraints of the process step configuration in the process flow.
|Ability to re-execute process step with override of constraints of the process step configuration in the Master Recipe or material workflow. In such a case an extra e-signature can be required.
|Ability to track batch/lot and material rework based on the Master Recipe or material workflow configuration.
|Ability to track use of one source material or load-carrier used for multiple orders Eg. bulk material that is used for different products.
|Ability to track multiple dispensing of the same material continuously for different work orders or batches/lots as part of a campaign
|Ability to route and disposition materials based on sampling plans Eg. hold or future hold materials until sample testing results are available
|Ability to route and disposition materials based on results of sample testing (off-line) and/or quality testing (in-line) Eg. hold, reject, scrap, or release materials based on sample result
|Ability to automatically or manually log an exception when data is not within configured limits and tolerances. Disallow process completion until exceptions have been logged with configured e-signatures and any authorized overrides have been processed e.g. supervisor signature, scrap, etc.
|Ability to track material consumption in a process step. Material consumption may include processing, assembly, weighing, dispensing, etc.
|Ability to track all WIP materials at all material hierarchy levels including batches, lots, and materials. Ie. material tracking history will include all activities performed on materials including issue, consumption, processing, mixing, assembly, movement, transfer, etc.
|All material tracking history will include context of material hierarchy levels
|Ability to track material association to work order and production order at all levels of material tracking hierarchy
|Ability to track material consumption and use at all levels of the material tracking hierarchy.
|Provide configurable way to review exceptions
|Ability to control automated equipment state (start, stop, pause, resume, etc.) during the execution of a process step.
|Ability to assign operators to equipment or equipment group at login.
|Ability to track equipment location for mobile equipment. The equipment log will include the equipment's location history or path.
|Ability to track material inventory and its physical location.
|Ability to track materials associations using the material tracking model. Ie. track physical material in tray location, trays in batches (Cohorts).
|All materials must be identifiable through auto-id (e.g. barcodes)
|Ability to track materials handled in load-carriers.
|Ability to track loading of material to a load-carrier and its location within the load carrier. Ie. material in a well, plate, flask, tank, tote, etc.
|Ability to track unloading of material from a load-carrier
|Ability to manage and track material consumption as part of a process step. Material consumption may include processing, weighing, dispensing, etc.
|Ability to consume by pre-configured unit of measure (UoM) quantities such as weight, volume, etc.
|Ability to track of material waste and scrap as part of the production process execution.
|Ability to transfer sample material as defined in sampling plan
|Ability to track material attributes during production operations with associated capabilities to browse their history and their trending e.g. temperature, assays, etc.
|Ability to define and dispatch work orders for the different segments of the manufacturing operation.
|Ability to define work order types to indicate special processing or release procedures. Ie normal, testing, prototype, validation, rush, etc.
|All records shall be Accurate. there must be the ability to build accuracy checks into the design of the system or configure verification for manually entered data as necessary.
|All records shall be Consistent, ie capture and recorded in the same manner and in the correct sequence of the acitivities or action being recroded.
|Ability to retrieve information from external a system of record so that Apps can get the required information for execution fo a specific process step.
|When an individual executes a series of signings during a single, continuous period of controlled system access, the first signing shall be executed using all electronic signature components; subsequent signings shall be executed using at least one electronic signature component that is only executable by, and designed to be used only by, the individual.
|Ability to print configured labels for sample materials