Login
      目次 x
      Understanding Process Actions
      • 07 Feb 2024
      • 44 読む分
      • 印刷する
      • 闇
        光
      目次

      Understanding Process Actions

      • 更新日 07 Feb 2024
      • 44 読む分
      • 印刷する
      • 闇
        光
      The content is currently unavailable in Ja - 日本語. You are viewing the default English version.
      記事の要約

      Who can use this feature?
        🌐 ✔️ MES (v7.X.X) ✔️ LES (v7.X.X)
        💻 Web app
        👤 Content Creator, System Admin, and procedure template co-author users


      VERSION NOTE:
      Process actions (also called inputs and actions) can be added to procedure templates in all supported versions of Tempo MES, AWI, and LES. This article covers adding process actions to procedure templates in Tempo v7.0.X and subsequent versions.
      * For information about adding inputs to a procedure template in Tempo v6.5.X, review the Understanding Inputs article.
      * For information about adding actions to a procedure template in Tempo v6.5.X, review the Understanding Actions article.

      The GIFs included to demonstrate some process actions during iOS execution were recorded in Tempo v6.5; some terminology or small user interface updates may have occurred in subsequent releases.

      Overview

      Procedure authors can associate one or more process actions with each step. (For an overview of steps, review the Creating and Managing Steps article.)

      This article provides detail regarding the Inputs, Materials, Equipment, Samples, Integrations, and Other process actions available in the process actions section of the step builder. Click the name of any process action type to jump to that section of the article.

      PREREQUISITE:

      Prior to completing the steps in any of the sections below, create or open the relevant draft procedure template in the Tempo web app.

      NOTES:
      • To edit a procedure template, it must be in the Draft stage.
      • Only the user who created a procedure template and any users assigned as a procedure co-author can edit a procedure template.

      Inputs

      There are eight types of inputs that a procedure author can add to a procedure template. Click the name of any input type to jump to that section of the article.

      • Value: Prompts the operator to record a specific text, spoken, or numerical value. This input can also reference parameter values and values pulled in from other steps.
      • Measure: Prompts the operator to record a specific measure. This input can also reference parameter measures and measures pulled in from other steps.
      • Checkbox: Prompts the operator to choose between two opposing values using a toggle, typically to indicate the completion (or non-completion) of an activity or requirement.
      • Dropdown: Prompts the operator to select one option from a dropdown list.
      • Photo: Prompts the operator to take a photo.
      • Date/Time Capture: Prompts the operator to record date/time information.
      • Table: Prompts the operator to complete information within a table.
      • Formulas: Calculates and displays the result of the formula to the operator.

      Value

      Procedure authoring in Tempo includes six types of value inputs:

      • Short Form Text: Prompts the operator to provide a short text response.
      • Long Form Text: Prompts the operator to provide a long text response.
      • Number: Prompts the operator to provide a numeric input.
      • Two Choice: Prompts the operator to select between two choices (for example, Yes and No).
      • Parameter: The app displays a value configured and enforced at the parameter level to the operator.
      • From Step Input: The app displays the value of a referred step input to the operator.
      NOTE:
      ⯈ Click here to view an example GIF of an operator completing a short form text value input on the Tempo iOS app. ⯇

      Value input field explanations

      • Prompt: Use this field to explain to the operator what value to input during execution.
        • Identifier: Each value input must have a unique identifier; this is the internal system ID for this specific value input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Value Type: Select one of the six value type inputs from the dropdown list (Short Form Text, Long Form Text, Number, Two Choice, Parameter, From Step Input); this selection determines any additional fields that may display. For additional information, refer to the table below.
      Value typeFields
      Short Form Text⋅ Condition: If the short form text entered by an operator must be a specific accepted value, select Values, then provide any accepted value(s) in the Accepted Value(s) field; otherwise, select None.
      Long Form TextN/A
      Number⋅ Review: If the number entered by an operator must be reviewed as a Critical Process Parameter (CPP), Critical Quality Attribute (CQA), or other reviewable value, select the relevant Trigger Value Exception option from the dropdown; otherwise, select No review required.

      ⋅ Condition: If the number entered by an operator must meet a certain acceptance condition, select one of the six conditions from the dropdown list (Value(s), Range, Greater Than, Greater Than or Equal, Less Than, Less Than or Equal), then define the acceptable conditions for this number using the related field(s) that display; otherwise, select None.
      For more information, review the Value & measure condition note below.

      Two Choice⋅ Option 1: Set the name for the first option.
      ⋅ Option 2: Set the name for the second option.
      ⋅ Condition: If the two choice option selected by an operator must be an accepted option, select Single, then select the name of the accepted option in the Condition Value field; otherwise, select None.
      Parameter⋅ Parameter: Select a previously-created parameter from this procedure template from the dropdown or create a new parameter by selecting Create New Parameter and completing all necessary information.
      For more information about parameters, review the Adding Parameters, Constants, and Resources to a Procedure Template article.
      From Step Process Action⋅ From Step Process Action: Select the name of the relevant previous step process action from the dropdown list.

      Value & measure condition note

      Both Number value inputs and Manual Entry measure inputs offer six potential acceptance conditions for information entered by an operator (Value(s), Range, Greater Than, Greater Than or Equal, Less Than, Less Than or Equal):

      • Accepted Value(s): If the procedure author selects Value(s), the procedure author may set the accepted value(s). The value or values in this field are accepted.
      • Range: If the procedure author selects Range, the procedure author may set the Lower Bound and Upper Bound of the acceptable range. Any value inside this range or equal the lower bound or upper bound is accepted.
      • Greater Than: If the procedure author selects Greater Than, the procedure author may set the highest value that is not an acceptable value. Any value greater than this number is accepted.
      • Greater Than or Equal To: If the procedure author selects Greater Than or Equal To, the procedure author may set the lowest acceptable value. Any value greater than or equal to this number is accepted.
      • Less Than: If the procedure author selects Less Than, the procedure author may set the lowest value that is not an acceptable value. Any value less than this number is accepted.
      • Less Than or Equal To: If the procedure author selects Less Than or Equal To, the procedure author may set the highest acceptable value. Any value less than or equal to this number is accepted.

      For manual entry measure inputs, the condition values are all automatically set in the Unit of Measure selected by the procedure author.

      Back to top

      Measure

      Procedure authoring in Tempo includes three types of measure inputs. During procedure execution, a measure input prompts an operator to record or review a measurement.

      • Manual Entry: Prompts the operator to manually enter a measurement.
      • From Step Process Action: The app displays the measure of a referred step process action to the operator.
      • Parameter: The app displays a measure configured and enforced at the parameter level to the operator.
      NOTE:
      ⯈ Click here to view an example GIF of an operator completing a manual measure input on the Tempo iOS app. ⯇

      Measure input field explanations

      • Prompt: Use this field to explain the purpose of the measure input to the operator.
        • Identifier: Each measure input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Measure Type: Select one of the three measure type inputs from the dropdown list (Manual Entry, From Step Process Action, Parameter); this selection determines any additional fields that may display. For additional information, refer to the table below.
      Measure typeFields
      Manual Entry⋅ Require Value in Scientific Format: Check this checkbox to require the measure value to be in scientific format; otherwise, leave the checkbox unchecked.
      ⋅ Unit of Measure: Select the unit of measure the operator will use.
      ⋅ Max # of Integer Places: Set the maximum number of digits acceptable before the decimal.
      ⋅ # of Decimal Places: Set the number of digits required after the decimal.
      ⋅ Review: If the value entered by an operator must be reviewed as a Critical Process Parameter (CPP), Critical Quality Attribute (CQA), or other reviewable value, select the relevant Trigger Measure Exception option from the dropdown; otherwise, select No review required.
      ⋅ Condition: If the measure entered by an operator must meet a certain acceptance condition, select one of the six conditions from the dropdown list (Value(s), Range, Greater Than, Greater Than or Equal, Less Than, Less Than or Equal), then define the acceptable conditions for this measure using the related field(s) that display; otherwise, select None.

      For more information, review the Value & measure condition note.

      From Step Process Action⋅ From Step Process Action: Select the name of the relevant previous step process action from the dropdown list.
      Parameter⋅ Parameter: Select a previously-created parameter from this procedure template from the dropdown or create a new parameter by selecting Create New Parameter and completing all necessary information.
      For more information about parameters, review the Adding Parameters, Constants, and Resources to a Procedure Template article.

      Back to top

      Checkbox

      NOTE:
      ⯈ Click here to view an example GIF of an operator completing a checkbox input on the Tempo iOS app. ⯇

      During procedure execution, a checkbox input prompts an operator to indicate the completion (or non-completion) of an activity or similar requirement. It displays to the operator as a toggle.

      Checkbox input field explanations

      • Prompt: Use this field to explain the purpose of the checkbox input to the operator.
        • Identifier: Each checkbox input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Condition: If the dropdown option selected by an operator must be an accepted option, select the relevant option (Checked, Unchecked); otherwise, select None.

      Back to top

      Dropdown

      During procedure execution, a dropdown input prompts an operator to select one option among any listed dropdown options.

      NOTE:
      ⯈ Click here to view an example GIF of an operator completing a dropdown input on the Tempo iOS app. ⯇

      Dropdown input field explanations

      • Prompt: Use this field to explain the purpose of the dropdown to the operator.
        • Identifier: Each dropdown input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Add Option: Add an additional dropdown option; repeat as needed.
      • Option X: Set the name this option.
      • Condition: If the dropdown option selected by an operator must be an accepted option, select Accepted Values, then select any accepted options in the Accepted Selections field; otherwise, select None.

      Back to top

      Photo

      During procedure execution, a photo input prompts an operator to take a photo using their device.

      Photo input field explanations

      • Prompt: Use this field to explain the purpose of the photo to the operator.

      Back to top

      Date/time capture

      Procedure authoring in Tempo includes three types of date/time capture inputs. During procedure execution, a date/time capture input prompts an operator to record the date or date and time information. Capturing date/time information using this process action also makes this information available for use in formula calculations. You can also specify conditions that the recorded information must meet in the context of other date/time captures.

      NOTE:
      ⯈ Click here to view an example GIF of an operator completing a date and time capture input on the Tempo iOS app. ⯇

      Date/time capture input field explanations

      • Prompt: Use this field to explain the purpose of the date/time capture input to the operator.
        • Identifier: Each date/time capture input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Capture Type: Select one of the three date/time capture type inputs from the dropdown list (Either, Date and Time, Date). For additional information, refer to the table below.
      Date/Time typeFields
      Either
      (operator may enter Date and Time or Date)      		⋅ Capture Condition: If the date/time or date capture entered by an operator must meet a specific condition in relation to other date/time capture input(s), select one of the three conditions from the dropdown list (Between, On or After, On or Before), then define the acceptable conditions for this input using the related field(s) that display; otherwise, select None.
      For more information, review the Date/time capture condition note below.
      Date and Time⋅ Capture Condition: If the date and time capture entered by an operator must meet a specific condition in relation to other date/time capture input(s), select one of the three conditions from the dropdown list (Between, On or After, On or Before), then define the acceptable conditions for this input using the related field(s) that display; otherwise, select None.
      For more information, review the Date/time capture condition note below.
      Date⋅ Capture Condition: If the date capture entered by an operator must meet a specific condition in relation to other date/time capture input(s), select one of the three conditions from the dropdown list (Between, On or After, On or Before), then define the acceptable conditions for this input using the related field(s) that display; otherwise, select None.
      For more information, review the Date/time capture condition note below.

      Date/time capture condition note

      All date/time capture conditions are set in terms of the relationship between this input with either one or two other date/time capture inputs. These other inputs cannot be added to the same step as the input that should have a condition. This means that setting up any other inputs on an earlier or later step in the procedure template is a prerequisite to defining a date/time capture condition.

      Back to top

      Table

      During procedure execution, the standard table input prompts an operator to enter information into a table. You can assign a specific process action for each column in the table. You can also set the minimum number of rows and determine if the operator can add or delete rows during execution.

      NOTE:
      ⯈ Click here to view an example GIF of an operator completing a standard table input on the Tempo iOS app. ⯇

      Table input field explanations

      • Prompt: All table input types require the procedure author to provide a prompt. Use this field to explain the purpose of the table to the operator.
        • Identifier: Each table input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Allow add/delete rows: If the operator should have the ability to add or delete rows from the table during execution, check this checkbox; otherwise, leave this checkbox unchecked.
      • Minimum rows: Use the + and - icons to add or remove rows from the table.
      • Add column: Add a new column to the table.
      • Column: More options: Expand the more options menu to delete or shift a column. For each column, select the input or action to add from the following list, then complete any additional information required:
        • Value
        • Measure
        • Checkbox
        • Dropdown
        • Location
        • Date/Time Capture
        • Material Scanning
        • Equipment Scanning
        • Sample Scanning
        • Read From Integration

      (Review the relevant section this article for more information about specific inputs.)

      Back to top

      Formula: Formula

      Procedure authoring in Tempo includes three types of formula inputs:

      • Formula
      • Time Formula
      • Table Formula

      During procedure execution, a formula action calculates and displays the result of the formula to the operator. You can use the formula builder to create the formula and define any conditions.

      NOTE:
      ⯈ Click here to view an example GIF of an operator completing a formula on the Tempo iOS app. ⯇

      PREREQUISITE:

      Any process actions that a Formula should reference must be added to the procedure prior to adding a Formula to a procedure. (Parameters and constants may be added directly from the formula builder, if necessary.)

      Formula field explanations

      • Prompt: Use this field to explain the purpose of the Formula process action to the operator.
        • Formula Variable Name: Each Formula process action must have a unique identifier; this is the internal system ID for this specific action. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Formula: Create the formula using a variable builder. For additional information, refer to the table below.
      Formula categoryOptions
      Operand⋅ %
      ⋅ (
      ⋅ )
      ⋅ *
      ⋅ +
      ⋅ -
      ⋅ /
      ⋅ ^
      Advanced⋅ Logarithm
      ⋅ Decadic Logarithm
      ⋅ Max
      ⋅ Mean
      ⋅ Min
      ⋅ Root
      ⋅ Round
      ⋅ Standard Deviation
      ParameterSelect a previously-created parameter from this procedure template or create a new parameter by selecting Add a Parameter and completing all necessary information.
      For more information about parameters, review the Adding Parameters, Constants, and Resources to a Procedure Template article.
      ConstantSelect a previously-created constant from this procedure template or create a new constant by selecting Add a Constant and completing all necessary information.
      For more information about parameters, review the Adding Parameters, Constants, and Resources to a Procedure Template article.
      Conditional⋅ Ternary Operation (Uses ? and : characters to separate pieces of a formula into an If ? Then : Else format.)
      EXAMPLE: {input.samplecount} > 2 **?** {input.weight} * 2 **:** {input.weight} + 2
      Process ActionSelect a process action from the procedure template.
      • Configure Formula Unit of Measure: Select the unit of measure for the formula.
      • Configure Scientific Format: Check this checkbox to require the measure value to be in scientific format; otherwise, leave the checkbox unchecked.
        • Rounded Coefficient Decimal Places: Select the number of decimal places at which the formula should round the results.
      • Configure Substitution Values: Define Substitution Values so the calculation can still be completed in case inputs are skipped.
      • Simulate: If specific values are available, allows the procedure author to simulate the result.
      • Custom Attribute: This field is only applicable to use of a LIMS integration with LES to link the result property for samples.
      • Condition: If the formula result must meet a certain acceptance condition, select one of the six conditions from the dropdown list (Value(s), Range, Greater Than, Greater Than or Equal, Less Than, Less Than or Equal), then define the acceptable conditions for this formula using the related field(s) that display; otherwise, select None.
        For more information, review the Formula condition note below.
      • Review: If the formula result must be reviewed as a Critical Process Parameter (CPP), Critical Quality Attribute (CQA), or other reviewable value, select the relevant Trigger Value Exception option from the dropdown; otherwise, select No review required.

      Formula condition note

      Formula actions offer six potential acceptance conditions for information entered by an operator (Value(s), Range, Greater Than, Greater Than or Equal, Less Than, Less Than or Equal):

      • Accepted Value(s): If the procedure author selects Value(s), the procedure author may set the accepted value(s). The value or values in this field are accepted.
      • Range: If the procedure author selects Range, the procedure author may set the Lower Bound and Upper Bound of the acceptable range. Any value inside this range or equal to the lower bound or upper bound is accepted.
      • Greater Than: If the procedure author selects Greater Than, the procedure author may set the highest value that is not an acceptable value. Any value greater than this number is accepted.
      • Greater Than or Equal To: If the procedure author selects Greater Than or Equal To, the procedure author may set the lowest acceptable value. Any value greater than or equal to this number is accepted.
      • Less Than: If the procedure author selects Less Than, the procedure author may set the lowest value that is not an acceptable value. Any value less than this number is accepted.
      • Less Than or Equal To: If the procedure author selects Less Than or Equal To, the procedure author may set the highest acceptable value. Any value less than or equal to this number is accepted.

      Back to top

      Formula: Time Formula

      Procedure authoring in Tempo includes two types of time formulas. During procedure execution, a time formula prompts an operator to make a calculation based on date or date and time information.

      • Difference: The formula calculates the difference between two dates or two times.
      • Addition: The formula adds to a date or date and time input.
      NOTE:
      ⯈ Click here to view an example GIF of an operator completing date/time capture inputs and a difference time formula on the Tempo iOS app. ⯇

      PREREQUISITE:

      Date/Time Capture input(s) must be added to the procedure to record any reference times (e.g., start time, end time) prior to adding a Time Formula to a procedure.

      Time formula action field explanations

      • Prompt: Use this field to explain the purpose of the time formula action to the operator.
      • Date/Time Capture Type: Select whether the date/time capture type is Date or Date and Time. This selection displays and determines the options listed in the Formula Type field; it also determines which time/date capture inputs are available for reference (that is, date-only captures do not display if the procedure author selects Date and Time).
      • Formula Type: Select whether the formula will calculate the difference between two inputs (Date Difference, Date and Time Difference) or calculate an addition to an input (Addition to Date, Addition to Date and Time); this selection determines any additional fields that may display. For additional information, refer to the table below.
      Formula typeFields
      Difference⋅ Reference Start Time / Reference Start Date: Select the Prompt value for the input reflecting the start time.
      ⋅ Reference End Time / Reference End Date: Select the Prompt value for the input reflecting the end time.
      ⋅ Condition: If the formula result must meet a certain acceptance condition, select one of the three conditions from the dropdown list (Range, Longer Than, Shorter Than), then define the acceptable conditions for this formula using the related field(s) that display; otherwise, select None.
      Addition⋅ Date/Time Reference / Date Reference: Select the Prompt value for the input reflecting the reference date/time or date.
      ⋅ Time to Add: Provide the amount of time to add to the reference input.
      ⋅ Condition: If the formula result must meet a certain acceptance condition, select one of the three conditions from the dropdown list (Between, On or After, On or Before), then define the acceptable conditions for this formula using the related field(s) that display; otherwise, select None.

      Time formula condition note

      Difference conditions

      Difference type time formula actions offer three potential acceptance conditions for information entered by an operator (Range, Longer Than, Shorter Than):

      • Range: If the procedure author selects Range, the procedure author may set the Minimum Duration and Maximum Duration of the acceptable range. Any value inside this range or equal to the minimum or maximum duration is accepted.
      • Longer Than: If the procedure author selects Longer Than, the procedure author may set the highest value that is not an acceptable value. Any value greater than this duration is accepted.
      • Shorter Than: If the procedure author selects Shorter Than, the procedure author may set the lowest value that is not an acceptable value. Any value less than this duration is accepted.

      Addition conditions

      Addition type time formula actions offer three potential acceptance conditions for information entered by an operator (Between, Before, After):

      • Between: If the procedure author selects Between, the procedure author may select the Prompt of the After and Before inputs that the result must be between to be acceptable.
      • On or After: If the procedure author selects On or After, the procedure author may select the Prompt of the date/time input that the result must be after to be acceptable.
      • On or Before: If the procedure author selects On or Before, the procedure author may select the Prompt of the date/time input that the result must be before to be acceptable.

      Back to top

      Formula: Table Formula

      During procedure execution, the table formula action prompts an operator to make calculations.

      Table formula action field explanations

      • Prompt: Use this field to explain the purpose of the table formula action to the operator.
      • Source Table: Select the previously-added sample table or sample plate table input.
      • Group By: If the formula result should be grouped, select a grouping option; otherwise, select None.

      Back to top

      Materials

      Material Scanning

      During procedure execution, a Material Scanning process action prompts an operator to scan a material (or automatically registers a pre-determined material resource, if Enable Auto Execution is enabled). This can be a material specified specifically by this process action or referenced from a parameter. It can also be an External Resource or a material barcode tracked by Tempo.

      Material Scanning field explanations

      • Prompt: Use this field to explain the purpose of the Material Scanning process action to the operator.
        • Identifier: Each Material Scanning process action must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Scan Type: Select one of up to three scan types from the dropdown list (External Resource, Resource Query, Resource Parameter)
        • Condition (Resource Query only): If the resource scanned by an operator must meet a certain acceptance condition, select Class/Subclass/Specific Resource, then define the acceptable conditions for this resource using the related field(s) that display; otherwise, select None.
        • Require This Material to Be Usable (Resource Query only): If checked, the material must be unexpired, in a usable status, and the lot must be approved.
        • Parameter (Resource Parameter only): Select a previously-created parameter from this procedure template from the dropdown.
          For more information about parameters, review the Adding Parameters, Constants, and Resources to a Procedure Template article.

      Back to top

      Dispense

      During procedure execution, the Dispense process action tracks the dispensing of material.

      PREREQUISITE:

      The class, subclass, and material information for this type of material must be stored within the system in order to use the Dispense process action.

      Dispense action field explanations

      • Prompt: Use this field to explain the purpose of the Dispense process action to the operator.
      • Use Bill of Materials: Select whether the material dispensed is defined using the Bill of Materials or by setting a Class/Subclass/Specific Resource.
        • Select Input Material BOM from (Yes only): Select from a previously-authored material parameter resource to specify what material will be dispensed.
        • Class/Subclass/Specific Resource (No only): Set the information about the material to dispense.
      • Autogenerate Sublot Name: When set to Yes, the output sublots will be assigned a name automatically.
        • Target Sublot Number Format (No only): Remind operators of the required sublot number format.
      • Automatically Allocate Dispensed Sublot to Batch Run?: Determines whether the material that is dispensed during this action will be allocated to the batch run for this procedure.
      • Required to Print a Label?: Set whether the operator must print a label for the dispensed material or not.

      Back to top

      Consume Material

      During procedure execution, the Consume Material process action tracks when the operator's action will deduct material from inventory.

      NOTE:
      ⯈ Click here to view an example GIF of an operator completing a Consume Material process action on the Tempo iOS app. ⯇

      PREREQUISITE:

      A Material Scanning process action must be added to the procedure prior to adding a Consume Material action.

      Consume material action field explanations

      • Prompt: Use this field to explain the purpose of the Consume Material process action to the operator.
      • Use Bill of Materials: Select whether the material to be deducted from inventory is defined using the Bill of Materials or by setting a Class/Subclass/Specific Resource.
        • Select Input Material BOM from (Yes only): Select from a previously-authored material parameter resource to specify what material will be deducted from inventory.
        • Class/Subclass/Specific Resource (No only): Set the information about the material to deduct from inventory.
      • Quantity: Set the quantity to consume.
      • Condition: Set the acceptance condition for the quantity. Select one of the three conditions from the dropdown list (Range, Greater Than or Equal, Less Than or Equal), then define the acceptable conditions for this measure using the related field(s) that display.
      • # of Decimal Places: Set the number of decimal places for the operator to provide.
      • Sublot Must Be Allocated to the Batch: Determine whether the scanned-in sublot must be allocated to the batch run containing this procedure in order to consume the material.

      Back to top

      Material Output

      During procedure execution, the Material Output process action tracks when the operator's action will create an intermediate or material output.

      NOTE:
      ⯈ Click here to view an example GIF of an operator completing a Material Output process action on the Tempo iOS app. ⯇

      PREREQUISITE:

      The class, subclass, and material information for this type of material must be stored within the system in order to use the Material Output process action.

      Material Output field explanations

      • Prompt: Use this field to explain the purpose of the Material Output process action to the operator.
      • Use Bill of Materials: Select whether the material output is defined using the Bill of Materials or by setting a Class/Subclass/Specific Resource.
        • Select Output Material BOM from (Yes only): Select from a previously-authored material parameter resource to specify what material will be output.
        • Class/Subclass/Specific Resource (No only):
            • Material Class: Select the class for the new material.
              • Material Subclass: Select the subclass for the new material.
                • Specific Resource: Specify the material. The Unit of Measure field on the material definition determines the unit of measure referenced by the Quantity Type field.
      • Quantity: Set the quantity to output.
      • Condition: Set the acceptance condition for the quantity. Select one of the three conditions from the dropdown list (Range, Greater Than or Equal, Less Than or Equal), then define the acceptable conditions for this measure using the related field(s) that display.
      • # of Decimal Places: Set the number of decimal places for the operator to provide.
      • Material Type: Select one of the two material types from the dropdown list (Intermediate, Output).
        • Product Type (Output only): Select one of the two product types from the dropdown list (Primary, Bi-product).
      • Autogenerate Sublot Name: When set to Yes, the output sublots will be assigned a name automatically.
        • Target Sublot Number Format (No only): Remind operators of the required sublot number format.
      • Set the Date of Manufacture: Select one of four options from the dropdown list (When a Particular Process Action is Completed, Manually Enter a Date, Select a Date That Has Been Set in a Sublot's Lot, This Action). Complete the additional field to define the specifics.
      • Expiration Date: Select one of three options from the dropdown list (Date of Manufacture + Material Shelf Life, Get Expiration Date from Sublot's Lot, Manually Enter a Date).
      • Required to Print a Label?: If the operator must print a label, then select Yes; otherwise, select No.

      Back to top

      Create Kit

      During procedure execution, the Create Kit Process Action prompts the operator to create a kit. For more information about kits, refer to the Creating, Editing & Deactivating a Kit article.

      NOTE:

      The current implementation does not support simultaneous multi-user execution of the Create Kit process actions. Customers are advised to only have one operator work on this process action at any given time.

      Create Kit field explanations

      • Prompt: Use this field to explain the purpose of the Create Kit process action to the operator.
      • Specify Input Materials from BOM: Select whether the input materials for the kit will be defined using the Bill of Materials or by the operator during execution.
        • Kit Name (Yes only): Set a name for the kit.
        • Specify Input Materials from BOM (Yes only): Select from a previously-authored material parameter resource to specify what material will be added to the kit.
      • Required to Print a Label?: If the operator must print a label, then select Yes; otherwise, select No.

      Back to top

      Use Kit

      During procedure execution, the Use Kit Process Action prompts the operator to use a kit. During the Use Kit process action during execution, the operator scans the kit and reviews its content. If necessary, the operator can add additional materials to the kit before the kit is used, or return or scrap those materials. For more information about kits, refer to the Kits Overview article.

      PREREQUISITE:

      The kit must be in a Usable state in order to be used.

      NOTE:

      The current implementation does not support simultaneous multi-user execution of the Use Kit process actions. Customers are advised to only have one operator work on this process action at any given time.

      Use Kit field explanations

      • Prompt: Use this field to explain the purpose of the Use Kit process action to the operator.
      • Specify Input Materials from BOM: Select from a previously-authored material parameter resource to specify what material will used as part of the kit.

      Back to top

      Create Label

      During procedure execution, a Create Label process action prompts an operator to create a label and configure how it should look when printed. The preview section displays how the label would print based on the information you define in Label Row 1 and Label Row 2.

      PREREQUISITES:
      • The create label action currently requires that the operator's iPad be set up to support printing.
      • Any attributes that a label should reference may need to be added to the procedure prior to adding the Create Label action to a procedure. (Parameters and constants may be added directly from the label builder, if necessary.)

      Create label action field explanations

      • Prompt: Use this field to explain the purpose of the Create Label process action action to the operator.
      • Resource Type: Select Dynamic.
        • Dynamic Resources: Select Process Action
          • Process Action: Select the relevant process action from the dropdown list.
      • Label Row 1 and Label Row 2: Create the first and second row of the label. Each field includes a variable builder to set the information and format for the label row. For additional information, refer to the table below.
      Label categoryOptions
      Separators⋅ Space [ ]
      ⋅ -
      ⋅ (
      ⋅ )
      Procedure Attributes⋅ Name
      ⋅ Type
      ⋅ Version
      Step Attributes⋅ Step Name
      ⋅ Step Number
      Operator⋅ Operator Initials
      Process ActionsAdd a reference to a process action from the procedure template.
      ParametersSelect a previously-created parameter from this procedure template or create a new parameter by selecting Add a Parameter and completing all necessary information.
      For more information about parameters, review the Adding Dynamic Content: Parameters & Constants article.
      ConstantsSelect a previously-created constant from this procedure template or create a new constant by selecting Add a Constant and completing all necessary information.
      For more information about constants, review the Adding Dynamic Content: Parameters & Constants article.
      NOTE:

      The Preview section at the bottom of the Create Label page provides a preview of the label based on the selected information for Label Row 1 and Label Row 2.

      Back to top

      Equipment

      Equipment Scanning

      During procedure execution, an Equipment Scanning process action prompts an operator to scan a piece of equipment (or automatically registers a pre-determined equipment instance, if Enable Auto Execution is enabled). This can be equipment specified specifically by this process action or referenced from a parameter. It can also be an External Resource or an equipment barcode tracked by Tempo.

      NOTE:
      ⯈ Click here to view an example GIF of an operator completing an Equipment Scanning process action on the Tempo iOS app. ⯇

      Equipment Scanning field explanations

      • Prompt: Use this field to explain the purpose of the Equipment Scanning process action to the operator.
        • Identifier: Each Equipment Scanning process action must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Scan Type: Select one of up to three scan types from the dropdown list (External Resource, Resource Query, Resource Parameter)
        • Enable Auto Execution (Resource Query only): Allow the system to automatically execute this action as though the equipment resource specified was scanned.
          NOTE:

          Before Enable Auto Execution can be enabled, the Condition must be set down to the Specific Resource level. Users may need to scroll up within the process action builder to access the Enable Auto Execution toggle.

        • Condition (Resource Query only): If the resource scanned by an operator must meet a certain acceptance condition, select Class/Subclass/Specific Resource, then define the acceptable conditions for this resource using the related field(s) that display; otherwise, select None.
        • Require This Equipment to Be Usable (Resource Query only): If checked, the equipment must be calibrated and in a usable status.
        • Parameter (Resource Parameter only): Select a previously-created parameter from this procedure template from the dropdown.
          For more information about parameters, review the Adding Parameters, Constants, and Resources to a Procedure Template article.

      Equipment Status

      During procedure execution, an Equipment Status process action propts the operator to update the status of a specific equipment instance (or automatically updates an equipment status, if Enable Auto Execution is enabled).

      PREREQUISITES:

      The specific equipment that will require a status change must be managed within the Tempo Manufacturing Cloud and must be added to the procedure using the Equipment Scanning process action prior to adding the Equipment Status process action to a procedure. (The relevant status and stage must also be associated with the relevant equipment class or subclass prior to adding this action.)

      Equipment Status action field explanations

      • Prompt: Use this field to explain the purpose of the Equipment Status action to the operator.
      • Enable Auto Execution: Allow the system to automatically execute this action as though the equipment resource specified was updated.
      • Use Resource from Step Process Action: Select from a previously-authored Equipment Scanning process action to specify what equipment will have its Status altered.
      • Select Status to Update: This dropdown contains a list of statuses associated with the equipment. If no results are found, there are no Statuses associated with the equipment selected. From the dropdown, select the status to be update.
      • Select Stage to Update Status to: From the Stages associated with the previously-selected Status, select the one you would like the equipment updated to. If no results are found, no Stages have been authored for the previously selected Status yet.

      Back to top

      Custom Properties: Read Property

      During procedure execution, a Read Property process action displays a custom property value from a previously-scanned equipment resource to the operator during execution. Additionally, if the property is set up for integrations, the integrated value displays. This process action can also support Review and Condition requirements; if conditions are not met, the system triggers an exception.

      PREREQUISITE:

      The specific equipment from which to read a property must be managed within the Tempo Manufacturing Cloud and must be added to the procedure using the Equipment Scanning process action prior to adding the Read Property process action to a procedure. (Additionally, the custom property must be added to the relevant equipment.)

      Read Property field explanations

      • Prompt: Use this field to explain the purpose of the Read Property process action to the operator.
      • Read Property from Resource Scanned in Step Process Action : Select from a previously-authored Equipment Scanning process action to specify what equipment to read the property from.
      • Select Property: Select a custom property to read into the procedure run.
      • Review: Select whether the property value must be reviewed as a Critical Process Parameter (CPP), Critical Quality Attribute (CQA), or other reviewable value; otherwise, select No review required.

      Back to top

      Custom Properties: Write Property

      During procedure execution, a Write Property process action writes a custom property value to a previously-scanned equipment resource during execution. Additionally, if the property is set up for integrations, this action will also trigger an integration to write to integration.

      PREREQUISITE:

      The specific equipment from which to read a property must be managed within the Tempo Manufacturing Cloud and must be added to the procedure using the Equipment Scanning process action prior to adding the Read Property process action to a procedure. (Additionally, the custom property must be added to the relevant equipment.)

      NOTE:

      The Write Property process action functions even if the Prevent Changes to Resources Referenced in Effective Procedure Templates toggle (settings Platform > Settings > Permissions) is enabled.

      Write Property field explanations

      • Prompt: Use this field to explain the purpose of the Write Property process action to the operator.
      • Write Property from Resource Scanned in Step Process Action : Select from a previously-authored Equipment Scanning process action to specify what equipment to write the property value to.
      • Select Property: Select a custom property to update as part of the the procedure run.

      Back to top

      Samples

      PACKAGE NOTE:
      All sample and array functionality require the Tempo LES package.

      Sampling: Sample Scanning

      During procedure execution, a Sample Scanning process action prompts an operator to scan a sample.

      Sampling: Sample Scanning field explanations

      • Prompt: Use this field to explain the purpose of the Sample Scanning process action to the operator.
        • Identifier: Each Sample Scanning process action must have a unique identifier; this is the internal system ID for this specific process action. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Scan Type: Select one of up to three scan types from the dropdown list (External Resource, Resource Query, Resource Parameter)
        • Condition (Resource Query only): If the resource scanned by an operator must meet a certain acceptance condition, select Class/Subclass/Specific Resource, then define the acceptable conditions for this resource using the related field(s) that display; otherwise, select None.
        • Parameter (Resource Parameter only): Select a previously-created parameter from this procedure template from the dropdown.
          For more information about parameters, review the Adding Parameters, Constants, and Resources to a Procedure Template article.

      Back to top

      Sampling: Create Sample

      During procedure execution, a Create Sample process action prompts an operator to create a new sample with no impact on system inventory.

      Create sample field explanations

      • Prompt: Use this field to explain the purpose of the Create Sample process action to the operator.
      • Sample Class: Select the sample class for the sample.
      • Sample Subclass: Select the sample subclass for the sample.
      • Required to Print a Label: If the operator must print a label, then select Yes; otherwise, select No.

      Back to top

      Sampling: Take Sample

      During procedure execution, a Take Sample process action prompts an operator to consume material in order to take a sample from an existing material sublot.

      Take sample field explanations

      • Prompt: Use this field to explain the purpose of the Take Sample process action to the operator.
      • Sample Class: Select the sample class for the sample.
      • Sample Subclass: Select the sample subclass for the sample.
      • Consume the Material from Step Process Action: Select the name of the relevant previous step process action for the material to consume when the sample is taken.
      • Quantity Type: Select Manual Entry by Operator from the dropdown list.
      • Unit of Measure: Select the unit of measure the sample will use.
      • Max # of Integer Places: Set the maximum number of digits acceptable before the decimal.
      • # of Decimal Places: Set the number of digits required after the decimal.
      • Required to Print a Label: If the operator must print a label, then select Yes; otherwise, select No.

      Back to top

      Arrays: Array Scanning

      During procedure execution, an Array Scanning process action prompts an operator to scan an array.

      Array scanning field explanations

      • Prompt: Use this field to explain the purpose of the Array Scanning process action to the operator.
        • Identifier: Each resource input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Scan Type: Select one of up to three scan types from the dropdown list (External Resource, Resource Query, Resource Parameter)
        • Condition (Resource Query only): If the resource scanned by an operator must meet a certain acceptance condition, select Class/Subclass/Specific Resource, then define the acceptable conditions for this resource using the related field(s) that display; otherwise, select None.
        • Parameter (Resource Parameter only): Select a previously-created parameter from this procedure template from the dropdown.
          For more information about parameters, review the Adding Parameters, Constants, and Resources to a Procedure Template article.

      Back to top

      Arrays: Load Plate

      During procedure execution, a load plate action prompts an operator to load a specific array.

      PREREQUISITE:

      The array resource that the load plate action should reference must be added to the procedure prior to adding a load plate action to a procedure.

      Load plate action field explanations

      Back to top

      Table: Sample Table

      During procedure execution, a Sample Table process action prompts an operator to capture a set of other process actions in a table format and does not require that an array resource has been loaded using the Load Plate process action.

      Sample Table field explanations

      • Prompt: Use this field to explain the purpose of the Sample Table process action to the operator.
        • Identifier: Each Sample Table input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Add column: Add a new column to the table.
      • Column: More options: Expand the more options menu to delete or shift a column. For each column, select the input or action to add from the following list, then complete any additional information required:
        • Value
        • Measure
        • Checkbox
        • Dropdown
        • Location
        • Date/Time Capture
        • Material Scanning
        • Equipment Scanning
        • Sample Scanning
        • Read From Integration

      (Review the relevant section this article for more information about specific inputs.)

      Back to top

      Table: Sample Plate Table

      During procedure execution, a Sample Plate Table process action prompts an operator to capture a set of other process actions in a table format. Sample Plate Table process actions are used with an array resource that has been loaded using the Load Plate action.

      PREREQUISITES:

      Add an Array resource parameter and a Load Plate process action to the procedure template.

      Sample Plate Table field explanations

      • Prompt: Use this field to explain the purpose of the Sample Plate Table process action to the operator.
        • Identifier: Each Sample Plate Table input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Load Plate Action: Select a previously-added Load Plate action from this procedure template from the dropdown.
      • Add column: Add a new column to the table.
      • Column: More options: Expand the more options menu to delete or shift a column. For each column, select the input or action to add from the following list, then complete any additional information required:
        • Value
        • Measure
        • Checkbox
        • Dropdown
        • Location
        • Date/Time Capture
        • Material Scanning
        • Equipment Scanning
        • Sample Scanning
        • Read From Integration

      (Review the relevant section this article for more information about specific inputs.)

      Back to top

      Integrations

      Event Trigger

      Event Triggers allow end users to send a custom event to a configured event queue endpoint during procedure run execution.

      PREREQUISITES:

      Event Trigger field explanations

      • Prompt: Use this field to explain the purpose of the Event Trigger to the operator.
      • Event Trigger: Search for or select the event trigger that has been configured for this use.

      Back to top

      Other (More)

      Link SOP

      During procedure execution, the Link SOP process action prompts an operator to review or complete a related, ancillary standard operating procedure (SOP).

      PREREQUISITES:
      NOTE:
      ⯈ Click here to view an example GIF of an operator completing a Link SOP process action on the Tempo iOS app. ⯇

      Link SOP field explanations

      • Prompt: Use this field to explain the purpose of the link procedure action to the operator.
      • SOP: Search for or select an effective procedure that has been attached to the draft to link using the Link SOP process action.

      Back to top

      Timer

      Procedure authoring in Tempo includes two types of Timers. During procedure execution, the Timer process action provides the operator with access to a countdown or stopwatch timer.

      Timer field explanations

      • Prompt: Use this field to explain the purpose of the timer to the operator.
      • Name: Provide a name for the timer.
      • Description (OPTIONAL): Provide a description for the timer action.
      • Timer Type: Select one of the two timer types from the dropdown list (Stopwatch, Countdown); this selection determines whether any additional fields display. For additional information, refer to the table below.
      Timer typeFields
      Stopwatch
      (counts in centiseconds)      		N/A
      Countdown
      (counts in seconds)      		⋅ Duration (Seconds): Set the number of seconds the countdown duration should be.
      ⋅ Warn At When Time Remaining Is (Sec) (OPTIONAL): Set a time remaining warning based on the number of seconds remaining in the countdown.

      Back to top

      Location

      During procedure execution, a Location process action prompts an operator to scan a location (or automatically registers a pre-determined location, if Enable Auto Execution is enabled).

      Location field explanations

      • Prompt: Use this field to explain the purpose of the Location process action to the operator.
        • Identifier: Each Location process action must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Enable Auto Execution: Allow the system to automatically execute this process action as though the location was scanned. Select a specific unit or is relationship in order to enable this field.
      • Condition: If the location must meet a specific condition, select one of the four conditions from the dropdown list (Site, Building, Area, Unit), then define the acceptable conditions for this input using the related field(s) that display; otherwise, select None.
      • Require Location to Be Usable: If checked, the location must be in a usable status.

      Back to top

      Condition

      Procedure authoring in Tempo includes two types of Condition process actions. During procedure execution, the Condition process action automatically evaluates a defined condition value as True or False, permitting complex step navigation based on either Parameters or Process Actions.

      PREREQUISITES:
      • Add the parameter or process action that the condition process action will evaluate prior to adding the condition process action.
      NOTE:

      The following process actions can be referenced as part of the Condition process action:

      • Standard Formula Process Action
      • Time Formula Process Action
      • Date/Time Capture Process Action
      • Location Process Action
      • Value Type:
        • Short text
        • Number
        • Two-choice
      • Measure Type:
        • Manual
        • Checkbox
        • Dropdown
        • Parameters

      Condition field explanations

      • Prompt: Use this field to explain the purpose of the Condition process action to the operator.
        • Identifier: Each Condition process action must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Prompt field.
      • Value Type: Select one of the two condition types from the dropdown list (Parameter, Process Action); this selection determines the author selects a Parameter or a Process Action from the procedure template in the subsequent dropdown.
      • Is/Is Not: Select whether the condition must meet (Is) or exclude (Is not) the described scenario.
      • Condition: Build the condition description. Options displayed depend upon parameter or process action type.
      • Add Multi Conditions: Select whether to add an And, Or, or Either/Or additional condition, then define the Value Type, Is/Is Not, and Condition fields for the additional condition.

      Back to top

      What's Next
      Change password!
      Changing your password will log you out immediately. Use the new password to log back in.
      Change profile
      Success!
      First name must have atleast 2 characters. Numbers and special characters are not allowed.
      Last name must have atleast 1 characters. Numbers and special characters are not allowed.
      Enter a valid email
      Enter a valid password
      Your profile has been successfully updated.
      Logout