When solving any tasks of optimizing DTIPs for various purposes using the software tools, presented on this website, are required full initial data about the considered discrete processes. Actually, the entire array of input information for the task to be solved consists of two parts: constant (system Information) and variable (custom information). The system information characterizes objects and general properties of this class of processes, and the custom — varying properties and behavior of a specific process of this class, which are set by the user.
For example, when it comes about the task of optimizing investment in real estate, being solved by using the tools MLIS/MNIS IO 2.2 and ... RIO 1.0, the system information about this process contains data on objects of real estate available for purchase, and the custom — on sums of cash and credit funds allocated by the user to buy such objects. Another example is the task of optimizing expenses when shopping in online store (MLIS/MNIS EO 1.3 and ... NPO 1.0). Here, the system information includes data on goods, being sold in the store, and the custom — on that amount of money, which the user has allocated for their acquiring.
Initially it was assumed that input to the considered tools of initial information about optimizable DTIPs will take place in manual mode. However, such input in many cases proved to be very labor-intensive because of the large amount of required input data. Therefore, the creators of the eight of these tools, namely: MLIS/MNIS NPO 1.0, ... IO 2.2, ... EO 1.3, ... RIO 1.0, ... TO 1.6, ... PTPDO 1.2, MP OROR 1.1 and MP OOR 1.2 gone through the use of files of databases with system information on DTIPs, which are commonly created by other manufacturers for practical use in their own purposes. In order to such initial files can be connected to the above programs, are required two conditions:
1) they must somehow be acquired with the right of commercial use;
2) you should create programs-converters for automatic conversion of proprietary formats of these files to the formats for the pointed tools.
Note 1. Any of all these tools allows to enter the initial data of the tasks to be solved in two file formats: specialized (dat) and standard (excel). Since the latter is well-known format, it makes sense to convert in it the original database formats of optimizable discrete processes.
As for the other three tools on optimizing DTIPs (MLIS/MNIS MBO 1.0, ... GAO 2.2 and ... HIO 1.2), in them the system information on DTIPs is entered not by importing files of databases that are absent here, but manually together with other parameters of tasks to be solved.
Detailed analysis of the problem of using databases for DTIPs allowed to the founder of Technology make the following conclusions:
· for all eight instruments, working with databases (MLIS/MNIS NPO 1.0, ... IO 2.2, ... EO 1.3, ... RIO 1.0, ... TO 1.6, ... PTPDO 1.2, MP OROR 1.1 и MP OOR 1.2) is necessary to provide mass access to databases with system information on DTIPs, prepared by their third-party vendors, that the easiest thing to do is by placing them on the server together with the network processing center (NPC) when realizing the mass network services on the basis on these optimizing tools;
Note 2. For example, to solve the tasks of optimizing purchase and sale of securities (SC) using MMLIS/MNIS IO 2.2, you must have the forecast information about behavior of stock prices of SC for a quite long time interval, which presents a certain probability characteristic . A file with such qualitative characteristics should be formed (and periodically updated) by experienced specialists in this sphere, being available for all those traders which are going to solve such tasks by this tool. Otherwise, the tool will be useless for this purpose.
· for MLIS/MNIS TO 1.6 and ... PTPDO 1.2:
· the first of these tools requires databases of roads networks (DBRN1s) for cities for which calculations will be performed, and the second — DBRN1s and databases of routes networks (DBRN2s) for such cities;
· the cost of the above databases, presented in open file formats (usually this — universal format MapInfo) is very high, because the process of creating them is quite labor-intensive, and the developers of these databases are trying themselves to use them for commercial purposes and absolutely no interest in any competition in this field. In this connection, it seems appropriate not to buy such databases to organize the network service on solving the tasks on optimizing DTIPs of this purpose, but to share with their manufactures or owners;
· it makes sense to develop programs-converters for DBRN1s and DBRN2s only when will be known a particular supplier of them for the abovementioned tools;
· given the above, it is proposed to developers and owners of DBRN1s and DBRN2s the next two possible variants of cooperation in this sphere:
1) dealership on joint realization of the mass network services (through MNIS TO 1.6 and MNIS PTPDO 1.2) when DBRN1s and DBRN2s will be placed on a dedicated server with a protected set of the NPC program, and access to them will have only the dealer that guarantees himself confidentiality of these databases;
2) realization of the local network services on the website of the owner of DBRN1s and DBRN2s, when the latter will be in his exclusive possession. At that, NPC will be hosted on a virtual server, access to which have the owner of these NISs;
· for MLIS/MNIS EO 1.3 are required databases of goods and services for selling to the mass user by some objects of online trade or service industry (online stores and centers of health and entertainment), which are quite possible to buy. It is also proposed an alternative way to the mass use of this tool, when will be used not itself (in a local or network performance) but its optimization function that should be integrated into existing software of the respective object of trade or service industry;
· for the other three instruments which do not use databases (MLIS/MNIS MBO 1.0, ... GAO 2.2 and ... HIO 1.2) the system information on DTIPs is entered manually when setting parameters of new tasks, as well as by importing the input data of existing tasks.