Topic 1.1.7: Editors & Modules

  • Configuration Programs (Editors)
    • InBatch is a product that uses multiple managers, editors, and utilities. The following configuration programs are used to develop and manage your batch system.
    • Environment Editor (EnvEdit): (Required) Used to define the batch configuration and runtime applications that are to be edited.
    • Process Model Editor (ModelEdit): (Required) Provides the capability for a user to create a process model database. Only one Process Model Editor can run in a system at any time.
    • Tag Link Editor (TagLinker): (Required) The Tag Link Editor utility associates InBatch tags with a control system. It is also capable of associating InBatch tags with InTouch tags. Tag Linker also exports InBatch tags to a comma separated variable file which will ultimately populate the InTouch tag dictionary with memory and/or IO tags.
    • Train Editor (TrainEdit): (Required) The Train Editor is used to create production lines on which batches are scheduled.
    • Materials Editor (MaterialEdit): (Required) Provides the capability for a user to create and edit a materials database both on and off-line. Multiple Materials Editors can run in a system enabling multiple users to edit the same database simultaneously.
    • Recipe Editor (RecipeEdit): (Required) Provides the capability for a user to create and edit a recipe database both on and offline. Multiple Recipe Editors can run in a system enabling multiple users to edit the same database simultaneously.
    • Process Log Editor (LogEdit): (Optional) Used to create, edit, and print logger configurations.
    • Batch Reporting (BatchReport): The BatchReport icon launches a web browser that provides access to the batch system's webbased reporting system.
    • Security Editor (SecEdit): (Optional) Provides the capability for a user to define the users of the system, security levels form each user, appropriate workstation access for each user, appropriate recipe access for each user, and enable/disable applications and functions requiring security. The Security Editor is part of the security system, and is available as an additional option to the batch control system.

  • Runtime Modules
    • The following runtime programs are used by the batch system during batch execution. The architecture of InBatch as a whole is made up of a combination of the following runtime modules. Only those modules which are required by the particular architecture of your application will be utilized.
    • Environment Manager (EnvMngr): (Required) Manages the execution of the batch configuration and runtime applications defined with the Environment Editor.
    • Environment Display (EnvDspl): (Required) The Environment Display is a client of the Environment Manager and provides a single interface for starting and stopping all batch system GUI applications.
    • Unilink Manager (UnilinkMngr): (Required) Manages inter-process communications.
    • InBatch Client (IBCli): (Required) IBCli is a runtime application which allows I/O client applications to access InBatch tags. One instance of IBCli is required for each I/O access name. IBCli communicates with Wonderware or third party tag server components using DDE, OPC, or SuiteLink protocols.
    • InBatch Message Exchange (IBMX): (Required if using Galaxy data) The InBatch Message Exchange (IBMX) is the link to Galaxy data using Wonderware Application Server. It enables mapping InBatch Tags with Galaxy attributes to transfer data between both environments. The communication between InBatch and Wonderware Application Server uses the Message Exchange protocol.
    • Memory Tag Manager (MemTagMngr): (Required) The System Tag Manager is responsible for generating the system tags for all of the equipment in the process model.
    • Simulation Manager (SimMngr): (Optional) The Simulation Manager replaces the communication drivers for a batch system and allows the system to be executed without control system hardware present.
    • Information Manager (InfoMngr): (Required) Provides general batch server information to client applications.
    • InBatch Server (IBServ): (Required) Runtime IBServ server application which allows I/O client applications (InTouch) to use InBatch TIM tags and Control System Tags.
    • Batch Manager (BatchMngr): (Required) Interfaces with the process model, recipe, and materials databases. The Batch Manager works in conjunction with the Batch Scheduler and Batch Display programs. The Batch Manager executes all recipes, manages unit allocation, moves batch information to the Historian, and triggers reports.
    • Batch Scheduler (BatchSched): (Optional) Interfaces with the Batch Manager and is used to construct a schedule of batches to be executed. Multiple Batch Schedulers can run in a system.
    • Batch Display (BatchDspl): (Optional) The Batch Display is a client of the Batch Manager, and provides all of the runtime information concerning the execution of a single batch. Multiple Batch Display modules can run in a system.
    • Process Logger Manager (LogMngr): (Optional) The Process Logger Manager controls the data logging of any tag in the system according to the logging configuration. Multiple Process Logger modules can be run in a system.
    • Security Manager (SecMngr): (Optional) The Security Manager is used by both batch and external applications to evaluate requests for security clearance. The Security Manager is part of the security system, and is available as an additional option to the batch control system.
    • Recipe Automation Server (RecipeEdit): The Recipe Automation Server is an integral part of Recipe Editor and is installed on the Batch Server and the Batch Development Client. (Refer to COM Technical Reference Guide for more information.)
    • Batch Talk ActiveX Control (OCXBATCH.OCX): The OCXBATCH.OCX is a background server supporting ActiveX technology that provides all functionality provided by the Batch Talk API. This server is installed in the Batch Server, Run-time and Development Clients. (Refer to COM Technical Reference Guide for more information.)
    • Recipe Procedure SFC Active X Control (INBATCHSFC.OCX): The SFC ActiveX Control is a GUI-based control for the recipe procedure. This control is installed in the Batch Server, Runtime and Development Clients. (Refer to COM Technical Reference Guide for more information.)
    • Material Automation Server (MATERIALSVR.EXE): The Material Automation Server provides access to the Material database using ActiveX technology. This server is installed in the Batch Server, Runtime and Development Clients.
    • Batch Function Interface Type Libraries (BATCHOBJSRV.DLL & BATCHVBSERVER.DLL): The Batch Function Interface Type libraries are used to construct a Batch Manager in-process server. The libraries provide access to the key events during batch execution. (Refer to COM Technical Reference Guide for more information.)
    • InBatch Stateless API: The InBatch Stateless API is used to access batch schedule and runtime batch data. The API is based on the Batch Talk ActiveX Control and is a class library that can be used on the InBatch Server platform or the InBatch run-time client platform. It is designed to be used in a custom .NET application or ArchestrA Application Object scripting.

  • Utility Modules
    • The following Utility Programs are provided with the batch system to help assist development and runtime processes.
    • Phase Logic Testing Tool (PhaseLogic): (Optional) The Phase Logic module permits individual phase execution independent of any batch operation. Multiple Phase Logic modules can be run in a system.
    • Change Password (ChgPwd):(Optional) The Change Password application permits the user to interact with the security system from the DOS command line in order to change a user's password. The Change Password utility is part of the security system and is available as an additional option to the batch control system.
    • Tag View (TagView):(Optional) The Tag View application permits monitoring and changing any of the InBatch equipment or TIM tags.
Last modified: Tuesday, 28 April 2020, 1:23 PM