INTOOLS terminal wiring diagram – an efficient solution
Thread Content
In large-scale chemical engineering projects, creating wiring diagrams for instruments often takes a lot of time; by utilizing secondary development of INTOOLS software, it is possible to import such wiring diagrams efficiently. The INTOOLS software is developed based on relational databases, and SQL statements can be used to insert and modify data in the database. Importing INTOOLS terminal diagrams in the form of SQL statements offers efficiency, accuracy, and ease of use.
This post is part of a series; once it’s completed and published, it can be shared with everyone
SPI is really top-notch. Pass by using EXCEL. . .
Just as a side note, the idea is good, but reliability issues often arise. When I was working on this, I also considered filling data into Orical through external writing, but I later found that the risks were too high and problems would arise very easily. Since it is a manual operation that is not under control, the data you import may not comply with the database’s rules – for example, there might be spaces added before or after the data, and all sorts of unusual situations can occur. As the data is imported (usually using EXCEL), its normalization cannot be guaranteed, which can easily lead to damage to the database. Moreover, once such problems arise, they are difficult to detect; you will only notice errors when trying to use the SPI connection function, without being able to identify exactly what the issue is. Therefore, for software that is highly specialized and closed-off like this, it is not recommended to use external methods for data insertion. You can use the data already present in the database, but writing new data into it is not advised.
Hello, thank you for the message. At this stage, tests have shown that writing to the database using SQL poses no problems. The key lies in analyzing the structure of the INTOOLS database, understanding the internal relationships between various parameters, as well as how the different data elements interact with each other.
Development can be divided into 5 stages: 1. Analyze the database structure and select the required database tables. 2. Analyze the selected database tables, clarify various parameter details, determine the parameter format for SQL statements, as well as gather all the necessary information for accessing those database tables. 3. Formulate rules for the assignment of labels, cables, and central control systems in accordance with industry standards. 4. Embed the established rules into the program, and generate SQL statements that can be directly written to the database in batches, following the SQL statement format defined in the second phase.
First, it is necessary to explain the traditional CAD drawing method. While this method is easy to learn, it requires manual creation of the framework and input of various details, which results in low efficiency. However, in large-scale projects, tag numbers that number in the thousands often require a great deal of manual effort, failing to meet production demands.
In the first phase, the database structure is analyzed. After frequently using INTOOLS, one becomes more familiar with the database structure, so no further explanation is needed here. Additionally, confidentiality issues are involved; please understand this. In the second phase, after determining the structure of the INTOOLS database, it is necessary to define the format for individual statements. For example, writing information about a cable, a junction box, a terminal, etc., each requires a specific statement for insertion. Once these statements are established in this phase, they will be processed in batches in the fourth phase.
In the third stage, the focus is on establishing various rules in line with the standards of this industry, including rules regarding cables, junction boxes, the control panel, and so on. The fourth phase is the process of integrating the second and third phases, during which relevant procedures are developed as needed.