Krunch Pipeline best practices: step order

The step order of the Analog DataStream pipeline is meant to run sequentially to ensure proper execution. Very few of the steps can be considered independent from each other.

• AttachHPDB – Attaches to the previously locked table, record, and remote record. This should always be the first step.
• RecordQuestionable – Typically the first step after AttachHPDB. This records flag.rtu_qsd, which is used in the RtuQsdAsDeviceDqSetFreshness step. Do not change the order.
• InitializeAnalogParameters – Initializes the AdditionalParameter collection used in most of the following steps. Do not change the order.
• CheckKrunchPrereqs – Exits the pipeline early if certain conditions are met. AVEVA does not recommend changing the order because it may affect performance.
• ConfigurableQualityBit – Checks quality of the raw data and performs some sanitizing on the raw KrunchData. Given that, the step should come early in the pipeline before any value conversion is performed by ConvertToRawValue.
• RawDataEnabled – Processes the raw value into the RealTime database (RTDB) table record. This step should always come early in the pipeline before any value conversion is performed by ConvertToRawValue. If you are recording the raw, unsanitized KrunchData value, move the step to before the ConfigurableQualityBit if so desired.
• ConvertToRawValue – Performs the conversion of the raw KrunchData. This step needs to come before all the following steps. AVEVA does not recommend changing the order.
• ApplySmoothing – Apply a linear filter to the raw value using a configured filter constant. AVEVA does not recommend changing the order.
• ConvertToEngUnits – Converts the raw value to engineering units and scales the AnalogValue AdditionalParameter. AVEVA does not recommend changing the order.
• CheckCutoff – Apply cutoff limits to clamp the analog value if required. AVEVA does not recommend changing the order.
• DetermineIfFreshAnalog – Updates flag.fresh based on IsQualityGood and InstrumentFailFlag AdditionalParameter. AVEVA does not recommend changing the order.
• RtuQsdAsDeviceDqSetFreshness – Updates flag.fresh based on data quality.
• AnalogProcessingDeadband – Check the polled value against the processing deadband to decide if further krunching is required. AVEVA does not recommend changing the order.
• UpdateLastPointCondition – Updates the last point condition state if using the Sub-Remote Status Indicator application. AVEVA does not recommend changing the order.
• KrunchAnalogValue –  Processes (krunches) the analog value. AVEVA does not recommend changing the order.
• UpdateRecordDisposition – Updates the record disposition if the fresh, secondpoll, last point condition flag, or isClamped flag has changed. This should always be the second-to-last step before DetachHPDB.
• DetachHPDB – Detaches from the analog table and record as well as the remote record. This should always be the last step.