Emerson Exchange 365

• Not Answered

Batch Input Parameter Limits

I'm working on a recipe in DeltaV Batch.  I have 5 components that will be added as a part of this recipe.  The limits, however, are not fixed values.  The limits for at least 2 of the components would need to be calculated from the values entered for the other 3 components.  If the input parameters are deferred up to an operation, is there a way to have the system calculate new limits as the values for that batch are entered?  Can the input values and limits be referenced to a control module to do the calculations?

Thanks for the help on this unusual problem.

Kent

• 5 Oct 2022 2:51 PM
• Cancel

4 Replies

• Matt Stoner

  

  • 5 Oct 2022 3:31 PM

  Recipes (Procedures, Unit Procedures and Operations) can't configure any logic so you would need to have the recipe parameters support the maximum range for the parameters and then pass this to a Phase and then you can do what you are wanting to calculate/check the values against limits and then use outputs from this phase to report values (Or just save to Unit Parameters) and then the rest of your logic could use these parameters.

  • Cancel
• Kent

  

  • 5 Oct 2022 3:42 PM

  In reply to Matt Stoner:

  Thanks! This will be slightly more complex than I originally thought but it should be doable.

  • Cancel
• Kent

  

  • 5 Oct 2022 3:55 PM

  In reply to Matt Stoner:

  I have a question on implementing this. I have created the Batch Input Parameters and the phase level where they will be used in the batch. Those parameters have been deferred up to the operation. If I create a recipe checking phase, how would I reference the existing Input Parameters in the new phase?

  • Cancel
• gamella

  

  • 13 Oct 2022 7:39 AM

  In reply to Kent:

  Operation REFERRED from a phase report parameters can be used to DEFER values into other PHASE batch input parameter inside same operation. This provides an OPERATION encapsulated method to transfer data from phase to phase.
  Eventually, OPERATION report parameters can be REFERRED into Unit Procedure report parameters and then DEFERRED into other OPERATION batch input parameter on same Unit Procedure. Same can be done at PROCEDURE level with Unit Procedure Report parameters.
  Also note that a parameter value generated into a phase running into a unit procedure can be transferred into a phase running into a different Unit Procedure (both Unit Procedures are part of same PROCEDURE).
  
  Some use cases:
  1) Phase to Phase into same OPERATION: OPERATION/PHASE_A/REPORT_PARAM =REFER=> OPERATION/X_PARAM =DEFER=> OPERATION/PHASE_B/INPUT_PARAM
  
  2) Phase to Phase into same Unit Procedure: UNIT_PROCEDURE/OPERATION_A/PHASE/REPORT_PARAM =REFER=> UNIT_PROCEDURE/OPERATION_A/X_PARAM =REFER=> UNIT_PROCEDURE/X_PARAM =DEFER=> UNIT_PROCEDURE/OPERATION_B/INPUT_PARAM =DEFER=> UNIT_PROCEDURE/OPERATION_B/PHASE/INPUT_PARAM
  
  3) Phase to Phase into different Unit Procedures: PROCEDURE/UNIT_PROCEDURE_A/OPERATION/PHASE/REPORT_PARAM =REFER=> PROCEDURE/UNIT_PROCEDURE_A/OPERATION/X_PARAM =REFER=> PROCEDURE/UNIT_PROCEDURE_A/X_PARAM =REFER=> PROCEDURE/X_PARAM =DEFER=> PROCEDURE/UNIT_PROCEDURE_B/INPUT_PARAM =DEFER=> PROCEDURE/UNIT_PROCEDURE_B/OPERATION/INPUT_PARAM =DEFER=> PROCEDURE/UNIT_PROCEDURE_B/OPERATION/PHASE/INPUT_PARAM
  
  Because parameter transfer chain can become complex, a convenient naming for parameters can be used.
  Naming convention example:
  Batch Input at any level (Procedure, Unit Procedure, Operation or Phase) : R_<name>
  Batch Report at any level (Procedure, Unit Procedure, Operation or Phase) : L_<name>
  Batch Report used to transfer data between recipe steps 8referred and then deferred): X_<name>

  • Cancel