JP2001306120A - Information management system for manufacturing industry - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem that users have to change an application for each file style when they refer to manufacturing information (information related to manufacturing procedures) which is made in plural file styles (DXF, CVS, HTML) by various groups and are registered/served by information system using WWW servers/clients environment. SOLUTION: All manufacturing information can be referred to with a single application by converting manufacturing information made by plural file styles to PDF file style and by providing a means for registering the information to WWW servers with the single file style.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information management system in the manufacturing industry, and in particular, converts information for manufacturing created in a plurality of file formats into a specific file format, and W
By registering on the WW (World Wide Web) server,
Refer to all manufacturing information using a single application.

[0002]

2. Description of the Related Art In the manufacturing industry, products to be produced are different, but a procedure for manufacturing is determined, and production is performed by observing the procedures. This procedure is created in the form of a document or data as information for manufacturing (hereinafter, manufacturing information).
Manufacturing information is not limited to procedures, but also information for parts inspection, data for automatic assembly equipment, procedures for testing assembled products and the necessary test programs, recording of these test results, training of workers There are records and qualification records, and various information is created by various departments.

[0003] These manufacturing information must be updated to the latest information in response to frequently occurring changes in design information, parts information, production resources, and the like, and in response to repair requests from customers. Therefore, it is necessary to manage to keep the information before update.

[0004] In the server / client system, the manufacturing information is registered in a database managed by the server, and the application corresponding to the creation format of the manufacturing information from each client machine.
For example, a CAD application refers to a drawing file created in the DXF format (Data eXchange Format).

[0005]

As described above, since various kinds of information are conventionally created by various departments in manufacturing information, the file format of the information is, for example, DXF, CS, etc.
V (Comma Separated Value), HTML (Hyper Text
Markup Language), and users who use such information have to change applications depending on the file format of manufacturing information, which is very troublesome.

[0006]

SUMMARY OF THE INVENTION The present invention has been made in consideration of the above problems, and has been made in consideration of a WWW server and a WW.
An information management system that uses a W client to register and provide information on manufacturing number and version number, registrant name, registrant's department name, revised content, and comment as manufacturing information and its management data in the manufacturing industry. By providing means for converting manufacturing information created in a plurality of file formats into a specific file format and integrating it into one file and registering it in a WWW server, all manufacturing information can be obtained using a single application. See

[0007]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS (1) Using a WWW server and a WWW client, information on management information, edition number, registrant name, registrant's department name, revised content, comment as production information and its management data The information management system for registering and providing a file includes a means for converting manufacturing information created in a plurality of file formats into a specific file format and integrating it into one file and registering it in a WWW server. It is possible to refer to only a single application without referencing across multiple viewer applications.

[0008] (2) In the information management system described in (1), manufacturing information created in a plurality of file formats;
A means for storing a specific file obtained by converting them into a specific file format and integrating them into one file as a data set in a storage unit for storing manufacturing information, and a storage unit for storing manufacturing information. Means for acquiring manufacturing information of the product, and converting and converting the manufacturing information and its specific file format into one file into one data set, thereby referring to and extracting the manufacturing information. Operability can be improved.

(3) In the information management system described in (2), when obtaining a file of manufacturing information from a storage unit for storing manufacturing information, means for obtaining the file with the same file name as when storing the file is provided. When the file name includes the configuration order and the configuration type of the manufacturing information, the same name as that at the time of storage can be maintained, so that the reconfiguration of the file name can be eliminated.

(4) In the information management system described in (1), (2) or (3), an HTML having a hierarchical structure
By converting the production information created by the document into an archive file maintaining the hierarchical structure, storing the archive information in a storage unit for storing the production information, and registering the HTML document in the WWW server, HTML with
Since the manufacturing information created as a document is one file, registration in the information management system can be easily performed.

(5) In the information management system described in (1), (2), (3) or (4), the management number is set by automatic numbering or a combination of arbitrary character string designation and automatic numbering. By providing the means for performing the above, it is possible to manage the manufacturing information with an easy-to-understand management number, and to quickly select from the information list.

(6) In the information management system described in (1), (2), (3), (4) or (5), the revision of the product information is registered by the registrant of the product information and the department to which the user belongs. By providing means for confirming that only one person performs the operation, it is possible to prevent erroneous product edition information from being revised and registered by another department.

(7) (1), (2), (3), (4),
In the information management system described in (5) or (6),
By providing a means for setting a reference destination of manufacturing information and a means for restricting reference to manufacturing information that is not set as a reference destination, information disclosure by suppressing disclosure to departments other than related departments And use of incorrect information can be prevented.

[0014]

FIG. 1 is a block diagram showing the configuration of an information management system according to the present invention. In the figure, reference numeral 20 denotes an information management server which manages manufacturing information, and 10 denotes an information management client which is connected to the information management server 20 via a network and registers and references the manufacturing information.

The information management server 20 includes a WWW server 21
And Web data 22 which is made public by the WWW server 21 and stores manufacturing information created in a specific file format and HTML format. Further, it receives information such as a management number, a version number, a registrant name, a department name of a registrant, a revised version, and a comment, which are manufacturing information and its management data, from the information management client 10, and outputs the manufacturing information and its management. The data is stored in the storage unit 24, and the production information of the compressed HTML document having the hierarchical structure is decompressed and registered in the Web data 22, and is also stored in the DXF format or CSV.
A specific file format that can refer to manufacturing information such as a format using a single application, for example, PDF (Portab
le Document Format, a document viewer developed by Adobe Systems, Inc. A file format that can be displayed and printed with software Acrobat) An information receiving unit 23 that converts and registers the web data 22 and a PDF file that converts manufacturing information created in a plurality of formats into a PDF format and integrates it into one file A conversion unit 25 and a file decompression unit 26 for decompressing a compressed file are provided.

The information management client 10 includes a WWW browser 11 for referring to and acquiring structure information published on the WWW server 21 of the information management server 20, and a storage unit for storing structure information for registration or edition registration. 1
4 and the structure information of the hierarchically structured HTML document is compressed into one file, and the structure information such as DXF format and CSV format is made into one data set, and the management number, version number, registrant name, registrant An information transmission unit 12 for adding management data such as a department name, revised contents, and comments to the information management server 20 and transmitting the same to the information management server 20 and a file compression unit 13 for compressing files having a hierarchical structure into one file are provided. I have.

The storage unit 24 stores the manufacturing information transmitted from the information management client, and stores the compressed HTML document in the same format and hierarchical structure as the transmitting side, in DXF format, CSV format. Manufacturing information such as 1
It is stored in the form of two datasets.

The storage unit 24 stores an information management table for storing management data for managing the manufacturing information, a revision history table for storing the revision history information of the manufacturing information, and a user of the information management system. Stores user tables, etc.

FIG. 2 shows a configuration diagram of an embodiment of the information management table and the revision history table. The information management table 241 includes a management number for managing manufacturing information, a version number, a name, a registrant name, a registered department signature, a registered file name, a file name in the system indicating a registered file name in the information management system, and a revised content. , A comment, a reference section name indicating a department to which manufacturing information can be referred to, a revision history table indicating a related revision history table name, and the like.

The revision history table 242 stores the version number,
It consists of the registrant's name, the contents of the revised edition, and comments.

FIG. 3 shows a configuration diagram of an embodiment of the user table. The user table 243 includes a user name, a department name, and a password.

FIG. 4 shows a configuration diagram of an embodiment of Web data. The web data 22 includes, in addition to the manufacturing information in the PDF file format and the manufacturing information in the HTML file format stored in the information receiving unit 23, a user confirmation HTML that controls a user interface with the information management client,
Acceptance notification HTML, information list HTML, information registration HTML
H such as L, revision information list HTML, revision registration HTML
A TML file is stored.

FIG. 5 shows a display screen of an embodiment of a user confirmation HTML document. FIG. 5A shows that the user of the information management client inputs the URL (Uniform Resource Loc) of the WWW server of the information management server to the address of the WWW browser.
ator) is a user authentication screen displayed when the information management system is used.
A user confirmation applet is linked to the OK button. When the user inputs a user name and a password and presses the OK button, the user confirmation applet is executed, and a user authentication process is performed.

FIG. 5B is a display screen of a reception notice HTML document created based on the execution result of the user confirmation applet, and shows that the information management system has accepted access from the user. The user can perform information list, information registration, and edition registration processing from this screen, and each item is linked with an information list creation applet, an information registration applet, and an edition registration applet.

FIG. 6 shows a processing flowchart of one embodiment of the user confirmation applet. Hereinafter, the operation will be described according to this flow.

Step S601: It is checked whether the user name and the password input on the user authentication screen are registered in the user table.

Step S602: As a result of the processing in step S601, if registered, the process proceeds to step S603, and if not registered, the process proceeds to step S604.

Step S603: A reception notifying HTML document as shown in FIG. 5B for notifying that the access to the information management system has been received is created and displayed. And
The process ends.

Step S604: Display an error message indicating that access to the information management system is not possible. Then, the process ends.

The operation of the information list creation applet will be described with reference to FIGS. FIG. 7 is a processing flowchart of an embodiment of an information list creation applet, and FIG. 8 is a display screen of an embodiment of an information list HTML document. Less than,
The operation will be described according to the flow of FIG. Note that the information list creation applet is linked to the information list in FIG. 5B and is executed when the information list is selected with a mouse or the like.

Step S701: The department name of the user name entered on the user authentication screen is obtained from the user table.

Step S702: Information management of management data (management number, version number, name, registrant name, registration section signature, etc.) of manufacturing information in which the obtained department name and the reference section signature of the information management table match. Extracted from table, information list H
Create and display a TML document. Then, the process ends.

FIG. 8 shows an example of a display screen of the information list HTML document. The detail display button on this screen is linked to the detail display applet, the reference button is linked to the manufacturing information in PDF file format corresponding to the management number, and when the browse button is pressed, the PDF file format is displayed on the WWW browser. Will be displayed.

The operation of the detailed display applet will be described with reference to FIGS. FIG. 9 is a processing flowchart of an embodiment of a detail display applet, and FIG. 10 is a display screen of an embodiment of a detail display HTML document. Hereinafter, FIG.
The operation will be described in accordance with the flow of FIG. The detail display applet is linked to the detail display button in FIG. 8 and is executed when the button is selected with a mouse or the like.

Step S901: A revision history table corresponding to the specified management number is obtained from the information management table.

Step S902: The name, registrant name, revised content, and comment for each version number are read from the obtained revision history table, and a detailed display HTML document as shown in FIG. 10 is created and displayed. Then, the process ends.

FIG. 11 shows a display screen of one embodiment of the information registration HTML document. This information registration HTML document is created by the information registration applet linked to the information registration in FIG. 5B, and displays the name of the registrant (user) and the name of the registration unit, the management number of the manufacturing information to be registered, Input fields such as version number, revised contents, comment, registered file name, reference section name, etc., and a registration button for instructing execution of registration processing are displayed. Note that a plurality of registered file names and reference destination signatures can be specified. Although the management number is displayed as an automatically numbered number, it may be added or changed for easy management.

Then, by pressing the registration button, the information transmission applet linked to the registration button is executed, and the registration process is performed.

FIG. 12 is a processing flowchart of one embodiment of the information transmission applet. The operation will be described below according to this flow.

Step S1201: Determine whether the file format of the file to be registered includes HTML. HTML
If there is, the process proceeds to step S1202, and if there is no HTML, the process proceeds to step S1204.

Step S1202: Archive all files under the directory where the HTML file to be registered exists. Here, one compressed file is created using a file compression unit while maintaining the hierarchical structure.

Step S1203: Information management data, an archive file (compressed file), and other registered files except HTML are transmitted to the information management server. Then, the process ends.

Step S1204: The information management data and the registration file are transmitted to the information management server. Then, the process ends.

FIG. 13 shows a processing flowchart of one embodiment of the information receiving section. This process is always executed while the information management system is operating, and receives the manufacturing information and its management data transmitted from the information management client and stores them in the storage unit or the Web data.

The operation will be described below according to this flow.

Step S1301: Determine whether the file format of the file to be registered includes HTML. HTML
If there is, the process proceeds to step S1302, and if there is no HTML, the process proceeds to step S1304.

Step S1302: A registration file other than an archive file (compressed file) is converted into a PDF file format via a PDF conversion unit, and registered as one file in Web data.

Step S1303: The archive file (compressed file) is restored by the file decompression unit, and the returned HTML file group is registered in Web data. Then, the process proceeds to step S1305.

Step S1304: Register file as P
The data is converted into the PDF file format via the DF conversion unit, and is registered in the Web data as one file.

Step S1305: The file name of the registered file is changed to a unique file name in the information management system and stored in the storage unit.

Step S1306: The original registered file name is added to the management data and stored in the information management table.
Then, the process ends.

Referring to FIGS. 14 and 15, the operation of the edition information list creation applet will be described. FIG. 14 is a processing flowchart of one embodiment of a revision information list creation applet, and FIG. 15 is a display screen of one embodiment of a revision information list HTML document. Hereinafter, the operation will be described according to the flow of FIG. The update information list creation applet is linked to the update registration in FIG. 5B, and is executed when the update registration is selected with a mouse or the like.

Step S1401: The department name of the user name entered on the user authentication screen is obtained from the user table.

Step S1402: Information management of management data (management number, version number, name, registrant name, registration section signature, etc.) of manufacturing information in which the obtained section name and registration section name in the information management table match. It extracts from the table, creates and displays a revision information list HTML document. Then, the process ends.

FIG. 15 shows an example of a display screen of the revision information list HTML document. The revision button on this screen is linked to a revision registration applet for creating a revision registration HTML document, and the takeout button is linked to a file takeout applet.

FIG. 16 shows a display screen of an embodiment of the revised registration HTML document. This revision registration HTML document is created by a revision registration applet linked to a revision button shown in FIG. 15, and displays a registrant name (user), a registration department signature, a management number, a name, and information on manufacturing information to be revised and registered. Version number,
Input fields for the contents of the revision, comments, registered file name, reference section name, etc., and a registration button for instructing execution of the registration process are displayed. Note that a plurality of registered file names and reference destination signatures can be specified.

Then, by pressing the registration button, the information transmission applet shown in FIG. 12 linked to the registration button is executed, and the registration processing is performed.

FIG. 17 shows a processing flowchart of one embodiment of the file retrieval applet. Hereinafter, the operation will be described according to this flow.

Step S1701: The data of the registered file name corresponding to the designated management number is read from the information management table, and a file fetched HTML document is created so that the file can be fetched for each registered file name, and is displayed. Then, the process ends.

FIG. 18 shows a display screen of an embodiment of the file retrieval HTML document. On this screen, each file of manufacturing information is linked to each registered file name. By selecting the registered file name to be extracted with a mouse or the like, the registered file stored in the storage unit of the information management server is displayed on the information management client. Is copied to

[0061]

The present invention is embodied in the form described above, and has the following effects.

By converting manufacturing information created in a plurality of file formats into a PDF file format and integrating it into one file and registering it in a WWW server, it is possible to refer to only a single application. Become. In addition, since only a single application is used, an environment for an information management client can be easily constructed,
Operability can also be improved.

Further, by making the manufacturing information and its PDF file into one data set, it is possible to easily perform operations of referring to and extracting the manufacturing information.

When the file of the manufacturing information is taken out, the file can be taken out with the same file name as when the file is stored. If the file name includes the configuration order and the configuration type of the manufacturing information, the file name is reconstructed. Can be eliminated.

Further, since the manufacturing information created by the HTML document having the hierarchical structure is one file, it is possible to easily register the manufacturing information in the information management system.

Also, at the time of information registration, the management number can be added or changed to the automatically numbered one.
Depending on the use of the information management system, an easy-to-understand management number can be assigned, and selection from the information list can be performed quickly.

In addition, since only the list of manufacturing information of the registered department name that matches the department name of the user is displayed from the information management table on the revised information list screen, the revised version information of incorrect manufacturing information from another department is registered. Can be prevented.

Also, since the information list screen displays only a list of manufacturing information of the reference department name that matches the department name of the user from the information management table, disclosure to departments other than the related department can be suppressed. Leakage and incorrect use of information can be prevented.

[Brief description of the drawings]

FIG. 1 is a configuration block diagram of an information management system of the present invention.

FIG. 2 is a configuration diagram of an embodiment of an information management table and a revision history table;

FIG. 3 is a configuration diagram of an embodiment of a user table.

FIG. 4 is a configuration diagram of an embodiment of Web data.

FIG. 5 is a display screen of an embodiment of a user confirmation HTML document.

FIG. 6 is a processing flowchart of an embodiment of a user confirmation applet.

FIG. 7 is a processing flowchart of an embodiment of an information list creation applet.

FIG. 8 is a display screen of an embodiment of an information list HTML document.

FIG. 9 is a processing flowchart of an embodiment of a detail display applet.

FIG. 10 is a display screen of an embodiment of a detailed display HTML document.

FIG. 11 is a display screen of an embodiment of an information registration HTML document.

FIG. 12 is a processing flowchart of an embodiment of an information transmission applet.

FIG. 13 is a processing flowchart of an embodiment of an information receiving unit.

FIG. 14 is a processing flowchart of an embodiment of a revision information list creation applet.

FIG. 15 is a display screen of an embodiment of a revision information list HTML document.

FIG. 16 is a display screen of an embodiment of a revision registration HTML document.

FIG. 17 is a processing flowchart of an embodiment of a file extracting applet.

FIG. 18 is a display screen of an embodiment of a file retrieval HTML document.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 Information management client 11 WWW browser 12 Information transmission part 13 File compression part 14 Storage part 20 Information management server 21 WWW server 22 Web data 23 Information reception part 24 Storage part 25 PDF conversion part 26 File decompression part

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G06F 17/60 512 G06F 17/60 512 F Term (Reference) 5B049 AA01 BB07 CC00 DD05 FF03 FF09 GG04 GG07 5B075 KK45 KK63 KK65 KK66 ND03 ND20 ND35 NK54 NR02 PP22 PQ02

Claims (7)

[Claims] 1. Using a WWW server and a WWW client, register and provide information on manufacturing information and management data, such as a management number, a version number, a registrant name, a department name of a registrant, a revised content, and a comment. In an information management system, manufacturing information created in a plurality of file formats is converted into a specific file format, and integrated into one file to create a W file.
An information management system comprising means for registering in a WW server. 2. The information management system according to claim 1, wherein the manufacturing information created in a plurality of file formats and a specific file converted into a specific file format and integrated into one file are stored in one file. An information management system, comprising: means for storing in a storage unit that stores manufacturing information as one data set; and means for acquiring each of the manufacturing information stored from the storage unit that stores the manufacturing information. 3. The information management system according to claim 2, further comprising: means for acquiring a file of the manufacturing information from a storage unit for storing the manufacturing information with the same file name as when storing the file. Information management system. 4. The information management system according to claim 1, wherein the production information created by the HTML document having the hierarchical structure is converted into an archive file maintaining the hierarchical structure.
An information management system, comprising: means for storing in a storage unit for storing manufacturing information and registering an HTML document in a WWW server. 5. An information management system according to claim 1, further comprising means for setting a management number by automatic numbering or by a combination of arbitrary character string designation and automatic numbering. And information management system. 6. The information management system according to claim 1, wherein it is confirmed that only the registrant of the manufacturing information and a person in the department to which the manufacturing information is updated are registered. An information management system comprising means. 7. The information management system according to claim 1, wherein: means for setting a reference destination of the production information; and restriction of reference to the production information not set as the reference destination. An information management system comprising: