Information processing system

Abstract

When a malfunction occurs, we track the history of the problem. [Solution] The information processing system 100 executes multiple scripts in stages. The execution history management unit 18 stores the execution history of each script, associating the identification data of each script with the input / output data at the time each script was executed.

Description

Technical Field

[0001] The present disclosure relates to an information processing system that sequentially executes a plurality of scripts.

Background Art

[0002] In various product developments, such as automobile development, an ETL tool is used to create new value by extracting some data from various measurement data (Extract), performing various conversion processes on the extracted data (Transform), and loading the converted data (Load).

[0003] Patent Document 1 shows that in a process of executing one or more scripts, account information of the script to be executed is saved, and when the account information is changed, the changed account information is memorized. Thereby, it is possible to check the account information when executing the script, and it is said that security can be improved.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Patent Document 3

Summary of the Invention

Problems to be Solved by the Invention

[0005] To track the history of product development, there is a need to accurately trace all previous changes and evolutions. For this reason, one might consider managing executed script information and its usage history together. However, in this case, both the management of the script itself (including changes to the script) and its execution history must be managed, which complicates the management system and could make it impossible to track history information in the event of a system error or malfunction in script management. [Means for solving the problem]

[0006] The information processing system relating to this disclosure is an information processing system that executes multiple scripts in stages, and stores the execution history of each script, associating the identification data of each script with the input / output data at the time each script was executed.

[0007] The aforementioned multiple scripts may include scripts for three stages: the extraction stage, the conversion stage, and the loading stage. [Effects of the Invention]

[0008] Even in the event of system errors or malfunctions in script management, historical information can be tracked. [Brief explanation of the drawing]

[0009] [Figure 1] This is a block diagram showing the overall configuration of the information processing system related to this disclosure. [Figure 2] This diagram shows an overview of the processing in the ETL (Extract, Streamlining, Load) processing unit during vehicle development. [Figure 3] This flowchart shows the processing in the ETL (Effective Toll Collection) section. [Figure 4] This diagram illustrates an example of the processing at each stage in the ETL processing unit. [Modes for carrying out the invention]

[0010] The embodiments of this disclosure will be described below with reference to the drawings. The embodiments described below are not limiting to this disclosure, and configurations formed by selectively combining multiple examples are also included in this disclosure.

[0011] "System Configuration" Figure 1 is a block diagram showing the overall configuration of the information processing system 100 related to this disclosure.

[0012] Various data from multiple data sources are input through the input unit 10. The input data is supplied to the ETL processing unit 12. The ETL processing unit 12 uses scripts to perform extraction, transformation, and loading operations on the input data, and supplies the resulting insights to the output unit 14. The output unit 14 outputs the results in various formats.

[0013] The scripts to be executed by the ETL processing unit 12 are stored in multiple script storage units 16, and the ETL processing unit 12 reads and executes the corresponding script as processing is performed. Furthermore, the multiple script storage units 16 may be located in different locations.

[0014] Furthermore, an execution history management unit 18 is connected to the ETL processing unit 12, and this execution history management unit 18 stores the script execution history of each script. The execution history management unit 18 also supplies the stored script execution history to the ETL processing unit 12 in accordance with requests from the ETL processing unit 12.

[0015] The execution history management unit 18 does not store the script itself, but rather stores identification data that identifies the script, i.e., the script ID, linked to the executed input data, output data, and their property information. Furthermore, it also stores the processing method for script execution linked to the script ID.

[0016] Figure 2 is a diagram showing an overview of the processing in the ETL processing unit 12 in vehicle development. First layer: In the data generation layer, data input by the input unit 10 is generated. Data is generated at each stage from product planning → system design → detailed design → prototype production → functional evaluation → component evaluation → vehicle evaluation → production → customer use.

[0017] Second layer: In the data management layer, the data generated in the first layer is classified and extracted. In this example, it is classified into requirements, block diagrams, specifications, 1D models, 2D CAD, 3D CAE, parts lists, configuration management, compliance constants, measurement results, factories, on-road driving, etc.

[0018] Third layer: In the data linking layer, for the data for each type of classification obtained in the second layer, the data is linked to generate new data as processing results.

[0019] Fourth layer: In the data utilization layer, using the processing results, provide various data search and viewing interfaces, utilize them in the integrated model, or "visualize" the processing results. Also, it is advisable to enable cross-search for various processing results.

[0020] Figure 3 is a flowchart showing the processing in the ETL processing unit 12. Data is extracted from a plurality of target systems (S11). S11 is the extraction (Extract) stage. Then, the extracted data is transformed (S12). Also, the transformed data is combined (S13) to generate new processed data (S14). S12 - S14 are the transformation (Transform) stage. Then, multiple processed data are read in (S15) to generate new insights (S16). S15 - S16 are the loading (Load) stage. The processing of each of the above stages may be performed by the stored scripts.

[0021] Figure 4 illustrates an example of the processing at each stage in the ETL processing unit 12. In this example, data for multiple product specifications is stored in the specifications database. This is done by using a predetermined script to extract data from various locations and store the extracted data in the specifications database. In this example, the selection of the script to be executed is done by a human.

[0022] Furthermore, product models created at various locations are stored in the model management database. In this example, the selection of models is done manually.

[0023] Based on various specifications stored in the specifications database, multiple performance calculations are performed—four in this example—and the results are stored in the results management database. Specifications data from the specifications database is supplied to each performance calculation via script execution. It is recommended to perform multiple performance calculations in a single batch.

[0024] The results management database stores multiple calculation results, including the parameters determined from those results. These new parameters are then returned to the parameters database. The contents of the parameters database should be made accessible to users.

[0025] Furthermore, various models from the model management database are supplied to their corresponding individual calculations. Data from the specifications database is then supplied to each individual calculation by the execution of a script. Consequently, each individual calculation performs calculations based on the supplied specifications, and the results are supplied to the results management database by the execution of a script.

[0026] Individual calculations can be performed on various performance metrics, such as torque maps, noise, vibration, and driving speed.

[0027] Performance specifications are generated from the result data in the results management database through the execution of a script. In other words, a performance specification for a new product is generated by reading various results. During the generation of this performance specification, specifications from the specifications database are supplied via the script and used for generation.

[0028] Furthermore, result data (various characteristics) from the results management database is supplied to the characteristics management database via a script. Reading data from the characteristics management database generates a list of target performance. The performance plan and target performance generated in this way are then used for product planning and other purposes.

[0029] Here, we will examine three scripts and explain how their execution history is used.

[0030] Script SC1 is a script that extracts specifications from the specifications database and supplies them to individual calculation 4. The execution history management unit 18 in Figure 1 stores the input / output data, data profile, and processing method for the execution of this script, linked to the script ID. In other words, it manages the execution history of the conversion scripts from the specifications management database to each individual calculation tool. This makes it possible to know which script was used to output which data from the input specifications database. Furthermore, since the execution history management unit 18 on the history management side has information on the input specifications and the conversion results, as well as the status of the script execution, it is possible to instantly determine whether the conversion was performed correctly. Similarly, the execution history of scripts that supply data to individual calculations 1-3 is also stored, allowing for similar use.

[0031] Script SC2 converts and outputs the target characteristics calculated from the results of Individual Calculation 1. By managing the execution history of this script, the method for calculating the target characteristics can be managed, and all data used in calculating the target characteristics and their change history can be obtained. Similarly, the execution history of scripts that process data from Individual Calculations 1-3 is also stored, allowing for similar use.

[0032] Script SC3 generates a performance plan, which is the final deliverable of the various specification data in the specification database. It may also generate various other specifications. When combined with an automated execution tool, Script SC3 seamlessly performs the conversion, calculation, and post-processing of input specifications without human intervention, leading to the final deliverable. This eliminates areas where human error can occur and allows for accurate tracking of the development process. It is also effective as a platform for generating and managing development evidence.

[0033] Thus, according to the information processing system described in this disclosure, only the execution history of scripts that perform extraction, transformation, and loading operations is centrally managed. In other words, the execution history of scripts is recorded, linked to the script execution ID, input / output data, and processing method. As a result, even if multiple combinations of source data are used, and even if the data is modified many times, its changes can be tracked. Furthermore, it is possible to accurately track calculations, actual device evaluations, and development history across product development projects, regardless of where the scripts are managed.

[0034] In this way, the script itself is considered a piece of data, and the execution history is centrally managed. It also accepts script execution instructions and stores status information such as errors. As a result, the system is lightweight, centralizes the management of only the history, tracks real-time changes such as monitoring, and helps diversify risks in the event of system failures.

[0035] Therefore, the management of data processing tools and traceability when processing methods change are ensured. In order to track the history of product development, it is necessary to accurately track the changes that led to the final data. According to this embodiment, the input and output data before and after the change, the property information of each data, and the information of the execution script used when converting the data are stored, so the history of development can be tracked. [Explanation of symbols]

[0036] 10 Input unit, 12 ETL processing unit, 14 Output unit, 16 Script storage unit, 18 Execution history management unit. 100 Information processing system.

Claims

[Claim 1] An information processing system that executes multiple scripts in stages, For the execution history of each script, the identification data of each script is stored in association with the input and output data at the time each script was executed. Information processing system.

Images