Readme for Data Transfer Hiway Conversion Project Link installation.

Last updated 3-04-02

 

This document contains instruction and notes related to the installation and use of the Project Link for the conversion of Hiway Gateway configuration data to the Process Manager.

History

Version 1.90.001 Date: 03-04-02

*      Fixed defects in the following Templates to modify expressions for translation of DIGALFMT, DIGALARM values. These templates did not migrate existing alarming behavior correctly for MultiFunction Controller Digital Inputs:

Version 1.90 Date: 02-20-02

*      Fixed defects in the following Templates to add expressions for translation of ZZTEXT values. These templates now detect a valid ZZTEXT parameter value and set the DC or DEVCTL PVTXTOPT parameter value to On:

*      Fixed defect in the Analog Composite - AI - HLAI Conversion - HLPIU/MC Template that resulted in the table ANLINHG being included in the generated SQL query. This resulted in numerous strategies being reported in the Data Collection with the same name.

Version 1.80 Date: 02-04-02

*      Fixed defects in the following Templates to correct expressions for translation of PVCHAR and SENSRTYP values:

Version 1.70 Date: 11-16-01

*      Fixed defect in Status Digital Input migration Templates. The TPS parameter PVNORMAL was based on the Hiway parameter STATE1, which may not be correct depending on the enumeration value for DIGALFMT. This binding has been replaced with a Transform Expression that looks at the enumeration value for the Hiway parameter DIGALFMT to determine the proper parameter value for PVNORMAL.

Version 1.60 Date: 09-09-01

*      Fixed defect in Status Digital Input migration Templates. The alarming detection was based on the Hiway parameter DIGALARM that does not exist for MC type Digital Inputs. This detection is now based on the Hiway parameter DIGALFMT

Version 1.50 Date: 08-04-01

*      Added expressions to Digital Composite, MC Flag, Digital Output, and Digit Input Templates to replace invalid characters found in the Hiway parameters STATE1, STATE2 with an underscore character and to generate an application log warning message when this occurs during the Import Data Collection task.

Version 1.40 Date: 07-27-01

*      Added bindings to Template used to migrate Hiway Digital Composite data points to Process Manager Digital Composite and Device Control strategies to set STn_OPn parameter values. These Project Link templates will support the output configuration for single or dual output migration

History

Version 1.30 Date: 05-25-01

*      Added new Templates to support migration of Hiway Digital Composite to Process Manager Device Control.

*      Added new Templates to support migration of Hiway Analog Output to Process Manager Regulatory Control AutoMan algorithm connected to an Analog Output component Strategy.

Prerequisites for using the Hiway Conversion Project Link
Importing a Project Link
Using the Hiway Conversion Project Link

Prerequisites for using the Hiway Conversion Project Link

Introduction

This Project Link is designed to connect to a Microsoft Access database that was created using the Translate EB Files Wizard located in the Tools menu of the Data Transfer application. This Project Link allows you to convert the primitive Hiway Gateway point types such as Analog Input/Output, Digital Input/Output, etc. to the Process Manager for all HG box types. When converting Hiway Gateway Regulatory controls, you will use the Data Transfer Hiway Gateway Regulatory Control Conversion Wizard, which is designed to handle the complexities involved in converting to Process Manager regulatory controls.

This Project Link will convert Hiway Gateway point configuration data to a HPM node as installed. If you wish to use this Project Link to convert to a PM or APM node, then you will have to modify the constant values and parameter bindings to conform to the specific node type.

NOTE: You are not required to have a Microsoft Access application installed on your workstation to use this Project Link. Data Transfer will automatically handle the data source connection.

When importing the Project Link into your application workspace, you will be required to specify an OLE DB connection to this EB translated Data Source. This translation must be done prior to importing the Hiway Conversion Project Link. When the Project Link has been successfully imported, you can change the Data Source connection (Microsoft Access database) to connect to another translated set of EB Files if you choose to maintain separate databases for your EB files. Read the online documentation topic Working with Project Links.

Translating Honeywell Exception Build (EB) Files

You must translate your EB files to a Microsoft Access database prior to importing this Project Link. Follow the steps below to translate your selected EB files. For more information on the translation wizard, see the topic Working with Honeywell Exception Build (EB) files

*      Start the EB file Translation Wizard by clicking the main menu item Tools - Translate EB Files.

*      Select the option Translate to Microsoft Access database and click Next

*      Specify where your EB files are located by clicking the browse button.

*      Specify the name and path to the Microsoft Access database that will be created during translation.

*      Select the Access 2000 option if you have a Microsoft Access 2000 installed version of office. You are not required to have a Microsoft Access application installed on your workstation to use this Project Link.

*      Check the EB files in the displayed list that you wish to translate to the Microsoft Access database.

*      Click the Next button to begin the translation process.

 

When you have completed the translation of your EB files, then you can begin the import of this Project Link file into your Data Transfer application workspace.

Importing a Project Link

  1. Click File - New in the main menu of the Data Transfer application.
  2. Click the Project Links tab.
  3. Click the Hiway Conversion To HPM icon to select the Project Link.
  4. Click the OK button to begin the import process.
  5. When you proceed to Step 3 of the Archive wizard, you will have to specify the Data Source connection by clicking on the Select Datasource... button. Do this now.
  6. In step 1 of the Data Source Connection window, select the type of Data Source to connect to from the drop list. In most cases this will be Microsoft Access.
  7. In step 2 of the Data Source Connection window, enter or click the browse button to specify the Data Source path to connect to. This will be the Microsoft Access database that was created during translation of your Honeywell Exception (EB) files.
  8. Click the Connect button to complete the connection.
  9. Complete Step 3 of the Archive wizard to import the Project Link.

 

Using the Hiway Conversion Project Link

After you have successfully imported this Project Link into your Data Transfer application workspace, you can begin using it to collect and import (convert) your Hiway Gateway configuration data.

Overview

Data Transfer uses a concept of Data Collection tasks to perform all import operations to TPS BuilderŽ. Data collections allow you to preview the results of any parameter data transformations that will be used to create or overwrite an existing TPS Strategy in your TPS BuilderŽ project. Data collections are based on the definition of parameter bindings that are defined in a Binding Drawing. A Binding Drawing defines the parameter bindings or relationships between a TPS Template (Analog Input, Analog Output, Digital Composite, etc.) and a connected Data Source, which in this case is the translated Microsoft Access database.

A Binding Drawing is where you graphically define these parameter bindings by drag and drop of parameters to establish connections (bindings). If the importing of a Data Source parameter value requires transformation, then you can add a Transform Window to provide the transformation expression. There are a large number of Hiway Gateway parameters that are identical in name to the Process Manager, but the enumeration values are not the same and/or they have different meaning. The transformation expressions will allow you to properly import the correct parameter values.

This Project Link contains many Templates that are used to import (convert) the various Hiway Gateway point types to the Process Manager configuration. When beginning a Data Collection task, you will be required to select from this list of Templates to determine the scope of Strategies that are converted to the Process Manager for a specific import operation. It is recommended that you begin by executing Data Collection tasks with a single Template and previewing the results of each Data Collection prior to importing to your TPS BuilderŽ project. Not all of these Templates will apply to your Hiway Gateway conversion project. There are Templates that are developed to handle conversions from specific Hiway Gateway box types and also to handle conversions to specific Process Manager IOP types such as HLAI, LLAI, LLMUX. You will have to determine what Templates apply for your conversion process.

NOTE: This Project Link as installed will convert Hiway Gateway configuration data to an HPM node type only.

Naming of Tables contained in the Translated Microsoft Access Database

The Honeywell Exception Build (EB) File translation process names the tables contained in the Microsoft Access database according to the Hiway Gateway point types. When configuring Binding Drawings to connect to the translated Microsoft Access database you will use these tables to specify where the parameter configuration data resides. The following list of tables is what you will find contained in the translated Microsoft Access database depending on the strategy types contained in your EB files used to translate:

*      ANLINHG - Analog Input

*      ANLOUTHG - Analog Output

*      ANLCMPHG - Analog Composite

*      DIGINHG - Digital Input

*      COUNTHG - Digital Counter

*      DIGCMPHG - Digital Composite

*      DIGOUTHG - Digital Output

*      FLAGHG - Flag

*      NUMERCHG - Numeric

*      PRCMODHG - Process Module

*      TIMERHG - Timer

*      REGHG - Regulatory

Collecting and Importing Hiway Gateway Configuration Data

Generate Notes
Changing the Project Link Templates to convert to a PM or APM Node Type
Advanced Naming
Recommendation for Containment of Converted Hiway Gateway Strategies
Resolving Connections
Assigning Address Data to the Converted Process Manager Strategies
Checking the converted Hiway Gateway Configuration
Forward Building to EB Files For TPS Loading
Comments

This Project Link for Hiway Migration provides a set of System Variables that are referenced in Constant expressions for all Templates that set the value of the Process Manager NTWKNUM, NODENUM, and NODETYP values with the exception of component strategies created from Digital Composite and Analog Composite templates. When these component strategies are created during the migration, the original Hiway address is transferred to the PM address variables so that the I/O Hardware Map Template can recognize and map the original Hiway Slot to the PM IOM Module to automatically update these PM based address values. Prior to executing any Data Collection tasks, you will want to access the System Variables and change the variable value to your desired address values.

When the Hiway strategies are migrated (created) in the TPS Builder project as Process Manager based types, the strategies are organized into Module strategies according to the Strategy Hiway and Box address values and the original Hiway point type. The table below displays what Module Strategy names are used during the migration process:

This example will show the names of the Module strategies that reside with the address HWYNUM=2 and BOXNUM=12

NOTE: the Module Strategy names are delimited with a dot character to form the hierarchy.

HG Point Type

Module Strategy Name

Notes

ANLINHG

HGBOX_0212.ANALOGIN_0212.strategyname

 

ANLOUTHG

HGBOX_0212.ANALOGOUT_0212.strategyname

 

DIGINHG

HGBOX_0212.DIGITALIN_0212.strategyname

 

DIGOUTHG

HGBOX_0212.DIGITALOUT_0212.strategyname

 

ANLCMPHG

HGBOX_0212.ANALOGCMP_0212.strategyname

 

DIGCMPHG

HGBOX_0212.DIGITALCMP_0212.strategyname

 

COUNTHG

HGBOX_0212.COUNTER_0212.strategyname

 

TIMERHG

HGBOX_0212.TIMER_0212.strategyname

 

NUMERCHG

HGBOX_0212.NUMERIC_0212.strategyname

 

PRCMODHG

HGBOX_0212.PROCMOD_0212.strategyname

 

FLAGHG

HGBOX_0212.FLAG_0212.strategyname

Non-Alarm Type Flags (INTVARNM > 64)

FLAGHG

HGBOX_0212.FLAG_W_ALM_0212.strategyname

Alarm Type Flags (INTVARNM < 65)

It is recommended that you begin the conversion process by working with a single Template for each Data Collection task and import (convert) operation. You will want to determine what IOM module types will be used in the Process Manager to determine what Project Link Templates are selected for converting a specific Hiway Gateway point type. The following comments are a guideline to using these Templates.

Analog Input HLAI Conversion - HLPIU/CB
Analog Input HLAI Conversion - MC
Analog Input LLAI Conversion - LLPIU
Analog Input LLMUX Conversion - LEPIU
Analog Input LLMUX Conversion - LLPIU
Analog Input - MC - With Accum to RegPV Totalizer
Analog Input - MC - With Accum to HLAI Conversion
Analog Output Standalone - HLPIU/MC Conversion
Analog Output For AutoMan - HLPIU/MC Conversion
Analog Output to RegCtl AutoMan Conversion
Digital Input - STATUS - Conversion
Digital Input - Input2 - STATUS - Conversion
Counter Conversion to AI Pulse
Counter Conversion - PI RegPV Totalizr Algorithm
Counter Conversion - ACCUM to Digital Input
Counter Conversion to DI ACCUM Using RegPV Calc
Counter Conversion To RegPV Calcultr Algorithm
Digital Output - DO - HLPIU/MC Conversion
Digital Output - DC - HLPIU/MC Conversion
Analog Composite - AI - HLAI Conversion - HLPIU/MC
Analog Composite - AO - Conversion - HLPIU/MC
Analog Composite to RegCtl AutoMan Conversion
Analog Composite - AO/AUTOMAN - Conversion
Digital Composite - DC Conversion - HLPIU/MC
Digital Composite - DC-DigInA - Conversion
Digital Composite - DC-DigInB - Conversion
Digital Composite - DC-DigOutA - Conversion
Digital Composite - DC-DigOutB - Conversion
Digital Composite - DEVCTL Conversion - HLPIU/MC
Digital Composite - DEVCTL -DigInA - Conversion
Digital Composite - DEVCTL -DigInB - Conversion
Digital Composite - DEVCTL -DigOutA - Conversion
Digital Composite - DEVCTL -DigOutB - Conversion
Flag - MC - Conversion
Numeric - MC - Conversion
Process Module - MC - Conversion
Timer - MC - Conversion

*      Analog Input HLAI Conversion - HLPIU/CB

Use this Template to convert your existing HLPIU and CB RV Analog Input strategies to a Process Manager HLAI IOP type. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and CB RV box types.

*      Analog Input HLAI Conversion - MC

Use this Template to convert your existing MC Analog Input strategies configured without accumulation to a Process Manager HLAI IOP type. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only MC box types with no analog accumulation. To convert MC Analog Input strategies that are configured for accumulation, use the Project Link Templates named Analog Input - MC - With Accum to RegPV Totalizer and Analog Input - MC - With Accum to HLAI Conversion

*      Analog Input LLAI Conversion - LLPIU

Use this Template to convert your existing LLPIU strategies to a Process Manager LLAI IOP type. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only LLPIU box types.

*      Analog Input LLMUX Conversion - LEPIU

Use this Template to convert your existing LEPIU strategies to a Process Manager LLMUX IOP type. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only LEPIU box types.

*      Analog Input LLMUX Conversion - LLPIU

Use this Template to convert your existing LLPIU strategies to a Process Manager LLMUX IOP type. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only LLPIU box types.

*      Analog Input - MC - With Accum to RegPV Totalizer

Use this Template to convert your existing MC Analog Input w/Accumulation strategies using a Process Manager Regulatory PV Totalizer algorithm. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only MC box types and strategies that contain AVOPTION = ENABLE. This Template connects the Analog Input strategy that is converted using the Analog Input HLAI Conversion - HLPIU/CB/MC Template to its PISRC(1) input connection using the PV parameter. The Hiway Gateway configuration data for timebase and accumulation related parameters are converted to the regulatory PV Totalizer strategy. This strategy is named by appending _TOTLZR to the name of the Hiway Gateway Analog Input strategy as in FQI0100_TOTLZR. If you wish to have these Regulatory PV Totalizer strategy names something different, then you must edit the Transform expression for the TPS.NAME to ANLINHG.NAME binding.

This Template inserts the created Regulatory PV Totalizer algorithm strategy into a Module Strategy named by pre-pending the text string TOTALZR to the Analog Input strategy name. If you wish to have the name of this containing Module Strategy something different, then you must edit the Template expression and replace the references.

*      Analog Input - MC - With Accum to HLAI Conversion

Use this Template to convert your existing MC Analog Input w/Accumulation strategies to a Process Manager HLAI Analog Input Strategy. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only MC box types and strategies that contain AVOPTION = ENABLE. This Template inserts the created Analog Input strategy into a Module Strategy named by pre-pending the text string TOTALZR to the Analog Input strategy name. If you wish to have the name of this containing Module Strategy something different, then you must edit the Template expression and replace the references.

*      Analog Output Standalone - HLPIU/MC Conversion

Use this Template to convert your existing HLPIU and MC Analog Output strategies to a Process Manager Analog Output full form type with PNTMODTY=AO_16. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

Any use of Remote Cascade options is carried forward to the Process Manager Analog Output strategy.

*      Analog Output For AutoMan - HLPIU/MC Conversion

Use this Template to convert your existing HLPIU and MC Analog Output strategies to a Process Manager Analog Output component form type with PNTMODTY=AO_16. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

This Template is designed to be used with the Template Analog Output to RegCtl AutoMan Conversion, which creates a Regulatory Control AutoMan algorithm for driving this Analog Output component Strategy. The name of the created Analog Output strategy is determined by appending _AO to the existing Hiway Gateway Analog Output Strategy as in XO201_AO. If you wish to have these strategy names something different, then you must edit the Transform expression for the TPS.NAME to ANLOUTHG.NAME binding. The name of the created Regulatory Control AutoMan Strategy retains the original name of the Hiway Analog Output Strategy.

Any use of Remote Cascade options is carried forward to the Process Manager Regulatory Control AutoMan Strategy.

*      Analog Output to RegCtl AutoMan Conversion

Use this Template to convert your existing HLPIU and MC Analog Output strategies to a Process Manager Regulatory Control AutoMan algorithm driving a Analog Output component Strategy. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

This Template is designed to be used with the Template Analog Output For AutoMan - HLPIU/MC Conversion, which creates the Analog Output component Strategy that is connected to CODSTN(1). The name of the created Regulatory Control AutoMan Strategy is the original name of the Hiway Analog Output Strategy.

Any use of Remote Cascade options is carried forward to this Process Manager Regulatory Control AutoMan Strategy.

*      Digital Input - STATUS - Conversion

Use this Template to convert your existing HLPIU and MC Digital Input strategies to a Process Manager Digital Input Status type. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

If the HG parameter NMBRINPT contains a value of 2 for two digital input connections, then you must use the Template Digital Input - Input2 - STATUS - Conversion to convert and create the second Process Manager Digital Input Status strategy.

*      Digital Input - Input2 - STATUS - Conversion

Use this Template to convert your existing HLPIU and MC Digital Input strategies that are defined as the second Digital Input connection to a Process Manager Digital Input Status type. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU / MC box types and the HG parameter value NMBRINPT = 2. The name of the created Digital Input strategy that represents the second connection is done by appending I2 to the existing Hiway Gateway Digital Input strategy as in XL201I2. If you wish to have these strategy names something different, then you must edit the Transform expression for the TPS.NAME to DIGINHG.NAME binding.

*      Counter Conversion to AI Pulse

Use this Template to convert your existing HLPIU and MC Digital Counter strategies to a Process Manager Analog Input Pulse type. This Template will convert the HG parameter values to conform to a Process Manager Analog Input Pulse PNTMODTY = PI for accepting variable frequency inputs. This conversion of the Counter Strategy to a Process Manager Analog Input Pulse type also requires that a RegPV Totalizer algorithm be used for accumulation. The Project Link Template named Counter Conversion - PI RegPV Totalizr Algorithm builds the required RegPV Totalizr algorithm Strategy by appending the text "_ACCUM" to the name of the original Counter Strategy as in FQ0100_ACCUM where FQ0100 was the name of the Hiway Counter Strategy. This RegPV Totalizr algorithm Strategy is also connected to the Analog Input Pulse type Strategy parameter PV using its PISRC(1) connection.

*      Counter Conversion - PI RegPV Totalizr Algorithm

Use this Template to convert your existing HLPIU and MC Digital Counter strategies to a Process Manager Analog Input Pulse type that requires the support of a Regulatory PV Totalizr Algorithm to provide accumulation. The RegPV Totalizr Algorithm Strategy is named by appending the text "_ACCUM" to the original Counter Strategy name. Any existing alarming for the Counter Strategy will be configured in the created Regulatory PV Totalizr Algorithm Strategy. This Template inserts the created Analog Input Pulse type Strategy into a Module Strategy named by pre-pending the text string ACCUM_ to the Counter Input strategy name. If you wish to have the name of this containing Module Strategy something different, then you must edit the Template expression and replace the references.

The RegPV Totalizr Algorithm parameter C - Scaling Constant may need to be reconfigured for scaling of the accumulated value. This constant value is defaulted to 1.0 and the application log will indicate this warning when using this Template in an Import task.

This Template should be used together with the Template Counter Conversion to AI Pulse to complete the Counter Strategy conversion utilizing an Analog Input Pulse type Strategy.

*      Counter Conversion - ACCUM to Digital Input

Use this Template to convert your existing HLPIU and MC Digital Counter strategies to a Process Manager Digital Input Accumulation type. This Template will convert the HG parameter values to conform to a Process Manager Digital Input with accumulation. This Template is constructed so that only Counter strategies that contain a value for AVCONV = 1.0 will become part of any Data Collection. This is because the PM Digital Input Accumulator type does not support scaling other than 1.0.

*      Counter Conversion to DI ACCUM Using RegPV Calc

Use this Template to convert your existing HLPIU and MC Digital Counter strategies to a Process Manager Digital Input Accumulation type that requires the support of a Regulatory PV Calcultr Algorithm to provide scaling of the Digital Input Accumulated Value (AV). This Template is constructed so that only Counter strategies that contain a value for AVCONV < 1.0 will become part of any Data Collection. The RegPV Calcultr Algorithm Strategy is named by appending the text "_ACCUM" to the original Counter Strategy name. This Template will convert the HG parameter values to conform to a Process Manager Digital Input with accumulation. Any existing alarming for the Counter Strategy will be configured in the created Regulatory PV Calcultr Algorithm Strategy. This Template inserts the created Digital Input with accumulation Strategy into a Module Strategy named by pre-pending the text string ACCUM_ to the Counter Input strategy name. If you wish to have the name of this containing Module Strategy something different, then you must edit the Template expression and replace the references.

This Template should be used together with the Template Counter Conversion To RegPV Calcultr Algorithm to complete the Counter Strategy conversion.

*      Counter Conversion To RegPV Calcultr Algorithm

Use this Template to convert your existing HLPIU and MC Digital Counter strategies that are configured for accumulation (AVOPTION=ENABLED) using a Process Manager Regulatory PV Calcultr Algorithm that is attached to a Digital Input Strategy configured for accumulation. If the HG parameter AVCONV contains a scaling factor other than 1.0, then you should use this Template to provide a DCS entity that contains the properly scaled totalizer value with alarming. The name of this RegPV Strategy is determined by appending the text string _ACCUM to the original name of the Counter Strategy. If you wish to have the name of this RegPV Strategy something different, then you must edit the Transform expression on the TPS NAME parameter binding and modify the expression. This Template inserts the created RegPV Calcultr Strategy into a Module Strategy named by pre-pending the text string ACCUM to the Counter Input strategy name. If you wish to have the name of this containing Module Strategy something different, then you must edit the Template expression and replace the references.

The Calcultr algorithm CALCEXP expression is written as "P1 * C1" where C1 is set to the Counter AVCONV value. The P1 source is the converted Counter to Digital Input Strategy name using the TPS parameter AV. The PVTV value of this Calcultr algorithm is set to the Counter PRESET value. If a value exists for PDEVTP other than 0.0, then a PVHITP value will be calculated using a PRESET - PDEVTP expression and PVHHTP will be set to the Counter PRESET value along with PVHHPR set to the Counter PRESETPR value and PVHIPR set to Low. If no PDEVTP value exists, then PVHITP will be set to the Counter PRESET value along with PVHIPR set to the Counter PRESETPR value.

*      Digital Output - DO - HLPIU/MC Conversion

Use this Template to convert your existing HLPIU and MC Digital Output strategies to a Process Manager Digital Output Status component form type with PNTMODTY=DO_32. Process Manager Digital Ouput strategies cannot be used by operators the same as a HG Digital Output. To properly convert a Digital Output strategy, you must also build a Digital Composite strategy that is used to control the states of the Digital Output strategy.

The Template Digital Output - DC - HLPIU/MC Conversion is used to create a Process Manager Digital Composite strategy connected to this converted HG Digital Output strategy. The naming of this converted Digital Output strategy is done by appending O1 to the existing HG Digital Output strategy name as in HS504O1. The Process Manager Digital Composite strategy will contain the same name as the converted HG Digital Output strategy. If you wish to have these strategy names something different, then you must edit the Transform expression for the TPS.NAME to DIGOUTHG.NAME binding

*      Digital Output - DC - HLPIU/MC Conversion

Use this Template to build a Process Manager Digital Composite strategy to connect to the converted HLPIU and MC Digital Output strategies. Process Manager Digital Ouput strategies cannot be used by operators the same as a HG Digital Output. To properly convert a Digital Output strategy, you must also build a Digital Composite strategy that is used to control the states of the Digital Output strategy.

This Digital Composite is created as a full form point with a single output connection to the converted HG Digital Output strategy. The TPS parameter value used to access the Digital Output connection is either SO or ONPULSE depending on the HG parameter value for PNTOPOP. Its strategy name will be the same name as the converted HG Digital Output strategy. Its single digital output connection will be the converted HG Digital Output strategy name + O1 as in HS504O1.SO. If you change the name expression used to convert the HG Digital Output strategies, then you must also change the Transform Expression binded to TPS.DODSTN(1) and DIGOUTHG.NAME to conform to the modified HG Digital Output strategy name.

*      Analog Composite - AI - HLAI Conversion - HLPIU/MC

Use this Template to convert your existing HLPIU and MC Analog Composite strategies to a Process Manager HLAI Analog Input full form type. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

This Template will only create the Process Manager Analog Input strategy. You will have to make a decision on how you want the Analog Input strategies to be utilized in control of the process. In some cases you may want to drive the Analog Output connection by creating a Process Manager Regulatory Control Strategy using the AutoMan algorithm. If you are required to do this, then use the conversion Template Analog Composite to RegCtl AutoMan Conversion to create this Process Manager Regulatory Control strategy. This converted HG Analog Input strategy will be connected to the created Process Manager Regulatory Control CISRC(1) connection using the HG Analog Composite name + _AI.PV.

NOTE: The naming used to create a strategy using this Template is done by appending _AI to the existing HG Analog Composite strategy name.

This Template contains a Template Expression, which specifies that a Process Manager Analog Composite and its component Analog Input/Output strategies be created in a strategy module. This is a good methodology to use when creating control implementations that results in all control related strategies being contained within the same module. It helps to organize the TPS BuilderŽ project the same as using folders in your workstation to organize your files. The Template Expression for this Template and the Analog Input/Output component templates uses the existing HG Analog Composite strategy name to create the module strategy name by prepending ACMODULE_ as in ACMODULE_HC524. This default module name can be changed by editing this Template expression.

*      Analog Composite - AO - Conversion - HLPIU/MC

Use this Template to convert your existing HLPIU and MC Analog Composite strategies to a Process Manager Analog Output full form type on an AO_16 IOM Module type. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

This Template will only create the Process Manager Analog Output strategy as a standalone data point. If you want to drive an Analog Output using a Regulatory AutoMan Algorithm Strategy, then choose the conversion Template Analog Composite - AO/AUTOMAN - Conversion to convert to an Analog Output that is connected to CODSTN(1) of the created Regulatory Control Strategy.

Any use of Remote Cascade options is carried forward to the Process Manager Analog Output strategy.

*      Analog Composite to RegCtl AutoMan Conversion

Use this Template to convert your existing HLPIU and MC Analog Composite strategies using the converted Process Manager Analog Input/Output strategies connected to a Process Manager Regulatory Control AutoMan Algorithm Strategy . This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

Any alarming requirements for this type of conversion is done on the created full form Process Manager Analog Input strategy. Control Equation EqA is used for the created AutoMan algorithm.

Any use of Remote Cascade options is carried forward to this created Regulatory Control Strategy.

*      Analog Composite - AO/AUTOMAN - Conversion

Use this Template to convert your existing HLPIU and MC Analog Composite strategies to a Process Manager Analog Output component form that is connected to CODSTN(1) of the created Regulatory AutoMan Algorithm Strategy. A constant binding specifies AO_16 as the PNTMODTY parameter value. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

This Template will only create the Process Manager Analog Output strategy. Use the conversion Template Analog Composite to RegCtl AutoMan Conversion to create the Process Manager Regulatory AutoMan Algorithm Strategy that is automatically connected to the converted Analog Input/Output component strategies..

This Template contains a Template Expression, which specifies that a Process Manager Analog Composite and its component Analog Input/Output strategies be created in a strategy module. This is a good methodology to use when creating control implementations that results in all control related strategies being contained within the same module. It helps to organize the TPS BuilderŽ project the same as using folders in your workstation to organize your files. The Template Expression for this Template and the Analog Input/Output component templates uses the existing HG Analog Composite strategy name to create the module strategy name by prepending ACMODULE_ as in ACMODULE_HC524. This default module name can be changed by editing this Template expression.

*      Digital Composite - DC Conversion - HLPIU/MC

Use this Template to convert your existing HLPIU and MC Digital Composite strategies to a Process Manager Digital Composite strategy. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

Whe converting HG Digital Composite strategies, a number of Process Manager Digital Input and Digital Output strategies must be configured for connecting to the Digital Composite strategy. Based on the parameter value for NMBRINPT, one or two digital input connections will be established to DISRC(1) and DISRC(2) using a variation of the HG Digital Composite strategy name by appending I1 and I2 to the existing HG Digital Composite strategy name and then appending the connection parameter value .PVFL as in DC402I1.PVFL for a Digital Composite strategy name of DC402. Based on the parameter value for NMBROUT, one or two digital output connections will be established to DODSTN(1) and DODSTN(2) using a variation of the HG Digital Composite strategy name by appending O1 and O2 to the existing HG Digital Composite strategy name and then appending the connection parameter value .SO or .ONPULSE as in DC402O1.SO for a Digital Composite strategy name of DC402. . If you wish to change the names that are generated for these connections, then you must edit the Transform Expressions for the bindings TPS.DISRC(1), TPS.DISRC(2), TPS.DODSTN(1), TPS.DODSTN(2) to DIGCMPHG.NAME.

The Process Manager PVNORMAL parameter is set based on the detection of the Hiway alarming state. If the Hiway parameter DIGALFMT is equal to State1 or Input1, then PVNORMAL is set to the state text of the Hiway parameter STATE2 and if DIGALFMT is equal to State2 or Input2, then PVNORMAL is set to the state text of the Hiway parameter STATE1.

This Template contains a Template Expression, which specifies that a Process Manager Digital Composite and its component Digital Input/Output strategies be created in a strategy module. This is a good methodology to use when creating control implementations that results in all control related strategies being contained within the same module. It helps to organize the TPS BuilderŽ project the same as using folders in your workstation to organize your files. The Template Expression for this Template and the Digital Input/Output component templates uses the existing HG Digital Composite strategy name to create the module strategy name by prepending DCMODULE_ as in DCMODULE_HS512. This default module name can be changed by editing this Template expression.

*      Digital Composite - DC-DigInA - Conversion

Use this Template to convert your existing HLPIU and MC Digital Composite strategies to a Process Manager Digital Input strategy. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

Hiway Gateway Digital Composite strategies may specify a number of Digital Input connections to existing card types. These hardware referenced strategy connections should be converted to Process Manager Digital Input strategies. This Template will determine if the HG parameter value NMBRINPT is greater than zero and will create the Process Manager Digital Input strategy as a component point form. All alarming associated with the HG Digital Input part of this Digital Composite strategy is applied to the Process Manager Digital Composite strategy.

The strategy name is determined by appending I1 to the existing HG Digital Composite strategy name and then appending the connection parameter value .PVFL as in DC402I1.PVFL for a Digital Composite strategy name of DC402.

*      Digital Composite - DC-DigInB - Conversion

Use this Template to convert your existing HLPIU and MC Digital Composite strategies to a Process Manager Digital Input strategy. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

Hiway Gateway Digital Composite strategies may specify a number of Digital Input connections to existing card types. These hardware referenced strategy connections should be converted to Process Manager Digital Input strategies. This Template will determine if the HG parameter value NMBRINPT is greater than one and will create the Process Manager Digital Input strategy as a component point form. All alarming associated with the HG Digital Input part of this Digital Composite strategy is applied to the Process Manager Digital Composite strategy.

The strategy name is determined by appending I2 to the existing HG Digital Composite strategy name and then appending the connection parameter value .PVFL as in DC402I2.PVFL for a Digital Composite strategy name of DC402.

*      Digital Composite - DC-DigOutA - Conversion

Use this Template to convert your existing HLPIU and MC Digital Composite strategies to a Process Manager Digital Output strategy. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

Hiway Gateway Digital Composite strategies may specify a number of Digital Output connections to existing card types. These hardware referenced strategy connections should be converted to Process Manager Digital Output strategies. This Template will determine if the HG parameter value NMBROUT is greater than zero and will create the Process Manager Digital Output strategy as a component point form.

The strategy name is determined by appending O1 to the existing HG Digital Composite strategy name as in DC402O1.SO for a Digital Composite strategy name of DC402.

*      Digital Composite - DC-DigOutB - Conversion

Use this Template to convert your existing HLPIU and MC Digital Composite strategies to a Process Manager Digital Output strategy. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

Hiway Gateway Digital Composite strategies may specify a number of Digital Output connections to existing card types. These hardware referenced strategy connections should be converted to Process Manager Digital Output strategies. This Template will determine if the HG parameter value NMBROUT is greater than one and will create the Process Manager Digital Output strategy as a component point form.

The strategy name is determined by appending O2 to the existing HG Digital Composite strategy name as in DC402O2.SO for a Digital Composite strategy name of DC402.

*      Digital Composite - DEVCTL Conversion - HLPIU/MC

Use this Template to convert your existing HLPIU and MC Digital Composite strategies to a Process Manager Device Control Strategy. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

Whe converting HG Digital Composite strategies, a number of Process Manager Digital Input and Digital Output strategies must be configured for connecting to the Device Control strategy. Based on the parameter value for NMBRINPT, one or two digital input connections will be established to DISRC(1) and DISRC(2) using a variation of the HG Digital Composite strategy name by appending I1 and I2 to the existing HG Digital Composite strategy name and then appending the connection parameter value .PVFL as in DC402I1.PVFL for a Digital Composite strategy name of DC402. Based on the parameter value for NMBROUT, one or two digital output connections will be established to DODSTN(1) and DODSTN(2) using a variation of the HG Digital Composite strategy name by appending O1 and O2 to the existing HG Digital Composite strategy name and then appending the connection parameter value .SO or .ONPULSE as in DC402O1.SO for a Digital Composite strategy name of DC402. . If you wish to change the names that are generated for these connections, then you must edit the Transform Expressions for the bindings TPS.DISRC(1), TPS.DISRC(2), TPS.DODSTN(1), TPS.DODSTN(2) to DIGCMPHG.NAME.

The Process Manager PVNORMAL parameter is set based on the detection of the Hiway alarming state. If the Hiway parameter DIGALFMT is equal to State1 or Input1, then PVNORMAL is set to the state text of the Hiway parameter STATE2 and if DIGALFMT is equal to State2 or Input2, then PVNORMAL is set to the state text of the Hiway parameter STATE1.

This Template contains a Template Expression, which specifies that a Process Device Control and its component Digital Input/Output strategies be created in a strategy module. This is a good methodology to use when creating control implementations that results in all control related strategies being contained within the same module. It helps to organize the TPS BuilderŽ project the same as using folders in your workstation to organize your files. The Template Expression for this Template and the Digital Input/Output component templates uses the existing HG Digital Composite strategy name to create the module strategy name by prepending DEVCTLMODULE_ as in DEVCTLMODULE_HS512. This default module name can be changed by editing this Template expression.

*      Digital Composite - DEVCTL -DigInA - Conversion

Use this Template to convert your existing HLPIU and MC Digital Composite strategies to a Process Manager Digital Input strategy. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

Hiway Gateway Digital Composite strategies may specify a number of Digital Input connections to existing card types. These hardware referenced strategy connections should be converted to Process Manager Digital Input strategies. This Template will determine if the HG parameter value NMBRINPT is greater than zero and will create the Process Manager Digital Input strategy as a component point form. All alarming associated with the HG Digital Input part of this Digital Composite strategy is applied to the Process Manager Device Control Strategy.

The strategy name is determined by appending I1 to the existing HG Digital Composite strategy name and then appending the connection parameter value .PVFL as in DC402I1.PVFL for a Digital Composite strategy name of DC402.

*      Digital Composite - DEVCTL -DigInB - Conversion

Use this Template to convert your existing HLPIU and MC Digital Composite strategies to a Process Manager Digital Input strategy. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

Hiway Gateway Digital Composite strategies may specify a number of Digital Input connections to existing card types. These hardware referenced strategy connections should be converted to Process Manager Digital Input strategies. This Template will determine if the HG parameter value NMBRINPT is greater than one and will create the Process Manager Digital Input strategy as a component point form. All alarming associated with the HG Digital Input part of this Digital Composite strategy is applied to the Process Manager Device Control Strategy.

The strategy name is determined by appending I2 to the existing HG Digital Composite strategy name and then appending the connection parameter value .PVFL as in DC402I2.PVFL for a Digital Composite strategy name of DC402.

*      Digital Composite - DEVCTL -DigOutA - Conversion

Use this Template to convert your existing HLPIU and MC Digital Composite strategies to a Process Manager Digital Output strategy. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

Hiway Gateway Digital Composite strategies may specify a number of Digital Output connections to existing card types. These hardware referenced strategy connections should be converted to Process Manager Digital Output strategies. This Template will determine if the HG parameter value NMBROUT is greater than zero and will create the Process Manager Digital Output strategy as a component point form.

The strategy name is determined by appending O1 to the existing HG Digital Composite strategy name as in DC402O1.SO for a Digital Composite strategy name of DC402.

*      Digital Composite - DEVCTL -DigOutB - Conversion

Use this Template to convert your existing HLPIU and MC Digital Composite strategies to a Process Manager Digital Output strategy. This Template contains a User Definition that builds a query on your Data Source that limits the scope of Hiway Gateway strategies to only HLPIU and MC box types.

Hiway Gateway Digital Composite strategies may specify a number of Digital Output connections to existing card types. These hardware referenced strategy connections should be converted to Process Manager Digital Output strategies. This Template will determine if the HG parameter value NMBROUT is greater than one and will create the Process Manager Digital Output strategy as a component point form.

The strategy name is determined by appending O2 to the existing HG Digital Composite strategy name as in DC402O2.SO for a Digital Composite strategy name of DC402.

*      Flag - MC - Conversion

Use this Template to convert your existing MC Flag strategies to a Process Manager Flag strategy.

Any detected use of Event Initiated Processing for the MC Flag strategy will result in a warning notification being generated that this cannot convert to the Process Manager Flag strategy. You will then have to determine how to resolve this.

*      Numeric - MC - Conversion

Use this Template to convert your existing MC Numeric strategies to a Process Manager Numeric strategy.

*      Process Module - MC - Conversion

Use this Template to convert your existing MC Process Module strategies to a Process Manager Process Module strategy.

*      Timer - MC - Conversion

Use this Template to convert your existing MC Timer strategies to a Process Manager Timer strategy.

Generate Notes

*      All real number parameter types such as PVEUHI, PVEULO, PVEXEUHI, PVEXEULO, PVHITP, etc., are rounded to zero decimal places during conversion. If you wish to change how these parameter values are rounded, you will have to modify the expressions for the specific parameter bindings and/or the Template Expression for the Binding Drawing. The parameters PVEUHI, PVEULO, PVHITP, PVHHTP, PVLOTP, PVLLTP have their rounding expressions specified in the Template Expression for each Template Binding drawing.

Changing the Project Link Templates to convert to a PM or APM Node Type

This Project Link is designed to convert all Hiway Gateway strategies to an HPM node type. If you need to convert the Hiway Gateway strategies to a PM or HPM node type, then you must modify the Constant Expression for all Template Binding Drawings. The Constant Expression is connected to the TPS parameter NODETYP and specifies the following expression value:

this = "HPM"

Change this expression to the desired node type.

Advanced Naming

Users that are capable of working with the Microsoft Access application can choose to modify the table structures for the tables DIGCMPHG, ANLCMPHG to add columns where the new names of the created component strategies are specified by editing the table data. For the DIGCMPHG table you would want to add 4 new columns to the table structure such as DIGIN1NAME, DIGIN2NAME, DIGOUTNAME1, DIGOUTNAME2 and edit the column data for each Hiway Gateway Digital Composite strategy that requires creating of these component strategies during the conversion process. You will then remove the existing Transform Expressions for DISRC(1), DISRC(2), DODSTN(1), DODSTN(2) and add a Transform Expression for each TPS connection parameter to its corresponding Table.Column name that you added to the table structure. The Transform Expression will be specified as:

 
        Sub OnImport(ONBIND)
        
              // This builds the Digital Input connection by using the binded Table.Column name value
              // and appending the TPS parameter to connect with.
              this + ".PVFL";
 
        End Sub
 
        Sub OnImport(ONBIND)
 
              // This builds the Digital Output connection by using the binded Table.Column name value
              // and appending the TPS parameter value to connect to based on the HG parameter value
              // PNTOPOP.
              IIf ( Val(DIGCMPHG.NMBROUT) = 0, NULL, this + IIF ( Upper( DIGCMPHG.PNTOPOP) = "PULSEOUT", ".ONPULSE", ".SO") );
 
        End Sub

You will also have to remove the Transform Expressions that are binding TPS.NAME to DIGCMPHG.NAME and replace these expressions with a simple parameter binding from TPS.NAME to your added Table.Column identifiers that specify the new component strategy names.

Recommendation for Containment of Converted Hiway Gateway Strategies

You may find it useful to contain your converted Hiway Gateway strategies in modules to help organize your TPS BuilderŽ project and to make it easier to delete TPS BuilderŽ strategies that for some reason did not convert as required.

You can specify a Template Expression for all Templates contained in this Project Link so that all Process Manager strategies created using the Template will be contained within a specified module strategy. You may want to organize your TPS BuilderŽ project strategies by:

*      Honeywell Process Unit ID

*      Process Manager Point Types

See the example Template Expression for the Template Digital Composite - DC Conversion to use in creating other Template expressions.

Resolving Connections

When converting Hiway Gateway Analog Composite and Digital Composite strategies, you will find it necessary to execute the TPS BuilderŽ Resolve Connections process to resolve all connections contained within these converted strategies. This resolving process will validate the connections that exist for these strategy types. If you do not perform this step, then when you call up a strategy of this type in the TPS BuilderŽ strategy form, the connection names will displayed in a LtRed text color indicating that they have not been validated.

Assigning Address Data to the Converted Process Manager Strategies

The final step in configuring your converted Process Manager strategies will be to assign valid address numbers to the Process Manager Node, Module, and Slot. There a number of ways to use Data Transfer to update the migrated Hiway data point addresses including:

Using a Generic Template to Export Existing Address Data for Changing and Re-importing

You can use a Generic Template to export all the existing address parameter data to a Microsoft Excel spreadsheet to affect the address changes and then import these back to your TPS Builder project to update the existing strategies. When working with Microsoft Excel spreadsheets, keep in mind that the data in any column must be formatted the same. If the first couple of rows in a column are formatted as a number and other data in this column in the remaining rows are formatted as text with the ' character preceding the column value, then only the first couple rows formatted as numeric will be visible to Data Transfer. See the online help topic for Generic Templates to use this method.

Using Entity List Files as a Text File Data Source

Using Data Transfer, you can generate an Entity List (EL) file that will contain all imported (converted) strategies using the Templates in this Project Link by clicking the button Generate EL File located on the Data Collection View for each Data Collection task. This will generate a text file with the extension .EL for all strategies that were imported using this Data Collection task.

To use this generated Entity List (EL) file in Data Transfer you will have to change the extension of the text file to replace EL with TXT. You can than connect to this Entity List file as a text Data Source. Before you do this you will have to modify the contents of this Entity List file so that Data Transfer can recognize valid column identifiers and their column data. The first row of any text file used as a Data Source must contain the column identifier names. In this case you would specify as the first row the text NAME. When connected to a Template in a Project Link this column identifier NAME can then be used to bind to a TPS Parameter. To add Node, Module, and Slot address information to this file, add the comma delimited column identifiers to the first row and continue specifying the address data next to its corresponding strategy name value as comma delimited values as in HS400, 10, 0, 5 where the column identifiers for this example would look like NAME, NODENUM, MODNUM, SLOTNUM.

You can also import this generated Entity List file into a Microsoft Excel Spreadsheet or Microsoft Access Database to build and define the address data for the imported (converted) Process Manager strategies.

See the online documentation topic Managing Project Links for more information.

Modifying the Microsoft Access Database For Address Changes

Users that are capable of working with the Microsoft Access application can choose to modify the table structures for the tables to add columns to specify the address parameters NODENUM, MODNUM, SLOTNUM and edit the table data to specify the address information. You can then execute a Data Collection task on the appropriate Project Link Templates to import this address parameter changes into the created Process Manager strategies in your TPS BuilderŽ project. The Data Collection will report only the parameter values that have changed, which in this case would be the address related parameters.

You can use a Generic Template from the TPS Generic Library to configure the bindings required to assign address parameter values to the imported (converted) strategies. A Generic Template is required when you are wanting to work with multiple point types using a single Template in a Project Link. A Generic Template therefore allows you to bind to TPS parameters that are common amongst a group of point types such as NAME, NODENUM, MODNUM, SLOTNUM, etc. See the online documentation topic Generic Templates for more information on working with Generic Template types.

Checking the converted Hiway Gateway Configuration

It is recommended that you check and validate the converted configuration data in your TPS BuilderŽ projects by using the TPS BuilderŽ Check functionality. If you find any problems that are related to the Transform Expressions or bindings in general, then you will want to correct the problems in Data Transfer and execute a Data Collection task on the affected Project Link Templates to update the parameter configuration data in your TPS BuilderŽ project.

Forward Building to EB Files For TPS Loading

You will use TPS BuilderŽ to forward build the converted Process Manager strategies to Honeywell Exception Build (EB) files for loading on the TPS System. When you import (convert) your Hiway Gateway strategies to your TPS BuilderŽ project using a Data Collection task, you can click on the button Generate EL File located on the Data Collection View to generate an Entity List (EL) file that contains a list of imported (converted) Process Manager strategies associated with the Data Collection import operation task. You can use this generated Entity List file to specify to the TPS BuilderŽ Forward Build tool the scope of strategies to build to an Exception Build file. This is also very convenient if you happen to modify or re-convert TPS strategies and need to overwrite the loaded TPS System configuration data.

Comments

AST is committed to providing the tools required to successfully convert your Hiway Gateway configuration data to Process Manager based controls. AST will be providing regular maintenance releases, which will bring more functionality and ease of use to the conversion process. AST has plans to implement or improve the following functionality:

*      Provide a Wizard similar to the existing Hiway Regulatory Control Conversion Wizard to handle conversion of HG Digital and Analog Composite point types.

*      Provide a Task Building Wizard that will allow you to build and save configured tasks. You will then be able to specify the exact group of Templates to use in a Project Link for your Data Collection and Import operation tasks. This Task definition can then be reused any time for a specific type of Hiway Gateway conversion process.

*      AST is in the process of defining the requirements for converting existing Area and History data from the TPS to conform to the converted UCN controls.

*      Provide a means of converting existing MultiFunction Controller Logic and CL to the Process Manager. This is currently a high priority.

*      Provide a search tool that will improve upon the existing TPS Documentation tool for finding references to converted Hiway Gateway strategies that may require subsequent modifications in Schematics/GUS Displays, Application Module CL, Computer Gateway, etc.

If you have any suggestions or recommendations on how AST can aid you in your conversion requirements, please contact AST support at http://www.autosofttech.com/SuggestionList.asp.

 

If you encounter any difficulties with this installation or if you have any comments please contact AST support at http://www.autosofttech.com/TechSupport.htm.