Information Processing System and Information Processing Method

Abstract

To obtain cross-company information on parts incorporated into finished products.SOLUTION: An information processing system comprises: a product lifecycle management system that manages information related to finished products and parts that operate with the software and the scope of disclosure of data related to software contracted with provider companies that provide the parts to a manufacturing company that manufactures the finished products by incorporating the parts, at the manufacturing company; and a product lifecycle management system that manages the scope of disclosure and software-related data that is the data related to software at the provider company. The product lifecycle management system requests disclosure of the software-related data within the scope of disclosure to the product lifecycle management system. The product lifecycle management system transmits the requested software-related data to the product lifecycle management system if the requested software-related data is within the scope of disclosure.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] This disclosure relates to a technology for managing product-related information in an enterprise.

Background Art

[0002] Patent Document 1 discloses a traceability management method for managing the relationships of a plurality of work products in each process of software development. The method disclosed in Patent Document 1 grants access rights for each requirement in traceability management, sets public or non-public, and then performs access restriction.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Generally, various components are incorporated in a product, but not all of these components are manufactured by the product manufacturing enterprise that manufactures the product. The product manufacturing enterprise may procure components from a component providing enterprise that manufactures the components used in the product and manufacture a product incorporating the components. In addition, some components are a combination of hardware and software.

[0005]

[0006] One object of the present disclosure is to provide a technology capable of obtaining information on components incorporated in a finished product across enterprises.

Means for Solving the Problem

[0007] To achieve the above object, the information processing system of the present disclosure includes a first life cycle management system that manages information on the finished product and the component, and the scope of disclosure of data related to the software that is contracted with a providing company that provides the component to the manufacturing company, at a manufacturing company that manufactures a finished product by incorporating a component that operates with software; and a second life cycle management system that manages the scope of disclosure and software-related data that is data related to the software, at the providing company. The first life cycle management system requests the second life cycle management system to disclose the software-related data within the scope of disclosure, and the second life cycle management system transmits the requested software-related data to the first life cycle management system if the requested software-related data is within the scope of disclosure.

Effect of the Invention

[0008] According to the present disclosure, it becomes possible to obtain information on components incorporated in a finished product across enterprises.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Embodiments for Carrying Out the Invention

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0011] FIG. 1 is a diagram showing an example of a finished product and parts to which the information processing system is applied.

[0012] As shown in FIG. 1 for example, the information processing system is incorporated into a completed automobile 11 and used to manage an ECU (Electronic Control Unit) 12 which is a component for electronically controlling the automobile 11 with software 13. Thereby, it becomes possible to acquire software data on the management systems of the enterprises that provide the ECU and its software from the management system of the enterprise manufacturing the automobile.

[0013] FIG. 2 is a diagram showing an embodiment of the information processing system.

[0014] As shown in FIG. 2, the information processing system in this embodiment is a product life cycle management system 21 owned by a finished product manufacturer which is a manufacturing enterprise that manufactures a finished automobile 11 by incorporating an ECU 12 which is a component operating with software 13 like the automobile 11 shown in FIG. 1, and product life cycle management systems 31-1 to 31-n owned by component suppliers which are providing enterprises that manufacture components and supply them to the finished product manufacturer, and are configured to be connectable via a communication line 91 such as the Internet. The finished product manufacturer is called an OEM. Note that it is preferable that the product life cycle management systems 31-1 to 31-n are provided in the number corresponding to the number of enterprises manufacturing components incorporated into the finished product manufactured by the product life cycle management system 21, but it may be only a part of the enterprises manufacturing components incorporated into the finished product manufactured by the product life cycle management system 21.

[0015] The product life cycle management system 21 (first life cycle management system) manages information on the finished product and the components incorporated therein, and the disclosure scope of data on the software contracted with the component supplier, and requests the product life cycle management systems 31-1 to 31-n to disclose software-related data within the disclosure scope.

[0016] The product life cycle management system 31-1 to 31-n (the second life cycle management system) manages the disclosure scope of data related to software contracted with a finished product manufacturer and software-related data which is data related to software of components manufactured in-house. If the software-related data requested from the product life cycle management system 21 is within the disclosure scope of data related to software contracted with the finished product manufacturer, the requested software-related data is transmitted to the product life cycle management system 21.

[0017] By configuring in this way, in a configuration where a manufacturing company procures components and software from a supplying company to manufacture a finished product, it becomes possible to obtain information across companies.

[0018] Figure 3 is a block diagram showing the configuration of the product life cycle management system 21 shown in Figure 2.

[0019] As shown in Figure 3, the product life cycle management system 21 shown in Figure 2 has a specification information management system 22, a product information management system 23, a procurement system 24, a contract information management system 25, a software management system 26, an impact scope analysis system 27, and a communication device 28.

[0020] The specification information management system 22 manages specification information management data in which, for each specification related to a finished product, component identification information indicating components incorporated in the finished product and software identification information indicating software operating on the components are associated with each other.

[0021] The product information management system 23 (the first product information management department) manages first product information management data in which finished product identification information indicating a finished product and the part name of a component incorporated in the finished product and component identification information indicating the component are associated with each other.

[0022] The procurement system 24 manages procurement management data in which software identification information and supplying company information identifying a supplying company of the software are associated with each other.

[0023] The contract information management system 25 (the first contract information management department) manages the first contract information management data indicating the contract disclosure level showing the disclosure range regarding the software contracted with each of the providing companies having the product life cycle management systems 31-1 to 31-n.

[0024] The software management system 26 manages information on in-house developed software and simple management information on externally procured software.

[0025] The impact scope analysis system 27 is configured to be able to access the first product information management data managed by the product information management system 23, the specification information management data managed by the specification information management system 22, the procurement management data managed by the procurement system 24, and the first contract information management data managed by the contract information management system 25. When a part name is specified, it accesses the first product information management data, acquires the part identification information corresponding to the specified part name, then accesses the specification information management data, acquires the software identification information corresponding to the acquired part identification information, then accesses the procurement management data, acquires the providing company information associated with the acquired software identification information, then accesses the contract information management data, acquires the contract disclosure level of the part supplier indicated by the acquired providing company information, and then transmits, via the communication device 28, a request to request disclosure of software-related data within the disclosure range of the acquired contract disclosure level to the product life cycle management system possessed by the part supplier. Further, the impact scope analysis system 27 displays the specified part name and the software-related data transmitted from the product life cycle management systems 31-1 to 31-n.

[0026] FIG. 4 is a block diagram showing the configuration of the product life cycle management systems 31-1 to 31-n shown in FIG. 2.

[0027] As shown in FIG. 4, the product life cycle management systems 31-1 to 31-n shown in FIG. 2 include a specification information management system 32, a product information management system 33, a procurement system 34, a contract information management system 35, a software management system 36, an impact scope analysis system 37, and a communication device 38.

[0028] The specification information management system 32 manages specification data regarding the detailed specifications of parts manufactured in-house.

[0029] The product information management system 33 (second product information management department) manages second product information management data that associates software identification information of software with version information of the provided software.

[0030] The procurement system 34 manages procurement data related to parts manufactured in-house.

[0031] The contract information management system 35 (second contract information management department) manages second contract information management data indicating a contract disclosure level showing the disclosure scope regarding software contracted with a finished product manufacturer having the product life cycle management system 21.

[0032] The software management system 36 manages software management data that associates, for each software and its version, software identification information, version information indicating the version, and software-related data at a level that can be disclosed regarding the software.

[0033] The influence range analysis system 37 (second influence range analysis unit) is configured to be able to access the second contract information management data managed by the contract information management system 35 and the software-related data managed by the software management system 36. When a request sent from the product life cycle management system 21 is received via the communication device 38, it accesses the second contract information management data. If the software-related data requested by the received request is within the disclosure range of the finished product manufacturer corresponding to the product life cycle management system 21 that is the source of the request, it acquires the version information of the provided software from the second product information management data, acquires the software-related data regarding the software from the software management data, and transmits it to the product life cycle management system 21 of the finished product manufacturer via the communication device 38.

[0034] Figure 5 is a block diagram showing the hardware configuration of each system shown in Figures 3 and 4.

[0035] As shown in Figure 5, the hardware configuration of each system shown in Figures 3 and 4 is such that a processor 41, a main memory 42, a storage device 43, a communication device 44, an input device 45, and a display device 46 are connected via a bus 47.

[0036] The processor 41 realizes each function shown in Figures 3 and 4 by executing a software program read from the storage device 43 into the main memory 42.

[0037] The communication device 44 is for connecting to other devices.

[0038] The input device 45 is for inputting information into various tables set in the storage device 43.

[0039] The display device 46 is for displaying and outputting the execution result in the processor 41.

[0040] Next, an information processing method in the information processing system configured as described above will be explained.

[0041] FIG. 6 is a flowchart for explaining an information processing method in the information processing system shown in FIGS. 2 and 3.

[0042] When a defect occurs in a component incorporated in a finished product manufactured by a finished product manufacturer having a product life cycle management system 21, when the part name of the defective component is input to the impact range analysis system 27 of the product life cycle management system 21 (step S101), the impact range analysis system 27 first accesses the product information management data managed by the product information management system 23, and uses the input part name to search for and obtain the part number serving as the part identification information of the component from the product information management data (step S102).

[0043] FIG. 7 is a diagram showing an example of product information management data managed by the product information management system 23 shown in FIG. 2.

[0044] As shown in FIG. 7, the product information management system 23 shown in FIG. 2 manages product information management data in which, for each finished product, finished product identification information indicating the finished product, a product name and a function name indicating its function, the part name of a component incorporated in the finished product, and its part number are associated with each other. Therefore, the impact range analysis system 27 can access the product information management data managed by the product information management system 23 and search for and obtain the part number serving as the part identification information of the component from the product information management data using the input part name.

[0045] Next, the impact range analysis system 27 accesses the specification information management data managed by the specification information management system 22, and uses the part number obtained in step S102 to search for and obtain the software ID serving as the software identification information corresponding to the part number from the specification information management data (step S103).

[0046] FIG. 8 is a diagram showing an example of specification information management data managed by the specification information management system 22 shown in FIG. 2.

[0047] As shown in FIG. 8, for each specification related to a finished product in the specification information management system 22 shown in FIG. 2, a specification ID indicating the specification is assigned, and to this specification ID, its classification, the content of the specification, related regulations indicating the regulations to be complied with, a part number, and a software ID which is software identification information indicating the software operating on the part are associated and the specification information management data is managed. Therefore, the impact range analysis system 27 can search for and obtain the software ID corresponding to the part number from the specification information management data using the part number acquired in step S102.

[0048] Next, the impact range analysis system 27 accesses the procurement management data managed by the procurement system 24, and searches for and obtains the name of the contractor which is the supplier information corresponding to the software ID from the procurement management data using the software ID acquired in step S103 (step S104).

[0049] FIG. 9 is a diagram showing an example of procurement management data managed by the procurement system 24 shown in FIG. 2.

[0050] As shown in FIG. 9, in the procurement system 24 shown in FIG. 2, for each part to be procured, a procurement ID for specifying the part procurement is assigned, and to this procurement ID, a software ID as a procurement item ID and the name of the contractor which is the procurement destination of the part are associated and the procurement management data is managed. Therefore, the impact range analysis system 27 can search for and obtain the name of the supplier corresponding to the software ID from the procurement management data using the software ID acquired in step S103.

[0051] Next, the scope of influence analysis system 27 accesses the contract information management data managed by the contract information management system 25, searches for the contract information corresponding to the company name from the contract information management data using the name of the contract partner obtained in step S104, and acquires the contract disclosure level included in the contract information (step S105).

[0052] FIG. 10 is a diagram showing an example of the contract information management data managed by the contract information management system 25 shown in FIG. 2.

[0053] As shown in FIG. 10, the contract information management system 25 shown in FIG. 2 manages contract information management data in which a contract ID for identifying a contract is assigned to each contract, and the name of the contract partner and the disclosure range that is the contract disclosure level for that contract partner are associated with this contract ID. Therefore, the scope of influence analysis system 27 can search for and acquire the disclosure range that is the contract disclosure level corresponding to the name of the contract partner from the contract information management data using the name of the contract partner obtained in step S104.

[0054] In the disclosure range obtained in step S105, if the software of the component of the component name input in step S101 is discloseable (step S106), after the other necessary information is input as supplementary information if there is any other necessary information (step S107), the scope of influence analysis system 27 requests the product life cycle management system (for example, the product life cycle management system 31-1) of the component supplier that manufactures the component to disclose the software-related data within the disclosure range of the contract disclosure level obtained in step S105 via the communication device 28 (step S108).

[0055] When the product life cycle management system 31-1 receives the request sent from the product life cycle management system 21 in step S108, the impact scope analysis system 37 of the product life cycle management system 31-1 first accesses the contract information management data managed by the contract information management system 35, and determines whether the requested software-related data can be disclosed for the finished product manufacturer that has sent a request to disclose the software-related data (step S109).

[0056] FIG. 11 is a diagram showing an example of the contract information management data managed by the contract information management system 35 shown in FIG. 3.

[0057] As shown in FIG. 11, the contract information management system 35 shown in FIG. 3 manages contract information management data in which a contract ID for identifying a contract is assigned to each contract, and the name of the contract partner and the disclosable range, which is the contract disclosure level for that contract partner, are associated with this contract ID. Therefore, the impact scope analysis system 37 can determine whether the requested software-related data is within the disclosable range for the company that has sent a request to disclose the software-related data in step S108.

[0058] If the requested software-related data is within the disclosable range for the company that has sent a request to disclose the software-related data in step S108, the impact scope analysis system 37 accesses the product information management data managed by the product information management system 33, and acquires the version information of the provided software from the product information management data (step S110).

[0059] FIG. 12 is a diagram showing an example of the product information management data managed by the product information management system 33 shown in FIG. 3.

[0060] As shown in Fig. 12, the product information management system 33 shown in Fig. 3 manages product information management data in which a software ID for identifying software is assigned to the software provided to the finished product manufacturer, and version information of the software currently provided to the finished product manufacturer is associated with this software ID. Also, in the product information management data, the name of the contract partner that provided the software may be associated with the software ID. Thereby, the impact scope analysis system 37 can acquire the version information of the software currently provided to the company that has sent a request to disclose software-related data in step S108 from the product information management data.

[0061] Next, the impact scope analysis system 37 accesses the software management data managed by the software management system 36, and searches for and acquires the software-related data of the software from the software management data based on the software ID and the version information acquired in step S110 (step S111).

[0062] Fig. 13 is a diagram showing an example of the software management data managed by the software management system 36 shown in Fig. 3.

[0063] As shown in FIG. 13, the software management system 36 shown in FIG. 3 manages software management data in which a software ID for identifying software is assigned to the software provided to the finished product manufacturer, and the version information of the software currently provided to the finished product manufacturer and the source code, which is software-related data, are associated with this software ID. Therefore, the impact range analysis system 37 can search for and acquire software-related data of the software from the software management data by using the version information of the software acquired in step S110. Note that the software-related data may include not only the source code of the software but also at least one of the source code of the software and the internal structure information. In that case, if the disclosure scope in the contract includes those that allow disclosure of both the source code and the internal structure information, those that do not allow disclosure of the source code but allow disclosure of the internal structure information, and those that do not allow disclosure of either the source code or the internal structure information, the contract determines whether the source code and the internal structure information of the software can be disclosed, and flexible data disclosure can be realized between companies according to the contract.

[0064] Thereafter, the impact range analysis system 37 transmits the software-related data acquired from the software management data in step S111 to the product life cycle management system of the finished product manufacturer via the communication device 38 (step S112).

[0065] When the impact range analysis system 27 receives the software-related data transmitted from the impact range analysis system 37 of the product life cycle management system 31 via the communication device 28 of the product life cycle management system 21, the impact range analysis system 27 displays the part name input in step S101 and the software-related data transmitted from the product life cycle management system 31-1.

[0066] Through the above series of processes, it becomes possible for the finished product manufacturer to request and obtain software-related data of the components incorporated in the finished product from the component suppliers.

[0067] In addition, the product life cycle management systems 31-1 to 31-n of the component suppliers record software-related data for each version of the software in the software management system 36, and by transmitting the software-related data regarding the version of the software provided to the finished product manufacturer to the product life cycle management system 21 of the finished product manufacturer, the finished product manufacturer can easily obtain the data regarding the version of the software applied to the components incorporated in the finished product.

[0068] Also, both the product life cycle management systems 21 and 31 manage data regarding contracts including the disclosure scope. The product life cycle management system 21 confirms whether the software-related data can be disclosed based on the contract with the component suppliers having the product life cycle management systems 31-1 to 31-n. If it can be disclosed, it requests the software-related data from the product life cycle management systems 31-1 to 31-n. The product life cycle management systems 31-1 to 31-n receive the request from the product life cycle management system 21 and confirm whether the software-related data can be disclosed based on the contract with the finished product manufacturer having the product life cycle management systems 31-1 to 31-n. If it can be disclosed, it transmits the software-related data to the product life cycle management system 21. By managing the disclosure scope by contract on both sides of the manufacturing enterprise and the providing enterprise and confirming the contract on both sides when disclosing the software-related data, it is possible to ensure disclosure within the contracted scope.

[0069] Also, as described above, since the specification information management system 22 of the product life cycle management system 21 possessed by the finished product manufacturer manages related regulation information indicating regulations to be complied with regarding the specifications of parts in the managed specification information management data, the influence range analysis system 27 accesses the specification information management data to further obtain the related regulation information corresponding to the part identification information, and may be configured to display the obtained related regulation information together with the part name input in step S101 and the software-related data transmitted from the part supplier. Thereby, it is possible to display the information on the related regulations together with the software-related data obtained by the manufacturing company from the providing company across companies.

[0070] Also, as described above, in the product information management data managed by the product information management system 23, since the function name indicating the function of the finished product is also associated with the part number of the parts incorporated in the finished product, when the function name is specified, the influence range analysis system 27 of the product life cycle management system 21 possessed by the finished product manufacturer accesses the product information management data managed by the product information management system 23, obtains the part identification information of the part corresponding to the specified function name, obtains the software identification information corresponding to the obtained part identification information, obtains the providing company information indicating the company that provides the software indicated by the obtained software identification information, obtains the contract disclosure level of the providing company indicated by the obtained providing company information, and sends a request to request the disclosure of data regarding the software within the disclosure range of the obtained contract disclosure level to the product life cycle management systems 31-1 to 31-n of the part suppliers indicated by the providing company information. In that case, it is possible to specify the influence range from the function name and obtain information on the software of the related parts.

[0071] The above-described embodiments are examples for explaining the present invention, and are not intended to limit the scope of the present invention only to those embodiments. Those skilled in the art can implement the present invention in various other modes without departing from the scope of the present invention.

Explanation of Reference Numerals

[0072] 11…Automobile, 12…ECU, 13…Software, 21…Product Life Cycle Management System (Finished Product Manufacturer), 22, 32…Specification Information Management System, 23, 33…Product Information Management System, 24, 34…Procurement System, 25, 35…Contract Information Management System, 26, 36…Software Management System, 27, 37…Impact Scope Analysis System, 28, 38…Communication Device, 31…Product Life Cycle Management System (Component Supplier), 41…Processor, 42…Main Memory, 43…Storage Device, 44…Communication Device, 45…Input Device, 46…Display Device, 47…Bus, 91…Communication Line

Claims

1. In a manufacturing company that manufactures a finished product by incorporating components that operate with software, a first life cycle management system that manages information regarding the finished product and the components, and the scope of disclosure of data regarding the software that has a contract with the providing company that provides the components to the manufacturing company; In the providing company, a second life cycle management system that manages the scope of disclosure and software-related data that is data regarding the software; having; The first life cycle management system requests the second life cycle management system to disclose the software-related data within the scope of disclosure; If the requested software-related data is within the scope of disclosure, the second life cycle management system transmits the software-related data to the first life cycle management system; An information processing system.

2. The second life cycle management system records the software-related data for each version of the software, and transmits the software-related data regarding the version of the software provided to the manufacturing company to the first life cycle management system; The information processing system according to Claim 1.

3. The first life cycle management system and the second life cycle management system both manage data regarding a contract including the scope of disclosure; Based on the contract, the first life cycle management system checks whether the software-related data is disclosable, and if it is disclosable, requests the second life cycle management system for the software-related data; Upon receiving a request from the first life cycle management system, the second life cycle management system checks whether the software-related data is disclosable based on the contract, and if it is disclosable, transmits the software-related data to the first life cycle management system; The information processing system according to Claim 1.

4. The software-related data includes at least one of the source code of the software and internal structure information; The disclosure scope in the contract includes those that allow disclosure of both the source code and the internal structure information, those that do not allow disclosure of the source code but allow disclosure of the internal structure information, and those that do not allow disclosure of either the source code or the internal structure information. The information processing system according to claim 1.

5. The first life cycle management system A first product information management unit that manages first product information management data in which the finished product identification information indicating the finished product is associated with the part name of the parts incorporated in the finished product and the part identification information indicating the parts; A specification information management unit that manages specification information management data in which, for each specification related to the finished product, the part identification information is associated with software identification information indicating the software operating on the part; A procurement management unit that manages procurement management data in which the software identification information is associated with the provider information identifying the software provider; A first contract information management unit that manages first contract information management data indicating the contract disclosure level indicating the disclosure scope regarding the software contracted with the provider; A first impact scope analysis unit that can access the first product information management data, the specification information management data, the procurement management data, and the first contract information management data, and manages the life cycle including the manufacture and operation of the finished product. The second life cycle management system A second product information management unit that manages second product information management data in which the software identification information of the software is associated with the version information of the provided software; A second contract information management unit that manages second contract information management data indicating the contract disclosure level indicating the disclosure scope regarding the software contracted with the manufacturing company that provides the parts; A software management unit that manages software management data in which, for each software and its version, the software identification information, the version information indicating the version, and software-related data at a disclosure level that can be disclosed for the software are associated; A second impact scope analysis unit that can access the second contract information management data and the software-related data, and manages the life cycle including the development, provision, and operation of the parts and software. When the first impact range analysis unit is specified with a component name, it accesses the first product information management data to obtain component identification information corresponding to the specified component name, accesses the specification information management data to obtain software identification information corresponding to the obtained component identification information, accesses the procurement management data to obtain the supplier information associated with the obtained software identification information, accesses the first contract information management data to obtain the contract disclosure level of the supplier indicated by the obtained supplier information, and sends a request to the second life cycle management system of the supplier to request disclosure of software-related data within the disclosure range of the obtained contract disclosure level. The second impact range analysis unit receives the request, accesses the second contract information management data, and if the software-related data requested in the request is within the disclosure range of the manufacturing company corresponding to the first life cycle management system that is the source of the request, obtains the version information of the provided software from the second product information management data, obtains software-related data regarding the software from the software management data, and sends it to the first life cycle management system of the manufacturing company. The first impact range analysis unit displays the specified component name and the software-related data sent from the second impact range analysis unit. The information processing system according to claim 1.

6. The specification information management unit further manages, in the specification information management data, related regulation information indicating regulations to be complied with regarding the specification. The first impact range analysis unit further accesses the specification information management data to obtain related regulation information corresponding to the component identification information, and displays the obtained related regulation information together with the specified component name and the software-related data. The information processing system according to claim 5.

7. The finished product is an automobile and the component is an ECU. The information processing system according to claim 5.

8. The first product information management unit further associates, in the first product information management data, a function name indicating the function of the finished product related to the component. The first impact range analysis unit When specified with a function name, it accesses the first product information management data to obtain component identification information of the component corresponding to the function name. Obtain software identification information corresponding to the acquired component identification information, Obtain provider company information indicating the company that provides the software indicated by the acquired software identification information, Obtain the contract disclosure level of the provider company indicated by the acquired provider company information, Send a request to the second life cycle management system of the provider company indicated by the provider company information to disclose data related to the software within the disclosure scope of the acquired contract disclosure level, The information processing system according to claim 5.

9. A first life cycle management system, which is an information processing system of a manufacturing company that manufactures a finished product by incorporating components operating with software, manages information related to the finished product and the components, and the disclosure scope of data related to the software contracted with a provider company that provides the components to the manufacturing company, A second life cycle management system, which is the information processing system of the provider company, manages the disclosure scope and software-related data that is data related to the software, The first life cycle management system requests the second life cycle management system to disclose software-related data within the disclosure scope, If the requested software-related data is within the disclosure scope, the second life cycle management system transmits the software-related data to the first life cycle management system, Information processing method.

Images