1 Introduction CIMS system is a system that optimizes and processes information such as enterprise business decision-making, management, planning, scheduling, process optimization, fault diagnosis, and field control based on enterprise network. This article takes the transformation design of the CIMS system of a cigarette factory power workshop cold station as an example and discusses the relevant technologies for the implementation of the cold station CIMS system in a relatively in-depth manner. 2 Implementation technology of CIMS system integration When building a CIMS system, the interconnection of control and information networks is of great significance. In the design of the cold station CIMS system, configuration software that supports OPC technology is used as a link to realize the integration of control and information networks. 2.1 OPC technology OPC is a key technology for realizing the interconnection of information between the field equipment level and the process monitoring level of the control system [4][5]. Based on Microsoft's (distributed) component object model, it adopts the client/server model and encapsulates an application (OPC server) as an object according to the principle of object orientation. Only the interface methods are exposed. The client calls them in a unified way, freeing the user from low-level development. OPC enables remote invocation, making application distribution independent of system hardware distribution, simplifying system hardware configuration, and thus broadening the system's application scope. In essence, OPC provides a mechanism that allows a system to obtain data from a data source in a standardized manner and pass it to any client program. The OPC server is the data supplier, responsible for providing the required data to OPC clients; the OPC client is the data user. As the middle layer of the fieldbus architecture, the OPC server seamlessly connects field signals with software such as SCADA and HMI according to a unified standard, effectively separating hardware and application software. The OPC server provides interfaces to lower-level devices, enabling various process information from the field to enter the OPC server, thus achieving downward interconnection; the OPC server also provides standard interfaces to upper-level devices, enabling intranet devices to obtain data from the OPC server, thus achieving upward interconnection. Both types of interconnection are bidirectional. Through the OPC interface, all field devices providing OPC servers can be accessed, enabling communication with these field devices. [align=center] Figure 1 OPC's position in the control system[/align] 2.2 The monitoring configuration software is convenient for equipment. The system uses rsview32 configuration software. This configuration software can generate various graphic objects or text through its drawing tools. It provides a large number of industrial equipment graphics and instrument symbols, as well as trend charts, historical curves, group data analysis charts and other graphic libraries. It can directly use objects generated by other drawing software packages such as AutoCAD and CorelDRAW. Its graphical user interface is user-friendly, including a complete set of Windows-style windows, pop-up menus, buttons, message areas, toolbars, scroll bars and monitoring screens. Its animation control function screen is rich and colorful. It can activate graphic objects to reflect process changes, which greatly facilitates the normal operation of equipment and centralized monitoring by operators. In addition, its important features are powerful communication functions, good openness and database resource sharing[6]. (1) Database resource sharing open design can easily share information with Microsoft products. Its real-time tag database is an ODBC[7] compatible database. It can use other database tools such as Microsoft Access, Sybase, SQL Server to browse and manage tags, realize data and information sharing between the local control unit and the host computer, provide users with a more centralized data operation environment, and realize centralized information management. (2) Powerful communication function This configuration software can be interconnected with multiple communication protocols and supports multiple hardware devices, such as various models of PLCs from companies such as Allen-Bradley, Modicon, Siemens, and Omron. It is adaptable to various measurement and control hardware devices and can meet the requirements of different measurement points. Downward, it can communicate with data acquisition hardware through RS-Linx, OPC, etc.; upward, it can be interconnected with the high-level management network through TCP/IP and Ethernet. OPC enables RS-View32 to act as a client or server, allowing point-to-point communication between different RS-View32 stations and other OPC servers. (3) The position of configuration software in the monitoring system In the monitoring system, the monitoring configuration software that is put into operation is the data acquisition and processing center, remote monitoring center and data forwarding center of the system[8]. As shown in Figure 2, the monitoring configuration software in operation, together with various control and detection equipment (such as industrial control computers and PLCs connected to the fieldbus), constitutes a rapid response/control center. After the monitoring configuration software is put into operation, the operator can complete the following tasks with its support: [align=center] Figure 2 The position of configuration software in the SCADA system[/align] View the real-time data and process screen of the production site, browse various real-time/historical trend screens; Automatically print various real-time/historical production reports; Timely obtain various process alarms and system alarms; When necessary, the production process can be manually intervened, and the production process parameters and status can be modified; Network with the computer of the management department to provide the management department with real-time production data. rsview32 supports OPC technology and is a bridge connecting the control network and the information network. Through the OPC interface, it can not only connect to information transmitted from field devices, but also exchange data with other application software; through the OPC interface, the information network and the real-time database of the control network can be interconnected, that is, the control network and the information network can be integrated. 3. Cold Station CIMS System Based on ControlNet 3.1 Cold Station CIMS Architecture Construction In order to realize the connection between the underlying control network and the factory information network, and to transmit the field device information and production process data of the workshop level to the factory management level in real time, and to realize the integration of the control network and the information network, a CIMS system based on ControlNet fieldbus technology was constructed: the design adopts a two-layer network structure of workshop process monitoring level and factory management level, as shown in Figure 3. 3.2 System Software Architecture To realize the linking, exchange and fusion of data between the control network and the information network, the software architecture shown in Figure 4 was constructed. At the monitoring layer, RSView32 uses a real-time database to store real-time field data; at the management layer, RSView32 can realize the linking and exchange of data with the monitoring layer. To achieve the integration of control network and information network, the core issues to be addressed are: [align=center] Figure 3 Schematic diagram of chiller plant CIMS structure[/align] [align=center] Figure 4 Schematic diagram of system software architecture[/align] (1) How to achieve real-time data acquisition and write it into the real-time database of configuration software; (2) How to achieve the exchange of real-time data information between the management monitoring machine and the intermediate monitoring host machine within the configuration software and achieve remote monitoring. In the chiller plant control system, the monitoring layer configuration software is both an OPC client and an OPC server. When acquiring real-time data from field equipment, the configuration software acts as an OPC client, and the chiller programmable controller (PLC) acts as an OPC server. Each OPC server is treated as an external device and can be defined, added, or deleted. During system operation, the OPC server provides an interface to the lower-level devices, enabling various process information from the field control layer to enter the OPC server; rsview32 establishes a connection with each OPC server, automatically completes data exchange with the OPC server, and collects data from each subsystem into the real-time database of the configuration software. Meanwhile, the monitoring layer upper computer configuration software rsview32 also serves as the OPC server, and the management layer monitoring software rsview32 serves as its OPC client. Through the communication configuration of the client and the server, the data exchange and integration of the control network and the information network are realized. 4 Configuration design of the control network monitoring operation platform of the cold station 4.1 Implementing the control function of the cold station system The main contents of the software configuration design (1) Human-machine interface. The cold station process flow diagram is displayed on the human-machine interface, that is, the simulated display of the field system and its environment; the operation mode, control switch and running status of the field equipment are displayed; the system operating environment and working description information are displayed; a pop-up menu similar to other Windows application software interfaces is displayed so that operators can call non-main interface information, such as the historical operation curves of various field equipment, production reports, secondary display monitoring interfaces and alarm records, etc. (2) Management of real-time and historical data. This includes the design of response and processing methods for various real-time data, the design of filtering and storage management of historical data, the display design of real-time and historical data (such as using dynamic display curves, historical trend charts, reports, etc.), and the output design of real-time and historical data (such as printing methods, data exchange protocols with other application software programs, and network publishing methods, etc.). (3) Alarm and event management. Record on-site accidents and fault information, so that the corresponding alarm information is displayed on the monitoring interface or transmitted to other sound and light alarm devices, and at the same time, the alarm information is transmitted to the corresponding control processing unit; record on-site production events and operation information, and provide query system operation status in the form of charts. 4.2 Creating a project The rsview32 configuration software mainly includes system, graphic display, alarm, data recording settings, logic and control components. The above functions of the monitoring system can be easily developed using these basic components. First, create this project in rsview32: Control system of a cigarette factory cold station. First, open RSView32. Click the "New" button in the "File" menu on the toolbar. In the "Create Project" dialog box, enter the project name in the "Project Name" field, as shown in Figure 5. Then click "Open" to complete the project creation. Once the project is created, you will see the project manager, where you can configure graphical, alarm, or trend displays after configuring system communication. 4.3 Channel Node Configuration RSView32 communicates with the programmable controllers connected to ControlNet via the included RSLINX. Therefore, RSLINX must be opened before starting RSView32. After starting RSView32, double-click the "System" component in the project editor to open the channel and node editors. In the channel editor, select the ControlNet network to which the node is connected. Since the programmable controllers used in this system are Omron PLC and Control Logix 5555, in the node editor: select "OPC Server" as the data source. RSView32 communicates with Omron PLC and Control Logix 5555 via RSLINX. Each chiller node is an OPC server, and the configuration software is an OPC client. Enter the custom node name for the programmable controller in the Node Name field; the node name for the cooling tower is opcnode_cooltower. Select "Enable," click "Accept" to save the node definition, click "Next," and then define another node, or select the "Close" command to exit node editing. 4.4 Tag Database Configuration The tag database consists of records called tags. Tag values ​​can be used by various parts of the system. Graphical displays use tag values ​​to control animated objects or update trend graphs; alarm systems monitor tag values ​​and compare them to "acceptable" ranges; "Data Records" store tag values ​​and create historical records. However, tag values ​​are stored in a numerical table, not in a database. Tag values ​​can be permanently recorded on disk by logging tag values ​​to a data file. To create a tag, you need to specify its name, type its data, and its data source. Alarms for individual tags are set in the tag database editor; this information can be set when adding the tag or added later when editing the tag. When creating this project, rsview32 will create system tags. If the tag database needs to monitor the changes in tag parameter values ​​to generate alarm information, alarm information configuration must be performed to specify which tags need to be monitored for alarm information. Select a tag in the tag database editor, and then select the "alarm" box to start the alarm editor. In this program, all tags with alarms are switch tags; that is, if the value of the tag is 1, an alarm is triggered. After the tag database is created, the tag parameters can be linked to trend or historical reports, allowing the system to display the real-time data changes to the user in the form of curves or tables. The trend and historical reports in rsview32 are given in standard graphical form, and developers need to set the corresponding parameters. Parameters in the trend include time range, scan cycle, value range, data source, etc., while parameters in the historical report include the report's start time, time range, time interval, data source, variables, etc. 4.5 Screen Configuration The graphical editor provides a large number of graphical objects. Using these basic graphical objects and inserting external bitmaps, the flow chart screen and various operating condition screens of the chiller plant control system can be configured and designed. The monitoring main screen is the default main screen; it can be switched to various operating condition screens as needed. The main monitoring screen of the chiller plant control system consists of operating parameters, engineering parameters, status display, historical curves, historical alarms, communication tests, and report printing. Window switching is possible by selecting menu items on the main screen. The status display shows the connection status and operating principle of the equipment, pipelines, and valves of the entire chiller plant monitoring system. When the system is not running, the entire screen is static. Once the system is operational, the screen will display the current operating conditions, the opening of corresponding equipment and valves, the continuous flow of the medium in the pipelines, and the temperature, pressure, and flow rate detected on-site, displayed in their respective positions. The animations mentioned above are achieved through the animation connection function in the graphics editor. The chiller plant control system monitoring interface is shown in Figures 5 and 6. [align=center]Figure 5 Overview of Cold Storage Plant Operation[/align] [align=center]Figure 6 Internal Flowchart of Refrigeration Unit[/align] RSView32 can also use alarm graphic objects to configure alarm screens for equipment or process parameters. Equipment fault alarms are judged and corresponding protection actions are executed by the controller itself, but alarm information can be uploaded through the communication interface and displayed on the equipment alarm screen. Process parameter alarms are based on the alarm parameters set during database configuration. When an alarm occurs, the alarm screen displays the alarm time, alarm tag number, alarm category, current alarm value, and whether it has been confirmed, while simultaneously emitting an audible alarm and shutting down related equipment. Users can confirm the current alarm using the confirmation button to troubleshoot the fault. 5 Information Network Configuration Design 5.1 OPC Remote Communication Design The field upper-level monitoring station uses OPC to communicate with the monitoring station of the remote control production management center. OPC allows RSView32 to act as a client or server, enabling point-to-point communication between different RSView32 stations and other OPC servers. This system uses the on-site RSView32 supervisory control unit as the server and the RSView32 monitoring unit in the remote control management center as the client. The client uses the server's RSView32 command `rtdataserveron` to read the server's real-time tag values ​​via Ethernet and the command `rtdatawriteenable` to write the server's real-time tag values. The setup is as follows: For the server, select the "opc/dde server" checkbox on the "Startup" page in the "Startup" editor and issue the `rtdata serveron` command; for the client, configure the server as an OPC node, specify the OPC server name, define a tag in the tag database with the device as the data source, select an OPC node for this tag, and specify the tag value to be provided by the OPC entry. 5.2 Configure DCOM in the operating system of the main station Since OPC is an open and interoperable user interface standard based on the functional requirements of Microsoft's OLE/COM and DCOM technologies, DCOM (Distributed COM Configuration Properties) must be configured in the operating system of the main station first. The steps are as follows: (1) On the Windows 2000 operating interface, click "Start", select "Run", type dcomcnfg, and then click "OK" to enter "Distributed COM Configuration Properties" and set the "Application"; (2) Set the "Default Properties"; (3) Set the "Default Security Mechanism". 5.3 Configure the communication between the server and the client's rsview32 The computer name of the rsview32 server is coldstation, the name of the upper-level monitoring program is jyc, the computer name of the client is remote, and the name of the upper-level monitoring program is rmjyc1. First, configure the communication of the server rsview32, and then configure the communication of the client rsview32. After the program rmjyc1 runs, the rmjyc1 flag can read the jyc flag value to realize remote real-time monitoring. 6. System Monitoring Software Operation 6.1 On-site Supervisory Monitoring Program Operation The on-site supervisory computer of the chiller plant control system enters the rsview32 supervisory monitoring platform and opens the supervisory monitoring program named "jyc". In the project manager, click the "Run Mode" tab, and then click "Run Project" in the status bar. After the on-site supervisory monitoring program runs, it will run according to the pre-set running steps of the startup sequence. The main monitoring interface appears immediately after the program runs, as shown in Figure 7. In addition to the title and date and time, the main screen mainly includes 9 button icons, which represent 9 main functional modules. These buttons are also called the system's first-level menu. Clicking the corresponding button will take you to the corresponding functional module. Since the startup macro "st" contains the command "set autocontrol 0", the pump station is in manual control mode at this time. The operator can switch between manual control operation and automatic control operation. 6.2 Implementation of Remote Monitoring Program [align=center] Figure 7 Main Interface of Cold Storage Plant Monitoring[/align] The remote monitoring machine enters the rsview32 upper-level monitoring platform, opens the upper-level monitoring program named "rmjyc1", clicks the "Run Mode" tab in the project manager, and then clicks "Run Project" in the status bar. After the remote monitoring program runs, the main monitoring interface appears according to the startup sequence settings. Since the field monitoring program jyc executes the commands rtdataserveron and rtdatawriteenable when it starts, the remote monitoring program rmjyc1 can read the flag values ​​of the field monitoring program in real time and configure them into the same level of monitoring interfaces as the field monitoring program. If remote management is required, the remote control personnel and the field personnel can, like the on-site personnel, manually control the relevant operations of the cold storage plant, enter the relevant operation interface, and control the start and stop of the refrigeration units to achieve remote management. 7 Conclusion This article is based on the integrated design of a cold storage plant system using ControlNet bus technology and constructs a CIMS system for the cold storage plant. Based on the analysis of OPC technology and configuration software, an integrated software architecture for the entire chiller plant control system was constructed. The control network and information network of the chiller plant were configured and designed using RSView32 configuration software, realizing the integration of the control network and information network.